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
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
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
** 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
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
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
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
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
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.
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
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
@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:
** 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,
** 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
** 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) =
** 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
** 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
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
** 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.
: 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
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.
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.
** 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.
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
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
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
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
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
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
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
*** 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
*** 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
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
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
** 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
** 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
** 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
@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
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
/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
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
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
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
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.
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
--
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:
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
--
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:
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
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
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).
*** 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
*** 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
** 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
** 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
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
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
@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
*** 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.
*** 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
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:
--
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
@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
** 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.
** 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
** 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
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
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
** 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
** 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:
*** 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
** 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
** 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
** 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
** 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
** 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:
** 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:
** 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:
** 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:
** 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
** 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
*** 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.
** 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:
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
$
** 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
** 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
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
** 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
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
--
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:
** 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
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
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
--
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:
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
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
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
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
--
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
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
1 - 100 of 251 matches
Mail list logo
