[Bug 2028044] [NEW] package xrdp 0.9.21.1-1 failed to install/upgrade: installed xrdp package post-installation script subprocess returned error exit status 126
Public bug reported: I suspect this bug happened when attempting to install XRDP on an Raspberry Pi 4 Model B (8GB RAM) via APT while I was also imaging Ubuntu 23.04 using the RPI Imager app. I think potential resource exhaustion caused the error configuring XRDP ProblemType: Package DistroRelease: Ubuntu 23.04 Package: xrdp 0.9.21.1-1 ProcVersionSignature: Ubuntu 6.2.0-1004.5-raspi 6.2.6 Uname: Linux 6.2.0-1004-raspi aarch64 ApportVersion: 2.26.1-0ubuntu2 Architecture: arm64 CasperMD5CheckResult: unknown Date: Mon Jul 17 18:12:10 2023 ErrorMessage: installed xrdp package post-installation script subprocess returned error exit status 126 ImageMediaBuild: 20230417 Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.21ubuntu1 apt 2.6.0 SourcePackage: xrdp Title: package xrdp 0.9.21.1-1 failed to install/upgrade: installed xrdp package post-installation script subprocess returned error exit status 126 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xrdp (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package arm64 arm64-image lunar raspi-image -- 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/2028044 Title: package xrdp 0.9.21.1-1 failed to install/upgrade: installed xrdp package post-installation script subprocess returned error exit status 126 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xrdp/+bug/2028044/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873295] [NEW] Updated 04-16-2000 and system-monitor shell extension broke
Public bug reported: I updated my 20.04 beta box to on 16 Apr 2020 and the system-monitor applet stopped working. Going to https://extensions.gnome.org/extension/120/system-monitor/ shows error. I removed and tried readding with same result. When adding back the /var/log/syslog shows: Apr 16 11:07:58 x1 gnome-shell[1892]: [System monitor] applet init from /home/pgraner/.local/share/gnome-shell/extensions/system-moni...@paradoxxx.zero.gmail.com Apr 16 11:07:58 x1 gnome-shell[1892]: [System monitor] applet enabling Apr 16 11:07:58 x1 gnome-shell[1892]: JS ERROR: Extension system-moni...@paradoxxx.zero.gmail.com: Error: Tried to construct an object without a GType; are you using GObject.registerClass() when inheriting from a GObject type?#012SystemMonitor_TipItem@/home/pgraner/.local/share/gnome-shell/extensions/system-moni...@paradoxxx.zero.gmail.com/extension.js:640:9#012tip_format@/home/pgraner/.local/share/gnome-shell/extensions/system-moni...@paradoxxx.zero.gmail.com/extension.js:898:27#012SystemMonitor_Cpu@/home/pgraner/.local/share/gnome-shell/extensions/system-moni...@paradoxxx.zero.gmail.com/extension.js:1196:14#012createCpus@/home/pgraner/.local/share/gnome-shell/extensions/system-moni...@paradoxxx.zero.gmail.com/extension.js:1363:20#012enable@/home/pgraner/.local/share/gnome-shell/extensions/system-moni...@paradoxxx.zero.gmail.com/extension.js:2316:26#012_callExtensionEnable@resource:///org/gnome/shell/ui/extensionSystem.js:166:32#012loadExtension@resource:///org/gnome/shell/ui/extensionSystem.js:336:26#012callback@resource:///org/gnome/shell/ui/extensionDownloader.js:232:39#012gotExtensionZipFile/<@resource:///org/gnome/shell/ui/extensionDownloader.js:115:13 Apr 16 11:08:00 x1 gnome-shell[1892]: JS ERROR: TypeError: this.tip_labels[i] is undefined#012update@/home/pgraner/.local/share/gnome-shell/extensions/system-moni...@paradoxxx.zero.gmail.com/extension.js:925:56 Nothing I've done can get it working. Googleing hasn't revealed anything useful. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 16 11:11:22 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-01-25 (82 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- 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/1873295 Title: Updated 04-16-2000 and system-monitor shell extension broke To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1873295/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1861940] [NEW] gimp crashed while editing an image
Public bug reported:
```
GNU Image Manipulation Program version 2.10.14
git-describe: GIMP_2_10_12-511-ga4f55d6c7e
C compiler:
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/9/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none:hsa
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu
9.2.1-9ubuntu2' --with-bugurl=file:///usr/share/doc/gcc-9/README.Bugs
--enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++,gm2 --prefix=/usr
--with-gcc-major-version-only --program-suffix=-9
--program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix
--libdir=/usr/lib --enable-nls --enable-bootstrap --enable-clocale=gnu
--enable-libstdcxx-debug --enable-libstdcxx-time=yes
--with-default-libstdcxx-abi=new --enable-gnu-unique-object
--disable-vtable-verify --enable-plugin --enable-default-pie --with-system-zlib
--with-target-system-zlib=auto --enable-multiarch --disable-werror
--with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32
--enable-multilib --with-tune=generic --enable-offload-targets=nvptx-none,hsa
--without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu
--host=x86_64-linux-gnu --target=x86_64-linux-gnu
Thread model: posix
gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2)
using babl version 0.1.72 (compiled against version 0.1.72)
using GEGL version 0.4.18 (compiled against version 0.4.18)
using GLib version 2.62.1 (compiled against version 2.62.1)
using GdkPixbuf version 2.40.0 (compiled against version 2.40.0)
using GTK+ version 2.24.32 (compiled against version 2.24.32)
using Pango version 1.42.3 (compiled against version 1.42.3)
using Fontconfig version 2.13.1 (compiled against version 2.13.1)
using Cairo version 1.16.0 (compiled against version 1.16.0)
```
> fatal error: Aborted
Stack trace:
```
# Stack traces obtained from PID 6744 - Thread 6744 #
[New LWP 6746]
[New LWP 6747]
[New LWP 6748]
[New LWP 6749]
[New LWP 6822]
[New LWP 6994]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
__libc_read (nbytes=256, buf=0x7fff9d5c3550, fd=52) at
../sysdeps/unix/sysv/linux/read.c:26
Id Target Id Frame
* 1Thread 0x7f24aeb54500 (LWP 6744) "gimp-2.10" __libc_read (nbytes=256,
buf=0x7fff9d5c3550, fd=52) at ../sysdeps/unix/sysv/linux/read.c:26
2Thread 0x7f24ae38e700 (LWP 6746) "worker" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
3Thread 0x7f24ad5b9700 (LWP 6747) "gmain" 0x7f24afb20c2f in
__GI___poll (fds=0x564cac691f50, nfds=2, timeout=-1) at
../sysdeps/unix/sysv/linux/poll.c:29
4Thread 0x7f24acdb8700 (LWP 6748) "gdbus" 0x7f24afb20c2f in
__GI___poll (fds=0x564cac80ee00, nfds=3, timeout=-1) at
../sysdeps/unix/sysv/linux/poll.c:29
5Thread 0x7f249660e700 (LWP 6749) "async" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
6Thread 0x7f249552c700 (LWP 6822) "swap writer" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
7Thread 0x7f23c8c54700 (LWP 6994) "paint" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
Thread 7 (Thread 0x7f23c8c54700 (LWP 6994)):
#0 0x7f24afb2694d in syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
#1 0x7f24afe13d83 in g_cond_wait () at
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x564cabb6d32d in ()
#3 0x7f24afdf in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4 0x7f24afc07669 in start_thread (arg=) at
pthread_create.c:479
ret =
pd =
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {139791668954880,
210471390955828466, 140735833453854, 140735833453855, 140735833454000,
139791668951296, -239764903826688782, -242383913082686222}, mask_was_saved =
0}}, priv = {pad = {0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0,
canceltype = 0}}}
not_first_call = 0
#5 0x7f24afb2d323 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
Thread 6 (Thread 0x7f249552c700 (LWP 6822)):
#0 0x7f24afb2694d in syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
#1 0x7f24afe13d83 in g_cond_wait () at
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x7f24b02dcc4d in () at /usr/lib/x86_64-linux-gnu/libgegl-0.4.so.0
#3 0x7f24afdf in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4 0x7f24afc07669 in start_thread (arg=) at
pthread_create.c:479
ret =
pd =
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {139795100780288,
210471390955828466, 140735833449198, 140735833449199, 140735833449344,
139795100776704, -242468461185469198, -242383913082686222}, mask_was_saved =
0}}, priv = {pad = {0x0, 0x0, 0x0, 0x0}, data =
[Bug 1835605] Re: /usr/lib/gvfs/gvfs-afc-volume-monitor: error while loading shared libraries: libssl.so.1.0.0
** Package changed: ubuntu => gvfs (Ubuntu) -- 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/1835605 Title: /usr/lib/gvfs/gvfs-afc-volume-monitor: error while loading shared libraries: libssl.so.1.0.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1835605/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1804008] Re: Gnome Shell extensions crash [Object Meta.WindowActor (...), has been already deallocated .... from ubuntu-d...@ubuntu.com/theming.js:416]
I have found a work-around to get back to desktop. If you have locked the screen and it has hung you can lock/unlock by using the SUPER + L hotkey (Or whatever your shortcut key is). -- 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/1804008 Title: Gnome Shell extensions crash [Object Meta.WindowActor (...), has been already deallocated from ubuntu-d...@ubuntu.com/theming.js:416] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1804008/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1804008] Re: Gnome Shell extensions crash [Object Meta.WindowActor (...), has been already deallocated .... from ubuntu-d...@ubuntu.com/theming.js:416]
Forgot to mention, you may need to use the hotkey twice to lock from desktop. -- 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/1804008 Title: Gnome Shell extensions crash [Object Meta.WindowActor (...), has been already deallocated from ubuntu-d...@ubuntu.com/theming.js:416] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1804008/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1766969] [NEW] DNS cannot be resolved in Hotel Hotspot
Public bug reported: I was asked to create a new bug for this in https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 as it seems to be a different issue. I have installed the nightly image of Kubuntu Bionic from 25th of April. There systemd is in version 237-3ubuntu10. When connecting to the wifi hotspot in my hotel (Quality Hotel Augsburg) I cannot open the hotspot landing page that should give me access to the WIFI. With Windows and on an Iphone it's working. For the following distributions I can confirm it not working: Kubuntu 17.10 Kubuntu 18.04 (nightly image 25th of April 2018) The logs were taken on 18.04. Workaround: sudo systemctl disable systemd-resolved.service sudo service systemd-resolved stop sudo rm /etc/resolv.conf sudo nano /etc/NetworkManager/NetworkManager.conf >> add "dns=default" under [main] sudo service network-manager restart Then I can connect to the WIFI and I see the login page in Firefox. To capture some data I did the following: - connect to Hotspot - enter golem.de Case 1: Fresh default Kubuntu install With a default Kubuntu install it does not work. I can connect to the WIFI and get IP and DNS from DHCP but I cannot resolve any hostname. When trying to open the router ip directly in the browser it forwards to hotsplots.de which cannot be resolved. Case 2: With aforementioned Workaround I connect to the wifi, I open firefox and the login page shows up (if I havent been connected yet. In the capture I already was able to connect to the hotspot which allows immediately to connect to the webpage) PS: I'll be in this hotel till Friday 27th if more information are required. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: dns systemd systemd-resolv -- 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/1766969 Title: DNS cannot be resolved in Hotel Hotspot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1766969/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 608162] Re: GNOME Keyring Daemon stops panel's shutdown
Problem occurs 100% of the time on two Mint Cinnamon 64 bit machines after the latest round of updates when shutting down or restarting from whisker menu. 'shutdown (-r) now' works without an error. The most commonly reported 'fix' for this problem is purging old kernels. I just reinstalled 18.3 Cinnamon 64 from scratch on one and then installed all the updates. There were only 2 kernels. I removed 4.10 4.13.0-36 is the only one installed. It did not fix the problem. I did not have the problem before the last round of updates. Also on another computer with 18.2 which has not been turned on for a while I never had the problem until I just installed updates. It is using 4.10.0-33 kernel. 4.8.0.53, 4.10.0-33, and 4.13.0-36 are installed. I had no problem with on two 18.3 XFCE 64 bit machines. One I last used/updated Sunday 3/4 or another I just updated (including latest kernel) as of 3/8/18 0245Z. All computers are set for autologin. I tried turning autologin off on one Cinnamon but that had no effect. It appears there is something in the recent updates for Cinnamon that is causing this problem. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/608162 Title: GNOME Keyring Daemon stops panel's shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/608162/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1741777] Re: drag and drop between desktop and nautilus doesn't work
Looks like this may be the same issue as this bug still not resolved. https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1704765 -- 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/1741777 Title: drag and drop between desktop and nautilus doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1741777/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1741777] Re: drag and drop between desktop and nautilus doesn't work
I confirm I have this exact problem. Using latest build of Ubuntu 17.10 (Wayland)from Jan 2018. Note: This bug also seems very similar to this one. https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1729887 -- 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/1741777 Title: drag and drop between desktop and nautilus doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1741777/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1704765] Re: can't drag file from desktop to folder window on Artful
I confirm this issue as well. Using latest build of 17.10 and updated. It requires me to log off/on to get things working again. I found multiple duplicate bugs on this issue, and yes...wonder why its not fixed? -- 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/1704765 Title: can't drag file from desktop to folder window on Artful To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1704765/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1584457] Re: gsd-backlight-helper spamming the logs since upate to 16.04
@zmoazeni: Stopping the service does indeed stop the log spam on my machine. 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/1584457 Title: gsd-backlight-helper spamming the logs since upate to 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1584457/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1567250] Re: ssh signin problem since OTA-10
** Changed in: gnome-keyring (Ubuntu) Assignee: Pete Woods (pete-woods) => (unassigned) ** Changed in: indicator-network (Ubuntu) Assignee: Pete Woods (pete-woods) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1567250 Title: ssh signin problem since OTA-10 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1567250/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1567250] Re: ssh signin problem since OTA-10
** Changed in: indicator-network (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1567250 Title: ssh signin problem since OTA-10 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1567250/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1543030] Re: /usr/bin/gnome-keyring-daemon:7:_gcry_aes_arm_encrypt_block:do_encrypt_aligned:do_encrypt:_gcry_aes_cbc_enc:_gcry_cipher_cbc_encrypt
** Also affects: libgcrypt20 (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-keyring (Ubuntu) Status: New => Invalid ** Changed in: libgcrypt20 (Ubuntu) Status: New => In Progress ** Changed in: libgcrypt20 (Ubuntu) Assignee: (unassigned) => Pete Woods (pete-woods) ** Changed in: gnome-keyring (Ubuntu) Assignee: (unassigned) => Pete Woods (pete-woods) ** Summary changed: - /usr/bin/gnome-keyring-daemon:7:_gcry_aes_arm_encrypt_block:do_encrypt_aligned:do_encrypt:_gcry_aes_cbc_enc:_gcry_cipher_cbc_encrypt + Crash in gnome-keyring (in libgcrypt AES assembler) when used on ARM ** Branch linked: lp:~pete-woods/ubuntu/wily/libgcrypt20/disable-arm- asm-rijndael -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1543030 Title: Crash in gnome-keyring (in libgcrypt AES assembler) when used on ARM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1543030/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1543030] Re: Crash in gnome-keyring (in libgcrypt AES assembler) when used on ARM
** No longer affects: gnome-keyring (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1543030 Title: Crash in gnome-keyring (in libgcrypt AES assembler) when used on ARM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libgcrypt20/+bug/1543030/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1543030] Re: Crash in gnome-keyring (in libgcrypt AES assembler) when used on ARM
** Branch unlinked: lp:~pete-woods/ubuntu/wily/libgcrypt20/disable-arm- asm-rijndael ** Branch linked: lp:~pete-woods/ubuntu/xenial/libgcrypt20/disable-arm- asm-rijndael ** Description changed: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-keyring. This problem was most recently seen with version 3.16.0-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/3b9e06f40b09d062f6d8ddeccd7df9f305f9dfc9 contains more details. + + See the upstream bug here: https://bugs.gnupg.org/gnupg/issue2242 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1543030 Title: Crash in gnome-keyring (in libgcrypt AES assembler) when used on ARM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1543030/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1438094] Re: indicator-network aborts when trying to run unexistant dbus method
No-longer applies as we moved to use QDBus ** Changed in: dbus-cpp (Ubuntu) Status: New = Confirmed ** Changed in: indicator-network (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to dbus-cpp in Ubuntu. https://bugs.launchpad.net/bugs/1438094 Title: indicator-network aborts when trying to run unexistant dbus method To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus-cpp/+bug/1438094/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1304500] Re: Indicator Test Plan QA Review
** Also affects: indicator-network (Ubuntu) Importance: Undecided Status: New ** No longer affects: indicator-network -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1304500 Title: Indicator Test Plan QA Review To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-bluetooth/+bug/1304500/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1422879] Re: GPS stays active after location data is used by a scope (even after not not using the scopes anymore)
Okay, tvoss has helped uncover the actual bug. There's a refcounting error with temporary scopes. Attaching MR. ** Branch linked: lp:~unity-api-team/unity-scopes-shell/fix-location- refcount-bug ** Branch linked: lp:~unity-api-team/unity-scopes-shell/fix-location- refcount-bug-vivid ** Changed in: location-service (Ubuntu) Status: New = Invalid ** Changed in: unity-scopes-api (Ubuntu RTM) Status: In Progress = Invalid ** Also affects: unity-scopes-shell (Ubuntu) Importance: Undecided Status: New ** Also affects: unity-scopes-shell (Ubuntu RTM) Importance: Undecided Status: New ** Changed in: unity-scopes-shell (Ubuntu) Importance: Undecided = Critical ** Changed in: unity-scopes-shell (Ubuntu) Assignee: (unassigned) = Pete Woods (pete-woods) ** Changed in: unity-scopes-shell (Ubuntu) Status: New = Confirmed ** Changed in: unity-scopes-shell (Ubuntu RTM) Status: New = Confirmed ** Changed in: unity8 (Ubuntu) Status: New = Confirmed ** Changed in: unity8 (Ubuntu RTM) Status: New = Confirmed ** Changed in: unity-scopes-shell (Ubuntu RTM) Importance: Undecided = Critical ** Changed in: unity-scopes-shell (Ubuntu RTM) Assignee: (unassigned) = Pete Woods (pete-woods) ** Changed in: unity8 (Ubuntu) Importance: Undecided = Critical ** Changed in: unity8 (Ubuntu) Assignee: (unassigned) = Pete Woods (pete-woods) ** Changed in: unity8 (Ubuntu RTM) Importance: Undecided = Critical ** Changed in: unity8 (Ubuntu RTM) Assignee: (unassigned) = Pete Woods (pete-woods) ** Changed in: unity8 (Ubuntu RTM) Status: Confirmed = In Progress ** Changed in: unity8 (Ubuntu) Status: Confirmed = In Progress ** Changed in: unity-scopes-shell (Ubuntu RTM) Status: Confirmed = In Progress ** Changed in: unity-scopes-shell (Ubuntu) Status: Confirmed = In Progress -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1422879 Title: GPS stays active after location data is used by a scope (even after not not using the scopes anymore) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1422879/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1422879] Re: GPS stays active after location data is used by a scope (even after not not using the scopes anymore)
Checking the logcat output, I definitely see the GPS updates stopping after moving away from location-aware scopes. This is on an N4. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1422879 Title: GPS stays active after location data is used by a scope (even after not not using the scopes anymore) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1422879/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1422879] Re: GPS stays active after location data is used by a scope (even after not not using the scopes anymore)
Testing the build from silo 3 confirms that the GPS active / inactive signal is being sent to the location service 5 seconds after the screen turns off. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1422879 Title: GPS stays active after location data is used by a scope (even after not not using the scopes anymore) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1422879/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1422879] Re: GPS stays active after location data is used by a scope (even after not not using the scopes anymore)
** Branch linked: lp:~unity-api-team/unity8/scopes-active-depends-on- screen ** Branch linked: lp:~unity-api-team/unity8/scopes-active-depends-on- screen-rtm -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1422879 Title: GPS stays active after location data is used by a scope (even after not not using the scopes anymore) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1422879/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1422879] Re: GPS stays active after location data is used by a scope (even after not not using the scopes anymore)
So it's *possible* the problem could be in the location service, maybe? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1422879 Title: GPS stays active after location data is used by a scope (even after not not using the scopes anymore) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1422879/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1422879] Re: GPS stays active after location data is used by a scope (even after not not using the scopes anymore)
Okay, further debugging reveals that if you put the phone to sleep with a scope that requires location visible, the location updates are not disabled. Looks like this is a regression. The location service listens to when scopes are marked as active/inactive, and they all used to be marked inactive when the phone went to sleep. This is obviously no-longer the case. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1422879 Title: GPS stays active after location data is used by a scope (even after not not using the scopes anymore) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1422879/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1422879] Re: GPS stays active after location data is used by a scope (even after not not using the scopes anymore)
I just put together a branch for unity-scopes-shell that logs when GPS updates from the location service are being enabled and disabled: lp:~unity-api-team/unity-scopes-shell/log-when-updating-location Trying this on my device produces the expected behaviour, i.e.: * When looking at a scope that requires location, it enables location updates. * When you move away from that scope, location updates stay enabled for a 5 second timeout (in order that the GPS isn't rapidly turned on and off as you browse through scopes). To be clear, the location session remains active all the time, we just toggle the updates property. This is the (I believe correct) way tvoß explained to use the location service to me. Log output: Enabling location updates Disabling location updates Enabling location updates Disabling location updates Enabling location updates Disabling location updates -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1422879 Title: GPS stays active after location data is used by a scope (even after not not using the scopes anymore) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1422879/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1422879] Re: GPS stays active after location data is used by a scope (even after not not using the scopes anymore)
I think it's worth noting that this bug could be in addition to the problem rsalveti is mentioning -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1422879 Title: GPS stays active after location data is used by a scope (even after not not using the scopes anymore) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1422879/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1108064] Re: HUD messes up application's Alt key bindings
HUD itself has nothing to do with keyboard shortcuts. All the user interaction is part of the unity project. ** Changed in: hud (Ubuntu) Status: Confirmed = Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to fcitx in Ubuntu. https://bugs.launchpad.net/bugs/1108064 Title: HUD messes up application's Alt key bindings To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1108064/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1358918] Re: ubuntu-location-serviced cpu usage spikes to 100% occasionally
Copying this backtrace from duplicate bug: http://paste.ubuntu.com/8425087/ -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1358918 Title: ubuntu-location-serviced cpu usage spikes to 100% occasionally To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus-cpp/+bug/1358918/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1358918] Re: ubuntu-location-serviced cpu usage spikes to 100% occasionally
Core file from indicator-network ** Attachment added: core. https://bugs.launchpad.net/ubuntu/+source/dbus-cpp/+bug/1358918/+attachment/4214812/+files/core. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1358918 Title: ubuntu-location-serviced cpu usage spikes to 100% occasionally To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus-cpp/+bug/1358918/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1366978] Re: unity8-dash hangs in location service property destructor
*** This bug is a duplicate of bug 1370524 *** https://bugs.launchpad.net/bugs/1370524 ** This bug has been marked a duplicate of bug 1370524 Connecting to the location service sometimes freezes -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1366978 Title: unity8-dash hangs in location service property destructor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1366978/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1362769] Re: Location trust store causes dash to hang
*** This bug is a duplicate of bug 1370524 *** https://bugs.launchpad.net/bugs/1370524 ** This bug is no longer a duplicate of bug 1366978 unity8-dash hangs in location service property destructor ** This bug has been marked a duplicate of bug 1370524 Connecting to the location service sometimes freezes -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1362769 Title: Location trust store causes dash to hang To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1362769/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1372828] [NEW] Altitude and vertical accuracy give NaN values (instead of being unset) when using HERE integration
Public bug reported:
As per the title, we're doing checks like:
if (pos.altitude)
{
// Do stuff with altitude
}
if (pos.accuracy.vertical)
{
// Do stuff with vertical accuracy
}
These checks are passing (when really pos.altitude should evaluate to
false) when using Nokia HERE integration, and the result is that we're
giving out NaN values to clients.
** Affects: location-service (Ubuntu)
Importance: High
Status: New
** Tags: rtm-14
** Changed in: location-service (Ubuntu)
Importance: Undecided = High
** Tags added: rtm-14
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to location-service in Ubuntu.
https://bugs.launchpad.net/bugs/1372828
Title:
Altitude and vertical accuracy give NaN values (instead of being
unset) when using HERE integration
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1372828/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1288025] Re: HUD entries don't get activated with gmenumodel
Another good test case that Ted has noticed is LibreOffice. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1288025 Title: HUD entries don't get activated with gmenumodel To manage notifications about this bug go to: https://bugs.launchpad.net/hud/+bug/1288025/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1288025] Re: HUD entries don't get activated with gmenumodel
** Also affects: hud Importance: Undecided Status: New ** Changed in: hud Status: New = Confirmed ** Changed in: evince (Ubuntu) Status: Confirmed = Invalid ** Changed in: hud Importance: Undecided = High ** Changed in: hud Assignee: (unassigned) = Pete Woods (pete-woods) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1288025 Title: HUD entries don't get activated with gmenumodel To manage notifications about this bug go to: https://bugs.launchpad.net/hud/+bug/1288025/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1288025] Re: HUD entries don't get activated with gmenumodel
** Branch linked: lp:~unity-api-team/hud/lp-1288025 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1288025 Title: HUD entries don't get activated with gmenumodel To manage notifications about this bug go to: https://bugs.launchpad.net/hud/+bug/1288025/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1215874] Re: Please support code generation from XML introspection
** Summary changed: - Please support code generation from XML instrospection + Please support code generation from XML introspection ** Description changed: I'd be using it right away if it had a xml2cpp style generator like - gdbus / qtdbus. + gdbus / qtdbus to generate interface client and sever stubs. - I think it's the only feature missing for me.. + Some matching CMake macros installed in /usr/lib/arch/cmake/dbus-cpp/ + would make this even better :) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to dbus-cpp in Ubuntu. https://bugs.launchpad.net/bugs/1215874 Title: Please support code generation from XML introspection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus-cpp/+bug/1215874/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1132985] Re: Media Inserted Dialog is Lacking Fonts
@Seb, for me the system had been freshly restarted. Attached is the .xsession-errors ** Attachment added: .xsession-errors https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1132985/+attachment/3547641/+files/.xsession-errors -- 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/1132985 Title: Media Inserted Dialog is Lacking Fonts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1132985/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 884856] Re: gnome-keyring integration breaks some GPG functions
Brief follow-up to previous comment: I seem to have left the Unity desktop (GUI method): section blank. I had created that section before realizing that the Unity directions were identical to the Cinnamon directions and had failed to remove it. My apologies for any confusion. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/884856 Title: gnome-keyring integration breaks some GPG functions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/884856/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 884856] Re: gnome-keyring integration breaks some GPG functions
(Resurrecting a long-idle thread. Sorry.) This issue has also propagated to Linux Mint 14, an Ubuntu derivative. I was having difficulty using my German Privacy Foundation Crypto Stick with Mint or Ubuntu. While it doesn't solve the underlying issue (that is, the gnome-keyring agent doesn't play nice with smartcards), one can easily disable the offending agent and thus restore normal GPG operations in the following ways * Unity desktop (GUI method): * MATE (fork of GNOME 2) desktop (GUI method): Click Menu -- Preferences -- Startup Applications. Uncheck the GPG Password Agent (it appears twice as the GNOME Keyring and MATE Keyring). * MATE (fork of GNOME 2) desktop (command line method): 1. Open a terminal. 2. Execute the following commands as your user account (root is not required): mkdir ~/.config/autostart cp /etc/xdg/autostart/gnome-keyring-gpg.desktop ~/.config/autostart/ echo X-MATE-Autostart-enabled=false ~/.config/autostart/gnome-keyring-gpg.desktop 3. Log out of your session and log back in. 4. Test to make sure things are working. * Cinnamon (or Unity) desktop: 1. Open a terminal. 2. Execute the following commands as your user account (root is not required): mkdir ~/.config/autostart cp /etc/xdg/autostart/gnome-keyring-gpg.desktop ~/.config/autostart/ echo X-GNOME-Autostart-enabled=false ~/.config/autostart/gnome-keyring-gpg.desktop 3. Log out of your session and log back in. 4. Test to make sure things are working. * How to test if things are working: 1. Open a terminal. 2. Execute the following command as your user account (root is not required): echo $GPG_AGENT_INFO 3. a. If S.gpg-agent (or nothing, in the case of Unity, oddly enough) appears in the result, GPG will use the normal GPG agent. (Example: /home/pete/.gnupg/S.gpg-agent:2120:1) b. If keyring appears in the result, GPG will use the GNOME keyring agent and you will likely not be able to access the smartcard. (Example /run/user/pete/keyring-k4pQam/gpg:0:1) The exact paths, usernames, and numbers in the responses will vary. This is normal. It's the presence of either S.gpg-agent or keyring that identify which agent is being used. 4. Run gpg2 --card-status (or gpg --card-status if you don't have gnupg2 installed) to verify that GPG is able to communicate with the card. * Even though it doesn't solve the underlying problem, I hope this workaround is helpful. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/884856 Title: gnome-keyring integration breaks some GPG functions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/884856/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1132985] Re: Media Inserted Dialog is Lacking Fonts
I got the attached screenshot, which leads me to believe its not just natilus. -- 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/1132985 Title: Media Inserted Dialog is Lacking Fonts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1132985/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1132985] Re: Media Inserted Dialog is Lacking Fonts
I got the attached screenshot, which leads me to believe its not just natilus. ** Attachment added: Screenshot from 2013-02-22 10:07:24.png https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1132985/+attachment/3546815/+files/Screenshot%20from%202013-02-22%2010%3A07%3A24.png -- 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/1132985 Title: Media Inserted Dialog is Lacking Fonts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1132985/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1075923] Re: nautilus hangs copying large directories from a samba share
Can confirm this, too, on Ubuntu 12.10. Copying works if I mount smb as cifs, but using Nautilus it gets randomly stuck... (Only happend copying large directories, in particular with many files, but maybe that just raises the chance...) -- 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/1075923 Title: nautilus hangs copying large directories from a samba share To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1075923/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1070004] Re: For applications using simplified save dialogues, selecting a destination through Other... saves to /HOME directory
I too have this bug, manifested in OpenShot. I'm on Lubuntu 12.10, Linux 3.5.0-21-generic #32-Ubuntu SMP. I will try the workarount above on my next project. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1070004 Title: For applications using simplified save dialogues, selecting a destination through Other... saves to /HOME directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1070004/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1026418] [NEW] nautilus crashed with SIGSEGV in gtk_ui_manager_new_merge_id()
Public bug reported: Crashed when deleting a directory from my Desktop. ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: nautilus 1:3.5.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-5.5-generic 3.5.0-rc7 Uname: Linux 3.5.0-5-generic x86_64 ApportVersion: 2.4-0ubuntu2 Architecture: amd64 CrashCounter: 1 Date: Wed Jul 18 21:51:13 2012 EcryptfsInUse: Yes ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b'800x550+0+24' b'org.gnome.nautilus.window-state' b'sidebar-width' b'208' InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) ProcCmdline: nautilus -n ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f3fd1e10120 gtk_ui_manager_new_merge_id:mov 0x18(%rdi),%rdx PC (0x7f3fd1e10120) ok source 0x18(%rdi) (0x0018) not located in a known VMA region (needed readable region)! destination %rdx ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: nautilus StacktraceTop: gtk_ui_manager_new_merge_id () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () ?? () ?? () ?? () Title: nautilus crashed with SIGSEGV in gtk_ui_manager_new_merge_id() 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 quantal 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/1026418 Title: nautilus crashed with SIGSEGV in gtk_ui_manager_new_merge_id() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1026418/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1026418] Re: nautilus crashed with SIGSEGV in gtk_ui_manager_new_merge_id()
-- 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/1026418 Title: nautilus crashed with SIGSEGV in gtk_ui_manager_new_merge_id() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1026418/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1025867] [NEW] nautilus crashed with SIGSEGV in gtk_ui_manager_new_merge_id()
Public bug reported: Just crashed ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: nautilus 1:3.5.3-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-4.4-generic 3.5.0-rc6 Uname: Linux 3.5.0-4-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.3-0ubuntu4 Architecture: amd64 CrashCounter: 1 Date: Tue Jul 17 15:56:45 2012 EcryptfsInUse: Yes ExecutablePath: /usr/bin/nautilus InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20120314) ProcCmdline: nautilus -n ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fc49b4d9580 gtk_ui_manager_new_merge_id:mov 0x18(%rdi),%rdx PC (0x7fc49b4d9580) ok source 0x18(%rdi) (0x0018) not located in a known VMA region (needed readable region)! destination %rdx ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: nautilus StacktraceTop: gtk_ui_manager_new_merge_id () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () ?? () ?? () ?? () Title: nautilus crashed with SIGSEGV in gtk_ui_manager_new_merge_id() 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 quantal 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/1025867 Title: nautilus crashed with SIGSEGV in gtk_ui_manager_new_merge_id() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1025867/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1025867] Re: nautilus crashed with SIGSEGV in gtk_ui_manager_new_merge_id()
-- 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/1025867 Title: nautilus crashed with SIGSEGV in gtk_ui_manager_new_merge_id() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1025867/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 390989] Re: [SecurityRoadmap] Locked screen shows the desktop
Had the issue today. Was working nearby with the screen timed out for more than 5 or 10 mins (black/blank). I assumed it was locked. To wake it, I started typing my password and hit enter only to find that I had sent my password to a co-worker over IM. I was able to chat with him for at least 30 seconds before the screen locked. I beleive this to be a huge security risk. Please promote this to a high priority. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/390989 Title: [SecurityRoadmap] Locked screen shows the desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/390989/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 390989] Re: [SecurityRoadmap] Locked screen shows the desktop
I should add that this is on an HP8540w notebook. nVidia driver 295.40 on Quadro FX 880M 1GB Running Twinview dual screens on docking station (lid closed): HP LP2475w (DFP-1) + DELL 1908FP (CRT-0) Had the issue today. Was working nearby with the screen timed out for more than 5 or 10 mins (black/blank). I assumed it was locked. To wake it, I started typing my password and hit enter only to find that I had sent my password to a co-worker over IM. I was able to chat with him for at least 30 seconds before the screen locked. I beleive this to be a huge security risk. Please promote this to a high priority. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/390989 Title: [SecurityRoadmap] Locked screen shows the desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/390989/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 390989] Re: [SecurityRoadmap] Locked screen shows the desktop
Ubuntu 12.04 x86_64 on HP8540w notebook. nVidia driver 295.40 on Quadro FX 880M 1GB Running Twinview dual screens on docking station (lid closed): HP LP2475w (DFP-1) + DELL 1908FP (CRT-0) Had the issue today. Was working nearby with the screen timed out for more than 5 or 10 mins (black/blank). I assumed it was locked. To wake it, I started typing my password and hit enter only to find that I had sent my password to a co-worker over IM. I was able to chat with him for at least 30 seconds before the screen locked. I beleive this to be a huge security risk. Please promote this to a high priority. Sorry for the multiple posts... https://bugs.launchpad.net/launchpad/+bug/119420 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/390989 Title: [SecurityRoadmap] Locked screen shows the desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/390989/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1022958] [NEW] nautilus crashed with SIGSEGV in gtk_ui_manager_new_merge_id()
*** This bug is a duplicate of bug 925503 *** https://bugs.launchpad.net/bugs/925503 Public bug reported: Just popped up while working.; ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: nautilus 1:3.5.3-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-3.3-generic 3.5.0-rc5 Uname: Linux 3.5.0-3-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.3-0ubuntu2 Architecture: amd64 Date: Tue Jul 10 08:50:56 2012 EcryptfsInUse: Yes ExecutablePath: /usr/bin/nautilus InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20120314) ProcCmdline: nautilus -n ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f8f9dbb2580 gtk_ui_manager_new_merge_id:mov 0x18(%rdi),%rdx PC (0x7f8f9dbb2580) ok source 0x18(%rdi) (0x0018) not located in a known VMA region (needed readable region)! destination %rdx ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: nautilus StacktraceTop: gtk_ui_manager_new_merge_id () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () ?? () ?? () ?? () Title: nautilus crashed with SIGSEGV in gtk_ui_manager_new_merge_id() 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 quantal 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/1022958 Title: nautilus crashed with SIGSEGV in gtk_ui_manager_new_merge_id() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1022958/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1022958] Re: nautilus crashed with SIGSEGV in gtk_ui_manager_new_merge_id()
*** This bug is a duplicate of bug 925503 *** https://bugs.launchpad.net/bugs/925503 -- 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/1022958 Title: nautilus crashed with SIGSEGV in gtk_ui_manager_new_merge_id() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1022958/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 771896] Re: No way to save current session
** Changed in: ubuntu-release-notes Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/771896 Title: No way to save current session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/771896/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 966858] Re: [power]: gnome-settings-daemon crashed with SIGSEGV in gnome_rr_screen_get_dpms_mode()
** Visibility changed 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/966858 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/ubuntu/+source/gnome-settings-daemon/+bug/966858/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 963080] [NEW] rhythmbox-metadata crashed with SIGSEGV in gst_structure_copy()
Private bug reported: Loaded up thythmbox and got this crash while it was scanning my library ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: rhythmbox 2.96-0ubuntu3 ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.95-0ubuntu1 Architecture: amd64 CrashCounter: 1 Date: Fri Mar 23 09:16:17 2012 EcryptfsInUse: Yes ExecutablePath: /usr/lib/rhythmbox/rhythmbox-metadata InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20120314) ProcCmdline: /usr/lib/rhythmbox/rhythmbox-metadata unix:tmpdir=/tmp ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SegvReason: reading NULL VMA Signal: 11 SourcePackage: rhythmbox Title: rhythmbox-metadata crashed with SIGSEGV in gst_structure_copy() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo ** Affects: rhythmbox (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 rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/963080 Title: rhythmbox-metadata crashed with SIGSEGV in gst_structure_copy() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/963080/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 963074] [NEW] gvfsd-sftp crashed with SIGSEGV in g_vfs_job_emit_finished()
Private bug reported: Loaded up rhythembox over a sshfs:// connection and gvfs crashed. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: gvfs-backends 1.11.5-1ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.95-0ubuntu1 Architecture: amd64 Date: Fri Mar 23 09:11:36 2012 EcryptfsInUse: Yes ExecutablePath: /usr/lib/gvfs/gvfsd-sftp InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20120314) ProcCmdline: /usr/lib/gvfs/gvfsd-sftp --spawner :1.5 /org/gtk/gvfs/exec_spaw/9 ProcEnviron: SHELL=/bin/bash PATH=(custom, user) LANG=en_US.UTF-8 SegvReason: reading NULL VMA Signal: 11 SourcePackage: gvfs Title: gvfsd-sftp crashed with SIGSEGV in g_vfs_job_emit_finished() 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 precise -- 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/963074 Title: gvfsd-sftp crashed with SIGSEGV in g_vfs_job_emit_finished() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/963074/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 934445] Re: hits g_assert (device-priv-styli) when my Wacom Bamboo 2FG 4x5 is plugged in
@seb128, Sorry for the delay I missed your question in bug mail. It works as expected now. -- 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/934445 Title: hits g_assert (device-priv-styli) when my Wacom Bamboo 2FG 4x5 is plugged in To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/934445/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 956956] Re: gnome-settings-daemon crashes when Wacom Tablet is plugged in
*** This bug is a duplicate of bug 956692 *** https://bugs.launchpad.net/bugs/956692 ** This bug has been marked a duplicate of private bug 956692 -- 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/956956 Title: gnome-settings-daemon crashes when Wacom Tablet is plugged in To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/956956/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 956956] [NEW] gnome-settings-daemon crashes when Wacom Tablet is plugged in
*** This bug is a duplicate of bug 956692 *** https://bugs.launchpad.net/bugs/956692 Public bug reported: when the machine first booted with the tablet connected, g-s-d crashes, the only way I noticed was I had the old gnome theme. then I started g-s-d form the command line and got the following output: pgraner@zorak:~$ gnome-settings-daemon color-plugin-WARNING **: failed to get edid: unable to get EDID for output [1331903731,000,xklavier.c:xkl_engine_start_listen/]The backend does not require manual layout management - but it is provided by the application ** WARNING **: Tablet 'usb:056a:0015' has no buttons defined, do something! ** WARNING **: Tablet 'usb:056a:0014' has no buttons defined, do something! ** WARNING **: Tablet 'usb:056a:0013' has no buttons defined, do something! wacom-plugin-WARNING **: Could not set the current stylus ID 0x0 for tablet 'Wacom Bamboo Pen Touch', no general pen found ** wacom-plugin:ERROR:gsd-wacom-device.c:1491:gsd_wacom_device_set_current_stylus: assertion failed: (device-priv-styli) Aborted (core dumped) ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-settings-daemon 3.3.91-0ubuntu6 ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9 Uname: Linux 3.2.0-18-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.94.1-0ubuntu2 Architecture: amd64 Date: Fri Mar 16 09:26:03 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20120314) ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise -- 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/956956 Title: gnome-settings-daemon crashes when Wacom Tablet is plugged in To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/956956/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 937792] [NEW] Left launcher does not revel when in autohide mode on multi-monitor setups
Public bug reported: After this mornings (21 Feb) updates, I found that the left launcher will not reveal when it is set to autohide ON thru the Settings-Appearance-Behavior application. This was working fine before the update. ** Affects: nvidia-graphics-drivers (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/937792 Title: Left launcher does not revel when in autohide mode on multi-monitor setups To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/937792/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 937792] Re: Left launcher does not revel when in autohide mode on multi-monitor setups
-- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/937792 Title: Left launcher does not revel when in autohide mode on multi-monitor setups To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/937792/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 934445] Re: gnome-settings-daemon 3.3.5 crashed with SIGABRT in g_assertion_message() when my Wacom Bamboo 2FG 4x5 is plugged in
@sarvatt Here are the output you asked for. Let me know if you need anything else. ** Attachment added: xinput.log https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/934445/+attachment/2758397/+files/xinput.log -- 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/934445 Title: gnome-settings-daemon 3.3.5 crashed with SIGABRT in g_assertion_message() when my Wacom Bamboo 2FG 4x5 is plugged in To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/934445/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 934445] Re: gnome-settings-daemon 3.3.5 crashed with SIGABRT in g_assertion_message() when my Wacom Bamboo 2FG 4x5 is plugged in
** Attachment added: lsusb.log https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/934445/+attachment/2758398/+files/lsusb.log -- 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/934445 Title: gnome-settings-daemon 3.3.5 crashed with SIGABRT in g_assertion_message() when my Wacom Bamboo 2FG 4x5 is plugged in To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/934445/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 934445] Re: gnome-settings-daemon crashed with SIGABRT in raise()
** Visibility changed 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/934445 Title: gnome-settings-daemon crashed with SIGABRT in raise() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/934445/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 934447] Re: gnome-settings-daemon crashed with SIGABRT in raise()
** Visibility changed 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/934447 Title: gnome-settings-daemon crashed with SIGABRT in raise() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/934447/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 649809] Re: the session settings manager can try starting before the login screen one exits
Having the same issue in Oneric, random occurences, sometimes reboot works, sometimes requires multiple reboots. Although still not sure if this is related to the bug mentioned here, or the one over here... http://askubuntu.com/questions/21305/desktop-forgets-theme Am running an old Athlon with regular HDD, although nVidia chipset present on mobo. Haven't tried yet the timings with the daemons but will look at that next. Just thought I'd add that this IS still occuring on a Oneric environment -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/649809 Title: the session settings manager can try starting before the login screen one exits To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/649809/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 73750] Re: After hibernate: Battery not correctly recognized/displayed in Panel applet
This Bug affects me too. I'm using 11.04 on my ASUS X53E laptop. Here is how I can produce the bug: 1. Laptop on battery and with plenty battery left 2. Let the laptop hibernate 3. wake it up again gnome-power-manager's battery applet shows the battery as critical (0%) after 30 seconds when the applet refeshes again, the battery shows the correct level again. cat /proc/acpi/battery/BAT0/state shows the correct state at all times. This bug is a problem when I have suspend on critical battery turned on, because the laptop wakes up from hibernation and goes right back into to suspend. This doesn't happen for me on suspend. -- 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/73750 Title: After hibernate: Battery not correctly recognized/displayed in Panel applet To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/73750/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 853621] Re: gnome-power-statistics crashed with SIGABRT
** Visibility changed to: Public -- 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/853621 Title: gnome-power-statistics crashed with SIGABRT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/853621/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 853003] Re: empathy crashed with SIGABRT
** Visibility changed to: Public -- 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/853003 Title: empathy crashed with SIGABRT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/853003/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 850778] Re: empathy crashed with SIGABRT in raise()
*** This bug is a duplicate of bug 845314 *** https://bugs.launchpad.net/bugs/845314 ** Visibility changed to: Public -- 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/850778 Title: empathy crashed with SIGABRT in raise() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/850778/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 849979] Re: metacity crashed with SIGABRT in raise()
** Visibility changed to: Public -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/849979 Title: metacity crashed with SIGABRT in raise() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/849979/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 850025] Re: metacity crashed with SIGABRT in raise()
** Visibility changed to: Public -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/850025 Title: metacity crashed with SIGABRT in raise() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/850025/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 849274] Re: empathy crashed with SIGSEGV in g_closure_invoke()
** Visibility changed to: Public -- 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/849274 Title: empathy crashed with SIGSEGV in g_closure_invoke() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/849274/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 848346] Re: nautilus crashed with SIGSEGV in g_main_context_dispatch()
** Visibility changed 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/848346 Title: nautilus crashed with SIGSEGV in g_main_context_dispatch() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/848346/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 847307] Re: empathy crashed with SIGABRT
** Visibility changed to: Public -- 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/847307 Title: empathy crashed with SIGABRT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/847307/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 847310] Re: empathy crashed with SIGABRT
** Visibility changed to: Public -- 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/847310 Title: empathy crashed with SIGABRT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/847310/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 847320] Re: empathy crashed with SIGABRT
** Visibility changed to: Public -- 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/847320 Title: empathy crashed with SIGABRT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/847320/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 847329] Re: empathy crashed with SIGABRT
** Visibility changed to: Public -- 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/847329 Title: empathy crashed with SIGABRT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/847329/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 847322] Re: gnome-power-statistics crashed with SIGABRT in raise()
** Visibility changed to: Public -- 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/847322 Title: gnome-power-statistics crashed with SIGABRT in raise() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/847322/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 847315] Re: gnome-power-statistics crashed with SIGABRT in raise()
** Visibility changed to: Public -- 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/847315 Title: gnome-power-statistics crashed with SIGABRT in raise() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/847315/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 845186] Re: gnome-power-statistics crashed with SIGABRT in raise()
*** This bug is a duplicate of bug 837354 *** https://bugs.launchpad.net/bugs/837354 ** Visibility changed to: Public -- 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/845186 Title: gnome-power-statistics crashed with SIGABRT in raise() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/845186/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 838527] Re: empathy crashed with SIGSEGV
** Visibility changed to: Public -- 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/838527 Title: empathy crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/838527/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 834523] Re: Can't change the keyboard layout from a default install
Afaict, the Region Language Settings dialog doesn't exist. $ grep Region /usr/share/applications/*.desktop /usr/share/applications/gnome-region-panel.desktop:Name=Region and Language $ grep Exec /usr/share/applications/gnome-region-panel.desktop Exec=gnome-control-center region $ gnome-control-center region (gnome-control-center:12420): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed ** (gnome-control-center:12420): WARNING **: Could not find settings panel region ** (gnome-control-center:12420): WARNING **: Could not load setting panel region: Unknown error -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/834523 Title: Can't change the keyboard layout from a default install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/834523/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 832378] Re: empathy crashed with SIGSEGV in g_memdup()
** Visibility changed to: Public -- 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/832378 Title: empathy crashed with SIGSEGV in g_memdup() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/832378/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 830068] Re: empathy-chat crashed with SIGSEGV in dbus_connection_dispatch()
** Visibility changed to: Public -- 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/830068 Title: empathy-chat crashed with SIGSEGV in dbus_connection_dispatch() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/830068/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 825250] Re: Remove Force fallback mode when not using GNOME Shell
I'm fine with making it work for Ubuntu 2D as well. I guess my position is we should either make it work with Ubuntu 2D or not show it when not in GNOME Shell. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/825250 Title: Remove Force fallback mode when not using GNOME Shell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/825250/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 825221] Re: empathy crashed with signal 5 in g_malloc()
** Visibility changed to: Public -- 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/825221 Title: empathy crashed with signal 5 in g_malloc() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/825221/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 825250] [NEW] Remove Force fallback mode when not using GNOME Shell
Public bug reported: If you go to the GNOME Control Center and start System Info there is a Graphics option. Inside there is an option to Force fallback mode. I have been using this to try using Ubuntu 2D, but the option only works when logging into GNOME Shell. Therefore, to avoid confusion we should not display this option when not using GNOME Shell. Yes, this is somewhat advanced but we have a very technical audience and this could cause a lot of confusion and wasted time. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-control-center 1:3.1.4-0ubuntu5 ProcVersionSignature: Ubuntu 3.0.0-8.10-generic 3.0.1 Uname: Linux 3.0.0-8-generic x86_64 Architecture: amd64 Date: Fri Aug 12 15:30:01 2011 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Alpha amd64 (20110728) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug oneiric running-unity -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/825250 Title: Remove Force fallback mode when not using GNOME Shell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/825250/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 825250] Re: Remove Force fallback mode when not using GNOME Shell
-- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/825250 Title: Remove Force fallback mode when not using GNOME Shell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/825250/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 822713] Re: gsettings-data-convert crashed with signal 5 in g_settings_set_value()
** Visibility changed to: Public -- 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/822713 Title: gsettings-data-convert crashed with signal 5 in g_settings_set_value() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/822713/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 818018] Re: gnome-keyring-daemon refuses to start
Hi Seb, Yes, the workaround (using setcap) seems to fix the issue. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/818018 Title: gnome-keyring-daemon refuses to start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/818018/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 818018] [NEW] gnome-keyring-daemon refuses to start
Public bug reported: I have just done a fresh install of Ubuntu 11.10 from the daily live CD from 29th July 2011. After installation, I could not connect to any wireless network or even my mobile broadband connection. I restored my home directory to see if maybe it was just the lack of a keyring and that still didn't help. Checking the wireless connections I noticed that a) none of my previously saved networks were listed and b) the one I had been trying to connect to was listed, but had no password filled in. I filled in the password for the WPA2 network and connected just fine. I checked seahorse to see if the password was saved and was informed seahorse couldn't connect to gnome-keyring-daemon. When I try to start the gnome-keyring-daemon from the command line, here is what I get: $ gnome-keyring-daemon gnome-keyring-daemon: error getting process capabilities, aborting I'm not sure how to debug this, so please let me know what other information I can give you. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-keyring 3.1.1-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-7.8-generic 3.0.0 Uname: Linux 3.0.0-7-generic x86_64 Architecture: amd64 Date: Fri Jul 29 13:21:10 2011 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Alpha amd64 (20110728) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-keyring UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-keyring (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug oneiric running-unity -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/818018 Title: gnome-keyring-daemon refuses to start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/818018/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 818018] Re: gnome-keyring-daemon refuses to start
-- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/818018 Title: gnome-keyring-daemon refuses to start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/818018/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 486154] Re: System beep broken in Karmic despite heroic efforts to fix it
Thomas, I don't think you need to run gconf-editor at all. This is what does it for me on Natty 11.04: /usr/bin/pactl remove-sample bell.ogg /usr/bin/pactl upload-sample /usr/share/sounds/gnome/default/alerts/glass.ogg bell.ogg /usr/bin/xset b on /usr/bin/xset b 100 Plug this into a session startup script. Of course it doesn't fix the problem that changing the sound of the bell via System - Preferences - Sound Preferences has no effect. I can't understand why this continues to be an issue in Ubuntu. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/486154 Title: System beep broken in Karmic despite heroic efforts to fix it -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 744929] Re: After auto-login, prompted to unlock keyring multiple times
I know this isn't a fix for the base bug, but it may fix the situation on an individual basis. See Comment #3 on bug #745780. Basic summary: if you have two keyrings you probably only want one. More in the comment. https://bugs.launchpad.net/ubuntu/+source/gnome- keyring/+bug/745780/comments/3 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/744929 Title: After auto-login, prompted to unlock keyring multiple times -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 745780] Re: multiple prompts from gnome-keyring
Ok, working though this I have a work-around, but not a solution. Someone else can probably come up with a cause. :-) I have two keyrings: login and default. In the file ~/.gnome2/keyrings/default the default keyring is set as default, and that is where all my passwords reside. The problem is that Ubuntu is expecting my passwords to be in a keyring called login. If I delete the login keyring then the keyring is recreated, but is of course blank and is *not* set as the default keyring. The way I got things working was to delete ~/.gnome2/keyrings/login.keyring and renamed ~/.gnome2/keyrings/default.keyring to ~/.gnome2/login.keyring. Then I edited ~/.gnome2/keyrings/default to say login is the default. This might be a roundabout way of doing things, but this worked for me. Now I just have to figure out why I'm not getting prompted for my keyring password at all - even though that keyring definitely has a password. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/745780 Title: multiple prompts from gnome-keyring -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 745780] [NEW] multiple prompts from gnome-keyring
Public bug reported: Binary package hint: gnome-keyring According to bug #637702 I should file a new bug for this. I'm using Ubuntu 11.04 up to date as of yesterday (29th March 2011). I get multiple prompts to unlock the keyring Default when logging in. Once I authorise the first prompt I can connect to the my choses wireless network and afaict there are no adverse effects to cancel the remaining prompts. It is not always a fixed number, but I am usually prompted five times for the password. Occasionally it is just two or four, but it doesn't seem to be consistent. When I open Seahorse I see I have two keyrings, login and default, and default is the default keyring. The login keyring has no passwords (afaict) but deleting it doesn't help. In fact the login key is just recreated on next login. I checked for autostart files and have deleted them from various places (~/.config/autostart/, ~/.kde/Autostart). Not sure where to go for troubleshooting. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: gnome-keyring 2.92.92.is.2.32.1-0ubuntu2 ProcVersionSignature: Ubuntu 2.6.38-7.39-generic-pae 2.6.38 Uname: Linux 2.6.38-7-generic-pae i686 Architecture: i386 Date: Wed Mar 30 14:23:47 2011 InstallationMedia: Ubuntu 11.04 Natty Narwhal - Alpha i386 (20110218) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-keyring UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-keyring (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 natty running-unity unity-2d -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/745780 Title: multiple prompts from gnome-keyring -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 745780] Re: multiple prompts from gnome-keyring
-- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/745780 Title: multiple prompts from gnome-keyring -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 732704] Re: empathy-auth-client crashed with SIGSEGV in g_closure_invalidate()
The system was just dist-upgraded and rebooted. So all packages were up to date. Marking new nice the script had no idea of what it was talking about. ** Visibility changed to: Public ** Changed in: empathy (Ubuntu) Status: Invalid = 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/732704 Title: empathy-auth-client crashed with SIGSEGV in g_closure_invalidate() -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
