Moving this to gtk+3.0. I believe it is gtk 3 specific. It is not just
limited to gedit, it happens with any app using indicator-appmenu (I
notice it most often under okular on pdfs with lots of bookmarks). But
it is also not indicator-appmenu specific because the following code,
when run with:
Public bug reported:
It appears if enabling the upstart user session (
https://wiki.ubuntu.com/RaringRingtail/ReleaseNotes#Upstart_User_Sessions_.28technology_preview.29
) there is a race between gnome-session and upstart for who starts
gnome-settings-daemon first.
Most of the time on my system,
Ah, in that case this may just be a bug with my setup.
$HOME/.config/autostart/ is likely read before any of those directories,
and I have a copy of gnome-settings-daemon.desktop in there. Thanks for
the information. I'll delete it and continue testing, but this bug is
probably invalid.
--
You
I think I worked out at least part of the problem, so might not be a
gnome-control-center bug after all. gnome-control-center uses the
mimetype video/x-ogm+ogg to determine the default Video app in Default
Applications. SMplayer does not have this mimetype in its
smplayer.desktop file, but instead
Hi Sam,
Yes the COMPIZ_CONFIG_PROFILE environment variable is still used, but if
unset or the empty string compiz first checks GNOME_DESKTOP_SESSION_ID,
which in quantal is currently set to 'this-is-deprecated'. If it is set,
then it returns the section name as gnome_session. Doesn't really
Alright, ideally I would use gsettings, but I cannot figure out how to
set up the default plugins without running some sort of script in the
user session to set the keys if they are not already set.
So, my thought is that we can just use the ini backend but with the
attached patch to
I noticed that when loading ccsm in the gnome classic session it
outputs:
Backend: ini
I can force it to use the gsettings backend by adding:
[gnome_session]
backend = gsettings
profile = Default
to /etc/compizconfig/config, but it will just load the unity active-
plugins from
Though it does work with the gsettings backend if the settings are set
at the user level with either ccsm or:
gsettings set org.compiz.core:/org/compiz/profiles/Default/plugins/core/
active-plugins
['core','composite','opengl','decor','move','imgpng','place','resize'];
So I guess it is just from
Updated the debdiff, forgot to bump the gtk+3.0 build-depends to 3.5.13
for the new gtk_entry_set_attributes() function in the patch.
** Patch added: gnome-control-center_fix-big-editable-labels-v2.debdiff
Attaching a debdiff with the upstream commit that fixes the issue.
** Patch added: gnome-control-center_fix-big-editable-labels.debdiff
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1041756/+attachment/3305931/+files/gnome-control-center_fix-big-editable-labels.debdiff
Thanks for the bug report. I found an upstream bug here:
https://bugzilla.gnome.org/show_bug.cgi?id=668035 and I submitted a
simple patch to fix it.
You can workaround the issue by manually adding:
info
packagePACKAGENAME/package
versionVERSION/version
revisionREVISION/revision
/info
to the
Thanks for the bug report. However, I cannot reproduce this bug. I am
going to move this to gnome-control-center. Can you add the output of:
apt-cache policy gnome-control-center;
Maybe you have a PPA overriding the default package. A screenshot of the
Appearance dialog may also be helpful.
One more idea, try running in a terminal:
XDG_CURRENT_DESKTOP=Unity gnome-control-center;
It will only show that option in a unity session, but maybe your
XDG_CURRENT_DESKTOP environment variable is overwritten somewhere. If
the above works, check:
echo $XDG_CURRENT_DESKTOP;
--
You received
Thanks for the screenshots. It turns out I am able to reproduce this in
the unity-2d session. Bug #1005136 is about adding the option for that
session.
Please check:
echo $DESKTOP_SESSION;
to see if you are running the ubuntu-2d session. If so, either try the
Ubuntu session or there are
CTRL+D sends EOF to the shell, indicating the end of input, so the shell
exits, which causes gnome-terminal to exit. You can verify this by
running another bash session in the terminal:
bash
then press CTRL+D. That instance of bash will exit but gnome-terminal
will remain open. Another example,
Have you tested this since the updates to glib 2.32 and gtk 3.4? I
marked this as confirmed last night since I could reproduce it
consistently, but since the updates today, I can no longer reproduce the
issue.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
This is fixed in 3.3.8-0ubuntu1.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/917071
Title:
gedit crashed with SIGSEGV in
_gtk_tree_selection_internal_select_node()
To manage
It isn't limited to gedit, but seems to affect any GtkTreeView. I
believe it is fixed upstream though:
http://git.gnome.org/browse/gtk+/commit/gtk/gtktreeview.c?id=022c576bd2764dc1fc48e46ad97aa95287c175cc
Rebuilt gtk with the patch and I can't reproduce the crash.
** Also affects: gtk+3.0
Looks like this is the same bug as in
https://bugs.launchpad.net/ubuntu/+source/ubuntuone-client/+bug/908787
--
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/910195
Title:
nautilus
Found the problem, it is actually caused by ubuntuone-client
(specifically libsyncdaemon). Due to a recent change from bug #859635 ,
the library is registering a dbus message marshaller for VOID__POINTER,
however the type registered is actually VOID__BOXED, which happens to be
the same type as
I can reproduce this in precise as well. Here is a slightly better
backtrace:
1) gdb nautilus
2) run Computer://
3) Double click a partition in the nautilus window
4) Following backtrace:
(gdb) run Computer://
Starting program: /usr/bin/nautilus Computer://
[Thread debugging using libthread_db
*** This bug is a duplicate of bug 817944 ***
https://bugs.launchpad.net/bugs/817944
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug #817944, so it is being marked as such. Please look
** Changed in: alacarte (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to alacarte in Ubuntu.
https://bugs.launchpad.net/bugs/800215
Title:
alacarte object has no attribute 'startswith'
To
Marking this as confirmed. The gnome-menus package includes a patch that
renames /etc/xdg/menus/applications.menu to gnome-applications.menu.
Including a minimal patch that allows alacarte to run. However it is
possible for tree.get_menu_file() to return None if both ~/.config/menus
Marking as confirmed. Rebuilt with the following patch, which just
renames all of the applications.menu references, and it seems to be
working.
** Patch added: panel-rename-menu.patch
Public bug reported:
Binary package hint: gedit
In Maverick gedit-2.30.3-1ubuntu1:
When configuring the Python Console plugin, changing the Command Color
results in a python NameError:
Traceback (most recent call last):
File /usr/lib/gedit-2/plugins/pythonconsole/config.py, line 129, in
** Patch added: gedit-pythonconsole-gconf.patch
https://bugs.launchpad.net/bugs/654867/+attachment/1672331/+files/gedit-pythonconsole-gconf.patch
** Attachment added: Dependencies.txt
https://bugs.launchpad.net/bugs/654867/+attachment/1672332/+files/Dependencies.txt
--
gedit python
27 matches
Mail list logo
