[Desktop-packages] [Bug 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop
I have the same issue with my Lenovo Thinkpad. The internal mic doesn't work, but when using a headset the mic works. Details: ❯ uname -a Linux my-laptop 5.3.0-28-generic #30~18.04.1-Ubuntu SMP Fri Jan 17 06:14:09 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux ❯ arecord -l List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 2: ALC285 Alt Analog [ALC285 Alt Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 System Information Manufacturer: LENOVO Product Name: 20QES0H400 Version: ThinkPad X1 Carbon 7th -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1840725 Title: Microphone not working in Ubuntu 18.04.3 LTS on new hp- spectre-x360-convertible-15 laptop Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal Microphone does not work in Ubuntu 18.04.3 LTS in a new hp- spectre-x360-convertible-15 laptop. The microphone works perfectly on Windows 10 (present in Dual boot mode). Initially, Internal Microphone was not even detected but installing alsa-tools-gui and overriding pin 0x12 to the Internal Microphone fixed that issue. [Pin 0x13 does not work and causes static in a headphone if it is plugged in.] Microphone is not able to pick up any sound. I changed levels/settings in alsamixer, pavucontrol without any success: In alsamixer: Experimented with levels ranging from very low to very high for Internal Mic, Capture, etc. In pavucontrol: Set the Internal Mic as a fallback device, unlocked the channels for the mic, experimented with reducing the level for one of the channels (reduced right mic level to Silence while keeping the left mic level normal/high and vice versa). alsa-info: http://alsa-project.org/db/?f=cf6d3ccc6372f955da7d99df07afbcb31d5a6c7f arecord -l List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1840725/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1862531] Re: [focal] Wayland session is not available when a laptop has an Nvidia card an Intel card is in use
I see, thanks for the clarification. I will need to read through other cases as well. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1862531 Title: [focal] Wayland session is not available when a laptop has an Nvidia card an Intel card is in use Status in gdm3 package in Ubuntu: Incomplete Status in nvidia-prime package in Ubuntu: Invalid Bug description: A Wayland session present at /usr/share/wayland-sessions/ubuntu- wayland.desktop is not displayed at the login screen when a system has an iGPU (Intel) and dGPU (Nvidia) and Intel iGPU is used: prime-select query intel Only sessions at /usr/share/xsessions are present. ➜ ~ ls /usr/share/xsessions remmina-gnome.desktop ubuntu.desktop ➜ ~ ls /usr/share/wayland-sessions ubuntu-wayland.desktop The root cause is the existence of a udev rule in 61-gdm.rules that runs gdm-disable-wayland when an nvidia driver is loaded in combination with LP: #1848326 (see this comment specifically https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1848326/comments/7). dpkg -S /lib/udev/rules.d/61-gdm.rules gdm3: /lib/udev/rules.d/61-gdm.rules grep nvidia /lib/udev/rules.d/61-gdm.rules # disable Wayland when using the proprietary nvidia driver DRIVER=="nvidia", RUN+="/usr/lib/gdm3/gdm-disable-wayland" When I comment it out and reboot, I get the right menu entry and am able to observe the right session type: ➜ ~ grep nvidia /lib/udev/rules.d/61-gdm.rules # disable Wayland when using the proprietary nvidia driver #DRIVER=="nvidia", RUN+="/usr/lib/gdm3/gdm-disable-wayland" ➜ ~ loginctl SESSION UID USER SEAT TTY 2 1000 dima seat0 tty2 1 sessions listed. ➜ ~ loginctl show-session 2 -p Type Type=wayland System info: lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Focal Fossa (development branch) Release: 20.04 Codename: focal ➜ ~ dpkg -l | grep gdm3 ii gdm3 3.34.1-1ubuntu1 amd64GNOME Display Manager ➜ ~ dpkg -l | grep nvidia-prime ii nvidia-prime 0.8.13 all Tools to enable NVIDIA's Prime ➜ ~ dpkg -l | grep nvidia-driver ii nvidia-driver-440 440.59-0ubuntu1 amd64NVIDIA driver metapackage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1862531/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1862531] Re: [focal] Wayland session is not available when a laptop has an Nvidia card an Intel card is in use
BTW, we don't want to remove the udev rule because removing it causes a bigger problem for more people: bug 1705369 So a general fix like https://gitlab.gnome.org/GNOME/mutter/merge_requests/625 would need to exist before the udev rule can be removed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1862531 Title: [focal] Wayland session is not available when a laptop has an Nvidia card an Intel card is in use Status in gdm3 package in Ubuntu: Incomplete Status in nvidia-prime package in Ubuntu: Invalid Bug description: A Wayland session present at /usr/share/wayland-sessions/ubuntu- wayland.desktop is not displayed at the login screen when a system has an iGPU (Intel) and dGPU (Nvidia) and Intel iGPU is used: prime-select query intel Only sessions at /usr/share/xsessions are present. ➜ ~ ls /usr/share/xsessions remmina-gnome.desktop ubuntu.desktop ➜ ~ ls /usr/share/wayland-sessions ubuntu-wayland.desktop The root cause is the existence of a udev rule in 61-gdm.rules that runs gdm-disable-wayland when an nvidia driver is loaded in combination with LP: #1848326 (see this comment specifically https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1848326/comments/7). dpkg -S /lib/udev/rules.d/61-gdm.rules gdm3: /lib/udev/rules.d/61-gdm.rules grep nvidia /lib/udev/rules.d/61-gdm.rules # disable Wayland when using the proprietary nvidia driver DRIVER=="nvidia", RUN+="/usr/lib/gdm3/gdm-disable-wayland" When I comment it out and reboot, I get the right menu entry and am able to observe the right session type: ➜ ~ grep nvidia /lib/udev/rules.d/61-gdm.rules # disable Wayland when using the proprietary nvidia driver #DRIVER=="nvidia", RUN+="/usr/lib/gdm3/gdm-disable-wayland" ➜ ~ loginctl SESSION UID USER SEAT TTY 2 1000 dima seat0 tty2 1 sessions listed. ➜ ~ loginctl show-session 2 -p Type Type=wayland System info: lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Focal Fossa (development branch) Release: 20.04 Codename: focal ➜ ~ dpkg -l | grep gdm3 ii gdm3 3.34.1-1ubuntu1 amd64GNOME Display Manager ➜ ~ dpkg -l | grep nvidia-prime ii nvidia-prime 0.8.13 all Tools to enable NVIDIA's Prime ➜ ~ dpkg -l | grep nvidia-driver ii nvidia-driver-440 440.59-0ubuntu1 amd64NVIDIA driver metapackage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1862531/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1862531] Re: [focal] Wayland session is not available when a laptop has an Nvidia card an Intel card is in use
Hi Daniel, thank you for the quick response and prior work. I think the upstream check for the nvidia driver in 61-gdm.rules is too broad to be useful as the nvidia driver might be loaded for other reasons (e.g. CUDA usage or hw accelerated video encoding/decoding while nvidia-drm.ko is blacklisted) so I believe I can come up with an issue upstream. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1862531 Title: [focal] Wayland session is not available when a laptop has an Nvidia card an Intel card is in use Status in gdm3 package in Ubuntu: Incomplete Status in nvidia-prime package in Ubuntu: Invalid Bug description: A Wayland session present at /usr/share/wayland-sessions/ubuntu- wayland.desktop is not displayed at the login screen when a system has an iGPU (Intel) and dGPU (Nvidia) and Intel iGPU is used: prime-select query intel Only sessions at /usr/share/xsessions are present. ➜ ~ ls /usr/share/xsessions remmina-gnome.desktop ubuntu.desktop ➜ ~ ls /usr/share/wayland-sessions ubuntu-wayland.desktop The root cause is the existence of a udev rule in 61-gdm.rules that runs gdm-disable-wayland when an nvidia driver is loaded in combination with LP: #1848326 (see this comment specifically https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1848326/comments/7). dpkg -S /lib/udev/rules.d/61-gdm.rules gdm3: /lib/udev/rules.d/61-gdm.rules grep nvidia /lib/udev/rules.d/61-gdm.rules # disable Wayland when using the proprietary nvidia driver DRIVER=="nvidia", RUN+="/usr/lib/gdm3/gdm-disable-wayland" When I comment it out and reboot, I get the right menu entry and am able to observe the right session type: ➜ ~ grep nvidia /lib/udev/rules.d/61-gdm.rules # disable Wayland when using the proprietary nvidia driver #DRIVER=="nvidia", RUN+="/usr/lib/gdm3/gdm-disable-wayland" ➜ ~ loginctl SESSION UID USER SEAT TTY 2 1000 dima seat0 tty2 1 sessions listed. ➜ ~ loginctl show-session 2 -p Type Type=wayland System info: lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Focal Fossa (development branch) Release: 20.04 Codename: focal ➜ ~ dpkg -l | grep gdm3 ii gdm3 3.34.1-1ubuntu1 amd64GNOME Display Manager ➜ ~ dpkg -l | grep nvidia-prime ii nvidia-prime 0.8.13 all Tools to enable NVIDIA's Prime ➜ ~ dpkg -l | grep nvidia-driver ii nvidia-driver-440 440.59-0ubuntu1 amd64NVIDIA driver metapackage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1862531/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1862450] Re: g_type_class_add_private() deprecated
** No longer affects: bamf (Ubuntu) ** Changed in: bamf Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bamf in Ubuntu. https://bugs.launchpad.net/bugs/1862450 Title: g_type_class_add_private() deprecated Status in BAMF: New Bug description: Hi all, Glib had deprecated "g_type_class_add_private()" with "G_ADD_PRIVATE()" with taking only one argument. Thanks, Jay To manage notifications about this bug go to: https://bugs.launchpad.net/bamf/+bug/1862450/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1862450] Re: g_type_class_add_private() deprecated
Hi Daniel, I am using unlisted OS : NetBSD 8.1 Release PKGSRC2019Q4 AMD64 Application : Vala-panel-appmenu [ https://gitlab.com/vala-panel-project/vala-panel-appmenu/-/releases ] bamf version : 0.5.4 Error : https://pastebin.com/9fUUabGF Patch i applied : ` SUBST_CLASSES+= fix-gtype SUBST_STAGE.fix-gtype= pre-configure SUBST_MESSAGE.fix-gtype=changing G_ADD_PRIVATE instead g_type_class_add_private() SUBST_FILES.fix-gtype+= work/*.c SUBST_SED.fix-gtype+= -e 's,"g_type_class_add_private(),"G_ADD_PRIVATE(),g' ` but G_ADD_PRIVATE(x) takes only one argument and older g_type_class_add_private(x,y) took two ones. Thanks, Jay -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bamf in Ubuntu. https://bugs.launchpad.net/bugs/1862450 Title: g_type_class_add_private() deprecated Status in BAMF: Incomplete Status in bamf package in Ubuntu: Incomplete Bug description: Hi all, Glib had deprecated "g_type_class_add_private()" with "G_ADD_PRIVATE()" with taking only one argument. Thanks, Jay To manage notifications about this bug go to: https://bugs.launchpad.net/bamf/+bug/1862450/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1862500] Re: Desktop icons are placed off-screen when using multiple monitors
I saw those. I was wondering how you know they're there if they're not visible in the screenshot. But now I remember mutter/gnome-shell will clip each screen so generally nothing will appear in those black offscreen areas even in screenshots. This issue might be caused by the absence of any screen in the usual top-left corner (0,0). Regardless, if this is Ubuntu 18.04 then the desktop icons are provided by nautilus-desktop, which is not being developed any more, and not available in later Ubuntu versions :/ ** Changed in: nautilus (Ubuntu) Status: Incomplete => New ** Tags added: multi-monitor ** Tags removed: multi-monitor ** Tags added: multimonitor -- 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/1862500 Title: Desktop icons are placed off-screen when using multiple monitors Status in nautilus package in Ubuntu: New Bug description: I have 2 monitors connected in "Join Display Mode". Monitor 1 (secondary) 1366x798, Landscape, 100% Monitor 2 (primary) 1920x1080, Landscape, 100% I can see files on the Desktop inside the File Browser, but on the Desktop icons are either not visible or limited text from one of the icons can be seen in the top left corner of the secondary monitor. Screenshots attached. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Feb 9 10:16:18 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: ndiswrapper, 1.60, 5.3.0-28-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0162] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [17aa:3083] Advanced Micro Devices, Inc. [AMD/ATI] Caicos PRO [Radeon HD 7450] [1002:677b] (prog-if 00 [VGA controller]) Subsystem: Bitland(ShenZhen) Information Technology Co., Ltd. Caicos PRO [Radeon HD 7450] [1642:3a76] InstallationDate: Installed on 2019-12-20 (50 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: LENOVO 3212AP3 ProcEnviron: LANGUAGE=en_ZA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_ZA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=c29a-51cf-4584-b908-5081f9693928 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/21/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 9SKT63AUS dmi.board.name: MAHOBAY dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnLENOVO:bvr9SKT63AUS:bd03/21/2013:svnLENOVO:pn3212AP3:pvrThinkCentreM92p:rvnLENOVO:rnMAHOBAY:rvrNODPK:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: 3212AP3 dmi.product.sku: LENOVO_MT_3212 dmi.product.version: ThinkCentre M92p dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1862500/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1862500] Re: Desktop icons are placed off-screen when using multiple monitors
Hi Daniel, screenshot added in comment #2. There are about 6 files in the Desktop folder, which is not visible in the screenshot. -- 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/1862500 Title: Desktop icons are placed off-screen when using multiple monitors Status in nautilus package in Ubuntu: Incomplete Bug description: I have 2 monitors connected in "Join Display Mode". Monitor 1 (secondary) 1366x798, Landscape, 100% Monitor 2 (primary) 1920x1080, Landscape, 100% I can see files on the Desktop inside the File Browser, but on the Desktop icons are either not visible or limited text from one of the icons can be seen in the top left corner of the secondary monitor. Screenshots attached. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Feb 9 10:16:18 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: ndiswrapper, 1.60, 5.3.0-28-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0162] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [17aa:3083] Advanced Micro Devices, Inc. [AMD/ATI] Caicos PRO [Radeon HD 7450] [1002:677b] (prog-if 00 [VGA controller]) Subsystem: Bitland(ShenZhen) Information Technology Co., Ltd. Caicos PRO [Radeon HD 7450] [1642:3a76] InstallationDate: Installed on 2019-12-20 (50 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: LENOVO 3212AP3 ProcEnviron: LANGUAGE=en_ZA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_ZA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=c29a-51cf-4584-b908-5081f9693928 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/21/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 9SKT63AUS dmi.board.name: MAHOBAY dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnLENOVO:bvr9SKT63AUS:bd03/21/2013:svnLENOVO:pn3212AP3:pvrThinkCentreM92p:rvnLENOVO:rnMAHOBAY:rvrNODPK:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: 3212AP3 dmi.product.sku: LENOVO_MT_3212 dmi.product.version: ThinkCentre M92p dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1862500/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1862531] Re: [focal] Wayland session is not available when a laptop has an Nvidia card an Intel card is in use
Although we can always try again and search for a third solution, if you would like to open a new bug upstream? https://gitlab.gnome.org/GNOME/gdm/issues ** Changed in: gdm3 (Ubuntu) Status: Won't Fix => Incomplete ** Changed in: gdm3 (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1862531 Title: [focal] Wayland session is not available when a laptop has an Nvidia card an Intel card is in use Status in gdm3 package in Ubuntu: Incomplete Status in nvidia-prime package in Ubuntu: Invalid Bug description: A Wayland session present at /usr/share/wayland-sessions/ubuntu- wayland.desktop is not displayed at the login screen when a system has an iGPU (Intel) and dGPU (Nvidia) and Intel iGPU is used: prime-select query intel Only sessions at /usr/share/xsessions are present. ➜ ~ ls /usr/share/xsessions remmina-gnome.desktop ubuntu.desktop ➜ ~ ls /usr/share/wayland-sessions ubuntu-wayland.desktop The root cause is the existence of a udev rule in 61-gdm.rules that runs gdm-disable-wayland when an nvidia driver is loaded in combination with LP: #1848326 (see this comment specifically https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1848326/comments/7). dpkg -S /lib/udev/rules.d/61-gdm.rules gdm3: /lib/udev/rules.d/61-gdm.rules grep nvidia /lib/udev/rules.d/61-gdm.rules # disable Wayland when using the proprietary nvidia driver DRIVER=="nvidia", RUN+="/usr/lib/gdm3/gdm-disable-wayland" When I comment it out and reboot, I get the right menu entry and am able to observe the right session type: ➜ ~ grep nvidia /lib/udev/rules.d/61-gdm.rules # disable Wayland when using the proprietary nvidia driver #DRIVER=="nvidia", RUN+="/usr/lib/gdm3/gdm-disable-wayland" ➜ ~ loginctl SESSION UID USER SEAT TTY 2 1000 dima seat0 tty2 1 sessions listed. ➜ ~ loginctl show-session 2 -p Type Type=wayland System info: lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Focal Fossa (development branch) Release: 20.04 Codename: focal ➜ ~ dpkg -l | grep gdm3 ii gdm3 3.34.1-1ubuntu1 amd64GNOME Display Manager ➜ ~ dpkg -l | grep nvidia-prime ii nvidia-prime 0.8.13 all Tools to enable NVIDIA's Prime ➜ ~ dpkg -l | grep nvidia-driver ii nvidia-driver-440 440.59-0ubuntu1 amd64NVIDIA driver metapackage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1862531/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1385061] Re: Cannot map Alt-k
[Expired for gnome-terminal (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-terminal (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1385061 Title: Cannot map Alt-k Status in gnome-terminal package in Ubuntu: Expired Bug description: I am unable to map anything to Alt-k from the keyboard shortcut menu. May have something to do with the feature that holding alt puts you in a context where you can select checkboxes and buttons by pressing another key. However I can map Alt-j and there are no issues. I do not have Alt-k mapped any where else in gnome or Ubuntu. I was able to work around the issue by editting the gconf settings file, however this should be fixed. I am also using Ubuntu Gnome. Description: Ubuntu 14.04.1 LTS Release: 14.04 gnome-terminal: Installed: 3.6.2-0ubuntu1 Candidate: 3.6.2-0ubuntu1 Version table: *** 3.6.2-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-terminal 3.6.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Oct 24 02:00:52 2014 InstallationDate: Installed on 1923-12-20 (33180 days ago) InstallationMedia: Ubuntu-GNOME 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1385061/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1395898] Re: gnome terminal crashes when having multiple terminals open and when i try to use tab complete
[Expired for gnome-terminal (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-terminal (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1395898 Title: gnome terminal crashes when having multiple terminals open and when i try to use tab complete Status in gnome-terminal package in Ubuntu: Expired Bug description: I had multiple terminals open with a few ssh connection going to servers(close to 10). I did a tab complete on my local machine suddenly my gnome terminal crashed. I ll try to reproduce the bug and get any further diagnostics I could get ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-terminal 3.6.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Nov 24 16:08:11 2014 InstallationDate: Installed on 2014-09-24 (61 days ago) InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.3) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1395898/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1862566] Re: Corrupt sound played
Can you please test a newer kernel? Either from: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.5.2/ or just live boot Ubuntu 19.10: https://ubuntu.com/download/desktop ** Changed in: pulseaudio (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1862566 Title: Corrupt sound played Status in pulseaudio package in Ubuntu: Incomplete Bug description: Every once in a while, I get sort of static-y sound with a degree of echo. This affects all sounds - within browser, using `play` from the terminal, etc. I can solve it by restarting pulseaudio. However, when I do that, I no longer get the terminal beep. Ubuntu 18.04 It's not common, and I can't find anything wrong in the system log. To restart, I killed the process: /usr/bin/pulseaudio --start --log-target=syslog It restarts itself, and audio generally seems to be working now. However, I now see in the system log things like: Feb 9 22:05:38 cerberus update-notifier.desktop[4802]: [9666:9666:0209/220538.227104:ERROR:pulse_util.cc(300)] pa_operation is nullptr. Feb 9 22:05:38 cerberus update-notifier.desktop[4802]: [9666:9666:0209/220538.227183:ERROR:pulse_util.cc(300)] pa_operation is nullptr. Feb 9 22:05:38 cerberus update-notifier.desktop[4802]: [8767:1:0209/220538.229919:ERROR:webrtc_sdp.cc(402)] Failed to parse: "a=msid: ". Reason: Missing track ID in msid attribute. Feb 9 22:05:38 cerberus update-notifier.desktop[4802]: [8767:1:0209/220538.243052:ERROR:rtc_peer_connection_handler.cc(2446)] Failed to create native session description. Type: "offer" SDP: "v=0\r\no=- 4839823990544483155 2 IN IP4 127.0.0.1\r\ns=-\r\nt=0 0\r\na=group:BUNDLE 0\r\na=msid-semantic: WMS\r\nm=application 9 UDP/TLS/RTP/SAVPF 119\r\nc=IN IP4 0.0.0.0\r\nb=AS:30\r\na=rtcp:9 IN IP4 0.0.0.0\r\na=ice-ufrag:7Ejs\r\na=ice-pwd:938XM9CAOZEbY2uhDpuFrizo\r\na=ice-options:trickle\r\na=fingerprint:sha-256 23:5D:00:AF:7B:28:BA:7D:02:92:4E:00:66:5F:B3:C1:C4:F2:BD:66:2B:10:03:74:93:B5:F1:9E:61:45:A3:15\r\na=setup:actpass\r\na=mid:0\r\na=sendrecv\r\na=msid: \r\na=rtcp-mux\r\na=rtpmap:119 google-data/9\r\na=ssrc:4203958806 cname:1yXiouHPsVbMJDst\r\na=ssrc:4203958806 msid:- \r\na=ssrc:4203958806 mslabel:-\r\na=ssrc:4203958806 label:\r\n" ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.5 ProcVersionSignature: Ubuntu 4.15.0-87.87-generic 4.15.18 Uname: Linux 4.15.0-87-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Feb 9 22:02:47 2020 InstallationDate: Installed on 2016-05-30 (1350 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to bionic on 2018-09-17 (511 days ago) dmi.bios.date: 01/29/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.0c dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X10DAI dmi.board.vendor: Supermicro dmi.board.version: 1.01 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.0c:bd01/29/2015:svnSupermicro:pnX10DAi:pvr123456789:rvnSupermicro:rnX10DAI:rvr1.01:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: SMC X10 dmi.product.name: X10DAi dmi.product.version: 123456789 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1862566/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1862566] Re: Corrupt sound played
I think we should ignore the log messages after restarting and focus on the original problem of corrupt sound. Bugs should only cover a single issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1862566 Title: Corrupt sound played Status in pulseaudio package in Ubuntu: Incomplete Bug description: Every once in a while, I get sort of static-y sound with a degree of echo. This affects all sounds - within browser, using `play` from the terminal, etc. I can solve it by restarting pulseaudio. However, when I do that, I no longer get the terminal beep. Ubuntu 18.04 It's not common, and I can't find anything wrong in the system log. To restart, I killed the process: /usr/bin/pulseaudio --start --log-target=syslog It restarts itself, and audio generally seems to be working now. However, I now see in the system log things like: Feb 9 22:05:38 cerberus update-notifier.desktop[4802]: [9666:9666:0209/220538.227104:ERROR:pulse_util.cc(300)] pa_operation is nullptr. Feb 9 22:05:38 cerberus update-notifier.desktop[4802]: [9666:9666:0209/220538.227183:ERROR:pulse_util.cc(300)] pa_operation is nullptr. Feb 9 22:05:38 cerberus update-notifier.desktop[4802]: [8767:1:0209/220538.229919:ERROR:webrtc_sdp.cc(402)] Failed to parse: "a=msid: ". Reason: Missing track ID in msid attribute. Feb 9 22:05:38 cerberus update-notifier.desktop[4802]: [8767:1:0209/220538.243052:ERROR:rtc_peer_connection_handler.cc(2446)] Failed to create native session description. Type: "offer" SDP: "v=0\r\no=- 4839823990544483155 2 IN IP4 127.0.0.1\r\ns=-\r\nt=0 0\r\na=group:BUNDLE 0\r\na=msid-semantic: WMS\r\nm=application 9 UDP/TLS/RTP/SAVPF 119\r\nc=IN IP4 0.0.0.0\r\nb=AS:30\r\na=rtcp:9 IN IP4 0.0.0.0\r\na=ice-ufrag:7Ejs\r\na=ice-pwd:938XM9CAOZEbY2uhDpuFrizo\r\na=ice-options:trickle\r\na=fingerprint:sha-256 23:5D:00:AF:7B:28:BA:7D:02:92:4E:00:66:5F:B3:C1:C4:F2:BD:66:2B:10:03:74:93:B5:F1:9E:61:45:A3:15\r\na=setup:actpass\r\na=mid:0\r\na=sendrecv\r\na=msid: \r\na=rtcp-mux\r\na=rtpmap:119 google-data/9\r\na=ssrc:4203958806 cname:1yXiouHPsVbMJDst\r\na=ssrc:4203958806 msid:- \r\na=ssrc:4203958806 mslabel:-\r\na=ssrc:4203958806 label:\r\n" ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.5 ProcVersionSignature: Ubuntu 4.15.0-87.87-generic 4.15.18 Uname: Linux 4.15.0-87-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Feb 9 22:02:47 2020 InstallationDate: Installed on 2016-05-30 (1350 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to bionic on 2018-09-17 (511 days ago) dmi.bios.date: 01/29/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.0c dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X10DAI dmi.board.vendor: Supermicro dmi.board.version: 1.01 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.0c:bd01/29/2015:svnSupermicro:pnX10DAi:pvr123456789:rvnSupermicro:rnX10DAI:rvr1.01:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: SMC X10 dmi.product.name: X10DAi dmi.product.version: 123456789 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1862566/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1853638] Re: BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data
Hello Edwin, Here is more information on the issue we are seeing wrt dropped packets and other connectivity issues with this NIC. The problem is *only* seen when the second port on the NIC is chosen as the active interface of a active-backup configuration. So on the "bad" system with the interfaces: enp94s0f0 -> when chosen as active, all OK enp94s0f1d1 -> when chosen as active, not OK I'll see if the reporters can confirm that on the "good" systems, there was no problem when the second interface is active. -- 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/1853638 Title: BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: The issue appears to be with the BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data Basically, we are dropping data, as you can see from the benchmark tool as follows: tcdforge@x310a:/usr/local/lib/lib/uhd/examples$ ./benchmark_rate --rx_rate 10e6 --tx_rate 10e6 --duration 300 [INFO] [UHD] linux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_3.14.1.1-0-g98c7c986 [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:00.07] Creating the usrp device with: ... [INFO] [X300] X300 initialization sequence... [INFO] [X300] Maximum frame size: 1472 bytes. [INFO] [X300] Radio 1x clock: 200 MHz [INFO] [GPS] Found an internal GPSDO: LC_XO, Firmware Rev 0.929a [INFO] [0/DmaFIFO_0] Initializing block control (NOC ID: 0xF1F0D000) [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1308 MB/s) [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1316 MB/s) [INFO] [0/Radio_0] Initializing block control (NOC ID: 0x12AD1001) [INFO] [0/Radio_1] Initializing block control (NOC ID: 0x12AD1001) [INFO] [0/DDC_0] Initializing block control (NOC ID: 0xDDC0) [INFO] [0/DDC_1] Initializing block control (NOC ID: 0xDDC0) [INFO] [0/DUC_0] Initializing block control (NOC ID: 0xD0C0) [INFO] [0/DUC_1] Initializing block control (NOC ID: 0xD0C0) Using Device: Single USRP: Device: X-Series Device Mboard 0: X310 RX Channel: 0 RX DSP: 0 RX Dboard: A RX Subdev: SBX-120 RX RX Channel: 1 RX DSP: 0 RX Dboard: B RX Subdev: SBX-120 RX TX Channel: 0 TX DSP: 0 TX Dboard: A TX Subdev: SBX-120 TX TX Channel: 1 TX DSP: 0 TX Dboard: B TX Subdev: SBX-120 TX [00:00:04.305374] Setting device timestamp to 0... [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:04.310990] Testing receive rate 10.00 Msps on 1 channels [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:04.318356] Testing transmit rate 10.00 Msps on 1 channels [00:00:06.693119] Detected Rx sequence error. D[00:00:09.402843] Detected Rx sequence error. DD[00:00:40.927978] Detected Rx sequence error. D[00:01:44.982243] Detected Rx sequence error. D[00:02:11.400692] Detected Rx sequence error. D[00:02:14.805292] Detected Rx sequence error. D[00:02:41.875596] Detected Rx sequence error. D[00:03:06.927743] Detected Rx sequence error. D[00:03:47.967891] Detected Rx sequence error. D[00:03:58.233659] Detected Rx sequence error. D[00:03:58.876588] Detected Rx sequence error. D[00:04:03.139770] Detected Rx sequence error. D[00:04:45.287465] Detected Rx sequence error. D[00:04:56.425845] Detected Rx sequence error. D[00:04:57.929209] Detected Rx sequence error. [00:05:04.529548] Benchmark complete. Benchmark rate summary: Num received samples: 2995435936 Num dropped samples: 4622800 Num overruns detected:0 Num transmitted samples: 3008276544 Num sequence errors (Tx): 0 Num sequence errors (Rx): 15 Num underruns detected: 0 Num late commands:0 Num timeouts (Tx):0 Num timeouts (Rx):0 Done! tcdforge@x310a:/usr/local/lib/lib/uhd/examples$ In this particular case description, the nodes are USRP x310s. However, we have the same issue with N210 nodes dropping samples connected to the BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device. There is no problem with the USRPs themselves, as we hav
[Desktop-packages] [Bug 1862566] [NEW] Corrupt sound played
Public bug reported: Every once in a while, I get sort of static-y sound with a degree of echo. This affects all sounds - within browser, using `play` from the terminal, etc. I can solve it by restarting pulseaudio. However, when I do that, I no longer get the terminal beep. Ubuntu 18.04 It's not common, and I can't find anything wrong in the system log. To restart, I killed the process: /usr/bin/pulseaudio --start --log-target=syslog It restarts itself, and audio generally seems to be working now. However, I now see in the system log things like: Feb 9 22:05:38 cerberus update-notifier.desktop[4802]: [9666:9666:0209/220538.227104:ERROR:pulse_util.cc(300)] pa_operation is nullptr. Feb 9 22:05:38 cerberus update-notifier.desktop[4802]: [9666:9666:0209/220538.227183:ERROR:pulse_util.cc(300)] pa_operation is nullptr. Feb 9 22:05:38 cerberus update-notifier.desktop[4802]: [8767:1:0209/220538.229919:ERROR:webrtc_sdp.cc(402)] Failed to parse: "a=msid: ". Reason: Missing track ID in msid attribute. Feb 9 22:05:38 cerberus update-notifier.desktop[4802]: [8767:1:0209/220538.243052:ERROR:rtc_peer_connection_handler.cc(2446)] Failed to create native session description. Type: "offer" SDP: "v=0\r\no=- 4839823990544483155 2 IN IP4 127.0.0.1\r\ns=-\r\nt=0 0\r\na=group:BUNDLE 0\r\na=msid-semantic: WMS\r\nm=application 9 UDP/TLS/RTP/SAVPF 119\r\nc=IN IP4 0.0.0.0\r\nb=AS:30\r\na=rtcp:9 IN IP4 0.0.0.0\r\na=ice-ufrag:7Ejs\r\na=ice-pwd:938XM9CAOZEbY2uhDpuFrizo\r\na=ice-options:trickle\r\na=fingerprint:sha-256 23:5D:00:AF:7B:28:BA:7D:02:92:4E:00:66:5F:B3:C1:C4:F2:BD:66:2B:10:03:74:93:B5:F1:9E:61:45:A3:15\r\na=setup:actpass\r\na=mid:0\r\na=sendrecv\r\na=msid: \r\na=rtcp-mux\r\na=rtpmap:119 google-data/9\r\na=ssrc:4203958806 cname:1yXiouHPsVbMJDst\r\na=ssrc:4203958806 msid:- \r\na=ssrc:4203958806 mslabel:-\r\na=ssrc:4203958806 label:\r\n" ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.5 ProcVersionSignature: Ubuntu 4.15.0-87.87-generic 4.15.18 Uname: Linux 4.15.0-87-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Feb 9 22:02:47 2020 InstallationDate: Installed on 2016-05-30 (1350 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to bionic on 2018-09-17 (511 days ago) dmi.bios.date: 01/29/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.0c dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X10DAI dmi.board.vendor: Supermicro dmi.board.version: 1.01 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.0c:bd01/29/2015:svnSupermicro:pnX10DAi:pvr123456789:rvnSupermicro:rnX10DAI:rvr1.01:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: SMC X10 dmi.product.name: X10DAi dmi.product.version: 123456789 dmi.sys.vendor: Supermicro ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic package-from-proposed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1862566 Title: Corrupt sound played Status in pulseaudio package in Ubuntu: New Bug description: Every once in a while, I get sort of static-y sound with a degree of echo. This affects all sounds - within browser, using `play` from the terminal, etc. I can solve it by restarting pulseaudio. However, when I do that, I no longer get the terminal beep. Ubuntu 18.04 It's not common, and I can't find anything wrong in the system log. To restart, I killed the process: /usr/bin/pulseaudio --start --log-target=syslog It restarts itself, and audio generally seems to be working now. However, I now see in the system log things like: Feb 9 22:05:38 cerberus update-notifier.desktop[4802]: [9666:9666:0209/220538.227104:ERROR:pulse_util.cc(300)] pa_operation is nullptr. Feb 9 22:05:38 cerberus update-notifier.desktop[4802]: [9666:9666:0209/220538.227183:ERROR:pulse_util.cc(300)] pa_operation is nullptr. Feb 9 22:05:38 cerberus update-notifier.desktop[4802]: [8767:1:0209/220538.229919:ERROR:webrtc_sdp.cc(402)] Failed to parse: "a=msid: ". Reason: Missing track ID in msid attribute. Feb 9 22:05:38 cerberus update-notifier.desktop[4802]: [8767:1:0209/220538.243052:ERROR:rtc_peer_connection_handler.cc(2446)] Failed to create native session description. Type: "offer" SDP: "v=0\r\no=- 4839823990544483155 2 IN IP4 127.0.0.1\r\ns=-\r\nt=0 0\r\na=group:BUNDLE 0\r\na=msid-semantic: WMS\r\nm=application 9 UDP/TLS/RTP/SAVPF 119\r\nc=IN IP4 0.0.0.0\r\nb=AS:30\r\na=rtcp:9 IN IP
[Desktop-packages] [Bug 1655189] Re: Cannot record videos into Theora
** Package changed: xorg (Ubuntu) => xserver-xorg-video-intel (Ubuntu) ** Bug watch added: gitlab.freedesktop.org/xorg/driver/xf86-video-intel/issues #134 https://gitlab.freedesktop.org/xorg/driver/xf86-video-intel/issues/134 ** Changed in: xorg-server Importance: Medium => Unknown ** Changed in: xorg-server Remote watch: freedesktop.org Bugzilla #99342 => gitlab.freedesktop.org/xorg/driver/xf86-video-intel/issues #134 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1655189 Title: Cannot record videos into Theora Status in guvcview: Confirmed Status in recordmydesktop: Confirmed Status in theora: Unknown Status in X.Org X server: Unknown Status in libtheora package in Ubuntu: Triaged Status in xserver-xorg-video-intel package in Ubuntu: Triaged Bug description: HOW TO REPRODUCE: - Record a video using the Theora codec. RESULT: - In the recording the image is frozen or broken. RELEVANT DETAILS: - Doesn't matter which application you use to record or play the video. - I'm attaching samples from various programs. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libtheora0 1.1.1+dfsg.1-8 ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35 Uname: Linux 4.4.0-57-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jan 10 01:17:54 2017 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu5 libgcc1 1:6.0.1-0ubuntu1 libogg0 1.3.2-1 multiarch-support 2.23-0ubuntu5 InstallationDate: Installed on 2013-01-25 (1445 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) SourcePackage: libtheora UpgradeStatus: Upgraded to xenial on 2016-08-05 (157 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/guvcview/+bug/1655189/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1862341] Re: Errors thrown at boot: Security
I can't see that error message in any of the attached logs. Can you please collect a full system log: journalctl -b0 > journal.txt and attach it here? ** Tags added: vmware vmwgfx ** 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/1862341 Title: Errors thrown at boot: Security Status in Ubuntu: Incomplete Bug description: DETAILS: Version: Ubuntu Focal Fossa (development branch) Release: 20.04 xorg: Installed: 1:7.7+19ubuntu13 Candidate: 1:7.7+19ubuntu13 Version table: *** 1:7.7+19ubuntu13 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status Xorg, at boot, through a couple of errors: [ error ] display server started at tty -1 For 20 seconds, the xorg server went on complaining the same issue. I tried to ssh into the virtual machine in VirtualBox, and it simply logged in without a password. Note: Automatic Login was disabled. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu13 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperVersion: 1.438 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Feb 7 11:41:03 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124) Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd quiet splash --- maybe-ubiquity SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.6-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1862341/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1862500] Re: Desktop icons are placed off-screen when using multiple monitors
Just to confirm, are you able to provide a screenshot of the actual problem? ** Changed in: nautilus (Ubuntu) Status: New => Incomplete -- 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/1862500 Title: Desktop icons are placed off-screen when using multiple monitors Status in nautilus package in Ubuntu: Incomplete Bug description: I have 2 monitors connected in "Join Display Mode". Monitor 1 (secondary) 1366x798, Landscape, 100% Monitor 2 (primary) 1920x1080, Landscape, 100% I can see files on the Desktop inside the File Browser, but on the Desktop icons are either not visible or limited text from one of the icons can be seen in the top left corner of the secondary monitor. Screenshots attached. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Feb 9 10:16:18 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: ndiswrapper, 1.60, 5.3.0-28-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0162] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [17aa:3083] Advanced Micro Devices, Inc. [AMD/ATI] Caicos PRO [Radeon HD 7450] [1002:677b] (prog-if 00 [VGA controller]) Subsystem: Bitland(ShenZhen) Information Technology Co., Ltd. Caicos PRO [Radeon HD 7450] [1642:3a76] InstallationDate: Installed on 2019-12-20 (50 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: LENOVO 3212AP3 ProcEnviron: LANGUAGE=en_ZA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_ZA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=c29a-51cf-4584-b908-5081f9693928 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/21/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 9SKT63AUS dmi.board.name: MAHOBAY dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnLENOVO:bvr9SKT63AUS:bd03/21/2013:svnLENOVO:pn3212AP3:pvrThinkCentreM92p:rvnLENOVO:rnMAHOBAY:rvrNODPK:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: 3212AP3 dmi.product.sku: LENOVO_MT_3212 dmi.product.version: ThinkCentre M92p dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1862500/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1862538] Re: gnome-shell-extension-prefs crashed with signal 5 in XGetWindowProperty
** Information type changed from Private to Public ** Description changed: + https://errors.ubuntu.com/problem/ac2ebc61ed42d4f034dfa6f6769fefed42ca834e + + --- + When I use shotdowntimer extension, I've faced with this bug. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.34.3-1ubuntu1 Uname: Linux 5.4.18-050418-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Sun Feb 9 22:16:45 2020 DisplayManager: lightdm ExecutablePath: /usr/bin/gnome-shell-extension-prefs InstallationDate: Installed on 2020-01-18 (21 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcCmdline: gnome-shell-extension-prefs shutdown-timer-gnome-shell-extension RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1 Signal: 5 SourcePackage: gnome-shell StacktraceTop: - () at /lib/x86_64-linux-gnu/libX11.so.6 - _XReply () at /lib/x86_64-linux-gnu/libX11.so.6 - XGetWindowProperty () at /lib/x86_64-linux-gnu/libX11.so.6 - ca_gtk_proplist_set_for_widget () at /lib/x86_64-linux-gnu/libcanberra-gtk3.so.0 - ca_gtk_proplist_set_for_event () at /lib/x86_64-linux-gnu/libcanberra-gtk3.so.0 + () at /lib/x86_64-linux-gnu/libX11.so.6 + _XReply () at /lib/x86_64-linux-gnu/libX11.so.6 + XGetWindowProperty () at /lib/x86_64-linux-gnu/libX11.so.6 + ca_gtk_proplist_set_for_widget () at /lib/x86_64-linux-gnu/libcanberra-gtk3.so.0 + ca_gtk_proplist_set_for_event () at /lib/x86_64-linux-gnu/libcanberra-gtk3.so.0 Title: gnome-shell-extension-prefs crashed with signal 5 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: ** Summary changed: - gnome-shell-extension-prefs crashed with signal 5 in XGetWindowProperty + gnome-shell-extension-prefs crashed with signal 5 in XGetWindowProperty from window_get_desktop from ca_gtk_proplist_set_for_widget -- 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/1862538 Title: gnome-shell-extension-prefs crashed with signal 5 in XGetWindowProperty from window_get_desktop from ca_gtk_proplist_set_for_widget Status in gnome-shell package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/ac2ebc61ed42d4f034dfa6f6769fefed42ca834e --- When I use shotdowntimer extension, I've faced with this bug. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.34.3-1ubuntu1 Uname: Linux 5.4.18-050418-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Sun Feb 9 22:16:45 2020 DisplayManager: lightdm ExecutablePath: /usr/bin/gnome-shell-extension-prefs InstallationDate: Installed on 2020-01-18 (21 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcCmdline: gnome-shell-extension-prefs shutdown-timer-gnome-shell-extension RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1 Signal: 5 SourcePackage: gnome-shell StacktraceTop: () at /lib/x86_64-linux-gnu/libX11.so.6 _XReply () at /lib/x86_64-linux-gnu/libX11.so.6 XGetWindowProperty () at /lib/x86_64-linux-gnu/libX11.so.6 ca_gtk_proplist_set_for_widget () at /lib/x86_64-linux-gnu/libcanberra-gtk3.so.0 ca_gtk_proplist_set_for_event () at /lib/x86_64-linux-gnu/libcanberra-gtk3.so.0 Title: gnome-shell-extension-prefs crashed with signal 5 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1862538/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1862500] Re: Desktop icons are placed off-screen when using multiple monitors
Good news of sorts: nautilus-desktop which is what provides the desktop icons in 18.04 is no longer supported and has been replaced in later Ubuntu versions. ** Package changed: xorg (Ubuntu) => nautilus (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/1862500 Title: Desktop icons are placed off-screen when using multiple monitors Status in nautilus package in Ubuntu: Incomplete Bug description: I have 2 monitors connected in "Join Display Mode". Monitor 1 (secondary) 1366x798, Landscape, 100% Monitor 2 (primary) 1920x1080, Landscape, 100% I can see files on the Desktop inside the File Browser, but on the Desktop icons are either not visible or limited text from one of the icons can be seen in the top left corner of the secondary monitor. Screenshots attached. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Feb 9 10:16:18 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: ndiswrapper, 1.60, 5.3.0-28-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0162] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [17aa:3083] Advanced Micro Devices, Inc. [AMD/ATI] Caicos PRO [Radeon HD 7450] [1002:677b] (prog-if 00 [VGA controller]) Subsystem: Bitland(ShenZhen) Information Technology Co., Ltd. Caicos PRO [Radeon HD 7450] [1642:3a76] InstallationDate: Installed on 2019-12-20 (50 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: LENOVO 3212AP3 ProcEnviron: LANGUAGE=en_ZA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_ZA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=c29a-51cf-4584-b908-5081f9693928 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/21/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 9SKT63AUS dmi.board.name: MAHOBAY dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnLENOVO:bvr9SKT63AUS:bd03/21/2013:svnLENOVO:pn3212AP3:pvrThinkCentreM92p:rvnLENOVO:rnMAHOBAY:rvrNODPK:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: 3212AP3 dmi.product.sku: LENOVO_MT_3212 dmi.product.version: ThinkCentre M92p dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1862500/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1862564] [NEW] /usr/bin/gnome-shell-extension-prefs:5:XGetWindowProperty:window_get_desktop:ca_gtk_proplist_set_for_widget:ca_gtk_proplist_set_for_event:ca_gtk_play_for_event
*** This bug is a duplicate of bug 1862538 *** https://bugs.launchpad.net/bugs/1862538 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.34.3-1ubuntu1~19.10.1, the problem page at https://errors.ubuntu.com/problem/ac2ebc61ed42d4f034dfa6f6769fefed42ca834e 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/. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: bionic disco eoan -- 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/1862564 Title: /usr/bin/gnome-shell-extension- prefs:5:XGetWindowProperty:window_get_desktop:ca_gtk_proplist_set_for_widget:ca_gtk_proplist_set_for_event:ca_gtk_play_for_event Status in gnome-shell package in Ubuntu: New 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 3.34.3-1ubuntu1~19.10.1, the problem page at https://errors.ubuntu.com/problem/ac2ebc61ed42d4f034dfa6f6769fefed42ca834e 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/ubuntu/+source/gnome-shell/+bug/1862564/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1862564] Re: /usr/bin/gnome-shell-extension-prefs:5:XGetWindowProperty:window_get_desktop:ca_gtk_proplist_set_for_widget:ca_gtk_proplist_set_for_event:ca_gtk_play_for_event
*** This bug is a duplicate of bug 1862538 *** https://bugs.launchpad.net/bugs/1862538 ** This bug has been marked a duplicate of private bug 1862538 -- 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/1862564 Title: /usr/bin/gnome-shell-extension- prefs:5:XGetWindowProperty:window_get_desktop:ca_gtk_proplist_set_for_widget:ca_gtk_proplist_set_for_event:ca_gtk_play_for_event Status in gnome-shell package in Ubuntu: New 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 3.34.3-1ubuntu1~19.10.1, the problem page at https://errors.ubuntu.com/problem/ac2ebc61ed42d4f034dfa6f6769fefed42ca834e 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/ubuntu/+source/gnome-shell/+bug/1862564/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1745345] Re: Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed.
** Changed in: xorg-server Status: Unknown => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1745345 Title: Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. Status in X.Org X server: New Status in gstreamer-vaapi package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Confirmed Bug description: It happened after upgrade to bionic, in the first login, after logon screen. Instead of opening the desktop area, gave the error. I had to do hard reset to be able to use X. After hard reset showed the same error but after a while it entered desktop. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: xserver-xorg-core 2:1.19.5-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13 Uname: Linux 4.13.0-31-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 AssertionMessage: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. CompositorRunning: None CurrentDesktop: GNOME-Greeter:GNOME Date: Thu Jan 25 10:09:41 2018 DistUpgraded: 2018-01-25 02:34:06,581 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py ([Errno 2] Ficheiro ou directoria inexistente: './xorg_fix_proprietary.py': './xorg_fix_proprietary.py') DistroCodename: bionic DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems HD Graphics 5500 [1179:f920] Subsystem: Toshiba America Info Systems Radeon R7 M260 [1179:f923] InstallationDate: Installed on 2018-01-07 (17 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: TOSHIBA SATELLITE L50-B ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/121/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcEnviron: LANGUAGE=pt:pt_BR:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_PT.UTF-8 SHELL=/bin/false ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic root=UUID=7985a6e4-e304-4f48-97b5-9111dc373a81 ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 __GI_abort () at abort.c:90 __assert_fail_base (fmt=, assertion=assertion@entry=0x7f549469ed25 "key->initialized", file=file@entry=0x7f549469ed08 "/usr/include/xorg/privates.h", line=line@entry=122, function=function@entry=0x7f549469fd00 "dixGetPrivateAddr") at assert.c:92 __GI___assert_fail (assertion=0x7f549469ed25 "key->initialized", file=0x7f549469ed08 "/usr/include/xorg/privates.h", line=122, function=0x7f549469fd00 "dixGetPrivateAddr") at assert.c:101 ?? () from /usr/lib/xorg/modules/drivers/amdgpu_drv.so Title: Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. UpgradeStatus: Upgraded to bionic on 2018-01-25 (0 days ago) UserGroups: dmi.bios.date: 01/21/2015 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 2.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name1 dmi.board.vendor: Type2 - Board Vendor Name1 dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis ManuFacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr2.10:bd01/21/2015:svnTOSHIBA:pnSATELLITEL50-B:pvrPSKTNE-01U011EP:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion: dmi.product.family: INVALID dmi.product.name: SATELLITE L50-B dmi.product.version: PSKTNE-01U011EP dmi.sys.vendor: TOSHIBA version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.89-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A 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/xorg-server/+bug/1745345/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1811023] Re: Xorg aborts with ../../../../dix/privates.c:384: dixRegisterPrivateKey: Assertion `!global_keys[type].created' failed.
** Changed in: xorg-server Status: Unknown => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1811023 Title: Xorg aborts with ../../../../dix/privates.c:384: dixRegisterPrivateKey: Assertion `!global_keys[type].created' failed. Status in X.Org X server: New Status in xorg-server package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding xorg-server. This problem was most recently seen with package version 2:1.20.3-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/e1038a75ca80364c2c74351221e2ad5ec5d00916 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/xorg-server/+bug/1811023/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1862450] Re: g_type_class_add_private() deprecated
Jay, Can you please also mention the version of Ubuntu that's affected and confirm the project/line of code you're referring to? ** Also affects: bamf (Ubuntu) Importance: Undecided Status: New ** Changed in: bamf Status: New => Incomplete ** Changed in: bamf (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bamf in Ubuntu. https://bugs.launchpad.net/bugs/1862450 Title: g_type_class_add_private() deprecated Status in BAMF: Incomplete Status in bamf package in Ubuntu: Incomplete Bug description: Hi all, Glib had deprecated "g_type_class_add_private()" with "G_ADD_PRIVATE()" with taking only one argument. Thanks, Jay To manage notifications about this bug go to: https://bugs.launchpad.net/bamf/+bug/1862450/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1862377] Re: WXtoimg
Please explain what kind of problem you are experiencing. ** 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/1862377 Title: WXtoimg Status in Ubuntu: Incomplete Bug description: No information ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 Uname: Linux 4.16.8-xanmod9 x86_64 ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Fri Feb 7 16:11:25 2020 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family Integrated Graphics Controller [1043:13c7] InstallationDate: Installed on 2019-08-19 (171 days ago) InstallationMedia: Skywave Linux 3.1.1 - Release amd64 (20180606) MachineType: ASUSTeK Computer Inc. K54L ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.16.8-xanmod9 root=UUID=4fd4c874-6312-499d-b5b8-a0d6f67182bc ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/26/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: K54L.208 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K54L 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.:bvrK54L.208:bd09/26/2011:svnASUSTeKComputerInc.:pnK54L:pvr1.0:rvnASUSTeKComputerInc.:rnK54L:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.family: K dmi.product.name: K54L dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.92+git1805251830.c1f2d9~oibaf~x version.libgl1-mesa-dri: libgl1-mesa-dri 18.2~git1806011930.f00fcf~oibaf~x version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.2~git1806011930.f00fcf~oibaf~x version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1+git1805221933.65c9df~oibaf~x version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15+git1805201934.ac8f7b~oibaf~x xserver.bootTime: Fri Feb 7 16:04:35 2020 xserver.configfile: default xserver.errors: Failed to load module "intel" (module does not exist, 0) Failed to load module "intel" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.8 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1862377/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1745345] Re: Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed.
Also tracking (sounds closely related) in: https://gitlab.freedesktop.org/xorg/xserver/issues/781 ** Bug watch added: gitlab.freedesktop.org/xorg/xserver/issues #781 https://gitlab.freedesktop.org/xorg/xserver/issues/781 ** Also affects: xorg-server via https://gitlab.freedesktop.org/xorg/xserver/issues/781 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1745345 Title: Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. Status in X.Org X server: Unknown Status in gstreamer-vaapi package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Confirmed Bug description: It happened after upgrade to bionic, in the first login, after logon screen. Instead of opening the desktop area, gave the error. I had to do hard reset to be able to use X. After hard reset showed the same error but after a while it entered desktop. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: xserver-xorg-core 2:1.19.5-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13 Uname: Linux 4.13.0-31-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 AssertionMessage: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. CompositorRunning: None CurrentDesktop: GNOME-Greeter:GNOME Date: Thu Jan 25 10:09:41 2018 DistUpgraded: 2018-01-25 02:34:06,581 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py ([Errno 2] Ficheiro ou directoria inexistente: './xorg_fix_proprietary.py': './xorg_fix_proprietary.py') DistroCodename: bionic DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems HD Graphics 5500 [1179:f920] Subsystem: Toshiba America Info Systems Radeon R7 M260 [1179:f923] InstallationDate: Installed on 2018-01-07 (17 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: TOSHIBA SATELLITE L50-B ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/121/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcEnviron: LANGUAGE=pt:pt_BR:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_PT.UTF-8 SHELL=/bin/false ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic root=UUID=7985a6e4-e304-4f48-97b5-9111dc373a81 ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 __GI_abort () at abort.c:90 __assert_fail_base (fmt=, assertion=assertion@entry=0x7f549469ed25 "key->initialized", file=file@entry=0x7f549469ed08 "/usr/include/xorg/privates.h", line=line@entry=122, function=function@entry=0x7f549469fd00 "dixGetPrivateAddr") at assert.c:92 __GI___assert_fail (assertion=0x7f549469ed25 "key->initialized", file=0x7f549469ed08 "/usr/include/xorg/privates.h", line=122, function=0x7f549469fd00 "dixGetPrivateAddr") at assert.c:101 ?? () from /usr/lib/xorg/modules/drivers/amdgpu_drv.so Title: Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. UpgradeStatus: Upgraded to bionic on 2018-01-25 (0 days ago) UserGroups: dmi.bios.date: 01/21/2015 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 2.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name1 dmi.board.vendor: Type2 - Board Vendor Name1 dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis ManuFacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr2.10:bd01/21/2015:svnTOSHIBA:pnSATELLITEL50-B:pvrPSKTNE-01U011EP:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion: dmi.product.family: INVALID dmi.product.name: SATELLITE L50-B dmi.product.version: PSKTNE-01U011EP dmi.sys.vendor: TOSHIBA version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.89-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A 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/xorg-server/+bu
[Desktop-packages] [Bug 1811023] Re: /usr/lib/xorg/Xorg:Xorg: ../../../../dix/privates.c:384: dixRegisterPrivateKey: Assertion `!global_keys[type].created' failed.
Also tracking in: https://gitlab.freedesktop.org/xorg/xserver/issues/939 and https://errors.ubuntu.com/problem/e1038a75ca80364c2c74351221e2ad5ec5d00916 ** Tags removed: disco ** Tags added: bionic ** Summary changed: - /usr/lib/xorg/Xorg:Xorg: ../../../../dix/privates.c:384: dixRegisterPrivateKey: Assertion `!global_keys[type].created' failed. + Xorg aborts with ../../../../dix/privates.c:384: dixRegisterPrivateKey: Assertion `!global_keys[type].created' failed. ** Changed in: xorg-server (Ubuntu) Importance: Undecided => High ** Tags added: eoan focal ** Bug watch added: gitlab.freedesktop.org/xorg/xserver/issues #939 https://gitlab.freedesktop.org/xorg/xserver/issues/939 ** Also affects: xorg-server via https://gitlab.freedesktop.org/xorg/xserver/issues/939 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1811023 Title: Xorg aborts with ../../../../dix/privates.c:384: dixRegisterPrivateKey: Assertion `!global_keys[type].created' failed. Status in X.Org X server: Unknown Status in xorg-server package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding xorg-server. This problem was most recently seen with package version 2:1.20.3-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/e1038a75ca80364c2c74351221e2ad5ec5d00916 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/xorg-server/+bug/1811023/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1862281] Re: Repeatable hang within 5 minutes using stress-ng + sleep + usb mouse
Thanks. It sounds like the problem is either in Xorg or in the kernel.
Please log into "Ubuntu on Wayland" or install 'weston' and try that. We
need to know if the same bug occurs in a Wayland compositor without any
Xorg server running.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Package changed: ubuntu => xorg-server (Ubuntu)
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1862281
Title:
Repeatable hang within 5 minutes using stress-ng + sleep + usb mouse
Status in linux package in Ubuntu:
Incomplete
Status in xorg-server package in Ubuntu:
Incomplete
Bug description:
If I run a thermal transition test script (30 seconds stress-ng, 30
seconds sleep, in a loop) and move a local USB mouse, Kubuntu reliably
crashes, usually in the first couple of runs and almost 100% of the
time by run 6.
This appears to be hardware-linked, but not due to a specific piece of
bad hardware: I have swapped literally every piece of hardware in the
system.
It shows up (while running the script at the end):
- On both an MSI B450 Gaming plus max and MSI MPG X570 Gaming plus mainboard.
- On both an AMD Ryzen 5 3600 and 3600X CPU.
- With one or two sticks of RAM. I've tested both sticks individually, in
more than one mainboard slot.
- Regardless of whether the mainboard is in/attached to a case.
- Regardless of whether there is an m.2 SSD installed or I'm running off a
live Kubuntu 19.10 USB stick with no hard disk attached.
- Regardless of which of two mice I use (an old Logitech one, or a GTX 133
Gaming mouse).
- Regardless of whether I'm using a Corsair VS650 or Corsair AX850 PSU.
- Regardless of whether I'm using an AMD RX 5700 XT or using an Nvidia
Gigabyte GeForce RTX 2700 Super (with open source drivers in both cases).
- Regardless of whether I'm using KDE or XFCE.
- Regardless of whether I'm using the default KDE DM or switch to GDM3 and
set WaylandEnable=false.
- Regardless of whether I use the default 5.3.0-29-generic kernel or
5.4.17-050417-generic.
- Regardless of whether I go directly into the graphical environment or start
in runlevel 3 and then manually run startx.
- Regardless of whether it's on the rising or falling edge of the
stress-script's temperature changes.
- Regardless of bios version on the X570 mainboard (the one it shipped with,
or the newest one released in January 2020).
- Regardless of whether XMP is on or off in the bios.
- Regardless of whether I use the default or set global c-state to "control =
disabled" in the bios.
- Regardless of whether I add processor.max_cstate=5 idle=halt in grub.
- Regardless of whether or not speakers are plugged in.
- Regardless of whether I'm using a USB port that is directly on the
motherboard or is on the front of the case.
- Regardless of which monitor it is attached to.
It doesn't show up:
- On an old i7-4771 machine I have, also running Kubuntu 19.10, while running
the test script.
- When I use a mouse remotely with ssh -Y [ip of the machine I am reporting
this from] xeyes, while running the test script.
- When I do non-mouse USB input, ie via a USB keyboard or USB wifi dongle,
including under saturated network load, while running the test script.
- During stress tests of the GPU, CPU, etc. Tools like memtest, mprime,
Unigine Superposition, repeated kernel compiles, etc run stably overnight.
- When the system is entirely idle aside from mouse movement.
- When I start in runlevel 3 and run the same test script, using the mouse
with gpm.
- Running the same test script without mouse movement: this was stable
overnight, then crashed within a couple of minutes of moving the mouse.
It shows up with load other than the stress-ng+sleep script too, but
much less reliably - I'm writing this bug report on the relevant
machine, with firefox open. Crashes occur at least once a week under
these conditions, but not frequently.
Crashes occur with sensor-reported CPU temperatures of 32 to 41
degrees Celsius. Nothing is overheating, and the system is stable at
much higher temperatures under sustained stress tests.
The symptoms of the crash: the display stops updating and the system
does not respond to any further input, including via the network or
magic sysrq key. There is nothing related to it in syslog or
journalctl, including when I'm running journalctl -f at the time of
the crash.
The test script:
#!/bin/bash
for x in {1..1}
do
echo "Run $x at `date`"
stress-ng --cpu 12 --cpu-method all --verify -t 30s --metrics-brief
sleep 30
done
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: xorg 1:7.7+19ubuntu12
Uname: Linux 5.4.17-050417-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.2
A
[Desktop-packages] [Bug 1811023] Re: /usr/lib/xorg/Xorg:Xorg: ../../../../dix/privates.c:384: dixRegisterPrivateKey: Assertion `!global_keys[type].created' failed.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg-server (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1811023 Title: Xorg aborts with ../../../../dix/privates.c:384: dixRegisterPrivateKey: Assertion `!global_keys[type].created' failed. Status in X.Org X server: Unknown Status in xorg-server package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding xorg-server. This problem was most recently seen with package version 2:1.20.3-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/e1038a75ca80364c2c74351221e2ad5ec5d00916 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/xorg-server/+bug/1811023/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1862290] Re: Xorg restarts when locked
*** This bug is a duplicate of bug 1811023 *** https://bugs.launchpad.net/bugs/1811023 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 1811023, 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. ** This bug has been marked a duplicate of bug 1811023 /usr/lib/xorg/Xorg:Xorg: ../../../../dix/privates.c:384: dixRegisterPrivateKey: Assertion `!global_keys[type].created' failed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1862290 Title: Xorg restarts when locked Status in xorg-server package in Ubuntu: Incomplete Bug description: My laptop is currently running Xubuntu 18.04.3. Whenever I lock or suspend my laptop, Xorg crashes and restarts, frequently bringing down whatever applications are running within it. Here's my light-locker --debug, just in case that helps: [gs_debug_init] gs-debug.c:106 (20:13:53): Debugging enabled [main] light-locker.c:142 (20:13:53): initializing light-locker 1.8.0 [main] light-locker.c:164 (20:13:53): Platform: gtk:3 systemd:yes ConsoleKit: yes UPower: yes [main] light-locker.c:196 (20:13:53): Features: lock-after-screensaver: yes late-locking: yes lock-on-suspend:yes lock-on-lid:yes settings backend: GSETTINGS [main] light-locker.c:198 (20:13:53): lock after screensaver 0 [main] light-locker.c:199 (20:13:53): late locking 0 [main] light-locker.c:200 (20:13:53): lock on suspend 0 [main] light-locker.c:201 (20:13:53): lock on lid 0 [main] light-locker.c:202 (20:13:53): idle hint 0 [init_session_id] gs-listener-dbus.c:2193 (20:13:53): Got session-id: /org/freedesktop/login1/session/c2 [init_session_id] gs-listener-dbus.c:2198 (20:13:53): Got sd-session-id: c2 [init_seat_path] gs-listener-dbus.c:2279 (20:13:53): Got seat: /org/freedesktop/DisplayManager/Seat0 ** (light-locker:25569): WARNING **: 20:13:53.499: screensaver already running in this session And here's my /etc/systemd/logind.conf: [Login] #NAutoVTs=6 #ReserveVT=6 #KillUserProcesses=no #KillOnlyUsers= #KillExcludeUsers=root #InhibitDelayMaxSec=5 #HandlePowerKey=poweroff #HandleSuspendKey=suspend #HandleHibernateKey=hibernate HandleLidSwitch=ignore HandleLidSwitchDocked=ignore #PowerKeyIgnoreInhibited=no #SuspendKeyIgnoreInhibited=no #HibernateKeyIgnoreInhibited=no #LidSwitchIgnoreInhibited=yes #HoldoffTimeoutSec=30s #IdleAction=ignore #IdleActionSec=30min #RuntimeDirectorySize=10% #RemoveIPC=yes #InhibitorsMax=8192 #SessionsMax=8192 #UserTasksMax=33% Additional info: Description: Ubuntu 18.04.3 LTS Release: 18.04 xorg: Installed: 1:7.7+19ubuntu7.1 Candidate: 1:7.7+19ubuntu7.1 Version table: *** 1:7.7+19ubuntu7.1 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:7.7+19ubuntu7 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-generic x86_64 NonfreeKernelModules: 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.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1) ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompositorRunning: None Date: Thu Feb 6 20:03:07 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 4.15.0-76-generic, x86_64: installed nvidia, 435.21, 5.0.0-37-generic, x86_64: installed nvidia, 435.21, 5.3.0-26-generic, x86_64: installed nvidia, 435.21, 5.3.0-28-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Skylake GT2 [HD Graphics 520] [103c:80e5] Subsystem: Hewlett-Packard Company GM107M [GeForce GTX 950M] [103c:80e5] InstallationDate: Installed on 2019-04-11 (301 days ago)
[Desktop-packages] [Bug 1862229] Re: gnome session crash on boot with kernel 5.3.0-29-generic
New bugs created by yourself will appear in this list: https://bugs.launchpad.net/~giacof/+reportedbugs?orderby=-id&start=0 Since I can't see any newer bugs there please follow step 2 in comment #2. -- 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/1862229 Title: gnome session crash on boot with kernel 5.3.0-29-generic Status in gnome-shell package in Ubuntu: Incomplete Bug description: lsb_release -rd Description: Ubuntu 19.10 Release: 19.10 apt-cache policy gnome-shell gnome-shell: Installato: 3.34.1+git20191024-1ubuntu1~19.10.1 Candidato: 3.34.1+git20191024-1ubuntu1~19.10.1 Tabella versione: *** 3.34.1+git20191024-1ubuntu1~19.10.1 500 500 http://it.archive.ubuntu.com/ubuntu eoan-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.34.1-1ubuntu1 500 500 http://it.archive.ubuntu.com/ubuntu eoan/main amd64 Packages First there was an issue with hibernation: after resuming, the gnome session was not restored and a new one was created (I had to login again from start). Here are some relevant log lines: [ 21.375254] PM: Image signature found, resuming [ 21.375255] PM: resume from hibernation [ 21.375607] Freezing user space processes ... (elapsed 0.001 seconds) done. [ 21.376719] OOM killer disabled. [ 21.376832] PM: Marking nosave pages: [mem 0x-0x0fff] [ 21.376834] PM: Marking nosave pages: [mem 0x0004f000-0x0004] [ 21.376834] PM: Marking nosave pages: [mem 0x0009d000-0x0009efff] [ 21.376835] PM: Marking nosave pages: [mem 0x000a-0x000f] [ 21.376837] PM: Marking nosave pages: [mem 0xae7a8000-0xae7aefff] [ 21.376838] PM: Marking nosave pages: [mem 0xaf18c000-0xaf66afff] [ 21.376856] PM: Marking nosave pages: [mem 0xb7db3000-0xb7ff] [ 21.376865] PM: Marking nosave pages: [mem 0xb8759000-0xb87f] [ 21.376868] PM: Marking nosave pages: [mem 0xb8f9d000-0xb8ff] [ 21.376870] PM: Marking nosave pages: [mem 0xba6f5000-0xba7f] [ 21.376875] PM: Marking nosave pages: [mem 0xbbcec000-0x] [ 21.377562] PM: Basic memory bitmaps created [ 24.367114] PM: Using 3 thread(s) for decompression [ 24.367115] PM: Loading and decompressing image data (1585416 pages)... [ 24.367127] Hibernate inconsistent memory map detected! [ 24.367138] fbcon: Taking over console [ 24.367139] PM: Image mismatch: architecture specific data [ 24.367141] PM: Read 6341664 kbytes in 0.01 seconds (634166.40 MB/s) [ 24.368077] PM: Error -1 resuming [ 24.368079] PM: Failed to load hibernation image, recovering. [ 24.368347] PM: Basic memory bitmaps freed [ 24.368347] OOM killer enabled. [ 24.368347] Restarting tasks ... done. [ 24.384357] Console: switching to colour frame buffer device 240x67 [ 24.404345] PM: resume from hibernation failed (-1) Then, since next restart I cannot login anymore, as the session keeps crashing immediately after entering user's password. The only way I could login back was by selecting the previous kernel version on boot (5.3.0-26-generic instead of 5.3.0-29-generic). I also noticed all gnome extensions (Applications Menu and Hibernate Status Button ) stopped working and were disabled. Boot journal attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1862229/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1862281] [NEW] Repeatable hang within 5 minutes using stress-ng + sleep + usb mouse
You have been subscribed to a public bug:
If I run a thermal transition test script (30 seconds stress-ng, 30
seconds sleep, in a loop) and move a local USB mouse, Kubuntu reliably
crashes, usually in the first couple of runs and almost 100% of the time
by run 6.
This appears to be hardware-linked, but not due to a specific piece of
bad hardware: I have swapped literally every piece of hardware in the
system.
It shows up (while running the script at the end):
- On both an MSI B450 Gaming plus max and MSI MPG X570 Gaming plus mainboard.
- On both an AMD Ryzen 5 3600 and 3600X CPU.
- With one or two sticks of RAM. I've tested both sticks individually, in more
than one mainboard slot.
- Regardless of whether the mainboard is in/attached to a case.
- Regardless of whether there is an m.2 SSD installed or I'm running off a live
Kubuntu 19.10 USB stick with no hard disk attached.
- Regardless of which of two mice I use (an old Logitech one, or a GTX 133
Gaming mouse).
- Regardless of whether I'm using a Corsair VS650 or Corsair AX850 PSU.
- Regardless of whether I'm using an AMD RX 5700 XT or using an Nvidia Gigabyte
GeForce RTX 2700 Super (with open source drivers in both cases).
- Regardless of whether I'm using KDE or XFCE.
- Regardless of whether I'm using the default KDE DM or switch to GDM3 and set
WaylandEnable=false.
- Regardless of whether I use the default 5.3.0-29-generic kernel or
5.4.17-050417-generic.
- Regardless of whether I go directly into the graphical environment or start
in runlevel 3 and then manually run startx.
- Regardless of whether it's on the rising or falling edge of the
stress-script's temperature changes.
- Regardless of bios version on the X570 mainboard (the one it shipped with, or
the newest one released in January 2020).
- Regardless of whether XMP is on or off in the bios.
- Regardless of whether I use the default or set global c-state to "control =
disabled" in the bios.
- Regardless of whether I add processor.max_cstate=5 idle=halt in grub.
- Regardless of whether or not speakers are plugged in.
- Regardless of whether I'm using a USB port that is directly on the
motherboard or is on the front of the case.
- Regardless of which monitor it is attached to.
It doesn't show up:
- On an old i7-4771 machine I have, also running Kubuntu 19.10, while running
the test script.
- When I use a mouse remotely with ssh -Y [ip of the machine I am reporting
this from] xeyes, while running the test script.
- When I do non-mouse USB input, ie via a USB keyboard or USB wifi dongle,
including under saturated network load, while running the test script.
- During stress tests of the GPU, CPU, etc. Tools like memtest, mprime, Unigine
Superposition, repeated kernel compiles, etc run stably overnight.
- When the system is entirely idle aside from mouse movement.
- When I start in runlevel 3 and run the same test script, using the mouse with
gpm.
- Running the same test script without mouse movement: this was stable
overnight, then crashed within a couple of minutes of moving the mouse.
It shows up with load other than the stress-ng+sleep script too, but
much less reliably - I'm writing this bug report on the relevant
machine, with firefox open. Crashes occur at least once a week under
these conditions, but not frequently.
Crashes occur with sensor-reported CPU temperatures of 32 to 41 degrees
Celsius. Nothing is overheating, and the system is stable at much higher
temperatures under sustained stress tests.
The symptoms of the crash: the display stops updating and the system
does not respond to any further input, including via the network or
magic sysrq key. There is nothing related to it in syslog or journalctl,
including when I'm running journalctl -f at the time of the crash.
The test script:
#!/bin/bash
for x in {1..1}
do
echo "Run $x at `date`"
stress-ng --cpu 12 --cpu-method all --verify -t 30s --metrics-brief
sleep 30
done
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: xorg 1:7.7+19ubuntu12
Uname: Linux 5.4.17-050417-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: KDE
Date: Fri Feb 7 00:02:22 2020
DistUpgraded: Fresh install
DistroCodename: eoan
DistroVariant: ubuntu
GraphicsCard:
NVIDIA Corporation Device [10de:1e84] (rev a1) (prog-if 00 [VGA controller])
Subsystem: Gigabyte Technology Co., Ltd Device [1458:4008]
InstallationDate: Installed on 2020-01-30 (7 days ago)
InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
MachineType: Micro-Star International Co., Ltd. MS-7C37
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.17-050417-generic
root=UUID=1a1a3bcc-cc59-4982-a1f5-f721ef6fe937 ro quiet splash
acpi_enforce_resources=lax vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/08/2020
dmi.bios.vendor:
[Desktop-packages] [Bug 1825515] Re: Looping login cycle when trying to login to Ubuntu-Gnome (both X and Wayland). But logs in to Ubuntu with Budgie desktop okay.
** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Fix Released -- 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/1825515 Title: Looping login cycle when trying to login to Ubuntu-Gnome (both X and Wayland). But logs in to Ubuntu with Budgie desktop okay. Status in gnome-shell package in Ubuntu: Fix Released Bug description: Bug started immediately after upgrading to Ubuntu 19.04. Have tried all the suggested work-arounds I can find on the web but none of them has any effect on the problem. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: login 1:4.5-1.1ubuntu2 ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Fri Apr 19 22:39:45 2019 InstallationDate: Installed on 2018-10-22 (179 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: shadow UpgradeStatus: Upgraded to disco on 2019-04-18 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1825515/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1825710] Re: Remove "Application is ready" notification
Since this is an upstream design issue please put future comments in the upstream bug: https://gitlab.gnome.org/GNOME/gnome-shell/issues/358 -- 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/1825710 Title: Remove "Application is ready" notification Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Triaged Bug description: The "Application is ready" notification is pointless, really. Say, I click on the open downloads folder button in Firefox and GNOME Shell gives me a notification saying "Application is ready" but doesn't open the notification. I'm totally expecting an app to open because I actively initiated it. As a workaround, I'm using a GNOME extensions "Focus my Window" which removes the "Application is ready" message and focuses the app window automatically. However, this cannot be treated as a solution. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1825710/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1825842] Re: [vmware] Background goes white when using scaling (200%, 300% or 400%)
The (potential) fix mentioned in comment #15 is coming in Gnome 3.36. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-vmware in Ubuntu. https://bugs.launchpad.net/bugs/1825842 Title: [vmware] Background goes white when using scaling (200%, 300% or 400%) Status in mutter package in Ubuntu: Triaged Status in xserver-xorg-video-vmware package in Ubuntu: Invalid Bug description: As soon as I set my display to scaled (any percentage) via Settings -> Displays -> Scale, the background image disappears and become all white. When I choose a different background image via Settings -> Background initially nothing happens. As soon as I switch back to 100% scaling, the image I choose before now appears. This problem started right after updating to 19.04. No such issues with either 18.04 or 18.10. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Apr 22 15:35:49 2019 DistUpgraded: 2019-04-21 17:34:15,063 DEBUG icon theme changed, re-reading DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2019-03-01 (51 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: VMware, Inc. VMware Virtual Platform ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=c8dc93a3-fd95-4152-9c04-0211309b2dc7 ro find_preseed=/preseed.cfg auto noprompt priority=critical locale=en_US quiet SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to disco on 2019-04-21 (0 days ago) dmi.bios.date: 04/13/2018 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:bd04/13/2018: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 N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1825842/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1804568] Re: click position is flipped to cursor position when in tent mode
** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/issues/1036 Importance: Unknown Status: Unknown ** Changed in: mutter (Ubuntu) Importance: Undecided => Medium ** Changed in: mutter (Ubuntu) Status: Confirmed => Triaged -- 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/1804568 Title: click position is flipped to cursor position when in tent mode Status in Mutter: Unknown Status in mutter package in Ubuntu: Triaged Bug description: Hello, same bug is present 18.04 and 18.10: after I log in in tent mode the screen goes upside down, and after xrandr --output eDP-1 --rotate normal it goes back to normal however now the cursor is upside down, and click position and cursor position isnt the same, they are flipped thank you for the fix in advance ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: coreutils 8.28-1ubuntu2 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Nov 22 04:28:21 2018 ExecutablePath: /bin/sleep InstallationDate: Installed on 2018-11-22 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcEnviron: LANG=hu_HU.UTF-8 TERM=xterm-256color SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) SourcePackage: coreutils UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: imi1950 F pulseaudio /dev/snd/controlC1: imi1950 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-03-30 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190329) MachineType: HP HP Spectre x360 Convertible 13-w0XX Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-8-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 RelatedPackageVersions: linux-restricted-modules-5.0.0-8-generic N/A linux-backports-modules-5.0.0-8-generic N/A linux-firmware 1.178 Tags: disco Uname: Linux 5.0.0-8-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/27/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.31 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 827E dmi.board.vendor: HP dmi.board.version: 94.60 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.31:bd04/27/2017:svnHP:pnHPSpectrex360Convertible13-w0XX:pvr:rvnHP:rn827E:rvr94.60:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=SPT dmi.product.name: HP Spectre x360 Convertible 13-w0XX dmi.product.sku: Z9E46EA#ABV dmi.sys.vendor: HP --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: imi1333 F pulseaudio /dev/snd/controlC1: imi1333 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-09-23 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190917) MachineType: HP HP Spectre x360 Convertible 13-w0XX Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-10-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 RelatedPackageVersions: linux-restricted-modules-5.3.0-10-generic N/A linux-backports-modules-5.3.0-10-generic N/A linux-firmware1.182 Tags: eoan Uname: Linux 5.3.0-10-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/03/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.49 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 827E dmi.board.vendor: HP dmi.board.version: 94.71 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.49:bd05/03/2019:svnHP:pnHPSpectrex360Convertible13-w0XX:pvr:rvnHP:rn827E:rvr94.71:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=SPT dmi.product.na
[Desktop-packages] [Bug 1862556] Re: Promore and Colourlovers
Could you please explain in more detail what kind of problem you are experiencing? ** 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/1862556 Title: Promore and Colourlovers Status in Ubuntu: Incomplete Bug description: Just appeared and no explanation as to function ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-173.203-generic 4.4.208 Uname: Linux 4.4.0-173-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 BootLog: [[0;32m OK [0m] Started LSB: COMODO cmgdaemon service. [[0;32m OK [0m] Started Network Manager Script Dispatcher Service. 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 Feb 9 17:19:28 2020 DistUpgraded: 2017-01-13 10:58:43,955 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS880 [Radeon HD 4200] [1002:9710] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company RS880 [Radeon HD 4200] [103c:3047] InstallationDate: Installed on 2017-01-10 (1125 days ago) InstallationMedia: It ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-173-generic root=UUID=f91ffe70-345b-4ad3-8970-945377f127c5 ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2017-01-13 (1122 days ago) dmi.bios.date: 04/18/2012 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786G6 v01.17 dmi.board.asset.tag: 2UA1422FS7 dmi.board.name: 3047h dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: 2UA1422FS7 dmi.chassis.type: 4 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786G6v01.17:bd04/18/2012:svnHewlett-Packard:pn:pvr:rvnHewlett-Packard:rn3047h:rvr:cvnHewlett-Packard:ct4:cvr: dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8 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 Feb 9 16:21:48 2020 xserver.configfile: default xserver.errors: /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.8 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1862556/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1862531] Re: [focal] Wayland session is not available when a laptop has an Nvidia card an Intel card is in use
Thanks for the bug report. That udev rule causing the problem is unfortunately something that upstream won't let us replace. I have tried replacing it with smarter mutter logic and (so far) it's been rejected: https://gitlab.gnome.org/GNOME/mutter/merge_requests/625 ** Tags added: focal ** Changed in: gdm3 (Ubuntu) Status: New => Won't Fix ** Changed in: nvidia-prime (Ubuntu) Status: New => Invalid ** Tags added: nvidia-drm.modeset -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1862531 Title: [focal] Wayland session is not available when a laptop has an Nvidia card an Intel card is in use Status in gdm3 package in Ubuntu: Won't Fix Status in nvidia-prime package in Ubuntu: Invalid Bug description: A Wayland session present at /usr/share/wayland-sessions/ubuntu- wayland.desktop is not displayed at the login screen when a system has an iGPU (Intel) and dGPU (Nvidia) and Intel iGPU is used: prime-select query intel Only sessions at /usr/share/xsessions are present. ➜ ~ ls /usr/share/xsessions remmina-gnome.desktop ubuntu.desktop ➜ ~ ls /usr/share/wayland-sessions ubuntu-wayland.desktop The root cause is the existence of a udev rule in 61-gdm.rules that runs gdm-disable-wayland when an nvidia driver is loaded in combination with LP: #1848326 (see this comment specifically https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1848326/comments/7). dpkg -S /lib/udev/rules.d/61-gdm.rules gdm3: /lib/udev/rules.d/61-gdm.rules grep nvidia /lib/udev/rules.d/61-gdm.rules # disable Wayland when using the proprietary nvidia driver DRIVER=="nvidia", RUN+="/usr/lib/gdm3/gdm-disable-wayland" When I comment it out and reboot, I get the right menu entry and am able to observe the right session type: ➜ ~ grep nvidia /lib/udev/rules.d/61-gdm.rules # disable Wayland when using the proprietary nvidia driver #DRIVER=="nvidia", RUN+="/usr/lib/gdm3/gdm-disable-wayland" ➜ ~ loginctl SESSION UID USER SEAT TTY 2 1000 dima seat0 tty2 1 sessions listed. ➜ ~ loginctl show-session 2 -p Type Type=wayland System info: lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Focal Fossa (development branch) Release: 20.04 Codename: focal ➜ ~ dpkg -l | grep gdm3 ii gdm3 3.34.1-1ubuntu1 amd64GNOME Display Manager ➜ ~ dpkg -l | grep nvidia-prime ii nvidia-prime 0.8.13 all Tools to enable NVIDIA's Prime ➜ ~ dpkg -l | grep nvidia-driver ii nvidia-driver-440 440.59-0ubuntu1 amd64NVIDIA driver metapackage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1862531/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1862556] [NEW] Promore and Colourlovers
Public bug reported: Just appeared and no explanation as to function ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-173.203-generic 4.4.208 Uname: Linux 4.4.0-173-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 BootLog: [[0;32m OK [0m] Started LSB: COMODO cmgdaemon service. [[0;32m OK [0m] Started Network Manager Script Dispatcher Service. 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 Feb 9 17:19:28 2020 DistUpgraded: 2017-01-13 10:58:43,955 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS880 [Radeon HD 4200] [1002:9710] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company RS880 [Radeon HD 4200] [103c:3047] InstallationDate: Installed on 2017-01-10 (1125 days ago) InstallationMedia: It ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-173-generic root=UUID=f91ffe70-345b-4ad3-8970-945377f127c5 ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2017-01-13 (1122 days ago) dmi.bios.date: 04/18/2012 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786G6 v01.17 dmi.board.asset.tag: 2UA1422FS7 dmi.board.name: 3047h dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: 2UA1422FS7 dmi.chassis.type: 4 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786G6v01.17:bd04/18/2012:svnHewlett-Packard:pn:pvr:rvnHewlett-Packard:rn3047h:rvr:cvnHewlett-Packard:ct4:cvr: dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8 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 Feb 9 16:21:48 2020 xserver.configfile: default xserver.errors: /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.8 xserver.video_driver: radeon ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1862556 Title: Promore and Colourlovers Status in xorg package in Ubuntu: New Bug description: Just appeared and no explanation as to function ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-173.203-generic 4.4.208 Uname: Linux 4.4.0-173-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 BootLog: [[0;32m OK [0m] Started LSB: COMODO cmgdaemon service. [[0;32m OK [0m] Started Network Manager Script Dispatcher Service. 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 Feb 9 17:19:28 2020 DistUpgraded: 2017-01-13 10:58:43,955 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS880 [Radeon HD 4200] [1002:9710] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company RS880 [Radeon HD 4200] [103c:3047] InstallationDate: Installed on 2017-01-10 (1125 days ago) InstallationMedia: It ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-173-generic root=UUID=f91ffe70-345b-4ad3-8970-945377f127c5 ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2017-01-13 (1122 days ago) dmi.bios.date: 04/18/2012 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786G6 v01.17 dmi.board.asset.tag: 2UA1422FS7 dmi.board.name: 3047h dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: 2UA1422FS7 dmi.chassis.type: 4 dmi.ch
[Desktop-packages] [Bug 1862158] Re: gnome-software tries to install snap updates in the background, causing unprompted polkit authentication for authorisation to install packages
I've proposed an MR here: https://gitlab.gnome.org/GNOME/gnome-software/merge_requests/420/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1862158 Title: gnome-software tries to install snap updates in the background, causing unprompted polkit authentication for authorisation to install packages Status in gnome-software package in Ubuntu: Confirmed Bug description: Every morning about ~30mins after powering on my focal machine I get (unprompted) a gnome-shell policykit authorisation popup saying 'authentication is required to install software' - I haven't yet actually authorised it since I wasn't sure what was causing it, however I notice that if I cancel the authorisation then I see a bunch of notifications from gnome-software about updates having been successfully installed (even though I presume it hasn't been since I never authorised it). Is gnome-software fighting snapd to refresh snaps? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-software 3.35.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 6 21:37:29 2020 InstallationDate: Installed on 2019-11-18 (79 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap3.35.2-0ubuntu1 SourcePackage: gnome-software UpgradeStatus: Upgraded to focal on 2020-01-22 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1862158/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1862158] Re: gnome-software tries to install snap updates in the background, causing unprompted polkit authentication for authorisation to install packages
Andrew - that patch seems reasonable with the existing code, as the daemon does the auto-updates, so no client should be performing it. This should probably be done with a quirk, so the update monitor doesn't need to special case Snaps (or the firmware as it currently does). But that is better discussed on an upstream MR. James - G-S doesn't currently have a mechanism to say why each operation is being performed, but I imagine we could add one. In this case it doesn't make sense as G-S shouldn't try and auto update. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1862158 Title: gnome-software tries to install snap updates in the background, causing unprompted polkit authentication for authorisation to install packages Status in gnome-software package in Ubuntu: Confirmed Bug description: Every morning about ~30mins after powering on my focal machine I get (unprompted) a gnome-shell policykit authorisation popup saying 'authentication is required to install software' - I haven't yet actually authorised it since I wasn't sure what was causing it, however I notice that if I cancel the authorisation then I see a bunch of notifications from gnome-software about updates having been successfully installed (even though I presume it hasn't been since I never authorised it). Is gnome-software fighting snapd to refresh snaps? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-software 3.35.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 6 21:37:29 2020 InstallationDate: Installed on 2019-11-18 (79 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap3.35.2-0ubuntu1 SourcePackage: gnome-software UpgradeStatus: Upgraded to focal on 2020-01-22 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1862158/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1862158] Re: gnome-software tries to install snap updates in the background, causing unprompted polkit authentication for authorisation to install packages
** Changed in: gnome-software (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1862158 Title: gnome-software tries to install snap updates in the background, causing unprompted polkit authentication for authorisation to install packages Status in gnome-software package in Ubuntu: Confirmed Bug description: Every morning about ~30mins after powering on my focal machine I get (unprompted) a gnome-shell policykit authorisation popup saying 'authentication is required to install software' - I haven't yet actually authorised it since I wasn't sure what was causing it, however I notice that if I cancel the authorisation then I see a bunch of notifications from gnome-software about updates having been successfully installed (even though I presume it hasn't been since I never authorised it). Is gnome-software fighting snapd to refresh snaps? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-software 3.35.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 6 21:37:29 2020 InstallationDate: Installed on 2019-11-18 (79 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap3.35.2-0ubuntu1 SourcePackage: gnome-software UpgradeStatus: Upgraded to focal on 2020-01-22 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1862158/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1862549] [NEW] memory leak when annotating PDFs
Public bug reported: When annotating PDFs or scrolling through larger PDFs that contain lots of annotations, evince claims a large amount of memory and never releases it. This becomes especially apparent when using the highlight feature, i.e. highlighting various parts of the text on the PDF. On a 12-page PDF, not annotated, evince used about 35 MB of RAM and claimed an additional 30 as soon as I used the highlight feature the first time, then this repeats with about the same amount or more for each additional highlight. The interface starts to lag visibly the more memory is allocated. Occasionally, the memory usage goes down by a few percent when scrolling, but it tends to allocate more and more memory until the system runs out of memory. Using the same 12-page PDF with about 100 highlighted lines and quickly scrolling through the document multiple times, evince reached about 6 GB of memory usage in less than one minute. This issue also makes closing documents very slow, taking about 5 to 10 seconds for each gigabyte of memory allocated. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: evince 3.34.1-1build1 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Feb 9 23:13:02 2020 InstallationDate: Installed on 2020-01-30 (10 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/zsh SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: evince (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apparmor apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1862549 Title: memory leak when annotating PDFs Status in evince package in Ubuntu: New Bug description: When annotating PDFs or scrolling through larger PDFs that contain lots of annotations, evince claims a large amount of memory and never releases it. This becomes especially apparent when using the highlight feature, i.e. highlighting various parts of the text on the PDF. On a 12-page PDF, not annotated, evince used about 35 MB of RAM and claimed an additional 30 as soon as I used the highlight feature the first time, then this repeats with about the same amount or more for each additional highlight. The interface starts to lag visibly the more memory is allocated. Occasionally, the memory usage goes down by a few percent when scrolling, but it tends to allocate more and more memory until the system runs out of memory. Using the same 12-page PDF with about 100 highlighted lines and quickly scrolling through the document multiple times, evince reached about 6 GB of memory usage in less than one minute. This issue also makes closing documents very slow, taking about 5 to 10 seconds for each gigabyte of memory allocated. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: evince 3.34.1-1build1 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Feb 9 23:13:02 2020 InstallationDate: Installed on 2020-01-30 (10 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/zsh SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1862549/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1862544] [NEW] Double-clicking a folder sometimes opens another, recently visited folder
Public bug reported: The following happens for me very frequently. Say I have the following folder structure: A |- B |- C |- some other files/folders... I'm currently browsing the folder B. Then I go up one level, to A, by pressing backspace. I then immediately double-click on the icon for folder C to enter into it. Very frequently, this instead takes me back into folder B. What appears to be happening is that when I go up from B to A, if I double-click the icon for C while the contents of A are being read from disk and the thumbnails are being refreshed, the program registers that I have double-clicked something, but after the thumbnail refresh has finished, the "selected folder" reverts back to B. Hence, the program thinks I double-clicked the icon for B instead. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-76.86-generic 4.15.18 Uname: Linux 4.15.0-76-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Feb 9 21:42:19 2020 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'196' b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2020-02-09 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- 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/1862544 Title: Double-clicking a folder sometimes opens another, recently visited folder Status in nautilus package in Ubuntu: New Bug description: The following happens for me very frequently. Say I have the following folder structure: A |- B |- C |- some other files/folders... I'm currently browsing the folder B. Then I go up one level, to A, by pressing backspace. I then immediately double-click on the icon for folder C to enter into it. Very frequently, this instead takes me back into folder B. What appears to be happening is that when I go up from B to A, if I double-click the icon for C while the contents of A are being read from disk and the thumbnails are being refreshed, the program registers that I have double-clicked something, but after the thumbnail refresh has finished, the "selected folder" reverts back to B. Hence, the program thinks I double-clicked the icon for B instead. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-76.86-generic 4.15.18 Uname: Linux 4.15.0-76-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Feb 9 21:42:19 2020 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'196' b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2020-02-09 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1862544/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1862541] [NEW] Ctrl+A does not always select all contents of the visited folder (can lead to permanently lost work!)
Public bug reported: The other day I wanted to move all the files in one folder over to another folder using the cut + paste method. I visited the source folder, pressed Ctrl+A (select all) followed by Ctrl+X (cut), and then browsed to the target folder and pressed Ctrl+V (paste). Then I went and deleted the source folder, which I reasonably assumed to now be empty. However, it turned out that not all the files had been moved, and that the remaining files had been deleted along with the original folder (which I deleted permanently with Shift+Del, I might add). After some troubleshooting I've been able to determine the most likely cause. When visiting a folder, there is usually some delay during which the contents of the folder are read from disk and the thumbnails are being updated (for large folders this delay can be on the order of seconds). If Ctrl+A is pressed before this process has finished, only a subset of the files/folders are selected. Thus, I probably only cut/moved some of the files, and left the remaining files behind. This is a very serious bug, as it can lead to permanent loss of work (as it did for me). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-76.86-generic 4.15.18 Uname: Linux 4.15.0-76-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Feb 9 21:22:24 2020 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'196' b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2020-02-09 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- 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/1862541 Title: Ctrl+A does not always select all contents of the visited folder (can lead to permanently lost work!) Status in nautilus package in Ubuntu: New Bug description: The other day I wanted to move all the files in one folder over to another folder using the cut + paste method. I visited the source folder, pressed Ctrl+A (select all) followed by Ctrl+X (cut), and then browsed to the target folder and pressed Ctrl+V (paste). Then I went and deleted the source folder, which I reasonably assumed to now be empty. However, it turned out that not all the files had been moved, and that the remaining files had been deleted along with the original folder (which I deleted permanently with Shift+Del, I might add). After some troubleshooting I've been able to determine the most likely cause. When visiting a folder, there is usually some delay during which the contents of the folder are read from disk and the thumbnails are being updated (for large folders this delay can be on the order of seconds). If Ctrl+A is pressed before this process has finished, only a subset of the files/folders are selected. Thus, I probably only cut/moved some of the files, and left the remaining files behind. This is a very serious bug, as it can lead to permanent loss of work (as it did for me). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-76.86-generic 4.15.18 Uname: Linux 4.15.0-76-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Feb 9 21:22:24 2020 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'196' b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2020-02-09 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1862541/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1862536] Re: problem with folder selection dialog in google drive with firefox
Also the firefox menu and the "More tools" overlow menu didn't open on click, just the buttons became darker as on hover over them. Ctrl Q worked to exit the browser however. On restart everything was okay. -- 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/1862536 Title: problem with folder selection dialog in google drive with firefox Status in firefox package in Ubuntu: New Bug description: I have tried to move two many pictures (about 100 maybe) from nautilus to google drive, first time google drive didn't react to my move of the pictures above the page, so i tried again, and it also didn't react this time. After that i said "this won't work", so i clicked their button to upload a folder. The folder upload menu showed, but i noticed that on the left in the list where "Home", "Downloads", etc. are there was one folder which didn't have a name but only an icon. I decided it was a bug so i closed the folder upload dialog from Ubuntu and selected it again to open. The page became darker as when the backdrop that is shown when the folder upload dialog is visible. The bug is that the folder upload dialog that should have shown the second time was missing and only the backdrop was shown. Page didn't react. That was until i pressed ESC key and the backdrop disappeared. After the backdrop disappeared the firefox html element with the upload icon and the text "Drop elements here to upload" finally showed unexpectedly after 2 minutes. Notice that i didn't move any files now, i moved them before the standard Ubuntu folder dialog bug. Firefox scrolling then became slow and lags in each tab, not only Google Drive tab. Also now when i am typing into the launchpad bug input the text is inserting with noticeable delay. Seems to be a FIrefox bug as text in gedit text editor enters as soon as i press any key. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: firefox 72.0.2+build1-0ubuntu0.19.10.1 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lyubomir 6009 F pulseaudio /dev/snd/pcmC0D0p: lyubomir 6009 F...m pulseaudio BuildID: 20200117190643 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Sun Feb 9 20:52:10 2020 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:727 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2020-02-08 (1 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IpRoute: default via 192.168.1.1 dev wlp3s0 proto dhcp metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.7 metric 600 Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:727 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=72.0.2/20200117190643 (In use) RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/03/2019 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.02 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Charmander_KL dmi.board.vendor: KBL dmi.board.version: V2.02 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.02 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.02:bd01/03/2019:svnAcer:pnAspireA515-51G:pvrV2.02:rvnKBL:rnCharmander_KL:rvrV2.02:cvnAcer:ct10:cvrV2.02: dmi.product.family: Aspire 5 dmi.product.name: Aspire A515-51G dmi.product.sku: dmi.product.version: V2.02 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1862536/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launc
[Desktop-packages] [Bug 1862536] [NEW] problem with folder selection dialog in google drive with firefox
Public bug reported: I have tried to move two many pictures (about 100 maybe) from nautilus to google drive, first time google drive didn't react to my move of the pictures above the page, so i tried again, and it also didn't react this time. After that i said "this won't work", so i clicked their button to upload a folder. The folder upload menu showed, but i noticed that on the left in the list where "Home", "Downloads", etc. are there was one folder which didn't have a name but only an icon. I decided it was a bug so i closed the folder upload dialog from Ubuntu and selected it again to open. The page became darker as when the backdrop that is shown when the folder upload dialog is visible. The bug is that the folder upload dialog that should have shown the second time was missing and only the backdrop was shown. Page didn't react. That was until i pressed ESC key and the backdrop disappeared. After the backdrop disappeared the firefox html element with the upload icon and the text "Drop elements here to upload" finally showed unexpectedly after 2 minutes. Notice that i didn't move any files now, i moved them before the standard Ubuntu folder dialog bug. Firefox scrolling then became slow and lags in each tab, not only Google Drive tab. Also now when i am typing into the launchpad bug input the text is inserting with noticeable delay. Seems to be a FIrefox bug as text in gedit text editor enters as soon as i press any key. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: firefox 72.0.2+build1-0ubuntu0.19.10.1 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lyubomir 6009 F pulseaudio /dev/snd/pcmC0D0p: lyubomir 6009 F...m pulseaudio BuildID: 20200117190643 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Sun Feb 9 20:52:10 2020 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:727 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2020-02-08 (1 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IpRoute: default via 192.168.1.1 dev wlp3s0 proto dhcp metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.7 metric 600 Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:727 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=72.0.2/20200117190643 (In use) RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/03/2019 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.02 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Charmander_KL dmi.board.vendor: KBL dmi.board.version: V2.02 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.02 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.02:bd01/03/2019:svnAcer:pnAspireA515-51G:pvrV2.02:rvnKBL:rnCharmander_KL:rvrV2.02:cvnAcer:ct10:cvrV2.02: dmi.product.family: Aspire 5 dmi.product.name: Aspire A515-51G dmi.product.sku: dmi.product.version: V2.02 dmi.sys.vendor: Acer ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1862536 Title: problem with folder selection dialog in google drive with firefox Status in firefox package in Ubuntu: New Bug description: I have tried to move two many pictures (about 100 maybe) from nautilus to google drive, first time google drive didn't react to my move of the pictures above the page, so i tried again, and it also didn't react this time. After that i said "this won't work", so i clicked their button to upload a folder. The folder upload menu showed, but i noticed that on the left in the list where "Home", "Downloads", etc. are there was one folder which didn't have a name but only an icon. I decided it was a bug so i closed the folder upload dia
[Desktop-packages] [Bug 1848326] Re: [cosmic+] error booting with prime-select intel: prime-select does not update initramfs to blacklist nvidia modules
** Tags added: champagne -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1848326 Title: [cosmic+] error booting with prime-select intel: prime-select does not update initramfs to blacklist nvidia modules Status in nvidia-prime package in Ubuntu: Confirmed Bug description: when I try to boot with the iGPU selected, DE won't boot, with nvidia selected, everithing is fine. I tried uninstalling nvidia driver and it allowed my to access without any problems and intel is working fine ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: nvidia-prime 0.8.13 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: KDE Date: Wed Oct 16 12:41:26 2019 Dependencies: InstallationDate: Installed on 2019-09-25 (20 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190925) PackageArchitecture: all SourcePackage: nvidia-prime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1848326/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1862531] [NEW] [focal] Wayland session is not available when a laptop has an Nvidia card an Intel card is in use
Public bug reported: A Wayland session present at /usr/share/wayland-sessions/ubuntu- wayland.desktop is not displayed at the login screen when a system has an iGPU (Intel) and dGPU (Nvidia) and Intel iGPU is used: prime-select query intel Only sessions at /usr/share/xsessions are present. ➜ ~ ls /usr/share/xsessions remmina-gnome.desktop ubuntu.desktop ➜ ~ ls /usr/share/wayland-sessions ubuntu-wayland.desktop The root cause is the existence of a udev rule in 61-gdm.rules that runs gdm-disable-wayland when an nvidia driver is loaded in combination with LP: #1848326 (see this comment specifically https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1848326/comments/7). dpkg -S /lib/udev/rules.d/61-gdm.rules gdm3: /lib/udev/rules.d/61-gdm.rules grep nvidia /lib/udev/rules.d/61-gdm.rules # disable Wayland when using the proprietary nvidia driver DRIVER=="nvidia", RUN+="/usr/lib/gdm3/gdm-disable-wayland" When I comment it out and reboot, I get the right menu entry and am able to observe the right session type: ➜ ~ grep nvidia /lib/udev/rules.d/61-gdm.rules # disable Wayland when using the proprietary nvidia driver #DRIVER=="nvidia", RUN+="/usr/lib/gdm3/gdm-disable-wayland" ➜ ~ loginctl SESSION UID USER SEAT TTY 2 1000 dima seat0 tty2 1 sessions listed. ➜ ~ loginctl show-session 2 -p Type Type=wayland System info: lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu Focal Fossa (development branch) Release:20.04 Codename: focal ➜ ~ dpkg -l | grep gdm3 ii gdm3 3.34.1-1ubuntu1 amd64GNOME Display Manager ➜ ~ dpkg -l | grep nvidia-prime ii nvidia-prime 0.8.13 all Tools to enable NVIDIA's Prime ➜ ~ dpkg -l | grep nvidia-driver ii nvidia-driver-440 440.59-0ubuntu1 amd64NVIDIA driver metapackage ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Affects: nvidia-prime (Ubuntu) Importance: Undecided Status: New ** Tags: champagne ** Also affects: nvidia-prime (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Wayland session is not available when a laptop has an Nvidia card an Intel card is in use + [focal] Wayland session is not available when a laptop has an Nvidia card an Intel card is in use -- 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/1862531 Title: [focal] Wayland session is not available when a laptop has an Nvidia card an Intel card is in use Status in gdm3 package in Ubuntu: New Status in nvidia-prime package in Ubuntu: New Bug description: A Wayland session present at /usr/share/wayland-sessions/ubuntu- wayland.desktop is not displayed at the login screen when a system has an iGPU (Intel) and dGPU (Nvidia) and Intel iGPU is used: prime-select query intel Only sessions at /usr/share/xsessions are present. ➜ ~ ls /usr/share/xsessions remmina-gnome.desktop ubuntu.desktop ➜ ~ ls /usr/share/wayland-sessions ubuntu-wayland.desktop The root cause is the existence of a udev rule in 61-gdm.rules that runs gdm-disable-wayland when an nvidia driver is loaded in combination with LP: #1848326 (see this comment specifically https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1848326/comments/7). dpkg -S /lib/udev/rules.d/61-gdm.rules gdm3: /lib/udev/rules.d/61-gdm.rules grep nvidia /lib/udev/rules.d/61-gdm.rules # disable Wayland when using the proprietary nvidia driver DRIVER=="nvidia", RUN+="/usr/lib/gdm3/gdm-disable-wayland" When I comment it out and reboot, I get the right menu entry and am able to observe the right session type: ➜ ~ grep nvidia /lib/udev/rules.d/61-gdm.rules # disable Wayland when using the proprietary nvidia driver #DRIVER=="nvidia", RUN+="/usr/lib/gdm3/gdm-disable-wayland" ➜ ~ loginctl SESSION UID USER SEAT TTY 2 1000 dima seat0 tty2 1 sessions listed. ➜ ~ loginctl show-session 2 -p Type Type=wayland System info: lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Focal Fossa (development branch) Release: 20.04 Codename: focal ➜ ~ dpkg -l | grep gdm3 ii gdm3 3.34.1-1ubuntu1 amd64GNOME Display Manager ➜ ~ dpkg -l | grep nvidia-prime ii nvidia-prime 0.8.13 all Tools to enable NVIDIA's Prime ➜ ~ dpkg -l | grep nvidia-driver ii nvidia-driver-440 440.59-
[Desktop-packages] [Bug 1799213] Re: Gtk-CRITICAL gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed
Posts twice about every 10 seconds. fred@fred-Z170N-focal:~$ echo $DESKTOP_SESSION gnome-flashback-metacity fred@fred-Z170N-focal:~$ gnome-shell --version GNOME Shell 3.34.3 fred@fred-Z170N-focal:~$ lsb_release -d Description:Ubuntu Focal Fossa (development branch) Feb 9 11:13:31 fred-Z170N-focal nm-applet[1680]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Feb 9 11:13:31 fred-Z170N-focal nm-applet[1680]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Feb 9 11:13:31 fred-Z170N-focal nm-applet[1680]: Can't set a parent on widget which has a parent Feb 9 11:13:41 fred-Z170N-focal nm-applet[1680]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Feb 9 11:13:41 fred-Z170N-focal nm-applet[1680]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1799213 Title: Gtk-CRITICAL gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Status in network-manager-applet package in Ubuntu: Confirmed Bug description: Ubuntu 18.10, network-manager-gnome 1.8.18-2 Every three minutes or less, the applet writes to stderr these messages: (nm-applet:3677): Gtk-CRITICAL **: 08:09:47.640: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed (nm-applet:3677): Gtk-CRITICAL **: 08:09:47.640: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed (nm-applet:3677): Gtk-WARNING **: 08:09:47.668: Can't set a parent on widget which has a parent (nm-applet:3677): Gtk-CRITICAL **: 08:10:50.616: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed (nm-applet:3677): Gtk-CRITICAL **: 08:10:50.616: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed (nm-applet:3677): Gtk-WARNING **: 08:10:50.639: Can't set a parent on widget which has a parent Steps to reproduce: - install network-manager-gnome, add the nm-applet to the panel - wait Expected outcome: - not filling up error logs Seen outcome: - filling up error logs ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: network-manager-gnome 1.8.18-2ubuntu2 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 CurrentDesktop: XFCE Date: Mon Oct 22 08:08:37 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-06-05 (869 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IpRoute: default via 192.168.1.1 dev enp5s0 proto dhcp metric 100 169.254.0.0/16 dev enp5s0 scope link metric 1000 192.168.1.0/24 dev enp5s0 proto kernel scope link src 192.168.1.111 metric 100 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=false SourcePackage: network-manager-applet UpgradeStatus: Upgraded to cosmic on 2018-10-21 (0 days ago) modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2018-03-20T22:16:27.108498 nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE FILENAME Wired connection 1 ac8e86d9-6cff-3015-828a-e5fdbd9f5b0b ethernet 1540209985 Mon 22 Oct 2018 08:06:25 AM EDT yes -999 no/org/freedesktop/NetworkManager/Settings/1 yes enp5s0 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- /etc/NetworkManager/system-connections/Wired connection 1 nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH enp5s0 ethernet connected /org/freedesktop/NetworkManager/Devices/2 Wired connection 1 ac8e86d9-6cff-3015-828a-e5fdbd9f5b0b /org/freedesktop/NetworkManager/ActiveConnection/1 wlp3s0 wifi disconnected /org/freedesktop/NetworkManager/Devices/3 -- ---- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.12.4 connected started full enabled enabled enabled enabled disabled To manage notifications about this bug
[Desktop-packages] [Bug 1848326] Re: [cosmic+] error booting with prime-select intel: prime-select does not update initramfs to blacklist nvidia modules
Based on a discussion with ~albertomilone, powering down the NVIDIA GPU
while keeping the modules loaded is the way to go long-term as opposed
to blacklisting the modules.
The power management feature is described here (requires Turing GPUs and above):
http://us.download.nvidia.com/XFree86/Linux-x86_64/440.44/README/dynamicpowermanagement.html
My GPU is pre-Turing (Pascal, 1060m), however, powering off is not where
the problem is.
Running `prime-select intel` creates /lib/udev/rules.d/80-pm-
nvidia.rules which contains the following line to unbind an NVIDIA GPU
device from its driver:
https://github.com/tseliot/nvidia-prime/blob/cf757cc9585dfc032930379fc81effb3a3d59606/prime-select#L164-L165
ACTION=="add", SUBSYSTEM=="pci", ATTR{vendor}=="0x10de",
ATTR{class}=="0x03", ATTR{remove}="1"
If I comment it out, I can boot just fine with my iGPU after running
`prime-select intel`. The resulting 80-pm-nvidia.rules file looks like
this: https://paste.ubuntu.com/p/HX6t9y8BPg/
Just commenting out the power management lines while leaving the
unbinding in-place results in the same issue (80-pm-nvidia.rules:
https://paste.ubuntu.com/p/mTdXbZZk8H/).
The unbinding operation hangs which results in something like this even
before X11 or gdm3 are attempted to be started:
[ 15.683190] nvidia-uvm: Loaded the UVM driver, major device number 511.
[ 15.824882] NVRM: Attempting to remove minor device 0 with non-zero usage
count!
[ 15.824903] [ cut here ]
[ 15.825082] WARNING: CPU: 0 PID: 759 at
/var/lib/dkms/nvidia/440.59/build/nvidia/nv-pci.c:577 nv_pci_remove+0x338/0x360
[nvidia]
# ...
[ 15.825330] ---[ end trace 353e142c2126a8a0 ]---
# ...
[ 242.649248] INFO: task nvidia-persiste:1876 blocked for more than 120
seconds.
[ 242.649931] Tainted: PW O 5.4.0-12-generic #15-Ubuntu
[ 242.650618] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this
message.
[ 242.651319] nvidia-persiste D0 1876 1 0x0004
Eventually it fails with a timeout:
systemd[1]: nvidia-persistenced.service: start operation timed out. Terminating.
systemd[1]: nvidia-persistenced.service: Failed with result 'timeout'.
systemd[1]: Failed to start NVIDIA Persistence Daemon.
Masking nvidia-persistenced via `sudo systemctl mask nvidia-
persistenced` and rebooting shows that systemd-udevd and rmmod hang as
well:
Feb 9 17:18:43 blade systemd-udevd[717]: :01:00.0: Worker [756] processing
SEQNUM=4430 is taking a long time
Feb 9 17:18:43 blade systemd-udevd[717]: :01:00.1: Worker [746] processing
SEQNUM=4440 is taking a long time
Feb 9 17:20:43 blade systemd-udevd[717]: :01:00.1: Worker [746] processing
SEQNUM=4440 killed
Feb 9 17:20:43 blade systemd-udevd[717]: :01:00.0: Worker [756] processing
SEQNUM=4430 killed
Feb 9 17:21:31 blade kernel: [ 242.818665] INFO: task systemd-udevd:746
blocked for more than 120 seconds.
Feb 9 17:21:31 blade kernel: [ 242.819381] Tainted: PW O
5.4.0-12-generic #15-Ubuntu
Feb 9 17:21:31 blade kernel: [ 242.820075] "echo 0 >
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
Feb 9 17:21:31 blade kernel: [ 242.820797] systemd-udevd D0 746
717 0x0324
# ...
Feb 9 17:21:31 blade kernel: [ 242.823033] rmmod D0 1939
1937 0x4000
Feb 9 17:21:31 blade kernel: [ 242.823034] Call Trace:
# ...
Feb 9 17:21:31 blade kernel: [ 242.823783] nvkms_close_gpu+0x50/0x80
[nvidia_modeset]
Feb 9 17:21:31 blade kernel: [ 242.823793] _nv002598kms+0x14d/0x170
[nvidia_modeset]
# ...
Feb 9 17:21:31 blade kernel: [ 242.823893] ? nv_linux_drm_exit+0x9/0x768
[nvidia_drm]
Feb 9 17:21:31 blade kernel: [ 242.823897] ?
__x64_sys_delete_module+0x147/0x290
# ...
** Attachment added: "syslog-nvidia-persistenced-hang.txt"
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1848326/+attachment/5326678/+files/syslog-nvidia-persistenced-hang.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-prime in Ubuntu.
https://bugs.launchpad.net/bugs/1848326
Title:
[cosmic+] error booting with prime-select intel: prime-select does not
update initramfs to blacklist nvidia modules
Status in nvidia-prime package in Ubuntu:
Confirmed
Bug description:
when I try to boot with the iGPU selected, DE won't boot, with nvidia
selected, everithing is fine.
I tried uninstalling nvidia driver and it allowed my to access without any
problems and intel is working fine
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: nvidia-prime 0.8.13
ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
Uname: Linux 5.3.0-18-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
CurrentDesktop: KDE
Date: Wed Oct 16 12:41:26 2019
Dependencies:
InstallationDate: Installed on 2019-09-25 (20 days ago)
InstallationMedia
[Desktop-packages] [Bug 1849637] Re: nouveau driver spams dmesg with SCHED_ERROR
Hi, I tried again to switch on the nouveau driver, to see if there were any updates that had this bug fixed, but still crashing. It crashing random, after a few minutes on the desktop, browsing the web. Here is the new log, we can see a stacktrace. ** Attachment added: "journactl log upon Nouveau driver crash" https://bugs.launchpad.net/ubuntu/+source/nouveau-firmware/+bug/1849637/+attachment/5326676/+files/nouveau_crash.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1849637 Title: nouveau driver spams dmesg with SCHED_ERROR Status in nouveau-firmware package in Ubuntu: New Status in xserver-xorg-video-nouveau package in Ubuntu: New Bug description: Hi, Since the upgrade from 19.04 to 19.10, the nouveau driver is continuously spamming dmesg output with nouveau :01:00.0: fifo: SCHED_ERROR 08 [] -> lsb_release Description: Ubuntu 19.10 Release: 19.10 -> hardware 00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 630 (Mobile) 01:00.0 VGA compatible controller: NVIDIA Corporation TU106M [GeForce RTX 2060 Mobile] (rev a1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nouveau-firmware/+bug/1849637/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1862519] [NEW] My remote, Rii Mini i28 is not listed in the lirc installation.
Public bug reported: I am using Ubuntu 18.04.4 LTS ** Affects: lirc (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lirc in Ubuntu. https://bugs.launchpad.net/bugs/1862519 Title: My remote, Rii Mini i28 is not listed in the lirc installation. Status in lirc package in Ubuntu: New Bug description: I am using Ubuntu 18.04.4 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/1862519/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1825842] Re: [vmware] Background goes white when using scaling (200%, 300% or 400%)
I can confirmed having the same issue with 20.04 fresh installed as guest on virtual box -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-vmware in Ubuntu. https://bugs.launchpad.net/bugs/1825842 Title: [vmware] Background goes white when using scaling (200%, 300% or 400%) Status in mutter package in Ubuntu: Triaged Status in xserver-xorg-video-vmware package in Ubuntu: Invalid Bug description: As soon as I set my display to scaled (any percentage) via Settings -> Displays -> Scale, the background image disappears and become all white. When I choose a different background image via Settings -> Background initially nothing happens. As soon as I switch back to 100% scaling, the image I choose before now appears. This problem started right after updating to 19.04. No such issues with either 18.04 or 18.10. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Apr 22 15:35:49 2019 DistUpgraded: 2019-04-21 17:34:15,063 DEBUG icon theme changed, re-reading DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2019-03-01 (51 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: VMware, Inc. VMware Virtual Platform ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=c8dc93a3-fd95-4152-9c04-0211309b2dc7 ro find_preseed=/preseed.cfg auto noprompt priority=critical locale=en_US quiet SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to disco on 2019-04-21 (0 days ago) dmi.bios.date: 04/13/2018 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:bd04/13/2018: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 N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1825842/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 369064] Re: Maximized apps go under the bottom bar when using vertically stacked screens
** Changed in: metacity (Ubuntu) Status: Confirmed => Fix Released -- 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/369064 Title: Maximized apps go under the bottom bar when using vertically stacked screens Status in metacity package in Ubuntu: Fix Released Bug description: Binary package hint: metacity When using vertically stacked screens, maximized windows on the main screen have their status bar or lower portion of the window hidden underneath the bottom bar. ProblemType: Bug Architecture: i386 DistroRelease: Ubuntu 9.04 Package: metacity 1:2.25.144-0ubuntu2 ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: metacity Uname: Linux 2.6.28-11-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/369064/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 45706] Re: Resizing improvement request
** Changed in: metacity (Ubuntu) Status: Confirmed => Invalid -- 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/45706 Title: Resizing improvement request Status in metacity package in Ubuntu: Invalid Bug description: When I watch TV, I would love to be able to resize the window while keeping the aspect ratio constant. I gathered that metacity does already handle thie feature. However I understand that it must be handled by the application. But I watch TV using the programs "tvtime" or "xawtv", both of which are not gnome programs so can't assume that they are being used with metacity. So it would be great if it could be possible for the user, not the program, to control the aspect ratio. I dunno, for example, if I hold the "control" key while resizing the window, make metacity lock the aspect ratio, or add some option in the window menu (top left corner) or something... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/45706/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 395116] Re: Pidgin massive synchronization notifications halt metacity
** Changed in: metacity (Ubuntu) Status: Incomplete => Invalid -- 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/395116 Title: Pidgin massive synchronization notifications halt metacity Status in Pidgin: New Status in metacity package in Ubuntu: Invalid Bug description: Binary package hint: metacity How to reproduce the bug: 2 computers ( one with ubuntu using metacity - 1 MSN account ) - Add on MSN account as many contacts as you can. Probably 200-300 contacts. This account is set up in Pidgin and works perfectly on one computer. The contacts are stored on the local contact list and the server as well. - Disable the account on the first computer, and log in via Pidgin on another computer. The system should retrieve contacts from the server and add them to the local list. - While logged in, on the second computer, delete all the contacts of the specific account. Log out. - Go back to the first computer and log in. Now Pidgin will pop up one synchronization notification for every contact that is on the local contact list of the first computer, but not on the server; asking whether the contacts on the local contact file should be sent back to the server. - The user has to click YES or NO for every single window. There is no option for massive accepting or refusal. - After 25 or so notification pop ups at the same time (the user has no opportunity to click so fast, so that's going to happen for sure), the graphical environment will stop responding. - Problem can be solved temporarily by logging into the console and killing pidgin - Problem can be solved permanently when deleting the local contact database, so that Pidgin doesn't worry about the contacts syncing (or might there also be an option in Pidgin preferences, no idea) ProblemType: Bug Architecture: i386 DistroRelease: Ubuntu 8.10 ExecutablePath: /usr/bin/pidgin Package: pidgin 1:2.5.7-1ubuntu1~pidgin3.8.10 ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: pidgin Uname: Linux 2.6.27-14-generic i686 UnreportableReason: This is not a genuine Ubuntu package To manage notifications about this bug go to: https://bugs.launchpad.net/pidgin/+bug/395116/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 467972] Re: metacity assert failure: metacity:ERROR:core/bell.c:211:bell_flash_window_frame: assertion failed: (window->frame != NULL)
** Changed in: metacity (Ubuntu) Status: Triaged => Fix Released -- 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/467972 Title: metacity assert failure: metacity:ERROR:core/bell.c:211:bell_flash_window_frame: assertion failed: (window->frame != NULL) Status in Metacity: Fix Released Status in metacity package in Ubuntu: Fix Released Bug description: Binary package hint: metacity I don't know what happened. It just crashed. I was using Chrome when it happened and I just upgraded to Karmic today. ProblemType: Crash Architecture: i386 AssertionMessage: metacity:ERROR:core/bell.c:211:bell_flash_window_frame: assertion failed: (window->frame != NULL) Date: Sun Nov 1 11:45:57 2009 DistroRelease: Ubuntu 9.10 ExecutablePath: /usr/bin/metacity Package: metacity 1:2.28.0-0ubuntu1 ProcCmdline: metacity ProcEnviron: LANGUAGE=en_US.UTF-8 LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-14.48-generic Signal: 6 SourcePackage: metacity StacktraceTop: __kernel_vsyscall () raise () from /lib/tls/i686/cmov/libc.so.6 abort () from /lib/tls/i686/cmov/libc.so.6 g_assertion_message () from /lib/libglib-2.0.so.0 g_assertion_message_expr () from /lib/libglib-2.0.so.0 Title: metacity assert failure: metacity:ERROR:core/bell.c:211:bell_flash_window_frame: assertion failed: (window->frame != NULL) Uname: Linux 2.6.31-14-generic i686 UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev powerdev sambashare scanner tape video XsessionErrors: (gnome-settings-daemon:3172): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed (nautilus:3192): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed (polkit-gnome-authentication-agent-1:3195): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed (gnome-panel:3206): Gdk-WARNING **: /build/buildd/gtk+2.0-2.18.3/gdk/x11/gdkdrawable-x11.c:952 drawable is not a pixmap or window (chrome:3337): Gdk-WARNING **: XID collision, trouble ahead To manage notifications about this bug go to: https://bugs.launchpad.net/metacity/+bug/467972/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 892589] Re: attaching an external monitor to a laptop makes the image bad
** Changed in: metacity (Ubuntu) Status: New => Invalid -- 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/892589 Title: attaching an external monitor to a laptop makes the image bad Status in metacity package in Ubuntu: Invalid Bug description: If you attach an external monitor to a laptop while Ubuntu is running, always makes the image of the screen look bad on both the internal and the external monitor. I have two command attached to keyboard shortcuts which sometimes can make the computer usable again, if you switch back and forth between the internal and external monitor with: xrandr --output LVDS1 --off --output VGA1 --auto #switch on the internal monitor, external off xrandr --output LVDS1 --auto --output VGA1 --off #external on, internal off The success seem to depend on what programs are running at the moment of running those commands. If you only have a terminal opened it goes fine, but with Libreoffice and Firefox you need to restart Ubuntu. Attached are three screenshots which all show the screen looks like when the external monitor is attached. Ubuntu 11.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/892589/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 533758] Re: Button order/position should be part of Theme
** Changed in: metacity (Ubuntu) Status: Triaged => Invalid ** No longer affects: metacity -- 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/533758 Title: Button order/position should be part of Theme Status in metacity package in Ubuntu: Invalid Bug description: Binary package hint: metacity Given the change of default button layout in Lucid, I feel that this should be part of theme rather a part of a separate gconf entity. (I realise that might be a contentious request - but note I'm not asking to undo the new default button layout, just to associate it with the new themes rather than laying it down whatever theme people have). I'm referencing this from https://bugs.launchpad.net/ubuntu/+source /gnome-control-center/+bug/532754 which is the fact that the appearance dialog doesn't match the new reality. Dave To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/533758/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 968011] Re: window title font can't be scaled in precise (03-28)
** Changed in: metacity (Ubuntu) Status: New => Invalid -- 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/968011 Title: window title font can't be scaled in precise (03-28) Status in light-themes: Invalid Status in metacity package in Ubuntu: Invalid Bug description: window title font will remain absolute size no matter I scale up or down using Gnome-tweak-tool or universal access from system settings this happens in 12.04 64-bit daily from yesterday To manage notifications about this bug go to: https://bugs.launchpad.net/light-themes/+bug/968011/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1024802] Re: metacity crashed with SIGABRT in XFlush()
** Changed in: metacity (Ubuntu) Status: Confirmed => Invalid -- 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/1024802 Title: metacity crashed with SIGABRT in XFlush() Status in metacity package in Ubuntu: Invalid Bug description: metacity crashed. ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: metacity 1:2.34.1-1ubuntu11 ProcVersionSignature: Ubuntu 3.5.0-4.4-generic 3.5.0-rc6 Uname: Linux 3.5.0-4-generic i686 ApportVersion: 2.3-0ubuntu4 Architecture: i386 Date: Sat Jul 14 23:03:59 2012 ExecutablePath: /usr/bin/metacity InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) ProcCmdline: metacity ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: metacity StacktraceTop: ?? () from /usr/lib/i386-linux-gnu/libX11.so.6 ?? () from /usr/lib/i386-linux-gnu/libX11.so.6 _XEventsQueued () from /usr/lib/i386-linux-gnu/libX11.so.6 _XFlush () from /usr/lib/i386-linux-gnu/libX11.so.6 XFlush () from /usr/lib/i386-linux-gnu/libX11.so.6 Title: metacity crashed with SIGABRT in _XEventsQueued() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1024802/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 957276] Re: metacity crashed with SIGABRT in XSync()
** Changed in: metacity (Ubuntu) Status: Confirmed => Invalid -- 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/957276 Title: metacity crashed with SIGABRT in XSync() Status in metacity package in Ubuntu: Invalid Bug description: I was playing around with Remmina's windowed mode, trying to move the window around, when I got this crash. This is the first time this has happened, and I am unable to reproduce it. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: metacity 1:2.34.1-1ubuntu8 ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9 Uname: Linux 3.2.0-18-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 1.94.1-0ubuntu2 Architecture: amd64 Date: Fri Mar 16 14:06:55 2012 ExecutablePath: /usr/bin/metacity InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301) ProcCmdline: metacity ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: metacity StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XSync () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () Title: metacity crashed with SIGABRT in _XReply() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/957276/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1033417] Re: all window manager shortcuts (e.g. Alt-F4) broken in Unity
** Changed in: metacity (Ubuntu) Status: New => Invalid -- 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/1033417 Title: all window manager shortcuts (e.g. Alt-F4) broken in Unity Status in metacity package in Ubuntu: Invalid Bug description: Since about a week, all window manager shortcuts are broken, that is: pressing them does nothing. This affects most prominently Alt-F4 and Alt-Tab. The panel's shortcuts, like Alt, Super and Super+Number, are still working, as are shortcuts inside applications (and every other keyboard input). xev tells me that all input events for Alt-F4 are sent to the client window. This system is a virtual machine in VirtualBox under a 64-bit Windows 7 host; guest additions are installed. The system is used for web development; my typical session contains Firefox, Konsole (from KDE), Pidgin and pgAdmin III. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: metacity 1:2.34.1-1ubuntu11 ProcVersionSignature: Ubuntu 3.2.0-27.43-generic 3.2.21 Uname: Linux 3.2.0-27-generic x86_64 ApportVersion: 2.0.1-0ubuntu11 Architecture: amd64 Date: Mon Aug 6 08:59:53 2012 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) ProcEnviron: LANGUAGE= TERM=xterm-256color PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/zsh SourcePackage: metacity UpgradeStatus: Upgraded to precise on 2012-06-05 (61 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1033417/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1061032] Re: ref_count == 0, but source was still attached to a context
** Changed in: metacity (Ubuntu) Status: Confirmed => Invalid -- 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/1061032 Title: ref_count == 0, but source was still attached to a context Status in metacity package in Ubuntu: Invalid Bug description: Startng a user sesson desktop as "Gnome Sesson Classicc (Without effects)" I change to compiz and after to metacity. Then a error message is showed from glib: $ compiz --replace & [1] 2880 $ compiz (core) - Info: Loading plugin: core compiz (core) - Info: Starting plugin: core compiz (core) - Info: Loading plugin: ccp compiz (core) - Info: Starting plugin: ccp compizconfig - Info: Backend : ini compizconfig - Info: Integration : true compizconfig - Info: Profile : default $ metacity --replace & [2] 2883 $ compiz (core) - Info: Stopping plugin: ccp compiz (core) - Info: Unloading plugin: ccp compiz (core) - Info: Stopping plugin: core compiz (core) - Info: Unloading plugin: core (process:2880): GLib-WARNING **: /build/buildd/glib2.0-2.34.0/./glib/gmain.c:1817: ref_count == 0, but source was still attached to a context! ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: metacity 1:2.34.8-0ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4 Uname: Linux 3.5.0-16-generic i686 ApportVersion: 2.6.1-0ubuntu1 Architecture: i386 Date: Wed Oct 3 17:31:54 2012 InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20091126) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=es_ES.UTF-8 SHELL=/bin/bash SourcePackage: metacity UpgradeStatus: Upgraded to quantal on 2012-04-26 (160 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1061032/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 924909] Re: Windows have grey traces in Ubiquity
** Changed in: metacity (Ubuntu) Status: Confirmed => Invalid -- 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/924909 Title: Windows have grey traces in Ubiquity Status in metacity package in Ubuntu: Invalid Status in openbox package in Ubuntu: Fix Released Status in xfwm4 package in Ubuntu: Fix Released Bug description: I'm testing Xubuntu amd64 Precise alpha2 in live mode. When I get the screen to choose if I want to try it without any change or to install it, the background is black. Moving the window, it became grey "following the window". Sorry for this very bad report, I hope it's understandable. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: casper 1.302 ProcVersionSignature: Ubuntu 3.2.0-12.21-generic 3.2.2 Uname: Linux 3.2.0-12-generic x86_64 ApportVersion: 1.91-0ubuntu1 Architecture: amd64 CasperVersion: 1.302 Date: Wed Feb 1 14:47:54 2012 LiveMediaBuild: Xubuntu 12.04 "Precise Pangolin" - Alpha amd64 (20120201) ProcEnviron: PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: casper UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.casper.conf: 2012-02-01T15:42:30 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/924909/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 497031] Re: Auto maximize windows when dragging mouse cursor to the top of the screen
** Changed in: metacity (Ubuntu) Status: Triaged => Invalid -- 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/497031 Title: Auto maximize windows when dragging mouse cursor to the top of the screen Status in Metacity: Expired Status in metacity package in Ubuntu: Invalid Bug description: Binary package hint: metacity Dragging a window to the top of the screen not always maximize the window. ProblemType: Bug Architecture: amd64 Date: Tue Dec 15 13:19:38 2009 DistroRelease: Ubuntu 9.10 ExecutablePath: /usr/bin/metacity Package: metacity 1:2.28.0-0ubuntu1 ProcEnviron: SHELL=/bin/bash LANG=es_AR.UTF-8 ProcVersionSignature: Ubuntu 2.6.31-16.53-generic SourcePackage: metacity Uname: Linux 2.6.31-16-generic x86_64 XsessionErrors: (gnome-settings-daemon:1949): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed (gnome-settings-daemon:1949): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed (polkit-gnome-authentication-agent-1:1994): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed (nautilus:1989): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed To manage notifications about this bug go to: https://bugs.launchpad.net/metacity/+bug/497031/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1216292] Re: top program bar does not work with lenovo touchpad -- regression
"Package: metacity (not installed)", so not a bug in metacity. Ubuntu 13.10 is End Of Life. ** Changed in: metacity (Ubuntu) Status: New => Invalid -- 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/1216292 Title: top program bar does not work with lenovo touchpad -- regression Status in metacity package in Ubuntu: Invalid Bug description: So I woke up this morning (24-Aug-13) and my synaptic touchpad works to move the mouse but the buttons do not work on metacity components such as those three little circles in the upper left, nor to re-position the box, nor the side sliders. Keystroke commands work fine, as does my Lenovo touch screen. But the buttons to my synaptics touch pad seem to be non-operational. So I blamed metacity, because it wasn't recognizing the input from my touchpad buttons. The problem could also, of course, be with the drivers somehow. Funny, that little red button in the middle of my Lenovo typepad doesn't seem to work at all, but I usually don't use it so I'm not sure if the issues are connected. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: metacity (not installed) ProcVersionSignature: Ubuntu 3.11.0-3.8-generic 3.11.0-rc6 Uname: Linux 3.11.0-3-generic x86_64 ApportVersion: 2.12.1-0ubuntu2 Architecture: amd64 Date: Sat Aug 24 07:06:54 2013 InstallationDate: Installed on 2013-08-12 (12 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130811) MarkForUpload: True SourcePackage: metacity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1216292/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 894493] Re: After I use Xine Unity 2d panel become invisible
** Changed in: metacity (Ubuntu) Status: Confirmed => Invalid -- 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/894493 Title: After I use Xine Unity 2d panel become invisible Status in Metacity: Expired Status in unity-2d: Invalid Status in metacity package in Ubuntu: Invalid Status in unity-2d package in Ubuntu: Invalid Bug description: After I use Xine in Unity 2d , Unity 2d panel and menu bar become invisible. OnClick, OnMouseOver is work. To manage notifications about this bug go to: https://bugs.launchpad.net/metacity/+bug/894493/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 437139] Re: metacity assert failure: metacity:ERROR:core/boxes.c:1161:meta_rectangle_edge_aligns: code should not be reached
** Changed in: metacity (Ubuntu) Status: Triaged => Fix Released -- 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/437139 Title: metacity assert failure: metacity:ERROR:core/boxes.c:1161:meta_rectangle_edge_aligns: code should not be reached Status in Metacity: Fix Released Status in metacity package in Ubuntu: Fix Released Status in metacity source package in Precise: Invalid Status in metacity package in Debian: Fix Released Bug description: Binary package hint: metacity I think this is a new bug ProblemType: Crash Architecture: i386 AssertionMessage: metacity:ERROR:core/boxes.c:1161:meta_rectangle_edge_aligns: code should not be reached Date: Sat Sep 26 13:13:02 2009 DistroRelease: Ubuntu 9.10 ExecutablePath: /usr/bin/metacity Package: metacity 1:2.28.0-0ubuntu1 ProcCmdline: /usr/bin/metacity --replace ProcEnviron: LANG=it_IT.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-11.36-generic Signal: 6 SourcePackage: metacity StacktraceTop: __kernel_vsyscall () raise () from /lib/tls/i686/cmov/libc.so.6 abort () from /lib/tls/i686/cmov/libc.so.6 g_assertion_message () from /lib/libglib-2.0.so.0 ?? () Title: metacity assert failure: metacity:ERROR:core/boxes.c:1161:meta_rectangle_edge_aligns: code should not be reached Uname: Linux 2.6.31-11-generic i686 UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/metacity/+bug/437139/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1736449] Re: package libmetacity-private3a:amd64 1:3.18.7-0ubuntu0.3 failed to install/upgrade: Abhängigkeitsprobleme - verbleibt unkonfiguriert
** Changed in: metacity (Ubuntu) Status: New => Invalid -- 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/1736449 Title: package libmetacity-private3a:amd64 1:3.18.7-0ubuntu0.3 failed to install/upgrade: Abhängigkeitsprobleme - verbleibt unkonfiguriert Status in metacity package in Ubuntu: Invalid Bug description: The bug frequently occurs during updates. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libmetacity-private3a:amd64 1:3.18.7-0ubuntu0.3 ProcVersionSignature: Ubuntu 4.4.0-101.124-generic 4.4.95 Uname: Linux 4.4.0-101-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.13 Architecture: amd64 Date: Tue Dec 5 15:44:07 2017 ErrorMessage: Abhängigkeitsprobleme - verbleibt unkonfiguriert InstallationDate: Installed on 2016-07-21 (502 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: metacity Title: package libmetacity-private3a:amd64 1:3.18.7-0ubuntu0.3 failed to install/upgrade: Abhängigkeitsprobleme - verbleibt unkonfiguriert UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1736449/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 894487] Re: Gnome-panel won't redraw under tooltip
** Changed in: metacity (Ubuntu) Status: New => Invalid -- 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/894487 Title: Gnome-panel won't redraw under tooltip Status in metacity package in Ubuntu: Invalid Bug description: When using metacity if I place a nautilus window under gnome-panel in the bottom, and I move my mouse on a shortcut to have a tool-tip over gnome-panel, when I move the mouse to another shortcut, the area where the tool-tip was on gnome-panel is incorrectly redrawn with the content under gnome-panel. This behaviour is only reproducible with metacity, using compiz doesn't have the same issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/894487/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 971322] Re: Unity-2D/metacity window placement/move problems in precise
** Changed in: metacity (Ubuntu) Status: Confirmed => Invalid -- 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/971322 Title: Unity-2D/metacity window placement/move problems in precise Status in metacity package in Ubuntu: Invalid Bug description: I've upgraded oneiric to precise (32 bit). One annoying problem is the window placement/moving policy now. In oneiric this worked (I am using Unity-2D, so metacity, composing manager/effects are enabled) very well. If I open a new window, it will be placed "stacked" on existing window (eg if I open a new terminal (usually I have to open more of them), even if there is lots of "free" space on the workspace. So, I think metacity in oneiric tries to use available 'free' screen space, which is not true for oneiric. Another annoying thing is the window border "resistance". In oneiric, if I move a window, there is need for a little "push more" action to be able to move window when border is at another window's border. It's a great help to align windows in a nice way. In precise, this does not work, or at least it behaves oddly: if I move a window towards another horizontally this _is_ this effect, however not at the border but _before_ it! There is a huge space, probably the same size as the Unity launcher bar, is it possible, that positions are miscalculated? I am using "auto hide" for Unity. There is similar problem vertically however the "gap" is smaller, and I have no idea if there is some relation of the size of the gap and any other thing. It's about half of the height of the top panel, for example. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: metacity 1:2.34.1-1ubuntu9 ProcVersionSignature: Ubuntu 3.2.0-21.34-generic-pae 3.2.13 Uname: Linux 3.2.0-21-generic-pae i686 ApportVersion: 2.0-0ubuntu2 Architecture: i386 Date: Mon Apr 2 09:05:42 2012 InstallationMedia: Ubuntu-Server 10.04.1 LTS "Lucid Lynx" - Release i386 (20100816.2) SourcePackage: metacity UpgradeStatus: Upgraded to precise on 2012-03-01 (31 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/971322/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 985449] Re: unity-2d launcher behind a full screen window
** Changed in: metacity (Ubuntu) Status: Confirmed => Invalid -- 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/985449 Title: unity-2d launcher behind a full screen window Status in metacity package in Ubuntu: Invalid Bug description: Not exactly a show-stopper bug ... I have a terminal window, not maximazed, but full screen. I'm using Unity-2D+metacity, with composite support is switched on. The terminal window is semi- transparent. Now, if I move the mouse to the left side of the screen, I can see (through the semi transparent window) that Unity-2D's launcher is shown (it's configured for auto-hide). I guess it's a problem, since in case of a full screen window, I wouldn't except that anything other is activated if I move the mouse through the screen, as the screen is filled with a full screen window, so no other thing should be involved. The only problem I have with this: if I switch workspace then, unity-2d's launcher is still shown, so I have to move the mouse pointer on it, and then remove so it can be hidden, which is a bit annoying to do all the time, as I would like auto-hide ... Maybe it's not a metacity but an unity-2d problem? ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: metacity 1:2.34.1-1ubuntu11 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic-pae 3.2.14 Uname: Linux 3.2.0-23-generic-pae i686 ApportVersion: 2.0.1-0ubuntu5 Architecture: i386 Date: Thu Apr 19 09:34:33 2012 InstallationMedia: Ubuntu-Server 10.04.1 LTS "Lucid Lynx" - Release i386 (20100816.2) SourcePackage: metacity UpgradeStatus: Upgraded to precise on 2012-03-01 (48 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/985449/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 949191] Re: Maximize button-tooltips doesn't disappear after clicked
** Changed in: metacity (Ubuntu)
Status: New => Invalid
--
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/949191
Title:
Maximize button-tooltips doesn't disappear after clicked
Status in metacity package in Ubuntu:
Invalid
Bug description:
Hi,
when I move the mouse pointer to a window's 'maximize' button, and
waiting for the tooltip ("Maximize window") show, a "Close window"
tooltip gets up after I clicked on the 'maximize' button immediately,
and I can't remove it from the screen anymore.
The only way to remove it, I need to size back the window, and move
the pointer again to the buttons to show up a tooltip again.
Configuration:
Ubuntu 12.04 beta 1
Intel® Core 2 Duo E4500
Intel® G965 / ICH8 Chipset
Intel® GMA X3000
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: metacity 1:2.34.1-1ubuntu7
ProcVersionSignature: Ubuntu 3.2.0-18.28-generic-pae 3.2.9
Uname: Linux 3.2.0-18-generic-pae i686
ApportVersion: 1.94-0ubuntu2
Architecture: i386
Date: Wed Mar 7 18:02:40 2012
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120301)
ProcEnviron:
TERM=xterm
LANG=hu_HU.UTF-8
SHELL=/bin/bash
SourcePackage: metacity
UpgradeStatus: Upgraded to precise on 2012-03-07 (0 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/949191/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 733431] Re: Windows lack borders: visually unpleasant and leaves only one option to resize
** Changed in: metacity (Ubuntu)
Status: Confirmed => Invalid
--
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/733431
Title:
Windows lack borders: visually unpleasant and leaves only one option
to resize
Status in Ayatana Design:
Invalid
Status in light-themes:
Fix Released
Status in Unity:
Invalid
Status in unity-2d:
Invalid
Status in metacity package in Ubuntu:
Invalid
Bug description:
The latest change in light-themes (bug #733233) to drop the window
borders lowers the visual quality and the usability of the desktop for
Metacity users. Unity 2D users are all affected as well as Classic
desktop users with 'No Effects'.
Visually there is no frontier any more between application which just
looks odd. I do not know of any other OS that does that. The main
difference with Compiz is that Metacity does not have shadows.
Usability wise, the border was also use has a handle (probably too
thin) to let the user resize the window. Without that border the user
can only resize the window using the bottom right handle.
Proposal to re-apply zero-pixel borders:
Bug #740579 ("Wishlist: move to 0px borders now that Unity and
Unity-2D/Metacity can cope")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/733431/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1495733] Re: /usr/bin/metacity:6:g_assertion_message:g_assertion_message_expr:meta_rectangle_edge_aligns:apply_edge_resistance:apply_edge_resistance_to_each_side
** Changed in: metacity (Ubuntu) Status: New => Invalid -- 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/1495733 Title: /usr/bin/metacity:6:g_assertion_message:g_assertion_message_expr:meta_rectangle_edge_aligns:apply_edge_resistance:apply_edge_resistance_to_each_side Status in metacity package in Ubuntu: Invalid Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding metacity. This problem was most recently seen with version 1:3.14.3-1ubuntu7, the problem page at https://errors.ubuntu.com/problem/402541de22135316e7f1ce394346da0d4f716d2f contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1495733/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1160843] Re: Top panel is not active, does not show date or allow access to System Settings
** Changed in: metacity (Ubuntu) Status: New => Invalid -- 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/1160843 Title: Top panel is not active, does not show date or allow access to System Settings Status in metacity package in Ubuntu: Invalid Bug description: This is a regression. After updates of Tues 27 Mar 2013, the date vanished from the top panel and some of the icons lost functions. For instance, it is no longer possible to access System Settings that way. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: metacity 1:2.34.13-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-14.9-lowlatency 3.8.4 Uname: Linux 3.8.0-14-lowlatency x86_64 ApportVersion: 2.9.2-0ubuntu5 Architecture: amd64 Date: Wed Mar 27 07:02:05 2013 InstallationDate: Installed on 2013-01-04 (81 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130102) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: metacity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1160843/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1636620] Re: no wallpaper when compositing manager disabled
This is not metacity bug and 16.10 has reached End of Life long time ago. ** Changed in: metacity (Ubuntu) Status: Confirmed => Invalid -- 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/1636620 Title: no wallpaper when compositing manager disabled Status in metacity package in Ubuntu: Invalid Bug description: When compositing-manager is disabled for metacity, no wallpaper is shown. Ubuntu version: 16.10 (yakkety) metacity version: 1:3.20.3-1ubuntu2 Steps to reproduce: - open dconf-editor and set org.gnome.metacity.compositing-manager to false Expected result: - window shadows disappear, but otherwise no visible changes Actual result: - wallpaper disappears as well, desktop becomes solid black (note that the desktop is still functional, icons are shown normally; it's just the wallpaper that's missing) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1636620/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 58977] Re: Maximizing ignores docked panles with Xinerama
Launchpad has imported 15 comments from the remote bug at https://bugzilla.gnome.org/show_bug.cgi?id=339692. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2006-04-25T11:33:46+00:00 Antoinecailliau wrote: On maximize, the window should be stopped along the panel as when the panel is on the top Other information: I attached a screenshot of the bug. Reply at: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/58977/comments/0 On 2006-04-25T11:34:24+00:00 Antoinecailliau wrote: Created attachment 64267 Screenshot Reply at: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/58977/comments/1 On 2006-04-25T14:25:54+00:00 Sergej Kotliar wrote: Ah, so you mean that the X icon is hidden... strange... Can't reproduce it here, have been using a right-side panel since forever, and never seen that... Are you using metacity window manager? (the default one installed) If you try to move the panel somewhere else, and then put it back, does this bug appear again? Reply at: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/58977/comments/2 On 2006-04-25T16:34:21+00:00 Antoinecailliau wrote: Yes i'm using the default window manager, Metacity. When I move the panel somewhere and then put it back, the bug appear again, nothing changed. I've dual screen and the bug appear when the panel is in the "middle" of the both screen, there is no bug when the panel is on the right of the right screen, sorry never think that it could be that. Reply at: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/58977/comments/3 On 2006-04-25T16:37:16+00:00 Sergej Kotliar wrote: Yeah, I think that's the cause of it then. Retitling the bug. Don't have two screens, so I'll let someone else confirm this one. Reply at: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/58977/comments/4 On 2006-04-25T17:28:20+00:00 Elijah wrote: The EWMH provides no way to reserve any area of the screen except the portion at the edges. (Note that in a xinerama setup, there is only one "screen" which spans both monitors, so that rules out reserving the area this bug report talks about) So, the panel can't tell metacity that this area is reserved. metacity-2.14.x does have most of the code necessary to handle reserved area that isn't at screen edges, but not quite all of it. So three bugs: 1) EWMH needs to be extended to handle xinerama edges too 2) Metacity needs to support the new hints 3) gnome-panel needs to use the new hints EWMH is first, so I'll move to metacity for now and try to remember to bring this up on wm-spec-list at some point. Reply at: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/58977/comments/5 On 2006-04-25T18:32:44+00:00 Antoinecailliau wrote: Ok, tanks for the information, I'll try to follow my bug ^^ Reply at: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/58977/comments/6 On 2006-09-10T12:09:21+00:00 Sebastien Bacher wrote: Ubuntu bug about that: https://launchpad.net/distros/ubuntu/+source/metacity/+bug/58977 Reply at: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/58977/comments/8 On 2007-03-21T03:47:40+00:00 Elijah wrote: *** Bug 420626 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/58977/comments/11 On 2008-03-07T13:01:10+00:00 Marnanel Thurman wrote: *** Bug 520713 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/58977/comments/13 On 2008-04-11T16:18:13+00:00 0-marco wrote: *** Bug 527547 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/58977/comments/14 On 2009-01-25T20:52:39+00:00 Gnome-2 wrote: I wonder if this can be solved in the restricted case of n-monitors in line without changing anything except the STRUT_PARTIAL hint set by the panel. In my case I have two monitors stacked vertically (as far
[Desktop-packages] [Bug 58977] Re: Maximizing ignores docked panles with Xinerama
This is now fixed in both Metacity and Compiz, but it will require also changes in gnome-panel and GTK. ** Bug watch added: bugzilla.gnome.org/ #339692 https://bugzilla.gnome.org/show_bug.cgi?id=339692 ** Changed in: metacity Importance: Low => Unknown ** Changed in: metacity Status: Confirmed => Unknown ** Changed in: metacity Remote watch: GNOME Bug Tracker #339692 => bugzilla.gnome.org/ #339692 ** Changed in: metacity (Ubuntu) Status: Triaged => Fix Released -- 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/58977 Title: Maximizing ignores docked panles with Xinerama Status in Metacity: Unknown Status in compiz package in Ubuntu: Confirmed Status in kdebase-workspace package in Ubuntu: Invalid Status in metacity package in Ubuntu: Fix Released Status in metacity package in Debian: Fix Released Bug description: Binary package hint: metacity Hi When I add another screen using Xinerama, the gnome panels remain in the first screen, which is great, but when the panel is aligned vertically near the border between the two screens (either on the right of the left screen, or on the left of the right screen), maximizing a window ignores the panel, and the window is maximized right to the edge of the screen. Steps to reproduce: 1. Use xinerama with the second screen to the right of the first. 2. Add a vertical gnome panel to the right edge of the left screen. 3. maximize a window in the left screen. 4. The screen is maximized right to the edge of the screen, instead of the edge of the panel. To manage notifications about this bug go to: https://bugs.launchpad.net/metacity/+bug/58977/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1862500] Re: Desktop icons are placed off-screen when using multiple monitors
Resolution Settings ** Attachment added: "MonitorSettings.png" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1862500/+attachment/5326639/+files/MonitorSettings.png -- 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/1862500 Title: Desktop icons are placed off-screen when using multiple monitors Status in xorg package in Ubuntu: New Bug description: I have 2 monitors connected in "Join Display Mode". Monitor 1 (secondary) 1366x798, Landscape, 100% Monitor 2 (primary) 1920x1080, Landscape, 100% I can see files on the Desktop inside the File Browser, but on the Desktop icons are either not visible or limited text from one of the icons can be seen in the top left corner of the secondary monitor. Screenshots attached. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Feb 9 10:16:18 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: ndiswrapper, 1.60, 5.3.0-28-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0162] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [17aa:3083] Advanced Micro Devices, Inc. [AMD/ATI] Caicos PRO [Radeon HD 7450] [1002:677b] (prog-if 00 [VGA controller]) Subsystem: Bitland(ShenZhen) Information Technology Co., Ltd. Caicos PRO [Radeon HD 7450] [1642:3a76] InstallationDate: Installed on 2019-12-20 (50 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: LENOVO 3212AP3 ProcEnviron: LANGUAGE=en_ZA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_ZA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=c29a-51cf-4584-b908-5081f9693928 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/21/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 9SKT63AUS dmi.board.name: MAHOBAY dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnLENOVO:bvr9SKT63AUS:bd03/21/2013:svnLENOVO:pn3212AP3:pvrThinkCentreM92p:rvnLENOVO:rnMAHOBAY:rvrNODPK:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: 3212AP3 dmi.product.sku: LENOVO_MT_3212 dmi.product.version: ThinkCentre M92p dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1862500/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1862500] Re: Desktop icons are placed off-screen when using multiple monitors
Image showing the perceived location of missing icons on Desktop ** Attachment added: "FullDesktop.jpg" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1862500/+attachment/5326638/+files/FullDesktop.jpg -- 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/1862500 Title: Desktop icons are placed off-screen when using multiple monitors Status in xorg package in Ubuntu: New Bug description: I have 2 monitors connected in "Join Display Mode". Monitor 1 (secondary) 1366x798, Landscape, 100% Monitor 2 (primary) 1920x1080, Landscape, 100% I can see files on the Desktop inside the File Browser, but on the Desktop icons are either not visible or limited text from one of the icons can be seen in the top left corner of the secondary monitor. Screenshots attached. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Feb 9 10:16:18 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: ndiswrapper, 1.60, 5.3.0-28-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0162] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [17aa:3083] Advanced Micro Devices, Inc. [AMD/ATI] Caicos PRO [Radeon HD 7450] [1002:677b] (prog-if 00 [VGA controller]) Subsystem: Bitland(ShenZhen) Information Technology Co., Ltd. Caicos PRO [Radeon HD 7450] [1642:3a76] InstallationDate: Installed on 2019-12-20 (50 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: LENOVO 3212AP3 ProcEnviron: LANGUAGE=en_ZA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_ZA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=c29a-51cf-4584-b908-5081f9693928 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/21/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 9SKT63AUS dmi.board.name: MAHOBAY dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnLENOVO:bvr9SKT63AUS:bd03/21/2013:svnLENOVO:pn3212AP3:pvrThinkCentreM92p:rvnLENOVO:rnMAHOBAY:rvrNODPK:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: 3212AP3 dmi.product.sku: LENOVO_MT_3212 dmi.product.version: ThinkCentre M92p dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1862500/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1862500] [NEW] Desktop icons are placed off-screen when using multiple monitors
Public bug reported: I have 2 monitors connected in "Join Display Mode". Monitor 1 (secondary) 1366x798, Landscape, 100% Monitor 2 (primary) 1920x1080, Landscape, 100% I can see files on the Desktop inside the File Browser, but on the Desktop icons are either not visible or limited text from one of the icons can be seen in the top left corner of the secondary monitor. Screenshots attached. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Feb 9 10:16:18 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: ndiswrapper, 1.60, 5.3.0-28-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0162] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [17aa:3083] Advanced Micro Devices, Inc. [AMD/ATI] Caicos PRO [Radeon HD 7450] [1002:677b] (prog-if 00 [VGA controller]) Subsystem: Bitland(ShenZhen) Information Technology Co., Ltd. Caicos PRO [Radeon HD 7450] [1642:3a76] InstallationDate: Installed on 2019-12-20 (50 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: LENOVO 3212AP3 ProcEnviron: LANGUAGE=en_ZA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_ZA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=c29a-51cf-4584-b908-5081f9693928 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/21/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 9SKT63AUS dmi.board.name: MAHOBAY dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnLENOVO:bvr9SKT63AUS:bd03/21/2013:svnLENOVO:pn3212AP3:pvrThinkCentreM92p:rvnLENOVO:rnMAHOBAY:rvrNODPK:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: 3212AP3 dmi.product.sku: LENOVO_MT_3212 dmi.product.version: ThinkCentre M92p dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.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 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1862500 Title: Desktop icons are placed off-screen when using multiple monitors Status in xorg package in Ubuntu: New Bug description: I have 2 monitors connected in "Join Display Mode". Monitor 1 (secondary) 1366x798, Landscape, 100% Monitor 2 (primary) 1920x1080, Landscape, 100% I can see files on the Desktop inside the File Browser, but on the Desktop icons are either not visible or limited text from one of the icons can be seen in the top left corner of the secondary monitor. Screenshots attached. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Feb 9 10:16:18 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: ndiswrapper, 1.60, 5.3.0-28-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0162] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [17aa:3083] Advanced Micro Devices, Inc. [AMD/ATI] Caicos PRO [Radeon HD 7450] [1002:677b] (prog-if 00 [VGA controller]) Subsystem: Bitland(ShenZhen) Information Technology Co., Lt
