[Bug 2072146] [NEW] package xrdp 0.9.12-1ubuntu0.1 failed to install/upgrade: o subprocesso instalado, do pacote xrdp, o script post-installation retornou erro do status de saída 1
Public bug reported: Linux said to me it have a error ProblemType: Package DistroRelease: Ubuntu 20.04 Package: xrdp 0.9.12-1ubuntu0.1 ProcVersionSignature: Ubuntu 5.4.0-187.207-generic 5.4.271 Uname: Linux 5.4.0-187-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Jul 4 17:15:47 2024 ErrorMessage: o subprocesso instalado, do pacote xrdp, o script post-installation retornou erro do status de saída 1 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.10 SourcePackage: xrdp Title: package xrdp 0.9.12-1ubuntu0.1 failed to install/upgrade: o subprocesso instalado, do pacote xrdp, o script post-installation retornou erro do status de saída 1 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.xrdp.sesman.ini: 2022-06-08T14:54:11.732992 mtime.conffile..etc.xrdp.xrdp.ini: 2022-06-08T14:54:11.728992 ** Affects: xrdp (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to xrdp in Ubuntu. https://bugs.launchpad.net/bugs/2072146 Title: package xrdp 0.9.12-1ubuntu0.1 failed to install/upgrade: o subprocesso instalado, do pacote xrdp, o script post-installation retornou erro do status de saída 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xrdp/+bug/2072146/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
Thanks for the detailed reply @jjohansen, Do you think it would be feasible to spawn a pop-up that says something like "This application uses namespaces which is considered vulnerable to exploits, are you sure you want to continue?" and ask for the password to allow the application to run. This would resolve the issue while still allowing portable applications to run properly. This could be achieved for example providing a tool to ask apparmor for permissions. From my side I can just detect if apparmor is used and ask apparmor to grant access to namespaces, in term, apparmor would spawn a pop-up for the user saying that my application is requesting this permission. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to devhelp in Ubuntu. https://bugs.launchpad.net/bugs/2046844 Title: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/2046844/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
Thanks for the reply! My use case is this one 'shipped as a .tar.gz that people unpack into their home dir and then use'. To me it seems counter-intuitive to force applications to run un-sanboxed for added security; both the solutions proposed (with the application profile and to turn off the user namespace restrictions) would require root privileges, which I currently do not require users to have to be able to run my application. Does Ubuntu have plans for an alternative to bubblewrap sandboxing? Blocking kernel features because they might be exploited seems really extreme. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to devhelp in Ubuntu. https://bugs.launchpad.net/bugs/2046844 Title: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/2046844/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
Hello, Pardon my ignorance, but I ship applications with my own build of bubblewrap to run in a sandboxed manner. bwrap's pivot_root allows my application to work across several distros without worrying about issues with missing or incompatible libraries; it also makes possible to run the same binary on both musl and glibc systems. Does this mean that this will never work on ubuntu again even after the proposed fix (since I do not use the system provided /usr/bin/bwrap binary)? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to devhelp in Ubuntu. https://bugs.launchpad.net/bugs/2046844 Title: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/2046844/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1974054] Re: Without a reason gnome-shell CPU usage gets high
I had the same problem, and my computer graphics felt slow (i.e the side bar opening animation). I had fixed this by messing with the nvidia drivers, using prime-select to select nvidia, etc. However after update plus restart, this started to happen again. I noticed gnome-shell always at 30% more or less. I disabled the extension "Vitals" but had the same issue, and disabled all extensions and the issue persisted. So I logged out and in again, and it started working correctly. I re-enabled extensions minus-vitals, and so far it is working correctly with the animations -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1974054 Title: Without a reason gnome-shell CPU usage gets high To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1974054/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1994019] Re: Black screen after login with MUTTER_DEBUG_FORCE_KMS_MODE=simple
I reinstalled Ubuntu 22.10 and I can see no issues. It seems you were right Daniel. Please close this bug, nothing to see here. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1994019 Title: Black screen after login with MUTTER_DEBUG_FORCE_KMS_MODE=simple To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1994019/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1994019] Re: Black screen after login with MUTTER_DEBUG_FORCE_KMS_MODE=simple
Removed the llvm oibaf package altogether and still have the same issue -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1994019 Title: Black screen after login with MUTTER_DEBUG_FORCE_KMS_MODE=simple To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1994019/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1994019] Re: Black screen after login with MUTTER_DEBUG_FORCE_KMS_MODE=simple
I see I still have the llvm Oibaf package, but that doesn't seem related (and I ppa-purged the PPA, so IDK why that's still there...) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1994019 Title: Black screen after login with MUTTER_DEBUG_FORCE_KMS_MODE=simple To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1994019/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1994019] [NEW] Black screen after login with MUTTER_DEBUG_FORCE_KMS_MODE=simple
Public bug reported: The same as in bug 1994000. I removed the oibaf PPAs altogether and now should be running the standard distro packages. The situation has not been solved. I also attach the prevboot file. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.0-1ubuntu2 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: Mon Oct 24 11:27:47 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-09-26 (27 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: Upgraded to kinetic on 2022-10-20 (3 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic third-party-packages wayland-session ** Attachment added: "prevboot.txt" https://bugs.launchpad.net/bugs/1994019/+attachment/5626387/+files/prevboot.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1994019 Title: Black screen after login with MUTTER_DEBUG_FORCE_KMS_MODE=simple To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1994019/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1994000] Re: Can't log in anymore after setting MUTTER_DEBUG_FORCE_KMS_MODE=simple
From the file, it would seem it actually booted into the session but didn't show anything... -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1994000 Title: Can't log in anymore after setting MUTTER_DEBUG_FORCE_KMS_MODE=simple To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1994000/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1994000] Re: Can't log in anymore after setting MUTTER_DEBUG_FORCE_KMS_MODE=simple
I just switched to the non-atomic KMS (MUTTER_DEBUG_FORCE_KMS_MODE=simple). My computer turned to black and turned unusable. I wasn't able to Crtl+Alt+F3 and switch to the terminal at all. Hopefully, I was able to change the /etc/environment to the default with a live CD and was able to boot again to my computer normally. I can't see any crashes related to this (the last crash was yesterday, and this was a few minutes ago) in /var/crash. I can upload, though, the system log from the previous boot. ** Attachment added: "prevboot.txt" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1994000/+attachment/5626377/+files/prevboot.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1994000 Title: Can't log in anymore after setting MUTTER_DEBUG_FORCE_KMS_MODE=simple To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1994000/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1994000] Re: Can't log in anymore after setting MUTTER_DEBUG_FORCE_KMS_MODE=simple
Well, I wasn't using that one right now because, as I said, made me unable to use my computer. Will try to do as you suggest. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1994000 Title: Can't log in anymore after setting MUTTER_DEBUG_FORCE_KMS_MODE=simple To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1994000/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968040] Re: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]
Hello Daniel. Thanks for your help, see bug 1994000. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1968040 Title: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument] To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1968040/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1994000] [NEW] Laptop screen can't be turned on after suspension or locking
Public bug reported: My laptop is running a Hybrid Nvidia RTX3060 + Intel i5 11400h graphics. After installing the Nvidia drivers and with Wayland (this doesn't happen with Xorg), once the screen is turned off (for example, by locking the screen or suspending the computer, it cannot be turned on. This is a behavior similarish to the one in bug 1968040 (IDK if that one was also triggered by a screen lock, this one gets triggered inmediately after turning off the screen for whatever reason). In 22.04, I solved it quite easily by setting MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0. As suggested in that ticket, I set this time MUTTER_DEBUG_FORCE_KMS_MODE=simple. I unfortunately cannot tell whether this would solve my issues because, when I reboot my computer with that variable, I simply cannot log in into my account. I type my password as usual (the login screen works perfectly, though) and then, once submited, the output is a black screen (LCD is on, though) and nothing shows up after. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.0-1ubuntu2 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: Mon Oct 24 08:40:12 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-09-26 (27 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: Upgraded to kinetic on 2022-10-20 (3 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic third-party-packages wayland-session -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1994000 Title: Laptop screen can't be turned on after suspension or locking To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1994000/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968040] Re: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]
Same issue in 22.10. MUTTER_DEBUG_FORCE_KMS_MODE=simple doesn't work (it gets stuck in the login screen, I can't actually login to my session). -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1968040 Title: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument] To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1968040/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968040] Re: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]
#23 yes. My laptop is a Nvidia+Intel hybrid laptop. Internal screen now wakes up (although the lockscreen blurred background is shown black, but that's a minor issue for me), and external one works perfectly. I never had performance issues, and once I get past the lockscreen it just works. Again, on Fedora I simply did not have such a problem. I wonder what did Canonical do on Ubuntu for this bug to appear. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1968040 Title: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument] To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1968040/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968040] Re: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]
Hi Daniel! #20 works for me! Thanks! Do you have any explanation for this? How come this was not a problem back when I was running Fedora? Is Ubuntu 22.04 using an older, unfixed version of some package? Was this bug introduced downstream in the Ubuntu release? Are there any plans of fixing this for 22.04.1? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1968040 Title: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument] To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1968040/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968040] Re: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]
I'm facing the same issue (duplicated in reported bug 1971674) with my Mi Notebook Pro 2018 running Ubuntu 22.04, an Intel® Core™ i7-8550U with an NVIDIA GeForce MX150 using Wayland. I thought the issue was with Nvidia, but I can tell that's not the case. ** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1968040/+attachment/5586937/+files/journal.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1968040 Title: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1968040/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1971149] Re: Wayland session: Internal display is black after sleep
Thank you Daniel, I just did (bug #1971674) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1971149 Title: Wayland session: Internal display is black after sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971149/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1971674] [NEW] Laptop screen black (not powered on) when inactive but NOT in sleep
Public bug reported: I thought this was similar to bug #1971149, but that's not the case at all. Apparently my problem comes from the screen being black but not suspended (while playing some audio). Suspending the laptop (by closing the lid or pressing the POWER buttom) and then waking it up solves the problem. Let me attach you the log. I'm on a Mi Notebook Pro 2018 running Ubuntu 22.04, an Intel® Core™ i7-8550U with an NVIDIA GeForce MX150 using Wayland. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 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 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Thu May 5 10:51:26 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-04-30 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) 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 ** Attachment added: "journal.txt" https://bugs.launchpad.net/bugs/1971674/+attachment/5586891/+files/journal.txt ** Description changed: - I thought this was similar to #1971149, but that's not the case at all. - Apparently my problem comes from the screen being black but not + I thought this was similar to bug #1971149, but that's not the case at + all. Apparently my problem comes from the screen being black but not suspended (while playing some audio). Suspending the laptop (by closing the lid or pressing the POWER buttom) and then waking it up solves the problem. Let me attach you the log. I'm on a Mi Notebook Pro 2018 running Ubuntu 22.04, an Intel® Core™ i7-8550U with an NVIDIA GeForce MX150 using Wayland. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 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 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Thu May 5 10:51:26 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-04-30 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Summary changed: - Laptop black (not powered on) when inactive but NOT in sleep + Laptop screen black (not powered on) when inactive but NOT in sleep -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1971674 Title: Laptop screen black (not powered on) when inactive but NOT in sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1971674/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1971149] Re: Wayland session: Internal display is black after sleep
Here you have ** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1971149/+attachment/5586890/+files/journal.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1971149 Title: Wayland session: Internal display is black after sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971149/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1971149] Re: Wayland session: Internal display is black after sleep
I'm facing a similar issue. I'm also using Wayland and a Nvidia MX150 card. Let me attach the log once I have the issue again. It seems to happen after long periods of sleep. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1971149 Title: Wayland session: Internal display is black after sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971149/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1870736] Re: [nvidia] Screen scaling 125% gives 200%
RTX 2080, same problem -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1870736 Title: [nvidia] Screen scaling 125% gives 200% To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870736/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1827428] Re: Mouse cursor left frozen copy of itself
Having this problem in 20.04 GPU: AMD RX 5700XT Fractional Scaling: 175% Display: 4k Asus MG28UQ Also, I can "workaround" it by moving the cursor to the bottom right, so it will be hidden there. But then on Pressing F11 (for fullscreen in Firefox / Youtube) the auto hidden dock will reveal constantly and there will be a loss of performance, like if it is in a continuous loop -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1827428 Title: Mouse cursor left frozen copy of itself To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1827428/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1181666] Re: gnome-shell randomly blocks mouse clicks from working in app windows
This is also happening in Ubuntu 20.04 with Gnome 3.36 and is very annoying -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1181666 Title: gnome-shell randomly blocks mouse clicks from working in app windows To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1181666/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1825720] Re: No option to 'star' file in 19.04
This is another weird solution. It may be correct but there is absolutely no evidence or hints that this is the way to solve it. A feature in Nautilus as simple as starring a file or folder so that it can show up in the Starred entry in the sidebar should be as easy as bookmarking a location, or renaming a file. The option should be on the list after right click, without a hidden and obscure trail to enable it. Now, the need to go to Settings, then Search, then "gear", then Other, then... is a complete nonsense. I've been using Ubuntu and other Linux distros since 1998 (eventually) and 2005 (continuously) and it seems that the developers' community does all efforts to make things difficult. Come on! A feature in an application must be set/unset in the application settings/properties. A new feature should be ON by default, or at least asked during installation. Imagine you buying a car with a new feature, say ABS... the salesperson says "This car has ABS" and nothing else, and you leave happily driving, and your ABS does not work, just to realize after exhaustive search that you must take the car to Grease Monkeys to enable the feature. ABSolutely nonsense! You keep the secrets on an almost unreachable oracle as if you don't want this marvelous OS to grow and become popular. YOU make it difficult. YOU want to keep it restricted to a small community. Laypeople have enormous difficulties to handle things like that. I am not a layperson. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1825720 Title: No option to 'star' file in 19.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1825720/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1672424] Re: Cannot install Debian files outside of the repositories
@CrazySky
The Ubuntu developers added the potential fix to "proposed" (which is not
enabled by default in Ubuntu) so that testers could opt in to get and test it.
When the developers are satisfied that the fix has had enough testing, and has
passed the tests, then they will add the fix to some other repository
("updates" I think) which is enabled by default.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1672424
Title:
Cannot install Debian files outside of the repositories
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1672424/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1672113] [NEW] package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 2
Public bug reported: i cant install software brackets because i can problem in gconf2 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: gconf2 3.2.6-3ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 Uname: Linux 4.4.0-66-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Sun Mar 12 00:05:26 2017 ErrorMessage: el subproceso instalado el script post-installation devolvió el código de salida de error 2 InstallationDate: Installed on 2016-05-06 (310 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gconf (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1672113 Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1672113/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1666676] Re: Enable tracker by default for Unity too
Hi Jeremy/Carlos, thanks for working on better search for Nautilus, we've needed this for a long time. I have some questions! - What does an upgrade look like? Let's say I have a home directory with gigs of data, when I accomplish an upgrade to 17.10 when/how does indexing take place? Is this something that happens in the background or during a package installation? Is indexing a long process? Is it something we need to display to the user? Is it one of those things where we'll need to inform users in the release notes that an expensive io operation will take place as part of the upgrade? - In the past I recall having to modify inotify handles for performance, at some point the default handles we set in ubuntu would run out and search wouldn't work well at all. Since that was years ago I'm assuming these sorts of issues have been sorted out? Thanks! -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/176 Title: Enable tracker by default for Unity too To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/176/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 149076] Re: I can't write a cd
** Package changed: cdrkit (Ubuntu) => brasero (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to brasero in Ubuntu. https://bugs.launchpad.net/bugs/149076 Title: I can't write a cd To manage notifications about this bug go to: https://bugs.launchpad.net/pywodim/+bug/149076/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1641324] [NEW] package systemd-shim 9-1bzr4ubuntu1 failed to install/upgrade: subprocess installed post-removal script returned error exit status 2
Public bug reported: Restoring Xubuntu Xenial to manifest list of contents ProblemType: Package DistroRelease: Ubuntu 16.04 Package: systemd-shim 9-1bzr4ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Sat Nov 12 11:19:26 2016 ErrorMessage: subprocess installed post-removal script returned error exit status 2 InstallationDate: Installed on 2014-03-19 (969 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: systemd-shim Title: package systemd-shim 9-1bzr4ubuntu1 failed to install/upgrade: subprocess installed post-removal script returned error exit status 2 UpgradeStatus: Upgraded to xenial on 2016-11-11 (0 days ago) mtime.conffile..etc.dbus-1.system.d.org.freedesktop.systemd1.conf: 2016-10-26T09:04:44 ** Affects: systemd-shim (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check xenial -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1641324 Title: package systemd-shim 9-1bzr4ubuntu1 failed to install/upgrade: subprocess installed post-removal script returned error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1641324/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1628687] [NEW] Assertion failure when PID 1 receives a zero-length message over notify socket
Public bug reported: Environment: Xenial 16.04.1 Amd64 Description. Systemd fails an assertion in manager_invoke_notify_message when a zero- length message is received over /run/systemd/notify. This allows a local user to perform a denial-of-service attack against PID 1. How to trigger the bug: $ while true; do NOTIFY_SOCKET=/run/systemd/notify systemd-notify ""; done The following entries are written into /var/log/syslog, at this point systemd is crashed. Sep 28 20:57:20 ubuntu systemd[1]: Started User Manager for UID 1000. Sep 28 20:57:28 ubuntu systemd[1]: Assertion 'n > 0' failed at ../src/core/manager.c:1501, function manager_invoke_notify_message(). Aborting. Sep 28 20:57:29 ubuntu systemd[1]: Caught , dumped core as pid 1307. Sep 28 20:57:29 ubuntu systemd[1]: Freezing execution. Public bug: https://github.com/systemd/systemd/issues/4234 ** Affects: systemd (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: sts ** Tags added: sts -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1628687 Title: Assertion failure when PID 1 receives a zero-length message over notify socket To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1628687/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1292113] Re: CTRL+ALT+T - shortcut to open Terminal is does not work
Still happens on: Distributor ID: Ubuntu Description:Ubuntu 14.04.3 LTS Release:14.04 Codename: trusty The shortkeys works almost all the time. But sometimes, it does not work. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1292113 Title: CTRL+ALT+T - shortcut to open Terminal is does not work To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1292113/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1504665] Re: Evolution fails to show IMAP folder "Inbox". It only shows the bogus empty folder "INBOX" (all caps)
@Sebastien Bacher (seb128) Do you think this update would fit the SRU criteria? The criterion that comes closest to matching is: Bugs which do not fit under above categories, but (1) have an obviously safe patch and (2) affect an application rather than critical infrastructure packages (like X.org or the kernel). But I do not know if this bug has an "obviously safe patch". I myself am using evolution 3.18.2-0ubuntu1~wily1 (along with many other Gnome 3.18 packages) from gnome3-staging PPA. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1504665 Title: Evolution fails to show IMAP folder "Inbox". It only shows the bogus empty folder "INBOX" (all caps) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1504665/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1504665] Re: Evolution fails to show IMAP folder "Inbox". It only shows the bogus empty folder "INBOX" (all caps)
** Summary changed: - Evolution fails to show Imap folder "Inbox". It only shows the unexisting grayed-out empty folder "INBOX" (all caps) + Evolution fails to show IMAP folder "Inbox". It only shows the bogus empty folder "INBOX" (all caps) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1504665 Title: Evolution fails to show IMAP folder "Inbox". It only shows the bogus empty folder "INBOX" (all caps) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1504665/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1504665] Re: Evolution fails to show Imap folder "Inbox". It only shows the unexisting grayed-out empty folder "INBOX" (all caps)
I have worked around the bug by using another email client to subscribe to Inbox. Then Evolution started working correctly. Please see this thread: https://mail.gnome.org/archives/evolution-list/2015-October/msg00015.html sigurgeirg is another user that faced this bug, and I have successfully copied his/her solution. Ideally, Ubuntu developers would check if upstream Evolution has solved this bug and would backport the solution to Ubuntu 15.10 (and possibly 14.04 and 12.04, if applicable). -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1504665 Title: Evolution fails to show Imap folder "Inbox". It only shows the unexisting grayed-out empty folder "INBOX" (all caps) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1504665/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1504665] Re: Evolution fails to show Imap folder "Inbox". It only shows the unexisting grayed-out empty folder "INBOX" (all caps)
Milan Crha (who has a Red Hat email) wrote that this is not an Evolution bug, but instead a server bug. evolution-data-server 3.18.1 and later has a workaround. https://mail.gnome.org/archives/evolution- list/2015-October/msg00059.html -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1504665 Title: Evolution fails to show Imap folder "Inbox". It only shows the unexisting grayed-out empty folder "INBOX" (all caps) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1504665/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1504665] Re: Evolution fails to show Imap folder "Inbox". It only shows the unexisting grayed-out empty folder "INBOX" (all caps)
** Description changed: - In my workplace, email is accessible via IMAP. The default mail client - is Thunderbird (Windows). Thunderbird on Ubuntu does work correctly. I + In my workplace, I access email via IMAP. The default mail client is + Thunderbird (Windows). Thunderbird on Ubuntu does work correctly. I wanted though to use Evolution. However, evolution fails to show Inbox. Instead of Inbox it shows an empty, grayed-out "INBOX" (all-caps). - This happens both on a fully updated installation of 15.04, and on a + This bug occurs both on a fully updated installation of 15.04, and on a fully updated installation of 15.10 (I installed it in a Virtualbox VM and updated it with apt). I have tried to reproduce it with Evolution 3.18, but: - - The OpenSuse live Gnome image mentioned in www.gnome.org/getting-gnome/ fails to load the X server within Virtualbox. - - In Fedora 23 Beta live (in Virtualbox), Evolution fails to connect to the IMAP server. I then tried to install Fedora 23 Beta to disk (within Virtualbox) but Anaconda crashed every time I tried. + 1. In Fedora 23 Beta live (in Virtualbox), Evolution fails to connect to the IMAP server. I then tried to install Fedora 23 Beta to disk (within Virtualbox) but Anaconda crashed every time I tried. + + 2. The OpenSuse live Gnome image mentioned in www.gnome.org/getting- + gnome/ fails to load the X server within Virtualbox. I have written it + to a pen drive and booted it, but then I was unable to access the email. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: evolution 3.16.5-1ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-15.18-generic 4.2.3 Uname: Linux 4.2.0-15-generic x86_64 ApportVersion: 2.19.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Oct 9 16:30:06 2015 InstallationDate: Installed on 2015-10-05 (4 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924) SourcePackage: evolution UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: In my workplace, I access email via IMAP. The default mail client is Thunderbird (Windows). Thunderbird on Ubuntu does work correctly. I wanted though to use Evolution. However, evolution fails to show Inbox. Instead of Inbox it shows an empty, grayed-out "INBOX" (all-caps). This bug occurs both on a fully updated installation of 15.04, and on a fully updated installation of 15.10 (I installed it in a Virtualbox VM and updated it with apt). I have tried to reproduce it with Evolution 3.18, but: 1. In Fedora 23 Beta live (in Virtualbox), Evolution fails to connect to the IMAP server. I then tried to install Fedora 23 Beta to disk (within Virtualbox) but Anaconda crashed every time I tried. 2. The OpenSuse live Gnome image mentioned in www.gnome.org/getting- - gnome/ fails to load the X server within Virtualbox. I have written it - to a pen drive and booted it, but then I was unable to access the email. + gnome/ fails to load the X server within Virtualbox. Then I wrote it to + a pen drive and booted it, but I was unable to access the email within + live Gnome. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: evolution 3.16.5-1ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-15.18-generic 4.2.3 Uname: Linux 4.2.0-15-generic x86_64 ApportVersion: 2.19.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Oct 9 16:30:06 2015 InstallationDate: Installed on 2015-10-05 (4 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924) SourcePackage: evolution UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: In my workplace, I access email via IMAP. The default mail client is Thunderbird (Windows). Thunderbird on Ubuntu does work correctly. I wanted though to use Evolution. However, evolution fails to show Inbox. Instead of Inbox it shows an empty, grayed-out "INBOX" (all-caps). This bug occurs both on a fully updated installation of 15.04, and on a fully updated installation of 15.10 (I installed it in a Virtualbox VM and updated it with apt). I have tried to reproduce it with Evolution 3.18, but: 1. In Fedora 23 Beta live (in Virtualbox), Evolution fails to connect to the IMAP server. I then tried to install Fedora 23 Beta to disk (within Virtualbox) but Anaconda crashed every time I tried. 2. The OpenSuse live Gnome image mentioned in www.gnome.org/getting- gnome/ fails to load the X server within Virtualbox. Then I wrote it to - a pen drive and booted it, but I was unable to access the email within - live Gnome. + a pen drive and booted it, but I had network problems with live Gnome. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: evolution 3.16.5-1ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-15.18-generic 4.2.3 Uname: Linux 4.2.0-15-generic x86_64 ApportVersion: 2.19.1-0ubuntu2
[Bug 1504665] Re: Evolution fails to show Imap folder "Inbox". It only shows the unexisting grayed-out empty folder "INBOX" (all caps)
** Description changed: In my workplace, I access email via IMAP. The default mail client is Thunderbird (Windows). Thunderbird on Ubuntu does work correctly. I wanted though to use Evolution. However, evolution fails to show Inbox. - Instead of Inbox it shows an empty, grayed-out "INBOX" (all-caps). + Instead of Inbox it shows an empty bogus "INBOX" (all-caps). This bug occurs both on a fully updated installation of 15.04, and on a fully updated installation of 15.10 (I installed it in a Virtualbox VM and updated it with apt). I have tried to reproduce it with Evolution 3.18, but: 1. In Fedora 23 Beta live (in Virtualbox), Evolution fails to connect to the IMAP server. I then tried to install Fedora 23 Beta to disk (within Virtualbox) but Anaconda crashed every time I tried. 2. The OpenSuse live Gnome image mentioned in www.gnome.org/getting- gnome/ fails to load the X server within Virtualbox. Then I wrote it to a pen drive and booted it, but I had network problems with live Gnome. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: evolution 3.16.5-1ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-15.18-generic 4.2.3 Uname: Linux 4.2.0-15-generic x86_64 ApportVersion: 2.19.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Oct 9 16:30:06 2015 InstallationDate: Installed on 2015-10-05 (4 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924) SourcePackage: evolution UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1504665 Title: Evolution fails to show Imap folder "Inbox". It only shows the unexisting grayed-out empty folder "INBOX" (all caps) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1504665/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1504665] [NEW] Evolution fails to show Imap folder "Inbox". It only shows the unexisting grayed-out empty folder "INBOX" (all caps)
Public bug reported: In my workplace, email is accessible via IMAP. The default mail client is Thunderbird (Windows). Thunderbird on Ubuntu does work correctly. I wanted though to use Evolution. However, evolution fails to show Inbox. Instead of Inbox it shows an empty, grayed-out "INBOX" (all-caps). This happens both on a fully updated installation of 15.04, and on a fully updated installation of 15.10 (I installed it in a Virtualbox VM and updated it with apt). I have tried to reproduce it with Evolution 3.18, but: - The OpenSuse live Gnome image mentioned in www.gnome.org/getting-gnome/ fails to load the X server within Virtualbox. - In Fedora 23 Beta live (in Virtualbox), Evolution fails to connect to the IMAP server. I then tried to install Fedora 23 Beta to disk (within Virtualbox) but Anaconda crashed every time I tried. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: evolution 3.16.5-1ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-15.18-generic 4.2.3 Uname: Linux 4.2.0-15-generic x86_64 ApportVersion: 2.19.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Oct 9 16:30:06 2015 InstallationDate: Installed on 2015-10-05 (4 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924) SourcePackage: evolution UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: evolution (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wily -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1504665 Title: Evolution fails to show Imap folder "Inbox". It only shows the unexisting grayed-out empty folder "INBOX" (all caps) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1504665/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1270579] Re: On laptops, screen brightness isn't memorized between sessions
I wrote a couple of upstart scripts to save and retore brightness between bootups. I hope the scripts are smart enough to run unmodified in any system with /sys/class/backlight. You can find them at bitbucket with install instructions: https://bitbucket.org/jjchico/upstart-brightness Quick manual: cd /etc/init sudo wget https://bitbucket.org/jjchico/upstart-brightness/raw/d9a5d9484475eb1256d56c64b28e680a7aeae72c/brightness-store.conf sudo wget https://bitbucket.org/jjchico/upstart-brightness/raw/d9a5d9484475eb1256d56c64b28e680a7aeae72c/brightness-restore.conf Test reports and patches are wellcome (these are my first upstart scripts). Enjoy! -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to a duplicate bug report (403075). https://bugs.launchpad.net/bugs/1270579 Title: On laptops, screen brightness isn't memorized between sessions To manage notifications about this bug go to: https://bugs.launchpad.net/elementaryos/+bug/1270579/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1391555] Re: Bluetooth mouse battery reported as Extra battery
Problem solved in 14.04.1 when reverted to original kernel: $ uname -a Linux jjc-xps 3.13.0-44-generic #73-Ubuntu SMP Tue Dec 16 00:22:43 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Problem happens when using updated kernel also in the repositories: Linux jjc-xps 3.16.0-29-generic #39-Ubuntu SMP Tue Dec 16 20:54:13 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux So problem may be kernel-related or upower/gnome-power-manager not understanding new kernels. Previous report was generated with 3.16.0-29-generic #39. People with 14.10 may try to boot with a 3.13 kernel and report here. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1391555 Title: Bluetooth mouse battery reported as Extra battery To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1391555/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1391555] Re: Bluetooth mouse battery reported as Extra battery
Same problem in Ubuntu 14.04 with a Dell XPS 13 9333. Extrangely, before upgrading to 14.04 from the original stock 12.04 Ubuntu version shipped with the computer, the mouse battery was reported correctly (as a mouse). Mouse is Dell Travel Mouse WM524 === # lsb_release -rd Description:Ubuntu 14.04.1 LTS Release:14.04 === # upower --dump Device: /org/freedesktop/UPower/devices/line_power_ADP0 native-path: ADP0 power supply: yes updated: mar 20 ene 2015 15:44:41 CET (1558 seconds ago) has history: no has statistics: no line-power online: yes Device: /org/freedesktop/UPower/devices/battery_BAT0 native-path: BAT0 vendor: SIMPLO model:Dell serial: 2959 power supply: yes updated: mar 20 ene 2015 16:10:20 CET (19 seconds ago) has history: yes has statistics: yes battery present: yes rechargeable:yes state: charging energy: 33,1076 Wh energy-empty:0 Wh energy-full: 55,944 Wh energy-full-design: 55,944 Wh energy-rate: 17,9894 W voltage: 8,036 V time to full:1,3 hours percentage: 59% capacity:100% technology: lithium-ion History (charge): 1421766620 59,000 charging 1443692692 80,000 discharging History (rate): 1421766620 17,989 charging 1421766590 18,100 charging 1421766560 18,256 charging 1421766530 18,271 charging 1443692698 8,939 discharging 1443692696 9,805 discharging 1443692694 17,242 discharging 1443692692 12,735 discharging Device: /org/freedesktop/UPower/devices/battery_hid_00o1fo20oe8o4co97_battery native-path: hid-00:1f:20:e8:4c:97-battery model:Dell Travel Mouse WM524 power supply: no updated: mar 20 ene 2015 16:10:33 CET (6 seconds ago) has history: yes has statistics: yes battery present: yes rechargeable:yes state: discharging energy: 0 Wh energy-empty:0 Wh energy-full: 0 Wh energy-full-design: 0 Wh energy-rate: 0 W percentage: 88% capacity:100% Daemon: daemon-version: 0.9.23 can-suspend: yes can-hibernate: yes on-battery: no on-low-battery: no lid-is-closed: no lid-is-present: yes is-docked: no === # apt-cache policy upower upower: Instalados: 0.9.23-2ubuntu1 Candidato: 0.9.23-2ubuntu1 Tabla de versión: *** 0.9.23-2ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status === # apt-cache policy gnome-power-manager gnome-power-manager: Instalados: 3.8.2-1ubuntu2 Candidato: 3.8.2-1ubuntu2 Tabla de versión: *** 3.8.2-1ubuntu2 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status === # grep . /sys/class/power_supply/*/* grep: /sys/class/power_supply/ADP0/device: Is a directory /sys/class/power_supply/ADP0/online:1 grep: /sys/class/power_supply/ADP0/power: Is a directory grep: /sys/class/power_supply/ADP0/subsystem: Is a directory /sys/class/power_supply/ADP0/type:Mains /sys/class/power_supply/ADP0/uevent:POWER_SUPPLY_NAME=ADP0 /sys/class/power_supply/ADP0/uevent:POWER_SUPPLY_ONLINE=1 /sys/class/power_supply/BAT0/alarm:0 /sys/class/power_supply/BAT0/capacity:61 /sys/class/power_supply/BAT0/capacity_level:Normal /sys/class/power_supply/BAT0/charge_full:756 /sys/class/power_supply/BAT0/charge_full_design:756 /sys/class/power_supply/BAT0/charge_now:4644000 /sys/class/power_supply/BAT0/current_now:2467000 /sys/class/power_supply/BAT0/cycle_count:0 grep: /sys/class/power_supply/BAT0/device: Is a directory /sys/class/power_supply/BAT0/manufacturer:SIMPLO /sys/class/power_supply/BAT0/model_name:Dell grep: /sys/class/power_supply/BAT0/power: Is a directory /sys/class/power_supply/BAT0/present:1 /sys/class/power_supply/BAT0/serial_number:2959 /sys/class/power_supply/BAT0/status:Charging grep: /sys/class/power_supply/BAT0/subsystem: Is a directory /sys/class/power_supply/BAT0/technology:Li-ion /sys/class/power_supply/BAT0/type:Battery /sys/class/power_supply/BAT0/uevent:POWER_SUPPLY_NAME=BAT0 /sys/class/power_supply/BAT0/uevent:POWER_SUPPLY_STATUS=Charging /sys/class/power_supply/BAT0/uevent:POWER_SUPPLY_PRESENT=1 /sys/class/power_supply/BAT0/uevent:POWER_SUPPLY_TECHNOLOGY=Li-ion /sys/class/power_supply/BAT0/uevent:POWER_SUPPLY_CYCLE_COUNT=0
[Bug 1352951] [NEW] nautilus crashed with SIGSEGV in g_slice_alloc()
Public bug reported: Nautilus crash when only download a torrent, no copying, deleting or moving files. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: nautilus 1:3.10.1-0ubuntu9.3 Uname: Linux 3.6.11 x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Aug 5 10:14:18 2014 ExecutablePath: /usr/bin/nautilus ExecutableTimestamp: 1405434801 GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' b['name', 'size', 'type', 'date_modified', 'date_accessed', 'group', 'permissions', 'octal_permissions', 'owner', 'mime_type', 'where'] InstallationDate: Installed on 2014-07-30 (5 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) ProcCmdline: nautilus -n ProcCwd: /home/joel SegvAnalysis: Segfault happened at: 0x7fa82174c297 g_slice_alloc+167: mov (%rbx),%rax PC (0x7fa82174c297) ok source (%rbx) (0x00842552) not located in a known VMA region (needed readable region)! destination %rax ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: nautilus 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 g_type_create_instance () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_newv () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: nautilus crashed with SIGSEGV in g_slice_alloc() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash need-amd64-retrace trusty ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1352951 Title: nautilus crashed with SIGSEGV in g_slice_alloc() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1352951/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1352951] Re: nautilus crashed with SIGSEGV in g_slice_alloc()
*** This bug is a duplicate of bug 1161468 *** https://bugs.launchpad.net/bugs/1161468 The bug 1161468 is private I cannot see the bug. How work in it?. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1352951 Title: nautilus crashed with SIGSEGV in g_slice_alloc() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1352951/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1350599] [NEW] file-roller crashed with SIGSEGV
Public bug reported: file-roller crashes when I extract an archive (not show bar progress) and I extract it again. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: file-roller 3.10.2.1-0ubuntu4.1 ProcVersionSignature: Ubuntu 3.5.0-51.76-generic 3.5.7.33 Uname: Linux 3.5.0-51-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Wed Jul 30 17:55:51 2014 Disassembly: = 0x7fcd9085e63b: No se puede acceder a la memoria en la dirección 0x7fcd9085e63b ExecutablePath: /usr/bin/file-roller ExecutableTimestamp: 1405437685 InstallationDate: Installed on 2014-07-30 (0 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) ProcCmdline: file-roller /home/joel/Descargas/mono-3.0.0.tar.bz2 ProcCwd: /home/joel SegvAnalysis: Segfault happened at: 0x7fcd9085e63b: No se puede acceder a la memoria en la dirección 0x7fcd9085e63b PC (0x7fcd9085e63b) ok source 0x7fcd9085e63b (0x7fcd9085e63b) ok SP (0x7fff3b896720) ok Reason could not be automatically determined. Signal: 11 SourcePackage: file-roller StacktraceTop: ?? () ?? () ?? () ?? () ?? () Title: file-roller crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo ** Affects: file-roller (Ubuntu) Importance: Undecided Status: Invalid ** Tags: amd64 apport-crash trusty ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/1350599 Title: file-roller crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1350599/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 550101] Re: Export of keys and keyrings is not available
I am affected by the problem on 14.04. The export menu entry seems available for my OpenSSH key, but it is greyed out when I select a password keyring. I want to export my passwords to Keepass2, so I could synchronize with my Android smartphone. Should this bug be filed upstream? In that case, would it be better to wait for the Ubuntu Seahorse mantainer to file it, or should I file it myself? Regards -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to seahorse in Ubuntu. https://bugs.launchpad.net/bugs/550101 Title: Export of keys and keyrings is not available To manage notifications about this bug go to: https://bugs.launchpad.net/seahorse/+bug/550101/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1315449] [NEW] package gnome-settings-daemon-schemas (not installed) failed to install/upgrade: intentando sobreescribir `/usr/share/GConf/gsettings/gnome-settings-daemon.convert', que está tambi
Public bug reported: After upgrading to ubuntu 14.04 from 13.10 no display appears at start I ran recover mode from grub Now Desktop appears but report errors ProblemType: Package DistroRelease: Ubuntu 14.04 Package: gnome-settings-daemon-schemas (not installed) ProcVersionSignature: Ubuntu 3.11.0-20.34-generic 3.11.10.6 Uname: Linux 3.11.0-20-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Fri May 2 10:43:46 2014 DuplicateSignature: package:gnome-settings-daemon-schemas:(not installed):intentando sobreescribir `/usr/share/GConf/gsettings/gnome-settings-daemon.convert', que está también en el paquete gnome-settings-daemon 3.10.2-0ubuntu1~saucy1 ErrorMessage: intentando sobreescribir `/usr/share/GConf/gsettings/gnome-settings-daemon.convert', que está también en el paquete gnome-settings-daemon 3.10.2-0ubuntu1~saucy1 MarkForUpload: True SourcePackage: gnome-settings-daemon Title: package gnome-settings-daemon-schemas (not installed) failed to install/upgrade: intentando sobreescribir `/usr/share/GConf/gsettings/gnome-settings-daemon.convert', que está también en el paquete gnome-settings-daemon 3.10.2-0ubuntu1~saucy1 UpgradeStatus: Upgraded to trusty on 2014-05-01 (1 days ago) ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package trusty -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1315449 Title: package gnome-settings-daemon-schemas (not installed) failed to install/upgrade: intentando sobreescribir `/usr/share/GConf/gsettings /gnome-settings-daemon.convert', que está también en el paquete gnome- settings-daemon 3.10.2-0ubuntu1~saucy1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1315449/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1313430] Re: Crashes on Ubuntu 14.04 when trying to connect to iPod
Same problem here. I can add that this problem exists in my installation indeed before to upgrade to 14.04. jtome@revo:~$ rhythmbox (rhythmbox:18119): Gtk-CRITICAL **: gtk_css_provider_load_from_path: assertion 'path != NULL' failed g_dbus_connection_real_closed: Remote peer vanished with error: Error receiving message: Connection reset by peer (g-io-error-quark, 0). Exiting. Violación de segmento (`core' generado) jtome@revo:~$ dpkg -l |grep rhythmbox ii gir1.2-rb-3.0 3.0.2-0ubuntu1 i386 GObject introspection data for the rhythmbox music player rc librhythmbox-core52.96-0ubuntu4.2 i386 support library for the rhythmbox music player rc librhythmbox-core62.98-0ubuntu5 i386 support library for the rhythmbox music player rc librhythmbox-core72.99.1-0ubuntu1 i386 support library for the rhythmbox music player ii librhythmbox-core83.0.2-0ubuntu1 i386 support library for the rhythmbox music player ii rhythmbox 3.0.2-0ubuntu1 i386 music player and organizer for GNOME ii rhythmbox-data3.0.2-0ubuntu1 all data files for rhythmbox ii rhythmbox-mozilla 3.0.2-0ubuntu1 i386 Rhythmbox Mozilla plugin ii rhythmbox-plugin-cdrecorder 3.0.2-0ubuntu1 i386 burning plugin for rhythmbox music player ii rhythmbox-plugin-magnatune3.0.2-0ubuntu1 i386 Magnatune plugin for rhythmbox music player ii rhythmbox-plugin-zeitgeist3.0.2-0ubuntu1 all zeitgeist plugin for rhythmbox music player ii rhythmbox-plugins 3.0.2-0ubuntu1 i386 plugins for rhythmbox music player jtome@revo:~$ ldd -r /usr/lib/librhythmbox-core.so.8 linux-gate.so.1 = (0xb77a4000) libm.so.6 = /lib/i386-linux-gnu/libm.so.6 (0xb75f6000) libtotem-plparser.so.18 = /usr/lib/libtotem-plparser.so.18 (0xb75d8000) libgudev-1.0.so.0 = /usr/lib/i386-linux-gnu/libgudev-1.0.so.0 (0xb75cc000) libwebkitgtk-3.0.so.0 = /usr/lib/i386-linux-gnu/libwebkitgtk-3.0.so.0 (0xb58c2000) libsoup-2.4.so.1 = /usr/lib/i386-linux-gnu/libsoup-2.4.so.1 (0xb5826000) libpeas-gtk-1.0.so.0 = /usr/lib/libpeas-gtk-1.0.so.0 (0xb5818000) libgtk-3.so.0 = /usr/lib/i386-linux-gnu/libgtk-3.so.0 (0xb52ca000) libpeas-1.0.so.0 = /usr/lib/libpeas-1.0.so.0 (0xb52b5000) libgdk-3.so.0 = /usr/lib/i386-linux-gnu/libgdk-3.so.0 (0xb521) libatk-1.0.so.0 = /usr/lib/i386-linux-gnu/libatk-1.0.so.0 (0xb51ef000) libpangocairo-1.0.so.0 = /usr/lib/i386-linux-gnu/libpangocairo-1.0.so.0 (0xb51e2000) libgdk_pixbuf-2.0.so.0 = /usr/lib/i386-linux-gnu/libgdk_pixbuf-2.0.so.0 (0xb51bf000) libpango-1.0.so.0 = /usr/lib/i386-linux-gnu/libpango-1.0.so.0 (0xb5171000) libcairo.so.2 = /usr/lib/i386-linux-gnu/libcairo.so.2 (0xb504e000) libgirepository-1.0.so.1 = /usr/lib/libgirepository-1.0.so.1 (0xb5017000) libxml2.so.2 = /usr/lib/i386-linux-gnu/libxml2.so.2 (0xb4ebd000) libtdb.so.1 = /usr/lib/i386-linux-gnu/libtdb.so.1 (0xb4ea9000) libjson-glib-1.0.so.0 = /usr/lib/i386-linux-gnu/libjson-glib-1.0.so.0 (0xb4e83000) libgio-2.0.so.0 = /usr/lib/i386-linux-gnu/libgio-2.0.so.0 (0xb4d02000) libgstaudio-1.0.so.0 = /usr/lib/i386-linux-gnu/libgstaudio-1.0.so.0 (0xb4cb) libgstbase-1.0.so.0 = /usr/lib/i386-linux-gnu/libgstbase-1.0.so.0 (0xb4c4c000) libgstreamer-1.0.so.0 = /usr/lib/i386-linux-gnu/libgstreamer-1.0.so.0 (0xb4b49000) libgobject-2.0.so.0 = /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 (0xb4af6000) libglib-2.0.so.0 = /lib/i386-linux-gnu/libglib-2.0.so.0 (0xb49ea000) libgstpbutils-1.0.so.0 = /usr/lib/i386-linux-gnu/libgstpbutils-1.0.so.0 (0xb49c5000) libgstcontroller-1.0.so.0 = /usr/lib/i386-linux-gnu/libgstcontroller-1.0.so.0 (0xb49b4000) libgsttag-1.0.so.0 = /usr/lib/i386-linux-gnu/libgsttag-1.0.so.0 (0xb497c000) libpthread.so.0 = /lib/i386-linux-gnu/libpthread.so.0 (0xb495f000) libc.so.6 = /lib/i386-linux-gnu/libc.so.6 (0xb47b) /lib/ld-linux.so.2 (0xb77a5000) libgmime-2.6.so.0 =
[Bug 1313430] Re: Crashes on Ubuntu 14.04 when trying to connect to iPod
@bizauionica Version is `rhythmbox 3.0.2-0ubuntu1` but this problem is present (at last in all my computers) since previous distributions and has never been solved :-( My iPod Classic is totally usefulness if I cannot synchronize it. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1313430 Title: Crashes on Ubuntu 14.04 when trying to connect to iPod To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1313430/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1311911] Re: Append remote hostname to gnome-terminal title by default
So we do this ootb on a pristine install -- in g-t I was setting Keep title instead of append, which would mean I set it to not show anything in there but Terminal. This is invalid, sorry for the bugspam. ** Changed in: bash (Ubuntu) Status: Confirmed = Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1311911 Title: Append remote hostname to gnome-terminal title by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1311911/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1170647] Re: Clicking on Nautilus’ launcher icon opens new window instead of restoring the minimized one when browsing external drives/locations
I can also confirm this is happening on 14.04 x64 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1170647 Title: Clicking on Nautilus’ launcher icon opens new window instead of restoring the minimized one when browsing external drives/locations To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bamf/+bug/1170647/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1311911] [NEW] Append remote hostname to gnome-terminal title by default
Public bug reported: The window matching in 14.04 is perfect for finding windows you think you've lost. Sysadmins usually use a bunch of terminals, it would be cool if Super-W then typing in a remote hostname would Just Work with Unity's spread and searching. To do this we need to set gnome-terminal's title when a person ssh'es to a machine to have something like jorge@remotehost in the title. This would allow the spread to search for those windows. See also: http://unix.stackexchange.com/questions/14113/is-it-possible- to-set-gnome-terminals-title-to-userhost-for-whatever-host-i ** Affects: bash (Ubuntu) Importance: Wishlist Status: New ** Affects: gnome-terminal (Ubuntu) Importance: Wishlist Status: New ** Also affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-terminal (Ubuntu) Importance: Undecided = Wishlist ** Description changed: The window matching in 14.04 is perfect for finding windows you think you've lost. Sysadmins usually use a bunch of terminals, it would be cool if Super-W then typing in a remote hostname would Just Work with Unity's spread and searching. To do this we need to set gnome-terminal's title when a person ssh'es to a machine to have something like jorge@remotehost in the title. This would allow the spread to search for those windows. + + See also: http://unix.stackexchange.com/questions/14113/is-it-possible- + to-set-gnome-terminals-title-to-userhost-for-whatever-host-i -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1311911 Title: Append remote hostname to gnome-terminal title by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1311911/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1250675] [NEW] [clipboard]: gnome-settings-daemon crashed with signal 5 in _XReply()
*** This bug is a duplicate of bug 946059 *** https://bugs.launchpad.net/bugs/946059 Public bug reported: gnome-settings-daemon crashed and gtk-window-decorator hidden close button and window's title. It can't restore by itself, must be killed and restart manually. ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: gnome-settings-daemon 3.4.2-0ubuntu15 ProcVersionSignature: Ubuntu 3.5.0-42.65-generic 3.5.7.21 Uname: Linux 3.5.0-42-generic x86_64 ApportVersion: 2.6.1-0ubuntu13 Architecture: amd64 Date: Tue Nov 12 17:39:49 2013 ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon InstallationDate: Installed on 2013-07-18 (117 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon Signal: 5 SourcePackage: gnome-settings-daemon StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XGetWindowAttributes () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XGetWindowAttributes () from /usr/lib/x86_64-linux-gnu/libX11.so.6 Title: [clipboard]: gnome-settings-daemon crashed with signal 5 in _XReply() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev sambashare scanner sudo tape vboxusers video wireshark ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash clipboard quantal third-party-packages ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1250675 Title: [clipboard]: gnome-settings-daemon crashed with signal 5 in _XReply() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1250675/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1215090] [NEW] gvfsd-obexftp crashed with SIGABRT in __libc_message()
Public bug reported: When I connect my Android phone to PC Bluetooth and I want to browse my sdcard, gvfsd-obexftp fail instantly. ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: gvfs-backends 1.14.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.5.0-37.58-generic 3.5.7.16 Uname: Linux 3.5.0-37-generic x86_64 ApportVersion: 2.6.1-0ubuntu12 Architecture: amd64 CrashCounter: 1 Date: Wed Aug 21 13:09:23 2013 ExecutablePath: /usr/lib/gvfs/gvfsd-obexftp ExecutableTimestamp: 1349728911 InstallationDate: Installed on 2013-07-18 (34 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True ProcCmdline: /usr/lib/gvfs/gvfsd-obexftp --spawner :1.7 /org/gtk/gvfs/exec_spaw/3 ProcCwd: / Signal: 6 SourcePackage: gvfs StacktraceTop: raise () from /lib/x86_64-linux-gnu/libc.so.6 abort () from /lib/x86_64-linux-gnu/libc.so.6 ?? () from /lib/x86_64-linux-gnu/libc.so.6 ?? () from /lib/x86_64-linux-gnu/libc.so.6 ?? () Title: gvfsd-obexftp crashed with SIGABRT in raise() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo ** Affects: gvfs (Ubuntu) Importance: Medium Status: New ** Tags: amd64 apport-crash quantal ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1215090 Title: gvfsd-obexftp crashed with SIGABRT in __libc_message() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1215090/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1175547] Re: photo viewer closes by itself when opening picture
Seems related/equal as https://bugs.launchpad.net/ubuntu/+source/gthumb/+bug/1179525 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/1175547 Title: photo viewer closes by itself when opening picture To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1175547/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1175547] Re: photo viewer closes by itself when opening picture
Seems related/equal https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/1179735 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/1175547 Title: photo viewer closes by itself when opening picture To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1175547/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1175547] Re: photo viewer closes by itself when opening picture
Reported fixed in: http://cgit.freedesktop.org/cairo/commit/src/cairo-mempool.c?id=01a8bf01c6508a4fea8d40371c3049e7a2f7908a -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/1175547 Title: photo viewer closes by itself when opening picture To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1175547/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1175547] Re: photo viewer closes by itself when opening picture
Same here, Ubuntu 12.04.2 LTS, kernel 3.2.0-48-generic-pae $ eog IMG_1673.JPG eog: /build/buildd/cairo-1.12.14/src/cairo-mempool.c:160: get_buddy: Assertion `offset + (1 bits) = pool-num_blocks' failed. eog 3.4.2-0ubuntu1.1 libcairo2 1.12.14-0ubuntu1~precise1 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/1175547 Title: photo viewer closes by itself when opening picture To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1175547/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1072817] Re: msn chat will not connect
Where can I locate the requested log file? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/1072817 Title: msn chat will not connect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1072817/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1072817] Re: msn chat will not connect
Attached empathy log. ** Attachment added: empathy.log https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1072817/+attachment/3418541/+files/empathy.log -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/1072817 Title: msn chat will not connect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1072817/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1072817] [NEW] msn chat will not connect
Public bug reported: At my workplace I keep getting a network error in empathy when I try to connect my MSN Account. However if I try Pidgin or Windows Live Messenger they work properly. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: empathy 3.6.0.3-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu6 Architecture: i386 Date: Mon Oct 29 17:18:15 2012 InstallationDate: Installed on 2011-09-21 (403 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: empathy UpgradeStatus: Upgraded to quantal on 2012-07-28 (93 days ago) ** Affects: empathy (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 quantal running-unity -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/1072817 Title: msn chat will not connect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1072817/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 727877] Re: Evolution no deja enviar mensajes
How i resolve this bug? can some one help me? thanks -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/727877 Title: Evolution no deja enviar mensajes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/727877/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 727877] Re: Evolution no deja enviar mensajes
this is the message in spanish The reported error was Error en la respuesta de bienvenida: Conexión reinicializada por la máquina remota -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/727877 Title: Evolution no deja enviar mensajes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/727877/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1054363] Re: Shotwell crashes while importing collection
Here you are :) ** Attachment added: shotwell.gdb https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1054363/+attachment/3343220/+files/shotwell.gdb -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shotwell in Ubuntu. https://bugs.launchpad.net/bugs/1054363 Title: Shotwell crashes while importing collection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1054363/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1054363] Re: Shotwell crashes while importing collection
** Attachment added: ~/.cache/shotwell/shotwell.log https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1054363/+attachment/3343221/+files/shotwell.log -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shotwell in Ubuntu. https://bugs.launchpad.net/bugs/1054363 Title: Shotwell crashes while importing collection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1054363/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1054363] Re: Shotwell crashes while importing collection
(gdb) backtrace full #0 0x7fff9576583b in dca_syncinfo () from /usr/lib/libdca.so.0 No symbol table info available. #1 0x7fff9598cb7b in ?? () from /usr/lib/x86_64-linux-gnu/gstreamer-0.10/libgstdtsdec.so No symbol table info available. #2 0x7fff975dc0fc in ?? () from /usr/lib/x86_64-linux-gnu/libgstaudio-0.10.so.0 No symbol table info available. #3 0x7fff975dc5c0 in ?? () from /usr/lib/x86_64-linux-gnu/libgstaudio-0.10.so.0 No symbol table info available. #4 0x7fff975dd37b in ?? () from /usr/lib/x86_64-linux-gnu/libgstaudio-0.10.so.0 No symbol table info available. #5 0x7fff9598bc97 in ?? () from /usr/lib/x86_64-linux-gnu/gstreamer-0.10/libgstdtsdec.so No symbol table info available. #6 0x7770b22a in ?? () from /usr/lib/x86_64-linux-gnu/libgstreamer-0.10.so.0 No symbol table info available. #7 0x7770eae6 in gst_pad_push () from /usr/lib/x86_64-linux-gnu/libgstreamer-0.10.so.0 No symbol table info available. #8 0x7fffce08a536 in ?? () from /usr/lib/x86_64-linux-gnu/gstreamer-0.10/libgstcoreelements.so No symbol table info available. #9 0x77734dcc in ?? () from /usr/lib/x86_64-linux-gnu/libgstreamer-0.10.so.0 No symbol table info available. #10 0x7410c248 in g_thread_pool_thread_proxy (data=optimised out) at /build/buildd/glib2.0-2.32.3/./glib/gthreadpool.c:309 task = 0x7fff88014f90 pool = 0x15e9670 #11 0x7410b9e5 in g_thread_proxy (data=0x31a60f0) at /build/buildd/glib2.0-2.32.3/./glib/gthread.c:801 thread = 0x31a60f0 #12 0x739eee9a in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 No symbol table info available. #13 0x7371c4bd in clone () from /lib/x86_64-linux-gnu/libc.so.6 No symbol table info available. #14 0x in ?? () No symbol table info available. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shotwell in Ubuntu. https://bugs.launchpad.net/bugs/1054363 Title: Shotwell crashes while importing collection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1054363/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1054363] [NEW] Shotwell crashes while importing collection
Public bug reported: 1, Open Shotwell. 2, It starts importing my collection. 3, It crashes. No need to do any single action. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: shotwell 0.12.3-0ubuntu0.1 ProcVersionSignature: Ubuntu 3.2.0-30.48-generic 3.2.27 Uname: Linux 3.2.0-30-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.0.1-0ubuntu13 Architecture: amd64 Date: Fri Sep 21 23:20:09 2012 InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120823.1) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: shotwell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: shotwell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise running-unity -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shotwell in Ubuntu. https://bugs.launchpad.net/bugs/1054363 Title: Shotwell crashes while importing collection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1054363/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1054363] Re: Shotwell crashes while importing collection
-- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shotwell in Ubuntu. https://bugs.launchpad.net/bugs/1054363 Title: Shotwell crashes while importing collection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1054363/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 971353] Re: power : gnome-settings-daemon crashed with SIGSEGV in gnome_rr_screen_get_dpms_mode
Subscribed.. It happens with my system AMD Phenom II X4 945 2X2GB DDR III 1333mhz Asus M4A785TD-M Evo Gigabyte HD 7850 OC version Software: Ubuntu 12.04, Kernel 3.2.0.20, 32bits/64bits (problem happens in both) When I start Ubuntu its all ok I open firefox, go to youtube, play a video, and firefox crash Close session, ubuntu crash, the login screen appears to choose the user, but i cant do anything. Anything that may use some 3d acceleration like changing workspace, crashes This is a very serious problem, since i need to use windows to work in my desktop Thanks -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/971353 Title: power : gnome-settings-daemon crashed with SIGSEGV in gnome_rr_screen_get_dpms_mode To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/971353/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1014558] Re: MSN Account Offline Error
Configure the MSN Account in Empathy. Reboot Launch empathy through dash Empathy says my accounts are disabled Go to account manager and see MSN account is ON but status says Offline - Status set to Offline Re-enable account and it connects properly and shows my contacts in empathy main window -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/1014558 Title: MSN Account Offline Error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1014558/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1017864] Re: empathy msn fake offline
Configure the MSN Account in Empathy. Reboot Launch empathy through dash Empathy says my accounts are disabled Go to account manager and see MSN account is ON but status says Offline - Status set to Offline Re-enable account and it connects properly and says I am online. Other people can see me but empathy main window will not show my contacts Quit empathy Launch empathy through dash and it will show I am available and displays my contacts properly. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/1017864 Title: empathy msn fake offline To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1017864/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1017864] Re: empathy msn fake offline
After updating my ubuntu to the quantal alpha release this issue has not resurfaced. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/1017864 Title: empathy msn fake offline To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1017864/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1014558] Re: MSN Account Offline Error
After updating my ubuntu to the quantal alpha release this error has not resurfaced. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/1014558 Title: MSN Account Offline Error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1014558/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 787039] Re: Python 3 Doc not show in Devhelp
But it works for me, I have installed python3.2-doc and python2.7-doc packages, changed the tag name in their DevHelp Book Description solve the problem. A example: the gtkmm documentation packages (2.4 and 3.0) difference the DevHelp Book Description using gtkmm-2.4 and gtkmm-3.0 in attribute name in the tag book. The python documentation packages must do the same. Is possible use Python2.7 and Python3.2, this can help if has installed more than one the same major version: 2.* or 3.* versions. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to devhelp in Ubuntu. https://bugs.launchpad.net/bugs/787039 Title: Python 3 Doc not show in Devhelp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/devhelp/+bug/787039/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 787039] Re: Python 3 Doc not show in Devhelp
The problem is in tag name in python3.2.devhelp.gz and python2.7.devhelp.gz, this is the same: Python; and DevHelp use the major version (this case python3-doc). A solution is change the tag name to: Python2 and Python3 respectively. ** Changed in: devhelp (Ubuntu) Status: Expired = Incomplete ** Changed in: devhelp (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to devhelp in Ubuntu. https://bugs.launchpad.net/bugs/787039 Title: Python 3 Doc not show in Devhelp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/devhelp/+bug/787039/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 787039] Re: Python 3 Doc not show in Devhelp
This problem is in python3.2-dev and python2.7-doc DevHelp Book File (.devhelp.gz) ** Also affects: python2.7 (Ubuntu) Importance: Undecided Status: New ** Also affects: python3.2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to devhelp in Ubuntu. https://bugs.launchpad.net/bugs/787039 Title: Python 3 Doc not show in Devhelp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/devhelp/+bug/787039/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 787039] Re: Python 3 Doc not show in Devhelp
** Tags added: precise -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to devhelp in Ubuntu. https://bugs.launchpad.net/bugs/787039 Title: Python 3 Doc not show in Devhelp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/devhelp/+bug/787039/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1014558] Re: MSN Account Offline Error
Where can I find this log file? Is it the one from empathy mission control? If so I already attached it. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/1014558 Title: MSN Account Offline Error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1014558/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1027618] Re: Stale Gedit syntax file for golang
** Changed in: gedit (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1027618 Title: Stale Gedit syntax file for golang To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1027618/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1017864] Re: empathy msn fake offline
As requested ** Attachment added: All-27-06-12_09-46-39.log https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1017864/+attachment/3205414/+files/All-27-06-12_09-46-39.log -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/1017864 Title: empathy msn fake offline To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1017864/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1014558] Re: MSN Account Offline Error
This issue as resurfaced. I am adding the log from mission control. ** Attachment added: All-27-06-12_09-46-39.log https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1014558/+attachment/3205415/+files/All-27-06-12_09-46-39.log -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/1014558 Title: MSN Account Offline Error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1014558/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1017864] [NEW] empathy msn fake offline
Public bug reported: Empathy main window claims my accounts are all disabled when it starts (automatically launching at startup). When I check the Account status (F4) it clearly shows MSN trying to connect and it succeeds. However the main window stil claims my accounts are disabled. If I quit Empathy and relaunch my MSN contacts are instantly displayed. I am creating this separate issue as recommended by Bilal Shahid in https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1014558 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: empathy 3.4.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-25.40-generic-pae 3.2.18 Uname: Linux 3.2.0-25-generic-pae i686 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu8 Architecture: i386 Date: Tue Jun 26 09:44:14 2012 InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: empathy UpgradeStatus: Upgraded to precise on 2012-03-21 (96 days ago) ** Affects: empathy (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 precise -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/1017864 Title: empathy msn fake offline To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1017864/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1017864] Re: empathy msn fake offline
-- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/1017864 Title: empathy msn fake offline To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1017864/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1014558] Re: MSN Account Offline Error
Separate bug report created as requested https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1017864 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/1014558 Title: MSN Account Offline Error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1014558/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1014558] Re: MSN Account Offline Error
Ok, I'll try to clarify. I have Empathy running on startup. Each time it started my MSN account status would be: Offline - Status set to Offline. I would then disable it and then re-enable on the Account status window ( F4) and the it would be set to Available and my MSN contacts would be displayed. Now I am showing a different issue (same equipment): Empathy main window claims my accounts are all disabled. When I check the Account status (F4) it clearly shows MSN trying to connect and it succeeds. However the main window stil claims my accounts are disabled. If I quit Empathy and relaunch my MSN contacts are instantly displayed. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/1014558 Title: MSN Account Offline Error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1014558/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1014558] [NEW] MSN Account Offline Error
Public bug reported: Hello, I have two PCs with the Empathy configured to my MSN Chat account. When I start Empathy, launching automatically at login, my MSN account almost always claims that is Offline. If I disable the account and re-enable it it starts working properly. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: empathy 3.4.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-25.40-generic-pae 3.2.18 Uname: Linux 3.2.0-25-generic-pae i686 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu8 Architecture: i386 Date: Mon Jun 18 10:24:11 2012 InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: empathy UpgradeStatus: Upgraded to precise on 2012-03-21 (88 days ago) ** Affects: empathy (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 precise -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/1014558 Title: MSN Account Offline Error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1014558/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1014558] Re: MSN Account Offline Error
-- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/1014558 Title: MSN Account Offline Error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1014558/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1014558] Re: MSN Account Offline Error
Problem persists after purging. Directory ~/.gnome/Empathy does not exist -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/1014558 Title: MSN Account Offline Error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1014558/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1014558] Re: MSN Account Offline Error
Sorry I meant ./gnome2/Empathy does not exist -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/1014558 Title: MSN Account Offline Error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1014558/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 966556] Re: Share Desktop with Empathy need before to go to Share your Desktop
** Also affects: empathy via https://bugzilla.gnome.org/show_bug.cgi?id=651960 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/966556 Title: Share Desktop with Empathy need before to go to Share your Desktop To manage notifications about this bug go to: https://bugs.launchpad.net/empathy/+bug/966556/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 966556] Re: Share Desktop with Empathy need before to go to Share your Desktop
** Changed in: empathy (Ubuntu) Assignee: (unassigned) = Ken VanDine (ken-vandine) ** Also affects: empathy (Ubuntu Precise) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/966556 Title: Share Desktop with Empathy need before to go to Share your Desktop To manage notifications about this bug go to: https://bugs.launchpad.net/empathy/+bug/966556/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 721416] Re: Rhythmbox does not show album art
Similar problem: either Rhytmbox does not display the cover, or does not display the right cover -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/721416 Title: Rhythmbox does not show album art To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/721416/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 985835] Re: qBittorrent closes after create a torrent.
-- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/985835 Title: qBittorrent closes after create a torrent. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/985835/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 985835] [NEW] qBittorrent closes after create a torrent.
Public bug reported: I have created a new torrent and, just finish, program closes. I have tried it a few times and always happens, but the torrent is ok. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: nautilus 1:3.2.1-0ubuntu4.2 ProcVersionSignature: Ubuntu 3.0.0-17.30-generic-pae 3.0.22 Uname: Linux 3.0.0-17-generic-pae i686 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu4 Architecture: i386 Date: Thu Apr 19 21:11:02 2012 ExecutablePath: /usr/bin/nautilus InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111012) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) XsessionErrors: (gnome-settings-daemon:1474): Gdk-WARNING **: The program 'gnome-settings-daemon' received an X Window System error. (firefox:1877): Gtk-WARNING **: Unable to retrieve the file info for `file:///home/libero/Documentos/SpanishDesigningTheFutureEBook.pdf': Error al mostrar la información del estado del archivo «/home/libero/Documentos/SpanishDesigningTheFutureEBook.pdf»: No existe el archivo o el directorio (firefox:1877): Gtk-WARNING **: Unable to retrieve the file info for `file:///home/libero/Descargas/Paradise_or_Oblivion_28_language_subtitles_-_YouTube.flv': Error al mostrar la información del estado del archivo «/home/libero/Descargas/Paradise_or_Oblivion_28_language_subtitles_-_YouTube.flv»: No existe el archivo o el directorio (qbittorrent:2199): Gtk-WARNING **: Unable to retrieve the file info for `file:///home/libero/Descargas/qBittorrent/torrents/Aseptik%20Noise%20-%20Live%20Larrazpi%202012': Error al mostrar la información del estado del archivo «/home/libero/Descargas/qBittorrent/torrents/Aseptik Noise - Live Larrazpi 2012»: No existe el archivo o el directorio (qbittorrent:2530): Gtk-WARNING **: Unable to retrieve the file info for `file:///home/libero/Descargas/qBittorrent/torrents/Aseptik%20Noise%20-%20Live%20Larrazpi%202012': Error al mostrar la información del estado del archivo «/home/libero/Descargas/qBittorrent/torrents/Aseptik Noise - Live Larrazpi 2012»: No existe el archivo o el directorio ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug apport-lpi i386 oneiric running-unity -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/985835 Title: qBittorrent closes after create a torrent. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/985835/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 965351] Re: xchat-gnome crashed with SIGSEGV in gtk_clipboard_set_with_data()
** Visibility changed to: Public -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to xchat-gnome in Ubuntu. https://bugs.launchpad.net/bugs/965351 Title: xchat-gnome crashed with SIGSEGV in gtk_clipboard_set_with_data() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xchat-gnome/+bug/965351/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 963578] [NEW] gnome-panel crashed with SIGSEGV in g_signal_emit_valist()
Private bug reported: After upgrade from 11.10, on 23-Mar-2012. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: gnome-panel 1:3.3.92-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 1.95-0ubuntu1 Architecture: amd64 Date: Fri Mar 23 18:54:02 2012 ExecutablePath: /usr/bin/gnome-panel InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) ProcCmdline: gnome-panel ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, user) LANG=pt_BR.UTF-8 SHELL=/bin/bash SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-panel Title: gnome-panel crashed with SIGSEGV in g_signal_emit_valist() UpgradeStatus: Upgraded to precise on 2012-03-23 (0 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare ** Affects: gnome-panel (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash need-amd64-retrace precise -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-panel in Ubuntu. https://bugs.launchpad.net/bugs/963578 Title: gnome-panel crashed with SIGSEGV in g_signal_emit_valist() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/963578/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 652331] Re: terminal window super hard to resize
*** This bug is a duplicate of bug 878198 *** https://bugs.launchpad.net/bugs/878198 ** This bug is no longer a duplicate of bug 160311 Resizing windows by grabbing window borders is difficult ** This bug has been marked a duplicate of bug 878198 Difficult to grab window borders in unity-2d -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/652331 Title: terminal window super hard to resize To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/652331/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 827414] Re: gedit fails to start on first try, but does on the second
Gerry, I had this problem in 11.10 (comment #30), but I just installed Precise Beta 1 and can't reproduce anymore too. Seems to be fixed. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/827414 Title: gedit fails to start on first try, but does on the second To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/827414/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 827414] Re: gedit fails to start on first try, but does on the second
About comment #36: in both cases i ran unity-2d. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/827414 Title: gedit fails to start on first try, but does on the second To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/827414/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
