[Desktop-packages] [Bug 1951210] Re: libreoffice help doesn't open in firefox (404 error on file:///tmp/lu417531j7po.tmp/NewHelp0.html)
It also works properly on mine now -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1951210 Title: libreoffice help doesn't open in firefox (404 error on file:///tmp/lu417531j7po.tmp/NewHelp0.html) Status in libreoffice package in Ubuntu: Fix Released Status in snapd package in Ubuntu: Fix Committed Status in libreoffice source package in Jammy: Fix Released Status in snapd source package in Jammy: Confirmed Bug description: Ubuntu jammy live QA-test on - dell [optiplex] 780 (c2q-q9400, 8gb, amd/ati cedar radeon hd 5000/6000/7350/8350) Opened LibreOffice Writer as random apps in QA-test. Hit F1 to call help, and all I get is an error URL: file:///tmp/lu417531j7po.tmp/NewHelp0.html --- File not found Firefox can’t find the file at /tmp/lu417531j7po.tmp/NewHelp0.html. Check the file name for capitalization or other typing errors. Check to see if the file was moved, renamed or deleted. --- Firefox opens as a snap; but it isn't accessing the data from LibreOffice. Reported first at https://forum.snapcraft.io/t/firefox-snap-breaks- libreoffice-deb/27537 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libreoffice-writer 1:7.2.2-0ubuntu0.21.10.1 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu73 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.465+canary3.3 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 17 04:46:33 2021 LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (2026) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1951210/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1973467] Re: [Wayland] Backlight stays on with black screen when monitor should be sleeping
This also affects me, with a dual-monitor - laptop screen + one external monitor - setup (it's harder to tell if it also happens without the second monitor but I can check that if useful.) The second monitor is connected by either HDMI direct or HDMI via a thunderbolt dongle, and it happens in both cases. The only GPU in this laptop is i915, and it's running Ubuntu 22.04. It's maybe notable that in some but not all cases, I'll return and the mouse pointer is visible on the otherwise black screen. Also, it's not smooth. If I lock with super-L: * I get the lock screen * after a second, the lock screen fades to black, the laptop screen goes blank (maybe DPMS-off, it's hard to tell) and the external monitor reports "no signal" and turns itself off after a short moment * they remains off for a few seconds * they then wake up again and show the lock screen * after some time (20 seconds maybe) the external says "no signal" again and then powers off, laptop screen goes blank * it wakes up again, back at the lock screen * it settles on on with the lock screen showing, no change for a few minutes That's where I stopped, but I suspect that after some time the screen blanker turns the display blank but doesn't power things off. I can get a more precise sequence if it'd be useful. I ran these with both colour profiles and nightlight disabled, though they were previously enabled. My hypothesis is that the monitor turning off causes some event that causes Gnome to wake it up (in the past I've noticed windows moving from one screen to another, as if it were unplugged, but I haven't seen that recently), and then some other "let's not repeatedly power cycle things" check stops it happening too much. But that's 100% speculation. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1973467 Title: [Wayland] Backlight stays on with black screen when monitor should be sleeping Status in mutter package in Ubuntu: Confirmed Bug description: In Power -> Power Saving Options -> Screen Blank - the option states that the screen will be turned off after some period, which is what I'd expect from a sleep mode. I have a hybrid system. I have disabled the internal display and I use the external connected via HDMI (and I believe it is connected to the NVIDIA GPU). When the screen goes blank the external monitor is not turned off really. It goes blank but it is still turned on and glows, so no power is saved. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 510.60.02 Wed Mar 16 11:24:05 UTC 2022 GCC version: ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 15 19:16:56 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 630 [1028:0798] NVIDIA Corporation GP107M [GeForce GTX 1050 Ti Mobile] [10de:1c8c] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:0798] InstallationDate: Installed on 2022-05-01 (14 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Dell Inc. Inspiron 15 7000 Gaming ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=19e3ad11-d1ce-49ce-8809-80fc68612eb3 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/30/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 065C71 dmi.board.vendor: Dell Inc. dmi.board.version: X02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd08/30/2021:br1.15:svnDellInc.:pnInspiron157000Gaming:pvr:rvnDellInc.:rn065C71:rvrX02:cvnDellInc.:ct10:cvr:sku0798: dmi.product.family: Inspiron dmi.product.name: Inspiron 15 7000 Gaming dmi.product.sku: 0798 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1
[Desktop-packages] [Bug 1997175] [NEW] Help doesn't open the installed help files
Public bug reported: Open, for example, libreoffice calc. In the menu, open Help -> LibreOffice Help Firefox opens and says "Firefox can’t find the file at /usr/share/libreoffice/help/index.html?Target=scalc/.uno:HelpIndex=en- US=UNIX=7.4." $ ls /usr/share/libreoffice/help/index.html /usr/share/libreoffice/help/index.html I'm guessing this is due to firefox being in a snap and not having normal file system access. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: libreoffice-core 1:7.4.2~rc3-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Nov 20 20:15:08 2022 InstallationDate: Installed on 2022-03-23 (242 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) SourcePackage: libreoffice UpgradeStatus: Upgraded to kinetic on 2022-10-22 (29 days ago) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic wayland-session -- 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/1997175 Title: Help doesn't open the installed help files Status in libreoffice package in Ubuntu: New Bug description: Open, for example, libreoffice calc. In the menu, open Help -> LibreOffice Help Firefox opens and says "Firefox can’t find the file at /usr/share/libreoffice/help/index.html?Target=scalc/.uno:HelpIndex=en- US=UNIX=7.4." $ ls /usr/share/libreoffice/help/index.html /usr/share/libreoffice/help/index.html I'm guessing this is due to firefox being in a snap and not having normal file system access. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: libreoffice-core 1:7.4.2~rc3-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Nov 20 20:15:08 2022 InstallationDate: Installed on 2022-03-23 (242 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) SourcePackage: libreoffice UpgradeStatus: Upgraded to kinetic on 2022-10-22 (29 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1997175/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966787] Re: Totem crashes on launch | GStreamer-GL-CRITICAL **: Failed to flush Wayland connection | Gdk-Message: Error flushing display: Protocol error
*** This bug is a duplicate of bug 1965563 *** https://bugs.launchpad.net/bugs/1965563 Totem works in 22.10 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1966787 Title: Totem crashes on launch | GStreamer-GL-CRITICAL **: Failed to flush Wayland connection | Gdk-Message: Error flushing display: Protocol error Status in NVIDIA / egl-wayland: Unknown Status in egl-wayland package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Status in totem package in Ubuntu: Confirmed Bug description: If I launch totem, it crashes pretty much immediately. I resolved this by deleting .config/totem. I had moved some video files that had been previously opened within it recently, so possibly it was trying to reference them (for thumbnails or whatever) and that broke it. robin@malik:~$ totem (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection Gdk-Message: 18:00:17.844: Error flushing display: Protocol error robin@malik:~$ ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: totem 42.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 28 18:00:39 2022 InstallationDate: Installed on 2022-03-23 (5 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/egl-wayland/+bug/1966787/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969602] Re: gnome-shell with "Focus on hover" behaves wrongly when alt-tabbing
Sorry, didn't see the reply with the upstream link. It seems different to me, I haven't had any issues (that I've noticed) with invisible windows. I've attached a screen recording. In this, I have terminal in the foreground and alt-tab to settings. Because the mouse is outside the settings window (i.e., still over terminal), terminal gets pulled almost immediately to the front again. ** Attachment added: "video of the issue" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1969602/+attachment/5594297/+files/Screencast%20from%2001-06-22%2012%3A19%3A59.webm -- 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/1969602 Title: gnome-shell with "Focus on hover" behaves wrongly when alt-tabbing Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I have set gnome to "focus on hover", i.e. focus follows mouse. If I alt-tab to bring a window to the front but the mouse is over another window, then the hovered-over window will reclaim focus and the window I raised will typically get covered up again. In previous gnome versions, if I explicitly focussed a window via keyboard shortcuts, it remained focussed and I think this is the preferred behaviour. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 20 11:35:20 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-03-17 (33 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1969602/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1976356] [NEW] "Dim screen" setting still operates when turned off
Public bug reported: I have "dim screen" set to off in my power settings, because it's mildly annoying when I'm on power, which is most of the time. Despite this, the screen will still dim after 30 seconds of inactivity. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-power-manager 3.32.0-2build2 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue May 31 11:23:59 2022 InstallationDate: Installed on 2022-03-17 (74 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-power-manager UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-power-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session ** Attachment added: "Screenshot of the setting" https://bugs.launchpad.net/bugs/1976356/+attachment/5594063/+files/Screenshot%20from%202022-05-31%2011-24-57.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1976356 Title: "Dim screen" setting still operates when turned off Status in gnome-power-manager package in Ubuntu: New Bug description: I have "dim screen" set to off in my power settings, because it's mildly annoying when I'm on power, which is most of the time. Despite this, the screen will still dim after 30 seconds of inactivity. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-power-manager 3.32.0-2build2 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue May 31 11:23:59 2022 InstallationDate: Installed on 2022-03-17 (74 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-power-manager UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1976356/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1974435] Re: wacom tablet button selection interface doesn't allow picking from dropdown
Someone else having the same issue, with workarounds: https://www.reddit.com/r/gnome/comments/tzbcru/gnome_42_wacom_cannot_set_tablet_buttons_actions/ -- 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/1974435 Title: wacom tablet button selection interface doesn't allow picking from dropdown Status in gnome-control-center package in Ubuntu: New Bug description: I have a graphics table (Wacom Co., Ltd CTL-4100WL [Intuos BT (S)]), and gnome sees it happily. It provides me an interface to bind the buttons on the tablet to other functions, for example keyboard shortcuts. However it's not possible to select options in the dropdown for doing this, the mouse clicks are simply ignored on the dropdown. I also can't send a screenshot of the interface because prt scr doesn't work there, and when I use a different method I just get a black screenshot - so attached is a photo of the screen, sorry. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.4-1ubuntu13.2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri May 20 13:42:02 2022 InstallationDate: Installed on 2022-03-23 (57 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1974435/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1974435] [NEW] wacom tablet button selection interface doesn't allow picking from dropdown
Public bug reported: I have a graphics table (Wacom Co., Ltd CTL-4100WL [Intuos BT (S)]), and gnome sees it happily. It provides me an interface to bind the buttons on the tablet to other functions, for example keyboard shortcuts. However it's not possible to select options in the dropdown for doing this, the mouse clicks are simply ignored on the dropdown. I also can't send a screenshot of the interface because prt scr doesn't work there, and when I use a different method I just get a black screenshot - so attached is a photo of the screen, sorry. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.4-1ubuntu13.2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri May 20 13:42:02 2022 InstallationDate: Installed on 2022-03-23 (57 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session ** Attachment added: "Photo of the interface that doesn't work" https://bugs.launchpad.net/bugs/1974435/+attachment/5591555/+files/PXL_20220520_114842609.MP.jpg -- 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/1974435 Title: wacom tablet button selection interface doesn't allow picking from dropdown Status in gnome-control-center package in Ubuntu: New Bug description: I have a graphics table (Wacom Co., Ltd CTL-4100WL [Intuos BT (S)]), and gnome sees it happily. It provides me an interface to bind the buttons on the tablet to other functions, for example keyboard shortcuts. However it's not possible to select options in the dropdown for doing this, the mouse clicks are simply ignored on the dropdown. I also can't send a screenshot of the interface because prt scr doesn't work there, and when I use a different method I just get a black screenshot - so attached is a photo of the screen, sorry. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.4-1ubuntu13.2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri May 20 13:42:02 2022 InstallationDate: Installed on 2022-03-23 (57 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1974435/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1973886] Re: "Install additional software" button does nothing
note: I apt installed gstreamer1.0-plugins-bad after trying the button, but before doing ubuntu-bug, hence it showing up in the GstreamerVersions.txt file. -- 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/1973886 Title: "Install additional software" button does nothing Status in rhythmbox package in Ubuntu: New Bug description: I imported some m4a files, which by default can't be played. Rhythmbox gives me a button "Install Additional Software" to install the required codecs. Clicking this button does nothing. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: rhythmbox 3.4.4-5ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed May 18 11:06:03 2022 InstallationDate: Installed on 2022-03-17 (61 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: rhythmbox UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1973886/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1973886] [NEW] "Install additional software" button does nothing
Public bug reported: I imported some m4a files, which by default can't be played. Rhythmbox gives me a button "Install Additional Software" to install the required codecs. Clicking this button does nothing. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: rhythmbox 3.4.4-5ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed May 18 11:06:03 2022 InstallationDate: Installed on 2022-03-17 (61 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: rhythmbox UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session ** Attachment added: "Screenshot showing the button in question" https://bugs.launchpad.net/bugs/1973886/+attachment/5590645/+files/Screenshot%20from%202022-05-18%2011-09-56.png -- 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/1973886 Title: "Install additional software" button does nothing Status in rhythmbox package in Ubuntu: New Bug description: I imported some m4a files, which by default can't be played. Rhythmbox gives me a button "Install Additional Software" to install the required codecs. Clicking this button does nothing. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: rhythmbox 3.4.4-5ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed May 18 11:06:03 2022 InstallationDate: Installed on 2022-03-17 (61 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: rhythmbox UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1973886/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966787] Re: Totem crashes on launch | GStreamer-GL-CRITICAL **: Failed to flush Wayland connection | Gdk-Message: Error flushing display: Protocol error
https://github.com/NVIDIA/egl-wayland/issues/41#issuecomment-959550980 and https://bugs.launchpad.net/egl-wayland/+bug/1968488 look related. ** Bug watch added: github.com/NVIDIA/egl-wayland/issues #41 https://github.com/NVIDIA/egl-wayland/issues/41 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1966787 Title: Totem crashes on launch | GStreamer-GL-CRITICAL **: Failed to flush Wayland connection | Gdk-Message: Error flushing display: Protocol error Status in totem package in Ubuntu: New Bug description: If I launch totem, it crashes pretty much immediately. I resolved this by deleting .config/totem. I had moved some video files that had been previously opened within it recently, so possibly it was trying to reference them (for thumbnails or whatever) and that broke it. robin@malik:~$ totem (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection Gdk-Message: 18:00:17.844: Error flushing display: Protocol error robin@malik:~$ ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: totem 42.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 28 18:00:39 2022 InstallationDate: Installed on 2022-03-23 (5 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1966787/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969753] [NEW] gnome-power-statistics graph labels hard to read in dark mode
Public bug reported: I am running with Ubuntu set to dark mode. The graph labels on gnome- power-statistics are black on dark grey, which is very hard to read. See attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-power-manager 3.32.0-2build2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 21 11:20:41 2022 InstallationDate: Installed on 2022-03-17 (34 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-power-manager UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-power-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session ** Attachment added: "screenshot showing the problem" https://bugs.launchpad.net/bugs/1969753/+attachment/5582023/+files/Screenshot%20from%202022-04-21%2011-21-10.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1969753 Title: gnome-power-statistics graph labels hard to read in dark mode Status in gnome-power-manager package in Ubuntu: New Bug description: I am running with Ubuntu set to dark mode. The graph labels on gnome- power-statistics are black on dark grey, which is very hard to read. See attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-power-manager 3.32.0-2build2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 21 11:20:41 2022 InstallationDate: Installed on 2022-03-17 (34 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-power-manager UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1969753/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969602] [NEW] gnome-shell with "Focus on hover" behaves wrongly when alt-tabbing
Public bug reported: I have set gnome to "focus on hover", i.e. focus follows mouse. If I alt-tab to bring a window to the front but the mouse is over another window, then the hovered-over window will reclaim focus and the window I raised will typically get covered up again. In previous gnome versions, if I explicitly focussed a window via keyboard shortcuts, it remained focussed and I think this is the preferred behaviour. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 20 11:35:20 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-03-17 (33 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1969602 Title: gnome-shell with "Focus on hover" behaves wrongly when alt-tabbing Status in gnome-shell package in Ubuntu: New Bug description: I have set gnome to "focus on hover", i.e. focus follows mouse. If I alt-tab to bring a window to the front but the mouse is over another window, then the hovered-over window will reclaim focus and the window I raised will typically get covered up again. In previous gnome versions, if I explicitly focussed a window via keyboard shortcuts, it remained focussed and I think this is the preferred behaviour. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 20 11:35:20 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-03-17 (33 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1969602/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966787] Re: Totem crashes on launch | GStreamer-GL-CRITICAL **: Failed to flush Wayland connection | Gdk-Message: Error flushing display: Protocol error
Oh wait, I'm being hit with Bug #1968929 where I now don't get wayland at all and so fell back to Xorg. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1966787 Title: Totem crashes on launch | GStreamer-GL-CRITICAL **: Failed to flush Wayland connection | Gdk-Message: Error flushing display: Protocol error Status in totem package in Ubuntu: New Bug description: If I launch totem, it crashes pretty much immediately. I resolved this by deleting .config/totem. I had moved some video files that had been previously opened within it recently, so possibly it was trying to reference them (for thumbnails or whatever) and that broke it. robin@malik:~$ totem (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection Gdk-Message: 18:00:17.844: Error flushing display: Protocol error robin@malik:~$ ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: totem 42.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 28 18:00:39 2022 InstallationDate: Installed on 2022-03-23 (5 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1966787/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966787] Re: Totem crashes on launch | GStreamer-GL-CRITICAL **: Failed to flush Wayland connection | Gdk-Message: Error flushing display: Protocol error
After a recent update followed by a reboot, totem works again. Some mutter related updates were there, so you might well have been right about that. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1966787 Title: Totem crashes on launch | GStreamer-GL-CRITICAL **: Failed to flush Wayland connection | Gdk-Message: Error flushing display: Protocol error Status in totem package in Ubuntu: New Bug description: If I launch totem, it crashes pretty much immediately. I resolved this by deleting .config/totem. I had moved some video files that had been previously opened within it recently, so possibly it was trying to reference them (for thumbnails or whatever) and that broke it. robin@malik:~$ totem (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection Gdk-Message: 18:00:17.844: Error flushing display: Protocol error robin@malik:~$ ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: totem 42.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 28 18:00:39 2022 InstallationDate: Installed on 2022-03-23 (5 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1966787/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966787] Re: Totem crashes on launch or when attempting to play video with a Wayland flush error
> 1. Tell us which message you now mean; and robin@malik:~/Videos$ totem Outrageous\ Fortune\ S04E08.m4v Gdk-Message: 11:02:22.100: Error flushing display: Protocol error robin@malik:~/Videos$ This result appears pretty much immediately, and no desktop window opens. > 2. Follow these instructions: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment No crash dump is produced as this isn't a SIGSEV or similar style crash, more a failing to work so shutting down abort. > Maybe related? This looks to me more like a screencast bug rather than a playback bug. Maybe relevant, I do get slightly different results sometimes. I just tried it again: robin@malik:~/Videos$ totem Outrageous\ Fortune\ S04E08.m4v (totem:3576): GStreamer-GL-CRITICAL **: 11:09:08.153: Failed to flush Wayland connection Gdk-Message: 11:09:08.153: Error flushing display: Protocol error (totem:3576): GStreamer-GL-CRITICAL **: 11:09:08.153: Failed to flush Wayland connection robin@malik:~/Videos$ i.e sometimes the "Failed to flush" message appears, sometimes it doesn't. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1966787 Title: Totem crashes on launch or when attempting to play video with a Wayland flush error Status in totem package in Ubuntu: Incomplete Bug description: If I launch totem, it crashes pretty much immediately. I resolved this by deleting .config/totem. I had moved some video files that had been previously opened within it recently, so possibly it was trying to reference them (for thumbnails or whatever) and that broke it. robin@malik:~$ totem (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection Gdk-Message: 18:00:17.844: Error flushing display: Protocol error robin@malik:~$ ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: totem 42.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 28 18:00:39 2022 InstallationDate:
[Desktop-packages] [Bug 1966787] Re: Totem crashes on launch or when attempting to play video with a Wayland flush error
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1966787 Title: Totem crashes on launch or when attempting to play video with a Wayland flush error Status in totem package in Ubuntu: Incomplete Bug description: If I launch totem, it crashes pretty much immediately. I resolved this by deleting .config/totem. I had moved some video files that had been previously opened within it recently, so possibly it was trying to reference them (for thumbnails or whatever) and that broke it. robin@malik:~$ totem (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection Gdk-Message: 18:00:17.844: Error flushing display: Protocol error robin@malik:~$ ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: totem 42.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 28 18:00:39 2022 InstallationDate: Installed on 2022-03-23 (5 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1966787/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966787] Re: Totem crashes on launch
Update: my resolution didn't resolve it. If I attempt to play a file, it crashes with the same message as above. ** Summary changed: - Totem crashes on launch + Totem crashes on launch or when attempting to play video with a Wayland flush error -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1966787 Title: Totem crashes on launch or when attempting to play video with a Wayland flush error Status in totem package in Ubuntu: New Bug description: If I launch totem, it crashes pretty much immediately. I resolved this by deleting .config/totem. I had moved some video files that had been previously opened within it recently, so possibly it was trying to reference them (for thumbnails or whatever) and that broke it. robin@malik:~$ totem (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection Gdk-Message: 18:00:17.844: Error flushing display: Protocol error robin@malik:~$ ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: totem 42.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 28 18:00:39 2022 InstallationDate: Installed on 2022-03-23 (5 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1966787/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966787] [NEW] Totem crashes on launch or when attempting to play video with a Wayland flush error
Public bug reported: If I launch totem, it crashes pretty much immediately. I resolved this by deleting .config/totem. I had moved some video files that had been previously opened within it recently, so possibly it was trying to reference them (for thumbnails or whatever) and that broke it. robin@malik:~$ totem (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection Gdk-Message: 18:00:17.844: Error flushing display: Protocol error robin@malik:~$ ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: totem 42.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 28 18:00:39 2022 InstallationDate: Installed on 2022-03-23 (5 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' ** Affects: totem (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1966787 Title: Totem crashes on launch or when attempting to play video with a Wayland flush error Status in totem package in Ubuntu: New Bug description: If I launch totem, it crashes pretty much immediately. I resolved this by deleting .config/totem. I had moved some video files that had been previously opened within it recently, so possibly it was trying to reference them (for thumbnails or whatever) and that broke it. robin@malik:~$ totem (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **:
[Desktop-packages] [Bug 1966505] [NEW] Lock screen should listen for fingerprint immediately
Public bug reported: I have a laptop with a fingerprint reader that works fine. When the screensaver comes on, I can unlock one of two ways: 1) enter my password, 2) press a key and then press the fingerprint reader With 2) I'm required to press a key before the fingerprint reader starts listening. Instead, it should listen all the time so that I can just open the laptop to wake it from suspend, or if not suspended I can just press the fingerprint reader and have it unlock immediately. This way it'll behave more similar to how a phone's fingerprint reader does and save a (minor) unnecessary interaction. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-screensaver (not installed) ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Mar 25 18:50:10 2022 InstallationDate: Installed on 2022-03-23 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) SourcePackage: gnome-screensaver UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-screensaver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1966505 Title: Lock screen should listen for fingerprint immediately Status in gnome-screensaver package in Ubuntu: New Bug description: I have a laptop with a fingerprint reader that works fine. When the screensaver comes on, I can unlock one of two ways: 1) enter my password, 2) press a key and then press the fingerprint reader With 2) I'm required to press a key before the fingerprint reader starts listening. Instead, it should listen all the time so that I can just open the laptop to wake it from suspend, or if not suspended I can just press the fingerprint reader and have it unlock immediately. This way it'll behave more similar to how a phone's fingerprint reader does and save a (minor) unnecessary interaction. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-screensaver (not installed) ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Mar 25 18:50:10 2022 InstallationDate: Installed on 2022-03-23 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) SourcePackage: gnome-screensaver UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1966505/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1934579] Re: Nautilus crashes when opening places from the dock contextmenu
This is reproducible in 22.04 also -- 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/1934579 Title: Nautilus crashes when opening places from the dock contextmenu Status in nautilus package in Ubuntu: Confirmed Bug description: After updating to Ubuntu 21.04, Nautilus crashes every time I try to open a second folder by right-clicking on the Nautilus icon in the "Favorites" left sidebar (i.e., launch panel) and selecting a bookmarked "Places" folder. Normally, this would open a second Nautilus window for the selected folder, but instead, any open Nautilus windows disappear and no window opens for the selected folder. In other words, Nautilus crashes. This did not occur on Ubuntu 20.10. This AskUbuntu post describes the same issue: https://askubuntu.com/questions/1344175/nautilus-crashes-when-trying- to-open-another-window-by-right-clicking-the-nautil If, instead, I right-click the Nautilus icon, select "New Window" and then select the desired "Places" folder from the left sidebar of the newly opened window, Nautilus does not crash. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: nautilus 1:3.38.2-1ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Jul 4 13:36:13 2021 InstallationDate: Installed on 2020-02-05 (514 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: nautilus UpgradeStatus: Upgraded to hirsute on 2021-06-30 (4 days ago) usr_lib_nautilus: evince40.1-1 file-roller 3.38.1-1 nautilus-extension-gnome-terminal 3.38.1-1ubuntu1 nautilus-share0.7.3-2ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1934579/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966054] [NEW] Dock gets confused in dual monitor setup with different scaling
Public bug reported: I have two monitors: the inbuilt laptop one, 1920x1080 at 125% scaling shifted slightly down to match the relative heights on my desk, and an external one, 1920x1080 at 100% scaling, primary. I have the dock set to autohide. When I open the dock by mousing to the side of the primary monitor it will appear, usually with the icons correct. Then, I think as a result of pushing the mouse slightly more to the left but not off the monitor (as the edge is slightly sticky), the icons will expand (see screenshot) I suspect as though they're picking up the scaling from the wrong monitor. Typically mousing over them will cause them to go back to their proper size again. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell-extension-ubuntu-dock 72~ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Mar 23 10:43:34 2022 InstallationDate: Installed on 2022-03-17 (5 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session ** Attachment added: "screenshot illustrating the incorrectly sized icons" https://bugs.launchpad.net/bugs/1966054/+attachment/5572135/+files/Screenshot-1-cropped.png -- 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/1966054 Title: Dock gets confused in dual monitor setup with different scaling Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: I have two monitors: the inbuilt laptop one, 1920x1080 at 125% scaling shifted slightly down to match the relative heights on my desk, and an external one, 1920x1080 at 100% scaling, primary. I have the dock set to autohide. When I open the dock by mousing to the side of the primary monitor it will appear, usually with the icons correct. Then, I think as a result of pushing the mouse slightly more to the left but not off the monitor (as the edge is slightly sticky), the icons will expand (see screenshot) I suspect as though they're picking up the scaling from the wrong monitor. Typically mousing over them will cause them to go back to their proper size again. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell-extension-ubuntu-dock 72~ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Mar 23 10:43:34 2022 InstallationDate: Installed on 2022-03-17 (5 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1966054/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1292490] Re: totem/totem-video-thumbnailer crashed with SIGSEGV in magazine_chain_pop_head() from thread_memory_magazine1_alloc() from g_slice_alloc() from g_slice_alloc0() fro
Personally I haven't seen it in roughly forever. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1292490 Title: totem/totem-video-thumbnailer crashed with SIGSEGV in magazine_chain_pop_head() from thread_memory_magazine1_alloc() from g_slice_alloc() from g_slice_alloc0() from gst_ffmpegviddec_video_frame_new() Status in totem package in Ubuntu: Incomplete Bug description: Totem froze and eventually crashed when seeking through a Matroska H.264 video file. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: totem 3.10.1-1ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Unity Date: Sat Mar 15 00:53:28 2014 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2011-04-26 (1052 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) ProcCmdline: totem /home/username/Downloads/Californication.S06E03.720p.HDTV.x264-IMMERSE.mkv SegvAnalysis: Segfault happened at: 0x7f2b1e82628a :mov 0x8(%rdx),%rbx PC (0x7f2b1e82628a) ok source "0x8(%rdx)" (0x408) not located in a known VMA region (needed readable region)! destination "%rbx" ok Stack memory exhausted (SP below stack segment) SegvReason: reading unknown VMA Signal: 11 SourcePackage: totem StacktraceTop: g_slice_alloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_slice_alloc0 () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstlibav.so ?? () from /usr/lib/x86_64-linux-gnu/libavcodec.so.54 avcodec_decode_video2 () from /usr/lib/x86_64-linux-gnu/libavcodec.so.54 Title: totem crashed with SIGSEGV in g_slice_alloc() UpgradeStatus: Upgraded to trusty on 2014-03-09 (5 days ago) UserGroups: adm admin cdrom dialout fuse lpadmin netdev plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1292490/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725955] Re: "Printer added" notification
It still occurs in 18.04. -- 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/1725955 Title: "Printer added" notification Status in GNOME Settings Daemon: Confirmed Status in gnome-settings-daemon package in Ubuntu: Triaged Bug description: I've recently installed Ubuntu 17.10 (Gnome shell). After a while I saw an OSD notification with the message "printer added", and thought that must be because of the new driverless printers feature in the kernel. I have a brother printer in the network, and I tested it and it worked. The thing is that the message repeats itself, approximately every two minutes, and it's really distracting. I saw a question about this on AskUbuntu (https://askubuntu.com/questions/918462/ubuntu-17-04 -printer-added-notifications-under-gnome), and a solution, but it seemed like no one had filed a bug report. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1725955/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1795121] Re: 18.10: Indicator icons not shown in the panel
Attached. This is a pretty much everything (I removed the network- related stuff) it covers a boot with the issue until a shutdown (as I restarted to try to fix the issue.) ** Attachment added: "journalctl covering a boot that had the issue" https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1795121/+attachment/5239823/+files/journalctl.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1795121 Title: 18.10: Indicator icons not shown in the panel Status in gnome-shell-extension-appindicator package in Ubuntu: Confirmed Bug description: The indicator icons are not showing on a fresh installation of Ubuntu 18.10 beta. On 18.04 I can see the tray icons of Chrome, Hangouts, Dropbox and InSync but on 18.10 they are missing. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell-extension-appindicator 22-1 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Sep 29 10:00:34 2018 Dependencies: InstallationDate: Installed on 2018-09-28 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell-extension-appindicator UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1795121/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1795121] Re: 18.10: Indicator icons not shown in the panel
The only extensions I have active are: * https://extensions.gnome.org/extension/750/openweather/ (which is broken due to not handling proxies anyway) * https://extensions.gnome.org/extension/905/refresh-wifi-connections/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1795121 Title: 18.10: Indicator icons not shown in the panel Status in gnome-shell-extension-appindicator package in Ubuntu: Confirmed Bug description: The indicator icons are not showing on a fresh installation of Ubuntu 18.10 beta. On 18.04 I can see the tray icons of Chrome, Hangouts, Dropbox and InSync but on 18.10 they are missing. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell-extension-appindicator 22-1 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Sep 29 10:00:34 2018 Dependencies: InstallationDate: Installed on 2018-09-28 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell-extension-appindicator UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1795121/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1795121] Re: 18.10: Indicator icons not shown in the panel
I'm away from my computer right now, but in case it's useful: It happens after first login after boot, but not always. This said, I did about four reboots today and it happened on every one. In the past it would happen sometimes. There's not enough info there to be statistical however, beyond it happening often. It doesn't seem to happen on logout then login. Suspend/resume seems to have no impact. I'll check out the extensions thing tomorrow, but from memory I only have one that adds a WiFi scanning button. Is there an easy place to see what extensions are installed? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1795121 Title: 18.10: Indicator icons not shown in the panel Status in gnome-shell-extension-appindicator package in Ubuntu: Confirmed Bug description: The indicator icons are not showing on a fresh installation of Ubuntu 18.10 beta. On 18.04 I can see the tray icons of Chrome, Hangouts, Dropbox and InSync but on 18.10 they are missing. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell-extension-appindicator 22-1 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Sep 29 10:00:34 2018 Dependencies: InstallationDate: Installed on 2018-09-28 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell-extension-appindicator UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1795121/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1795121] Re: 18.10: Indicator icons not shown in the panel
I see this regularly on 18.04 too. It seems to have sprung up in the past few months. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1795121 Title: 18.10: Indicator icons not shown in the panel Status in gnome-shell-extension-appindicator package in Ubuntu: Confirmed Bug description: The indicator icons are not showing on a fresh installation of Ubuntu 18.10 beta. On 18.04 I can see the tray icons of Chrome, Hangouts, Dropbox and InSync but on 18.10 they are missing. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell-extension-appindicator 22-1 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Sep 29 10:00:34 2018 Dependencies: InstallationDate: Installed on 2018-09-28 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell-extension-appindicator UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1795121/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1756811] [NEW] gnome-shell uses too much memory
Public bug reported: After running for a few weeks, gnome-shell is using more memory than is reasonable: PID USER PRI NI VIRT RES SHR S CPU% MEM% TIME+ Command 1692 robin 20 0 4380M 956M 48792 S 0.7 6.0 12h59:46 /usr/bin/gnome-shell as time goes on, it tends to slowly creep up. Unfortunately it is harder to restart than something like Firefox. If you kill it, it doesn't automatically come back. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.2-0ubuntu0.1 ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 19 08:46:49 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: b'org.gnome.shell' b'enabled-extensions' b"['openweather-extens...@jenslody.de', 'refresh-w...@kgshank.net']" b'org.gnome.shell' b'enable-hot-corners' b'true' b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 'firefox.desktop', 'org.gnome.Terminal.desktop', 'thunderbird.desktop', 'pidgin.desktop', 'quasselclient.desktop', 'telegramdesktop.desktop', 'slack.desktop', 'google-play-music-desktop-player.desktop', 'keepassx.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'clock-show-date' b'true' InstallationDate: Installed on 2015-11-30 (839 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2018-01-12 (65 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- 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/1756811 Title: gnome-shell uses too much memory Status in gnome-shell package in Ubuntu: New Bug description: After running for a few weeks, gnome-shell is using more memory than is reasonable: PID USER PRI NI VIRT RES SHR S CPU% MEM% TIME+ Command 1692 robin 20 0 4380M 956M 48792 S 0.7 6.0 12h59:46 /usr/bin/gnome-shell as time goes on, it tends to slowly creep up. Unfortunately it is harder to restart than something like Firefox. If you kill it, it doesn't automatically come back. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.2-0ubuntu0.1 ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 19 08:46:49 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: b'org.gnome.shell' b'enabled-extensions' b"['openweather-extens...@jenslody.de', 'refresh-w...@kgshank.net']" b'org.gnome.shell' b'enable-hot-corners' b'true' b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 'firefox.desktop', 'org.gnome.Terminal.desktop', 'thunderbird.desktop', 'pidgin.desktop', 'quasselclient.desktop', 'telegramdesktop.desktop', 'slack.desktop', 'google-play-music-desktop-player.desktop', 'keepassx.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'clock-show-date' b'true' InstallationDate: Installed on 2015-11-30 (839 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2018-01-12 (65 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1756811/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1397142] Re: Bluetooth headset play/pause key not fully effective in various media players
For my case, with Bose QC35 bluetooth headphones, skip forward and backward worked with no configuration, but play/pause didn't at all. The workaround I found was to use xbindkeys with the help of xbindkeys- config to set the following: "xdotool key XF86AudioPlay" c:208 in my ~/.xbindkeysrc. This is strange, as pretty much everything else sees the button as XF86AudioPlay, but it wasn't being seen as a media key by the player. But it works now. -- 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/1397142 Title: Bluetooth headset play/pause key not fully effective in various media players Status in GNOME Shell: New Status in Unity: Invalid Status in gnome-settings-daemon package in Ubuntu: Confirmed Status in unity-settings-daemon package in Ubuntu: Confirmed Bug description: UPDATE: Function GnomeGrabber::Impl::ActivateDBusAction dont emit dbus signal "AcceleratorActivated" if be pressed key with keycodes 208 or 215 (its XF86AudioPlay). Can be reproduce: run in one terminal 'dbus-monitor "path=/org/gnome/Shell"' and in other run 'xdotool key NUMBER' where NUMBER - keycodes. Can be check 172, 172, 209, bugged 208 and 215 and other. - I have a Sony SRS-BTM8 Bluetooth speaker, and its audio side works fairly well with Ubuntu. It also has a play/pause button and that doesn't work so well. I think the problem lies in unity-settings-daemon. To demonstrate that the Bluetooth side is working, if I switch to a text console and run "evtest /dev/input/event9", then when pressing the button I get events for KEY_PLAYCD if the speaker is not playing anything, and alternating KEY_PAUSECD and KEY_PLAYCD if it is playing something. However, within the Unity desktop I find that if I'm running Banshee or Rhythmbox then pressing the button successfully pauses the music, but doesn't start it playing again. If I run "xev" and give it the keyboard focus while testing this (so xev sees all ungrabbed keystrokes) then it sees only a KeyRelease event for XF86AudioPause, but both KeyPress and KeyRelease events for XF86AudioPlay. I've attached the full output from xev. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-settings-daemon 14.04.0+14.04.20140606-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-25.33~14.04.2-generic 3.16.7 Uname: Linux 3.16.0-25-generic i686 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: i386 CurrentDesktop: Unity Date: Thu Nov 27 23:43:01 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-motts-20100121-3 EcryptfsInUse: Yes InstallationDate: Installed on 2010-06-09 (1632 days ago) InstallationMedia: Ubuntu GNU/Linux 9.10 "Karmic" - Build i386 LIVE Binary 20100121-21:52 SourcePackage: unity-settings-daemon UpgradeStatus: Upgraded to trusty on 2014-08-15 (104 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1397142/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1469355] [NEW] aspell doesn't warn when given an unknown language string
Public bug reported: If I run, say: $ aspell -l en_NZ --mode=tex check file.tex or $ aspell -l en_BLAH --mode=tex check file.tex aspell will continue on and do its spell checking in en_US, which is very incorrect behaviour. It should throw an error rather than proceed on doing the wrong thing. If I use en_GB it'll use correct spellings for that language. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: aspell 0.60.7~20110707-1.3 ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8 Uname: Linux 3.19.0-21-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: Unity Date: Sat Jun 27 15:54:06 2015 InstallationDate: Installed on 2011-04-26 (1522 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) SourcePackage: aspell UpgradeStatus: Upgraded to vivid on 2015-04-26 (61 days ago) ** Affects: aspell (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 aspell in Ubuntu. https://bugs.launchpad.net/bugs/1469355 Title: aspell doesn't warn when given an unknown language string Status in aspell package in Ubuntu: New Bug description: If I run, say: $ aspell -l en_NZ --mode=tex check file.tex or $ aspell -l en_BLAH --mode=tex check file.tex aspell will continue on and do its spell checking in en_US, which is very incorrect behaviour. It should throw an error rather than proceed on doing the wrong thing. If I use en_GB it'll use correct spellings for that language. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: aspell 0.60.7~20110707-1.3 ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8 Uname: Linux 3.19.0-21-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: Unity Date: Sat Jun 27 15:54:06 2015 InstallationDate: Installed on 2011-04-26 (1522 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) SourcePackage: aspell UpgradeStatus: Upgraded to vivid on 2015-04-26 (61 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aspell/+bug/1469355/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1143282] Re: Unable to add podcasts in rhythmbox
This still happens in 14.10. -- 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/1143282 Title: Unable to add podcasts in rhythmbox Status in rhythmbox package in Ubuntu: Confirmed Bug description: I am unable to add a podcast in rhythmbox. Procedure: 1) Open rhythmbox 2) select Podcasts under Library on the left 3) Press the Add button 4) Enter a URL from a podcast feed that you know should work because you can see it in firefox, e.g. http://feeds.feedburner.com/Rsaudio (typing or copy/pasting appears to make no difference.) 5) Note that the subscribe button isn't lit up, so click search 6) You get a message saying Unable to load the feed. Check your network connection. and the podcast URL is 7) Subscribe is now enabled, so press that. Result: 8) the feed URL disappears from the list, but you aren't subscribed to it Expected result: 8) you are subscribed to it. Notes: * My network connection is active * It is managed by network manager, although my desktop is xmonad and I don't have the applet visible (but apparently it is running) ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: rhythmbox 2.97-1ubuntu6.1 ProcVersionSignature: Ubuntu 3.5.0-23.35-generic 3.5.7.2 Uname: Linux 3.5.0-23-generic x86_64 ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 Date: Mon Mar 4 14:45:43 2013 MarkForUpload: True SourcePackage: rhythmbox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1143282/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1342429] [NEW] ubuntu-bug crashes when there's no sources.list
Public bug reported: $ ubuntu-bug apport *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. Traceback (most recent call last): File /usr/bin/apport-cli, line 365, in module if not app.run_argv(): File /usr/lib/python2.7/dist-packages/apport/ui.py, line 554, in run_argv return self.run_report_bug() File /usr/lib/python2.7/dist-packages/apport/ui.py, line 359, in run_report_bug self.collect_info(symptom_script) File /usr/lib/python2.7/dist-packages/apport/ui.py, line 874, in collect_info icthread.exc_raise() File /usr/lib/python2.7/dist-packages/apport/REThread.py, line 34, in run self._retval = self.__target(*self.__args, **self.__kwargs) File /usr/lib/python2.7/dist-packages/apport/ui.py, line 74, in thread_collect_info report.add_package_info(package) File /usr/lib/python2.7/dist-packages/apport/report.py, line 219, in add_package_info version = packaging.get_version(package) File /usr/lib/python2.7/dist-packages/apport/packaging_impl.py, line 92, in get_version pkg = self._apt_pkg(package) File /usr/lib/python2.7/dist-packages/apport/packaging_impl.py, line 85, in _apt_pkg return self._cache()[package] File /usr/lib/python2.7/dist-packages/apport/packaging_impl.py, line 53, in _cache self._apt_cache = apt.Cache(progress, rootdir='/') File /usr/lib/python2.7/dist-packages/apt/cache.py, line 101, in __init__ self._check_and_create_required_dirs(rootdir) File /usr/lib/python2.7/dist-packages/apt/cache.py, line 131, in _check_and_create_required_dirs open(rootdir + f, w).close() IOError: [Errno 13] Permission denied: '//etc/apt/sources.list' If I run it with sudo, then it makes a zero-byte sources.list file. The reason we don't have a sources.list is that puppet manages the files in /etc/apt/sources.list.d according to the needs of the server. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: apport 2.0.1-0ubuntu17.6 ProcVersionSignature: Ubuntu 3.8.0-42.63~precise1-generic 3.8.13.23 Uname: Linux 3.8.0-42-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 CrashReports: 640:3276:106:13876:2014-07-16 11:35:09.958702133 +1200:2014-07-16 11:35:09.958702133 +1200:/var/crash/_usr_bin_apport-bug.3276.crash Date: Wed Jul 16 11:46:54 2014 MarkForUpload: True PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apport (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 apport in Ubuntu. https://bugs.launchpad.net/bugs/1342429 Title: ubuntu-bug crashes when there's no sources.list Status in “apport” package in Ubuntu: New Bug description: $ ubuntu-bug apport *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. Traceback (most recent call last): File /usr/bin/apport-cli, line 365, in module if not app.run_argv(): File /usr/lib/python2.7/dist-packages/apport/ui.py, line 554, in run_argv return self.run_report_bug() File /usr/lib/python2.7/dist-packages/apport/ui.py, line 359, in run_report_bug self.collect_info(symptom_script) File /usr/lib/python2.7/dist-packages/apport/ui.py, line 874, in collect_info icthread.exc_raise() File /usr/lib/python2.7/dist-packages/apport/REThread.py, line 34, in run self._retval = self.__target(*self.__args, **self.__kwargs) File /usr/lib/python2.7/dist-packages/apport/ui.py, line 74, in thread_collect_info report.add_package_info(package) File /usr/lib/python2.7/dist-packages/apport/report.py, line 219, in add_package_info version = packaging.get_version(package) File /usr/lib/python2.7/dist-packages/apport/packaging_impl.py, line 92, in get_version pkg = self._apt_pkg(package) File /usr/lib/python2.7/dist-packages/apport/packaging_impl.py, line 85, in _apt_pkg return self._cache()[package] File /usr/lib/python2.7/dist-packages/apport/packaging_impl.py, line 53, in _cache self._apt_cache = apt.Cache(progress, rootdir='/') File /usr/lib/python2.7/dist-packages/apt/cache.py, line 101, in __init__ self._check_and_create_required_dirs(rootdir) File /usr/lib/python2.7/dist-packages/apt/cache.py, line 131, in _check_and_create_required_dirs open(rootdir + f, w).close() IOError: [Errno 13] Permission denied: '//etc/apt/sources.list' If I run it with sudo, then it makes a zero-byte sources.list file. The reason we don't have a sources.list is that puppet manages the files in /etc/apt/sources.list.d according to the needs of the server. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: apport 2.0.1-0ubuntu17.6
[Desktop-packages] [Bug 1292759] Re: Nautilus default window size is slightly too small
I tried a guest session and it worked. Also, remember resizing is working for me now too. I guess it was some artefact of the upgrade that was doing weird things and then got better, so I'll mark this as invalid. ** Changed in: nautilus (Ubuntu) Status: New = Invalid -- 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/1292759 Title: Nautilus default window size is slightly too small Status in “nautilus” package in Ubuntu: Invalid Bug description: When you open a nautilus window, it is slightly too narrow to show four columns, so instead it shows three with a chunk of space wasted. See the attached screenshot. It probably should remember the size it was last made, or at least be a little bit wider. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nautilus 1:3.10.1-0ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sat Mar 15 14:26:16 2014 GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' b['name', 'size', 'type', 'date_modified', 'owner', 'group', 'where', 'mime_type', 'permissions'] InstallationDate: Installed on 2011-04-26 (1053 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) SourcePackage: nautilus UpgradeStatus: Upgraded to trusty on 2014-03-09 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1292759/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1292759] Re: Nautilus default window size is slightly too small
I don't know what I've changed from default. This installation is a few years old now, I've probably poked and prodded at all kinds of things. This morning however it seems to be doing 4 columns. I don't know if it remembered a resizing I did in a previous session, or something's updated and changed, or what it is. -- 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/1292759 Title: Nautilus default window size is slightly too small Status in “nautilus” package in Ubuntu: New Bug description: When you open a nautilus window, it is slightly too narrow to show four columns, so instead it shows three with a chunk of space wasted. See the attached screenshot. It probably should remember the size it was last made, or at least be a little bit wider. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nautilus 1:3.10.1-0ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sat Mar 15 14:26:16 2014 GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' b['name', 'size', 'type', 'date_modified', 'owner', 'group', 'where', 'mime_type', 'permissions'] InstallationDate: Installed on 2011-04-26 (1053 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) SourcePackage: nautilus UpgradeStatus: Upgraded to trusty on 2014-03-09 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1292759/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1292759] [NEW] Nautilus default window size is slightly too small
Public bug reported: When you open a nautilus window, it is slightly too narrow to show four columns, so instead it shows three with a chunk of space wasted. See the attached screenshot. It probably should remember the size it was last made, or at least be a little bit wider. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nautilus 1:3.10.1-0ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sat Mar 15 14:26:16 2014 GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' b['name', 'size', 'type', 'date_modified', 'owner', 'group', 'where', 'mime_type', 'permissions'] InstallationDate: Installed on 2011-04-26 (1053 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) SourcePackage: nautilus UpgradeStatus: Upgraded to trusty on 2014-03-09 (5 days ago) ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty ** Attachment added: Screenshot showing the slightly too small nautilus window https://bugs.launchpad.net/bugs/1292759/+attachment/4024797/+files/Schermafdruk%20van%202014-03-15%2014%3A26%3A00.png -- 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/1292759 Title: Nautilus default window size is slightly too small Status in “nautilus” package in Ubuntu: New Bug description: When you open a nautilus window, it is slightly too narrow to show four columns, so instead it shows three with a chunk of space wasted. See the attached screenshot. It probably should remember the size it was last made, or at least be a little bit wider. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nautilus 1:3.10.1-0ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sat Mar 15 14:26:16 2014 GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' b['name', 'size', 'type', 'date_modified', 'owner', 'group', 'where', 'mime_type', 'permissions'] InstallationDate: Installed on 2011-04-26 (1053 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) SourcePackage: nautilus UpgradeStatus: Upgraded to trusty on 2014-03-09 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1292759/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1235625] Re: fix legacy keygrabber for gnome-ish sessions
Can confirm that this takes play/pause and volume from not working to working under xmonad. -- 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/1235625 Title: fix legacy keygrabber for gnome-ish sessions Status in “gnome-settings-daemon” package in Ubuntu: Fix Released Status in “gnome-settings-daemon” source package in Saucy: Fix Committed Bug description: [ Description ] In Saucy, media keys in gnome-ish (using gnome-settings-daemon) sessions only work when gnome-panel or Unity are in use, as the code path checks for their names on the bus. They ought to work for all sessions. [ Fix ] Change the logic so that the keygrabber is started all the time except under Shell sessions. [ QA ] In a session that runs gnome-settings-daemon but neither panel nor shell (xfce or Openbox? or a custom xmonad), check that media keys now work. [ Regression potential ] Changes activation criteria for the legacy keygrabber. Check it still works in Unity, panel and that the new method works under shell. [ Original report ] The previous patch to fix the legacy keygrabber was Unity specific and breaks on gnome-ish sessions that require it, instead we should load the legacy keygrabber for any session that is not gnome-shell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1235625/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1143282] Re: Unable to add podcasts in rhythmbox
It is still occuring for me, and rhythmbox has been restarted. -- 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/1143282 Title: Unable to add podcasts in rhythmbox Status in “rhythmbox” package in Ubuntu: Confirmed Bug description: I am unable to add a podcast in rhythmbox. Procedure: 1) Open rhythmbox 2) select Podcasts under Library on the left 3) Press the Add button 4) Enter a URL from a podcast feed that you know should work because you can see it in firefox, e.g. http://feeds.feedburner.com/Rsaudio (typing or copy/pasting appears to make no difference.) 5) Note that the subscribe button isn't lit up, so click search 6) You get a message saying Unable to load the feed. Check your network connection. and the podcast URL is 7) Subscribe is now enabled, so press that. Result: 8) the feed URL disappears from the list, but you aren't subscribed to it Expected result: 8) you are subscribed to it. Notes: * My network connection is active * It is managed by network manager, although my desktop is xmonad and I don't have the applet visible (but apparently it is running) ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: rhythmbox 2.97-1ubuntu6.1 ProcVersionSignature: Ubuntu 3.5.0-23.35-generic 3.5.7.2 Uname: Linux 3.5.0-23-generic x86_64 ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 Date: Mon Mar 4 14:45:43 2013 MarkForUpload: True SourcePackage: rhythmbox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1143282/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1143282] [NEW] Unable to add podcasts in rhythmbox
Public bug reported: I am unable to add a podcast in rhythmbox. Procedure: 1) Open rhythmbox 2) select Podcasts under Library on the left 3) Press the Add button 4) Enter a URL from a podcast feed that you know should work because you can see it in firefox, e.g. http://feeds.feedburner.com/Rsaudio (typing or copy/pasting appears to make no difference.) 5) Note that the subscribe button isn't lit up, so click search 6) You get a message saying Unable to load the feed. Check your network connection. and the podcast URL is 7) Subscribe is now enabled, so press that. Result: 8) the feed URL disappears from the list, but you aren't subscribed to it Expected result: 8) you are subscribed to it. Notes: * My network connection is active * It is managed by network manager, although my desktop is xmonad and I don't have the applet visible (but apparently it is running) ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: rhythmbox 2.97-1ubuntu6.1 ProcVersionSignature: Ubuntu 3.5.0-23.35-generic 3.5.7.2 Uname: Linux 3.5.0-23-generic x86_64 ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 Date: Mon Mar 4 14:45:43 2013 MarkForUpload: True SourcePackage: rhythmbox UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug quantal -- 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/1143282 Title: Unable to add podcasts in rhythmbox Status in “rhythmbox” package in Ubuntu: New Bug description: I am unable to add a podcast in rhythmbox. Procedure: 1) Open rhythmbox 2) select Podcasts under Library on the left 3) Press the Add button 4) Enter a URL from a podcast feed that you know should work because you can see it in firefox, e.g. http://feeds.feedburner.com/Rsaudio (typing or copy/pasting appears to make no difference.) 5) Note that the subscribe button isn't lit up, so click search 6) You get a message saying Unable to load the feed. Check your network connection. and the podcast URL is 7) Subscribe is now enabled, so press that. Result: 8) the feed URL disappears from the list, but you aren't subscribed to it Expected result: 8) you are subscribed to it. Notes: * My network connection is active * It is managed by network manager, although my desktop is xmonad and I don't have the applet visible (but apparently it is running) ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: rhythmbox 2.97-1ubuntu6.1 ProcVersionSignature: Ubuntu 3.5.0-23.35-generic 3.5.7.2 Uname: Linux 3.5.0-23-generic x86_64 ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 Date: Mon Mar 4 14:45:43 2013 MarkForUpload: True SourcePackage: rhythmbox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1143282/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1143389] [NEW] Rhythmbox crashes if you hit subscribe too many times
Public bug reported: Follow the procedure from bug #1143282: Procedure: 1) Open rhythmbox 2) select Podcasts under Library on the left 3) Press the Add button 4) Enter a URL from a podcast feed that you know should work because you can see it in firefox, e.g. http://feeds.feedburner.com/Rsaudio (typing or copy/pasting appears to make no difference.) 5) Note that the subscribe button isn't lit up, so click search 6) You get a message saying Unable to load the feed. Check your network connection. and the podcast URL is 7) Subscribe is now enabled, so press that. Now: 8) Press subscribe again. Result: 9) rhythmbox crashes: (rhythmbox:7022): Gtk-CRITICAL **: gtk_list_store_get_value: assertion `iter_is_valid (iter, list_store)' failed (rhythmbox:7022): GLib-GObject-WARNING **: /build/buildd/glib2.0-2.34.1/./gobject/gtype.c:4204: type id `0' is invalid (rhythmbox:7022): GLib-GObject-WARNING **: can't peek value table for type `invalid' which is not currently referenced Segmentatiefout (geheugendump gemaakt) Expected result: 9) it doesn't crash. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: rhythmbox 2.97-1ubuntu6.1 ProcVersionSignature: Ubuntu 3.5.0-23.35-generic 3.5.7.2 Uname: Linux 3.5.0-23-generic x86_64 ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 Date: Mon Mar 4 15:39:37 2013 MarkForUpload: True SourcePackage: rhythmbox UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug quantal -- 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/1143389 Title: Rhythmbox crashes if you hit subscribe too many times Status in “rhythmbox” package in Ubuntu: New Bug description: Follow the procedure from bug #1143282: Procedure: 1) Open rhythmbox 2) select Podcasts under Library on the left 3) Press the Add button 4) Enter a URL from a podcast feed that you know should work because you can see it in firefox, e.g. http://feeds.feedburner.com/Rsaudio (typing or copy/pasting appears to make no difference.) 5) Note that the subscribe button isn't lit up, so click search 6) You get a message saying Unable to load the feed. Check your network connection. and the podcast URL is 7) Subscribe is now enabled, so press that. Now: 8) Press subscribe again. Result: 9) rhythmbox crashes: (rhythmbox:7022): Gtk-CRITICAL **: gtk_list_store_get_value: assertion `iter_is_valid (iter, list_store)' failed (rhythmbox:7022): GLib-GObject-WARNING **: /build/buildd/glib2.0-2.34.1/./gobject/gtype.c:4204: type id `0' is invalid (rhythmbox:7022): GLib-GObject-WARNING **: can't peek value table for type `invalid' which is not currently referenced Segmentatiefout (geheugendump gemaakt) Expected result: 9) it doesn't crash. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: rhythmbox 2.97-1ubuntu6.1 ProcVersionSignature: Ubuntu 3.5.0-23.35-generic 3.5.7.2 Uname: Linux 3.5.0-23-generic x86_64 ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 Date: Mon Mar 4 15:39:37 2013 MarkForUpload: True SourcePackage: rhythmbox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1143389/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 957794] Re: Mouse pointer reappears while playing a file
I don't think I've seen it happen for a while now. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/957794 Title: Mouse pointer reappears while playing a file Status in “totem” package in Ubuntu: Incomplete Bug description: When watching a movie file in totem, after a period of time the mouse pointer shows up on its own (i.e. with no movement) on the screen. When this happens, moving the mouse doesn't reactivate the time bar thing at the bottom, but double click will take it out of full screen (single clicking has no noticable effect.) After going back to windowed and then to fullscreen, the mouse behaves normally (activates the time bar, disappears after a few seconds) until the pointer comes back again. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: totem 3.0.1-0ubuntu20 ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9 Uname: Linux 3.2.0-18-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.94.1-0ubuntu2 Architecture: amd64 Date: Sat Mar 17 23:02:12 2012 InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) SourcePackage: totem UpgradeStatus: Upgraded to precise on 2012-03-16 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/957794/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 972785] Re: Unable to add new startup applications
The details above didn't fix my problem, but I ended up deleting the existing nm-applet config from there and it got readded automatically (so far as I could tell) and that seemed to solve my issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/972785 Title: Unable to add new startup applications Status in “gnome-session” package in Ubuntu: Confirmed Bug description: When attempting to add a program to start on boot, it isn't saved when it should be. To reproduce: 1. Go to the gear/power menu thing at the top-right 2. Select Startup Applications (or whatever it actually says in en) 3. Add a new program 3.1. Fill out the three boxes with something you want 4. Note that your program has been added to the list of startup programs 5. Close that window 6. Open it again 7. Note that your program is no longer there 8. Reboot 9. Note that your program doesn't start up. Expected results: 7. Your program is there. 9. Your program starts up. Notes: * Whether or not you perform steps 6-7, the result of 9 is not affected. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-session-bin 3.2.1-0ubuntu6 ProcVersionSignature: Ubuntu 3.2.0-21.34-generic 3.2.13 Uname: Linux 3.2.0-21-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0-0ubuntu2 Architecture: amd64 Date: Wed Apr 4 07:44:44 2012 InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) SourcePackage: gnome-session UpgradeStatus: Upgraded to precise on 2012-03-16 (18 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/972785/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 927384] Re: indicator-weather crashed with SIGSEGV in g_array_free()
This was happening long before google disabled their API. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to indicator-weather in Ubuntu. https://bugs.launchpad.net/bugs/927384 Title: indicator-weather crashed with SIGSEGV in g_array_free() Status in “indicator-weather” package in Ubuntu: Confirmed Status in “indicator-weather” source package in Precise: Confirmed Status in “indicator-weather” source package in Quantal: Confirmed Bug description: Crashes at random times, doesn't seem to matter what program(s) is/are running at the time. No difficulty restarting from dash. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: indicator-weather 11.11.28-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-14.23-generic 3.2.3 Uname: Linux 3.2.0-14-generic x86_64 ApportVersion: 1.91-0ubuntu1 Architecture: amd64 CrashCounter: 1 Date: Sun Feb 5 18:38:23 2012 ExecutablePath: /usr/bin/indicator-weather InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) InterpreterPath: /usr/bin/python2.7 PackageArchitecture: all ProcCmdline: /usr/bin/python /usr/bin/indicator-weather SegvAnalysis: Segfault happened at: 0x7f7902f2ce98 g_array_free+24: lock xadd %edx,0x18(%rdi) PC (0x7f7902f2ce98) ok source %edx ok destination 0x18(%rdi) (0x7f78f8bdcc58) in non-writable VMA region: 0x7f78f8bd1000-0x7f78f8be9000 r-xp /usr/lib/x86_64-linux-gnu/libdbusmenu-glib.so.4.0.7 SegvReason: writing VMA /usr/lib/x86_64-linux-gnu/libdbusmenu-glib.so.4.0.7 Signal: 11 SourcePackage: indicator-weather StacktraceTop: g_array_free () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libdbusmenu-glib.so.4 ?? () from /usr/lib/x86_64-linux-gnu/libdbusmenu-glib.so.4 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: indicator-weather crashed with SIGSEGV in g_array_free() UpgradeStatus: Upgraded to precise on 2012-02-05 (0 days ago) UserGroups: adm admin cdrom dialout fuse lpadmin mail plugdev sambashare scanner users video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-weather/+bug/927384/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 681002] Re: gpg: problem with the agent: Bad CA certificate
DUPLICITY: INFO 4 'home/robin/.gnupg/pubring.gpg' DUPLICITY: . A home/robin/.gnupg/pubring.gpg DUPLICITY: DEBUG 1 DUPLICITY: . Removing still remembered temporary file /tmp/duplicity-_XHa0A-tempdir/mkstemp-DS0LuL-1 DUPLICITY: DEBUG 1 DUPLICITY: . Removing still remembered temporary file /tmp/duplicity-_XHa0A-tempdir/mktemp-w2gx_c-2 DUPLICITY: INFO 1 DUPLICITY: . GPG error detail: Traceback (most recent call last): DUPLICITY: . File /usr/bin/duplicity, line 1403, in module DUPLICITY: . with_tempdir(main) DUPLICITY: . File /usr/bin/duplicity, line 1396, in with_tempdir DUPLICITY: . fn() DUPLICITY: . File /usr/bin/duplicity, line 1366, in main DUPLICITY: . full_backup(col_stats) DUPLICITY: . File /usr/bin/duplicity, line 500, in full_backup DUPLICITY: . globals.backend) DUPLICITY: . File /usr/bin/duplicity, line 378, in write_multivol DUPLICITY: . globals.gpg_profile, globals.volsize) DUPLICITY: . File /usr/lib/python2.7/dist-packages/duplicity/gpg.py, line 332, in GPGWriteFile DUPLICITY: . file.close() DUPLICITY: . File /usr/lib/python2.7/dist-packages/duplicity/gpg.py, line 221, in close DUPLICITY: . self.gpg_failed() DUPLICITY: . File /usr/lib/python2.7/dist-packages/duplicity/gpg.py, line 206, in gpg_failed DUPLICITY: . raise GPGError, msg DUPLICITY: . GPGError: GPG Failed, see log below: DUPLICITY: . = Begin GnuPG log = DUPLICITY: . gpg: can't handle text lines longer than 19995 characters DUPLICITY: . = End GnuPG log = DUPLICITY: . DUPLICITY: . DUPLICITY: ERROR 31 GPGError DUPLICITY: . GPGError: GPG Failed, see log below: DUPLICITY: . = Begin GnuPG log = DUPLICITY: . gpg: can't handle text lines longer than 19995 characters DUPLICITY: . = End GnuPG log = -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/681002 Title: gpg: problem with the agent: Bad CA certificate Status in Déjà Dup Backup Tool: Invalid Status in GNOME keyring services: Fix Released Status in “gnome-keyring” package in Ubuntu: Fix Released Bug description: If I don't encrypt the backup all works well, otherwise... [...] DUPLICITY: INFO 1 DUPLICITY: . GPG error detail: Traceback (most recent call last): DUPLICITY: . File /usr/bin/duplicity-2.6, line 1245, in module DUPLICITY: . with_tempdir(main) DUPLICITY: . File /usr/bin/duplicity-2.6, line 1238, in with_tempdir DUPLICITY: . fn() DUPLICITY: . File /usr/bin/duplicity-2.6, line 1220, in main DUPLICITY: . incremental_backup(sig_chain) DUPLICITY: . File /usr/bin/duplicity-2.6, line 488, in incremental_backup DUPLICITY: . globals.backend) DUPLICITY: . File /usr/bin/duplicity-2.6, line 295, in write_multivol DUPLICITY: . globals.gpg_profile, globals.volsize) DUPLICITY: . File /usr/lib64/python2.6/site-packages/duplicity/gpg.py, line 291, in GPGWriteFile DUPLICITY: . file.close() DUPLICITY: . File /usr/lib64/python2.6/site-packages/duplicity/gpg.py, line 180, in close DUPLICITY: . self.gpg_failed() DUPLICITY: . File /usr/lib64/python2.6/site-packages/duplicity/gpg.py, line 165, in gpg_failed DUPLICITY: . raise GPGError, msg DUPLICITY: . GPGError: GPG Failed, see log below: DUPLICITY: . = Begin GnuPG log = DUPLICITY: . gpg: problem with the agent: Bad CA certificate DUPLICITY: . = End GnuPG log = DUPLICITY: . DUPLICITY: . DUPLICITY: ERROR 31 GPGError DUPLICITY: . GPGError: GPG Failed, see log below: DUPLICITY: . = Begin GnuPG log = DUPLICITY: . gpg: problem with the agent: Bad CA certificate DUPLICITY: . = End GnuPG log = DUPLICITY: . [...] I'm using duplicity-0.6.11 To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/681002/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1019293] [NEW] deja-jup gets into ask password loop when backing up some data
Public bug reported:
When I run deja-dup, and it encounters some data* it asks for the
password to be reentered, and when you do that, it tries again, and gets
in the same loop, over and over until you cancel. Nothing ends up being
backed up.
* e.g. my gpg public keyring, but when I exclude .gnupg, it has what may
be the same problem on something else too, so I think that's
coincidence.
The last part of the log is at the bottom of this, and I'll attach the
final 1000 lines. I don't think this is a duplicate of bug #883742, as
the source of the error is quite different.
DUPLICITY: DEBUG 1
DUPLICITY: . Selecting /home/robin/.gnupg/gpg.conf
DUPLICITY: DEBUG 1
DUPLICITY: . Comparing ('home', 'robin', '.gnupg', 'gpg.conf') and None
DUPLICITY: DEBUG 1
DUPLICITY: . Getting delta of (('home', 'robin', '.gnupg', 'gpg.conf')
/home/robin/.gnupg/gpg.conf reg) and None
DUPLICITY: INFO 4 'home/robin/.gnupg/gpg.conf'
DUPLICITY: . A home/robin/.gnupg/gpg.conf
DUPLICITY: DEBUG 1
DUPLICITY: . Selecting /home/robin/.gnupg/gpg.conf~
DUPLICITY: DEBUG 1
DUPLICITY: . Comparing ('home', 'robin', '.gnupg', 'gpg.conf~') and None
DUPLICITY: DEBUG 1
DUPLICITY: . Getting delta of (('home', 'robin', '.gnupg', 'gpg.conf~')
/home/robin/.gnupg/gpg.conf~ reg) and None
DUPLICITY: INFO 4 'home/robin/.gnupg/gpg.conf~'
DUPLICITY: . A home/robin/.gnupg/gpg.conf~
DUPLICITY: DEBUG 1
DUPLICITY: . Selecting /home/robin/.gnupg/pubring.gpg
DUPLICITY: DEBUG 1
DUPLICITY: . Comparing ('home', 'robin', '.gnupg', 'pubring.gpg') and None
DUPLICITY: DEBUG 1
DUPLICITY: . Getting delta of (('home', 'robin', '.gnupg', 'pubring.gpg')
/home/robin/.gnupg/pubring.gpg reg) and None
DUPLICITY: INFO 4 'home/robin/.gnupg/pubring.gpg'
DUPLICITY: . A home/robin/.gnupg/pubring.gpg
DUPLICITY: DEBUG 1
DUPLICITY: . Removing still remembered temporary file
/tmp/duplicity-_XHa0A-tempdir/mkstemp-DS0LuL-1
DUPLICITY: DEBUG 1
DUPLICITY: . Removing still remembered temporary file
/tmp/duplicity-_XHa0A-tempdir/mktemp-w2gx_c-2
DUPLICITY: INFO 1
DUPLICITY: . GPG error detail: Traceback (most recent call last):
DUPLICITY: . File /usr/bin/duplicity, line 1403, in module
DUPLICITY: . with_tempdir(main)
DUPLICITY: . File /usr/bin/duplicity, line 1396, in with_tempdir
DUPLICITY: . fn()
DUPLICITY: . File /usr/bin/duplicity, line 1366, in main
DUPLICITY: . full_backup(col_stats)
DUPLICITY: . File /usr/bin/duplicity, line 500, in full_backup
DUPLICITY: . globals.backend)
DUPLICITY: . File /usr/bin/duplicity, line 378, in write_multivol
DUPLICITY: . globals.gpg_profile, globals.volsize)
DUPLICITY: . File /usr/lib/python2.7/dist-packages/duplicity/gpg.py, line
332, in GPGWriteFile
DUPLICITY: . file.close()
DUPLICITY: . File /usr/lib/python2.7/dist-packages/duplicity/gpg.py, line
221, in close
DUPLICITY: . self.gpg_failed()
DUPLICITY: . File /usr/lib/python2.7/dist-packages/duplicity/gpg.py, line
206, in gpg_failed
DUPLICITY: . raise GPGError, msg
DUPLICITY: . GPGError: GPG Failed, see log below:
DUPLICITY: . = Begin GnuPG log =
DUPLICITY: . gpg: can't handle text lines longer than 19995 characters
DUPLICITY: . = End GnuPG log =
DUPLICITY: .
DUPLICITY: .
DUPLICITY: ERROR 31 GPGError
DUPLICITY: . GPGError: GPG Failed, see log below:
DUPLICITY: . = Begin GnuPG log =
DUPLICITY: . gpg: can't handle text lines longer than 19995 characters
DUPLICITY: . = End GnuPG log =
DUPLICITY: .
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: deja-dup 22.0-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-25.40-generic 3.2.18
Uname: Linux 3.2.0-25-generic x86_64
ApportVersion: 2.0.1-0ubuntu8
Architecture: amd64
Date: Fri Jun 29 14:04:01 2012
InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
SourcePackage: deja-dup
UpgradeStatus: Upgraded to precise on 2012-05-08 (52 days ago)
** Affects: deja-dup (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 deja-dup in Ubuntu.
https://bugs.launchpad.net/bugs/1019293
Title:
deja-jup gets into ask password loop when backing up some data
Status in “deja-dup” package in Ubuntu:
New
Bug description:
When I run deja-dup, and it encounters some data* it asks for the
password to be reentered, and when you do that, it tries again, and
gets in the same loop, over and over until you cancel. Nothing ends up
being backed up.
* e.g. my gpg public keyring, but when I exclude .gnupg, it has what
may be the same problem on something else too, so I think that's
coincidence.
The last part of the log is at the bottom of this, and I'll attach the
final 1000 lines. I don't think this is a duplicate of bug #883742, as
the source of the error is quite different.
DUPLICITY: DEBUG 1
DUPLICITY: . Selecting /home/robin/.gnupg/gpg.conf
DUPLICITY: DEBUG 1
DUPLICITY: . Comparing
[Desktop-packages] [Bug 1019293] Re: deja-jup gets into ask password loop when backing up some data
** Attachment added: last 1000 lines of deja-dup log file.
https://bugs.launchpad.net/bugs/1019293/+attachment/3207803/+files/deja-dup.log
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to deja-dup in Ubuntu.
https://bugs.launchpad.net/bugs/1019293
Title:
deja-jup gets into ask password loop when backing up some data
Status in “deja-dup” package in Ubuntu:
New
Bug description:
When I run deja-dup, and it encounters some data* it asks for the
password to be reentered, and when you do that, it tries again, and
gets in the same loop, over and over until you cancel. Nothing ends up
being backed up.
* e.g. my gpg public keyring, but when I exclude .gnupg, it has what
may be the same problem on something else too, so I think that's
coincidence.
The last part of the log is at the bottom of this, and I'll attach the
final 1000 lines. I don't think this is a duplicate of bug #883742, as
the source of the error is quite different.
DUPLICITY: DEBUG 1
DUPLICITY: . Selecting /home/robin/.gnupg/gpg.conf
DUPLICITY: DEBUG 1
DUPLICITY: . Comparing ('home', 'robin', '.gnupg', 'gpg.conf') and None
DUPLICITY: DEBUG 1
DUPLICITY: . Getting delta of (('home', 'robin', '.gnupg', 'gpg.conf')
/home/robin/.gnupg/gpg.conf reg) and None
DUPLICITY: INFO 4 'home/robin/.gnupg/gpg.conf'
DUPLICITY: . A home/robin/.gnupg/gpg.conf
DUPLICITY: DEBUG 1
DUPLICITY: . Selecting /home/robin/.gnupg/gpg.conf~
DUPLICITY: DEBUG 1
DUPLICITY: . Comparing ('home', 'robin', '.gnupg', 'gpg.conf~') and None
DUPLICITY: DEBUG 1
DUPLICITY: . Getting delta of (('home', 'robin', '.gnupg', 'gpg.conf~')
/home/robin/.gnupg/gpg.conf~ reg) and None
DUPLICITY: INFO 4 'home/robin/.gnupg/gpg.conf~'
DUPLICITY: . A home/robin/.gnupg/gpg.conf~
DUPLICITY: DEBUG 1
DUPLICITY: . Selecting /home/robin/.gnupg/pubring.gpg
DUPLICITY: DEBUG 1
DUPLICITY: . Comparing ('home', 'robin', '.gnupg', 'pubring.gpg') and None
DUPLICITY: DEBUG 1
DUPLICITY: . Getting delta of (('home', 'robin', '.gnupg', 'pubring.gpg')
/home/robin/.gnupg/pubring.gpg reg) and None
DUPLICITY: INFO 4 'home/robin/.gnupg/pubring.gpg'
DUPLICITY: . A home/robin/.gnupg/pubring.gpg
DUPLICITY: DEBUG 1
DUPLICITY: . Removing still remembered temporary file
/tmp/duplicity-_XHa0A-tempdir/mkstemp-DS0LuL-1
DUPLICITY: DEBUG 1
DUPLICITY: . Removing still remembered temporary file
/tmp/duplicity-_XHa0A-tempdir/mktemp-w2gx_c-2
DUPLICITY: INFO 1
DUPLICITY: . GPG error detail: Traceback (most recent call last):
DUPLICITY: . File /usr/bin/duplicity, line 1403, in module
DUPLICITY: . with_tempdir(main)
DUPLICITY: . File /usr/bin/duplicity, line 1396, in with_tempdir
DUPLICITY: . fn()
DUPLICITY: . File /usr/bin/duplicity, line 1366, in main
DUPLICITY: . full_backup(col_stats)
DUPLICITY: . File /usr/bin/duplicity, line 500, in full_backup
DUPLICITY: . globals.backend)
DUPLICITY: . File /usr/bin/duplicity, line 378, in write_multivol
DUPLICITY: . globals.gpg_profile, globals.volsize)
DUPLICITY: . File /usr/lib/python2.7/dist-packages/duplicity/gpg.py, line
332, in GPGWriteFile
DUPLICITY: . file.close()
DUPLICITY: . File /usr/lib/python2.7/dist-packages/duplicity/gpg.py, line
221, in close
DUPLICITY: . self.gpg_failed()
DUPLICITY: . File /usr/lib/python2.7/dist-packages/duplicity/gpg.py, line
206, in gpg_failed
DUPLICITY: . raise GPGError, msg
DUPLICITY: . GPGError: GPG Failed, see log below:
DUPLICITY: . = Begin GnuPG log =
DUPLICITY: . gpg: can't handle text lines longer than 19995 characters
DUPLICITY: . = End GnuPG log =
DUPLICITY: .
DUPLICITY: .
DUPLICITY: ERROR 31 GPGError
DUPLICITY: . GPGError: GPG Failed, see log below:
DUPLICITY: . = Begin GnuPG log =
DUPLICITY: . gpg: can't handle text lines longer than 19995 characters
DUPLICITY: . = End GnuPG log =
DUPLICITY: .
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: deja-dup 22.0-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-25.40-generic 3.2.18
Uname: Linux 3.2.0-25-generic x86_64
ApportVersion: 2.0.1-0ubuntu8
Architecture: amd64
Date: Fri Jun 29 14:04:01 2012
InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
SourcePackage: deja-dup
UpgradeStatus: Upgraded to precise on 2012-05-08 (52 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1019293/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 681002] Re: gpg: problem with the agent: Bad CA certificate
This is still an issue in Ubuntu 12.04 for me. It gets to my .gnupg directory and then asks for the password again (I don't know if that's a coincidence or not.) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/681002 Title: gpg: problem with the agent: Bad CA certificate Status in Déjà Dup Backup Tool: Invalid Status in GNOME keyring services: Fix Released Status in “gnome-keyring” package in Ubuntu: Fix Released Bug description: If I don't encrypt the backup all works well, otherwise... [...] DUPLICITY: INFO 1 DUPLICITY: . GPG error detail: Traceback (most recent call last): DUPLICITY: . File /usr/bin/duplicity-2.6, line 1245, in module DUPLICITY: . with_tempdir(main) DUPLICITY: . File /usr/bin/duplicity-2.6, line 1238, in with_tempdir DUPLICITY: . fn() DUPLICITY: . File /usr/bin/duplicity-2.6, line 1220, in main DUPLICITY: . incremental_backup(sig_chain) DUPLICITY: . File /usr/bin/duplicity-2.6, line 488, in incremental_backup DUPLICITY: . globals.backend) DUPLICITY: . File /usr/bin/duplicity-2.6, line 295, in write_multivol DUPLICITY: . globals.gpg_profile, globals.volsize) DUPLICITY: . File /usr/lib64/python2.6/site-packages/duplicity/gpg.py, line 291, in GPGWriteFile DUPLICITY: . file.close() DUPLICITY: . File /usr/lib64/python2.6/site-packages/duplicity/gpg.py, line 180, in close DUPLICITY: . self.gpg_failed() DUPLICITY: . File /usr/lib64/python2.6/site-packages/duplicity/gpg.py, line 165, in gpg_failed DUPLICITY: . raise GPGError, msg DUPLICITY: . GPGError: GPG Failed, see log below: DUPLICITY: . = Begin GnuPG log = DUPLICITY: . gpg: problem with the agent: Bad CA certificate DUPLICITY: . = End GnuPG log = DUPLICITY: . DUPLICITY: . DUPLICITY: ERROR 31 GPGError DUPLICITY: . GPGError: GPG Failed, see log below: DUPLICITY: . = Begin GnuPG log = DUPLICITY: . gpg: problem with the agent: Bad CA certificate DUPLICITY: . = End GnuPG log = DUPLICITY: . [...] I'm using duplicity-0.6.11 To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/681002/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1015653] [NEW] No way to cycle through your own photos
Public bug reported: If you open up the background settings panel, and add files of your own to display, there seems to be no way to tell it to cycle through your photos so you get to see them all. There is the built in photo collection that does that, and that's nice, but it's not obvious how you add your own. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-control-center 1:3.4.2-0ubuntu0.2 ProcVersionSignature: Ubuntu 3.2.0-25.40-generic 3.2.18 Uname: Linux 3.2.0-25-generic x86_64 ApportVersion: 2.0.1-0ubuntu8 Architecture: amd64 Date: Wed Jun 20 16:56:36 2012 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to precise on 2012-05-08 (43 days ago) usr_lib_gnome-control-center: activity-log-manager-control-center 0.9.4-0ubuntu3 deja-dup22.0-0ubuntu2 gnome-bluetooth 3.2.2-0ubuntu5 indicator-datetime 0.3.94-0ubuntu2 ** Affects: gnome-control-center (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 gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1015653 Title: No way to cycle through your own photos Status in “gnome-control-center” package in Ubuntu: New Bug description: If you open up the background settings panel, and add files of your own to display, there seems to be no way to tell it to cycle through your photos so you get to see them all. There is the built in photo collection that does that, and that's nice, but it's not obvious how you add your own. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-control-center 1:3.4.2-0ubuntu0.2 ProcVersionSignature: Ubuntu 3.2.0-25.40-generic 3.2.18 Uname: Linux 3.2.0-25-generic x86_64 ApportVersion: 2.0.1-0ubuntu8 Architecture: amd64 Date: Wed Jun 20 16:56:36 2012 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to precise on 2012-05-08 (43 days ago) usr_lib_gnome-control-center: activity-log-manager-control-center 0.9.4-0ubuntu3 deja-dup22.0-0ubuntu2 gnome-bluetooth 3.2.2-0ubuntu5 indicator-datetime 0.3.94-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1015653/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1015653] Re: No way to cycle through your own photos
-- 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/1015653 Title: No way to cycle through your own photos Status in “gnome-control-center” package in Ubuntu: New Bug description: If you open up the background settings panel, and add files of your own to display, there seems to be no way to tell it to cycle through your photos so you get to see them all. There is the built in photo collection that does that, and that's nice, but it's not obvious how you add your own. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-control-center 1:3.4.2-0ubuntu0.2 ProcVersionSignature: Ubuntu 3.2.0-25.40-generic 3.2.18 Uname: Linux 3.2.0-25-generic x86_64 ApportVersion: 2.0.1-0ubuntu8 Architecture: amd64 Date: Wed Jun 20 16:56:36 2012 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to precise on 2012-05-08 (43 days ago) usr_lib_gnome-control-center: activity-log-manager-control-center 0.9.4-0ubuntu3 deja-dup22.0-0ubuntu2 gnome-bluetooth 3.2.2-0ubuntu5 indicator-datetime 0.3.94-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1015653/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 972311] Re: Accessing a MTP device like the Galaxy Nexus fails
Adding a bit of a me too, but it might be worth noting that this happens after a bit of a delay: nautilus freezes for a while, and then ~30 seconds later that error pops up. Also, I only managed to make it work in Oneiric once, was never able to make it work again. -- 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/972311 Title: Accessing a MTP device like the Galaxy Nexus fails Status in “nautilus” package in Ubuntu: Confirmed Bug description: When I connect my Galaxy Nexus to my system (up to date precise) and try to access the data on my phone, I get the following error... The folder contents could not be displayed. Sorry, could not display all the contents of Galaxy: DBus error org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. In Oneiric accessing Android 4.0 devices via Nautilus worked. Not very good, but transfering a couple of files didn't fail. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: nautilus 1:3.4.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-21.34-generic 3.2.13 Uname: Linux 3.2.0-21-generic x86_64 ApportVersion: 2.0-0ubuntu3 Architecture: amd64 Date: Tue Apr 3 12:31:01 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120301) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/972311/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 972311] Re: Accessing a MTP device like the Galaxy Nexus fails
Oh, I also realised that I have a different error message (even despite the translation): Het weergeven van de inhoud van ‘Galaxy’ is mislukt: DBus error org.freedesktop.DBus.Error.UnknownMethod: Method Enumerate with signature ayssus on interface org.gtk.vfs.Mount doesn't exist Dunno if it's still related now, or if I should create a new bug... -- 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/972311 Title: Accessing a MTP device like the Galaxy Nexus fails Status in “nautilus” package in Ubuntu: Confirmed Bug description: When I connect my Galaxy Nexus to my system (up to date precise) and try to access the data on my phone, I get the following error... The folder contents could not be displayed. Sorry, could not display all the contents of Galaxy: DBus error org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. In Oneiric accessing Android 4.0 devices via Nautilus worked. Not very good, but transfering a couple of files didn't fail. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: nautilus 1:3.4.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-21.34-generic 3.2.13 Uname: Linux 3.2.0-21-generic x86_64 ApportVersion: 2.0-0ubuntu3 Architecture: amd64 Date: Tue Apr 3 12:31:01 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120301) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/972311/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 985451] [NEW] totem flickers between cover art and visualisation
Public bug reported: When playing an MP3 that has embedded cover art, the visualisation appears. However, once or twice a second (roughly) the cover art flicks up for about a frame. This doesn't detract from the playing, it's just quite distracting. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: totem 3.0.1-0ubuntu21 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu5 Architecture: amd64 Date: Thu Apr 19 19:44:15 2012 InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) SourcePackage: totem UpgradeStatus: Upgraded to precise on 2012-03-16 (33 days ago) ** Affects: totem (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 totem in Ubuntu. https://bugs.launchpad.net/bugs/985451 Title: totem flickers between cover art and visualisation Status in “totem” package in Ubuntu: New Bug description: When playing an MP3 that has embedded cover art, the visualisation appears. However, once or twice a second (roughly) the cover art flicks up for about a frame. This doesn't detract from the playing, it's just quite distracting. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: totem 3.0.1-0ubuntu21 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu5 Architecture: amd64 Date: Thu Apr 19 19:44:15 2012 InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) SourcePackage: totem UpgradeStatus: Upgraded to precise on 2012-03-16 (33 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/985451/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 985451] Re: totem flickers between cover art and visualisation
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/985451 Title: totem flickers between cover art and visualisation Status in “totem” package in Ubuntu: New Bug description: When playing an MP3 that has embedded cover art, the visualisation appears. However, once or twice a second (roughly) the cover art flicks up for about a frame. This doesn't detract from the playing, it's just quite distracting. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: totem 3.0.1-0ubuntu21 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu5 Architecture: amd64 Date: Thu Apr 19 19:44:15 2012 InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) SourcePackage: totem UpgradeStatus: Upgraded to precise on 2012-03-16 (33 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/985451/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 972785] Re: Unable to add new startup applications
$ ls .local/share/applications/ alacarte-made.desktop number-none_com-braid_1.desktop bit-blot_com-aquaria_1.desktop PenumbraOverture.desktop frozenbyte-Survivor.desktop wine frozenbyte-Trine.desktopwireshark.desktop galaxy-nexus.desktopwolfire_com-lugaru_1.desktop mimeapps.list -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/972785 Title: Unable to add new startup applications Status in “gnome-session” package in Ubuntu: New Bug description: When attempting to add a program to start on boot, it isn't saved when it should be. To reproduce: 1. Go to the gear/power menu thing at the top-right 2. Select Startup Applications (or whatever it actually says in en) 3. Add a new program 3.1. Fill out the three boxes with something you want 4. Note that your program has been added to the list of startup programs 5. Close that window 6. Open it again 7. Note that your program is no longer there 8. Reboot 9. Note that your program doesn't start up. Expected results: 7. Your program is there. 9. Your program starts up. Notes: * Whether or not you perform steps 6-7, the result of 9 is not affected. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-session-bin 3.2.1-0ubuntu6 ProcVersionSignature: Ubuntu 3.2.0-21.34-generic 3.2.13 Uname: Linux 3.2.0-21-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0-0ubuntu2 Architecture: amd64 Date: Wed Apr 4 07:44:44 2012 InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) SourcePackage: gnome-session UpgradeStatus: Upgraded to precise on 2012-03-16 (18 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/972785/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 972785] Re: Unable to add new startup applications
It works with gedit, but it doesn't work with network manager. The fields I enter are: Name: Network Manager Command: /usr/bin/nm-applet Comment: Network Manager applet The only message that shows in the terminal is: (gnome-session-properties:3602): GLib-GObject-WARNING **: g_object_set_valist: object class `GsmAppDialog' has no property named `allow-shrink' but I don't think that's relevant. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/972785 Title: Unable to add new startup applications Status in “gnome-session” package in Ubuntu: Incomplete Bug description: When attempting to add a program to start on boot, it isn't saved when it should be. To reproduce: 1. Go to the gear/power menu thing at the top-right 2. Select Startup Applications (or whatever it actually says in en) 3. Add a new program 3.1. Fill out the three boxes with something you want 4. Note that your program has been added to the list of startup programs 5. Close that window 6. Open it again 7. Note that your program is no longer there 8. Reboot 9. Note that your program doesn't start up. Expected results: 7. Your program is there. 9. Your program starts up. Notes: * Whether or not you perform steps 6-7, the result of 9 is not affected. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-session-bin 3.2.1-0ubuntu6 ProcVersionSignature: Ubuntu 3.2.0-21.34-generic 3.2.13 Uname: Linux 3.2.0-21-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0-0ubuntu2 Architecture: amd64 Date: Wed Apr 4 07:44:44 2012 InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) SourcePackage: gnome-session UpgradeStatus: Upgraded to precise on 2012-03-16 (18 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/972785/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 972785] [NEW] Unable to add new startup applications
Public bug reported: When attempting to add a program to start on boot, it isn't saved when it should be. To reproduce: 1. Go to the gear/power menu thing at the top-right 2. Select Startup Applications (or whatever it actually says in en) 3. Add a new program 3.1. Fill out the three boxes with something you want 4. Note that your program has been added to the list of startup programs 5. Close that window 6. Open it again 7. Note that your program is no longer there 8. Reboot 9. Note that your program doesn't start up. Expected results: 7. Your program is there. 9. Your program starts up. Notes: * Whether or not you perform steps 6-7, the result of 9 is not affected. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-session-bin 3.2.1-0ubuntu6 ProcVersionSignature: Ubuntu 3.2.0-21.34-generic 3.2.13 Uname: Linux 3.2.0-21-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0-0ubuntu2 Architecture: amd64 Date: Wed Apr 4 07:44:44 2012 InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) SourcePackage: gnome-session UpgradeStatus: Upgraded to precise on 2012-03-16 (18 days ago) ** Affects: gnome-session (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 gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/972785 Title: Unable to add new startup applications Status in “gnome-session” package in Ubuntu: New Bug description: When attempting to add a program to start on boot, it isn't saved when it should be. To reproduce: 1. Go to the gear/power menu thing at the top-right 2. Select Startup Applications (or whatever it actually says in en) 3. Add a new program 3.1. Fill out the three boxes with something you want 4. Note that your program has been added to the list of startup programs 5. Close that window 6. Open it again 7. Note that your program is no longer there 8. Reboot 9. Note that your program doesn't start up. Expected results: 7. Your program is there. 9. Your program starts up. Notes: * Whether or not you perform steps 6-7, the result of 9 is not affected. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-session-bin 3.2.1-0ubuntu6 ProcVersionSignature: Ubuntu 3.2.0-21.34-generic 3.2.13 Uname: Linux 3.2.0-21-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0-0ubuntu2 Architecture: amd64 Date: Wed Apr 4 07:44:44 2012 InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) SourcePackage: gnome-session UpgradeStatus: Upgraded to precise on 2012-03-16 (18 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/972785/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 972785] Re: Unable to add new startup applications
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/972785 Title: Unable to add new startup applications Status in “gnome-session” package in Ubuntu: New Bug description: When attempting to add a program to start on boot, it isn't saved when it should be. To reproduce: 1. Go to the gear/power menu thing at the top-right 2. Select Startup Applications (or whatever it actually says in en) 3. Add a new program 3.1. Fill out the three boxes with something you want 4. Note that your program has been added to the list of startup programs 5. Close that window 6. Open it again 7. Note that your program is no longer there 8. Reboot 9. Note that your program doesn't start up. Expected results: 7. Your program is there. 9. Your program starts up. Notes: * Whether or not you perform steps 6-7, the result of 9 is not affected. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-session-bin 3.2.1-0ubuntu6 ProcVersionSignature: Ubuntu 3.2.0-21.34-generic 3.2.13 Uname: Linux 3.2.0-21-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0-0ubuntu2 Architecture: amd64 Date: Wed Apr 4 07:44:44 2012 InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) SourcePackage: gnome-session UpgradeStatus: Upgraded to precise on 2012-03-16 (18 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/972785/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 964151] [NEW] lightdm should work with both left and right handed mouse
Public bug reported: I use the mouse left handed. When I do something that pops up a dialogue, say telling the computer to shut down from the login screen, the buttons on the dialogue don't respond to the primary mouse button (the right one in this case.) I think the menus to bring up that dialogue are ambidextrous (well, I didn't get button confusion bringing it up, anyway.) ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: lightdm 1.1.9-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-19.30-generic 3.2.11 Uname: Linux 3.2.0-19-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.95-0ubuntu1 Architecture: amd64 Date: Sun Mar 25 10:06:53 2012 InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) SourcePackage: lightdm UpgradeStatus: Upgraded to precise on 2012-03-16 (8 days ago) ** Affects: lightdm (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 lightdm in Ubuntu. https://bugs.launchpad.net/bugs/964151 Title: lightdm should work with both left and right handed mouse Status in “lightdm” package in Ubuntu: New Bug description: I use the mouse left handed. When I do something that pops up a dialogue, say telling the computer to shut down from the login screen, the buttons on the dialogue don't respond to the primary mouse button (the right one in this case.) I think the menus to bring up that dialogue are ambidextrous (well, I didn't get button confusion bringing it up, anyway.) ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: lightdm 1.1.9-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-19.30-generic 3.2.11 Uname: Linux 3.2.0-19-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.95-0ubuntu1 Architecture: amd64 Date: Sun Mar 25 10:06:53 2012 InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) SourcePackage: lightdm UpgradeStatus: Upgraded to precise on 2012-03-16 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/964151/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 964151] Re: lightdm should work with both left and right handed mouse
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/964151 Title: lightdm should work with both left and right handed mouse Status in “lightdm” package in Ubuntu: New Bug description: I use the mouse left handed. When I do something that pops up a dialogue, say telling the computer to shut down from the login screen, the buttons on the dialogue don't respond to the primary mouse button (the right one in this case.) I think the menus to bring up that dialogue are ambidextrous (well, I didn't get button confusion bringing it up, anyway.) ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: lightdm 1.1.9-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-19.30-generic 3.2.11 Uname: Linux 3.2.0-19-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.95-0ubuntu1 Architecture: amd64 Date: Sun Mar 25 10:06:53 2012 InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) SourcePackage: lightdm UpgradeStatus: Upgraded to precise on 2012-03-16 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/964151/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 957794] Re: Mouse pointer reappears while playing a file
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/957794 Title: Mouse pointer reappears while playing a file Status in “totem” package in Ubuntu: New Bug description: When watching a movie file in totem, after a period of time the mouse pointer shows up on its own (i.e. with no movement) on the screen. When this happens, moving the mouse doesn't reactivate the time bar thing at the bottom, but double click will take it out of full screen (single clicking has no noticable effect.) After going back to windowed and then to fullscreen, the mouse behaves normally (activates the time bar, disappears after a few seconds) until the pointer comes back again. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: totem 3.0.1-0ubuntu20 ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9 Uname: Linux 3.2.0-18-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.94.1-0ubuntu2 Architecture: amd64 Date: Sat Mar 17 23:02:12 2012 InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) SourcePackage: totem UpgradeStatus: Upgraded to precise on 2012-03-16 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/957794/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 957794] [NEW] Mouse pointer reappears while playing a file
Public bug reported: When watching a movie file in totem, after a period of time the mouse pointer shows up on its own (i.e. with no movement) on the screen. When this happens, moving the mouse doesn't reactivate the time bar thing at the bottom, but double click will take it out of full screen (single clicking has no noticable effect.) After going back to windowed and then to fullscreen, the mouse behaves normally (activates the time bar, disappears after a few seconds) until the pointer comes back again. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: totem 3.0.1-0ubuntu20 ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9 Uname: Linux 3.2.0-18-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.94.1-0ubuntu2 Architecture: amd64 Date: Sat Mar 17 23:02:12 2012 InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) SourcePackage: totem UpgradeStatus: Upgraded to precise on 2012-03-16 (0 days ago) ** Affects: totem (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 totem in Ubuntu. https://bugs.launchpad.net/bugs/957794 Title: Mouse pointer reappears while playing a file Status in “totem” package in Ubuntu: New Bug description: When watching a movie file in totem, after a period of time the mouse pointer shows up on its own (i.e. with no movement) on the screen. When this happens, moving the mouse doesn't reactivate the time bar thing at the bottom, but double click will take it out of full screen (single clicking has no noticable effect.) After going back to windowed and then to fullscreen, the mouse behaves normally (activates the time bar, disappears after a few seconds) until the pointer comes back again. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: totem 3.0.1-0ubuntu20 ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9 Uname: Linux 3.2.0-18-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.94.1-0ubuntu2 Architecture: amd64 Date: Sat Mar 17 23:02:12 2012 InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) SourcePackage: totem UpgradeStatus: Upgraded to precise on 2012-03-16 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/957794/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 213053] Re: Totem is 'uninterruptible'
I think that's a different thing. The problem here was with processes that didn't respond to a kill. If they get a new PID, then they are being killed and something else is firing them up again. Probably you have a file that is causing the thumbnailer to get stuck, I'd try to figure out what that file is (lsof will help here) and file a new bug on it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/213053 Title: Totem is 'uninterruptible' Status in PulseAudio sound server: Fix Released Status in Ubuntu: Fix Released Status in “fuse” package in Ubuntu: Fix Released Status in “linux” package in Ubuntu: Incomplete Status in “totem” package in Ubuntu: Invalid Bug description: Binary package hint: totem I was editing movies and repeatedly watching the outputs with Totem. After a while I checked system monitor and saw that there was a stray totem process running, and it's status was uninterruptible. It was using less than 200KB of memory but was at 60% CPU usage continuously. I could not kill it or stop it. When I went to restart my system it took over a minute to leave the desktop, and was never able to completely shut down. I had to manually restart. :( This only happened once, and I have no clue what caused it to happen. I have never had a problem like this before. - Description: Ubuntu hardy (development branch) Release: 8.04 Totem Movie Player 2.22.0 (2.22.0-0ubuntu3) using GStreamer 0.10.18 and GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/213053/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 927379] [NEW] Importing a folder with tracks containing some characters causes them to be re-imported
Public bug reported:
To reproduce:
1) have an album in your collection, already loaded into Banshee's collection,
that contains ',' in the tags (song name at least)
2) import the folder containing this album using Media-Import Media... in the
hope that it'll pick up anything newly added
3) notice that the tracks with ',' (possibly others, not sure) get imported
into your collection again as duplicates
Expected:
* These would not get imported as they're already there. This works correctly
for tracks without those characters in their tags.
Note:
* The comma is also in the filename of the track
Further testing:
* This also seems to happen with a track containing '(',')' and ''. It doesn't
happen with tracks that contain just '(',')' or '', it seems to be the
combination.
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: banshee 2.2.1-1ubuntu3
ProcVersionSignature: Ubuntu 3.0.0-15.26-generic 3.0.13
Uname: Linux 3.0.0-15-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
Date: Mon Feb 6 13:23:17 2012
InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007)
ProcEnviron:
LANGUAGE=nl:en_NZ:en
PATH=(custom, user)
LANG=nl_NL.UTF-8
LC_MESSAGES=nl_NL.UTF-8
SHELL=/bin/bash
SourcePackage: banshee
UpgradeStatus: Upgraded to oneiric on 2011-10-13 (115 days ago)
** Affects: banshee (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug oneiric running-unity
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to banshee in Ubuntu.
https://bugs.launchpad.net/bugs/927379
Title:
Importing a folder with tracks containing some characters causes them
to be re-imported
Status in “banshee” package in Ubuntu:
New
Bug description:
To reproduce:
1) have an album in your collection, already loaded into Banshee's
collection, that contains ',' in the tags (song name at least)
2) import the folder containing this album using Media-Import Media... in
the hope that it'll pick up anything newly added
3) notice that the tracks with ',' (possibly others, not sure) get imported
into your collection again as duplicates
Expected:
* These would not get imported as they're already there. This works correctly
for tracks without those characters in their tags.
Note:
* The comma is also in the filename of the track
Further testing:
* This also seems to happen with a track containing '(',')' and ''. It
doesn't happen with tracks that contain just '(',')' or '', it seems to be the
combination.
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: banshee 2.2.1-1ubuntu3
ProcVersionSignature: Ubuntu 3.0.0-15.26-generic 3.0.13
Uname: Linux 3.0.0-15-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
Date: Mon Feb 6 13:23:17 2012
InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007)
ProcEnviron:
LANGUAGE=nl:en_NZ:en
PATH=(custom, user)
LANG=nl_NL.UTF-8
LC_MESSAGES=nl_NL.UTF-8
SHELL=/bin/bash
SourcePackage: banshee
UpgradeStatus: Upgraded to oneiric on 2011-10-13 (115 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/banshee/+bug/927379/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 927379] Re: Importing a folder with tracks containing some characters causes them to be re-imported
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to banshee in Ubuntu.
https://bugs.launchpad.net/bugs/927379
Title:
Importing a folder with tracks containing some characters causes them
to be re-imported
Status in “banshee” package in Ubuntu:
New
Bug description:
To reproduce:
1) have an album in your collection, already loaded into Banshee's
collection, that contains ',' in the tags (song name at least)
2) import the folder containing this album using Media-Import Media... in
the hope that it'll pick up anything newly added
3) notice that the tracks with ',' (possibly others, not sure) get imported
into your collection again as duplicates
Expected:
* These would not get imported as they're already there. This works correctly
for tracks without those characters in their tags.
Note:
* The comma is also in the filename of the track
Further testing:
* This also seems to happen with a track containing '(',')' and ''. It
doesn't happen with tracks that contain just '(',')' or '', it seems to be the
combination.
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: banshee 2.2.1-1ubuntu3
ProcVersionSignature: Ubuntu 3.0.0-15.26-generic 3.0.13
Uname: Linux 3.0.0-15-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
Date: Mon Feb 6 13:23:17 2012
InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007)
ProcEnviron:
LANGUAGE=nl:en_NZ:en
PATH=(custom, user)
LANG=nl_NL.UTF-8
LC_MESSAGES=nl_NL.UTF-8
SHELL=/bin/bash
SourcePackage: banshee
UpgradeStatus: Upgraded to oneiric on 2011-10-13 (115 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/banshee/+bug/927379/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 876055] Re: gnome-terminal stops repainting
Nope, happened to me in xmonad. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/876055 Title: gnome-terminal stops repainting Status in “gnome-terminal” package in Ubuntu: Confirmed Bug description: I haven't been able to reproduce this consistently (sorry) but it's happened twice since I upgraded to 11.10. Sometimes when I switch the workspace to one containing gnome- terminal, g-t fails to repaint. The screen remains the default off- white colour. It hasn't locked up, if I right-click I get a menu and can do things with it. But when I close the menu, the area where it was isn't cleared. I'm using xmonad, and so don't have compositing. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-terminal 3.0.1-0ubuntu3 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu3 Architecture: amd64 Date: Mon Oct 17 12:10:19 2011 ProcEnviron: LANGUAGE=nl_NL:nl PATH=(custom, user) LANG=nl_NL.UTF-8 SHELL=/bin/bash SourcePackage: gnome-terminal UpgradeStatus: Upgraded to oneiric on 2011-10-14 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/876055/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 878560] Re: evolution mail view stops updating
It's still happening, and I've found an email that consistently reproduces it (at least, when I view it within my email.) ** Attachment added: Viewing this as part of email consistently breaks the updating of the evolution preview pane https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/878560/+attachment/2619722/+files/evolution-breaking.mbox -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/878560 Title: evolution mail view stops updating Status in “evolution” package in Ubuntu: Confirmed Status in “xmonad” package in Ubuntu: Incomplete Bug description: Every so often, particularly when going through a set of messages quickly (though it's hard to reproduce) the mail view pane in evolution stops refreshing. That is, it'll get stuck showing whatever it was showing. Content is being rendered there (I can tell because mouseover things still work as expected, you just can't see where they are) but it's not showing up. If I right-click on it, the image of the menu will remain there. If I hide and reshow the pane (ctrl-m) it doesn't fix it, it comes back but still nothing gets drawn there. I'm not using compositing (I'm running xmonad), so that will influence some of these symptoms I expect. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: evolution 3.2.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu3 Architecture: amd64 Date: Thu Oct 20 11:44:27 2011 ProcEnviron: LANGUAGE=nl_NL:nl PATH=(custom, user) LANG=nl_NL.UTF-8 SHELL=/bin/bash SourcePackage: evolution UpgradeStatus: Upgraded to oneiric on 2011-10-14 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/878560/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 896376] Re: Galaxy Nexus (MTP, phone) and Xoom (MTP, tablet) don't show up in Banshee
I have the same thing with rhythmbox on the galaxy nexus. I can manually mount it using mtpfs just fine, but the rhythmbox MTP plugin doesn't notice that it's there. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to banshee in Ubuntu. https://bugs.launchpad.net/bugs/896376 Title: Galaxy Nexus (MTP, phone) and Xoom (MTP, tablet) don't show up in Banshee Status in Banshee Music Player: New Status in “banshee” package in Ubuntu: Triaged Bug description: I have a new phone, but it doesn't show up in Banshee. I've even recompiled libmtp to add the device ID, but that didn't help. As the same thing happens with my Xoom tablet (also an Android device), which is included in the unpatched libmtp, I think this is a Banshee bug. The MTP plugin is enabled. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: banshee 2.2.1-1ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-13.22-generic 3.0.6 Uname: Linux 3.0.0-13-generic x86_64 ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Fri Nov 25 19:45:32 2011 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Alpha amd64 (20110803) ProcEnviron: PATH=(custom, user) LANG=nl_NL.UTF-8 SHELL=/bin/bash SourcePackage: banshee UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/banshee/+bug/896376/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 881807] [NEW] Network manager requires the wrong number of characters for the WPA password
Public bug reported: If I attempt to connect to a WPA network, when I type in the password, the connect button lights up after typing 5 characters, but goes dark again when I type more. The password is longer than 5 characters, so I can't connect to the network. This is the scan details for the network: Cell 01 - Address: 06:1F:D4:00:A0:51 Channel:1 Frequency:2.412 GHz (Channel 1) Quality=44/70 Signal level=-66 dBm Encryption key:on ESSID:Hashigo Zake 2 Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s 9 Mb/s; 12 Mb/s; 18 Mb/s Bit Rates:24 Mb/s; 36 Mb/s; 48 Mb/s; 54 Mb/s Mode:Master Extra:tsf=002f20b41180 Extra: Last beacon: 824ms ago IE: Unknown: 000E4861736869676F205A616B652032 IE: Unknown: 010882848B960C121824 IE: Unknown: 030101 IE: Unknown: 0706465220010D14 IE: Unknown: 200100 IE: Unknown: 2A0103 IE: Unknown: 32043048606C IE: WPA Version 1 Group Cipher : TKIP Pairwise Ciphers (1) : TKIP Authentication Suites (1) : PSK IE: Unknown: DD0900037F0101FF7F ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: network-manager 0.9.1.90-0ubuntu4 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic-pae 3.0.4 Uname: Linux 3.0.0-12-generic-pae i686 ApportVersion: 1.23-0ubuntu3 Architecture: i386 Date: Tue Oct 25 21:42:11 2011 EcryptfsInUse: Yes IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu-Netbook 10.10 Maverick Meerkat - Release i386 (20101007) IpRoute: default via 192.168.43.1 dev wlan1 proto static 169.254.0.0/16 dev wlan1 scope link metric 1000 192.168.43.0/24 dev wlan1 proto kernel scope link src 192.168.43.18 metric 2 Keyfiles: Error: [Errno 2] Bestand of map bestaat niet NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: LANGUAGE=nl_NL:nl:en_NZ:en_AU:en_GB:en PATH=(custom, no user) LANG=en_NZ.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to oneiric on 2011-10-18 (7 days ago) ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 oneiric running-unity -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/881807 Title: Network manager requires the wrong number of characters for the WPA password Status in “network-manager” package in Ubuntu: New Bug description: If I attempt to connect to a WPA network, when I type in the password, the connect button lights up after typing 5 characters, but goes dark again when I type more. The password is longer than 5 characters, so I can't connect to the network. This is the scan details for the network: Cell 01 - Address: 06:1F:D4:00:A0:51 Channel:1 Frequency:2.412 GHz (Channel 1) Quality=44/70 Signal level=-66 dBm Encryption key:on ESSID:Hashigo Zake 2 Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s 9 Mb/s; 12 Mb/s; 18 Mb/s Bit Rates:24 Mb/s; 36 Mb/s; 48 Mb/s; 54 Mb/s Mode:Master Extra:tsf=002f20b41180 Extra: Last beacon: 824ms ago IE: Unknown: 000E4861736869676F205A616B652032 IE: Unknown: 010882848B960C121824 IE: Unknown: 030101 IE: Unknown: 0706465220010D14 IE: Unknown: 200100 IE: Unknown: 2A0103 IE: Unknown: 32043048606C IE: WPA Version 1 Group Cipher : TKIP Pairwise Ciphers (1) : TKIP Authentication Suites (1) : PSK IE: Unknown: DD0900037F0101FF7F ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: network-manager 0.9.1.90-0ubuntu4 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic-pae 3.0.4 Uname: Linux 3.0.0-12-generic-pae i686 ApportVersion: 1.23-0ubuntu3 Architecture: i386 Date: Tue Oct 25 21:42:11 2011 EcryptfsInUse: Yes IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu-Netbook 10.10 Maverick Meerkat - Release i386 (20101007) IpRoute: default via 192.168.43.1 dev wlan1 proto static 169.254.0.0/16 dev wlan1 scope link metric 1000
[Desktop-packages] [Bug 881807] Re: Network manager requires the wrong number of characters for the WPA password
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/881807 Title: Network manager requires the wrong number of characters for the WPA password Status in “network-manager” package in Ubuntu: New Bug description: If I attempt to connect to a WPA network, when I type in the password, the connect button lights up after typing 5 characters, but goes dark again when I type more. The password is longer than 5 characters, so I can't connect to the network. This is the scan details for the network: Cell 01 - Address: 06:1F:D4:00:A0:51 Channel:1 Frequency:2.412 GHz (Channel 1) Quality=44/70 Signal level=-66 dBm Encryption key:on ESSID:Hashigo Zake 2 Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s 9 Mb/s; 12 Mb/s; 18 Mb/s Bit Rates:24 Mb/s; 36 Mb/s; 48 Mb/s; 54 Mb/s Mode:Master Extra:tsf=002f20b41180 Extra: Last beacon: 824ms ago IE: Unknown: 000E4861736869676F205A616B652032 IE: Unknown: 010882848B960C121824 IE: Unknown: 030101 IE: Unknown: 0706465220010D14 IE: Unknown: 200100 IE: Unknown: 2A0103 IE: Unknown: 32043048606C IE: WPA Version 1 Group Cipher : TKIP Pairwise Ciphers (1) : TKIP Authentication Suites (1) : PSK IE: Unknown: DD0900037F0101FF7F ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: network-manager 0.9.1.90-0ubuntu4 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic-pae 3.0.4 Uname: Linux 3.0.0-12-generic-pae i686 ApportVersion: 1.23-0ubuntu3 Architecture: i386 Date: Tue Oct 25 21:42:11 2011 EcryptfsInUse: Yes IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu-Netbook 10.10 Maverick Meerkat - Release i386 (20101007) IpRoute: default via 192.168.43.1 dev wlan1 proto static 169.254.0.0/16 dev wlan1 scope link metric 1000 192.168.43.0/24 dev wlan1 proto kernel scope link src 192.168.43.18 metric 2 Keyfiles: Error: [Errno 2] Bestand of map bestaat niet NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: LANGUAGE=nl_NL:nl:en_NZ:en_AU:en_GB:en PATH=(custom, no user) LANG=en_NZ.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to oneiric on 2011-10-18 (7 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/881807/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 878560] Re: evolution mail view stops updating
Guilherme, that looks exactly like what I was seeing. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/878560 Title: evolution mail view stops updating Status in “evolution” package in Ubuntu: Incomplete Status in “xmonad” package in Ubuntu: New Bug description: Every so often, particularly when going through a set of messages quickly (though it's hard to reproduce) the mail view pane in evolution stops refreshing. That is, it'll get stuck showing whatever it was showing. Content is being rendered there (I can tell because mouseover things still work as expected, you just can't see where they are) but it's not showing up. If I right-click on it, the image of the menu will remain there. If I hide and reshow the pane (ctrl-m) it doesn't fix it, it comes back but still nothing gets drawn there. I'm not using compositing (I'm running xmonad), so that will influence some of these symptoms I expect. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: evolution 3.2.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu3 Architecture: amd64 Date: Thu Oct 20 11:44:27 2011 ProcEnviron: LANGUAGE=nl_NL:nl PATH=(custom, user) LANG=nl_NL.UTF-8 SHELL=/bin/bash SourcePackage: evolution UpgradeStatus: Upgraded to oneiric on 2011-10-14 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/878560/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 878560] Re: evolution mail view stops updating
Changing to Show plaintext if present didn't repair it for me, I'll see if it prevents if happening again. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/878560 Title: evolution mail view stops updating Status in “evolution” package in Ubuntu: Confirmed Status in “xmonad” package in Ubuntu: Incomplete Bug description: Every so often, particularly when going through a set of messages quickly (though it's hard to reproduce) the mail view pane in evolution stops refreshing. That is, it'll get stuck showing whatever it was showing. Content is being rendered there (I can tell because mouseover things still work as expected, you just can't see where they are) but it's not showing up. If I right-click on it, the image of the menu will remain there. If I hide and reshow the pane (ctrl-m) it doesn't fix it, it comes back but still nothing gets drawn there. I'm not using compositing (I'm running xmonad), so that will influence some of these symptoms I expect. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: evolution 3.2.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu3 Architecture: amd64 Date: Thu Oct 20 11:44:27 2011 ProcEnviron: LANGUAGE=nl_NL:nl PATH=(custom, user) LANG=nl_NL.UTF-8 SHELL=/bin/bash SourcePackage: evolution UpgradeStatus: Upgraded to oneiric on 2011-10-14 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/878560/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 878560] Re: evolution mail view stops updating
It just happened to me again. I'm attaching a screenshot, which is interesting as it shows that the pane is still scrolling, just the content in it isn't rendering. The scrollbar moves when I scroll, also. Just before this happened, I flicked to a different workspace, and when I came back, none of the evolution UI repainted until something caused it to happen (e.g. mouseover.) Then I changed message, it rendered, and then stopped rendering when I tried to scroll. The reason that you can't see the partial message in here is that I changed workspace and back again by accident, which makes it paint as the default colour. Not sure if this is a useful data point, but it might be. Note that this is almost certainly related to Bug #876055 that I reported shortly before this one, and is the same symptom but in Gnome Terminal. (also, I think the launchpad janitor got it wrong, I suspect it's evolution or gtk or something rather than xmonad.) ** Attachment added: Screenshot of evolution breaking https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/878560/+attachment/2570938/+files/evo-break.png ** Changed in: xmonad (Ubuntu) Status: Confirmed = Incomplete ** Changed in: evolution (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/878560 Title: evolution mail view stops updating Status in “evolution” package in Ubuntu: Confirmed Status in “xmonad” package in Ubuntu: Incomplete Bug description: Every so often, particularly when going through a set of messages quickly (though it's hard to reproduce) the mail view pane in evolution stops refreshing. That is, it'll get stuck showing whatever it was showing. Content is being rendered there (I can tell because mouseover things still work as expected, you just can't see where they are) but it's not showing up. If I right-click on it, the image of the menu will remain there. If I hide and reshow the pane (ctrl-m) it doesn't fix it, it comes back but still nothing gets drawn there. I'm not using compositing (I'm running xmonad), so that will influence some of these symptoms I expect. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: evolution 3.2.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu3 Architecture: amd64 Date: Thu Oct 20 11:44:27 2011 ProcEnviron: LANGUAGE=nl_NL:nl PATH=(custom, user) LANG=nl_NL.UTF-8 SHELL=/bin/bash SourcePackage: evolution UpgradeStatus: Upgraded to oneiric on 2011-10-14 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/878560/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 878560] [NEW] evolution mail view stops updating
Public bug reported: Every so often, particularly when going through a set of messages quickly (though it's hard to reproduce) the mail view pane in evolution stops refreshing. That is, it'll get stuck showing whatever it was showing. Content is being rendered there (I can tell because mouseover things still work as expected, you just can't see where they are) but it's not showing up. If I right-click on it, the image of the menu will remain there. If I hide and reshow the pane (ctrl-m) it doesn't fix it, it comes back but still nothing gets drawn there. I'm not using compositing (I'm running xmonad), so that will influence some of these symptoms I expect. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: evolution 3.2.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu3 Architecture: amd64 Date: Thu Oct 20 11:44:27 2011 ProcEnviron: LANGUAGE=nl_NL:nl PATH=(custom, user) LANG=nl_NL.UTF-8 SHELL=/bin/bash SourcePackage: evolution UpgradeStatus: Upgraded to oneiric on 2011-10-14 (5 days ago) ** Affects: evolution (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug oneiric -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/878560 Title: evolution mail view stops updating Status in “evolution” package in Ubuntu: New Bug description: Every so often, particularly when going through a set of messages quickly (though it's hard to reproduce) the mail view pane in evolution stops refreshing. That is, it'll get stuck showing whatever it was showing. Content is being rendered there (I can tell because mouseover things still work as expected, you just can't see where they are) but it's not showing up. If I right-click on it, the image of the menu will remain there. If I hide and reshow the pane (ctrl-m) it doesn't fix it, it comes back but still nothing gets drawn there. I'm not using compositing (I'm running xmonad), so that will influence some of these symptoms I expect. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: evolution 3.2.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu3 Architecture: amd64 Date: Thu Oct 20 11:44:27 2011 ProcEnviron: LANGUAGE=nl_NL:nl PATH=(custom, user) LANG=nl_NL.UTF-8 SHELL=/bin/bash SourcePackage: evolution UpgradeStatus: Upgraded to oneiric on 2011-10-14 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/878560/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 878560] Re: evolution mail view stops updating
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/878560 Title: evolution mail view stops updating Status in “evolution” package in Ubuntu: New Bug description: Every so often, particularly when going through a set of messages quickly (though it's hard to reproduce) the mail view pane in evolution stops refreshing. That is, it'll get stuck showing whatever it was showing. Content is being rendered there (I can tell because mouseover things still work as expected, you just can't see where they are) but it's not showing up. If I right-click on it, the image of the menu will remain there. If I hide and reshow the pane (ctrl-m) it doesn't fix it, it comes back but still nothing gets drawn there. I'm not using compositing (I'm running xmonad), so that will influence some of these symptoms I expect. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: evolution 3.2.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu3 Architecture: amd64 Date: Thu Oct 20 11:44:27 2011 ProcEnviron: LANGUAGE=nl_NL:nl PATH=(custom, user) LANG=nl_NL.UTF-8 SHELL=/bin/bash SourcePackage: evolution UpgradeStatus: Upgraded to oneiric on 2011-10-14 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/878560/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 876015] Re: gnome-terminal doesn't respect the setting to show the menu bar on startup
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/876015 Title: gnome-terminal doesn't respect the setting to show the menu bar on startup Status in “gnome-terminal” package in Ubuntu: New Bug description: If you have gnome-terminal set to not show the menu bar, when a terminal window is opened, the menu bar shows anyway. Selecting and then deselecting the option will remove it. This is not using Unity (using xmonad instead.) ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-terminal 3.0.1-0ubuntu3 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu3 Architecture: amd64 Date: Mon Oct 17 10:52:25 2011 ProcEnviron: LANGUAGE=nl_NL:nl PATH=(custom, user) LANG=nl_NL.UTF-8 SHELL=/bin/bash SourcePackage: gnome-terminal UpgradeStatus: Upgraded to oneiric on 2011-10-14 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/876015/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 876015] [NEW] gnome-terminal doesn't respect the setting to show the menu bar on startup
Public bug reported: If you have gnome-terminal set to not show the menu bar, when a terminal window is opened, the menu bar shows anyway. Selecting and then deselecting the option will remove it. This is not using Unity (using xmonad instead.) ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-terminal 3.0.1-0ubuntu3 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu3 Architecture: amd64 Date: Mon Oct 17 10:52:25 2011 ProcEnviron: LANGUAGE=nl_NL:nl PATH=(custom, user) LANG=nl_NL.UTF-8 SHELL=/bin/bash SourcePackage: gnome-terminal UpgradeStatus: Upgraded to oneiric on 2011-10-14 (2 days ago) ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug oneiric -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/876015 Title: gnome-terminal doesn't respect the setting to show the menu bar on startup Status in “gnome-terminal” package in Ubuntu: New Bug description: If you have gnome-terminal set to not show the menu bar, when a terminal window is opened, the menu bar shows anyway. Selecting and then deselecting the option will remove it. This is not using Unity (using xmonad instead.) ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-terminal 3.0.1-0ubuntu3 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu3 Architecture: amd64 Date: Mon Oct 17 10:52:25 2011 ProcEnviron: LANGUAGE=nl_NL:nl PATH=(custom, user) LANG=nl_NL.UTF-8 SHELL=/bin/bash SourcePackage: gnome-terminal UpgradeStatus: Upgraded to oneiric on 2011-10-14 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/876015/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 876015] Re: gnome-terminal doesn't respect the setting to show the menu bar on startup
Attached screenshot showing what I'm talking about. Also, the value in UBUNTU_MENUPROXY makes no difference. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/876015 Title: gnome-terminal doesn't respect the setting to show the menu bar on startup Status in “gnome-terminal” package in Ubuntu: New Bug description: If you have gnome-terminal set to not show the menu bar, when a terminal window is opened, the menu bar shows anyway. Selecting and then deselecting the option will remove it. This is not using Unity (using xmonad instead.) ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-terminal 3.0.1-0ubuntu3 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu3 Architecture: amd64 Date: Mon Oct 17 10:52:25 2011 ProcEnviron: LANGUAGE=nl_NL:nl PATH=(custom, user) LANG=nl_NL.UTF-8 SHELL=/bin/bash SourcePackage: gnome-terminal UpgradeStatus: Upgraded to oneiric on 2011-10-14 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/876015/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 876015] Re: gnome-terminal doesn't respect the setting to show the menu bar on startup
** Attachment added: Screenshot illustrating the issue https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/876015/+attachment/2551807/+files/gnome-terminal-menu.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/876015 Title: gnome-terminal doesn't respect the setting to show the menu bar on startup Status in “gnome-terminal” package in Ubuntu: New Bug description: If you have gnome-terminal set to not show the menu bar, when a terminal window is opened, the menu bar shows anyway. Selecting and then deselecting the option will remove it. This is not using Unity (using xmonad instead.) ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-terminal 3.0.1-0ubuntu3 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu3 Architecture: amd64 Date: Mon Oct 17 10:52:25 2011 ProcEnviron: LANGUAGE=nl_NL:nl PATH=(custom, user) LANG=nl_NL.UTF-8 SHELL=/bin/bash SourcePackage: gnome-terminal UpgradeStatus: Upgraded to oneiric on 2011-10-14 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/876015/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 876055] Re: gnome-terminal stops repainting
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/876055 Title: gnome-terminal stops repainting Status in “gnome-terminal” package in Ubuntu: New Bug description: I haven't been able to reproduce this consistently (sorry) but it's happened twice since I upgraded to 11.10. Sometimes when I switch the workspace to one containing gnome- terminal, g-t fails to repaint. The screen remains the default off- white colour. It hasn't locked up, if I right-click I get a menu and can do things with it. But when I close the menu, the area where it was isn't cleared. I'm using xmonad, and so don't have compositing. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-terminal 3.0.1-0ubuntu3 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu3 Architecture: amd64 Date: Mon Oct 17 12:10:19 2011 ProcEnviron: LANGUAGE=nl_NL:nl PATH=(custom, user) LANG=nl_NL.UTF-8 SHELL=/bin/bash SourcePackage: gnome-terminal UpgradeStatus: Upgraded to oneiric on 2011-10-14 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/876055/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 876055] [NEW] gnome-terminal stops repainting
Public bug reported: I haven't been able to reproduce this consistently (sorry) but it's happened twice since I upgraded to 11.10. Sometimes when I switch the workspace to one containing gnome-terminal, g-t fails to repaint. The screen remains the default off-white colour. It hasn't locked up, if I right-click I get a menu and can do things with it. But when I close the menu, the area where it was isn't cleared. I'm using xmonad, and so don't have compositing. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-terminal 3.0.1-0ubuntu3 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu3 Architecture: amd64 Date: Mon Oct 17 12:10:19 2011 ProcEnviron: LANGUAGE=nl_NL:nl PATH=(custom, user) LANG=nl_NL.UTF-8 SHELL=/bin/bash SourcePackage: gnome-terminal UpgradeStatus: Upgraded to oneiric on 2011-10-14 (2 days ago) ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug oneiric -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/876055 Title: gnome-terminal stops repainting Status in “gnome-terminal” package in Ubuntu: New Bug description: I haven't been able to reproduce this consistently (sorry) but it's happened twice since I upgraded to 11.10. Sometimes when I switch the workspace to one containing gnome- terminal, g-t fails to repaint. The screen remains the default off- white colour. It hasn't locked up, if I right-click I get a menu and can do things with it. But when I close the menu, the area where it was isn't cleared. I'm using xmonad, and so don't have compositing. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-terminal 3.0.1-0ubuntu3 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu3 Architecture: amd64 Date: Mon Oct 17 12:10:19 2011 ProcEnviron: LANGUAGE=nl_NL:nl PATH=(custom, user) LANG=nl_NL.UTF-8 SHELL=/bin/bash SourcePackage: gnome-terminal UpgradeStatus: Upgraded to oneiric on 2011-10-14 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/876055/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
