[Desktop-packages] [Bug 2020782] Re: Xdcv: Changing display scale setting and reverting it fails
I've also tested the "vv5" package in a fresh VM and can confirm that zero hz is now supported, and now facing the same scenario where multiple monitors are automatically enabled. Another issue that still stands is the "config history" issue I've mentioned. If you exclusively change the resolution from gnome display settings, it can apply a new resolution and revert to a previous config (via the timeout prompt) without any issue. But when the resolution is changed via the NICE DCV client's options (or via `xrandr` for that matter), mutter does not register that resolution change in `config_history`, and cannot revert back to the previous config when prompted. This is reproducible with just the default gnome desktop environment and the `xrandr` The reproducer is as follows: (assume that the initial resolution is 1920x1080) - Set a resolution via `xrandr`, e.g. (1366x768) - Open gnome display settings, and try to set the resolution to 1024x768 - Press "revert back" when prompted - The resolution will not go back to 1366x768 as it should and will stay at 1024x768 I've debugged this and noticed that gnome display settings use mutter's org.gnome.Mutter.DisplayConfig DBus interface and calls ApplyMonitorsConfig for resolution changes, whereas neither NICE DCV nor xrandr does that, so mutter is not notified about the change. I guess this will need a separate issue. -- 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/2020782 Title: Xdcv: Changing display scale setting and reverting it fails Status in mutter package in Ubuntu: In Progress Bug description: In Amazon Workspaces running Ubuntu 22.04, when attempting to change the Scale in the Gnome Display settings, if you click on a different scale (i.e. changing from 100% to 200%) and hitting apply, it will bring up a prompt asking if you want to keep or revert the changes and there will be a timer of 20 seconds. If you try to revert the changes (either by letting the timer expire or by clicking the "revert" button), we will hit one of the following two behaviors: 1 - The setting won't revert and will keep scaled 2 - gnome-shell will show some error messages in syslog and the display will be "corrupted", where the only window you are able to click is the display setting and if you try to drag it, it will leave a "blur" throughout the window (per discussions, this seems to be https://launchpad.net/bugs/1924689) For both situations, changing the display resolution (i.e. going into and out of full screen in the workspaces client) will fix the issue When hitting situation 1, syslog shows: May 17 17:33:10 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous configuration: Invalid mode 1920x1080 (19.958942) for monitor 'unknown unknown' When hitting situation 2, syslog shows: May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use stored monitor configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use linear monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use fallback monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Impossible to set scaling on crtc 59 to 1.00, error id 2 May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Xlib: extension "DPMS" missing on display ":1". May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Object St.Label (0x557090d07de0), has been already disposed — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: == Stack trace for context 0x557090bee180 == May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #0 557093f00e68 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/appIcons.js:1349 (2cdac32b2e20 @ 105) May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #1 557093f00dd8 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/dash.js:42 (2cdac32a5d80 @ 27) May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #2 557093f00d58 i resource:///org/gnome/shell/ui/dash.js:545 (20c3e0d20970 @ 24) May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: JS ERROR: TypeError: monitor is null#012_updateWorkAreaBox@resource:///org/gnome/shell/ui/overviewControls.js:58:26#012_init/<@resource:///org/gnome/shell/ui/overviewControls.js:51:45 Sometimes the stack trace isn't shown, but the symptom is the same: May 17 18:31:39 U-1AZMIM8SIPZ6I
[Desktop-packages] [Bug 2020782] Re: Xdcv: Changing display scale setting and reverting it fails
Hello Daniel, I've also been debugging this issue and noticed something weird while reproducing it. It seems that resizing the screen via resizing the NICE DCV client does not invoke the `meta_monitor_config_manager_set_current` method, so the current config and the history are untouched. Let's say we have an initial resolution of QxZ@T hz, sf 1(scale factor). The NICE DCV client screen resize changes it to WxH@F sf 1.5, but libmutter still thinks the screen is at QxZ@T sf 1. At this point, `xrandr` output no longer shows QxZ@T hz as a supported resolution. When the user tries to change the scale, the change is registered as both the resolution change and the scale change as per the perspective of "libmutter", and if the user proceeds to accept this configuration, everything is fine because the Xdcv already lists `WxH@F` as a supported resolution, but if not (i.e. user tries to revert back to the previous) it fails because QxZ@T hz is no longer on the supported resolution set. Therefore, I think one of the problems we're facing here is libmutter/Xdcv being out-of-sync when the screen resolution is changed via the NICE DCV client. I'm currently looking into how we can reflect the client resolutions to libmutter (I'm not well-versed in mutter codebase so progressing a little bit slow) I'll continue to post my findings as I progress. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2020782 Title: Xdcv: Changing display scale setting and reverting it fails Status in mutter package in Ubuntu: In Progress Bug description: In Amazon Workspaces running Ubuntu 22.04, when attempting to change the Scale in the Gnome Display settings, if you click on a different scale (i.e. changing from 100% to 200%) and hitting apply, it will bring up a prompt asking if you want to keep or revert the changes and there will be a timer of 20 seconds. If you try to revert the changes (either by letting the timer expire or by clicking the "revert" button), we will hit one of the following two behaviors: 1 - The setting won't revert and will keep scaled 2 - gnome-shell will show some error messages in syslog and the display will be "corrupted", where the only window you are able to click is the display setting and if you try to drag it, it will leave a "blur" throughout the window (per discussions, this seems to be https://launchpad.net/bugs/1924689) For both situations, changing the display resolution (i.e. going into and out of full screen in the workspaces client) will fix the issue When hitting situation 1, syslog shows: May 17 17:33:10 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous configuration: Invalid mode 1920x1080 (19.958942) for monitor 'unknown unknown' When hitting situation 2, syslog shows: May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use stored monitor configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use linear monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use fallback monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Impossible to set scaling on crtc 59 to 1.00, error id 2 May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Xlib: extension "DPMS" missing on display ":1". May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Object St.Label (0x557090d07de0), has been already disposed — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: == Stack trace for context 0x557090bee180 == May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #0 557093f00e68 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/appIcons.js:1349 (2cdac32b2e20 @ 105) May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #1 557093f00dd8 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/dash.js:42 (2cdac32a5d80 @ 27) May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #2 557093f00d58 i resource:///org/gnome/shell/ui/dash.js:545 (20c3e0d20970 @ 24) May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: JS ERROR: TypeError: monitor is null#012_updateWorkAreaBox@resource:///org/gnome/shell/ui/overviewControls.js:58:26#012_init/<@resource:///org/gnome/shell/ui/overviewControls.js:51:45 Sometimes the stack trace isn't shown, but the symptom is the same: May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed
[Desktop-packages] [Bug 2020782] Re: Changing display scale setting and reverting it, causes gnome-shell to error with "Failed to restore previous configuration" and other error messages
Reproducer: -- Grab a fresh Ubuntu 22.04 VM, then install NICE DCV Server & NICE Xdcv -- # Exit graphical mode sudo systemctl isolate multi-user.target # Install `ssh` & import id (optional) sudo apt -y install openssh-server ssh-import-id # Disable wayland sudo sed -i "s/WaylandEnable=True/WaylandEnable=false/" /etc/gdm3/custom.conf # Install NICE DCV Server & Nice XDCV cd /tmp wget https://d1uj6qtbmh3dt5.cloudfront.net/NICE-GPG-KEY gpg --import NICE-GPG-KEY wget https://d1uj6qtbmh3dt5.cloudfront.net/2023.0/Servers/nice-dcv-2023.0-15065-ubuntu2204-x86_64.tgz tar -xvzf nice-dcv-2023.0-15065-ubuntu2204-x86_64.tgz cd nice-dcv-2023.0-15065-ubuntu2204-x86_64 sudo apt -y install ./nice-dcv-server_2023.0.15065-1_amd64.ubuntu2204.deb sudo apt -y install ./nice-xdcv_2023.0.547-1_amd64.ubuntu2204.deb # Add "dcv" user to "video" group: sudo usermod -aG video dcv # Start dcv server: sudo systemctl start dcvserver # Create a session: sudo dcv create-session my-test-session --owner=test -- client -- # Install NICE DCV client and connect to the dcv host wget https://d1uj6qtbmh3dt5.cloudfront.net/2023.0/Clients/nice-dcv-viewer_2023.0.5483-1_amd64.ubuntu2204.deb dpkg -i nice-dcv-viewer_2023.0.5483-1_amd64.ubuntu2204.deb dcvviewer https://:8443#my-test-session # Then, try to change the display scale, and click "revert settings", the session should freeze # gnome-shell log should contain similar log messages to the following: May 30 15:59:03 test-2 gnome-shell[4906]: Failed to restore previous configuration: Invalid mode 3840x1352 (59,963089) for monitor 'unknown unknown' May 30 15:59:03 test-2 gnome-shell[4906]: Failed to use linear monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' May 30 15:59:03 test-2 gnome-shell[4906]: Failed to use fallback monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' May 30 15:59:03 test-2 gnome-shell[4906]: Impossible to set scaling on crtc 59 to 1,00, error id 2 -- 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/2020782 Title: Changing display scale setting and reverting it, causes gnome-shell to error with "Failed to restore previous configuration" and other error messages Status in mutter package in Ubuntu: New Bug description: In Amazon Workspaces running Ubuntu 22.04, when attempting to change the Scale in the Gnome Display settings, if you click on a different scale (i.e. changing from 100% to 200%) and hitting apply, it will bring up a prompt asking if you want to keep or revert the changes and there will be a timer of 20 seconds. If you try to revert the changes (either by letting the timer expire or by clicking the "revert" button), we will hit one of the following two behaviors: 1 - The setting won't revert and will keep scaled 2 - gnome-shell will show some error messages in syslog and the display will be "corrupted", where the only window you are able to click is the display setting and if you try to drag it, it will leave a "blur" throughout the window (per discussions, this seems to be https://launchpad.net/bugs/1924689) For both situations, changing the display resolution (i.e. going into and out of full screen in the workspaces client) will fix the issue When hitting situation 1, syslog shows: May 17 17:33:10 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous configuration: Invalid mode 1920x1080 (19.958942) for monitor 'unknown unknown' When hitting situation 2, syslog shows: May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use stored monitor configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use linear monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use fallback monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Impossible to set scaling on crtc 59 to 1.00, error id 2 May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Xlib: extension "DPMS" missing on display ":1". May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Object St.Label (0x557090d07de0), has been already disposed — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: == Stack trace for context 0x557090bee180 == May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #0 557093f00e68 i
[Desktop-packages] [Bug 2020782] Re: Changing display scale setting and reverting it, causes gnome-shell to error with "Failed to restore previous configuration" and other error messages
I'm still able to reproduce the bug with the PPA installed. I'll investigate this further and share my findings. -- 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/2020782 Title: Changing display scale setting and reverting it, causes gnome-shell to error with "Failed to restore previous configuration" and other error messages Status in mutter package in Ubuntu: New Bug description: In Amazon Workspaces running Ubuntu 22.04, when attempting to change the Scale in the Gnome Display settings, if you click on a different scale (i.e. changing from 100% to 200%) and hitting apply, it will bring up a prompt asking if you want to keep or revert the changes and there will be a timer of 20 seconds. If you try to revert the changes (either by letting the timer expire or by clicking the "revert" button), we will hit one of the following two behaviors: 1 - The setting won't revert and will keep scaled 2 - gnome-shell will show some error messages in syslog and the display will be "corrupted", where the only window you are able to click is the display setting and if you try to drag it, it will leave a "blur" throughout the window (per discussions, this seems to be https://launchpad.net/bugs/1924689) For both situations, changing the display resolution (i.e. going into and out of full screen in the workspaces client) will fix the issue When hitting situation 1, syslog shows: May 17 17:33:10 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous configuration: Invalid mode 1920x1080 (19.958942) for monitor 'unknown unknown' When hitting situation 2, syslog shows: May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use stored monitor configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use linear monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use fallback monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Impossible to set scaling on crtc 59 to 1.00, error id 2 May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Xlib: extension "DPMS" missing on display ":1". May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Object St.Label (0x557090d07de0), has been already disposed — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: == Stack trace for context 0x557090bee180 == May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #0 557093f00e68 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/appIcons.js:1349 (2cdac32b2e20 @ 105) May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #1 557093f00dd8 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/dash.js:42 (2cdac32a5d80 @ 27) May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #2 557093f00d58 i resource:///org/gnome/shell/ui/dash.js:545 (20c3e0d20970 @ 24) May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: JS ERROR: TypeError: monitor is null#012_updateWorkAreaBox@resource:///org/gnome/shell/ui/overviewControls.js:58:26#012_init/<@resource:///org/gnome/shell/ui/overviewControls.js:51:45 Sometimes the stack trace isn't shown, but the symptom is the same: May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown' May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use stored monitor configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown' May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use linear monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use fallback monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Impossible to set scaling on crtc 59 to 1.00, error id 2 May 17 18:31:40 U-1AZMIM8SIPZ6I gnome-shell[3030]: Xlib: extension "DPMS" missing on display ":1". I'm unable to reproduce the problem if I manually install ubuntu-desktop and use the Nice DCV Server (as used by Workspaces) by following the steps from (using the xorg-x11-drv-dummy): https://docs.aws.amazon.com/dcv/latest/adminguide/setting-up- installing-linux.html One relevant difference is that Workspaces uses a custom X11 server /usr/bin/Xdcv,
[Desktop-packages] [Bug 2007746] Re: [SRU] xserver crashes when hyperv_drm kernel module is loaded on azure NV series instances w/ nvidia grid driver
Tested the proposed package (2:1.20.13-1ubuntu1~20.04.7) with the test plan; it no longer crashes and behaves as expected. ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done-focal -- 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/2007746 Title: [SRU] xserver crashes when hyperv_drm kernel module is loaded on azure NV series instances w/ nvidia grid driver Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server source package in Focal: Fix Committed Bug description: [ Impact ] * Microsoft Azure NV-series instances with NVidia GRID drivers started to experience xserver crashes while following Microsoft's official guide to installing Nvidia drivers [1]. * Root cause analysis showed that it was due to having a device with BusID "PCI:0@:0:0", where domain id is >= 32767 while the hyperv_drm kernel module is loaded. * Removing either the BusID specification or unloading the hyperv_drm kernel module seems to fix the crash. * The crash is happening while X.server is trying to enumerate PCI devices. X.server dereferences a NULL pointer while trying to access to the PCI device info. * The reason why it only happens while the hyperv_drm kernel module is loaded is that the hyperv_drm module does not expose PCI hardware information since it's a virtual device. * The upstream patch [2] addresses the issue and it's confirmed that the xserver with the patch does not experience the crash. * Ubuntu Focal `xorg-server` package does not include the patch [2] at the moment (xserver-xorg-core=2:1.20.13-1ubuntu1~20.04.6). [1]: https://learn.microsoft.com/en-us/azure/virtual-machines/linux/n-series-driver-setup#install-grid-drivers-on-nv-or-nvv3-series-vms [2]: https://github.com/freedesktop/xorg-xserver/commit/0d93bbfa2cfacbb73741f8bed0e32fa1a656b928 [ Test Plan ] Part (a) is quoted from Microsoft's official guide [1]. Part (a): * Spawn a Microsoft Azure NV-series instance with an NVidia GRID-supported GPU - e.g. `NV36adms A10` * Install updates, required tooling, and the desktop environment: - sudo apt-get update - sudo apt-get upgrade -y - sudo apt-get dist-upgrade -y - sudo apt-get install build-essential ubuntu-desktop -y - sudo apt-get install linux-azure -y * Disable nouveau kernel driver: # Create a blacklist file /etc/modprobe.d/nouveau.conf with following contents: blacklist nouveau blacklist lbm-nouveau * Reboot the VM, re-connect, and then stop X server: - sudo reboot # wait for the reboot, reconnect, and continue: - sudo systemctl stop lightdm.service * Download and install the NVidia GRID driver: - wget -O NVIDIA-Linux-x86_64-grid.run https://go.microsoft.com/fwlink/?linkid=874272 - chmod +x NVIDIA-Linux-x86_64-grid.run - sudo ./NVIDIA-Linux-x86_64-grid.run - # When the setup asks whether you want to run the nvidia-xconfig utility to update your X configuration file, select Yes. * Copy /etc/nvidia/gridd.conf.template to /etc/nvidia/gridd.conf - sudo cp /etc/nvidia/gridd.conf.template /etc/nvidia/gridd.conf * Edit /etc/nvidia/grid.conf - sudo nano /etc/nvidia/grid.conf # Append the following lines: IgnoreSP=FALSE EnableUI=FALSE # Remove this line if present: FeatureType=0 # And save. * Reboot the VM Part (b): * Ensure that the hyperv_drm kernel module is loaded: - sudo modprobe hyperv_drm * Use the attached xorg.conf file to override /etc/X11/xorg.conf file * try to start the `xserver`: - sudo startx * `xserver` should crash with a similar output to the following: X.Org X Server 1.20.13 X Protocol Version 11, Revision 0 Build Operating System: linux Ubuntu Current Operating System: Linux a10test 5.15.0-1031-azure #38~20.04.1-Ubuntu SMP Mon Jan 9 18:23:48 UTC 2023 x86_64 Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.15.0-1031-azure root=PARTUUID=4cac852b-afba-447b-b3e7-c002155c1305 ro console=tty1 console=ttyS0 earlyprintk=ttyS0 panic=-1 Build Date: 07 February 2023 12:48:13PM xorg-server 2:1.20.13-1ubuntu1~20.04.6 (For technical support please see http://www.ubuntu.com/support) Current version of pixman: 0.38.4 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.1.log", Time: Sat Feb 18 10:54:26 2023 (==) Using config file: "/etc/X11/xorg.conf" (==) Using system config directory "/usr/share/X11/xorg.conf.d" (EE) (EE) Backtrace: (EE) 0:
[Desktop-packages] [Bug 2003176] Re: SRU: metacity crashes while minimizing a windows that has undocked child
Kinetic and above has >= 3.46.0, later series not affected. ** Changed in: metacity (Ubuntu) Status: New => 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/2003176 Title: SRU: metacity crashes while minimizing a windows that has undocked child Status in metacity package in Ubuntu: Fix Released Status in metacity source package in Focal: Fix Released Status in metacity source package in Jammy: Fix Released Bug description: [General information about the SRU] * It includes the fix for the bug https://gitlab.gnome.org/GNOME/metacity/-/issues/31 * The fix is already included in 3.46.0 release: https://gitlab.gnome.org/GNOME/metacity/-/commit/77f1d55479bfef479f76011a1ee5636f9bf6b08b#9f621eb5fd3bcb2fa5c7bd228c9b1ad42edc46c8 * The reproducer also revealed another issue with docked windows, undocked windows are not being restored after parent window is minimized and restored * The fix for restore is included in 3.46.1 release: https://gitlab.gnome.org/GNOME/metacity/-/commit/3db07fafa1c7ff9749b6a82ccb36d8b62f2304d9 * Focal(3.36.1) and Jammy (3.44.0) needs both fixes to be backported [Impact] This affects users using applications that have docked windows [Test Case] * Install gnome-session-flashback (metacity) and reproducer's dependencies `sudo apt install lightdm gnome-session-flashback pyside2-tools python3-pyside2.qtwidgets` * Start a graphical session with metacity * run python3 Untitled.py * Undock one of the application's child windows * Minimize main window * Result: Metacity will crash * Fix: install fix from ppa: * sudo add-apt-repository ppa:mustafakemalgilor/lp-2003176-0 * sudo apt update * sudo reboot # or alternatively, restart display manager * run python3 Untitled.py * Undock one of the application's child windows * Minimize main window * Expectation: it should not crash and the application should be minimized. [Regression Potential] The fix is small in size and localized, it should not cause any regressions. - Bug Version: 1:3.36.1-1 / 1:3.44.0-1 Metacity is running without the composite manager. Users cannot minimize an application with an undocked child window ProblemType: Bug DistroRelease: Ubuntu 20.04 / Ubuntu 22.04 Package: metacity 1:3.36.1-1 / 1:3.44.0-1 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/2003176/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2007746] Re: [SRU] xserver crashes when hyperv_drm kernel module is loaded on azure NV series instances w/ nvidia grid driver
** Description changed: [ Impact ] - * Microsoft Azure NV-series instances with NVidia GRID drivers started + * Microsoft Azure NV-series instances with NVidia GRID drivers started to experience xserver crashes while following Microsoft's official guide to installing Nvidia drivers [1]. - * Root cause analysis showed that it was due to having a device with + * Root cause analysis showed that it was due to having a device with BusID "PCI:0@:0:0", where domain id is >= 32767 while the hyperv_drm kernel module is loaded. - * Removing either the BusID specification or unloading the hyperv_drm + * Removing either the BusID specification or unloading the hyperv_drm kernel module seems to fix the crash. - * The crash is happening while X.server is trying to enumerate PCI + * The crash is happening while X.server is trying to enumerate PCI devices. X.server dereferences a NULL pointer while trying to access to the PCI device info. - * The reason why it only happens while the hyperv_drm kernel module is + * The reason why it only happens while the hyperv_drm kernel module is loaded is that the hyperv_drm module does not expose PCI hardware information since it's a virtual device. - * The upstream patch [2] addresses the issue and it's confirmed that + * The upstream patch [2] addresses the issue and it's confirmed that the xserver with the patch does not experience the crash. - * Ubuntu Focal `xorg-server` package does not include the patch [2] at + * Ubuntu Focal `xorg-server` package does not include the patch [2] at the moment (xserver-xorg-core=2:1.20.13-1ubuntu1~20.04.6). - [1]: https://learn.microsoft.com/en-us/azure/virtual-machines/linux/n-series-driver-setup#install-grid-drivers-on-nv-or-nvv3-series-vms - [2]: https://github.com/freedesktop/xorg-xserver/commit/0d93bbfa2cfacbb73741f8bed0e32fa1a656b928 + [1]: https://learn.microsoft.com/en-us/azure/virtual-machines/linux/n-series-driver-setup#install-grid-drivers-on-nv-or-nvv3-series-vms + [2]: https://github.com/freedesktop/xorg-xserver/commit/0d93bbfa2cfacbb73741f8bed0e32fa1a656b928 [ Test Plan ] Part (a) is quoted from Microsoft's official guide [1]. Part (a): - * Spawn a Microsoft Azure NV-series instance with an NVidia GRID-supported GPU -- e.g. `NV36adms A10` - * Install updates, required tooling, and the desktop environment: -- sudo apt-get update -- sudo apt-get upgrade -y -- sudo apt-get dist-upgrade -y -- sudo apt-get install build-essential ubuntu-desktop -y -- sudo apt-get install linux-azure -y - * Disable nouveau kernel driver: -# Create a blacklist file /etc/modprobe.d/nouveau.conf with following contents: -blacklist nouveau -blacklist lbm-nouveau - * Reboot the VM, re-connect, and then stop X server: -- sudo reboot -# wait for the reboot, reconnect, and continue: -- sudo systemctl stop lightdm.service - * Download and install the NVidia GRID driver: -- wget -O NVIDIA-Linux-x86_64-grid.run https://go.microsoft.com/fwlink/?linkid=874272 -- chmod +x NVIDIA-Linux-x86_64-grid.run -- sudo ./NVIDIA-Linux-x86_64-grid.run -- # When the setup asks whether you want to run the nvidia-xconfig utility to update your X configuration file, select Yes. - * Copy /etc/nvidia/gridd.conf.template to /etc/nvidia/gridd.conf -- sudo cp /etc/nvidia/gridd.conf.template /etc/nvidia/gridd.conf - * Edit /etc/nvidia/grid.conf -- sudo nano /etc/nvidia/grid.conf -# Append the following lines: -IgnoreSP=FALSE -EnableUI=FALSE -# Remove this line if present: -FeatureType=0 -# And save. - * Reboot the VM + * Spawn a Microsoft Azure NV-series instance with an NVidia GRID-supported GPU + - e.g. `NV36adms A10` + * Install updates, required tooling, and the desktop environment: + - sudo apt-get update + - sudo apt-get upgrade -y + - sudo apt-get dist-upgrade -y + - sudo apt-get install build-essential ubuntu-desktop -y + - sudo apt-get install linux-azure -y + * Disable nouveau kernel driver: + # Create a blacklist file /etc/modprobe.d/nouveau.conf with following contents: + blacklist nouveau + blacklist lbm-nouveau + * Reboot the VM, re-connect, and then stop X server: + - sudo reboot + # wait for the reboot, reconnect, and continue: + - sudo systemctl stop lightdm.service + * Download and install the NVidia GRID driver: + - wget -O NVIDIA-Linux-x86_64-grid.run https://go.microsoft.com/fwlink/?linkid=874272 + - chmod +x NVIDIA-Linux-x86_64-grid.run + - sudo ./NVIDIA-Linux-x86_64-grid.run + - # When the setup asks whether you want to run the nvidia-xconfig utility to update your X configuration file, select Yes. + * Copy /etc/nvidia/gridd.conf.template to /etc/nvidia/gridd.conf + - sudo cp /etc/nvidia/gridd.conf.template /etc/nvidia/gridd.conf + * Edit /etc/nvidia/grid.conf + - sudo nano /etc/nvidia/grid.conf + #
[Desktop-packages] [Bug 2007746] Re: [SRU] xserver crashes when hyperv_drm kernel module is loaded on azure NV series instances w/ nvidia grid driver
The relevant function is absent in Bionic and Jammy is based on an upstream version that contains the fix, so I presume the only affected series is Focal right now. -- 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/2007746 Title: [SRU] xserver crashes when hyperv_drm kernel module is loaded on azure NV series instances w/ nvidia grid driver Status in xorg-server package in Ubuntu: New Status in xorg-server source package in Focal: In Progress Bug description: [ Impact ] * Microsoft Azure NV-series instances with NVidia GRID drivers started to experience xserver crashes while following Microsoft's official guide to installing Nvidia drivers [1]. * Root cause analysis showed that it was due to having a device with BusID "PCI:0@:0:0", where domain id is >= 32767 while the hyperv_drm kernel module is loaded. * Removing either the BusID specification or unloading the hyperv_drm kernel module seems to fix the crash. * The crash is happening while X.server is trying to enumerate PCI devices. X.server dereferences a NULL pointer while trying to access to the PCI device info. * The reason why it only happens while the hyperv_drm kernel module is loaded is that the hyperv_drm module does not expose PCI hardware information since it's a virtual device. * The upstream patch [2] addresses the issue and it's confirmed that the xserver with the patch does not experience the crash. * Ubuntu Focal `xorg-server` package does not include the patch [2] at the moment (xserver-xorg-core=2:1.20.13-1ubuntu1~20.04.6). [1]: https://learn.microsoft.com/en-us/azure/virtual-machines/linux/n-series-driver-setup#install-grid-drivers-on-nv-or-nvv3-series-vms [2]: https://github.com/freedesktop/xorg-xserver/commit/0d93bbfa2cfacbb73741f8bed0e32fa1a656b928 [ Test Plan ] Part (a) is quoted from Microsoft's official guide [1]. Part (a): * Spawn a Microsoft Azure NV-series instance with an NVidia GRID-supported GPU - e.g. `NV36adms A10` * Install updates, required tooling, and the desktop environment: - sudo apt-get update - sudo apt-get upgrade -y - sudo apt-get dist-upgrade -y - sudo apt-get install build-essential ubuntu-desktop -y - sudo apt-get install linux-azure -y * Disable nouveau kernel driver: # Create a blacklist file /etc/modprobe.d/nouveau.conf with following contents: blacklist nouveau blacklist lbm-nouveau * Reboot the VM, re-connect, and then stop X server: - sudo reboot # wait for the reboot, reconnect, and continue: - sudo systemctl stop lightdm.service * Download and install the NVidia GRID driver: - wget -O NVIDIA-Linux-x86_64-grid.run https://go.microsoft.com/fwlink/?linkid=874272 - chmod +x NVIDIA-Linux-x86_64-grid.run - sudo ./NVIDIA-Linux-x86_64-grid.run - # When the setup asks whether you want to run the nvidia-xconfig utility to update your X configuration file, select Yes. * Copy /etc/nvidia/gridd.conf.template to /etc/nvidia/gridd.conf - sudo cp /etc/nvidia/gridd.conf.template /etc/nvidia/gridd.conf * Edit /etc/nvidia/grid.conf - sudo nano /etc/nvidia/grid.conf # Append the following lines: IgnoreSP=FALSE EnableUI=FALSE # Remove this line if present: FeatureType=0 # And save. * Reboot the VM Part (b): * Ensure that the hyperv_drm kernel module is loaded: - sudo modprobe hyperv_drm * Use the attached xorg.conf file to override /etc/X11/xorg.conf file * try to start the `xserver`: - sudo startx * `xserver` should crash with a similar output to the following: X.Org X Server 1.20.13 X Protocol Version 11, Revision 0 Build Operating System: linux Ubuntu Current Operating System: Linux a10test 5.15.0-1031-azure #38~20.04.1-Ubuntu SMP Mon Jan 9 18:23:48 UTC 2023 x86_64 Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.15.0-1031-azure root=PARTUUID=4cac852b-afba-447b-b3e7-c002155c1305 ro console=tty1 console=ttyS0 earlyprintk=ttyS0 panic=-1 Build Date: 07 February 2023 12:48:13PM xorg-server 2:1.20.13-1ubuntu1~20.04.6 (For technical support please see http://www.ubuntu.com/support) Current version of pixman: 0.38.4 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.1.log", Time: Sat Feb 18 10:54:26 2023 (==) Using config file: "/etc/X11/xorg.conf" (==) Using system config directory "/usr/share/X11/xorg.conf.d" (EE) (EE) Backtrace: (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x55e7787c5ecc] (EE)
[Desktop-packages] [Bug 2007746] [NEW] [SRU] xserver crashes when hyperv_drm kernel module is loaded on azure NV series instances w/ nvidia grid driver
address 0x124 (EE) Fatal server error: (EE) Caught signal 11 (Segmentation fault). Server aborting (EE) (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. (EE) Please also check the log file at "/var/log/Xorg.1.log" for additional information. (EE) (EE) Server terminated with error (1). Closing log file. ^Cxinit: giving up xinit: unable to connect to X server: Connection refused xinit: unexpected signal 2 [ Where problems could occur ] * The regression risk is low, given that the patch is well-isolated and basically adds a null check that is already assumed to be there in the first place. [ Other Info ] * workaround #1: unload hyperv_drm kernel module: - sudo modprobe -r hyperv_drm * workaround #2: Comment out BusID line in /etc/X11/xorg.conf [Device] section: Section "Device" Identifier "Device0" Driver "nvidia" VendorName "NVIDIA Corporation" # BusID "PCI:0@32828:0:0" Option "HardDPMS" "false" Option "CustomEDID" "DFP-0:/etc/X11/vdisplay.edid" EndSection ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Affects: xorg-server (Ubuntu Focal) Importance: Undecided Assignee: Mustafa Kemal Gilor (mustafakemalgilor) Status: In Progress ** Attachment added: "xorg.conf" https://bugs.launchpad.net/bugs/2007746/+attachment/5648222/+files/xorg.conf ** Also affects: xorg-server (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: xorg-server (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: xorg-server (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: xorg-server (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: xorg-server (Ubuntu Bionic) Importance: Undecided Status: New ** No longer affects: xorg-server (Ubuntu Bionic) ** No longer affects: xorg-server (Ubuntu Jammy) ** No longer affects: xorg-server (Ubuntu Kinetic) ** No longer affects: xorg-server (Ubuntu Lunar) ** Changed in: xorg-server (Ubuntu Focal) Status: New => In Progress ** Changed in: xorg-server (Ubuntu Focal) Assignee: (unassigned) => Mustafa Kemal Gilor (mustafakemalgilor) -- 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/2007746 Title: [SRU] xserver crashes when hyperv_drm kernel module is loaded on azure NV series instances w/ nvidia grid driver Status in xorg-server package in Ubuntu: New Status in xorg-server source package in Focal: In Progress Bug description: [ Impact ] * Microsoft Azure NV-series instances with NVidia GRID drivers started to experience xserver crashes while following Microsoft's official guide to installing Nvidia drivers [1]. * Root cause analysis showed that it was due to having a device with BusID "PCI:0@:0:0", where domain id is >= 32767 while the hyperv_drm kernel module is loaded. * Removing either the BusID specification or unloading the hyperv_drm kernel module seems to fix the crash. * The crash is happening while X.server is trying to enumerate PCI devices. X.server dereferences a NULL pointer while trying to access to the PCI device info. * The reason why it only happens while the hyperv_drm kernel module is loaded is that the hyperv_drm module does not expose PCI hardware information since it's a virtual device. * The upstream patch [2] addresses the issue and it's confirmed that the xserver with the patch does not experience the crash. * Ubuntu Focal `xorg-server` package does not include the patch [2] at the moment (xserver-xorg-core=2:1.20.13-1ubuntu1~20.04.6). [1]: https://learn.microsoft.com/en-us/azure/virtual-machines/linux/n-series-driver-setup#install-grid-drivers-on-nv-or-nvv3-series-vms [2]: https://github.com/freedesktop/xorg-xserver/commit/0d93bbfa2cfacbb73741f8bed0e32fa1a656b928 [ Test Plan ] Part (a) is quoted from Microsoft's official guide [1]. Part (a): * Spawn a Microsoft Azure NV-series instance with an NVidia GRID-supported GPU - e.g. `NV36adms A10` * Install updates, required tooling, and the desktop environment: - sudo apt-get update - sudo apt-get upgrade -y - sudo apt-get dist-upgrade -y - sudo apt-get install build-essential ubuntu-desktop -y - sudo apt-get install linux-azure -y * Disable nouveau kernel driver: # Create a blacklist file /etc/modprobe.d/nouveau.conf with following contents: blacklist nouveau blacklist lbm-nouveau * Reboot the VM, re-connect, and then stop X server: - sudo reboot # wait for the reboot, reconnect, and continu
[Desktop-packages] [Bug 2003176] Re: SRU: metacity crashes while minimizing a windows that has undocked child
Verification is done for Focal and Jammy, I've run the test case 3 times for both, and experienced no crashes while minimizing a parent window with undocked child. Also, the window is restored properly when un- minimized. ** Attachment added: "Screenshot from 2023-02-13 13-45-20.png" https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/2003176/+attachment/5646788/+files/Screenshot%20from%202023-02-13%2013-45-20.png ** Tags removed: verification-needed verification-needed-focal verification-needed-jammy ** Tags added: verification-done-focal verification-done-jammy -- 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/2003176 Title: SRU: metacity crashes while minimizing a windows that has undocked child Status in metacity package in Ubuntu: New Status in metacity source package in Focal: Fix Committed Status in metacity source package in Jammy: Fix Committed Bug description: [General information about the SRU] * It includes the fix for the bug https://gitlab.gnome.org/GNOME/metacity/-/issues/31 * The fix is already included in 3.46.0 release: https://gitlab.gnome.org/GNOME/metacity/-/commit/77f1d55479bfef479f76011a1ee5636f9bf6b08b#9f621eb5fd3bcb2fa5c7bd228c9b1ad42edc46c8 * The reproducer also revealed another issue with docked windows, undocked windows are not being restored after parent window is minimized and restored * The fix for restore is included in 3.46.1 release: https://gitlab.gnome.org/GNOME/metacity/-/commit/3db07fafa1c7ff9749b6a82ccb36d8b62f2304d9 * Focal(3.36.1) and Jammy (3.44.0) needs both fixes to be backported [Impact] This affects users using applications that have docked windows [Test Case] * Install gnome-session-flashback (metacity) and reproducer's dependencies `sudo apt install lightdm gnome-session-flashback pyside2-tools python3-pyside2.qtwidgets` * Start a graphical session with metacity * run python3 Untitled.py * Undock one of the application's child windows * Minimize main window * Result: Metacity will crash * Fix: install fix from ppa: * sudo add-apt-repository ppa:mustafakemalgilor/lp-2003176-0 * sudo apt update * sudo reboot # or alternatively, restart display manager * run python3 Untitled.py * Undock one of the application's child windows * Minimize main window * Expectation: it should not crash and the application should be minimized. [Regression Potential] The fix is small in size and localized, it should not cause any regressions. - Bug Version: 1:3.36.1-1 / 1:3.44.0-1 Metacity is running without the composite manager. Users cannot minimize an application with an undocked child window ProblemType: Bug DistroRelease: Ubuntu 20.04 / Ubuntu 22.04 Package: metacity 1:3.36.1-1 / 1:3.44.0-1 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/2003176/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2003176] Re: SRU: metacity crashes while minimizing a windows that has undocked child
** Changed in: metacity (Ubuntu Jammy) Status: New => In Progress -- 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/2003176 Title: SRU: metacity crashes while minimizing a windows that has undocked child Status in metacity package in Ubuntu: New Status in metacity source package in Focal: In Progress Status in metacity source package in Jammy: In Progress Bug description: [General information about the SRU] * It includes the fix for the bug https://gitlab.gnome.org/GNOME/metacity/-/issues/31 * The fix is already included in 3.46.0 release: https://gitlab.gnome.org/GNOME/metacity/-/commit/77f1d55479bfef479f76011a1ee5636f9bf6b08b#9f621eb5fd3bcb2fa5c7bd228c9b1ad42edc46c8 * The reproducer also revealed another issue with docked windows, undocked windows are not being restored after parent window is minimized and restored * The fix for restore is included in 3.46.1 release: https://gitlab.gnome.org/GNOME/metacity/-/commit/3db07fafa1c7ff9749b6a82ccb36d8b62f2304d9 * Focal(3.36.1) and Jammy (3.44.0) needs both fixes to be backported [Impact] This affects users using applications that have docked windows [Test Case] * Install gnome-session-flashback (metacity) and reproducer's dependencies `sudo apt install lightdm gnome-session-flashback pyside2-tools python3-pyside2.qtwidgets` * Start a graphical session with metacity * run python3 Untitled.py * Undock one of the application's child windows * Minimize main window * Result: Metacity will crash * Fix: install fix from ppa: * sudo add-apt-repository ppa:mustafakemalgilor/lp-2003176-0 * sudo apt update * sudo reboot # or alternatively, restart display manager * run python3 Untitled.py * Undock one of the application's child windows * Minimize main window * Expectation: it should not crash and the application should be minimized. [Regression Potential] The fix is small in size and localized, it should not cause any regressions. - Bug Version: 1:3.36.1-1 / 1:3.44.0-1 Metacity is running without the composite manager. Users cannot minimize an application with an undocked child window ProblemType: Bug DistroRelease: Ubuntu 20.04 / Ubuntu 22.04 Package: metacity 1:3.36.1-1 / 1:3.44.0-1 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/2003176/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2003176] Re: SRU: metacity crashes while minimizing a windows that has undocked child
** Merge proposal unlinked: https://code.launchpad.net/~mustafakemalgilor/ubuntu/+source/metacity/+git/metacity/+merge/435956 -- 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/2003176 Title: SRU: metacity crashes while minimizing a windows that has undocked child Status in metacity package in Ubuntu: New Status in metacity source package in Focal: In Progress Status in metacity source package in Jammy: New Bug description: [General information about the SRU] * It includes the fix for the bug https://gitlab.gnome.org/GNOME/metacity/-/issues/31 * The fix is already included in 3.46.0 release: https://gitlab.gnome.org/GNOME/metacity/-/commit/77f1d55479bfef479f76011a1ee5636f9bf6b08b#9f621eb5fd3bcb2fa5c7bd228c9b1ad42edc46c8 * The reproducer also revealed another issue with docked windows, undocked windows are not being restored after parent window is minimized and restored * The fix for restore is included in 3.46.1 release: https://gitlab.gnome.org/GNOME/metacity/-/commit/3db07fafa1c7ff9749b6a82ccb36d8b62f2304d9 * Focal(3.36.1) and Jammy (3.44.0) needs both fixes to be backported [Impact] This affects users using applications that have docked windows [Test Case] * Install gnome-session-flashback (metacity) and reproducer's dependencies `sudo apt install lightdm gnome-session-flashback pyside2-tools python3-pyside2.qtwidgets` * Start a graphical session with metacity * run python3 Untitled.py * Undock one of the application's child windows * Minimize main window * Result: Metacity will crash * Fix: install fix from ppa: * sudo add-apt-repository ppa:mustafakemalgilor/lp-2003176-0 * sudo apt update * sudo reboot # or alternatively, restart display manager * run python3 Untitled.py * Undock one of the application's child windows * Minimize main window * Expectation: it should not crash and the application should be minimized. [Regression Potential] The fix is small in size and localized, it should not cause any regressions. - Bug Version: 1:3.36.1-1 / 1:3.44.0-1 Metacity is running without the composite manager. Users cannot minimize an application with an undocked child window ProblemType: Bug DistroRelease: Ubuntu 20.04 / Ubuntu 22.04 Package: metacity 1:3.36.1-1 / 1:3.44.0-1 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/2003176/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2003176] Re: SRU: metacity crashes while minimizing a windows that has undocked child
** Changed in: metacity (Ubuntu Focal) Status: New => In Progress -- 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/2003176 Title: SRU: metacity crashes while minimizing a windows that has undocked child Status in metacity package in Ubuntu: New Status in metacity source package in Focal: In Progress Status in metacity source package in Jammy: New Bug description: [General information about the SRU] * It includes the fix for the bug https://gitlab.gnome.org/GNOME/metacity/-/issues/31 * The fix is already included in 3.46.0 release: https://gitlab.gnome.org/GNOME/metacity/-/commit/77f1d55479bfef479f76011a1ee5636f9bf6b08b#9f621eb5fd3bcb2fa5c7bd228c9b1ad42edc46c8 * The reproducer also revealed another issue with docked windows, undocked windows are not being restored after parent window is minimized and restored * The fix for restore is included in 3.46.1 release: https://gitlab.gnome.org/GNOME/metacity/-/commit/3db07fafa1c7ff9749b6a82ccb36d8b62f2304d9 * Focal(3.36.1) and Jammy (3.44.0) needs both fixes to be backported [Impact] This affects users using applications that have docked windows [Test Case] * Install gnome-session-flashback (metacity) and reproducer's dependencies `sudo apt install lightdm gnome-session-flashback pyside2-tools python3-pyside2.qtwidgets` * Start a graphical session with metacity * run python3 Untitled.py * Undock one of the application's child windows * Minimize main window * Result: Metacity will crash * Fix: install fix from ppa: * sudo add-apt-repository ppa:mustafakemalgilor/lp-2003176-0 * sudo apt update * sudo reboot # or alternatively, restart display manager * run python3 Untitled.py * Undock one of the application's child windows * Minimize main window * Expectation: it should not crash and the application should be minimized. [Regression Potential] The fix is small in size and localized, it should not cause any regressions. - Bug Version: 1:3.36.1-1 / 1:3.44.0-1 Metacity is running without the composite manager. Users cannot minimize an application with an undocked child window ProblemType: Bug DistroRelease: Ubuntu 20.04 / Ubuntu 22.04 Package: metacity 1:3.36.1-1 / 1:3.44.0-1 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/2003176/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2003176] Re: SRU: metacity crashes while minimizing a windows that has undocked child
** Description changed: [General information about the SRU] * It includes the fix for the bug https://gitlab.gnome.org/GNOME/metacity/-/issues/31 * The fix is already included in 3.46.0 release: https://gitlab.gnome.org/GNOME/metacity/-/commit/77f1d55479bfef479f76011a1ee5636f9bf6b08b#9f621eb5fd3bcb2fa5c7bd228c9b1ad42edc46c8 * The reproducer also revealed another issue with docked windows, undocked windows are not being restored after parent window is minimized and restored * The fix for restore is included in 3.46.1 release: https://gitlab.gnome.org/GNOME/metacity/-/commit/3db07fafa1c7ff9749b6a82ccb36d8b62f2304d9 * Focal(3.36.1) and Jammy (3.44.0) needs both fixes to be backported [Impact] This affects users using applications that have docked windows [Test Case] * Install gnome-session-flashback (metacity) and reproducer's dependencies `sudo apt install lightdm gnome-session-flashback pyside2-tools python3-pyside2.qtwidgets` * Start a graphical session with metacity * run python3 Untitled.py * Undock one of the application's child windows * Minimize main window * Result: Metacity will crash + + * Fix: install fix from ppa: + * sudo add-apt-repository ppa:mustafakemalgilor/lp-2003176-0 + * sudo apt update + * sudo reboot # or alternatively, restart display manager + * run python3 Untitled.py + * Undock one of the application's child windows + * Minimize main window * Expectation: it should not crash and the application should be minimized. [Regression Potential] The fix is small in size and localized, it should not cause any regressions. - Bug Version: 1:3.36.1-1 / 1:3.44.0-1 Metacity is running without the composite manager. Users cannot minimize an application with an undocked child window ProblemType: Bug DistroRelease: Ubuntu 20.04 / Ubuntu 22.04 Package: metacity 1:3.36.1-1 / 1:3.44.0-1 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 -- 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/2003176 Title: SRU: metacity crashes while minimizing a windows that has undocked child Status in metacity package in Ubuntu: New Status in metacity source package in Focal: New Status in metacity source package in Jammy: New Bug description: [General information about the SRU] * It includes the fix for the bug https://gitlab.gnome.org/GNOME/metacity/-/issues/31 * The fix is already included in 3.46.0 release: https://gitlab.gnome.org/GNOME/metacity/-/commit/77f1d55479bfef479f76011a1ee5636f9bf6b08b#9f621eb5fd3bcb2fa5c7bd228c9b1ad42edc46c8 * The reproducer also revealed another issue with docked windows, undocked windows are not being restored after parent window is minimized and restored * The fix for restore is included in 3.46.1 release: https://gitlab.gnome.org/GNOME/metacity/-/commit/3db07fafa1c7ff9749b6a82ccb36d8b62f2304d9 * Focal(3.36.1) and Jammy (3.44.0) needs both fixes to be backported [Impact] This affects users using applications that have docked windows [Test Case] * Install gnome-session-flashback (metacity) and reproducer's dependencies `sudo apt install lightdm gnome-session-flashback pyside2-tools python3-pyside2.qtwidgets` * Start a graphical session with metacity * run python3 Untitled.py * Undock one of the application's child windows * Minimize main window * Result: Metacity will crash * Fix: install fix from ppa: * sudo add-apt-repository ppa:mustafakemalgilor/lp-2003176-0 * sudo apt update * sudo reboot # or alternatively, restart display manager * run python3 Untitled.py * Undock one of the application's child windows * Minimize main window * Expectation: it should not crash and the application should be minimized. [Regression Potential] The fix is small in size and localized, it should not cause any regressions. - Bug Version: 1:3.36.1-1 / 1:3.44.0-1 Metacity is running without the composite manager. Users cannot minimize an application with an undocked child window ProblemType: Bug DistroRelease: Ubuntu 20.04 / Ubuntu 22.04 Package: metacity 1:3.36.1-1 / 1:3.44.0-1 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/2003176/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2003176] Re: SRU: metacity crashes while minimizing a windows that has undocked child
** Description changed: [General information about the SRU] * It includes the fix for the bug https://gitlab.gnome.org/GNOME/metacity/-/issues/31 - * The fix is already included in 3.46.0 version: https://gitlab.gnome.org/GNOME/metacity/-/commit/77f1d55479bfef479f76011a1ee5636f9bf6b08b#9f621eb5fd3bcb2fa5c7bd228c9b1ad42edc46c8 - * Focal(3.36.1) and Jammy (3.44.0) needs the fix to be backported + * The fix is already included in 3.46.0 release: https://gitlab.gnome.org/GNOME/metacity/-/commit/77f1d55479bfef479f76011a1ee5636f9bf6b08b#9f621eb5fd3bcb2fa5c7bd228c9b1ad42edc46c8 + * The reproducer also revealed another issue with docked windows, undocked windows are not being restored after parent window is minimized and restored + * The fix for restore is included in 3.46.1 release: https://gitlab.gnome.org/GNOME/metacity/-/commit/3db07fafa1c7ff9749b6a82ccb36d8b62f2304d9 + * Focal(3.36.1) and Jammy (3.44.0) needs both fixes to be backported [Impact] This affects users using applications that have docked windows [Test Case] * Install gnome-session-flashback (metacity) and reproducer's dependencies `sudo apt install lightdm gnome-session-flashback pyside2-tools python3-pyside2.qtwidgets` * Start a graphical session with metacity * run python3 Untitled.py * Undock one of the application's child windows * Minimize main window - * Result: Metacity will crash + * Result: Metacity will crash * Expectation: it should not crash and the application should be minimized. [Regression Potential] The fix is small in size and localized, it should not cause any regressions. - Bug Version: 1:3.36.1-1 / 1:3.44.0-1 Metacity is running without the composite manager. Users cannot minimize an application with an undocked child window ProblemType: Bug DistroRelease: Ubuntu 20.04 / Ubuntu 22.04 Package: metacity 1:3.36.1-1 / 1:3.44.0-1 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 -- 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/2003176 Title: SRU: metacity crashes while minimizing a windows that has undocked child Status in metacity package in Ubuntu: New Status in metacity source package in Focal: New Status in metacity source package in Jammy: New Bug description: [General information about the SRU] * It includes the fix for the bug https://gitlab.gnome.org/GNOME/metacity/-/issues/31 * The fix is already included in 3.46.0 release: https://gitlab.gnome.org/GNOME/metacity/-/commit/77f1d55479bfef479f76011a1ee5636f9bf6b08b#9f621eb5fd3bcb2fa5c7bd228c9b1ad42edc46c8 * The reproducer also revealed another issue with docked windows, undocked windows are not being restored after parent window is minimized and restored * The fix for restore is included in 3.46.1 release: https://gitlab.gnome.org/GNOME/metacity/-/commit/3db07fafa1c7ff9749b6a82ccb36d8b62f2304d9 * Focal(3.36.1) and Jammy (3.44.0) needs both fixes to be backported [Impact] This affects users using applications that have docked windows [Test Case] * Install gnome-session-flashback (metacity) and reproducer's dependencies `sudo apt install lightdm gnome-session-flashback pyside2-tools python3-pyside2.qtwidgets` * Start a graphical session with metacity * run python3 Untitled.py * Undock one of the application's child windows * Minimize main window * Result: Metacity will crash * Expectation: it should not crash and the application should be minimized. [Regression Potential] The fix is small in size and localized, it should not cause any regressions. - Bug Version: 1:3.36.1-1 / 1:3.44.0-1 Metacity is running without the composite manager. Users cannot minimize an application with an undocked child window ProblemType: Bug DistroRelease: Ubuntu 20.04 / Ubuntu 22.04 Package: metacity 1:3.36.1-1 / 1:3.44.0-1 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/2003176/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2003176] Re: SRU: metacity crashes while minimizing a windows that has undocked child
Reproducer script: ** Attachment added: "Untitled.py" https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/2003176/+attachment/5642194/+files/Untitled.py -- 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/2003176 Title: SRU: metacity crashes while minimizing a windows that has undocked child Status in metacity package in Ubuntu: New Status in metacity source package in Focal: New Status in metacity source package in Jammy: New Bug description: [General information about the SRU] * It includes the fix for the bug https://gitlab.gnome.org/GNOME/metacity/-/issues/31 * The fix is already included in 3.46.0 release: https://gitlab.gnome.org/GNOME/metacity/-/commit/77f1d55479bfef479f76011a1ee5636f9bf6b08b#9f621eb5fd3bcb2fa5c7bd228c9b1ad42edc46c8 * The reproducer also revealed another issue with docked windows, undocked windows are not being restored after parent window is minimized and restored * The fix for restore is included in 3.46.1 release: https://gitlab.gnome.org/GNOME/metacity/-/commit/3db07fafa1c7ff9749b6a82ccb36d8b62f2304d9 * Focal(3.36.1) and Jammy (3.44.0) needs both fixes to be backported [Impact] This affects users using applications that have docked windows [Test Case] * Install gnome-session-flashback (metacity) and reproducer's dependencies `sudo apt install lightdm gnome-session-flashback pyside2-tools python3-pyside2.qtwidgets` * Start a graphical session with metacity * run python3 Untitled.py * Undock one of the application's child windows * Minimize main window * Result: Metacity will crash * Expectation: it should not crash and the application should be minimized. [Regression Potential] The fix is small in size and localized, it should not cause any regressions. - Bug Version: 1:3.36.1-1 / 1:3.44.0-1 Metacity is running without the composite manager. Users cannot minimize an application with an undocked child window ProblemType: Bug DistroRelease: Ubuntu 20.04 / Ubuntu 22.04 Package: metacity 1:3.36.1-1 / 1:3.44.0-1 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/2003176/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2003176] [NEW] SRU: metacity crashes while minimizing a windows that has undocked child
Public bug reported: [General information about the SRU] * It includes the fix for the bug https://gitlab.gnome.org/GNOME/metacity/-/issues/31 * The fix is already included in 3.46.0 release: https://gitlab.gnome.org/GNOME/metacity/-/commit/77f1d55479bfef479f76011a1ee5636f9bf6b08b#9f621eb5fd3bcb2fa5c7bd228c9b1ad42edc46c8 * The reproducer also revealed another issue with docked windows, undocked windows are not being restored after parent window is minimized and restored * The fix for restore is included in 3.46.1 release: https://gitlab.gnome.org/GNOME/metacity/-/commit/3db07fafa1c7ff9749b6a82ccb36d8b62f2304d9 * Focal(3.36.1) and Jammy (3.44.0) needs both fixes to be backported [Impact] This affects users using applications that have docked windows [Test Case] * Install gnome-session-flashback (metacity) and reproducer's dependencies `sudo apt install lightdm gnome-session-flashback pyside2-tools python3-pyside2.qtwidgets` * Start a graphical session with metacity * run python3 Untitled.py * Undock one of the application's child windows * Minimize main window * Result: Metacity will crash * Expectation: it should not crash and the application should be minimized. [Regression Potential] The fix is small in size and localized, it should not cause any regressions. - Bug Version: 1:3.36.1-1 / 1:3.44.0-1 Metacity is running without the composite manager. Users cannot minimize an application with an undocked child window ProblemType: Bug DistroRelease: Ubuntu 20.04 / Ubuntu 22.04 Package: metacity 1:3.36.1-1 / 1:3.44.0-1 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 ** Affects: metacity (Ubuntu) Importance: Undecided Status: New ** Affects: metacity (Ubuntu Focal) Importance: Undecided Assignee: Mustafa Kemal Gilor (mustafakemalgilor) Status: New ** Affects: metacity (Ubuntu Jammy) Importance: Undecided Assignee: Mustafa Kemal Gilor (mustafakemalgilor) Status: New ** Also affects: metacity (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: metacity (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: metacity (Ubuntu Focal) Assignee: (unassigned) => Mustafa Kemal Gilor (mustafakemalgilor) ** Changed in: metacity (Ubuntu Jammy) Assignee: (unassigned) => Mustafa Kemal Gilor (mustafakemalgilor) -- 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/2003176 Title: SRU: metacity crashes while minimizing a windows that has undocked child Status in metacity package in Ubuntu: New Status in metacity source package in Focal: New Status in metacity source package in Jammy: New Bug description: [General information about the SRU] * It includes the fix for the bug https://gitlab.gnome.org/GNOME/metacity/-/issues/31 * The fix is already included in 3.46.0 release: https://gitlab.gnome.org/GNOME/metacity/-/commit/77f1d55479bfef479f76011a1ee5636f9bf6b08b#9f621eb5fd3bcb2fa5c7bd228c9b1ad42edc46c8 * The reproducer also revealed another issue with docked windows, undocked windows are not being restored after parent window is minimized and restored * The fix for restore is included in 3.46.1 release: https://gitlab.gnome.org/GNOME/metacity/-/commit/3db07fafa1c7ff9749b6a82ccb36d8b62f2304d9 * Focal(3.36.1) and Jammy (3.44.0) needs both fixes to be backported [Impact] This affects users using applications that have docked windows [Test Case] * Install gnome-session-flashback (metacity) and reproducer's dependencies `sudo apt install lightdm gnome-session-flashback pyside2-tools python3-pyside2.qtwidgets` * Start a graphical session with metacity * run python3 Untitled.py * Undock one of the application's child windows * Minimize main window * Result: Metacity will crash * Expectation: it should not crash and the application should be minimized. [Regression Potential] The fix is small in size and localized, it should not cause any regressions. - Bug Version: 1:3.36.1-1 / 1:3.44.0-1 Metacity is running without the composite manager. Users cannot minimize an application with an undocked child window ProblemType: Bug DistroRelease: Ubuntu 20.04 / Ubuntu 22.04 Package: metacity 1:3.36.1-1 / 1:3.44.0-1 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/2003176/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-pa
[Desktop-packages] [Bug 1254628] Re: update-notifier crashed with SIGSEGV in rate_limiter_free()
I got this in 21.04 (hirsute) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1254628 Title: update-notifier crashed with SIGSEGV in rate_limiter_free() Status in GLib: Fix Released Status in glib2.0 package in Ubuntu: Confirmed Bug description: 1) patben@esp-patben-amd:~$ lsb_release -rd Description: Ubuntu 13.10 Release: 13.10 2) patben@esp-patben-amd:~$ apt-cache policy update-notifier update-notifier: Zainstalowana: 0.147.1 Kandydująca: 0.147.1 Tabela wersji: *** 0.147.1 0 500 http://archive.ubuntu.com/ubuntu/ saucy-proposed/main amd64 Packages 100 /var/lib/dpkg/status 0.147 0 500 http://archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: update-notifier 0.147.1 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Uname: Linux 3.11.0-14-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Mon Nov 25 07:54:33 2013 ExecutablePath: /usr/bin/update-notifier InstallationDate: Installed on 2013-05-28 (180 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True ProcCmdline: update-notifier SegvAnalysis: Segfault happened at: 0x7fbf4f501ae4:mov(%rdi),%rdi PC (0x7fbf4f501ae4) ok source "(%rdi)" (0x) not located in a known VMA region (needed readable region)! destination "%rdi" ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: update-notifier StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 g_file_monitor_emit_event () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: update-notifier crashed with SIGSEGV in g_file_monitor_emit_event() UpgradeStatus: Upgraded to saucy on 2013-10-30 (25 days ago) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1254628/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1829651] Re: Caps Lock status notifications
hi Sebastien, i posted issue in there as you suggested me: https://gitlab.gnome.org/GNOME/gnome-shell/issues/1306 but it is annoying that there is no default "Caps Lock" notification/indicator on screen. dont you think so? some laptops or keyboards dont have led indicator physically like mine. and 3rd party apps for caps lock really dont suit with default notifications. thanks. ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #1306 https://gitlab.gnome.org/GNOME/gnome-shell/issues/1306 -- 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/1829651 Title: Caps Lock status notifications Status in gnome-shell package in Ubuntu: New Bug description: this is suggestion more than a bug report. ubuntu has default cool on screen indicators for volume control, display brightness ..ie. but there is no Caps Lock on screen indicator by default. i am currently using Lenovo ThinkPad X230 and unfortunately there is no led indicator light on the keyboard for caps lock. could you please consider putting caps lock on screen indicator by default to ubuntu? it would be cool if you could. thanks. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-05-14 (4 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Package: gnome-shell 3.28.3+git20190124-0ubuntu18.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20 Tags: bionic Uname: Linux 4.18.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1829651/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1829651] Re: Caps Lock indicator on screen
@Sebastien Bacher, another screenshot of "Volume mute" attached. Caps Lock indicator also should be "on screen" looks like other indicators. not on top bar or anywhere else. for example when Caps Lock is on bright white A logo in the box, and when Caps Lock is off gray crossed A looks like the volume mute indicator in the box. you can add settings like to do it permanent on screen when Caps Lock is ON and temporary when it is OFF or both can be visible permanent on screen. those can be optional in my suggestion. as a suggestion maybe you can put Num Lock and Scroll Lock indicators as well. thank you all in advance for your hard works and contributions to make Ubuntu the best. ** Attachment added: "Volume mute indicator" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1829651/+attachment/5265129/+files/Screenshot%20from%202019-05-20%2023-32-51.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1829651 Title: Caps Lock indicator on screen Status in gnome-shell package in Ubuntu: Incomplete Bug description: this is suggestion more than a bug report. ubuntu has default cool on screen indicators for volume control, display brightness ..ie. but there is no Caps Lock on screen indicator by default. i am currently using Lenovo ThinkPad X230 and unfortunately there is no led indicator light on the keyboard for caps lock. could you please consider putting caps lock on screen indicator by default to ubuntu? it would be cool if you could. thanks. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-05-14 (4 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Package: gnome-shell 3.28.3+git20190124-0ubuntu18.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20 Tags: bionic Uname: Linux 4.18.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1829651/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1829651] Re: Caps Lock indicator on screen
Hi. i am expecting a Caps Lock indicator by default (without need of usage any 3rd party app which are not working proper tested few) like the screenshot of Volume indicator as an example i attached. thanks. ** Attachment added: "example - Volume indicator on screen" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1829651/+attachment/5265128/+files/Screenshot%20from%202019-05-20%2023-32-46.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1829651 Title: Caps Lock indicator on screen Status in gnome-shell package in Ubuntu: Incomplete Bug description: this is suggestion more than a bug report. ubuntu has default cool on screen indicators for volume control, display brightness ..ie. but there is no Caps Lock on screen indicator by default. i am currently using Lenovo ThinkPad X230 and unfortunately there is no led indicator light on the keyboard for caps lock. could you please consider putting caps lock on screen indicator by default to ubuntu? it would be cool if you could. thanks. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-05-14 (4 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Package: gnome-shell 3.28.3+git20190124-0ubuntu18.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20 Tags: bionic Uname: Linux 4.18.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1829651/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1734887] Re: No caps lock indicator on login screen
i am currently using Lenovo ThinkPad x230 which doesnt have physical caps lock indicator on keyboard like some other ThinkPad laptops. i noticed that on Ubuntu 18.04.2 there is no Caps Lock indicator on screen. it would be perfect if you put it default as other on screen indicators such as volume controls, microphone indicator, screen brightness indicator. thanks. -- 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/1734887 Title: No caps lock indicator on login screen Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: Triaged Status in gnome-shell source package in Cosmic: Triaged Status in gnome-shell source package in Disco: Fix Released Status in gnome-shell source package in Eoan: Fix Released Bug description: Expected results: Pressing the Caps Lock key should cause an indicator to appear on the login screen. Actual results: Pressing the Caps Lock key does not cause the login screen to change in any way. Reproducing: 1. Install Ubuntu 17.10 Desktop ISO and log in, press Caps Lock key, see no indicator. (gdm3 3.26.1-3ubuntu3) 2. Install Fedora 27 Workstation ISO and log in, press Caps Lock key, see an indicator. (gdm-3.26.2.1-1.fc27.x86_64) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gdm3 3.26.1-3ubuntu3 Uname: Linux 4.14.2-041402-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Tue Nov 28 08:24:31 2017 InstallationDate: Installed on 2017-11-05 (22 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Release amd64 (20171017.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1734887/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1829651] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1829651/+attachment/5264768/+files/ProcEnviron.txt -- 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/1829651 Title: Caps Lock indicator on screen Status in gnome-shell package in Ubuntu: New Bug description: this is suggestion more than a bug report. ubuntu has default cool on screen indicators for volume control, display brightness ..ie. but there is no Caps Lock on screen indicator by default. i am currently using Lenovo ThinkPad X230 and unfortunately there is no led indicator light on the keyboard for caps lock. could you please consider putting caps lock on screen indicator by default to ubuntu? it would be cool if you could. thanks. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-05-14 (4 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Package: gnome-shell 3.28.3+git20190124-0ubuntu18.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20 Tags: bionic Uname: Linux 4.18.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1829651/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1829651] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1829651/+attachment/5264767/+files/ProcCpuinfoMinimal.txt -- 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/1829651 Title: Caps Lock indicator on screen Status in gnome-shell package in Ubuntu: New Bug description: this is suggestion more than a bug report. ubuntu has default cool on screen indicators for volume control, display brightness ..ie. but there is no Caps Lock on screen indicator by default. i am currently using Lenovo ThinkPad X230 and unfortunately there is no led indicator light on the keyboard for caps lock. could you please consider putting caps lock on screen indicator by default to ubuntu? it would be cool if you could. thanks. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-05-14 (4 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Package: gnome-shell 3.28.3+git20190124-0ubuntu18.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20 Tags: bionic Uname: Linux 4.18.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1829651/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1829651] GsettingsChanges.txt
apport information ** Attachment added: "GsettingsChanges.txt" https://bugs.launchpad.net/bugs/1829651/+attachment/5264766/+files/GsettingsChanges.txt -- 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/1829651 Title: Caps Lock indicator on screen Status in gnome-shell package in Ubuntu: New Bug description: this is suggestion more than a bug report. ubuntu has default cool on screen indicators for volume control, display brightness ..ie. but there is no Caps Lock on screen indicator by default. i am currently using Lenovo ThinkPad X230 and unfortunately there is no led indicator light on the keyboard for caps lock. could you please consider putting caps lock on screen indicator by default to ubuntu? it would be cool if you could. thanks. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-05-14 (4 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Package: gnome-shell 3.28.3+git20190124-0ubuntu18.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20 Tags: bionic Uname: Linux 4.18.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1829651/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1829651] Re: Caps Lock indicator on screen
apport information ** Package changed: powernap (Ubuntu) => gnome-shell (Ubuntu) ** Tags added: apport-collected bionic ** Description changed: - this is suggestion more than a bug report. ubuntu has default cool on - screen indicators for volume control, display brightness ..ie. but there - is no Caps Lock on screen indicator by default. i am currently using - Lenovo ThinkPad X230 and unfortunately there is no led indicator light - on the keyboard for caps lock. could you please consider putting caps - lock on screen indicator by default to ubuntu? it would be cool if you - could. thanks. + this is suggestion more than a bug report. ubuntu has default cool on screen indicators for volume control, display brightness ..ie. but there is no Caps Lock on screen indicator by default. i am currently using Lenovo ThinkPad X230 and unfortunately there is no led indicator light on the keyboard for caps lock. could you please consider putting caps lock on screen indicator by default to ubuntu? it would be cool if you could. thanks. + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.6 + Architecture: amd64 + CurrentDesktop: ubuntu:GNOME + DisplayManager: gdm3 + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2019-05-14 (4 days ago) + InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) + Package: gnome-shell 3.28.3+git20190124-0ubuntu18.04.2 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20 + Tags: bionic + Uname: Linux 4.18.0-20-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1829651/+attachment/5264765/+files/Dependencies.txt -- 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/1829651 Title: Caps Lock indicator on screen Status in gnome-shell package in Ubuntu: New Bug description: this is suggestion more than a bug report. ubuntu has default cool on screen indicators for volume control, display brightness ..ie. but there is no Caps Lock on screen indicator by default. i am currently using Lenovo ThinkPad X230 and unfortunately there is no led indicator light on the keyboard for caps lock. could you please consider putting caps lock on screen indicator by default to ubuntu? it would be cool if you could. thanks. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-05-14 (4 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Package: gnome-shell 3.28.3+git20190124-0ubuntu18.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20 Tags: bionic Uname: Linux 4.18.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1829651/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1809110] [NEW] Intel drivers
Public bug reported: i wanna see if it helps with setting up vagrant ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None Date: Wed Dec 19 14:33:31 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e12] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Dell 4 Series Chipset Integrated Graphics Controller [1028:027f] Subsystem: Dell 4 Series Chipset Integrated Graphics Controller [1028:027f] InstallationDate: Installed on 2018-01-28 (324 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. OptiPlex 760 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic root=UUID=7dde6342-329e-4620-8e17-2e953c29f852 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/18/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.name: 0M858N dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA02:bd02/18/2009:svnDellInc.:pnOptiPlex760:pvr:rvnDellInc.:rn0M858N:rvrA00:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 760 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic 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/1809110 Title: Intel drivers Status in xorg package in Ubuntu: New Bug description: i wanna see if it helps with setting up vagrant ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None Date: Wed Dec 19 14:33:31 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e12] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Dell 4 Series Chipset Integrated Graphics Controller [1028:027f] Subsystem: Dell 4 Series Chipset Integrated Graphics Controller [1028:027f] InstallationDate: Installed on 2018-01-28 (324 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. OptiPlex 760 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic root=UUID=7dde6342-329e-4620-8e17-2e953c29f852 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/18/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.name: 0M858N dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA02:bd02/18/2009:svnDellInc.:pnOptiPlex760:pvr:rvnDellInc.:rn0M858N:rvrA00:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 760 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to:
[Desktop-packages] [Bug 1751252] Re: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: ''
In the Live Version on MacBook Pro 2015 (13 inches, Retina) I changed
the 'Screen Scale' from 200% to 100%, settings > Device > Display, and
solved!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cairo in Ubuntu.
https://bugs.launchpad.net/bugs/1751252
Title:
[regression] ubiquity crashed in debconf.py:104 with ValueError:
invalid literal for int() with base 10: ''
Status in cairo:
Unknown
Status in OEM Priority Project:
Fix Released
Status in cairo package in Ubuntu:
In Progress
Status in ubiquity package in Ubuntu:
Fix Released
Status in ubiquity source package in Bionic:
Fix Released
Bug description:
* Impact
The Ubuntu installer crashes on some machines (seems more often on hiDPI
machines (QHD/UHD etc)).
* Test case
Try installing Ubuntu on an hidpi machine, it should complete installation
instead of crashing.
* Regression potential
The fix in ubiquity touches the code handle uid drop/privilege, that can have
unexpected side effects so we need proper/complete testing of the installer
--
Update: Actually the crash occurs on slow-ish systems due to a race
condition. It's not strictly only hi-DPI machines - that's just the
most common place it is experienced.
---
https://errors.ubuntu.com/problem/82f7f7e7923663c7b2123c7f1f49af29f6ff4d77
https://errors.ubuntu.com/problem/735a2b847e0eeab6c8a7b954de5110e43889be15
https://errors.ubuntu.com/problem/dcd4c9da5ee0cc6d36324446e0e49d39705c90b7
https://errors.ubuntu.com/problem/cb82f70f9ede07369e8104da9ddf87e28b42257d
https://errors.ubuntu.com/problem/84a5563af3d2b85f098da832ece4cb8450bfd524
---
WORKAROUND:
1. Boot into the live session.
2. Settings > Devices > Displays > Scale = 100%
3. Click Apply.
4. Proceed with installation: Click "Install Ubuntu 18.04 LTS".
---
Crashed in a VM in the middle of installation. The host is Bionic up
to date.
From the journal
Feb 23 12:52:27 ubuntu kernel: traps: ubiquity[2646] trap int3
ip:7f5a76936961 sp:7ffde5090c50 error:0 in
libglib-2.0.so.0.5400.1[7f5a768e6000+111000]
Feb 23 12:52:41 ubuntu /install.py[6858]: Exception during installation:
Feb 23 12:52:41 ubuntu /install.py[6858]: Traceback (most recent call last):
Feb 23 12:52:41 ubuntu /install.py[6858]: File
"/usr/share/ubiquity/install.py", line 757, in
Feb 23 12:52:41 ubuntu /install.py[6858]: install.run()
Feb 23 12:52:41 ubuntu /install.py[6858]: File
"/usr/share/ubiquity/install.py", line 135, in run
Feb 23 12:52:41 ubuntu /install.py[6858]: self.copy_all()
Feb 23 12:52:41 ubuntu /install.py[6858]: File
"/usr/share/ubiquity/install.py", line 505, in copy_all
Feb 23 12:52:41 ubuntu /install.py[6858]: self.db.progress('SET', 10 +
copy_progress)
Feb 23 12:52:41 ubuntu /install.py[6858]: File
"/usr/lib/python3/dist-packages/debconf.py", line 83, in
Feb 23 12:52:41 ubuntu /install.py[6858]: lambda *args, **kw:
self.command(command, *args, **kw))
Feb 23 12:52:41 ubuntu /install.py[6858]: File
"/usr/lib/python3/dist-packages/debconf.py", line 104, in command
Feb 23 12:52:41 ubuntu /install.py[6858]: status = int(status)
Feb 23 12:52:41 ubuntu /install.py[6858]: ValueError: invalid literal for
int() with base 10: ''
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.1
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CasperVersion: 1.388
Date: Fri Feb 23 12:52:28 2018
ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper
initrd=/casper/initrd.lz quiet splash --- keyboard-configuration/layoutcode=fr
keyboard-configuration/variantcode=oss
InterpreterPath: /usr/bin/python3.6
LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222)
ProcCmdline: /usr/bin/python3 /usr/lib/ubiquity/bin/ubiquity -d
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=C.UTF-8
SHELL=/bin/bash
Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
Signal: 5
SourcePackage: ubiquity
StacktraceTop:
?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
_XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6
XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6
?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
Title: ubiquity crashed with signal 5 in _XEventsQueued()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
To manage notifications about this bug go to:
https://bugs.launchpad.net/cairo/+bug/1751252/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe :
[Desktop-packages] [Bug 977228] Re: gnome-screenshot forgets "last-save-directory"
Still present in Ubuntu 16.04. It only remembers last-save-directory when gnome-screenshot is running interactively. But when I press shift + prnt scr shortcut it forgets the last-save-directory. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screenshot in Ubuntu. https://bugs.launchpad.net/bugs/977228 Title: gnome-screenshot forgets "last-save-directory" Status in Gnome Screenshot: Won't Fix Status in gnome-screenshot package in Ubuntu: Confirmed Bug description: Ubuntu 12.04, Beta 2 1) press [PrintScreen] to do a screenshot 2) gnome-screenshot proposes to save it in "$HOME/pictures" 3) change location to "$HOME/videos" or similiar and close gnome-screenshot 4) press [PrintScreen] again and take another screenshot 6) tool wants to save picture in "$HOME/pictures" again 5) expected behaviour: proposes to save pic in "$HOME/videos" BTW: Setting a fixed path in dconf-editor entry "last-save-directory" doesn't change anything. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-screenshot 3.4.0-0ubuntu1 Uname: Linux 3.3.1-030301-generic i686 ApportVersion: 2.0-0ubuntu4 Architecture: i386 Date: Mon Apr 9 15:37:26 2012 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) SourcePackage: gnome-screenshot UpgradeStatus: Upgraded to precise on 2011-11-24 (136 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-screenshot/+bug/977228/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 606365] Re: unable to import config with inlined ca, cert, key or tls-auth
My ubuntu 16.04 has affected but #77 fixed it.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-openvpn in Ubuntu.
https://bugs.launchpad.net/bugs/606365
Title:
unable to import config with inlined ca, cert, key or tls-auth
Status in NetworkManager-OpenVPN:
Fix Released
Status in plasma-nm:
New
Status in network-manager-openvpn package in Ubuntu:
Fix Released
Status in plasma-nm package in Ubuntu:
Fix Released
Bug description:
Binary package hint: network-manager-openvpn-gnome
So a client of mine runs an OpenVPN setup. It exported a client.ovpn
file but it fails to completely import this file using the network-
manager (gnome) on Ubuntu 10.04.
When I import the file, it gives me the name ("client") and gateway
("vpn.example.org") on the initial screen. No other fields are
populated even though the client.ovpn file also includes a user
certificate, server certifikate and a private key.
When I go to advanced, some (most) of the settings obviously seem to
import correct, others not at all. E.g. none of the TLS settings (key
and key direction) are imported.
From what I understand I should be able to use this without any
additional settings.
The following software is installed through aptitude:
* openvpn (2.1.0)
* openvpn-blacklist
* network-manager-openvpn
* network-manager-openvpn-gnome
To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager-openvpn/+bug/606365/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1773575] Re: dual vga
yes it solved my problem thanks alot i could not find such a solution online. you saved my day On Sun, May 27, 2018 at 8:34 AM, Christopher M. Penalver < christopher.m.penal...@gmail.com> wrote: > mustafa: > > 1) Regarding crash files, you would not want to attach them, as they may > contain sensitive information you don't want to reveal publicly. > > Instead, one may report them in a privacy respectful way via a terminal: > ubuntu-bug /var/crash/FILENAME.crash > > where FILENAME is the name of the crash file. > > 2) It is advised to immediately back up your data (config files, list of > what apps you have installed, etc.), so that in the event of a disaster > (hardware failure, OS stops working entirely, etc.) you may perform a > clean install and bring the OS back to the desired state. Stating "i do > not want to lose my server configuration and reinstall Ubuntu and all > the configuration and apps that i used" doesn't mean you won't have to > do it. This is a matter of how prepared are you if you must. > > 3) Post the results of the following terminal command: > history > > 4) To confirm a WORKAROUND, if you install the package gnome-session- > flashback and login to GNOME (Metacity), does this allow you to use the > GUI again? > > ** Attachment removed: "_usr_lib_x86_64-linux-gnu_ > unity_compiz-config-profile-setter.1000_copy.crash" >https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/ > 1773575/+attachment/5145036/+files/_usr_lib_x86_64-linux- > gnu_unity_compiz-config-profile-setter.1000_copy.crash > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1773575 > > Title: > dual vga > > Status in xorg package in Ubuntu: > Incomplete > > Bug description: > i have a laptop dell which has two vga one from intel and the other > one is amd. i tried to update the drivers in one way or another every > thing stoped and i can not use the gui anymore > > ProblemType: Bug > DistroRelease: Ubuntu 16.04 > Package: xorg 1:7.7+13ubuntu3 > ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16 > Uname: Linux 4.13.0-43-generic x86_64 > .tmp.unity_support_test.1: > > ApportVersion: 2.20.1-0ubuntu2.17 > Architecture: amd64 > CompizPlugins: No value set for `/apps/compiz-1/general/ > screen0/options/active_plugins' > CompositorRunning: None > Date: Sat May 26 22:00:13 2018 > DistUpgraded: Fresh install > DistroCodename: xenial > DistroVariant: ubuntu > ExtraDebuggingInterest: Yes, including running git bisection searches > GraphicsCard: >Intel Corporation 3rd Gen Core processor Graphics Controller > [8086:0166] (rev 09) (prog-if 00 [VGA controller]) > Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:05b8] >Advanced Micro Devices, Inc. [AMD/ATI] Mars [Radeon HD 8730M] > [1002:6601] (rev ff) (prog-if ff) > InstallationDate: Installed on 2018-01-10 (136 days ago) > InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 > (20170801) > MachineType: Dell Inc. Inspiron 5521 > ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-43-generic > root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 > SourcePackage: xorg > UpgradeStatus: No upgrade log present (probably fresh install) > Xrandr: Screen 0: minimum 0 x 0, current 3600 x 1080, maximum 4096 x 4096 > dmi.bios.date: 07/31/2015 > dmi.bios.vendor: Dell Inc. > dmi.bios.version: A14 > dmi.board.name: 0C46Y8 > dmi.board.vendor: Dell Inc. > dmi.board.version: A00 > dmi.chassis.type: 8 > dmi.chassis.vendor: Dell Inc. > dmi.chassis.version: A14 > dmi.modalias: dmi:bvnDellInc.:bvrA14:bd07/31/2015:svnDellInc.: > pnInspiron5521:pvrA14:rvnDellInc.:rn0C46Y8:rvrA00:cvnDellInc.:ct8:cvrA14: > dmi.product.family: 103C_5335KV > dmi.product.name: Inspiron 5521 > dmi.product.version: A14 > dmi.sys.vendor: Dell Inc. > version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 > version.ia32-libs: ia32-libs N/A > version.libdrm2: libdrm2 2.4.83-1~16.04.1 > version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 > version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A > version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 > version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7 > 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-x
Re: [Desktop-packages] [Bug 1773575] Re: dual vga
i tried all the possibilities that i found online even to install invidia because they told me that there might help installing some important files. now it doesn't allow me to use the GUI i can use only command line. i tried many ways to restore the original drivers but i could not restore them. in windows there is something called soft system reset which reinstall the system basic files and drivers which i could not find it on ubuntu, because i do not want to lose my server configuration and reinstall Ubuntu and all the configuration and apps that i used. so if there is any future from the command line to restore the drivers or the basic files of the system without damaging my web server it would be helpful please. it might not be a bug but i can see it as bug because i tried to remove the new installed drivers and though i can not use the gui and it gives me error when i try to login with my user and pass. Could you please advise what you did precisely, in a keyboard click-for-click fashion? concerning this question i can not give you an answer because i tried many things and now i can not remember them . i tired to install amd drivers and intel and something from invidia and then tried to remove them all but the gui still give me error when i try to login . in my crash i can find the following / in the attachment/ i could not understand all the things inside the crash file thanks for the great job that you and the team doing and i hope that you can help me to solve this problem. greetings On Sun, May 27, 2018 at 7:20 AM, Christopher M. Penalver < christopher.m.penal...@gmail.com> wrote: > mustafa, thank you for reporting this and helping make Ubuntu better. > > 1) Regarding your Bug Description: > >"i tried to update the drivers in one way or another..." > > This is not enough information. Could you please advise what you did > precisely, in a keyboard click-for-click fashion? > > 2) Are there any crash files in the /var/crash folder? > > 3) As per your logs, you install unsupported software (PPA) and have > installed the nvidia proprietary drivers when you don't have a nvidia > card installed. Hence, after removing all PPAs and the nvidia drivers, > and rebooting does this allow you to use the GUI? > > ** Tags added: latest-bios-a14 > > ** Changed in: xorg (Ubuntu) >Importance: Undecided => Low > > ** Changed in: xorg (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1773575 > > Title: > dual vga > > Status in xorg package in Ubuntu: > Incomplete > > Bug description: > i have a laptop dell which has two vga one from intel and the other > one is amd. i tried to update the drivers in one way or another every > thing stoped and i can not use the gui anymore > > ProblemType: Bug > DistroRelease: Ubuntu 16.04 > Package: xorg 1:7.7+13ubuntu3 > ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16 > Uname: Linux 4.13.0-43-generic x86_64 > .tmp.unity_support_test.1: > > ApportVersion: 2.20.1-0ubuntu2.17 > Architecture: amd64 > CompizPlugins: No value set for `/apps/compiz-1/general/ > screen0/options/active_plugins' > CompositorRunning: None > Date: Sat May 26 22:00:13 2018 > DistUpgraded: Fresh install > DistroCodename: xenial > DistroVariant: ubuntu > ExtraDebuggingInterest: Yes, including running git bisection searches > GraphicsCard: >Intel Corporation 3rd Gen Core processor Graphics Controller > [8086:0166] (rev 09) (prog-if 00 [VGA controller]) > Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:05b8] >Advanced Micro Devices, Inc. [AMD/ATI] Mars [Radeon HD 8730M] > [1002:6601] (rev ff) (prog-if ff) > InstallationDate: Installed on 2018-01-10 (136 days ago) > InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 > (20170801) > MachineType: Dell Inc. Inspiron 5521 > ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-43-generic > root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 > SourcePackage: xorg > UpgradeStatus: No upgrade log present (probably fresh install) > Xrandr: Screen 0: minimum 0 x 0, current 3600 x 1080, maximum 4096 x 4096 > dmi.bios.date: 07/31/2015 > dmi.bios.vendor: Dell Inc. > dmi.bios.version: A14 > dmi.board.name: 0C46Y8 > dmi.board.vendor: Dell Inc. > dmi.board.version: A00 > dmi.chassis.type: 8 > dmi.chassis.vendor: Dell Inc. > dmi.chassis.version: A14 > dmi.modalias: dmi:bvnDellInc.:bvrA14:bd07/31/2015:svnDellInc.: > pnInspiron5521:pvrA14:rvnDellInc.:rn0C46Y8:rvrA00:cvnDellInc.:ct8:cvrA14: > dmi.product.family: 103C_5335KV >
[Desktop-packages] [Bug 1773575] [NEW] dual vga
Public bug reported: i have a laptop dell which has two vga one from intel and the other one is amd. i tried to update the drivers in one way or another every thing stoped and i can not use the gui anymore ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-43-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sat May 26 22:00:13 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:05b8] Advanced Micro Devices, Inc. [AMD/ATI] Mars [Radeon HD 8730M] [1002:6601] (rev ff) (prog-if ff) InstallationDate: Installed on 2018-01-10 (136 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Dell Inc. Inspiron 5521 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-43-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) Xrandr: Screen 0: minimum 0 x 0, current 3600 x 1080, maximum 4096 x 4096 dmi.bios.date: 07/31/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 0C46Y8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A14 dmi.modalias: dmi:bvnDellInc.:bvrA14:bd07/31/2015:svnDellInc.:pnInspiron5521:pvrA14:rvnDellInc.:rn0C46Y8:rvrA00:cvnDellInc.:ct8:cvrA14: dmi.product.family: 103C_5335KV dmi.product.name: Inspiron 5521 dmi.product.version: A14 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7 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 N/A xserver.bootTime: Tue May 22 09:07:33 2018 xserver.configfile: default xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 927 vendor LGD xserver.version: 2:1.18.4-0ubuntu0.7 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug possible-manual-nvidia-install third-party-packages 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/1773575 Title: dual vga Status in xorg package in Ubuntu: New Bug description: i have a laptop dell which has two vga one from intel and the other one is amd. i tried to update the drivers in one way or another every thing stoped and i can not use the gui anymore ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-43-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sat May 26 22:00:13 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:05b8] Advanced Micro Devices, Inc. [AMD/ATI] Mars [Radeon HD 8730M] [1002:6601] (rev ff) (prog-if ff) InstallationDate: Installed on 2018-01-10 (136 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Dell Inc. Inspiron 5521 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-43-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) Xrandr: Screen 0: minimum 0 x 0, current 3600 x 1080, maximum 4096 x 4096 dmi.bios.date:
[Desktop-packages] [Bug 1741675] [NEW] desktop screen
Public bug reported: when i go to launcher the screen keeps resetting ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17 Uname: Linux 4.10.0-28-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CasperVersion: 1.376.2 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sat Jan 6 18:33:24 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.10.0-28-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Dell Mobile GM965/GL960 Integrated Graphics Controller (primary) [1028:022f] Subsystem: Dell Mobile GM965/GL960 Integrated Graphics Controller (secondary) [1028:022f] LiveMediaBuild: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Dell Inc. Inspiron 1525 ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/16/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A16 dmi.board.name: 0CP549 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA16:bd10/16/2008:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn0CP549:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Inspiron 1525 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 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 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/1741675 Title: desktop screen Status in xorg package in Ubuntu: New Bug description: when i go to launcher the screen keeps resetting ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17 Uname: Linux 4.10.0-28-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CasperVersion: 1.376.2 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sat Jan 6 18:33:24 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.10.0-28-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Dell Mobile GM965/GL960 Integrated Graphics Controller (primary) [1028:022f] Subsystem: Dell Mobile GM965/GL960 Integrated Graphics Controller (secondary) [1028:022f] LiveMediaBuild: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Dell Inc. Inspiron 1525 ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/16/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A16 dmi.board.name: 0CP549 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA16:bd10/16/2008:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn0CP549:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Inspiron 1525 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2
[Desktop-packages] [Bug 1738724] [NEW] [iMac15, 1, Cirrus Logic CS4206, Speaker, Internal] No sound at all
Public bug reported: I have iMac 15.1 2014. Sometimes my internal speaker works, sometimes doesn't. When I ran the ubuntu-bug tool, internal speakers worked, however when I use spotify or youtube from different browsers, there are no sound at all. I did remove alsa-lib again and again but no luck. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: said 2018 F pulseaudio /dev/snd/pcmC0D0p: said 2018 F...m pulseaudio /dev/snd/controlC0: said 2018 F pulseaudio CurrentDesktop: GNOME Date: Mon Dec 18 09:42:42 2017 InstallationDate: Installed on 2017-08-01 (138 days ago) InstallationMedia: Ubuntu-GNOME 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [iMac15,1, Cirrus Logic CS4206, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/22/2016 dmi.bios.vendor: Apple Inc. dmi.bios.version: IM151.88Z.0207.B06.1602221600 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-FA842E06C61E91C5 dmi.board.vendor: Apple Inc. dmi.board.version: iMac15,1 dmi.chassis.type: 13 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-FA842E06C61E91C5 dmi.modalias: dmi:bvnAppleInc.:bvrIM151.88Z.0207.B06.1602221600:bd02/22/2016:svnAppleInc.:pniMac15,1:pvr1.0:rvnAppleInc.:rnMac-FA842E06C61E91C5:rvriMac15,1:cvnAppleInc.:ct13:cvrMac-FA842E06C61E91C5: dmi.product.name: iMac15,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2017-10-24T17:32:41.504894 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1738724 Title: [iMac15,1, Cirrus Logic CS4206, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: I have iMac 15.1 2014. Sometimes my internal speaker works, sometimes doesn't. When I ran the ubuntu-bug tool, internal speakers worked, however when I use spotify or youtube from different browsers, there are no sound at all. I did remove alsa-lib again and again but no luck. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: said 2018 F pulseaudio /dev/snd/pcmC0D0p: said 2018 F...m pulseaudio /dev/snd/controlC0: said 2018 F pulseaudio CurrentDesktop: GNOME Date: Mon Dec 18 09:42:42 2017 InstallationDate: Installed on 2017-08-01 (138 days ago) InstallationMedia: Ubuntu-GNOME 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [iMac15,1, Cirrus Logic CS4206, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/22/2016 dmi.bios.vendor: Apple Inc. dmi.bios.version: IM151.88Z.0207.B06.1602221600 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-FA842E06C61E91C5 dmi.board.vendor: Apple Inc. dmi.board.version: iMac15,1 dmi.chassis.type: 13 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-FA842E06C61E91C5 dmi.modalias: dmi:bvnAppleInc.:bvrIM151.88Z.0207.B06.1602221600:bd02/22/2016:svnAppleInc.:pniMac15,1:pvr1.0:rvnAppleInc.:rnMac-FA842E06C61E91C5:rvriMac15,1:cvnAppleInc.:ct13:cvrMac-FA842E06C61E91C5: dmi.product.name: iMac15,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2017-10-24T17:32:41.504894 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1738724/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1446689] Re: network-manager configured to use /usr/sbin/pppoe but does not recommend pppoe
Could you increase the priority of this bug, maybe even mark it as blocker, its effect is bad and it is easy to fix, just a build flag or added dependency. -- 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/1446689 Title: network-manager configured to use /usr/sbin/pppoe but does not recommend pppoe Status in network-manager package in Ubuntu: Confirmed Status in network-manager package in Debian: New Bug description: networkmanager switched from using ppp to using pppoe binary for dsl/pppoe connections, I am using pppoe and I can't connect to the Internet unless I install "pppoe" package. From: http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?h=nm-0-9-10=7955806a02db64b20079267743056d7d9d45af3b "for now, work around this by using the userland pppoe client rather than the kernel code" One way to fix it is to include pppoe Another way is to configure --with-pppoe=/usr/sbin/pppd. I think this is urgent as pppoe/dsl on all vivid machines will be broken out-of-the-box. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1446689/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1446689] Re: network-manager configured to use /usr/sbin/pppoe but does not recommend pppoe
This still exist in Wily Werewolf beta 1, this is important and the release is approaching. -- 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/1446689 Title: network-manager configured to use /usr/sbin/pppoe but does not recommend pppoe Status in network-manager package in Ubuntu: Confirmed Status in network-manager package in Debian: New Bug description: networkmanager switched from using ppp to using pppoe binary for dsl/pppoe connections, I am using pppoe and I can't connect to the Internet unless I install "pppoe" package. From: http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?h=nm-0-9-10=7955806a02db64b20079267743056d7d9d45af3b "for now, work around this by using the userland pppoe client rather than the kernel code" One way to fix it is to include pppoe Another way is to configure --with-pppoe=/usr/sbin/pppd. I think this is urgent as pppoe/dsl on all vivid machines will be broken out-of-the-box. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1446689/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1365695] Re: No longer able to use GUI after update
exakt_cl...@hotmail.com -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331-updates in Ubuntu. https://bugs.launchpad.net/bugs/1365695 Title: No longer able to use GUI after update Status in nvidia-graphics-drivers-304-updates package in Ubuntu: Triaged Status in nvidia-graphics-drivers-331 package in Ubuntu: New Status in nvidia-graphics-drivers-331-updates package in Ubuntu: Triaged Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in xserver-xorg-video-intel package in Ubuntu: Fix Released Status in xserver-xorg-video-intel-lts-trusty package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-304-updates source package in Precise: Triaged Status in nvidia-graphics-drivers-331 source package in Precise: Triaged Status in nvidia-graphics-drivers-331-updates source package in Precise: Triaged Status in ubuntu-drivers-common source package in Precise: Invalid Status in xserver-xorg-video-intel source package in Precise: Invalid Status in xserver-xorg-video-intel-lts-trusty source package in Precise: Fix Released Status in nvidia-graphics-drivers-304-updates source package in Trusty: Triaged Status in nvidia-graphics-drivers-331 source package in Trusty: Triaged Status in nvidia-graphics-drivers-331-updates source package in Trusty: Triaged Status in ubuntu-drivers-common source package in Trusty: Fix Released Status in xserver-xorg-video-intel source package in Trusty: Fix Released Status in xserver-xorg-video-intel-lts-trusty source package in Trusty: Invalid Bug description: Until yesterday the 14.04 install on this Thinkpad T530 (nvidia Optimus) with nvidia-331 drivers worked just fine, including excellent multi-monitor behavior. Yesterday the set of packages below [1] was updated. I shut down, booted this morning and found out that I was not shown the lightdm login screen: I was stuck at the purple screen that precedes it (into which I enter my disk encryption password). Now the funny thing is that I could hear the lightdm startup sound and could actually login by typing my password (disk activity and started processes verify I am actually logged in), but I can't see anything: I'm still stuck at the puple screen. Uninstalling the nvidia drivers solved the problem: I'm typing this in a browser window using the nouveau drivers. I atttempted switching to nvidia-304, but that doesn't work either. Using those drivers I am shown the lightdm login screen, but after logging in I'm stuck with a screen showing only the background image. Nothing else is available, no keyboard or mouse trickery will reveal any menu, dialog or terminal to gain access. Since nouveau doesn't support a multi-monitor setup, it would be great if I someone could tell me how to get the nvidia drivers working again. Some things I noticed: - .xsession-errors reported 'Xlib: extension GLX missing on display :0' - /var/log/Xorg.0.log reported 'setversion 1.4 failed: Permission denied' [1] The packages that were updated: Start-Date: 2014-09-03 15:07:38 Upgrade: libsystemd-login0:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), systemd-services:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), librbd1:amd64 (0.80.1-0ubuntu1.1, 0.80.5-0ubuntu0.14.04.1), ubuntu-drivers-common:amd64 (0.2.91.5, 0.2.91.6), libsystemd-daemon0:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), libgudev-1.0-0:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), libgudev-1.0-0:i386 (204-5ubuntu20.4, 204-5ubuntu20.5), libpam-systemd:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), librados2:amd64 (0.80.1-0ubuntu1.1, 0.80.5-0ubuntu0.14.04.1), shotwell-common:amd64 (0.18.0-0ubuntu4.1, 0.18.0-0ubuntu4.2), udev:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), shotwell:amd64 (0.18.0-0ubuntu4.1, 0.18.0-0ubuntu4.2), gir1.2-gudev-1.0:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), libudev-dev:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), libudev1:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), libudev1:i386 (204-5ubuntu20.4, 204-5ubuntu20.5), xserver-xorg-video-intel:amd64 (2.99.910-0ubuntu1, 2.99.910-0ubuntu1.1), libsystemd-jou rnal0:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), rsyslog:amd64 (7.4.4-1ubuntu2, 7.4.4-1ubuntu2.1) End-Date: 2014-09-03 15:08:06 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nvidia-current-updates (not installed) ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CurrentDesktop: Unity Date: Thu Sep 4 22:07:11 2014 SourcePackage: nvidia-graphics-drivers-304-updates UpgradeStatus: Upgraded to trusty on 2014-06-03 (93 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304-updates/+bug/1365695/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 1446689] Re: network-manager configured to use /usr/sbin/pppoe but does not recommend pppoe
Installing pppoe solves the problem for me -- 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/1446689 Title: network-manager configured to use /usr/sbin/pppoe but does not recommend pppoe Status in network-manager package in Ubuntu: Confirmed Bug description: networkmanager switched from using ppp to using pppoe binary for dsl/pppoe connections, I am using pppoe and I can't connect to the Internet unless I install pppoe package. From: http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?h=nm-0-9-10id=7955806a02db64b20079267743056d7d9d45af3b for now, work around this by using the userland pppoe client rather than the kernel code One way to fix it is to include pppoe Another way is to configure --with-pppoe=/usr/sbin/pppd. I think this is urgent as pppoe/dsl on all vivid machines will be broken out-of-the-box. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1446689/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1446689] [NEW] networkmanager requires pppoe but it is not in requires
Public bug reported: networkmanager switched from using ppp to using pppoe binary for dsl/pppoe connections, I am using pppoe and I can't connect to the Internet unless I install pppoe package. From: http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?h=nm-0-9-10id=7955806a02db64b20079267743056d7d9d45af3b for now, work around this by using the userland pppoe client rather than the kernel code One way to fix it is to include pppoe Another way is to configure --with-pppoe=/usr/sbin/pppd. I think this is urgent as pppoe/dsl on all vivid machines will be broken out-of-the-box. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- 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/1446689 Title: networkmanager requires pppoe but it is not in requires Status in network-manager package in Ubuntu: New Bug description: networkmanager switched from using ppp to using pppoe binary for dsl/pppoe connections, I am using pppoe and I can't connect to the Internet unless I install pppoe package. From: http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?h=nm-0-9-10id=7955806a02db64b20079267743056d7d9d45af3b for now, work around this by using the userland pppoe client rather than the kernel code One way to fix it is to include pppoe Another way is to configure --with-pppoe=/usr/sbin/pppd. I think this is urgent as pppoe/dsl on all vivid machines will be broken out-of-the-box. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1446689/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1397544] [NEW] package fontconfig 2.11.0-0ubuntu4.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: problem ProblemType: Package DistroRelease: Ubuntu 14.04 Package: fontconfig 2.11.0-0ubuntu4.1 ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10 Uname: Linux 3.13.0-40-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 Date: Fri Nov 28 23:51:10 2014 DuplicateSignature: package:fontconfig:2.11.0-0ubuntu4.1:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2014-04-18 (224 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) SourcePackage: fontconfig Title: package fontconfig 2.11.0-0ubuntu4.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: fontconfig (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1397544 Title: package fontconfig 2.11.0-0ubuntu4.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in fontconfig package in Ubuntu: New Bug description: problem ProblemType: Package DistroRelease: Ubuntu 14.04 Package: fontconfig 2.11.0-0ubuntu4.1 ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10 Uname: Linux 3.13.0-40-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 Date: Fri Nov 28 23:51:10 2014 DuplicateSignature: package:fontconfig:2.11.0-0ubuntu4.1:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2014-04-18 (224 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) SourcePackage: fontconfig Title: package fontconfig 2.11.0-0ubuntu4.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1397544/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1397544] Re: package fontconfig 2.11.0-0ubuntu4.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
problem -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1397544 Title: package fontconfig 2.11.0-0ubuntu4.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in fontconfig package in Ubuntu: New Bug description: problem ProblemType: Package DistroRelease: Ubuntu 14.04 Package: fontconfig 2.11.0-0ubuntu4.1 ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10 Uname: Linux 3.13.0-40-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 Date: Fri Nov 28 23:51:10 2014 DuplicateSignature: package:fontconfig:2.11.0-0ubuntu4.1:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2014-04-18 (224 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) SourcePackage: fontconfig Title: package fontconfig 2.11.0-0ubuntu4.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1397544/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1165609] Re: There is no apparent way to stop Orca.
very stupid program does not help anything. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-orca in Ubuntu. https://bugs.launchpad.net/bugs/1165609 Title: There is no apparent way to stop Orca. Status in “gnome-orca” package in Ubuntu: Confirmed Bug description: The Orca Screen Reader icon in the Dash is a trap. If a user accidentally opens it, the only apparent recourse for the incessant jabber is to either mute the volume system-wide or log out. This makes for a very poor user experience. Orca could avoid this situation by providing at least one of the following: 1) A notification of how to stop it, if there is a way to stop it. 2) A confirmation prompt prior to starting. 3) A quit option in a standard location such as the indicator menu. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gnome-orca 3.8.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5 Uname: Linux 3.8.0-16-generic x86_64 ApportVersion: 2.9.2-0ubuntu5 Architecture: amd64 Date: Sat Apr 6 18:35:02 2013 InstallationDate: Installed on 2013-04-06 (0 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130402.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-orca UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-orca/+bug/1165609/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1239316] [NEW] Network Manager asks for the password it already have
Public bug reported: Network Manager asks for the password it already have, every time the WiFi goes down and up, even if it has saved it. I think this got fixed upstream sometime ago, not sure this is a regression or didn't got the fix in Kubuntu ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: network-manager 0.9.8.0-0ubuntu22 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Sun Oct 13 13:15:07 2013 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-10-10 (2 days ago) InstallationMedia: Kubuntu 13.10 Saucy Salamander - Beta amd64 (20130925.1) IpRoute: default via 192.168.0.1 dev wlan0 proto static 192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.100 metric 9 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH hussain 357764b9-8e9a-46f3-8d2c-1afbce5573b9 802-11-wireless 1381577113 12 أكت, 2013 AST 02:25:13 مyes no /org/freedesktop/NetworkManager/Settings/2 New 802-11-wireless connection 26eedf69-821e-4178-b4a8-3eb2b3d62edf 802-11-wireless 1381484555 11 أكت, 2013 AST 12:42:35 مyes no /org/freedesktop/NetworkManager/Settings/1 Saad 984440ea-af1b-46b1-b755-a865abddd155 802-11-wireless 1381659310 13 أكت, 2013 AST 01:15:10 مyes no /org/freedesktop/NetworkManager/Settings/0 Wired connection 1d57d073f-1609-48ed-8a35-a49c791f0691 802-3-ethernet1381649411 13 أكت, 2013 AST 10:30:11 صyes no /org/freedesktop/NetworkManager/Settings/3 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/1 wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.0connected enabled enabled enabledenabled disabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1239316 Title: Network Manager asks for the password it already have Status in “network-manager” package in Ubuntu: New Bug description: Network Manager asks for the password it already have, every time the WiFi goes down and up, even if it has saved it. I think this got fixed upstream sometime ago, not sure this is a regression or didn't got the fix in Kubuntu ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: network-manager 0.9.8.0-0ubuntu22 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Sun Oct 13 13:15:07 2013 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-10-10 (2 days ago) InstallationMedia: Kubuntu 13.10 Saucy Salamander - Beta amd64 (20130925.1) IpRoute: default via 192.168.0.1 dev wlan0 proto static 192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.100 metric 9 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH hussain 357764b9-8e9a-46f3-8d2c-1afbce5573b9 802-11-wireless 1381577113 12 أكت, 2013 AST 02:25:13 مyes no /org/freedesktop/NetworkManager/Settings/2 New 802-11-wireless connection 26eedf69-821e-4178-b4a8-3eb2b3d62edf 802-11-wireless 1381484555 11 أكت, 2013 AST 12:42:35 مyes no /org/freedesktop/NetworkManager/Settings/1 Saad 984440ea-af1b-46b1-b755-a865abddd155 802-11-wireless 1381659310 13 أكت, 2013 AST 01:15:10 م
[Desktop-packages] [Bug 1066623] Re: Chromium browser crash
This was an old version of Chromium and Ubuntu, please close this bug as I can't reproduce it anymore. ** Changed in: chromium-browser (Ubuntu) Status: New = Opinion -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1066623 Title: Chromium browser crash Status in “chromium-browser” package in Ubuntu: Opinion Bug description: Chromium browser crashed several times, I started it from console to see what is happening I got: mustafa@mustafa-Lenovo-B570e:~$ chromium-browser [6411:6456:401683:ERROR:download_updates_command.cc(99)] PostClientToServerMessage() failed during GetUpdates [6411:6456:4046444097:ERROR:download_updates_command.cc(99)] PostClientToServerMessage() failed during GetUpdates [6411:6456:4049445805:ERROR:download_updates_command.cc(99)] PostClientToServerMessage() failed during GetUpdates [6411:6456:4056449015:ERROR:download_updates_command.cc(99)] PostClientToServerMessage() failed during GetUpdates [6411:6456:4057446233:ERROR:download_updates_command.cc(99)] PostClientToServerMessage() failed during GetUpdates [6411:6456:4074448897:ERROR:download_updates_command.cc(99)] PostClientToServerMessage() failed during GetUpdates [6411:6456:4100451287:ERROR:download_updates_command.cc(99)] PostClientToServerMessage() failed during GetUpdates [6411:6456:4139453703:ERROR:download_updates_command.cc(99)] PostClientToServerMessage() failed during GetUpdates [6411:6456:4236455023:ERROR:download_updates_command.cc(99)] PostClientToServerMessage() failed during GetUpdates Segmentation fault (core dumped) then: mustafa@mustafa-Lenovo-B570e:~$ chromium-browser Segmentation fault (core dumped) I don't know what is wrong. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: chromium-browser 20.0.1132.47~r144678-0ubuntu6 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 Date: Mon Oct 15 02:39:46 2012 Desktop-Session: DESKTOP_SESSION = kde-plasma XDG_CONFIG_DIRS = /etc/xdg/xdg-kde-plasma:/etc/xdg XDG_DATA_DIRS = /usr/share/kde-plasma:/usr/local/share/:/usr/share/ DetectedPlugins: = Remoting Viewer - enabled = True - path= internal-remoting-viewer = Remoting Viewer - enabled = True Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = None InstallationMedia: Kubuntu 12.10 Quantal Quetzal - Beta amd64 (20120926.3) ProcEnviron: LANGUAGE= TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) chromium-default: CHROMIUM_FLAGS= gconf-keys: gconftool-2 not found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1066623/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1066643] Re: Apport KDE crash
I can't reproduce this anymore, please close it.
** Changed in: apport (Ubuntu)
Status: New = Opinion
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1066643
Title:
Apport KDE crash
Status in “apport” package in Ubuntu:
Opinion
Bug description:
Dr. Konqi generated this crash report so I will paste it here:
Application: python3 (1.0)
KDE Platform Version: 4.9.2
Qt Version: 4.8.3
Operating System: Linux 3.5.0-17-generic x86_64
Distribution: Ubuntu 12.10
-- Information about the crash:
I was trying to report a bug in Chromium, I didn't write chromium-browser,
instead just chromium (or any random string), this crashed apport-kde, it first
tells me that the package does not exist then crashes.
The crash can be reproduced every time.
-- Backtrace:
Application: Apport KDE (python3.2mu), signal: Segmentation fault
Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1.
[KCrash Handler]
#5 QWidget::~QWidget (this=0x211a940, __in_chrg=optimized out) at
kernel/qwidget.cpp:1630
#6 0x7ffdcb336759 in ?? () from
/usr/lib/python3/dist-packages/PyQt4/QtGui.cpython-32mu.so
#7 0x7ffdcb32a976 in ?? () from
/usr/lib/python3/dist-packages/PyQt4/QtGui.cpython-32mu.so
#8 0x7ffdcb7a6cd4 in ?? () from
/usr/lib/python3/dist-packages/sip.cpython-32mu.so
#9 0x7ffdcb7a85b9 in ?? () from
/usr/lib/python3/dist-packages/sip.cpython-32mu.so
#10 0x0046e6e7 in subtype_dealloc.6395
(self=ProgressDialog(buttons=QDialogButtonBox at remote 0x21fd050,
text=QLabel at remote 0x1ebcef0, progress=QProgressBar at remote 0x1ebcf80,
vboxlayout=QVBoxLayout at remote 0x1ebcdd0, heading=QLabel at remote
0x1ebce60) at remote 0x1ebca70) at ../Objects/typeobject.c:977
#11 0x004d6f97 in dict_dealloc.65589 (mp=0x1e8e400) at
../Objects/dictobject.c:1048
#12 0x0046e77f in subtype_dealloc.6395
(self=MainUserInterface(report_file=None, gettext_domain='apport', args=[],
crashdb=CrashDatabase at remote 0x20d4950, cur_package='chromium',
dialog=None, report=Report at remote 0x20e2810,
progress=ProgressDialog(buttons=QDialogButtonBox at remote 0x21fd050,
text=QLabel at remote 0x1ebcef0, progress=QProgressBar at remote 0x1ebcf80,
vboxlayout=QVBoxLayout at remote 0x1ebcdd0, heading=QLabel at remote
0x1ebce60) at remote 0x1ebca70, options=Values(save=None,
package='chromium', pid=None, update_report=None, window=False, version=None,
hanging=False, tag=[], filebug=True, crash_file=None, symptom=None) at remote
0x20e2710) at remote 0x1ec5f10) at ../Objects/typeobject.c:962
#13 0x004cb383 in insertdict_by_entry.65617 (mp=mp@entry=0x11233d0,
key=key@entry='UserInterface', hash=hash@entry=1546387388073679355,
ep=optimized out, value=value@entry=None) at ../Objects/dictobject.c:527
#14 0x004cb437 in insertdict (value=None, hash=1546387388073679355,
key='UserInterface', mp=0x11233d0) at ../Objects/dictobject.c:564
#15 dict_set_item_by_hash_or_entry (value=None, ep=0x0,
hash=1546387388073679355, key='UserInterface', op={'qUncompress': None,
'Q_ENUMS': None, 'QVBoxLayout': None, 'text': None, 'QState': None,
'QProcessEnvironment': None, 'qRound64': None, 'QDir': None, 'qRound': None,
'noforcesign': None, 'QVariantAnimation': None, 'QSignalMapper': None,
'QRadioButton': None, 'ReportDialog': None, 'QPyNullVariant': None,
'copyright': None, 'qChecksum': None, 'description': None, 'QPoint': None,
'KCmdLineArgs': None, 'QDialog': None, 'QAbstractEventDispatcher': None,
'QLineEdit': None, 'apport': None, 'QBitArray': None,
'QXmlStreamEntityDeclaration': None, 'QModelIndex': None, 'QLocale': None,
'pyqtSignature': None, 'QFinalState': None, 'KApplication': None, 'QFile':
None, 'qAbs': None, 'MainUserInterface': None, 'QMutexLocker': None,
'QSettings': None, '__cached__': None, 'uppercasebase': None, 'QtSystemMsg':
None, 'QAbstractAnimation': None, 'QThread': None, 'QBasicTimer': None, 'oct_':
None, 'qsrand': None, 'pyqtWrapperType': None, 'QTimeLine': None,
'QAbstractTransition': None, 'QEventTransition': None,
'QSequentialAnimati...(truncated)) at ../Objects/dictobject.c:803
#16 PyDict_SetItem (op=op@entry={'qUncompress': None, 'Q_ENUMS': None,
'QVBoxLayout': None, 'text': None, 'QState': None, 'QProcessEnvironment': None,
'qRound64': None, 'QDir': None, 'qRound': None, 'noforcesign': None,
'QVariantAnimation': None, 'QSignalMapper': None, 'QRadioButton': None,
'ReportDialog': None, 'QPyNullVariant': None, 'copyright': None, 'qChecksum':
None, 'description': None, 'QPoint': None, 'KCmdLineArgs': None, 'QDialog':
None, 'QAbstractEventDispatcher': None, 'QLineEdit': None, 'apport': None,
'QBitArray': None, 'QXmlStreamEntityDeclaration': None, 'QModelIndex': None,
'QLocale': None, 'pyqtSignature': None, 'QFinalState': None, 'KApplication':
None, 'QFile': None, 'qAbs': None,
[Desktop-packages] [Bug 1229065] [NEW] Flash player crashes when watching some video or animation
Public bug reported: My problem is that Flash player keeps on crashing always. I'm using dual graphics. Yesterday I switched to high GPU and later switched back to intel GPU. And the Flash player never worked since then. I did some search on forums Google, then tried every possibilities but still problem persists. By the way when I right click settings flash player keeps on crashing and I can't change any settings. How can i fix that ? Thank you in advance. ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Tags: chrome crashes firefox flash player sigsegv ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1229065 Title: Flash player crashes when watching some video or animation Status in “chromium-browser” package in Ubuntu: New Bug description: My problem is that Flash player keeps on crashing always. I'm using dual graphics. Yesterday I switched to high GPU and later switched back to intel GPU. And the Flash player never worked since then. I did some search on forums Google, then tried every possibilities but still problem persists. By the way when I right click settings flash player keeps on crashing and I can't change any settings. How can i fix that ? Thank you in advance. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1229065/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 998489] Re: Fn+F11 does not control Ambient Light Sensor on HP 8560W
is there any update on this. it's also not working on my HP 8560P. setting /sys/devices/platform/hp-wmi/als to 1 works -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/998489 Title: Fn+F11 does not control Ambient Light Sensor on HP 8560W Status in “xserver-xorg-input-evdev” package in Ubuntu: Confirmed Bug description: Ubuntu 12.04 LTS with Gnome Classic tries to disable touchpad (at least it displays that image in top right corner). But actually seems nothing happens at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/998489/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1175790] Re: Nautilus is very laggy when opening/closing home foder
** Description changed: Nautilus is very laggy and slow in opening and closing when having over 1000 files. After first installing Ubuntu 13.04 it was OK, later after starting to download many files and have over 1000 files it started to be extremely slow, and also the desktop when trying to mark with the mouse items on the desktop it lags. Note that all other application run fine, except for nautilus. I am on Sony Vaio SVS13125CAW With corei5 processor 3rd generation, 4GB RAM and 5400rpm Hard drive. + + UPDATE + When I tried down grading to Ubuntu 12.04 LTS, nautilus is now working fine with the same number of files in the home folder. So I guess this bug is only in 13.04 -- 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/1175790 Title: Nautilus is very laggy when opening/closing home foder Status in “nautilus” package in Ubuntu: New Bug description: Nautilus is very laggy and slow in opening and closing when having over 1000 files. After first installing Ubuntu 13.04 it was OK, later after starting to download many files and have over 1000 files it started to be extremely slow, and also the desktop when trying to mark with the mouse items on the desktop it lags. Note that all other application run fine, except for nautilus. I am on Sony Vaio SVS13125CAW With corei5 processor 3rd generation, 4GB RAM and 5400rpm Hard drive. UPDATE When I tried down grading to Ubuntu 12.04 LTS, nautilus is now working fine with the same number of files in the home folder. So I guess this bug is only in 13.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1175790/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1175790] [NEW] Nautilus is very laggy when opening/closing home foder
Public bug reported: Nautilus is very laggy and slow in opening and closing when having over 1000 file. It makes the system unusable. ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New -- 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/1175790 Title: Nautilus is very laggy when opening/closing home foder Status in “nautilus” package in Ubuntu: New Bug description: Nautilus is very laggy and slow in opening and closing when having over 1000 file. It makes the system unusable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1175790/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1175790] Re: Nautilus is very laggy when opening/closing home foder
** Description changed: - Nautilus is very laggy and slow in opening and closing when having over 1000 file. - It makes the system unusable. + Nautilus is very laggy and slow in opening and closing when having over 1000 files. + After first installing Ubuntu 13.04 it was OK, later after starting to download many files and have over 1000 files it started to be extremely slow, and also the desktop when trying to mark with the mouse items on the desktop it lags. Note that all other application run fine, except for nautilus. I am on Sony Vaio SVS13125CAW With corei5 processor 3rd generation, 4GB RAM and 5400rpm Hard drive. -- 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/1175790 Title: Nautilus is very laggy when opening/closing home foder Status in “nautilus” package in Ubuntu: New Bug description: Nautilus is very laggy and slow in opening and closing when having over 1000 files. After first installing Ubuntu 13.04 it was OK, later after starting to download many files and have over 1000 files it started to be extremely slow, and also the desktop when trying to mark with the mouse items on the desktop it lags. Note that all other application run fine, except for nautilus. I am on Sony Vaio SVS13125CAW With corei5 processor 3rd generation, 4GB RAM and 5400rpm Hard drive. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1175790/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 850840] Re: file-roller crashed with SIGSEGV in g_simple_async_result_complete()
i got this error. i use $ sudo apt-get install rar and worked. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/850840 Title: file-roller crashed with SIGSEGV in g_simple_async_result_complete() Status in File Roller: New Status in “file-roller” package in Ubuntu: Confirmed Bug description: I have this crash just after the startup! ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: file-roller 3.1.91-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-9.15-generic 3.0.3 Uname: Linux 3.0.0-9-generic i686 NonfreeKernelModules: fglrx ApportVersion: 1.22.1-0ubuntu2 Architecture: i386 Date: Thu Sep 15 09:09:35 2011 ExecutablePath: /usr/bin/file-roller InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) ProcCmdline: file-roller /home/username/development/Qt\ development/QOgre1.0.0.0-build-desktop/meshes/SdkTrays.zip ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x8d13e2: mov%eax,0x24(%edi) PC (0x008d13e2) ok source %eax ok destination 0x24(%edi) (0xaace) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: file-roller StacktraceTop: ?? () from /usr/lib/libgtk-3.so.0 g_simple_async_result_complete () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/libgtk-3.so.0 g_simple_async_result_complete () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0 Title: file-roller crashed with SIGSEGV in g_simple_async_result_complete() UpgradeStatus: Upgraded to oneiric on 2011-09-14 (1 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/file-roller/+bug/850840/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 876082] Re: Gwibber Identi.ca Account Setup Issue
On Sat, Feb 11, 2012 at 4:56 AM, Bilal Shahid s9ip...@gmail.com wrote: Thank you for taking the time to report this bug and helping to make Ubuntu better, * can you reproduce it ? * if so than which version are you on ? which versions are you using ? ** Changed in: gwibber (Ubuntu) Status: New = Incomplete ** Changed in: gwibber (Ubuntu) Importance: Undecided = Medium -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/876082 Title: Gwibber Identi.ca Account Setup Issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gwibber/+bug/876082/+subscriptions * Yes, I can reproduce it * I am using Ubuntu 11.10 Gwibber 3.2.1 * The issue can be reproduced with the following steps - Open Gwibber - Go to Edit Accounts - Select Identica from drop down list - Click on Add button - Click on Authorize button - Nothing happens after that no matter how many times you press the Authorize button. For other services it opens the autohization windows in which we can login to that service. But for Identica it never happens. -- *Mustafa Qasim* mu...@linux.com http://blog.mustu.info -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gwibber in Ubuntu. https://bugs.launchpad.net/bugs/876082 Title: Gwibber Identi.ca Account Setup Issue Status in “gwibber” package in Ubuntu: Incomplete Bug description: Can't add identi.ca account int Gwibber. After selecting Identi.ca from services list the Authorize button doesn't connects to identi.ca and doesn't opens any authorization window. However it works fine for twitter. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gwibber/+bug/876082/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 916874] [NEW] package libreoffice-base-core 1:3.5.0~beta2-2ubuntu3 failed to install/upgrade: dependency problems - leaving unconfigured
Public bug reported: still have same bug... ProblemType: Package DistroRelease: Ubuntu 12.04 Package: libreoffice-base-core 1:3.5.0~beta2-2ubuntu3 ProcVersionSignature: Ubuntu 3.2.0-8.15-generic 3.2.0 Uname: Linux 3.2.0-8-generic i686 ApportVersion: 1.90-0ubuntu2 Architecture: i386 Date: Fri Jan 13 14:52:04 2012 ErrorMessage: dependency problems - leaving unconfigured InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) SourcePackage: libreoffice Title: package libreoffice-base-core 1:3.5.0~beta2-2ubuntu3 failed to install/upgrade: dependency problems - leaving unconfigured UpgradeStatus: Upgraded to precise on 2012-01-14 (0 days ago) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 precise -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/916874 Title: package libreoffice-base-core 1:3.5.0~beta2-2ubuntu3 failed to install/upgrade: dependency problems - leaving unconfigured Status in “libreoffice” package in Ubuntu: New Bug description: still have same bug... ProblemType: Package DistroRelease: Ubuntu 12.04 Package: libreoffice-base-core 1:3.5.0~beta2-2ubuntu3 ProcVersionSignature: Ubuntu 3.2.0-8.15-generic 3.2.0 Uname: Linux 3.2.0-8-generic i686 ApportVersion: 1.90-0ubuntu2 Architecture: i386 Date: Fri Jan 13 14:52:04 2012 ErrorMessage: dependency problems - leaving unconfigured InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) SourcePackage: libreoffice Title: package libreoffice-base-core 1:3.5.0~beta2-2ubuntu3 failed to install/upgrade: dependency problems - leaving unconfigured UpgradeStatus: Upgraded to precise on 2012-01-14 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/916874/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 916874] Re: package libreoffice-base-core 1:3.5.0~beta2-2ubuntu3 failed to install/upgrade: dependency problems - leaving unconfigured
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/916874 Title: package libreoffice-base-core 1:3.5.0~beta2-2ubuntu3 failed to install/upgrade: dependency problems - leaving unconfigured Status in “libreoffice” package in Ubuntu: New Bug description: still have same bug... ProblemType: Package DistroRelease: Ubuntu 12.04 Package: libreoffice-base-core 1:3.5.0~beta2-2ubuntu3 ProcVersionSignature: Ubuntu 3.2.0-8.15-generic 3.2.0 Uname: Linux 3.2.0-8-generic i686 ApportVersion: 1.90-0ubuntu2 Architecture: i386 Date: Fri Jan 13 14:52:04 2012 ErrorMessage: dependency problems - leaving unconfigured InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) SourcePackage: libreoffice Title: package libreoffice-base-core 1:3.5.0~beta2-2ubuntu3 failed to install/upgrade: dependency problems - leaving unconfigured UpgradeStatus: Upgraded to precise on 2012-01-14 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/916874/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 915981] Re: package libreoffice-base-core 1:3.5.0~beta2-2ubuntu2 failed to install/upgrade: ErrorMessage: dependency problems - leaving unconfigured
*** This bug is a duplicate of bug 915271 *** https://bugs.launchpad.net/bugs/915271 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/915981 Title: package libreoffice-base-core 1:3.5.0~beta2-2ubuntu2 failed to install/upgrade: ErrorMessage: dependency problems - leaving unconfigured Status in “libreoffice” package in Ubuntu: New Bug description: teriebel.. ProblemType: Package DistroRelease: Ubuntu 12.04 Package: libreoffice-base-core 1:3.5.0~beta2-2ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-8.15-generic 3.2.0 Uname: Linux 3.2.0-8-generic i686 ApportVersion: 1.90-0ubuntu1 Architecture: i386 Date: Thu Jan 12 18:45:21 2012 ErrorMessage: ErrorMessage: dependency problems - leaving unconfigured InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) SourcePackage: libreoffice Title: package libreoffice-base-core 1:3.5.0~beta2-2ubuntu2 failed to install/upgrade: ErrorMessage: dependency problems - leaving unconfigured UpgradeStatus: Upgraded to precise on 2012-01-12 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/915981/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 876082] [NEW] Gwibber Identi.ca Account Setup Issue
Public bug reported: Can't add identi.ca account int Gwibber. After selecting Identi.ca from services list the Authorize button doesn't connects to identi.ca and doesn't opens any authorization window. However it works fine for twitter. ** Affects: gwibber (Ubuntu) Importance: Undecided Status: New ** Tags: gwibber identi.ca -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gwibber in Ubuntu. https://bugs.launchpad.net/bugs/876082 Title: Gwibber Identi.ca Account Setup Issue Status in “gwibber” package in Ubuntu: New Bug description: Can't add identi.ca account int Gwibber. After selecting Identi.ca from services list the Authorize button doesn't connects to identi.ca and doesn't opens any authorization window. However it works fine for twitter. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gwibber/+bug/876082/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
