[Desktop-packages] [Bug 1826616] Re: After resuming from suspend, wallpaper turns to static
Also the lockscreen image is affected as well. Sometimes other parts of the UI are as well like browser windows. -- 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/1826616 Title: After resuming from suspend, wallpaper turns to static Status in gnome-shell package in Ubuntu: New Bug description: As stated in the title of the bug, every time I resume from suspend, the wallpaper turns into a static picture. This can be somewhat alleviated by switching the wallpaper, but the previous wallpaper is unusable until reboot. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0+git20190410-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 26 20:15:54 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-11-11 (166 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2019-04-17 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1826616/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1826616] Re: After resuming from suspend, wallpaper turns to static
** Attachment added: "Static wallpaper" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1826616/+attachment/5259404/+files/Screenshot%20from%202019-04-26%2020-16-08.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/1826616 Title: After resuming from suspend, wallpaper turns to static Status in gnome-shell package in Ubuntu: New Bug description: As stated in the title of the bug, every time I resume from suspend, the wallpaper turns into a static picture. This can be somewhat alleviated by switching the wallpaper, but the previous wallpaper is unusable until reboot. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0+git20190410-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 26 20:15:54 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-11-11 (166 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2019-04-17 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1826616/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1826616] [NEW] After resuming from suspend, wallpaper turns to static
Public bug reported: As stated in the title of the bug, every time I resume from suspend, the wallpaper turns into a static picture. This can be somewhat alleviated by switching the wallpaper, but the previous wallpaper is unusable until reboot. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0+git20190410-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 26 20:15:54 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-11-11 (166 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2019-04-17 (9 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- 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/1826616 Title: After resuming from suspend, wallpaper turns to static Status in gnome-shell package in Ubuntu: New Bug description: As stated in the title of the bug, every time I resume from suspend, the wallpaper turns into a static picture. This can be somewhat alleviated by switching the wallpaper, but the previous wallpaper is unusable until reboot. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0+git20190410-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 26 20:15:54 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-11-11 (166 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2019-04-17 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1826616/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1826057] [NEW] Automatically signed out of Ubuntu One on terminating session
Public bug reported: If the user reboots or shuts down (uncertain about logging off and back on), they will be signed out from Ubuntu One. Previously, Ubuntu Software on 18.10 and earlier, the user would be signed out of Ubuntu One after closing the Software Store, but now it takes a reboot or something similar and the user is signed out of Ubuntu One. At least the bug is now less annoying. Running Ubuntu 19.04 amd64 with gnome-software 3.30.6-2ubuntu3. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-software 3.30.6-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 23 16:38:51 2019 InstallationDate: Installed on 2018-11-11 (162 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) InstalledPlugins: gnome-software-plugin-flatpak 3.30.6-2ubuntu3 gnome-software-plugin-snap3.30.6-2ubuntu3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-software UpgradeStatus: Upgraded to disco on 2019-04-17 (6 days ago) ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1826057 Title: Automatically signed out of Ubuntu One on terminating session Status in gnome-software package in Ubuntu: New Bug description: If the user reboots or shuts down (uncertain about logging off and back on), they will be signed out from Ubuntu One. Previously, Ubuntu Software on 18.10 and earlier, the user would be signed out of Ubuntu One after closing the Software Store, but now it takes a reboot or something similar and the user is signed out of Ubuntu One. At least the bug is now less annoying. Running Ubuntu 19.04 amd64 with gnome- software 3.30.6-2ubuntu3. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-software 3.30.6-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 23 16:38:51 2019 InstallationDate: Installed on 2018-11-11 (162 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) InstalledPlugins: gnome-software-plugin-flatpak 3.30.6-2ubuntu3 gnome-software-plugin-snap3.30.6-2ubuntu3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-software UpgradeStatus: Upgraded to disco on 2019-04-17 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1826057/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1825756] Re: Window snapping to corners via mouse
** Description changed: Curretly, this feature simply does not exist, unless you count the buggy keyboard implementation. Please add the feature to snap windows to the bottom left and right and upper left and right corners via the mouse alone. Currently, if you manually install compiz settings, you can map the keyboard out to do this. Windows 10 and Ubuntu MATE and possibly other distros/desktop environments allow this snap behavior. Why not Ubuntu with GNOME? Running Ubuntu 19.04 amd64. CCSM version 1:0.9.14.0+19.04.20190223.1-0ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 19.04 - Package: compiz (not installed) + Package: gnome-shell ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..04.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:04:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: - NVRM version: NVIDIA UNIX x86_64 Kernel Module 418.56 Fri Mar 15 12:59:26 CDT 2019 - GCC version: gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1) + NVRM version: NVIDIA UNIX x86_64 Kernel Module 418.56 Fri Mar 15 12:59:26 CDT 2019 + GCC version: gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1) ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Apr 21 18:49:51 2019 DistUpgraded: 2019-04-17 14:06:01,387 INFO cache.commit() DistroCodename: disco DistroVariant: ubuntu DkmsStatus: nvidia, 418.56, 5.0.0-13-generic, x86_64: installed GraphicsCard: - Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) -Subsystem: Hewlett-Packard Company HD Graphics 5500 [103c:80de] -Subsystem: Hewlett-Packard Company GM107M [GeForce GTX 950M] [103c:80de] + Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) + Subsystem: Hewlett-Packard Company HD Graphics 5500 [103c:80de] + Subsystem: Hewlett-Packard Company GM107M [GeForce GTX 950M] [103c:80de] GsettingsChanges: - + InstallationDate: Installed on 2018-11-11 (161 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Hewlett-Packard HP ENVY Notebook ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=1b2784f7-5eb6-447e-bc5e-224950bc1205 ro quiet splash vt.handoff=1 SourcePackage: compiz UpgradeStatus: Upgraded to disco on 2019-04-17 (4 days ago) dmi.bios.date: 11/21/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.51 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80DE dmi.board.vendor: Hewlett-Packard dmi.board.version: 64.44 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.51:bd11/21/2018:svnHewlett-Packard:pnHPENVYNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn80DE:rvr64.44:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV dmi.product.name: HP ENVY Notebook dmi.product.sku: L3T35AV dmi.product.version: Type1ProductConfigId dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 -- 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/1825756 Title: Window snapping to corners via mouse Status in Ubuntu: New Status in gnome-shell package in Ubuntu: New Bug description: Curretly, this feature simply does not exist, unless you count the buggy keyboard implementation. Please add the feature to snap windows to the bottom left and right and upper left and right corners via the mouse alone. Currently, if you manually install compiz settings, you can map the keyboard out to do this. Windows 10 and Ubuntu MATE and possibly other distros/desktop
[Desktop-packages] [Bug 1825756] Re: Window snapping to corners via mouse
** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- 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/1825756 Title: Window snapping to corners via mouse Status in Ubuntu: New Status in gnome-shell package in Ubuntu: New Bug description: Curretly, this feature simply does not exist, unless you count the buggy keyboard implementation. Please add the feature to snap windows to the bottom left and right and upper left and right corners via the mouse alone. Currently, if you manually install compiz settings, you can map the keyboard out to do this. Windows 10 and Ubuntu MATE and possibly other distros/desktop environments allow this snap behavior. Why not Ubuntu with GNOME? Running Ubuntu 19.04 amd64. CCSM version 1:0.9.14.0+19.04.20190223.1-0ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: compiz (not installed) ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..04.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:04:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 418.56 Fri Mar 15 12:59:26 CDT 2019 GCC version: gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1) ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Apr 21 18:49:51 2019 DistUpgraded: 2019-04-17 14:06:01,387 INFO cache.commit() DistroCodename: disco DistroVariant: ubuntu DkmsStatus: nvidia, 418.56, 5.0.0-13-generic, x86_64: installed GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 5500 [103c:80de] Subsystem: Hewlett-Packard Company GM107M [GeForce GTX 950M] [103c:80de] GsettingsChanges: InstallationDate: Installed on 2018-11-11 (161 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Hewlett-Packard HP ENVY Notebook ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=1b2784f7-5eb6-447e-bc5e-224950bc1205 ro quiet splash vt.handoff=1 SourcePackage: compiz UpgradeStatus: Upgraded to disco on 2019-04-17 (4 days ago) dmi.bios.date: 11/21/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.51 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80DE dmi.board.vendor: Hewlett-Packard dmi.board.version: 64.44 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.51:bd11/21/2018:svnHewlett-Packard:pnHPENVYNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn80DE:rvr64.44:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV dmi.product.name: HP ENVY Notebook dmi.product.sku: L3T35AV dmi.product.version: Type1ProductConfigId dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1825756/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1802982] Re: GNOME Software keeps logging out of the Ubuntu One account
Actually the bug does effect disco. Noticed it again after a few app openings. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1802982 Title: GNOME Software keeps logging out of the Ubuntu One account Status in gnome-software package in Ubuntu: Confirmed Bug description: Every time I restart the system, my Ubuntu One account that is was connected to ubuntu Software keeps disconnected. This doesn't happen with the Snap account, only with the Ubuntu One account. Description: Ubuntu 18.10 Release: 18.10 gnome-software: Instalado: 3.30.2-0ubuntu8 Candidato: 3.30.2-0ubuntu8 Tabela de versão: *** 3.30.2-0ubuntu8 500 500 http://br.archive.ubuntu.com/ubuntu cosmic-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.30.2-0ubuntu5 500 500 http://br.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1802982/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1802982] Re: GNOME Software keeps logging out of the Ubuntu One account
Bug does not effect disco. I checked. As a workaround, you can download all the related packages from disco and the login issue will be resolved. Maybe the devs can find out what changed and backport it? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1802982 Title: GNOME Software keeps logging out of the Ubuntu One account Status in gnome-software package in Ubuntu: Confirmed Bug description: Every time I restart the system, my Ubuntu One account that is was connected to ubuntu Software keeps disconnected. This doesn't happen with the Snap account, only with the Ubuntu One account. Description: Ubuntu 18.10 Release: 18.10 gnome-software: Instalado: 3.30.2-0ubuntu8 Candidato: 3.30.2-0ubuntu8 Tabela de versão: *** 3.30.2-0ubuntu8 500 500 http://br.archive.ubuntu.com/ubuntu cosmic-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.30.2-0ubuntu5 500 500 http://br.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1802982/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1805053] [NEW] "Keep aligned" gets toggled off after logging out
Public bug reported: Log into Ubuntu like normal. Now right click the desktop and toggle on "Keep Aligned". Now log off. Don't reboot or shutdown as neither appear to trigger the bug. Log back in. Notice 100% of the time the checkbox is now untoggled. This is annoying and makes the desktop icons line up like they were meant for Windows 9x without alignment. The user selected option should persist past logoff. Running Ubuntu 18.10, with nautilus 1:3.26.4-0ubuntu7. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: nautilus 1:3.26.4-0ubuntu7 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Nov 25 17:52:59 2018 InstallationDate: Installed on 2018-11-11 (14 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: dropbox 2015.10.28 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic -- 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/1805053 Title: "Keep aligned" gets toggled off after logging out Status in nautilus package in Ubuntu: New Bug description: Log into Ubuntu like normal. Now right click the desktop and toggle on "Keep Aligned". Now log off. Don't reboot or shutdown as neither appear to trigger the bug. Log back in. Notice 100% of the time the checkbox is now untoggled. This is annoying and makes the desktop icons line up like they were meant for Windows 9x without alignment. The user selected option should persist past logoff. Running Ubuntu 18.10, with nautilus 1:3.26.4-0ubuntu7. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: nautilus 1:3.26.4-0ubuntu7 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Nov 25 17:52:59 2018 InstallationDate: Installed on 2018-11-11 (14 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: dropbox 2015.10.28 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1805053/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1803909] [NEW] Ubuntu Software not staying logged into Ubuntu One
Public bug reported: If the user signs into Ubuntu One, upon exiting Ubuntu Software they will be logged out. This does not apply to the Snap Store; sign in once there and things work properly - you are logged in for good. Running Ubuntu 18.04, version 3.30.2 of Ubuntu Software. User should stay logged into Ubuntu One once they sign in once instead of being automatically logged out. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: ubuntu-software 3.30.2-0ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Nov 18 19:12:30 2018 InstallationDate: Installed on 2018-11-11 (7 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) InstalledPlugins: gnome-software-plugin-flatpak 3.30.2-0ubuntu8 gnome-software-plugin-limba N/A gnome-software-plugin-snap3.30.2-0ubuntu8 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1803909 Title: Ubuntu Software not staying logged into Ubuntu One Status in gnome-software package in Ubuntu: New Bug description: If the user signs into Ubuntu One, upon exiting Ubuntu Software they will be logged out. This does not apply to the Snap Store; sign in once there and things work properly - you are logged in for good. Running Ubuntu 18.04, version 3.30.2 of Ubuntu Software. User should stay logged into Ubuntu One once they sign in once instead of being automatically logged out. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: ubuntu-software 3.30.2-0ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Nov 18 19:12:30 2018 InstallationDate: Installed on 2018-11-11 (7 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) InstalledPlugins: gnome-software-plugin-flatpak 3.30.2-0ubuntu8 gnome-software-plugin-limba N/A gnome-software-plugin-snap3.30.2-0ubuntu8 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1803909/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1769383] Re: Ubuntu dock/launcher is shown on the lock screen
Unfortunately I have no clue what triggers the bug as of yet. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1769383 Title: Ubuntu dock/launcher is shown on the lock screen Status in gnome-shell package in Ubuntu: Incomplete Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: In Progress Status in gnome-shell source package in Cosmic: Incomplete Status in gnome-shell-extension-ubuntu-dock source package in Cosmic: In Progress Status in gnome-shell source package in Disco: Incomplete Status in gnome-shell-extension-ubuntu-dock source package in Disco: In Progress Bug description: After an update from ubuntu 16.04 to 18.04 the dock is aviable on the lockscreen after user login. I did not configure this knowingly. Also i can start every application which is available on the dock. Settings, virtual box, visualstudio code and so on. After the update to 18.04 i just configure the screen frequency to 144Hz and the night mode on. And attach the dock on bottom. I later undid these customizations back to configuration before, but the dock is stil aviable on lockscreen. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-settings-daemon 3.28.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat May 5 18:30:16 2018 InstallationDate: Installed on 2018-04-08 (27 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to bionic on 2018-05-01 (3 days ago) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-08 (27 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell-extension-ubuntu-dock 0.9.1 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-05-01 (4 days ago) 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/1769383/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1769383] Re: Ubuntu dock/launcher is shown on the lock screen
Land for dingo? What are the possibilities of a backport to both 18.04 and 18.10? Couldn't this be considered a security vulnerability? It can theoretically be used to close someone else's work out without saving, depending on the application. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1769383 Title: Ubuntu dock/launcher is shown on the lock screen Status in gnome-shell package in Ubuntu: Incomplete Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: In Progress Bug description: After an update from ubuntu 16.04 to 18.04 the dock is aviable on the lockscreen after user login. I did not configure this knowingly. Also i can start every application which is available on the dock. Settings, virtual box, visualstudio code and so on. After the update to 18.04 i just configure the screen frequency to 144Hz and the night mode on. And attach the dock on bottom. I later undid these customizations back to configuration before, but the dock is stil aviable on lockscreen. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-settings-daemon 3.28.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat May 5 18:30:16 2018 InstallationDate: Installed on 2018-04-08 (27 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to bionic on 2018-05-01 (3 days ago) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-08 (27 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell-extension-ubuntu-dock 0.9.1 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-05-01 (4 days ago) 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/1769383/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1769383] Re: Ubuntu dock/launcher is shown on the lock screen
I did a clean install of Cosmic and the bug is present as well for me also. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1769383 Title: Ubuntu dock/launcher is shown on the lock screen Status in gnome-shell package in Ubuntu: Incomplete Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: In Progress Bug description: After an update from ubuntu 16.04 to 18.04 the dock is aviable on the lockscreen after user login. I did not configure this knowingly. Also i can start every application which is available on the dock. Settings, virtual box, visualstudio code and so on. After the update to 18.04 i just configure the screen frequency to 144Hz and the night mode on. And attach the dock on bottom. I later undid these customizations back to configuration before, but the dock is stil aviable on lockscreen. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-settings-daemon 3.28.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat May 5 18:30:16 2018 InstallationDate: Installed on 2018-04-08 (27 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to bionic on 2018-05-01 (3 days ago) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-08 (27 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell-extension-ubuntu-dock 0.9.1 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-05-01 (4 days ago) 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/1769383/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1802981] [NEW] Lockscreen shown dash when screen was locked
Public bug reported: I decided to leave my laptop and came back a few minutes later, and I noticed that the dash was visible from the lockscreen. Not good. Running Ubuntu 18.10 as a fresh install. Was able to quit and open applications from the dash. Uncertain if that's a security risk or not. Uncertain of how to reproduce as in what triggered it. Dash should definitely not be visible when the lockscreen is active. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gdm3 3.30.1-1ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Nov 12 15:41:14 2018 InstallationDate: Installed on 2018-11-11 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) 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) ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1802981 Title: Lockscreen shown dash when screen was locked Status in gdm3 package in Ubuntu: New Bug description: I decided to leave my laptop and came back a few minutes later, and I noticed that the dash was visible from the lockscreen. Not good. Running Ubuntu 18.10 as a fresh install. Was able to quit and open applications from the dash. Uncertain if that's a security risk or not. Uncertain of how to reproduce as in what triggered it. Dash should definitely not be visible when the lockscreen is active. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gdm3 3.30.1-1ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Nov 12 15:41:14 2018 InstallationDate: Installed on 2018-11-11 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) 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/ubuntu/+source/gdm3/+bug/1802981/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1772183] Re: [Microsoft Sculpt Ergonomic Mouse] Booting from Windows to Ubuntu causes mouse to scroll multiple lines at a time
Unfortunately I do not own a wired USB mouse to test it with. -- 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/1772183 Title: [Microsoft Sculpt Ergonomic Mouse] Booting from Windows to Ubuntu causes mouse to scroll multiple lines at a time Status in xorg package in Ubuntu: Incomplete Bug description: What happens when booting immediately from Windows to Ubuntu is that the mouse scrolls multiple lines at time. This problem doesn't happen when booting to and using Windows 10. WORKAROUND: https://sourceforge.net/projects/resetmsmice/ WORKAROUND: Once the problem has stopped in Ubuntu, avoid booting into Windows. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xserver-xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..04.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:04:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 396.24 Thu Apr 26 00:10:09 PDT 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3) ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat May 19 13:02:28 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 396.24, 4.15.0-20-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 5500 [103c:80de] Subsystem: Hewlett-Packard Company GM108M [GeForce 940M] [103c:80de] InstallationDate: Installed on 2018-04-27 (22 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180425.1) MachineType: HP HP ENVY m7 Notebook ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=f280ba9f-7dfc-4687-84f5-36a316b08404 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/02/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.49 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80DE dmi.board.vendor: HP dmi.board.version: 64.43 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.49:bd03/02/2018:svnHP:pnHPENVYm7Notebook:pvrType1ProductConfigId:rvnHP:rn80DE:rvr64.43:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV dmi.product.name: HP ENVY m7 Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1772183/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1772183] Re: [Microsoft Sculpt Ergonomic Mouse] on dual boot systems can scroll multiple lines at a time.
1) That is correct. Only rebooting into Windows will trigger the bug when you go back into Ubuntu. I've tested this just now to confirm it. 2) OK. Will take note. -- 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/1772183 Title: [Microsoft Sculpt Ergonomic Mouse] on dual boot systems can scroll multiple lines at a time. Status in xorg package in Ubuntu: Incomplete Bug description: In 16.04 and 18.04, the mouse scrolls multiple lines at time. Sometimes rebooting doesn't fix the issue. This problem doesn't happen in Windows 10. WORKAROUND: https://sourceforge.net/projects/resetmsmice/ ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xserver-xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..04.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:04:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 396.24 Thu Apr 26 00:10:09 PDT 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3) ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat May 19 13:02:28 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 396.24, 4.15.0-20-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 5500 [103c:80de] Subsystem: Hewlett-Packard Company GM108M [GeForce 940M] [103c:80de] InstallationDate: Installed on 2018-04-27 (22 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180425.1) MachineType: HP HP ENVY m7 Notebook ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=f280ba9f-7dfc-4687-84f5-36a316b08404 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/02/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.49 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80DE dmi.board.vendor: HP dmi.board.version: 64.43 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.49:bd03/02/2018:svnHP:pnHPENVYm7Notebook:pvrType1ProductConfigId:rvnHP:rn80DE:rvr64.43:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV dmi.product.name: HP ENVY m7 Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1772183/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1772183] Re: Microsoft Mice on dual boot systems can scroll multiple lines at a time.
1) The mouse model is Microsoft Sculpt Ergonomic Mouse. 2) This issue does not appear in Microsoft Windows 10, the version I have installed to my other partition. I believe from reading the comments on askububtu the bug needs a dual boot configuration to exist. 3) I don't believe I tested for this particular bug, but I noticed odd scrolling in Half Life in Steam that was only fixed by rebooting in the proper sequence. I had no clue about the depth of the bug at the time. But it definitely existed in 16.04 as well. Can't recall if it existed prior, but it wouldn't surprise me. 4) Computer is an HP envy m7-n101dx. 5) The workaround package is located here: https://sourceforge.net/projects/resetmsmice/ 6) Yeah removing and reinserting the transciever fixes it until you reboot into Windows 10 again. You don't have to do it intermittently. -- 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/1772183 Title: Microsoft Mice on dual boot systems can scroll multiple lines at a time. Status in xorg package in Ubuntu: Incomplete Bug description: Running Ubuntu 18.04. Noticed this bug in 16.04 and earlier for who knows how long. See https://askubuntu.com/questions/47100/mouse-wheel- scrolling-too-fast. Installing the workaround package or removing the transceiver appears to be a workaround for the time being. Xorg should automatically scroll normally, not multiple lines at time after rebooting. Sometimes rebooting doesn't fix the issue. Askubuntu mentions the bug dating back to Natty. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xserver-xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..04.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:04:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 396.24 Thu Apr 26 00:10:09 PDT 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3) ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat May 19 13:02:28 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 396.24, 4.15.0-20-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 5500 [103c:80de] Subsystem: Hewlett-Packard Company GM108M [GeForce 940M] [103c:80de] InstallationDate: Installed on 2018-04-27 (22 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180425.1) MachineType: HP HP ENVY m7 Notebook ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=f280ba9f-7dfc-4687-84f5-36a316b08404 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/02/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.49 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80DE dmi.board.vendor: HP dmi.board.version: 64.43 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.49:bd03/02/2018:svnHP:pnHPENVYm7Notebook:pvrType1ProductConfigId:rvnHP:rn80DE:rvr64.43:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV dmi.product.name: HP ENVY m7 Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1772183/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-packages] [Bug 1772183] Re: Microsoft Mice on dual boot systems can scroll multiple lines at a time.
** Summary changed: - Microsoft Mice on dual boot can scroll multiple lines at a time. + Microsoft Mice on dual boot systems can scroll multiple lines at a time. -- 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/1772183 Title: Microsoft Mice on dual boot systems can scroll multiple lines at a time. Status in xorg package in Ubuntu: New Bug description: Running Ubuntu 18.04. Noticed this bug in 16.04 and earlier for who knows how long. See https://askubuntu.com/questions/47100/mouse-wheel- scrolling-too-fast. Installing the workaround package or removing the transceiver appears to be a workaround for the time being. Xorg should automatically scroll normally, not multiple lines at time after rebooting. Sometimes rebooting doesn't fix the issue. Askubuntu mentions the bug dating back to Natty. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xserver-xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..04.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:04:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 396.24 Thu Apr 26 00:10:09 PDT 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3) ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat May 19 13:02:28 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 396.24, 4.15.0-20-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 5500 [103c:80de] Subsystem: Hewlett-Packard Company GM108M [GeForce 940M] [103c:80de] InstallationDate: Installed on 2018-04-27 (22 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180425.1) MachineType: HP HP ENVY m7 Notebook ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=f280ba9f-7dfc-4687-84f5-36a316b08404 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/02/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.49 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80DE dmi.board.vendor: HP dmi.board.version: 64.43 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.49:bd03/02/2018:svnHP:pnHPENVYm7Notebook:pvrType1ProductConfigId:rvnHP:rn80DE:rvr64.43:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV dmi.product.name: HP ENVY m7 Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1772183/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1772183] [NEW] Microsoft Mice on dual boot can scroll multiple lines at a time.
Public bug reported: Running Ubuntu 18.04. Noticed this bug in 16.04 and earlier for who knows how long. See https://askubuntu.com/questions/47100/mouse-wheel- scrolling-too-fast. Installing the workaround package or removing the transceiver appears to be a workaround for the time being. Xorg should automatically scroll normally, not multiple lines at time after rebooting. Sometimes rebooting doesn't fix the issue. Askubuntu mentions the bug dating back to Natty. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xserver-xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..04.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:04:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 396.24 Thu Apr 26 00:10:09 PDT 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3) ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat May 19 13:02:28 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 396.24, 4.15.0-20-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 5500 [103c:80de] Subsystem: Hewlett-Packard Company GM108M [GeForce 940M] [103c:80de] InstallationDate: Installed on 2018-04-27 (22 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180425.1) MachineType: HP HP ENVY m7 Notebook ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=f280ba9f-7dfc-4687-84f5-36a316b08404 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/02/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.49 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80DE dmi.board.vendor: HP dmi.board.version: 64.43 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.49:bd03/02/2018:svnHP:pnHPENVYm7Notebook:pvrType1ProductConfigId:rvnHP:rn80DE:rvr64.43:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV dmi.product.name: HP ENVY m7 Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 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/1772183 Title: Microsoft Mice on dual boot can scroll multiple lines at a time. Status in xorg package in Ubuntu: New Bug description: Running Ubuntu 18.04. Noticed this bug in 16.04 and earlier for who knows how long. See https://askubuntu.com/questions/47100/mouse-wheel- scrolling-too-fast. Installing the workaround package or removing the transceiver appears to be a workaround for the time being. Xorg should automatically scroll normally, not multiple lines at time after rebooting. Sometimes rebooting doesn't fix the issue. Askubuntu mentions the bug dating back to Natty. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xserver-xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..04.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:04:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 396.24 Thu Apr 26 00:10:09 PDT 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3) ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None
[Desktop-packages] [Bug 1423773] Re: Gnome-Shell don't free ram when I change a wallpaper
It does seem to increase memory usage. GNOME shell sure is leaky. Glad I have the luxury of 16GB of RAM. Still should be fixed in the LTS, IMO. Even if not high priority. -- 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/1423773 Title: Gnome-Shell don't free ram when I change a wallpaper Status in gnome-shell package in Ubuntu: Confirmed Bug description: Sorry for my bad english, here is the link to see the error by yourself: https://www.youtube.com/watch?v=O53tt-6v81Y=youtu.be To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1423773/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1448351] [NEW] Preserve job files (allow reprinting) causes UI freeze
Public bug reported: I can set this via dconf and I have no issues, but when I use the GUI to change this setting and press OK, the application freezes up and I have to force it to close. Happens on Ubuntu 15.04 currently, and it happened on 14.10 as well after some updates. I'm assuming it's an issue in this application and not CUPS because I can change it via dconf without issue. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: system-config-printer-gnome 1.5.6+20150318-0ubuntu2 Uname: Linux 4.0.0-04-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CupsErrorLog: E [24/Apr/2015:12:24:19 -0400] [Client 18] Local authentication certificate not found. E [24/Apr/2015:19:32:49 -0400] [Client 14] Local authentication certificate not found. E [24/Apr/2015:19:45:05 -0400] [Client 29] Local authentication certificate not found. CurrentDesktop: Unity Date: Fri Apr 24 19:58:36 2015 InstallationDate: Installed on 2015-04-23 (1 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: Acer Aspire X1430 PackageArchitecture: all Papersize: letter ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.0.0-04-generic root=UUID=68234429-c890-4e23-b852-c4a62ff3282d ro quiet splash vt.handoff=7 SourcePackage: system-config-printer UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/16/2011 dmi.bios.vendor: AMI dmi.bios.version: P01-C1 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Aspire X1430 dmi.board.vendor: Acer dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnAMI:bvrP01-C1:bd11/16/2011:svnAcer:pnAspireX1430:pvr:rvnAcer:rnAspireX1430:rvr:cvnAcer:ct3:cvr: dmi.product.name: Aspire X1430 dmi.sys.vendor: Acer ** Affects: system-config-printer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/1448351 Title: Preserve job files (allow reprinting) causes UI freeze Status in system-config-printer package in Ubuntu: New Bug description: I can set this via dconf and I have no issues, but when I use the GUI to change this setting and press OK, the application freezes up and I have to force it to close. Happens on Ubuntu 15.04 currently, and it happened on 14.10 as well after some updates. I'm assuming it's an issue in this application and not CUPS because I can change it via dconf without issue. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: system-config-printer-gnome 1.5.6+20150318-0ubuntu2 Uname: Linux 4.0.0-04-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CupsErrorLog: E [24/Apr/2015:12:24:19 -0400] [Client 18] Local authentication certificate not found. E [24/Apr/2015:19:32:49 -0400] [Client 14] Local authentication certificate not found. E [24/Apr/2015:19:45:05 -0400] [Client 29] Local authentication certificate not found. CurrentDesktop: Unity Date: Fri Apr 24 19:58:36 2015 InstallationDate: Installed on 2015-04-23 (1 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: Acer Aspire X1430 PackageArchitecture: all Papersize: letter ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.0.0-04-generic root=UUID=68234429-c890-4e23-b852-c4a62ff3282d ro quiet splash vt.handoff=7 SourcePackage: system-config-printer UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/16/2011 dmi.bios.vendor: AMI dmi.bios.version: P01-C1 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Aspire X1430 dmi.board.vendor: Acer dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnAMI:bvrP01-C1:bd11/16/2011:svnAcer:pnAspireX1430:pvr:rvnAcer:rnAspireX1430:rvr:cvnAcer:ct3:cvr: dmi.product.name: Aspire X1430 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1448351/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1311847] Re: Neither PrintScreen, SHIFT+PrintScreen, nor CTRL+PrintScreen keyboard shortcuts work on Trusty
xev output from PrintScreen: KeyPress event, serial 37, synthetic NO, window 0x6a1, root 0x7e, subw 0x0, time 4787314, (124,84), root:(189,598), state 0x10, keycode 218 (keysym 0xff61, Print), same_screen YES, XKeysymToKeycode returns keycode: 107 XLookupString gives 0 bytes: Keyboard layout is regular US English. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1311847 Title: Neither PrintScreen, SHIFT+PrintScreen, nor CTRL+PrintScreen keyboard shortcuts work on Trusty Status in “unity-settings-daemon” package in Ubuntu: Confirmed Bug description: Running Ubuntu 14.04 64 bit with the latest updates. Version of unity- settings-daemon is 14.04.0+14.04.20140414-0ubuntu1. Possible that this bug either affects unity-settings-daemon, gnome-screenshot, or something else. I expected PrintScreen to take a screenshot. Ditto for CTRL+PrintScreen and ALT+PrintScreen. All my settings under Keyboard Shortcuts are normal. Everything worked for every prior release of Ubuntu with the Print key taking a screenshot. Also, neither CTRL+PrintScreen nor SHIFT+PrintScreen work at all. If you reassign the keys for taking a screenshot, to any other keys, gnome-screenshot works as expected. Assigning either of those three key/key combinations to any command does not work. ALT+PrintScreen strangely enough works without issue. Running gnome-screenshot from the terminal also works without issue. Unlike the other bugs I've seen that sound similar, I do not hear a sound at all when pressing any of those three key combinations. Toggling the magic sysrq key does nothing for this issue either. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-settings-daemon 14.04.0+14.04.20140414-0ubuntu1 Uname: Linux 3.14.1-031401-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Wed Apr 23 15:13:53 2014 InstallationDate: Installed on 2014-04-17 (6 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unity-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.xdg.autostart.unity.fallback.mount.helper.desktop: [modified] mtime.conffile..etc.xdg.autostart.unity.fallback.mount.helper.desktop: 2014-04-18T11:00:48.144910 mtime.conffile..etc.xdg.autostart.unity.settings.daemon.desktop: 2014-04-18T11:00:48.144910 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1311847/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1311847] Re: Neither PrintScreen, SHIFT+PrintScreen, nor CTRL+PrintScreen keyboard shortcuts work on Trusty
Sorry for the massive delayed response. I'm also having more boot issues I want to get to the bottom of. I'll try asking around in IRC. I was sick for a little bit, too. So my response will come, but it may be a little while. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1311847 Title: Neither PrintScreen, SHIFT+PrintScreen, nor CTRL+PrintScreen keyboard shortcuts work on Trusty Status in “unity-settings-daemon” package in Ubuntu: Confirmed Bug description: Running Ubuntu 14.04 64 bit with the latest updates. Version of unity- settings-daemon is 14.04.0+14.04.20140414-0ubuntu1. Possible that this bug either affects unity-settings-daemon, gnome-screenshot, or something else. I expected PrintScreen to take a screenshot. Ditto for CTRL+PrintScreen and ALT+PrintScreen. All my settings under Keyboard Shortcuts are normal. Everything worked for every prior release of Ubuntu with the Print key taking a screenshot. Also, neither CTRL+PrintScreen nor SHIFT+PrintScreen work at all. If you reassign the keys for taking a screenshot, to any other keys, gnome-screenshot works as expected. Assigning either of those three key/key combinations to any command does not work. ALT+PrintScreen strangely enough works without issue. Running gnome-screenshot from the terminal also works without issue. Unlike the other bugs I've seen that sound similar, I do not hear a sound at all when pressing any of those three key combinations. Toggling the magic sysrq key does nothing for this issue either. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-settings-daemon 14.04.0+14.04.20140414-0ubuntu1 Uname: Linux 3.14.1-031401-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Wed Apr 23 15:13:53 2014 InstallationDate: Installed on 2014-04-17 (6 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unity-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.xdg.autostart.unity.fallback.mount.helper.desktop: [modified] mtime.conffile..etc.xdg.autostart.unity.fallback.mount.helper.desktop: 2014-04-18T11:00:48.144910 mtime.conffile..etc.xdg.autostart.unity.settings.daemon.desktop: 2014-04-18T11:00:48.144910 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1311847/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1311847] Re: Neither PrintScreen, SHIFT+PrintScreen, nor CTRL+PrintScreen keyboard shortcuts work on Trusty
Unfortunately, no, it does not work in a guest session. I honestly thought I had messed something up on my account and tried that. Doesn't work at all. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1311847 Title: Neither PrintScreen, SHIFT+PrintScreen, nor CTRL+PrintScreen keyboard shortcuts work on Trusty Status in “unity-settings-daemon” package in Ubuntu: Confirmed Bug description: Running Ubuntu 14.04 64 bit with the latest updates. Version of unity- settings-daemon is 14.04.0+14.04.20140414-0ubuntu1. Possible that this bug either affects unity-settings-daemon, gnome-screenshot, or something else. I expected PrintScreen to take a screenshot. Ditto for CTRL+PrintScreen and ALT+PrintScreen. All my settings under Keyboard Shortcuts are normal. Everything worked for every prior release of Ubuntu with the Print key taking a screenshot. Also, neither CTRL+PrintScreen nor SHIFT+PrintScreen work at all. If you reassign the keys for taking a screenshot, to any other keys, gnome-screenshot works as expected. Assigning either of those three key/key combinations to any command does not work. ALT+PrintScreen strangely enough works without issue. Running gnome-screenshot from the terminal also works without issue. Unlike the other bugs I've seen that sound similar, I do not hear a sound at all when pressing any of those three key combinations. Toggling the magic sysrq key does nothing for this issue either. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-settings-daemon 14.04.0+14.04.20140414-0ubuntu1 Uname: Linux 3.14.1-031401-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Wed Apr 23 15:13:53 2014 InstallationDate: Installed on 2014-04-17 (6 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unity-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.xdg.autostart.unity.fallback.mount.helper.desktop: [modified] mtime.conffile..etc.xdg.autostart.unity.fallback.mount.helper.desktop: 2014-04-18T11:00:48.144910 mtime.conffile..etc.xdg.autostart.unity.settings.daemon.desktop: 2014-04-18T11:00:48.144910 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1311847/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1311847] [NEW] Neither Print, SHIFT+Print, nor CTRL+Print keyboard shortcuts work on Trusty
Public bug reported: Running Ubuntu 14.04 64 bit with the latest updates. Version of unity- settings-daemon is 14.04.0+14.04.20140414-0ubuntu1. Possible that this bug either affects unity-settings-daemon, gnome-screenshot, or something else. I expected Print to take a screenshot. Ditto for CTRL+Print and ALT+Print. All my settings under Keyboard Shortcuts are normal. Everything worked for every prior release of Ubuntu with the Print key taking a screenshot. Also, neither CTRL+Print nor SHIFT+Print work at all. If you reassign the keys for taking a screenshot, to any other keys, gnome-screenshot works as expected. Assigning either of those three key/key combinations to any command does not work. ALT+Print strangely enough works without issue. Running gnome-screenshot from the terminal also works without issue. Unlike the other bugs I've seen that sound similar, I do not hear a sound at all when pressing any of those three key combinations. Toggling the magic sysrq key does nothing for this issue either. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-settings-daemon 14.04.0+14.04.20140414-0ubuntu1 Uname: Linux 3.14.1-031401-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Wed Apr 23 15:13:53 2014 InstallationDate: Installed on 2014-04-17 (6 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unity-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.xdg.autostart.unity.fallback.mount.helper.desktop: [modified] mtime.conffile..etc.xdg.autostart.unity.fallback.mount.helper.desktop: 2014-04-18T11:00:48.144910 mtime.conffile..etc.xdg.autostart.unity.settings.daemon.desktop: 2014-04-18T11:00:48.144910 ** Affects: unity-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1311847 Title: Neither Print, SHIFT+Print, nor CTRL+Print keyboard shortcuts work on Trusty Status in “unity-settings-daemon” package in Ubuntu: New Bug description: Running Ubuntu 14.04 64 bit with the latest updates. Version of unity- settings-daemon is 14.04.0+14.04.20140414-0ubuntu1. Possible that this bug either affects unity-settings-daemon, gnome-screenshot, or something else. I expected Print to take a screenshot. Ditto for CTRL+Print and ALT+Print. All my settings under Keyboard Shortcuts are normal. Everything worked for every prior release of Ubuntu with the Print key taking a screenshot. Also, neither CTRL+Print nor SHIFT+Print work at all. If you reassign the keys for taking a screenshot, to any other keys, gnome-screenshot works as expected. Assigning either of those three key/key combinations to any command does not work. ALT+Print strangely enough works without issue. Running gnome-screenshot from the terminal also works without issue. Unlike the other bugs I've seen that sound similar, I do not hear a sound at all when pressing any of those three key combinations. Toggling the magic sysrq key does nothing for this issue either. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-settings-daemon 14.04.0+14.04.20140414-0ubuntu1 Uname: Linux 3.14.1-031401-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Wed Apr 23 15:13:53 2014 InstallationDate: Installed on 2014-04-17 (6 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unity-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.xdg.autostart.unity.fallback.mount.helper.desktop: [modified] mtime.conffile..etc.xdg.autostart.unity.fallback.mount.helper.desktop: 2014-04-18T11:00:48.144910 mtime.conffile..etc.xdg.autostart.unity.settings.daemon.desktop: 2014-04-18T11:00:48.144910 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1311847/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1311847] Re: Neither Print, SHIFT+Print, nor CTRL+Print keyboard shortcuts work on Trusty
Also this only effects my HP dv7-4285dx laptop after fresh install, and my desktop seems to work fine. I Googled and saw that several KDE users some months ago had a similar issue. So maybe it's related to X, systemd, or something else at the low level? A lot of the users reporting the issue reported that they experienced it only on certain machines, and in every case it was a HP laptop in the dv-whatnot series. This may help trace the problem down. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1311847 Title: Neither Print, SHIFT+Print, nor CTRL+Print keyboard shortcuts work on Trusty Status in “unity-settings-daemon” package in Ubuntu: New Bug description: Running Ubuntu 14.04 64 bit with the latest updates. Version of unity- settings-daemon is 14.04.0+14.04.20140414-0ubuntu1. Possible that this bug either affects unity-settings-daemon, gnome-screenshot, or something else. I expected Print to take a screenshot. Ditto for CTRL+Print and ALT+Print. All my settings under Keyboard Shortcuts are normal. Everything worked for every prior release of Ubuntu with the Print key taking a screenshot. Also, neither CTRL+Print nor SHIFT+Print work at all. If you reassign the keys for taking a screenshot, to any other keys, gnome-screenshot works as expected. Assigning either of those three key/key combinations to any command does not work. ALT+Print strangely enough works without issue. Running gnome-screenshot from the terminal also works without issue. Unlike the other bugs I've seen that sound similar, I do not hear a sound at all when pressing any of those three key combinations. Toggling the magic sysrq key does nothing for this issue either. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-settings-daemon 14.04.0+14.04.20140414-0ubuntu1 Uname: Linux 3.14.1-031401-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Wed Apr 23 15:13:53 2014 InstallationDate: Installed on 2014-04-17 (6 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unity-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.xdg.autostart.unity.fallback.mount.helper.desktop: [modified] mtime.conffile..etc.xdg.autostart.unity.fallback.mount.helper.desktop: 2014-04-18T11:00:48.144910 mtime.conffile..etc.xdg.autostart.unity.settings.daemon.desktop: 2014-04-18T11:00:48.144910 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1311847/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1311847] Re: Neither PrintScreen, SHIFT+PrintScreen, nor CTRL+PrintScreen keyboard shortcuts work on Trusty
** Summary changed: - Neither Print, SHIFT+Print, nor CTRL+Print keyboard shortcuts work on Trusty + Neither PrintScreen, SHIFT+PrintScreen, nor CTRL+PrintScreen keyboard shortcuts work on Trusty ** Description changed: Running Ubuntu 14.04 64 bit with the latest updates. Version of unity- settings-daemon is 14.04.0+14.04.20140414-0ubuntu1. Possible that this bug either affects unity-settings-daemon, gnome-screenshot, or something else. - I expected Print to take a screenshot. Ditto for CTRL+Print and - ALT+Print. All my settings under Keyboard Shortcuts are normal. + I expected PrintScreen to take a screenshot. Ditto for CTRL+PrintScreen + and ALT+PrintScreen. All my settings under Keyboard Shortcuts are + normal. Everything worked for every prior release of Ubuntu with the Print key - taking a screenshot. Also, neither CTRL+Print nor SHIFT+Print work at - all. If you reassign the keys for taking a screenshot, to any other - keys, gnome-screenshot works as expected. Assigning either of those - three key/key combinations to any command does not work. ALT+Print - strangely enough works without issue. Running gnome-screenshot from the - terminal also works without issue. Unlike the other bugs I've seen that - sound similar, I do not hear a sound at all when pressing any of those - three key combinations. Toggling the magic sysrq key does nothing for - this issue either. + taking a screenshot. Also, neither CTRL+PrintScreen nor + SHIFT+PrintScreen work at all. If you reassign the keys for taking a + screenshot, to any other keys, gnome-screenshot works as expected. + Assigning either of those three key/key combinations to any command does + not work. ALT+PrintScreen strangely enough works without issue. Running + gnome-screenshot from the terminal also works without issue. Unlike the + other bugs I've seen that sound similar, I do not hear a sound at all + when pressing any of those three key combinations. Toggling the magic + sysrq key does nothing for this issue either. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-settings-daemon 14.04.0+14.04.20140414-0ubuntu1 Uname: Linux 3.14.1-031401-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Wed Apr 23 15:13:53 2014 InstallationDate: Installed on 2014-04-17 (6 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) ProcEnviron: - LANGUAGE=en_US - PATH=(custom, no user) - XDG_RUNTIME_DIR=set - LANG=en_US.UTF-8 - SHELL=/bin/bash + LANGUAGE=en_US + PATH=(custom, no user) + XDG_RUNTIME_DIR=set + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: unity-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.xdg.autostart.unity.fallback.mount.helper.desktop: [modified] mtime.conffile..etc.xdg.autostart.unity.fallback.mount.helper.desktop: 2014-04-18T11:00:48.144910 mtime.conffile..etc.xdg.autostart.unity.settings.daemon.desktop: 2014-04-18T11:00:48.144910 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1311847 Title: Neither PrintScreen, SHIFT+PrintScreen, nor CTRL+PrintScreen keyboard shortcuts work on Trusty Status in “unity-settings-daemon” package in Ubuntu: New Bug description: Running Ubuntu 14.04 64 bit with the latest updates. Version of unity- settings-daemon is 14.04.0+14.04.20140414-0ubuntu1. Possible that this bug either affects unity-settings-daemon, gnome-screenshot, or something else. I expected PrintScreen to take a screenshot. Ditto for CTRL+PrintScreen and ALT+PrintScreen. All my settings under Keyboard Shortcuts are normal. Everything worked for every prior release of Ubuntu with the Print key taking a screenshot. Also, neither CTRL+PrintScreen nor SHIFT+PrintScreen work at all. If you reassign the keys for taking a screenshot, to any other keys, gnome-screenshot works as expected. Assigning either of those three key/key combinations to any command does not work. ALT+PrintScreen strangely enough works without issue. Running gnome-screenshot from the terminal also works without issue. Unlike the other bugs I've seen that sound similar, I do not hear a sound at all when pressing any of those three key combinations. Toggling the magic sysrq key does nothing for this issue either. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-settings-daemon 14.04.0+14.04.20140414-0ubuntu1 Uname: Linux 3.14.1-031401-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Wed Apr 23 15:13:53 2014 InstallationDate: Installed on 2014-04-17 (6 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8
[Desktop-packages] [Bug 1263412] Re: strange/broken global-menu integration for AisleRiot
I can confirm this on both my Ubuntu 13.10 install and a live CD of 14.04. It's very annoying to see two menu bars. Inconsistent to the UI. I suggest hiding one of them for now at least, and if anyone has time make it so the GTK2 style menu bar is in the top panel in the global menu. Please remove the Gnome 3 menu. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to aisleriot in Ubuntu. https://bugs.launchpad.net/bugs/1263412 Title: strange/broken global-menu integration for AisleRiot Status in “aisleriot” package in Ubuntu: Confirmed Bug description: As the title states the global-menu integration is rather strange/broken. The Gnome 3 menu is displayed in the global-menu but their is also the normal game menu which is displayed in the gnome 2 style (in window). I guess it was meant to replace the Gnome 3 menu with an global-menu integrated version of the normal menu. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: aisleriot 1:3.8.0-2 ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Sat Dec 21 23:57:26 2013 InstallationDate: Installed on 2013-10-19 (63 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: aisleriot UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aisleriot/+bug/1263412/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1244499] [NEW] Minor inconsistency in UI under Appearance with regards to the auto-hide functionality in Saucy
Public bug reported: Minor bug. I've noticed that when I toggle on auto hide and toggle it off under Appearance and under the Behavior tab, I can still adjust the reveal location and reveal sensitivity even with the option to auto- hide the launcher toggled off again. Only happens after a toggle on and off. The behavior should be to grey out the options once disabled again and not allow the user to select them until the auto-hide option is enabled again. Running the latest updates on 64 bit Saucy. Screenshots coming up. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-control-center 1:3.6.3-0ubuntu45 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.1 Architecture: amd64 Date: Thu Oct 24 22:15:55 2013 InstallationDate: Installed on 2013-10-17 (7 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: activity-log-manager 0.9.7-0ubuntu4 deja-dup 27.3.1-0ubuntu1 gnome-control-center-datetime 13.10.0+13.10.20131016.2-0ubuntu1 gnome-control-center-signon 0.1.7~+13.10.20130724.1-0ubuntu1 gnome-control-center-unity1.3+13.10.20131004-0ubuntu1 ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug package-from-proposed saucy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1244499 Title: Minor inconsistency in UI under Appearance with regards to the auto- hide functionality in Saucy Status in “gnome-control-center” package in Ubuntu: New Bug description: Minor bug. I've noticed that when I toggle on auto hide and toggle it off under Appearance and under the Behavior tab, I can still adjust the reveal location and reveal sensitivity even with the option to auto-hide the launcher toggled off again. Only happens after a toggle on and off. The behavior should be to grey out the options once disabled again and not allow the user to select them until the auto- hide option is enabled again. Running the latest updates on 64 bit Saucy. Screenshots coming up. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-control-center 1:3.6.3-0ubuntu45 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.1 Architecture: amd64 Date: Thu Oct 24 22:15:55 2013 InstallationDate: Installed on 2013-10-17 (7 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: activity-log-manager 0.9.7-0ubuntu4 deja-dup 27.3.1-0ubuntu1 gnome-control-center-datetime 13.10.0+13.10.20131016.2-0ubuntu1 gnome-control-center-signon 0.1.7~+13.10.20130724.1-0ubuntu1 gnome-control-center-unity1.3+13.10.20131004-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1244499/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1244499] Re: Minor inconsistency in UI under Appearance with regard to the suto-hide functionality
** Attachment added: aftertwotoggles.png https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1244499/+attachment/3890561/+files/aftertwotoggles.png ** Summary changed: - Minor inconsistency in UI under Appearance with regard to the suto-hide functionality + Minor inconsistency in UI under Appearance with regard to the auto-hide functionality in Saucy ** Summary changed: - Minor inconsistency in UI under Appearance with regard to the auto-hide functionality in Saucy + Minor inconsistency in UI under Appearance with regards to the auto-hide functionality in Saucy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1244499 Title: Minor inconsistency in UI under Appearance with regards to the auto- hide functionality in Saucy Status in “gnome-control-center” package in Ubuntu: New Bug description: Minor bug. I've noticed that when I toggle on auto hide and toggle it off under Appearance and under the Behavior tab, I can still adjust the reveal location and reveal sensitivity even with the option to auto-hide the launcher toggled off again. Only happens after a toggle on and off. The behavior should be to grey out the options once disabled again and not allow the user to select them until the auto- hide option is enabled again. Running the latest updates on 64 bit Saucy. Screenshots coming up. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-control-center 1:3.6.3-0ubuntu45 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.1 Architecture: amd64 Date: Thu Oct 24 22:15:55 2013 InstallationDate: Installed on 2013-10-17 (7 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: activity-log-manager 0.9.7-0ubuntu4 deja-dup 27.3.1-0ubuntu1 gnome-control-center-datetime 13.10.0+13.10.20131016.2-0ubuntu1 gnome-control-center-signon 0.1.7~+13.10.20130724.1-0ubuntu1 gnome-control-center-unity1.3+13.10.20131004-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1244499/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1244499] Re: Minor inconsistency in UI under Appearance with regard to the suto-hide functionality
** Attachment added: normalbehavior.png https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1244499/+attachment/3890560/+files/normalbehavior.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1244499 Title: Minor inconsistency in UI under Appearance with regards to the auto- hide functionality in Saucy Status in “gnome-control-center” package in Ubuntu: New Bug description: Minor bug. I've noticed that when I toggle on auto hide and toggle it off under Appearance and under the Behavior tab, I can still adjust the reveal location and reveal sensitivity even with the option to auto-hide the launcher toggled off again. Only happens after a toggle on and off. The behavior should be to grey out the options once disabled again and not allow the user to select them until the auto- hide option is enabled again. Running the latest updates on 64 bit Saucy. Screenshots coming up. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-control-center 1:3.6.3-0ubuntu45 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.1 Architecture: amd64 Date: Thu Oct 24 22:15:55 2013 InstallationDate: Installed on 2013-10-17 (7 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: activity-log-manager 0.9.7-0ubuntu4 deja-dup 27.3.1-0ubuntu1 gnome-control-center-datetime 13.10.0+13.10.20131016.2-0ubuntu1 gnome-control-center-signon 0.1.7~+13.10.20130724.1-0ubuntu1 gnome-control-center-unity1.3+13.10.20131004-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1244499/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1204592] Re: LibreOffice unity menus populate sluggishly the first time
Ditto it effects me. Meaning it probably effects all end users on 4.1 and later versions. Or in the rare case someones ports this bug-creating patch to an older version. If the bug is simple to fix, please fix it ASAP. Know you all are busy. In the mean time, I'm going to use some third-party software (Ubuntu Tweak) to edit the quicklists and see if I can get a workaround going. If it messes stuff up even worse, I'll write the results in hopes that it helps you all pinpoint the issue further. It's all good since I've dug the computer out of WAY deeper holes before. Plus, this software has a button to reset Unity to defaults. Have found it extremely useful before. -- 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/1204592 Title: LibreOffice unity menus populate sluggishly the first time Status in “libreoffice” package in Ubuntu: Confirmed Bug description: As a side effect of the upstreamed fix for bug 1085169 the unity menu takes some time to be populated. This will be observed with LibreOffice 4.1.0 (or older versions that have the fix backported). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1204592/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1204592] Re: LibreOffice unity menus populate sluggishly the first time
Found a partial workaround. (Note this only works for launcher-locked LibreOffice applications. It does not fix other user accounts nor does it fix unlocked LibreOffice applications). If anyone has Ubuntu Tweak installed, under the Admin tab is a Quicklists Editor. There you can see several LibreOffice applications (by default, Writer, Calc, and Impress) that are in the left-hand column of the program. Click on them one at a time and simply add the name New Document (without quotes) to each one. Strangely, the command is already correct. Now, when you are done with one LO application be sure to click Save. Otherwise progress will be lost. Do this for each one (by default there are three) and (most) of the problems from this bug should be alleviated. If anyone else has a better idea for a workaround (such as a way to edit the quicklists for every LibreOffice application for every user on the installation), let me know by posting a comment. I'm sure others will find it useful if they stumble across this post as well. -- 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/1204592 Title: LibreOffice unity menus populate sluggishly the first time Status in “libreoffice” package in Ubuntu: Confirmed Bug description: As a side effect of the upstreamed fix for bug 1085169 the unity menu takes some time to be populated. This will be observed with LibreOffice 4.1.0 (or older versions that have the fix backported). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1204592/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1196668] Re: VNC crashes on startup on Raring
** Attachment added: Full stack trace. https://bugs.launchpad.net/ubuntu/+source/vino/+bug/1196668/+attachment/3723657/+files/_usr_lib_vino_vino-server.1000.crash -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vino in Ubuntu. https://bugs.launchpad.net/bugs/1196668 Title: VNC crashes on startup on Raring Status in GNOME Remote Desktop: New Status in “vino” package in Ubuntu: New Bug description: Vino-server is what is impacted. I believe what triggers this is related to customizing via vino-preferences. Afterwards, vino will not launch the server. A similar bug was reported on Oneiric and older, but I believe the bug report was marked as invalid due to it not having nearly enough info. The notification area icon will not stay. It will appear after startup, and quickly disappear. VNC is COMPLETELY UNUSABLE in every FOSS application I've tried on Ubuntu 13.04. From the GNOME Remote Desktop Client to Remnima, nothing works. Worse yet, none of the proprietary clients/servers such as Splashtop work either. The only remote desktop tool working is Teamviewer, and that runs under WINE. So remote desktop is borked on both my desktop and laptop. I will copy and paste some debug below: /usr/lib/vino/vino-server --sm-disable (vino-server:27458): EggSMClient-CRITICAL **: egg_sm_client_set_mode: assertion `global_client == NULL || global_client_mode == EGG_SM_CLIENT_MODE_DISABLED' failed 01/07/2013 03:01:26 PM Autoprobing TCP port in (all) network interface 01/07/2013 03:01:26 PM Listening IPv6://[::]:5900 01/07/2013 03:01:26 PM Listening IPv4://0.0.0.0:5900 01/07/2013 03:01:26 PM Autoprobing selected port 5900 01/07/2013 03:01:26 PM Advertising security type: 'TLS' (18) 01/07/2013 03:01:26 PM Re-binding socket to listen for VNC connections on TCP port 5900 in (all) interface 01/07/2013 03:01:26 PM Listening IPv6://[::]:5900 01/07/2013 03:01:26 PM Listening IPv4://0.0.0.0:5900 01/07/2013 03:01:26 PM Clearing securityTypes 01/07/2013 03:01:26 PM Advertising security type: 'TLS' (18) 01/07/2013 03:01:26 PM Clearing securityTypes 01/07/2013 03:01:26 PM Advertising security type: 'TLS' (18) 01/07/2013 03:01:26 PM Advertising authentication type: 'No Authentication' (1) 01/07/2013 03:01:26 PM Re-binding socket to listen for VNC connections on TCP port 5900 in (all) interface 01/07/2013 03:01:26 PM Listening IPv6://[::]:5900 01/07/2013 03:01:26 PM Listening IPv4://0.0.0.0:5900 01/07/2013 03:01:26 PM Clearing securityTypes 01/07/2013 03:01:26 PM Clearing authTypes 01/07/2013 03:01:26 PM Advertising security type: 'TLS' (18) 01/07/2013 03:01:26 PM Advertising authentication type: 'VNC Authentication' (2) 01/07/2013 03:01:26 PM Clearing securityTypes 01/07/2013 03:01:26 PM Clearing authTypes 01/07/2013 03:01:26 PM Advertising security type: 'TLS' (18) 01/07/2013 03:01:26 PM Advertising authentication type: 'VNC Authentication' (2) 01/07/2013 03:01:26 PM Advertising security type: 'VNC Authentication' (2) (vino-server:27458): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're its parent. *** Error in `/usr/lib/vino/vino-server': free(): invalid pointer: 0x7fdfefbf5798 *** === Backtrace: = /lib/x86_64-linux-gnu/libc.so.6(+0x80a46)[0x7fdfef8b4a46] /usr/lib/libminiupnpc.so.8(FreeUPNPUrls+0x11)[0x7fdff2494add] /usr/lib/vino/vino-server[0x4165e5] /usr/lib/vino/vino-server[0x41666d] /usr/lib/vino/vino-server[0x416c00] /usr/lib/vino/vino-server[0x416dae] /lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x49b1b)[0x7fdfefc45b1b] /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x135)[0x7fdfefc44f05] /lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x49248)[0x7fdfefc45248] /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_loop_run+0x6a)[0x7fdfefc456ba] /usr/lib/vino/vino-server[0x40bdb2] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)[0x7fdfef855ea5] /usr/lib/vino/vino-server[0x40be99] === Memory map: 0040-00446000 r-xp 08:06 9420 /usr/lib/vino/vino-server 00646000-00647000 r--p 00046000 08:06 9420 /usr/lib/vino/vino-server 00647000-00649000 rw-p 00047000 08:06 9420 /usr/lib/vino/vino-server 00649000-00656000 rw-p 00:00 0 01c67000-01e19000 rw-p 00:00 0 [heap] 7fdfd400-7fdfd4022000 rw-p 00:00 0 7fdfd4022000-7fdfd800 ---p 00:00 0 7fdfd800-7fdfd8022000 rw-p 00:00 0 7fdfd8022000-7fdfdc00 ---p 00:00 0 7fdfdedc-7fdfdedc5000 r-xp 08:06 131713 /usr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0/menuproxies/libappmenu.so 7fdfdedc5000-7fdfdefc4000 ---p 5000 08:06 131713
[Desktop-packages] [Bug 1196668] Re: VNC crashes on startup on Raring
This bug has been confirmed as specific to the patched version of Vino that Ubuntu uses. So the ball is now completely in Ubuntu's court. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vino in Ubuntu. https://bugs.launchpad.net/bugs/1196668 Title: VNC crashes on startup on Raring Status in GNOME Remote Desktop: New Status in “vino” package in Ubuntu: New Bug description: Vino-server is what is impacted. I believe what triggers this is related to customizing via vino-preferences. Afterwards, vino will not launch the server. A similar bug was reported on Oneiric and older, but I believe the bug report was marked as invalid due to it not having nearly enough info. The notification area icon will not stay. It will appear after startup, and quickly disappear. VNC is COMPLETELY UNUSABLE in every FOSS application I've tried on Ubuntu 13.04. From the GNOME Remote Desktop Client to Remnima, nothing works. Worse yet, none of the proprietary clients/servers such as Splashtop work either. The only remote desktop tool working is Teamviewer, and that runs under WINE. So remote desktop is borked on both my desktop and laptop. I will copy and paste some debug below: /usr/lib/vino/vino-server --sm-disable (vino-server:27458): EggSMClient-CRITICAL **: egg_sm_client_set_mode: assertion `global_client == NULL || global_client_mode == EGG_SM_CLIENT_MODE_DISABLED' failed 01/07/2013 03:01:26 PM Autoprobing TCP port in (all) network interface 01/07/2013 03:01:26 PM Listening IPv6://[::]:5900 01/07/2013 03:01:26 PM Listening IPv4://0.0.0.0:5900 01/07/2013 03:01:26 PM Autoprobing selected port 5900 01/07/2013 03:01:26 PM Advertising security type: 'TLS' (18) 01/07/2013 03:01:26 PM Re-binding socket to listen for VNC connections on TCP port 5900 in (all) interface 01/07/2013 03:01:26 PM Listening IPv6://[::]:5900 01/07/2013 03:01:26 PM Listening IPv4://0.0.0.0:5900 01/07/2013 03:01:26 PM Clearing securityTypes 01/07/2013 03:01:26 PM Advertising security type: 'TLS' (18) 01/07/2013 03:01:26 PM Clearing securityTypes 01/07/2013 03:01:26 PM Advertising security type: 'TLS' (18) 01/07/2013 03:01:26 PM Advertising authentication type: 'No Authentication' (1) 01/07/2013 03:01:26 PM Re-binding socket to listen for VNC connections on TCP port 5900 in (all) interface 01/07/2013 03:01:26 PM Listening IPv6://[::]:5900 01/07/2013 03:01:26 PM Listening IPv4://0.0.0.0:5900 01/07/2013 03:01:26 PM Clearing securityTypes 01/07/2013 03:01:26 PM Clearing authTypes 01/07/2013 03:01:26 PM Advertising security type: 'TLS' (18) 01/07/2013 03:01:26 PM Advertising authentication type: 'VNC Authentication' (2) 01/07/2013 03:01:26 PM Clearing securityTypes 01/07/2013 03:01:26 PM Clearing authTypes 01/07/2013 03:01:26 PM Advertising security type: 'TLS' (18) 01/07/2013 03:01:26 PM Advertising authentication type: 'VNC Authentication' (2) 01/07/2013 03:01:26 PM Advertising security type: 'VNC Authentication' (2) (vino-server:27458): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're its parent. *** Error in `/usr/lib/vino/vino-server': free(): invalid pointer: 0x7fdfefbf5798 *** === Backtrace: = /lib/x86_64-linux-gnu/libc.so.6(+0x80a46)[0x7fdfef8b4a46] /usr/lib/libminiupnpc.so.8(FreeUPNPUrls+0x11)[0x7fdff2494add] /usr/lib/vino/vino-server[0x4165e5] /usr/lib/vino/vino-server[0x41666d] /usr/lib/vino/vino-server[0x416c00] /usr/lib/vino/vino-server[0x416dae] /lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x49b1b)[0x7fdfefc45b1b] /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x135)[0x7fdfefc44f05] /lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x49248)[0x7fdfefc45248] /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_loop_run+0x6a)[0x7fdfefc456ba] /usr/lib/vino/vino-server[0x40bdb2] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)[0x7fdfef855ea5] /usr/lib/vino/vino-server[0x40be99] === Memory map: 0040-00446000 r-xp 08:06 9420 /usr/lib/vino/vino-server 00646000-00647000 r--p 00046000 08:06 9420 /usr/lib/vino/vino-server 00647000-00649000 rw-p 00047000 08:06 9420 /usr/lib/vino/vino-server 00649000-00656000 rw-p 00:00 0 01c67000-01e19000 rw-p 00:00 0 [heap] 7fdfd400-7fdfd4022000 rw-p 00:00 0 7fdfd4022000-7fdfd800 ---p 00:00 0 7fdfd800-7fdfd8022000 rw-p 00:00 0 7fdfd8022000-7fdfdc00 ---p 00:00 0 7fdfdedc-7fdfdedc5000 r-xp 08:06 131713 /usr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0/menuproxies/libappmenu.so 7fdfdedc5000-7fdfdefc4000 ---p 5000 08:06 131713 /usr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0/menuproxies/libappmenu.so
[Desktop-packages] [Bug 1196668] Re: VNC crashes on startup on Raring
I promise a $20 bounty to whomever fixes this bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vino in Ubuntu. https://bugs.launchpad.net/bugs/1196668 Title: VNC crashes on startup on Raring Status in GNOME Remote Desktop: New Status in “vino” package in Ubuntu: New Bug description: Vino-server is what is impacted. I believe what triggers this is related to customizing via vino-preferences. Afterwards, vino will not launch the server. A similar bug was reported on Oneiric and older, but I believe the bug report was marked as invalid due to it not having nearly enough info. The notification area icon will not stay. It will appear after startup, and quickly disappear. VNC is COMPLETELY UNUSABLE in every FOSS application I've tried on Ubuntu 13.04. From the GNOME Remote Desktop Client to Remnima, nothing works. Worse yet, none of the proprietary clients/servers such as Splashtop work either. The only remote desktop tool working is Teamviewer, and that runs under WINE. So remote desktop is borked on both my desktop and laptop. I will copy and paste some debug below: /usr/lib/vino/vino-server --sm-disable (vino-server:27458): EggSMClient-CRITICAL **: egg_sm_client_set_mode: assertion `global_client == NULL || global_client_mode == EGG_SM_CLIENT_MODE_DISABLED' failed 01/07/2013 03:01:26 PM Autoprobing TCP port in (all) network interface 01/07/2013 03:01:26 PM Listening IPv6://[::]:5900 01/07/2013 03:01:26 PM Listening IPv4://0.0.0.0:5900 01/07/2013 03:01:26 PM Autoprobing selected port 5900 01/07/2013 03:01:26 PM Advertising security type: 'TLS' (18) 01/07/2013 03:01:26 PM Re-binding socket to listen for VNC connections on TCP port 5900 in (all) interface 01/07/2013 03:01:26 PM Listening IPv6://[::]:5900 01/07/2013 03:01:26 PM Listening IPv4://0.0.0.0:5900 01/07/2013 03:01:26 PM Clearing securityTypes 01/07/2013 03:01:26 PM Advertising security type: 'TLS' (18) 01/07/2013 03:01:26 PM Clearing securityTypes 01/07/2013 03:01:26 PM Advertising security type: 'TLS' (18) 01/07/2013 03:01:26 PM Advertising authentication type: 'No Authentication' (1) 01/07/2013 03:01:26 PM Re-binding socket to listen for VNC connections on TCP port 5900 in (all) interface 01/07/2013 03:01:26 PM Listening IPv6://[::]:5900 01/07/2013 03:01:26 PM Listening IPv4://0.0.0.0:5900 01/07/2013 03:01:26 PM Clearing securityTypes 01/07/2013 03:01:26 PM Clearing authTypes 01/07/2013 03:01:26 PM Advertising security type: 'TLS' (18) 01/07/2013 03:01:26 PM Advertising authentication type: 'VNC Authentication' (2) 01/07/2013 03:01:26 PM Clearing securityTypes 01/07/2013 03:01:26 PM Clearing authTypes 01/07/2013 03:01:26 PM Advertising security type: 'TLS' (18) 01/07/2013 03:01:26 PM Advertising authentication type: 'VNC Authentication' (2) 01/07/2013 03:01:26 PM Advertising security type: 'VNC Authentication' (2) (vino-server:27458): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're its parent. *** Error in `/usr/lib/vino/vino-server': free(): invalid pointer: 0x7fdfefbf5798 *** === Backtrace: = /lib/x86_64-linux-gnu/libc.so.6(+0x80a46)[0x7fdfef8b4a46] /usr/lib/libminiupnpc.so.8(FreeUPNPUrls+0x11)[0x7fdff2494add] /usr/lib/vino/vino-server[0x4165e5] /usr/lib/vino/vino-server[0x41666d] /usr/lib/vino/vino-server[0x416c00] /usr/lib/vino/vino-server[0x416dae] /lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x49b1b)[0x7fdfefc45b1b] /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x135)[0x7fdfefc44f05] /lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x49248)[0x7fdfefc45248] /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_loop_run+0x6a)[0x7fdfefc456ba] /usr/lib/vino/vino-server[0x40bdb2] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)[0x7fdfef855ea5] /usr/lib/vino/vino-server[0x40be99] === Memory map: 0040-00446000 r-xp 08:06 9420 /usr/lib/vino/vino-server 00646000-00647000 r--p 00046000 08:06 9420 /usr/lib/vino/vino-server 00647000-00649000 rw-p 00047000 08:06 9420 /usr/lib/vino/vino-server 00649000-00656000 rw-p 00:00 0 01c67000-01e19000 rw-p 00:00 0 [heap] 7fdfd400-7fdfd4022000 rw-p 00:00 0 7fdfd4022000-7fdfd800 ---p 00:00 0 7fdfd800-7fdfd8022000 rw-p 00:00 0 7fdfd8022000-7fdfdc00 ---p 00:00 0 7fdfdedc-7fdfdedc5000 r-xp 08:06 131713 /usr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0/menuproxies/libappmenu.so 7fdfdedc5000-7fdfdefc4000 ---p 5000 08:06 131713 /usr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0/menuproxies/libappmenu.so 7fdfdefc4000-7fdfdefc5000 r--p 4000 08:06 131713
[Desktop-packages] [Bug 1196668] Re: VNC crashes on startup on Raring
apport information ** Tags added: apport-collected ** Description changed: Vino-server is what is impacted. I believe what triggers this is related to customizing via vino-preferences. Afterwards, vino will not launch the server. A similar bug was reported on Oneiric and older, but I believe the bug report was marked as invalid due to it not having nearly enough info. The notification area icon will not stay. It will appear after startup, and quickly disappear. VNC is COMPLETELY UNUSABLE in every FOSS application I've tried on Ubuntu 13.04. From the GNOME Remote Desktop Client to Remnima, nothing works. Worse yet, none of the proprietary clients/servers such as Splashtop work either. The only remote desktop tool working is Teamviewer, and that runs under WINE. So remote desktop is borked on both my desktop and laptop. I will copy and paste some debug below: /usr/lib/vino/vino-server --sm-disable (vino-server:27458): EggSMClient-CRITICAL **: egg_sm_client_set_mode: assertion `global_client == NULL || global_client_mode == EGG_SM_CLIENT_MODE_DISABLED' failed 01/07/2013 03:01:26 PM Autoprobing TCP port in (all) network interface 01/07/2013 03:01:26 PM Listening IPv6://[::]:5900 01/07/2013 03:01:26 PM Listening IPv4://0.0.0.0:5900 01/07/2013 03:01:26 PM Autoprobing selected port 5900 01/07/2013 03:01:26 PM Advertising security type: 'TLS' (18) 01/07/2013 03:01:26 PM Re-binding socket to listen for VNC connections on TCP port 5900 in (all) interface 01/07/2013 03:01:26 PM Listening IPv6://[::]:5900 01/07/2013 03:01:26 PM Listening IPv4://0.0.0.0:5900 01/07/2013 03:01:26 PM Clearing securityTypes 01/07/2013 03:01:26 PM Advertising security type: 'TLS' (18) 01/07/2013 03:01:26 PM Clearing securityTypes 01/07/2013 03:01:26 PM Advertising security type: 'TLS' (18) 01/07/2013 03:01:26 PM Advertising authentication type: 'No Authentication' (1) 01/07/2013 03:01:26 PM Re-binding socket to listen for VNC connections on TCP port 5900 in (all) interface 01/07/2013 03:01:26 PM Listening IPv6://[::]:5900 01/07/2013 03:01:26 PM Listening IPv4://0.0.0.0:5900 01/07/2013 03:01:26 PM Clearing securityTypes 01/07/2013 03:01:26 PM Clearing authTypes 01/07/2013 03:01:26 PM Advertising security type: 'TLS' (18) 01/07/2013 03:01:26 PM Advertising authentication type: 'VNC Authentication' (2) 01/07/2013 03:01:26 PM Clearing securityTypes 01/07/2013 03:01:26 PM Clearing authTypes 01/07/2013 03:01:26 PM Advertising security type: 'TLS' (18) 01/07/2013 03:01:26 PM Advertising authentication type: 'VNC Authentication' (2) 01/07/2013 03:01:26 PM Advertising security type: 'VNC Authentication' (2) (vino-server:27458): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're its parent. *** Error in `/usr/lib/vino/vino-server': free(): invalid pointer: 0x7fdfefbf5798 *** === Backtrace: = /lib/x86_64-linux-gnu/libc.so.6(+0x80a46)[0x7fdfef8b4a46] /usr/lib/libminiupnpc.so.8(FreeUPNPUrls+0x11)[0x7fdff2494add] /usr/lib/vino/vino-server[0x4165e5] /usr/lib/vino/vino-server[0x41666d] /usr/lib/vino/vino-server[0x416c00] /usr/lib/vino/vino-server[0x416dae] /lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x49b1b)[0x7fdfefc45b1b] /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x135)[0x7fdfefc44f05] /lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x49248)[0x7fdfefc45248] /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_loop_run+0x6a)[0x7fdfefc456ba] /usr/lib/vino/vino-server[0x40bdb2] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)[0x7fdfef855ea5] /usr/lib/vino/vino-server[0x40be99] === Memory map: 0040-00446000 r-xp 08:06 9420 /usr/lib/vino/vino-server 00646000-00647000 r--p 00046000 08:06 9420 /usr/lib/vino/vino-server 00647000-00649000 rw-p 00047000 08:06 9420 /usr/lib/vino/vino-server 00649000-00656000 rw-p 00:00 0 01c67000-01e19000 rw-p 00:00 0 [heap] 7fdfd400-7fdfd4022000 rw-p 00:00 0 7fdfd4022000-7fdfd800 ---p 00:00 0 7fdfd800-7fdfd8022000 rw-p 00:00 0 7fdfd8022000-7fdfdc00 ---p 00:00 0 7fdfdedc-7fdfdedc5000 r-xp 08:06 131713 /usr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0/menuproxies/libappmenu.so 7fdfdedc5000-7fdfdefc4000 ---p 5000 08:06 131713 /usr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0/menuproxies/libappmenu.so 7fdfdefc4000-7fdfdefc5000 r--p 4000 08:06 131713 /usr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0/menuproxies/libappmenu.so 7fdfdefc5000-7fdfdefc6000 rw-p 5000 08:06 131713 /usr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0/menuproxies/libappmenu.so 7fdfdefc6000-7fdfdefca000 r-xp 08:06 134821
[Desktop-packages] [Bug 1197562] [NEW] Vino crashes on startup
Public bug reported: To be filled out. Last bug report didn't get enough info. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: vino 3.6.2-0ubuntu4 Uname: Linux 3.10.0-031000-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.2 Architecture: amd64 Date: Wed Jul 3 18:41:03 2013 InstallationDate: Installed on 2013-03-16 (109 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130316) MarkForUpload: True ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: vino UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: vino (Ubuntu) Importance: Undecided Status: Invalid ** Tags: amd64 apport-bug raring third-party-packages ** Changed in: vino (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vino in Ubuntu. https://bugs.launchpad.net/bugs/1197562 Title: Vino crashes on startup Status in “vino” package in Ubuntu: Invalid Bug description: To be filled out. Last bug report didn't get enough info. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: vino 3.6.2-0ubuntu4 Uname: Linux 3.10.0-031000-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.2 Architecture: amd64 Date: Wed Jul 3 18:41:03 2013 InstallationDate: Installed on 2013-03-16 (109 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130316) MarkForUpload: True ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: vino UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vino/+bug/1197562/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1196668] Re: VNC crashes on startup on Raring
** Bug watch added: GNOME Bug Tracker #703496 https://bugzilla.gnome.org/show_bug.cgi?id=703496 ** Also affects: vino via https://bugzilla.gnome.org/show_bug.cgi?id=703496 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vino in Ubuntu. https://bugs.launchpad.net/bugs/1196668 Title: VNC crashes on startup on Raring Status in GNOME Remote Desktop: Unknown Status in “vino” package in Ubuntu: New Bug description: Vino-server is what is impacted. I believe what triggers this is related to customizing via vino-preferences. Afterwards, vino will not launch the server. A similar bug was reported on Oneiric and older, but I believe the bug report was marked as invalid due to it not having nearly enough info. The notification area icon will not stay. It will appear after startup, and quickly disappear. VNC is COMPLETELY UNUSABLE in every FOSS application I've tried on Ubuntu 13.04. From the GNOME Remote Desktop Client to Remnima, nothing works. Worse yet, none of the proprietary clients/servers such as Splashtop work either. The only remote desktop tool working is Teamviewer, and that runs under WINE. So remote desktop is borked on both my desktop and laptop. I will copy and paste some debug below: /usr/lib/vino/vino-server --sm-disable (vino-server:27458): EggSMClient-CRITICAL **: egg_sm_client_set_mode: assertion `global_client == NULL || global_client_mode == EGG_SM_CLIENT_MODE_DISABLED' failed 01/07/2013 03:01:26 PM Autoprobing TCP port in (all) network interface 01/07/2013 03:01:26 PM Listening IPv6://[::]:5900 01/07/2013 03:01:26 PM Listening IPv4://0.0.0.0:5900 01/07/2013 03:01:26 PM Autoprobing selected port 5900 01/07/2013 03:01:26 PM Advertising security type: 'TLS' (18) 01/07/2013 03:01:26 PM Re-binding socket to listen for VNC connections on TCP port 5900 in (all) interface 01/07/2013 03:01:26 PM Listening IPv6://[::]:5900 01/07/2013 03:01:26 PM Listening IPv4://0.0.0.0:5900 01/07/2013 03:01:26 PM Clearing securityTypes 01/07/2013 03:01:26 PM Advertising security type: 'TLS' (18) 01/07/2013 03:01:26 PM Clearing securityTypes 01/07/2013 03:01:26 PM Advertising security type: 'TLS' (18) 01/07/2013 03:01:26 PM Advertising authentication type: 'No Authentication' (1) 01/07/2013 03:01:26 PM Re-binding socket to listen for VNC connections on TCP port 5900 in (all) interface 01/07/2013 03:01:26 PM Listening IPv6://[::]:5900 01/07/2013 03:01:26 PM Listening IPv4://0.0.0.0:5900 01/07/2013 03:01:26 PM Clearing securityTypes 01/07/2013 03:01:26 PM Clearing authTypes 01/07/2013 03:01:26 PM Advertising security type: 'TLS' (18) 01/07/2013 03:01:26 PM Advertising authentication type: 'VNC Authentication' (2) 01/07/2013 03:01:26 PM Clearing securityTypes 01/07/2013 03:01:26 PM Clearing authTypes 01/07/2013 03:01:26 PM Advertising security type: 'TLS' (18) 01/07/2013 03:01:26 PM Advertising authentication type: 'VNC Authentication' (2) 01/07/2013 03:01:26 PM Advertising security type: 'VNC Authentication' (2) (vino-server:27458): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're its parent. *** Error in `/usr/lib/vino/vino-server': free(): invalid pointer: 0x7fdfefbf5798 *** === Backtrace: = /lib/x86_64-linux-gnu/libc.so.6(+0x80a46)[0x7fdfef8b4a46] /usr/lib/libminiupnpc.so.8(FreeUPNPUrls+0x11)[0x7fdff2494add] /usr/lib/vino/vino-server[0x4165e5] /usr/lib/vino/vino-server[0x41666d] /usr/lib/vino/vino-server[0x416c00] /usr/lib/vino/vino-server[0x416dae] /lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x49b1b)[0x7fdfefc45b1b] /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x135)[0x7fdfefc44f05] /lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x49248)[0x7fdfefc45248] /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_loop_run+0x6a)[0x7fdfefc456ba] /usr/lib/vino/vino-server[0x40bdb2] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)[0x7fdfef855ea5] /usr/lib/vino/vino-server[0x40be99] === Memory map: 0040-00446000 r-xp 08:06 9420 /usr/lib/vino/vino-server 00646000-00647000 r--p 00046000 08:06 9420 /usr/lib/vino/vino-server 00647000-00649000 rw-p 00047000 08:06 9420 /usr/lib/vino/vino-server 00649000-00656000 rw-p 00:00 0 01c67000-01e19000 rw-p 00:00 0 [heap] 7fdfd400-7fdfd4022000 rw-p 00:00 0 7fdfd4022000-7fdfd800 ---p 00:00 0 7fdfd800-7fdfd8022000 rw-p 00:00 0 7fdfd8022000-7fdfdc00 ---p 00:00 0 7fdfdedc-7fdfdedc5000 r-xp 08:06 131713 /usr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0/menuproxies/libappmenu.so 7fdfdedc5000-7fdfdefc4000 ---p 5000 08:06 131713
[Desktop-packages] [Bug 1196668] [NEW] VNC crashes on startup on Raring
Public bug reported: Vino-server is what is impacted. I believe what triggers this is related to customizing via vino-preferences. Afterwards, vino will not launch the server. A similar bug was reported on Oneiric and older, but I believe the bug report was marked as invalid due to it not having nearly enough info. The notification area icon will not stay. It will appear after startup, and quickly disappear. VNC is COMPLETELY UNUSABLE in every FOSS application I've tried on Ubuntu 13.04. From the GNOME Remote Desktop Client to Remnima, nothing works. Worse yet, none of the proprietary clients/servers such as Splashtop work either. The only remote desktop tool working is Teamviewer, and that runs under WINE. So remote desktop is borked on both my desktop and laptop. I will copy and paste some debug below: /usr/lib/vino/vino-server --sm-disable (vino-server:27458): EggSMClient-CRITICAL **: egg_sm_client_set_mode: assertion `global_client == NULL || global_client_mode == EGG_SM_CLIENT_MODE_DISABLED' failed 01/07/2013 03:01:26 PM Autoprobing TCP port in (all) network interface 01/07/2013 03:01:26 PM Listening IPv6://[::]:5900 01/07/2013 03:01:26 PM Listening IPv4://0.0.0.0:5900 01/07/2013 03:01:26 PM Autoprobing selected port 5900 01/07/2013 03:01:26 PM Advertising security type: 'TLS' (18) 01/07/2013 03:01:26 PM Re-binding socket to listen for VNC connections on TCP port 5900 in (all) interface 01/07/2013 03:01:26 PM Listening IPv6://[::]:5900 01/07/2013 03:01:26 PM Listening IPv4://0.0.0.0:5900 01/07/2013 03:01:26 PM Clearing securityTypes 01/07/2013 03:01:26 PM Advertising security type: 'TLS' (18) 01/07/2013 03:01:26 PM Clearing securityTypes 01/07/2013 03:01:26 PM Advertising security type: 'TLS' (18) 01/07/2013 03:01:26 PM Advertising authentication type: 'No Authentication' (1) 01/07/2013 03:01:26 PM Re-binding socket to listen for VNC connections on TCP port 5900 in (all) interface 01/07/2013 03:01:26 PM Listening IPv6://[::]:5900 01/07/2013 03:01:26 PM Listening IPv4://0.0.0.0:5900 01/07/2013 03:01:26 PM Clearing securityTypes 01/07/2013 03:01:26 PM Clearing authTypes 01/07/2013 03:01:26 PM Advertising security type: 'TLS' (18) 01/07/2013 03:01:26 PM Advertising authentication type: 'VNC Authentication' (2) 01/07/2013 03:01:26 PM Clearing securityTypes 01/07/2013 03:01:26 PM Clearing authTypes 01/07/2013 03:01:26 PM Advertising security type: 'TLS' (18) 01/07/2013 03:01:26 PM Advertising authentication type: 'VNC Authentication' (2) 01/07/2013 03:01:26 PM Advertising security type: 'VNC Authentication' (2) (vino-server:27458): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're its parent. *** Error in `/usr/lib/vino/vino-server': free(): invalid pointer: 0x7fdfefbf5798 *** === Backtrace: = /lib/x86_64-linux-gnu/libc.so.6(+0x80a46)[0x7fdfef8b4a46] /usr/lib/libminiupnpc.so.8(FreeUPNPUrls+0x11)[0x7fdff2494add] /usr/lib/vino/vino-server[0x4165e5] /usr/lib/vino/vino-server[0x41666d] /usr/lib/vino/vino-server[0x416c00] /usr/lib/vino/vino-server[0x416dae] /lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x49b1b)[0x7fdfefc45b1b] /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x135)[0x7fdfefc44f05] /lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x49248)[0x7fdfefc45248] /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_loop_run+0x6a)[0x7fdfefc456ba] /usr/lib/vino/vino-server[0x40bdb2] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)[0x7fdfef855ea5] /usr/lib/vino/vino-server[0x40be99] === Memory map: 0040-00446000 r-xp 08:06 9420 /usr/lib/vino/vino-server 00646000-00647000 r--p 00046000 08:06 9420 /usr/lib/vino/vino-server 00647000-00649000 rw-p 00047000 08:06 9420 /usr/lib/vino/vino-server 00649000-00656000 rw-p 00:00 0 01c67000-01e19000 rw-p 00:00 0 [heap] 7fdfd400-7fdfd4022000 rw-p 00:00 0 7fdfd4022000-7fdfd800 ---p 00:00 0 7fdfd800-7fdfd8022000 rw-p 00:00 0 7fdfd8022000-7fdfdc00 ---p 00:00 0 7fdfdedc-7fdfdedc5000 r-xp 08:06 131713 /usr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0/menuproxies/libappmenu.so 7fdfdedc5000-7fdfdefc4000 ---p 5000 08:06 131713 /usr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0/menuproxies/libappmenu.so 7fdfdefc4000-7fdfdefc5000 r--p 4000 08:06 131713 /usr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0/menuproxies/libappmenu.so 7fdfdefc5000-7fdfdefc6000 rw-p 5000 08:06 131713 /usr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0/menuproxies/libappmenu.so 7fdfdefc6000-7fdfdefca000 r-xp 08:06 134821 /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-png.so 7fdfdefca000-7fdfdf1ca000 ---p 4000 08:06 134821
[Desktop-packages] [Bug 1153350] Re: LibreOffice4 Global Menu Items Do Not Highlight on Mouse Hover
Well, it's been about a month. I know there's a ton of bugs on Launchpad, but when is the Unity Team going to merge this in to Raring's Unity so the next update will patch this annoyance? Not bugging, but I would like to know since I cannot even find any other major bugs affecting me on Raring. This seems like a simple patch but without the patch, Libreoffice is just plain hard to use. Have to squint to make out what menu button I'm on. Again sorry for the bugging, but I just want to see some coordination between the top and the bottom. -- 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/1153350 Title: LibreOffice4 Global Menu Items Do Not Highlight on Mouse Hover Status in LibreOffice Productivity Suite: Unknown Status in Application Indicators: Invalid Status in Unity: In Progress Status in “indicator-appmenu” package in Ubuntu: Invalid Status in “libreoffice” package in Ubuntu: Invalid Bug description: Open LibreOffice Writer, go to global menu, click on any menu to open, hover over items. Expected: Orange highlight (from default theme, color not important) on mouse hover Actual: No highlight ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: libreoffice-core 1:4.0.0~beta2-0ubuntu2 ProcVersionSignature: Ubuntu 3.8.0-11.20-generic 3.8.2 Uname: Linux 3.8.0-11-generic x86_64 ApportVersion: 2.9.1-0ubuntu1 Architecture: amd64 Date: Sun Mar 10 12:37:34 2013 ExecutablePath: /usr/lib/libreoffice/program/soffice.bin InstallationDate: Installed on 2013-03-06 (4 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130305) MarkForUpload: True SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) XsessionErrors: gnome-session[12370]: WARNING: Application 'compiz.desktop' killed by signal 9 gnome-session[12370]: WARNING: App 'compiz.desktop' respawning too quickly gnome-session[12370]: CRITICAL: We failed, but the fail whale is dead. Sorry gnome-session[12370]: WARNING: App 'compiz.desktop' respawning too quickly (gedit:14523): Gtk-CRITICAL **: gtk_widget_event: assertion `WIDGET_REALIZED_FOR_EVENT (widget, event)' failed To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1153350/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1153350] Re: LibreOffice4 Global Menu Items Do Not Highlight on Mouse Hover
Regardless of comments, I don't want an ETA or anything like that myself. Raring is a very nice release, but this one bug is irking me just a bit. Take your time fixing it, but it would be nice to know if it's on the list of stuff to get fixed, and if anyone will eventually be assigned. I am patient. I just hope it gets fixed eventually. A lot of you guys are volunteers. And Canonical doesn't have a billion employees. But large and obnoxious bugs should be assigned eventually. As I said, I am easily able to wait. I know the Libreoffice globalmenu recently went through a rehaul. So good luck to all! -- 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/1153350 Title: LibreOffice4 Global Menu Items Do Not Highlight on Mouse Hover Status in Application Indicators: New Status in Unity: Invalid Status in “indicator-appmenu” package in Ubuntu: Confirmed Status in “libreoffice” package in Ubuntu: Incomplete Bug description: Open LibreOffice Writer, go to global menu, click on any menu to open, hover over items. Expected: Orange highlight (from default theme, color not important) on mouse hover Actual: No highlight ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: libreoffice-core 1:4.0.0~beta2-0ubuntu2 ProcVersionSignature: Ubuntu 3.8.0-11.20-generic 3.8.2 Uname: Linux 3.8.0-11-generic x86_64 ApportVersion: 2.9.1-0ubuntu1 Architecture: amd64 Date: Sun Mar 10 12:37:34 2013 ExecutablePath: /usr/lib/libreoffice/program/soffice.bin InstallationDate: Installed on 2013-03-06 (4 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130305) MarkForUpload: True SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) XsessionErrors: gnome-session[12370]: WARNING: Application 'compiz.desktop' killed by signal 9 gnome-session[12370]: WARNING: App 'compiz.desktop' respawning too quickly gnome-session[12370]: CRITICAL: We failed, but the fail whale is dead. Sorry gnome-session[12370]: WARNING: App 'compiz.desktop' respawning too quickly (gedit:14523): Gtk-CRITICAL **: gtk_widget_event: assertion `WIDGET_REALIZED_FOR_EVENT (widget, event)' failed To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-application/+bug/1153350/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1153350] Re: LibreOffice4 Global Menu Items Do Not Highlight on Mouse Hover
Yay for progress! Thanks for assigning this bug. May not be fixed in time for a release, but a fix promised is a fix good enough. -- 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/1153350 Title: LibreOffice4 Global Menu Items Do Not Highlight on Mouse Hover Status in Application Indicators: New Status in Unity: Triaged Status in “indicator-appmenu” package in Ubuntu: Confirmed Status in “libreoffice” package in Ubuntu: Incomplete Bug description: Open LibreOffice Writer, go to global menu, click on any menu to open, hover over items. Expected: Orange highlight (from default theme, color not important) on mouse hover Actual: No highlight ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: libreoffice-core 1:4.0.0~beta2-0ubuntu2 ProcVersionSignature: Ubuntu 3.8.0-11.20-generic 3.8.2 Uname: Linux 3.8.0-11-generic x86_64 ApportVersion: 2.9.1-0ubuntu1 Architecture: amd64 Date: Sun Mar 10 12:37:34 2013 ExecutablePath: /usr/lib/libreoffice/program/soffice.bin InstallationDate: Installed on 2013-03-06 (4 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130305) MarkForUpload: True SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) XsessionErrors: gnome-session[12370]: WARNING: Application 'compiz.desktop' killed by signal 9 gnome-session[12370]: WARNING: App 'compiz.desktop' respawning too quickly gnome-session[12370]: CRITICAL: We failed, but the fail whale is dead. Sorry gnome-session[12370]: WARNING: App 'compiz.desktop' respawning too quickly (gedit:14523): Gtk-CRITICAL **: gtk_widget_event: assertion `WIDGET_REALIZED_FOR_EVENT (widget, event)' failed To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-application/+bug/1153350/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1153350] Re: LibreOffice4 Global Menu Items Do Not Highlight on Mouse Hover
+1 For at least assigning the bug. It is making the menu system unacceptable. Pain in the butt when you want to use Libreoffice whenever you can to avoid buggy MS products. Now, it seems that MS Office is smoother than this, until this is fixed. Then Raring would be perfect for me. -- 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/1153350 Title: LibreOffice4 Global Menu Items Do Not Highlight on Mouse Hover Status in Application Indicators: New Status in Unity: Invalid Status in “indicator-appmenu” package in Ubuntu: Confirmed Status in “libreoffice” package in Ubuntu: Incomplete Bug description: Open LibreOffice Writer, go to global menu, click on any menu to open, hover over items. Expected: Orange highlight (from default theme, color not important) on mouse hover Actual: No highlight ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: libreoffice-core 1:4.0.0~beta2-0ubuntu2 ProcVersionSignature: Ubuntu 3.8.0-11.20-generic 3.8.2 Uname: Linux 3.8.0-11-generic x86_64 ApportVersion: 2.9.1-0ubuntu1 Architecture: amd64 Date: Sun Mar 10 12:37:34 2013 ExecutablePath: /usr/lib/libreoffice/program/soffice.bin InstallationDate: Installed on 2013-03-06 (4 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130305) MarkForUpload: True SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) XsessionErrors: gnome-session[12370]: WARNING: Application 'compiz.desktop' killed by signal 9 gnome-session[12370]: WARNING: App 'compiz.desktop' respawning too quickly gnome-session[12370]: CRITICAL: We failed, but the fail whale is dead. Sorry gnome-session[12370]: WARNING: App 'compiz.desktop' respawning too quickly (gedit:14523): Gtk-CRITICAL **: gtk_widget_event: assertion `WIDGET_REALIZED_FOR_EVENT (widget, event)' failed To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-application/+bug/1153350/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 978444] Re: HTTPS is not used for Google searches
It seems to be fixed in Firefox 20. ** Changed in: firefox (Ubuntu) Status: Triaged = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/978444 Title: HTTPS is not used for Google searches Status in The Mozilla Firefox Browser: Invalid Status in “firefox” package in Ubuntu: Fix Released Status in “ubufox” package in Ubuntu: Invalid Bug description: about:home and about:startpage does not use HTTPS which results in the communication being insecure and allows usage tracking and surveillance by a attacker as well as man-in-the-middle attacks. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/978444/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1158350] [NEW] [xrandr]: gnome-settings-daemon crashed with signal 5 in _XReply()
Public bug reported: Running Ubuntu 13.04 development branch with the latest updates. Latest version of gnome-settings-daemon. This crash seems to have happened in the background. ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: gnome-settings-daemon 3.6.4-0ubuntu7 Uname: Linux 3.9.0-030900rc3-generic x86_64 ApportVersion: 2.9.2-0ubuntu2 Architecture: amd64 Date: Mon Mar 18 19:44:39 2013 ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon InstallationDate: Installed on 2013-03-16 (4 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130316) MarkForUpload: True ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/false Signal: 5 SourcePackage: gnome-settings-daemon StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XSync () from /usr/lib/x86_64-linux-gnu/libX11.so.6 gdk_flush () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: [xrandr]: gnome-settings-daemon crashed with signal 5 in _XReply() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash need-amd64-retrace raring xrandr ** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1158350 Title: [xrandr]: gnome-settings-daemon crashed with signal 5 in _XReply() Status in “gnome-settings-daemon” package in Ubuntu: New Bug description: Running Ubuntu 13.04 development branch with the latest updates. Latest version of gnome-settings-daemon. This crash seems to have happened in the background. ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: gnome-settings-daemon 3.6.4-0ubuntu7 Uname: Linux 3.9.0-030900rc3-generic x86_64 ApportVersion: 2.9.2-0ubuntu2 Architecture: amd64 Date: Mon Mar 18 19:44:39 2013 ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon InstallationDate: Installed on 2013-03-16 (4 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130316) MarkForUpload: True ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/false Signal: 5 SourcePackage: gnome-settings-daemon StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XSync () from /usr/lib/x86_64-linux-gnu/libX11.so.6 gdk_flush () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: [xrandr]: gnome-settings-daemon crashed with signal 5 in _XReply() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1158350/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1102660] Re: Ubuntu Raring Hard Freezes with AMD Driver
Yep. No more crashes here, either. Now I can get back to testing and work. -- 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/1102660 Title: Ubuntu Raring Hard Freezes with AMD Driver Status in “xorg” package in Ubuntu: Fix Released Bug description: This bug is simple to explain, but hard to figure out what specifically is causing it. While using the computer, Ubuntu will frequently (within 5-10 minutes of use) hard freeze. I am unable to move the mouse, CTRL ALT F whatever to a virtual terminal, use the keyboard, and the power button doesn't respond unless I do a hard shutdown. This could be a bug with the kernel, Xorg, or compiz. Or even something else. I have no clue to as to what's causing this, so I will upload some log files from /var/log and provide my kernel version, graphics card, and more system info if necessary. This courts frequently on raring, but also happened occasionally on Quantal. But that's another bug report. Every package is up to date. I noticed this happened only on quantal when I manually upgraded to the mainline kernel. So it could also be a kernel bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1102660/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1102660] Re: Ubuntu Raring Hard Freezes with AMD Driver
Thanks for testing it out! With all the hard freezing I was ready to pull my hair out! But development branch is development stability, so I guess I should have expected issues. I will continue to use this Ubuntu release until I experience a freeze again. If I don't experience it in a week or so, and no others experience it again, I will mark the bug as resolved. -- 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/1102660 Title: Ubuntu Raring Hard Freezes with AMD Driver Status in “xorg” package in Ubuntu: Confirmed Bug description: This bug is simple to explain, but hard to figure out what specifically is causing it. While using the computer, Ubuntu will frequently (within 5-10 minutes of use) hard freeze. I am unable to move the mouse, CTRL ALT F whatever to a virtual terminal, use the keyboard, and the power button doesn't respond unless I do a hard shutdown. This could be a bug with the kernel, Xorg, or compiz. Or even something else. I have no clue to as to what's causing this, so I will upload some log files from /var/log and provide my kernel version, graphics card, and more system info if necessary. This courts frequently on raring, but also happened occasionally on Quantal. But that's another bug report. Every package is up to date. I noticed this happened only on quantal when I manually upgraded to the mainline kernel. So it could also be a kernel bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1102660/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1102660] Re: Ubuntu Raring Hard Freezes with AMD Driver
Now that you guys can get the magic SysRq keys to dump a log, and then we can get the ball rolling. I left plenty of logs, but still we need more. I oddly don't even have a SysRq key (I have a Microsoft keyboard that comes with its own funky layout) and I have no clue as to any alternate key commands. When I went on IRC to debug this mess, the devs told me I need to get more proper logs. If one of you guys can do it, it will be appreciated and we can make progress. Anyhow, the links they gave me were to https://wiki.ubuntu.com/X/Triaging#Package_Classification and also https://wiki.ubuntu.com/Kernel/Debugging but I think we just need to debug Xorg if you guys can get the kernel to respond. You've saved me some bug reporting work! Thank you! Just reference the first link. -- 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/1102660 Title: Ubuntu Raring Hard Freezes with AMD Driver Status in “xorg” package in Ubuntu: Confirmed Bug description: This bug is simple to explain, but hard to figure out what specifically is causing it. While using the computer, Ubuntu will frequently (within 5-10 minutes of use) hard freeze. I am unable to move the mouse, CTRL ALT F whatever to a virtual terminal, use the keyboard, and the power button doesn't respond unless I do a hard shutdown. This could be a bug with the kernel, Xorg, or compiz. Or even something else. I have no clue to as to what's causing this, so I will upload some log files from /var/log and provide my kernel version, graphics card, and more system info if necessary. This courts frequently on raring, but also happened occasionally on Quantal. But that's another bug report. Every package is up to date. I noticed this happened only on quantal when I manually upgraded to the mainline kernel. So it could also be a kernel bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1102660/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1102660] Re: Ubuntu Raring Hard Freezes with AMD Driver
In a way, I'm glad someone else has this problem. I wish nobody had it, but now we can confirm this bug. That means it's not a hardware issue. What specific graphics card do you have? I wonder if it's the same graphics card I have, an AMD Radeon HD 6300. Or does this effect every graphics card using the radeon driver? Please do investigate. -- 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/1102660 Title: Ubuntu Raring Hard Freezes with AMD Driver Status in “xorg” package in Ubuntu: Confirmed Bug description: This bug is simple to explain, but hard to figure out what specifically is causing it. While using the computer, Ubuntu will frequently (within 5-10 minutes of use) hard freeze. I am unable to move the mouse, CTRL ALT F whatever to a virtual terminal, use the keyboard, and the power button doesn't respond unless I do a hard shutdown. This could be a bug with the kernel, Xorg, or compiz. Or even something else. I have no clue to as to what's causing this, so I will upload some log files from /var/log and provide my kernel version, graphics card, and more system info if necessary. This courts frequently on raring, but also happened occasionally on Quantal. But that's another bug report. Every package is up to date. I noticed this happened only on quantal when I manually upgraded to the mainline kernel. So it could also be a kernel bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1102660/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1102660] Re: Ubuntu Raring Hard Freezes with AMD Driver
In case anyone is reading this bug report, I am going to attempt and SSH in to Raring the next time it freezes. I was unable to get it to do a dump when it last crashed. Must be really badly crashing. -- 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/1102660 Title: Ubuntu Raring Hard Freezes with AMD Driver Status in “xorg” package in Ubuntu: New Bug description: This bug is simple to explain, but hard to figure out what specifically is causing it. While using the computer, Ubuntu will frequently (within 5-10 minutes of use) hard freeze. I am unable to move the mouse, CTRL ALT F whatever to a virtual terminal, use the keyboard, and the power button doesn't respond unless I do a hard shutdown. This could be a bug with the kernel, Xorg, or compiz. Or even something else. I have no clue to as to what's causing this, so I will upload some log files from /var/log and provide my kernel version, graphics card, and more system info if necessary. This courts frequently on raring, but also happened occasionally on Quantal. But that's another bug report. Every package is up to date. I noticed this happened only on quantal when I manually upgraded to the mainline kernel. So it could also be a kernel bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1102660/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1102660] [NEW] Ubuntu Raring Hard Freezes with AMD Driver
Public bug reported: This bug is simple to explain, but hard to figure out what specifically is causing it. While using the computer, Ubuntu will frequently (within 5-10 minutes of use) hard freeze. I am unable to move the mouse, CTRL ALT F whatever to a virtual terminal, use the keyboard, and the power button doesn't respond unless I do a hard shutdown. This could be a bug with the kernel, Xorg, or compiz. Or even something else. I have no clue to as to what's causing this, so I will upload some log files from /var/log and provide my kernel version, graphics card, and more system info if necessary. This courts frequently on raring, but also happened occasionally on Quantal. But that's another bug report. Every package is up to date. I noticed this happened only on quantal when I manually upgraded to the mainline kernel. So it could also be a kernel bug. ** Affects: xorg (Ubuntu) Importance: Undecided Status: New -- 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/1102660 Title: Ubuntu Raring Hard Freezes with AMD Driver Status in “xorg” package in Ubuntu: New Bug description: This bug is simple to explain, but hard to figure out what specifically is causing it. While using the computer, Ubuntu will frequently (within 5-10 minutes of use) hard freeze. I am unable to move the mouse, CTRL ALT F whatever to a virtual terminal, use the keyboard, and the power button doesn't respond unless I do a hard shutdown. This could be a bug with the kernel, Xorg, or compiz. Or even something else. I have no clue to as to what's causing this, so I will upload some log files from /var/log and provide my kernel version, graphics card, and more system info if necessary. This courts frequently on raring, but also happened occasionally on Quantal. But that's another bug report. Every package is up to date. I noticed this happened only on quantal when I manually upgraded to the mainline kernel. So it could also be a kernel bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1102660/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1102660] Re: Ubuntu Raring Hard Freezes with AMD Driver
Kernel: Linux 3.8.0-1-generic 64 bit Log files on there way. Lert me know if additional details are needed. -- 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/1102660 Title: Ubuntu Raring Hard Freezes with AMD Driver Status in “xorg” package in Ubuntu: New Bug description: This bug is simple to explain, but hard to figure out what specifically is causing it. While using the computer, Ubuntu will frequently (within 5-10 minutes of use) hard freeze. I am unable to move the mouse, CTRL ALT F whatever to a virtual terminal, use the keyboard, and the power button doesn't respond unless I do a hard shutdown. This could be a bug with the kernel, Xorg, or compiz. Or even something else. I have no clue to as to what's causing this, so I will upload some log files from /var/log and provide my kernel version, graphics card, and more system info if necessary. This courts frequently on raring, but also happened occasionally on Quantal. But that's another bug report. Every package is up to date. I noticed this happened only on quantal when I manually upgraded to the mainline kernel. So it could also be a kernel bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1102660/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1102660] Re: Ubuntu Raring Hard Freezes with AMD Driver
** Attachment added: dmesg https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1102660/+attachment/3493266/+files/dmesg -- 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/1102660 Title: Ubuntu Raring Hard Freezes with AMD Driver Status in “xorg” package in Ubuntu: New Bug description: This bug is simple to explain, but hard to figure out what specifically is causing it. While using the computer, Ubuntu will frequently (within 5-10 minutes of use) hard freeze. I am unable to move the mouse, CTRL ALT F whatever to a virtual terminal, use the keyboard, and the power button doesn't respond unless I do a hard shutdown. This could be a bug with the kernel, Xorg, or compiz. Or even something else. I have no clue to as to what's causing this, so I will upload some log files from /var/log and provide my kernel version, graphics card, and more system info if necessary. This courts frequently on raring, but also happened occasionally on Quantal. But that's another bug report. Every package is up to date. I noticed this happened only on quantal when I manually upgraded to the mainline kernel. So it could also be a kernel bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1102660/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1102660] Re: Ubuntu Raring Hard Freezes with AMD Driver
** Attachment added: kern.log https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1102660/+attachment/3493269/+files/kern.log -- 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/1102660 Title: Ubuntu Raring Hard Freezes with AMD Driver Status in “xorg” package in Ubuntu: New Bug description: This bug is simple to explain, but hard to figure out what specifically is causing it. While using the computer, Ubuntu will frequently (within 5-10 minutes of use) hard freeze. I am unable to move the mouse, CTRL ALT F whatever to a virtual terminal, use the keyboard, and the power button doesn't respond unless I do a hard shutdown. This could be a bug with the kernel, Xorg, or compiz. Or even something else. I have no clue to as to what's causing this, so I will upload some log files from /var/log and provide my kernel version, graphics card, and more system info if necessary. This courts frequently on raring, but also happened occasionally on Quantal. But that's another bug report. Every package is up to date. I noticed this happened only on quantal when I manually upgraded to the mainline kernel. So it could also be a kernel bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1102660/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1102660] Re: Ubuntu Raring Hard Freezes with AMD Driver
** Attachment added: syslog https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1102660/+attachment/3493270/+files/syslog -- 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/1102660 Title: Ubuntu Raring Hard Freezes with AMD Driver Status in “xorg” package in Ubuntu: New Bug description: This bug is simple to explain, but hard to figure out what specifically is causing it. While using the computer, Ubuntu will frequently (within 5-10 minutes of use) hard freeze. I am unable to move the mouse, CTRL ALT F whatever to a virtual terminal, use the keyboard, and the power button doesn't respond unless I do a hard shutdown. This could be a bug with the kernel, Xorg, or compiz. Or even something else. I have no clue to as to what's causing this, so I will upload some log files from /var/log and provide my kernel version, graphics card, and more system info if necessary. This courts frequently on raring, but also happened occasionally on Quantal. But that's another bug report. Every package is up to date. I noticed this happened only on quantal when I manually upgraded to the mainline kernel. So it could also be a kernel bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1102660/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1102660] Re: Ubuntu Raring Hard Freezes with AMD Driver
** Attachment added: udev https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1102660/+attachment/3493271/+files/udev -- 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/1102660 Title: Ubuntu Raring Hard Freezes with AMD Driver Status in “xorg” package in Ubuntu: New Bug description: This bug is simple to explain, but hard to figure out what specifically is causing it. While using the computer, Ubuntu will frequently (within 5-10 minutes of use) hard freeze. I am unable to move the mouse, CTRL ALT F whatever to a virtual terminal, use the keyboard, and the power button doesn't respond unless I do a hard shutdown. This could be a bug with the kernel, Xorg, or compiz. Or even something else. I have no clue to as to what's causing this, so I will upload some log files from /var/log and provide my kernel version, graphics card, and more system info if necessary. This courts frequently on raring, but also happened occasionally on Quantal. But that's another bug report. Every package is up to date. I noticed this happened only on quantal when I manually upgraded to the mainline kernel. So it could also be a kernel bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1102660/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1102660] Re: Ubuntu Raring Hard Freezes with AMD Driver
** Attachment added: Xorg.0.log https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1102660/+attachment/3493272/+files/Xorg.0.log -- 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/1102660 Title: Ubuntu Raring Hard Freezes with AMD Driver Status in “xorg” package in Ubuntu: New Bug description: This bug is simple to explain, but hard to figure out what specifically is causing it. While using the computer, Ubuntu will frequently (within 5-10 minutes of use) hard freeze. I am unable to move the mouse, CTRL ALT F whatever to a virtual terminal, use the keyboard, and the power button doesn't respond unless I do a hard shutdown. This could be a bug with the kernel, Xorg, or compiz. Or even something else. I have no clue to as to what's causing this, so I will upload some log files from /var/log and provide my kernel version, graphics card, and more system info if necessary. This courts frequently on raring, but also happened occasionally on Quantal. But that's another bug report. Every package is up to date. I noticed this happened only on quantal when I manually upgraded to the mainline kernel. So it could also be a kernel bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1102660/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1102660] Re: Ubuntu Raring Hard Freezes with AMD Driver
** Attachment added: faillog https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1102660/+attachment/3493268/+files/faillog -- 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/1102660 Title: Ubuntu Raring Hard Freezes with AMD Driver Status in “xorg” package in Ubuntu: New Bug description: This bug is simple to explain, but hard to figure out what specifically is causing it. While using the computer, Ubuntu will frequently (within 5-10 minutes of use) hard freeze. I am unable to move the mouse, CTRL ALT F whatever to a virtual terminal, use the keyboard, and the power button doesn't respond unless I do a hard shutdown. This could be a bug with the kernel, Xorg, or compiz. Or even something else. I have no clue to as to what's causing this, so I will upload some log files from /var/log and provide my kernel version, graphics card, and more system info if necessary. This courts frequently on raring, but also happened occasionally on Quantal. But that's another bug report. Every package is up to date. I noticed this happened only on quantal when I manually upgraded to the mainline kernel. So it could also be a kernel bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1102660/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1102660] Re: Ubuntu Raring Hard Freezes with AMD Driver
** Attachment added: dmesg.0 https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1102660/+attachment/3493267/+files/dmesg.0 -- 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/1102660 Title: Ubuntu Raring Hard Freezes with AMD Driver Status in “xorg” package in Ubuntu: New Bug description: This bug is simple to explain, but hard to figure out what specifically is causing it. While using the computer, Ubuntu will frequently (within 5-10 minutes of use) hard freeze. I am unable to move the mouse, CTRL ALT F whatever to a virtual terminal, use the keyboard, and the power button doesn't respond unless I do a hard shutdown. This could be a bug with the kernel, Xorg, or compiz. Or even something else. I have no clue to as to what's causing this, so I will upload some log files from /var/log and provide my kernel version, graphics card, and more system info if necessary. This courts frequently on raring, but also happened occasionally on Quantal. But that's another bug report. Every package is up to date. I noticed this happened only on quantal when I manually upgraded to the mainline kernel. So it could also be a kernel bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1102660/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1051559]
This is probably going to be a royal pain to implement, but alas it is a necessary evil. I despise the fact that Firefox is going to have to implement proprietary codecs to stay relevant, but it's better than having 90% of the videos online not working. As a user and bug tester, this is indeed a sad day for us. This implementation is especially important since Adobe only supports Flash for Linux in Pepper form currently. Last thing I want is to have to reboot into Windows for yet another thing. I love Linux (any distro) but cannot sacrifice usability for ideology. Trust me, this will be worth it. We are getting a second rate experience, thanks Adobe! Oh well. Can't win all the battles out there but the war for freedom rages on. Just thought I'd deliver the non-typical power user opinion on this. Sorry if I got off topic. But the end user would wonder (on any platform) why videos wouldn't work on Firefox if we didn't support this, and they would likely dump Firefox for a proprietary browser such as Google Chrome. Best we stay relevant. Just imagine the consequences on Linux, where a lot of the brainpower is. Not to insult any other platform's users, but many Linux users are developers and users. Many Windows and Mac users are just users, with a few developers here and there. Any implementation to help us stay relevant is deeply appreciated. End rant. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1051559 Title: Build Firefox with GStreamer support Status in The Mozilla Firefox Browser: Confirmed Status in “firefox” package in Ubuntu: Triaged Bug description: Building Firefox with GStreamer support would provide support for a lot of websites that use h264. To build Firefox with GStreamer support you should use the --enable-gstreamer option. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1051559/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1056272] Re: gedit crashed with signal 5
** Visibility changed to: Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1056272 Title: gedit crashed with signal 5 Status in “gedit” package in Ubuntu: Invalid Bug description: Running Quantal development branch 64 bit with the latest updates. Seems to crash when I attempt to either Open a New Window or Open a New Document from the Unity quicklist for gedit. ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: gedit 3.5.3-0ubuntu1 Uname: Linux 3.5.4-030504-generic x86_64 ApportVersion: 2.5.2-0ubuntu4 Architecture: amd64 CrashCounter: 1 Date: Tue Sep 25 11:42:23 2012 Disassembly: = 0x7f271516bdef: Cannot access memory at address 0x7f271516bdef ExecutablePath: /usr/bin/gedit InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120905.2) ProcCmdline: gedit /media/username/PATRIOT/Documents/Text/Passwords.txt ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 5 SourcePackage: gedit Stacktrace: #0 0x7f271516bdef in ?? () No symbol table info available. Cannot access memory at address 0x7fffab12b6b0 StacktraceTop: ?? () ThreadStacktrace: . Thread 4 (LWP 13340): #0 0x7f2714c100fe in ?? () No symbol table info available. Cannot access memory at address 0x7f27077fdb40 Title: gedit crashed with signal 5 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1056272/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1056271] Re: gedit crashed with signal 5 in _XReply()
** Visibility changed to: Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1056271 Title: gedit crashed with signal 5 in _XReply() Status in “gedit” package in Ubuntu: New Bug description: Running Quantal development branch 64 bit with the latest updates. Seems to crash when I attempt to either Open a New Window or Open a New Document from the Unity quicklist for gedit. ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: gedit 3.5.3-0ubuntu1 Uname: Linux 3.5.4-030504-generic x86_64 ApportVersion: 2.5.2-0ubuntu4 Architecture: amd64 Date: Tue Sep 25 11:41:38 2012 ExecutablePath: /usr/bin/gedit InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120905.2) ProcCmdline: gedit /media/username/PATRIOT/Documents/Text/Passwords.txt ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 5 SourcePackage: gedit StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XInternAtom () from /usr/lib/x86_64-linux-gnu/libX11.so.6 gdk_x11_atom_to_xatom_for_display () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: gedit crashed with signal 5 in _XReply() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1056271/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1052497] Re: software-center crashed with ImportError in get_login_backend(): No module named login_impl.login_sso
Update: With Ubuntu Software Center 5.3.14.1 in Quantal (at least with me on amd64), it appears there is no longer a startup crash. This update popped in shortly after I updated my system literally about 5 minutes after commenting on this bug. Guys, please update your systems now and see if the bug is still there. It should be gone. If so, we can mark this bug as fixed. ** Changed in: software-center (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-center in Ubuntu. https://bugs.launchpad.net/bugs/1052497 Title: software-center crashed with ImportError in get_login_backend(): No module named login_impl.login_sso Status in “software-center” package in Ubuntu: Fix Released Bug description: Happened 3 times ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: software-center 5.3.14 ProcVersionSignature: Ubuntu 3.5.0-14.19-generic 3.5.3 Uname: Linux 3.5.0-14-generic i686 ApportVersion: 2.5.2-0ubuntu1 Architecture: i386 Date: Tue Sep 18 09:39:49 2012 ExecutablePath: /usr/share/software-center/software-center InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha i386 (20120809.1) InterpreterPath: /usr/bin/python2.7 PackageArchitecture: all ProcCmdline: /usr/bin/python /usr/bin/software-center ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash PythonArgs: ['/usr/bin/software-center'] SourcePackage: software-center Title: software-center crashed with ImportError in get_login_backend(): No module named login_impl.login_sso UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/1052497/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1052184] Re: rhythmbox crashed with SIGSEGV
** Visibility changed to: Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1052184 Title: rhythmbox crashed with SIGSEGV Status in “rhythmbox” package in Ubuntu: New Bug description: Running the latest Quantal development branch 64 bit with all the updates. Let me know if you guys need any more info. ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: rhythmbox 2.97-1ubuntu4 Uname: Linux 3.5.4-030504-generic x86_64 ApportVersion: 2.5.2-0ubuntu1 Architecture: amd64 Date: Mon Sep 17 16:54:18 2012 Disassembly: = 0x7f5d62605d4c: Cannot access memory at address 0x7f5d62605d4c ExecutablePath: /usr/bin/rhythmbox InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120905.2) LogAlsaMixer: Simple mixer control 'IEC958',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] ProcCmdline: rhythmbox ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANG=en_US.UTF-8 SegvAnalysis: Segfault happened at: 0x7f5d62605d4c:Cannot access memory at address 0x7f5d62605d4c PC (0x7f5d62605d4c) ok Stack memory exhausted (SP below stack segment) SP (0x7f5cbb9bf5e0) ok Reason could not be automatically determined. Signal: 11 SourcePackage: rhythmbox StacktraceTop: ?? () ?? () ?? () ?? () ?? () Title: rhythmbox crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1052184/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1051594] Re: Xorg crashed with SIGABRT in DRI2GetBuffersWithFormat()
** Visibility changed to: Public -- 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/1051594 Title: Xorg crashed with SIGABRT in DRI2GetBuffersWithFormat() Status in “xorg-server” package in Ubuntu: New Bug description: Seems to happen when opening up a playlist with VLC using the Nightlies. Running Quantal development 64 bit. Just causes Xorg to go down in flames. ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: xserver-xorg-core 2:1.13.0-0ubuntu1 Uname: Linux 3.5.4-030504-generic x86_64 ApportVersion: 2.5.1-0ubuntu7 Architecture: amd64 CrashCounter: 1 Date: Sun Sep 16 10:33:31 2012 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu ExecutablePath: /usr/bin/Xorg GraphicsCard: Advanced Micro Devices [AMD] nee ATI Wrestler [Radeon HD 6320] [1002:9806] (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0592] InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120905.2) MachineType: Acer Aspire X1430 ProcCmdline: /usr/bin/X :0 -core -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.4-030504-generic root=UUID=9d24f9df-12dc-41bf-adf6-f2fd97fcda6d ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: ?? () from /usr/lib/xorg/modules/drivers/radeon_drv.so ?? () ?? () DRI2GetBuffersWithFormat () ?? () Title: Xorg crashed with SIGABRT in DRI2GetBuffersWithFormat() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 08/03/2011 dmi.bios.vendor: AMI dmi.bios.version: P01-B2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Aspire X1430 dmi.board.vendor: Acer dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnAMI:bvrP01-B2:bd08/03/2011:svnAcer:pnAspireX1430:pvr:rvnAcer:rnAspireX1430:rvr:cvnAcer:ct3:cvr: dmi.product.name: Aspire X1430 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.8.0-0ubuntu1 version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.39-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0~git20120903.e1673d20.is.git20120821.c1114c61-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0~git20120903.e1673d20.is.git20120821.c1114c61-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120713.6ef1ad6a-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.7-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1051594/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1050506] Re: file-roller crashed with SIGSEGV in g_simple_async_result_complete()
*** This bug is a duplicate of bug 1036878 *** https://bugs.launchpad.net/bugs/1036878 ** Visibility changed to: Public -- 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/1050506 Title: file-roller crashed with SIGSEGV in g_simple_async_result_complete() Status in “file-roller” package in Ubuntu: New Bug description: Crazy error I got when trying to open a .7z archive on my flash drive. Let me know if you guys need any more info. ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: file-roller 3.5.91-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-14.16-generic 3.5.3 Uname: Linux 3.5.0-14-generic x86_64 ApportVersion: 2.5.1-0ubuntu7 Architecture: amd64 Date: Thu Sep 13 12:29:38 2012 ExecutablePath: /usr/bin/file-roller InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120905.2) ProcCmdline: file-roller /media/username/PATRIOT/Archived/School/12th\ Grade.7z ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x4199e3: mov0x20(%rax),%rdi PC (0x004199e3) ok source 0x20(%rax) (0x0020) not located in a known VMA region (needed readable region)! destination %rdi ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: file-roller StacktraceTop: ?? () ?? () ?? () ?? () g_simple_async_result_complete () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: file-roller crashed with SIGSEGV in g_simple_async_result_complete() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1050506/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 978444] Re: HTTPS is not used for Google searches
I can confirm that it is specific to Ubuntu. Tested it over IRC with other Linux distros and the builds from Mozilla's website, but they all defaulted to HTTPS. Only the builds from the Mozilla Team PPAs refused to default to HTTPS. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/978444 Title: HTTPS is not used for Google searches Status in The Mozilla Firefox Browser: Invalid Status in “firefox” package in Ubuntu: Triaged Status in “ubufox” package in Ubuntu: New Bug description: about:home and about:startpage does not use HTTPS which results in the communication being insecure and allows usage tracking and surveillance by a attacker as well as man-in-the-middle attacks. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/978444/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 965510] Re: option --new-window not working correctly
This bug is persisting in 3.4.1. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/965510 Title: option --new-window not working correctly Status in Light-Weight Text Editor for Gnome: New Status in “gedit” package in Ubuntu: Confirmed Bug description: First, to reproduce, open Gedit (Text Editor). Right click on its icon in the Unity Taskbar. Oddly, clicking either of the two new options (create a new document or open a new window) opens a new window with two tabs, labelled Untitled Document 2 and the other one Untitled Document 3. What should happen is one new tab is opened when creating a new document, and one new window with one tab is opened for opening a new window. However, the aforementioned happens. I will upload a screenshot ASAP. I am running Precise Beta with the latest updates, and the latest version of Gedit. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gedit 3.3.8-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 ApportVersion: 1.95-0ubuntu1 Architecture: amd64 Date: Mon Mar 26 13:02:15 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20120321) ProcEnviron: TERM=xterm LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/965510/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 981822] Re: nautilus crashed with signal 7
** Visibility changed to: Public -- 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/981822 Title: nautilus crashed with signal 7 Status in “nautilus” package in Ubuntu: New Bug description: Running the latest Precise development build with all the updates. I expected no random error, but apport happened to pop up with this one. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: nautilus 1:3.4.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.0.1-0ubuntu3 Architecture: amd64 CrashCounter: 1 Date: Sat Apr 14 09:26:39 2012 ExecutablePath: /usr/bin/nautilus GsettingsChanges: org.gnome.nautilus.window-state geometry '767x550+659+182' InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20120321) ProcCmdline: nautilus -n ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 7 SourcePackage: nautilus StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so ?? () 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: nautilus crashed with signal 7 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm lpadmin sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/981822/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 981830] Re: [power]: gnome-settings-daemon crashed with signal 7
** Visibility changed to: Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/981830 Title: [power]: gnome-settings-daemon crashed with signal 7 Status in “gnome-settings-daemon” package in Ubuntu: New Bug description: Running the latest Precise development build with all the updates. I expected no random error, but apport happened to pop up with this one. Could have been caused by BleachBit. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: gnome-settings-daemon 3.4.0-0ubuntu7 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.0.1-0ubuntu3 Architecture: amd64 Date: Sat Apr 14 09:24:39 2012 ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon ExecutableTimestamp: 1334234567 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20120321) ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon ProcCwd: /home/admin ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 7 SourcePackage: gnome-settings-daemon StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so ?? () 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: [power]: gnome-settings-daemon crashed with signal 7 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm lpadmin sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/981830/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 981822] Re: nautilus crashed with signal 7
When I think about it, this problem could have easily been caused by Bleachbit. Could any of the devs look into this? -- 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/981822 Title: nautilus crashed with signal 7 Status in “nautilus” package in Ubuntu: New Bug description: Running the latest Precise development build with all the updates. I expected no random error, but apport happened to pop up with this one. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: nautilus 1:3.4.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.0.1-0ubuntu3 Architecture: amd64 CrashCounter: 1 Date: Sat Apr 14 09:26:39 2012 ExecutablePath: /usr/bin/nautilus GsettingsChanges: org.gnome.nautilus.window-state geometry '767x550+659+182' InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20120321) ProcCmdline: nautilus -n ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 7 SourcePackage: nautilus StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so ?? () 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: nautilus crashed with signal 7 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm lpadmin sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/981822/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 871325] Re: Implement Unity Launcher API in Firefox for downloads' progress and quicklist
I certainly hope this bug is fixed. I can only say that this bug effects me, and try to bump this bug up by doing whatever I can with my limited power. ** Changed in: hundredpapercuts Status: Invalid = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/871325 Title: Implement Unity Launcher API in Firefox for downloads' progress and quicklist Status in The Mozilla Firefox Browser: Confirmed Status in One Hundred Paper Cuts: Confirmed Status in “firefox” package in Ubuntu: Confirmed Bug description: In Ubuntu, Firefox should use the Unity Launcher API to show progress of the downloads and to show a quicklist (for example, New Window). There's yet an extension about the downloads' progress: UnityFox (https://launchpad.net/unityfox). Could you integrate the extension in Firefox by default? To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/871325/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 965510] Re: option --new-window not working correctly
Just reported it. Here is the URL: https://bugzilla.gnome.org/show_bug.cgi?id=673741 And the bug number is 673741. ** Bug watch added: GNOME Bug Tracker #673741 https://bugzilla.gnome.org/show_bug.cgi?id=673741 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/965510 Title: option --new-window not working correctly Status in Light-Weight Text Editor for Gnome: New Status in “gedit” package in Ubuntu: Confirmed Bug description: First, to reproduce, open Gedit (Text Editor). Right click on its icon in the Unity Taskbar. Oddly, clicking either of the two new options (create a new document or open a new window) opens a new window with two tabs, labelled Untitled Document 2 and the other one Untitled Document 3. What should happen is one new tab is opened when creating a new document, and one new window with one tab is opened for opening a new window. However, the aforementioned happens. I will upload a screenshot ASAP. I am running Precise Beta with the latest updates, and the latest version of Gedit. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gedit 3.3.8-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 ApportVersion: 1.95-0ubuntu1 Architecture: amd64 Date: Mon Mar 26 13:02:15 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20120321) ProcEnviron: TERM=xterm LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/965510/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 965510] Re: option --new-window not working correctly
I think I'll upload the bug to Gnome later today... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/965510 Title: option --new-window not working correctly Status in Light-Weight Text Editor for Gnome: New Status in “gedit” package in Ubuntu: Confirmed Bug description: First, to reproduce, open Gedit (Text Editor). Right click on its icon in the Unity Taskbar. Oddly, clicking either of the two new options (create a new document or open a new window) opens a new window with two tabs, labelled Untitled Document 2 and the other one Untitled Document 3. What should happen is one new tab is opened when creating a new document, and one new window with one tab is opened for opening a new window. However, the aforementioned happens. I will upload a screenshot ASAP. I am running Precise Beta with the latest updates, and the latest version of Gedit. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gedit 3.3.8-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 ApportVersion: 1.95-0ubuntu1 Architecture: amd64 Date: Mon Mar 26 13:02:15 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20120321) ProcEnviron: TERM=xterm LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/965510/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 965471] Re: Brasero Quicklists do not work, save open a new window, quit, and lock to launcher
On a side note, all of these actions work from the menus, and from the buttons in Brasero. So this bug may have to do with Unity. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brasero in Ubuntu. https://bugs.launchpad.net/bugs/965471 Title: Brasero Quicklists do not work, save open a new window, quit, and lock to launcher Status in “brasero” package in Ubuntu: New Bug description: Right click Brasero in the Unity taskbar and click any of the new quicklists, like burn an image file or copy a disc. They simply do not work. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: brasero 3.3.92-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 ApportVersion: 1.95-0ubuntu1 Architecture: amd64 Date: Mon Mar 26 12:29:51 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20120321) ProcEnviron: TERM=xterm LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: brasero UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/965471/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 965510] Re: option --new-window not working correctly
I don't yet have a Bugzilla account, but when I have free time, I'll get one (maybe this weekend), so I can report the bug upstream. If anyone else wants to report this bug to the GNOME team, go right ahead. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/965510 Title: option --new-window not working correctly Status in Light-Weight Text Editor for Gnome: New Status in “gedit” package in Ubuntu: Confirmed Bug description: First, to reproduce, open Gedit (Text Editor). Right click on its icon in the Unity Taskbar. Oddly, clicking either of the two new options (create a new document or open a new window) opens a new window with two tabs, labelled Untitled Document 2 and the other one Untitled Document 3. What should happen is one new tab is opened when creating a new document, and one new window with one tab is opened for opening a new window. However, the aforementioned happens. I will upload a screenshot ASAP. I am running Precise Beta with the latest updates, and the latest version of Gedit. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gedit 3.3.8-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 ApportVersion: 1.95-0ubuntu1 Architecture: amd64 Date: Mon Mar 26 13:02:15 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20120321) ProcEnviron: TERM=xterm LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/965510/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 967197] [NEW] Gedit Unity Launcher Inconsistency
Public bug reported: This bug is easy to see, but hard to describe. I've read all about Unity terminology at: http://askubuntu.com/questions/10228/whats-the-right-terminology-for-unitys-ui-elements/19166#19166 However, there is no mention for the little white dots for when you run an application. I will just refer to these as white dots for this bug report. Anyhow, back to the actual bug. Launch Gedit. Notice how the white dots appear next to it in the launcher. Now, lock it to the launcher. Close Gedit. Now, launch it again. Notice that no white dots appear next to it in the launcher. Now, unlock it from the launcher. Go to the Unity Dash and search for gedit and launch it again. Now, it won't even appear in the Unity launcher. I will upload a screenshot or two momentarily. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gedit 3.4.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-20.33-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 ApportVersion: 1.95-0ubuntu1 Architecture: amd64 Date: Wed Mar 28 10:55:13 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20120321) ProcEnviron: TERM=xterm LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gedit (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/967197 Title: Gedit Unity Launcher Inconsistency Status in “gedit” package in Ubuntu: New Bug description: This bug is easy to see, but hard to describe. I've read all about Unity terminology at: http://askubuntu.com/questions/10228/whats-the-right-terminology-for-unitys-ui-elements/19166#19166 However, there is no mention for the little white dots for when you run an application. I will just refer to these as white dots for this bug report. Anyhow, back to the actual bug. Launch Gedit. Notice how the white dots appear next to it in the launcher. Now, lock it to the launcher. Close Gedit. Now, launch it again. Notice that no white dots appear next to it in the launcher. Now, unlock it from the launcher. Go to the Unity Dash and search for gedit and launch it again. Now, it won't even appear in the Unity launcher. I will upload a screenshot or two momentarily. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gedit 3.4.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-20.33-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 ApportVersion: 1.95-0ubuntu1 Architecture: amd64 Date: Wed Mar 28 10:55:13 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20120321) ProcEnviron: TERM=xterm LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/967197/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 967197] Re: Gedit Unity Launcher Inconsistency
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/967197 Title: Gedit Unity Launcher Inconsistency Status in “gedit” package in Ubuntu: New Bug description: This bug is easy to see, but hard to describe. I've read all about Unity terminology at: http://askubuntu.com/questions/10228/whats-the-right-terminology-for-unitys-ui-elements/19166#19166 However, there is no mention for the little white dots for when you run an application. I will just refer to these as white dots for this bug report. Anyhow, back to the actual bug. Launch Gedit. Notice how the white dots appear next to it in the launcher. Now, lock it to the launcher. Close Gedit. Now, launch it again. Notice that no white dots appear next to it in the launcher. Now, unlock it from the launcher. Go to the Unity Dash and search for gedit and launch it again. Now, it won't even appear in the Unity launcher. I will upload a screenshot or two momentarily. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gedit 3.4.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-20.33-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 ApportVersion: 1.95-0ubuntu1 Architecture: amd64 Date: Wed Mar 28 10:55:13 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20120321) ProcEnviron: TERM=xterm LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/967197/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 967197] Re: Gedit Unity Launcher Inconsistency
This bug is strange. Now, I can't seem to reproduce it. It was reproducible before, though. I will give it a week, and if it doesn't come back, I'll mark the bug as invalid. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/967197 Title: Gedit Unity Launcher Inconsistency Status in “gedit” package in Ubuntu: New Bug description: This bug is easy to see, but hard to describe. I've read all about Unity terminology at: http://askubuntu.com/questions/10228/whats-the-right-terminology-for-unitys-ui-elements/19166#19166 However, there is no mention for the little white dots for when you run an application. I will just refer to these as white dots for this bug report. Anyhow, back to the actual bug. Launch Gedit. Notice how the white dots appear next to it in the launcher. Now, lock it to the launcher. Close Gedit. Now, launch it again. Notice that no white dots appear next to it in the launcher. Now, unlock it from the launcher. Go to the Unity Dash and search for gedit and launch it again. Now, it won't even appear in the Unity launcher. I will upload a screenshot or two momentarily. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gedit 3.4.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-20.33-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 ApportVersion: 1.95-0ubuntu1 Architecture: amd64 Date: Wed Mar 28 10:55:13 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20120321) ProcEnviron: TERM=xterm LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/967197/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 967197] Re: Gedit Unity Launcher Inconsistency
** Attachment added: Gedit hidden from the Unity launcher. https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/967197/+attachment/2955344/+files/hiddeninlauncher.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/967197 Title: Gedit Unity Launcher Inconsistency Status in “gedit” package in Ubuntu: New Bug description: This bug is easy to see, but hard to describe. I've read all about Unity terminology at: http://askubuntu.com/questions/10228/whats-the-right-terminology-for-unitys-ui-elements/19166#19166 However, there is no mention for the little white dots for when you run an application. I will just refer to these as white dots for this bug report. Anyhow, back to the actual bug. Launch Gedit. Notice how the white dots appear next to it in the launcher. Now, lock it to the launcher. Close Gedit. Now, launch it again. Notice that no white dots appear next to it in the launcher. Now, unlock it from the launcher. Go to the Unity Dash and search for gedit and launch it again. Now, it won't even appear in the Unity launcher. I will upload a screenshot or two momentarily. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gedit 3.4.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-20.33-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 ApportVersion: 1.95-0ubuntu1 Architecture: amd64 Date: Wed Mar 28 10:55:13 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20120321) ProcEnviron: TERM=xterm LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/967197/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 967197] Re: Gedit Unity Launcher Inconsistency
** Attachment added: Gedit during its first run, showing up correctly in the Unity launcher. https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/967197/+attachment/2955349/+files/normalgeditfirstrun.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/967197 Title: Gedit Unity Launcher Inconsistency Status in “gedit” package in Ubuntu: New Bug description: This bug is easy to see, but hard to describe. I've read all about Unity terminology at: http://askubuntu.com/questions/10228/whats-the-right-terminology-for-unitys-ui-elements/19166#19166 However, there is no mention for the little white dots for when you run an application. I will just refer to these as white dots for this bug report. Anyhow, back to the actual bug. Launch Gedit. Notice how the white dots appear next to it in the launcher. Now, lock it to the launcher. Close Gedit. Now, launch it again. Notice that no white dots appear next to it in the launcher. Now, unlock it from the launcher. Go to the Unity Dash and search for gedit and launch it again. Now, it won't even appear in the Unity launcher. I will upload a screenshot or two momentarily. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gedit 3.4.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-20.33-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 ApportVersion: 1.95-0ubuntu1 Architecture: amd64 Date: Wed Mar 28 10:55:13 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20120321) ProcEnviron: TERM=xterm LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/967197/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 967197] Re: Gedit Unity Launcher Inconsistency
Yep, this bug is definitley a Unity bug. When using the Window Switcher (Meta+W) I can see Gedit, but I cannot see it through Unity's ALT+TAB or anywhere in the Launcher. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/967197 Title: Gedit Unity Launcher Inconsistency Status in “gedit” package in Ubuntu: New Bug description: This bug is easy to see, but hard to describe. I've read all about Unity terminology at: http://askubuntu.com/questions/10228/whats-the-right-terminology-for-unitys-ui-elements/19166#19166 However, there is no mention for the little white dots for when you run an application. I will just refer to these as white dots for this bug report. Anyhow, back to the actual bug. Launch Gedit. Notice how the white dots appear next to it in the launcher. Now, lock it to the launcher. Close Gedit. Now, launch it again. Notice that no white dots appear next to it in the launcher. Now, unlock it from the launcher. Go to the Unity Dash and search for gedit and launch it again. Now, it won't even appear in the Unity launcher. I will upload a screenshot or two momentarily. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gedit 3.4.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-20.33-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 ApportVersion: 1.95-0ubuntu1 Architecture: amd64 Date: Wed Mar 28 10:55:13 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20120321) ProcEnviron: TERM=xterm LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/967197/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 967197] Re: Gedit Unity Launcher Inconsistency
The bug just came back as quickly as it seemed resolved. Sorry for the double posts. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/967197 Title: Gedit Unity Launcher Inconsistency Status in “gedit” package in Ubuntu: New Bug description: This bug is easy to see, but hard to describe. I've read all about Unity terminology at: http://askubuntu.com/questions/10228/whats-the-right-terminology-for-unitys-ui-elements/19166#19166 However, there is no mention for the little white dots for when you run an application. I will just refer to these as white dots for this bug report. Anyhow, back to the actual bug. Launch Gedit. Notice how the white dots appear next to it in the launcher. Now, lock it to the launcher. Close Gedit. Now, launch it again. Notice that no white dots appear next to it in the launcher. Now, unlock it from the launcher. Go to the Unity Dash and search for gedit and launch it again. Now, it won't even appear in the Unity launcher. I will upload a screenshot or two momentarily. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gedit 3.4.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-20.33-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 ApportVersion: 1.95-0ubuntu1 Architecture: amd64 Date: Wed Mar 28 10:55:13 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20120321) ProcEnviron: TERM=xterm LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/967197/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 967197] Re: Gedit Unity Launcher Inconsistency
The same thing is happening now with the Update Manager. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/967197 Title: Gedit Unity Launcher Inconsistency Status in “gedit” package in Ubuntu: New Bug description: This bug is easy to see, but hard to describe. I've read all about Unity terminology at: http://askubuntu.com/questions/10228/whats-the-right-terminology-for-unitys-ui-elements/19166#19166 However, there is no mention for the little white dots for when you run an application. I will just refer to these as white dots for this bug report. Anyhow, back to the actual bug. Launch Gedit. Notice how the white dots appear next to it in the launcher. Now, lock it to the launcher. Close Gedit. Now, launch it again. Notice that no white dots appear next to it in the launcher. Now, unlock it from the launcher. Go to the Unity Dash and search for gedit and launch it again. Now, it won't even appear in the Unity launcher. I will upload a screenshot or two momentarily. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gedit 3.4.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-20.33-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 ApportVersion: 1.95-0ubuntu1 Architecture: amd64 Date: Wed Mar 28 10:55:13 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20120321) ProcEnviron: TERM=xterm LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/967197/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 965471] [NEW] Brasero Quicklists do not work, save open a new window, quit, and lock to launcher
Public bug reported: Right click Brasero in the Unity taskbar and click any of the new quicklists, like burn an image file or copy a disc. They simply do not work. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: brasero 3.3.92-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 ApportVersion: 1.95-0ubuntu1 Architecture: amd64 Date: Mon Mar 26 12:29:51 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20120321) ProcEnviron: TERM=xterm LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: brasero UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: brasero (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brasero in Ubuntu. https://bugs.launchpad.net/bugs/965471 Title: Brasero Quicklists do not work, save open a new window, quit, and lock to launcher Status in “brasero” package in Ubuntu: New Bug description: Right click Brasero in the Unity taskbar and click any of the new quicklists, like burn an image file or copy a disc. They simply do not work. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: brasero 3.3.92-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 ApportVersion: 1.95-0ubuntu1 Architecture: amd64 Date: Mon Mar 26 12:29:51 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20120321) ProcEnviron: TERM=xterm LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: brasero UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/965471/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 965471] Re: Brasero Quicklists do not work, save open a new window, quit, and lock to launcher
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brasero in Ubuntu. https://bugs.launchpad.net/bugs/965471 Title: Brasero Quicklists do not work, save open a new window, quit, and lock to launcher Status in “brasero” package in Ubuntu: New Bug description: Right click Brasero in the Unity taskbar and click any of the new quicklists, like burn an image file or copy a disc. They simply do not work. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: brasero 3.3.92-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 ApportVersion: 1.95-0ubuntu1 Architecture: amd64 Date: Mon Mar 26 12:29:51 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20120321) ProcEnviron: TERM=xterm LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: brasero UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/965471/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 965510] Re: New Quicklists for Gedit not working correctly
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/965510 Title: New Quicklists for Gedit not working correctly Status in “gedit” package in Ubuntu: New Bug description: First, to reproduce, open Gedit (Text Editor). Right click on its icon in the Unity Taskbar. Oddly, clicking either of the two new options (create a new document or open a new window) opens a new window with two tabs, labelled Untitled Document 2 and the other one Untitled Document 3. What should happen is one new tab is opened when creating a new document, and one new window with one tab is opened for opening a new window. However, the aforementioned happens. I will upload a screenshot ASAP. I am running Precise Beta with the latest updates, and the latest version of Gedit. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gedit 3.3.8-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 ApportVersion: 1.95-0ubuntu1 Architecture: amd64 Date: Mon Mar 26 13:02:15 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20120321) ProcEnviron: TERM=xterm LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/965510/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 965510] Re: New Quicklists for Gedit not working correctly
** Attachment added: Before clicking on the quicklist. https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/965510/+attachment/2942276/+files/before.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/965510 Title: New Quicklists for Gedit not working correctly Status in “gedit” package in Ubuntu: New Bug description: First, to reproduce, open Gedit (Text Editor). Right click on its icon in the Unity Taskbar. Oddly, clicking either of the two new options (create a new document or open a new window) opens a new window with two tabs, labelled Untitled Document 2 and the other one Untitled Document 3. What should happen is one new tab is opened when creating a new document, and one new window with one tab is opened for opening a new window. However, the aforementioned happens. I will upload a screenshot ASAP. I am running Precise Beta with the latest updates, and the latest version of Gedit. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gedit 3.3.8-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 ApportVersion: 1.95-0ubuntu1 Architecture: amd64 Date: Mon Mar 26 13:02:15 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20120321) ProcEnviron: TERM=xterm LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/965510/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 965510] Re: New Quicklists for Gedit not working correctly
** Attachment added: After clicking on the quicklist item. https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/965510/+attachment/2942294/+files/after.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/965510 Title: New Quicklists for Gedit not working correctly Status in “gedit” package in Ubuntu: New Bug description: First, to reproduce, open Gedit (Text Editor). Right click on its icon in the Unity Taskbar. Oddly, clicking either of the two new options (create a new document or open a new window) opens a new window with two tabs, labelled Untitled Document 2 and the other one Untitled Document 3. What should happen is one new tab is opened when creating a new document, and one new window with one tab is opened for opening a new window. However, the aforementioned happens. I will upload a screenshot ASAP. I am running Precise Beta with the latest updates, and the latest version of Gedit. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gedit 3.3.8-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 ApportVersion: 1.95-0ubuntu1 Architecture: amd64 Date: Mon Mar 26 13:02:15 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20120321) ProcEnviron: TERM=xterm LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/965510/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 965510] [NEW] New Quicklists for Gedit not working correctly
Public bug reported: First, to reproduce, open Gedit (Text Editor). Right click on its icon in the Unity Taskbar. Oddly, clicking either of the two new options (create a new document or open a new window) opens a new window with two tabs, labelled Untitled Document 2 and the other one Untitled Document 3. What should happen is one new tab is opened when creating a new document, and one new window with one tab is opened for opening a new window. However, the aforementioned happens. I will upload a screenshot ASAP. I am running Precise Beta with the latest updates, and the latest version of Gedit. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gedit 3.3.8-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 ApportVersion: 1.95-0ubuntu1 Architecture: amd64 Date: Mon Mar 26 13:02:15 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20120321) ProcEnviron: TERM=xterm LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gedit (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/965510 Title: New Quicklists for Gedit not working correctly Status in “gedit” package in Ubuntu: New Bug description: First, to reproduce, open Gedit (Text Editor). Right click on its icon in the Unity Taskbar. Oddly, clicking either of the two new options (create a new document or open a new window) opens a new window with two tabs, labelled Untitled Document 2 and the other one Untitled Document 3. What should happen is one new tab is opened when creating a new document, and one new window with one tab is opened for opening a new window. However, the aforementioned happens. I will upload a screenshot ASAP. I am running Precise Beta with the latest updates, and the latest version of Gedit. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gedit 3.3.8-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 ApportVersion: 1.95-0ubuntu1 Architecture: amd64 Date: Mon Mar 26 13:02:15 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20120321) ProcEnviron: TERM=xterm LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/965510/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
