Closing this as Invalid - at least it seems to be by design: with GNOME,
gnome-shell is meant to listen and respond to the phase change (asking for
confirmation).
Without gnome-shell (or unity), you will be logged out if nothing intervenes.
I'm now using my own confirmation dialog (zenity), and
Public bug reported:
I am trying to use a custom gnome-session with the Awesome window
manager, but the session is not working.
The configuration is based on
http://awesome.naquadah.org/wiki/Quickly_Setting_up_Awesome_with_Gnome#Gnome_3.9_.2F_Ubuntu_13.10
and was working with Ubuntu 14.04.
I
Public bug reported:
Using pm-hibernate might be prevented by /usr/lib/pm-utils/sleep.d
/000kernel-change.
In this case it would be useful if it could (optionally?) fall back to
pm-suspend.
Also, gnome-session-quit --power-off should display the Hibernate
action as greyed out / disabled right
** Changed in: gnome-control-center (Ubuntu)
Status: Confirmed = Triaged
--
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/1237121
Title:
Keyboard: cannot bind
On 25.02.2015 23:42, Gunnar Hjalmarsson wrote:
Thanks for your comments!
On 2015-02-25 19:56, Daniel Hahler wrote:
set -x
exec 1$logfile
exec 2$logfile
Really using the exec command in ~/.profile would stop the execution
of the main process (/usr/sbin/lightdm-session), so I
Thanks for working on this!
For what it's worth, I've been using the following, and had to move the
set -x now below the exec 2$logfile, otherwise this was detected
as being an error.
1. I've been using the following in ~/.profile, mainly for debugging
purposes:
** Changed in: gnome-terminal (Ubuntu)
Status: Confirmed = Triaged
** Changed in: gnome-terminal (Ubuntu)
Importance: Undecided = High
** Also affects: gnome-terminal via
https://bugzilla.gnome.org/show_bug.cgi?id=730643
Importance: Unknown
Status: Unknown
--
You
In case this still happens to you: you could get an strace log using the
following command:
sudo strace -f -p $(pgrep gnome-terminal) -o /tmp/gnome-terminal-
strace.txt
Abort it after a few seconds and then attach it here.
--
You received this bug notification because you are a member of
I am seeing the same problem recently (after upgrading to Ubuntu 14.04).
I have reported the issue in the GNOME bugtracker at:
https://bugzilla.gnome.org/show_bug.cgi?id=730643
** Bug watch added: GNOME Bug Tracker #730643
https://bugzilla.gnome.org/show_bug.cgi?id=730643
--
You received
Mikel,
I have used the patches from your website:
http://mikelward.com/software/gnome/flashing-terminal, and obviously
missed the config schema stuff.
Does this patch after all is able to just forward the terminal bell by
setting the X client window's urgent property? Because that's all I want
@Mikel: thanks for your work on this!
Any chance to have your PPA updated for the current Ubuntu release
(saucy and trusty)?
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
FWIW, I have tried to create a package, with the patch (obviously not
properly) refreshed, but it failed to build (against gnome-terminal in
trusty, built in a saucy pbuilder):
libtool: link: gcc -pthread -DVTE_SEAL_ENABLE -I/usr/include/glib-2.0
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include
There should show up a package at
https://launchpad.net/~blueyed/+archive/ppa/+sourcepub/4046208/+listing-
archive-extra
However, I do not see the options (and they are not in the patch as far
as I can see).
From your description it also does not look like it solves the single
set the X
** Changed in: gnome-terminal (Ubuntu)
Status: Confirmed = Invalid
** Bug watch added: Debian Bug tracker #681770
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681770
** Also affects: awesome (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681770
Importance:
** Description changed:
I have noticed that pydoc -k . hangs on my system.
This method is used by vim-ref (https://github.com/thinca/vim-ref/) to
get a list of all entries.
+
+ Stepping thorugh it via ipdb, it hangs at:
+
+
I can confirm that first importing gtk in /usr/bin/pydoc works around
`pydoc -k .` crashing.
** Also affects: pygtk (Ubuntu)
Importance: Undecided
Status: New
** Changed in: pygtk (Ubuntu)
Status: New = Triaged
** Changed in: pygtk (Ubuntu)
Importance: Undecided = Medium
--
*** This bug is a duplicate of bug 896836 ***
https://bugs.launchpad.net/bugs/896836
** This bug has been marked a duplicate of bug 896836
Segmentation fault when asking help() for the list of modules
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
@seb128
I am using the German keyboad layout (de, nodeadkey).
** Changed in: gnome-control-center (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
Here is a video describing the problem:
http://superuser.com/questions/555695/fix-terminal-vim-colours-on-focus-lost
** Changed in: gnome-terminal (Ubuntu)
Status: Confirmed = Triaged
** Changed in: gnome-terminal (Ubuntu)
Importance: Undecided = Medium
--
You received this bug
** Bug watch added: GNOME Bug Tracker #703967
https://bugzilla.gnome.org/show_bug.cgi?id=703967
** Also affects: gnome-control-center via
https://bugzilla.gnome.org/show_bug.cgi?id=703967
Importance: Unknown
Status: Unknown
** Description changed:
Up until Raring, it was
Public bug reported:
% ubuntu-bug gnome-control-center-data
ERROR: hook /usr/share/apport/package-hooks/source_gnome-control-center.py
crashed:
Traceback (most recent call last):
File /usr/lib/python3/dist-packages/apport/report.py, line 197, in _run_hook
symb['add_info'](report, ui)
Public bug reported:
When clicking on Key to show the HUD in the Keyboard's Shortcuts settings, I
cannot set the default itself:
1. Pressing the left Alt key results in the shortcut to get disabled (it says
Disabled then)
2. There's no possibility to cancel the editing
3. There's no
python-launchpadlib does not have any config, but uses cache files
insteaad. I have created bug 1068695 about this.
** Changed in: python-launchpadlib (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
Have you enabled compinit etc?
It might depend on the list of installed Python modules (which get queried
probably).
I am getting the following after Tab on the console:
/usr/lib/python2.7/dist-packages/gobject/constants.py:24: Warning:
g_boxed_type_register_static: assertion `g_type_from_name
Bug 960663 (a duplicate) is reproducible for me - just by trying to tab-
complete python -m uni.
(I am using zsh)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to pygobject in Ubuntu.
https://bugs.launchpad.net/bugs/946685
Title:
Sure.
** Attachment added: Output of udisks --dump
https://bugs.launchpad.net/ubuntu/+source/udisks/+bug/1005854/+attachment/3203661/+files/udisks-dump.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
Public bug reported:
nautilus-sendto crashes immediately when being opened from Nautilus or
Shotwell.
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: nautilus-sendto 3.0.1-2ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19
Uname: Linux 3.2.0-26-generic x86_64
ApportVersion:
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus-sendto in Ubuntu.
https://bugs.launchpad.net/bugs/1017074
Title:
nautilus-sendto crashed with SIGSEGV in g_slice_alloc()
To manage notifications about this bug go to:
** Attachment added: Valgrind logfile
https://bugs.launchpad.net/ubuntu/+source/nautilus-sendto/+bug/1017074/+attachment/3202300/+files/valgrind.log
** Description changed:
nautilus-sendto crashes immediately when being opened from Nautilus or
Shotwell.
+
+ Terminal output when run with
** Description changed:
nautilus-sendto crashes immediately when being opened from Nautilus or
Shotwell.
+
+ This is caused by the Evolution plugin:
+ after reporting this crash I have moved all plugins except libnstevolution.so
out of /usr/lib/nautilus-sendto/plugins and it still crashes.
** Description changed:
nautilus-sendto crashes immediately when being opened from Nautilus or
Shotwell.
This is caused by the Evolution plugin:
after reporting this crash I have moved all plugins except libnstevolution.so
out of /usr/lib/nautilus-sendto/plugins and it still crashes.
I am attaching the full output. The relevant part appears to be:
Volume(3): 199 MB Encrypted
Type: GProxyVolume (GProxyVolumeMonitorGdu)
ids:
unix-device: '/dev/sda5'
uuid: 'd39d1dee-5cd0-4368-90af-daf8596d6ae9'
themed icons: [drive-harddisk-ata] [drive-harddisk] [drive]
** Bug watch added: GNOME Bug Tracker #677397
https://bugzilla.gnome.org/show_bug.cgi?id=677397
** Also affects: gvfs via
https://bugzilla.gnome.org/show_bug.cgi?id=677397
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of
I think the best method is to just use pm-suspend-hybrid:
the system is fast to resume if you wake it up within 15 minutes again, but
suspends to disk after this and saves all the energy which Suspend To RAM would
still use.
If your system supports it, you can easily make suspend behave as
** Changed in: gvfs (Ubuntu)
Status: Confirmed = Triaged
** Changed in: gvfs (Ubuntu)
Importance: Undecided = Medium
--
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/871103
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evolution-data-server in Ubuntu.
https://bugs.launchpad.net/bugs/859542
Title:
e-addressbook-factory crashed with SIGSEGV in
** Changed in: nautilus (Ubuntu)
Status: Confirmed = Triaged
** Changed in: libx11 (Ubuntu)
Status: Confirmed = Triaged
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
** Visibility changed to: Public
--
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/820601
Title:
rhythmbox-metadata crashed with SIGSEGV in _start()
To manage notifications about
** Changed in: gnome-terminal (Ubuntu)
Status: Confirmed = Triaged
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/840313
Title:
gnome-terminal crashed with SIGSEGV
*** This bug is a duplicate of bug 905686 ***
https://bugs.launchpad.net/bugs/905686
** This bug is no longer a duplicate of bug 871020
nautilus assert failure: nautilus: ../../src/xcb_io.c:528: _XAllocID:
Assertion `ret != inval_id' failed.
** This bug has been marked a duplicate of
*** This bug is a duplicate of bug 905686 ***
https://bugs.launchpad.net/bugs/905686
Re-opening: this is the bug apport points you at, and I guess Sebastian
mixed up marking duplicates..
** Changed in: nautilus (Ubuntu)
Status: Invalid = Triaged
** This bug has been marked a
*** This bug is a duplicate of bug 905686 ***
https://bugs.launchpad.net/bugs/905686
I am marking it as a duplicate of a report from Ubuntu Precise
(development version).
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus
I have still experienced this buggy using gnome-terminal and its menubar
after upgrading to Ubuntu Precise.
I have fixed it now by installing any missing recommends, using sudo
apt-get install --fix-policy --install-recommends.
One or multiple of the packages this installed appears to have fixed
Victor, what are you experiencing? This bug is so messed up already and
there are quite some dupes which I and others do not consider to be
dupes really.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu.
*** This bug is a duplicate of bug 833675 ***
https://bugs.launchpad.net/bugs/833675
** This bug is no longer a duplicate of bug 844205
gnome-control-center crashed with SIGSEGV in
goa_oauth_provider_get_callback_uri()
** This bug has been marked a duplicate of bug 833675
*** This bug is a duplicate of bug 833675 ***
https://bugs.launchpad.net/bugs/833675
** This bug is no longer a duplicate of bug 844205
gnome-control-center crashed with SIGSEGV in
goa_oauth_provider_get_callback_uri()
** This bug has been marked a duplicate of bug 833675
*** This bug is a duplicate of bug 833675 ***
https://bugs.launchpad.net/bugs/833675
** This bug is no longer a duplicate of bug 844205
gnome-control-center crashed with SIGSEGV in
goa_oauth_provider_get_callback_uri()
** This bug has been marked a duplicate of bug 833675
*** This bug is a duplicate of bug 787465 ***
https://bugs.launchpad.net/bugs/787465
Try the workaround mentioned there (sudo apt-get purge appmenu-gtk
appmenu-gtk3), logout and login again.
** This bug has been marked a duplicate of bug 787465
View-Show MenuBar isn't working in 11.04 and
*** This bug is a duplicate of bug 787465 ***
https://bugs.launchpad.net/bugs/787465
** This bug has been marked a duplicate of bug 787465
View-Show MenuBar isn't working in 11.04 and later in gnome-terminal
--
You received this bug notification because you are a member of Ubuntu
Desktop
The workaround is to uninstall/purge appmenu-gtk and appmenu-gtk3 (if present).
This package also contains the /etc/X11/Xsession.d/80appmenu* files.
@Jeremy: when appmenu-gtk is uninstalled, gnome-terminal behaves
properly (regarding the Show menubar by default setting), at least for
me.
**
Try if the workaround for bug 787465 fixes it for you (sudo apt-get
purge appmenu-gtk appmenu-gtk3, re-login).
Might be caused by the same menu proxy.
** Changed in: gnome-terminal (Ubuntu)
Status: New = Incomplete
** Changed in: gnome-terminal (Ubuntu)
Importance: Undecided = Medium
** Visibility changed to: Public
** Changed in: gnome-terminal (Ubuntu)
Status: New = Triaged
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/852219
Title:
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/840313
Title:
gnome-terminal crashed with SIGSEGV in gdk_property_change()
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-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/838765
Title:
gnome-terminal crashed with SIGSEGV in g_type_check_instance_cast()
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-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/741728
Title:
gnome-terminal crashed with SIGABRT in raise()
To manage notifications about
Crashed out of the blue Is not reproducible.
Marking Confirmed according to duplicate.
** Changed in: gnome-terminal (Ubuntu)
Status: Incomplete = Confirmed
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/722064
Title:
gnome-terminal crashed with SIGSEGV in g_type_check_instance_cast()
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-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/750187
Title:
gnome-terminal crashed with SIGSEGV in __strlen_sse42()
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-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/827239
Title:
gnome-terminal crashed with SIGSEGV in g_type_check_instance_cast()
To manage
Might be related to handling of the menu (which would occupy one row).
Please note that it appears to be buggy in some regards, so it might even
consume one row although it's not being displayed. See also bug 863309.
** Changed in: gnome-terminal (Ubuntu)
Status: New = Triaged
--
You
** This bug is no longer a duplicate of bug 787465
View-Show MenuBar isn't working in 11.04 and later
** Summary changed:
- Menubar always shown by default (although deactivated)
+ Menubar always shown by default (although deactivated) (after upgrade)
--
You received this bug notification
*** This bug is a duplicate of bug 863309 ***
https://bugs.launchpad.net/bugs/863309
** This bug has been marked a duplicate of bug 863309
Menubar always shown by default (although deactivated)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
*** This bug is a duplicate of bug 863309 ***
https://bugs.launchpad.net/bugs/863309
** This bug has been marked a duplicate of bug 863309
Menubar always shown by default (although deactivated) (after upgrade)
--
You received this bug notification because you are a member of Ubuntu
I am closing this as Fix released, if it's fixed indeed.
However, it is not fixed in my current setup, where I've upgraded from Natty.
This is better handled in bug 863309 though.
** Changed in: gnome-terminal (Ubuntu)
Status: Incomplete = Fix Released
--
You received this bug
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/864871
Title:
gnome-terminal crashed with SIGSEGV
To manage notifications about this bug go
I've noticed that toggling the menubar on and off reduces the height of
the window (real screen estate and according to $LINES) by one line.
** Changed in: gnome-terminal (Ubuntu)
Status: Confirmed = Triaged
--
You received this bug notification because you are a member of Ubuntu
Desktop
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/863046
Title:
gnome-terminal crashed with SIGSEGV in gtk_menu_item_set_submenu()
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-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/852408
Title:
gnome-terminal crashed with SIGABRT in __kernel_vsyscall()
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-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/849695
Title:
gnome-terminal crashed with SIGSEGV in gdk_property_change()
To manage
JFI: you can check this using:
% echo $COLUMNS x $LINES
80 x 22
Enabling/disabling the menu bar changes the $LINES. Everytime I toggle
the bar on and off, I get one line less, currently 18 only.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
Thank you for your report.
Do you have both nautilus-open-terminal and ubuntuone-client-gnome
installed?
If so, this would be a duplicate of bug 865115 and you could work around
it by uninstalling one of the packages to work around this.
Please report back here. Thanks.
** Changed in: nautilus
*** This bug is a duplicate of bug 865115 ***
https://bugs.launchpad.net/bugs/865115
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11.10.2011 13:37, crtm wrote:
Daniel Hahler (blueyed), i'm unistall only nautilus-open-terminal.
(then, nautilus work fine (ubuntuone-client-gnome work
** Changed in: gnome-terminal (Ubuntu)
Importance: Low = Medium
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/863309
Title:
Menubar always shown by default (although
This appears to be caused by some settings when upgrading from Natty: a
virtualbox instance, which was installed from Oneiric (beta) straight,
has a properly behaving gnome-terminal.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
This has landed in Oneiric:
gnome-settings-daemon (3.2.0-0ubuntu5) oneiric; urgency=low
[ Rodrigo Moya ]
* debian/patches/00git_avoid_undesired_sleeps.patch:
- Avoid sleeping the computer when disabled (LP: #864479) and ditto for
the display (LP: #863038)
[ Marc Deslauriers ]
** Changed in: gnome-terminal (Ubuntu)
Importance: Undecided = Low
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/863309
Title:
Menubar always shown by default (although
** Changed in: gnome-screensaver (Ubuntu)
Importance: Undecided = Wishlist
** Changed in: gnome-screensaver (Ubuntu)
Status: Confirmed = Triaged
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu.
The --poke option is unknown to gnome-screensaver-command in Oneiric,
and xscreensaver-command is not installed.
--
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/805386
vlc appears to use both xscreensaver-command -deactivate and
gnome-screensaver-command --poke.
(Source: modules/misc/inhibit/xscreensaver.c).
** Changed in: vlc (Ubuntu)
Status: Confirmed = Triaged
** Changed in: vlc (Ubuntu)
Importance: Undecided = Medium
** Also affects:
--poke has been removed in gnome-screensaver 2.91.91: Remove --poke
option from the commandline tool (didn't work anyway)
I assume it broke during the transition to Gnome 3?!
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
There appears to be a fix upstream in xdg-utils already since March:
http://cgit.freedesktop.org/xdg/xdg-utils/commit/?id=666d65cae0f2e66d33ec0dc48c054afbf16c9e3f
** Bug watch added: freedesktop.org Bugzilla #29860
http://bugs.freedesktop.org/show_bug.cgi?id=29860
** Also affects:
xdg-utils calls gnome-screensaver-command --poke, via:
case $1 in
suspend)
screensaver_suspend_loop gnome-screensaver-command --poke
result=0
;;
** Changed in: xdg-utils (Ubuntu)
Status: Confirmed = Triaged
** Changed in: xdg-utils (Ubuntu)
From looking at the strace -f output for vlc, it appears that
xdg-screensaver is being called, but ends with xscreensaver-command: no
screens.
Then gnome-screensaver-command is used next then.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
** Patch added: xdg-utils_1.1.0~rc1-2ubuntu6.dsc.debdiff
https://bugs.launchpad.net/xdg-utils/+bug/805386/+attachment/2501712/+files/xdg-utils_1.1.0%7Erc1-2ubuntu6.dsc.debdiff
** Changed in: gnome-screensaver (Ubuntu)
Status: New = Invalid
--
You received this bug notification
Public bug reported:
Although I have deactivated the option Show menubar by default in new
terminals [1], it gets shown for new terminals (and has to be activated
and deactivated via the View menu to hide it).
1: this option in located in the Profile Preferences (in the Edit
menu)
ProblemType:
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/863309
Title:
Menubar always shown by default (although deactivated)
To manage notifications about this bug go to:
@FernanAguero: this bug is about a particular issue, do not request something
else here.
@Sergey: the original bug's problem still persists.
I will re-open this, because it regressed, at least for Natty.
I guess
https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/437429/comments/102
explains it
Sorry, will close this again: the GUI is there after all, and it's just
that you have enable and then disable it to make it work.
See bug 778569 about that.
** Changed in: gdm (Ubuntu)
Status: Triaged = Fix Released
--
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 675918 ***
https://bugs.launchpad.net/bugs/675918
Thanks for your bug report and investigation. I can confirm this for
Natty.
It looks like just the default state is handled improperly for this
checkbox (until it gets saved once).
The following comment may
*** This bug is a duplicate of bug 675918 ***
https://bugs.launchpad.net/bugs/675918
** This bug has been marked a duplicate of bug 675918
Login sound plays when 'Play login sound' is un-checked
* You can subscribe to bug 675918 by following this link:
** Changed in: gdm (Ubuntu)
Status: New = Triaged
** Changed in: gdm (Ubuntu)
Importance: Low = Medium
--
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/675918
Title:
Login
@spencerrecneps: you are seeing bug 778569 - you have to check and then
uncheck the box to make it stick.
--
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/560061
Title:
Play login sound
*** This bug is a duplicate of bug 675918 ***
https://bugs.launchpad.net/bugs/675918
There is a separate place to configure the sounds for the login manager
(gdm), and it is affected by a bug where you have to check and uncheck
the box once to make it stick.
See bug 778569.
** This bug has
@ogra: has this regressed (in Natty)?
Although I have selected Blank screen with When laptop lid is closed in the
On AC Power the screen does not get locked when closing the lid. The same
with the On Battery Power tab.
--
You received this bug notification because you are a member of Ubuntu
I have tried it with both /apps/gnome-power-manager/lock/blank_screen
and /apps/gnome-power-manager/lock/use_screensaver_settings enabled: the
screen appears to get locked only after the screensaver kicks in, not
when closing the lid.
I have set the lid action to Blank screen in
** Changed in: glib2.0 (Ubuntu)
Status: New = Triaged
** Changed in: glib2.0 (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/757866
Public bug reported:
Is it expected that gsettings will use the memory backend?
From the extra message I do not think so, and it may be the reason why I
cannot change this whitelist or the changes to the Unity starter are not being
remembered through re-logins.
% gsettings get
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/757866
Title:
gsettings uses the 'memory' GSettings backend / settings do not
stick?!
--
desktop-bugs mailing list
Public bug reported:
Binary package hint: gnome-control-center
When setting up a global shortcut via gnome-keybinding-properties (e.g.
`gnome-terminal`), the application started from there will not have the
environment set up to work with gnome-keyring-daemon ($SSH_AUTH_SOCK is
missing).
When
** Bug watch added: Debian Bug tracker #339785
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=339785
** Also affects: gnome-control-center (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=339785
Importance: Unknown
Status: Unknown
** Also affects: gnome-keyring
1 - 100 of 261 matches
Mail list logo
