Are there any reasons not to move the panel to the top in GDM? The
consistency with the desktop could be increased even more by making the
panel (as well as the login pane) dark, since this is the default
setting for the desktop (Ambiance). This is of less importance than the
position, though.
I
Marking the bug as fixed as the ordering of properties in UI files seems
to be permanent in Natty.
** Changed in: glade-3 (Ubuntu)
Status: Triaged = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glade-3 in
Closing the bug report as it cannot be reproduced anymore in Maverick.
This probably applies to some of the previous releases as well. Besides,
LottaNZB has dropped support for Intrepid long ago.
** Changed in: pygtk (Ubuntu)
Status: Triaged = Invalid
** Changed in: pygtk (Ubuntu)
A bug fix seems to have been committed upstream, but it isn't present in
the Maverick package as the bug can still be reproduced. I'll update the
report as soon as I'll be testing Natty.
** Bug watch added: GNOME Bug Tracker #628253
https://bugzilla.gnome.org/show_bug.cgi?id=628253
** Changed
** 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/701875
Title:
rhythmbox assert failure: *** glibc detected *** rhythmbox:
munmap_chunk():
Unfortunately, the crash doesn't occur when running Rhythmbox using
Valgrind. It does when launching it with GDB, but the resulting
information has already been added to the bug report and is thus not
particularly useful. Marking the bug as 'Incomplete'.
** Changed in: rhythmbox (Ubuntu)
Public bug reported:
Binary package hint: glade-3
When saving a glade file that contains a button or a menu item based on
an action but overriding its appearance, the following line will,
erroneously, *not* be part of the file:
property name=use_action_appearanceFalse/property
But unless this
In the following demo, the button will have the label The label of the
GtkAction, unless property
name=use_action_appearanceFalse/property is added manually to
demo.ui. This very line will be lost when loading and saving demo.ui
using glade the next time.
** Attachment added: demo.ui
** Attachment added: demo.py
http://launchpadlibrarian.net/53244382/demo.py
** Description changed:
Binary package hint: glade-3
When saving a glade file that contains a button or a menu item based on
an action but overriding its appearance, the following line will,
erroneously,
** Bug watch added: GNOME Bug Tracker #626328
https://bugzilla.gnome.org/show_bug.cgi?id=626328
** Also affects: glade-3 via
https://bugzilla.gnome.org/show_bug.cgi?id=626328
Importance: Unknown
Status: Unknown
--
'use_action_appearance' property changes location when saving
** Bug watch added: GNOME Bug Tracker #626330
https://bugzilla.gnome.org/show_bug.cgi?id=626330
** Also affects: glade-3 via
https://bugzilla.gnome.org/show_bug.cgi?id=626330
Importance: Unknown
Status: Unknown
--
'translatable' property of GtkAction labels lost when saving
The bug has been reported upstream.
** Bug watch added: GNOME Bug Tracker #626332
https://bugzilla.gnome.org/show_bug.cgi?id=626332
** Also affects: glade-3 via
https://bugzilla.gnome.org/show_bug.cgi?id=626332
Importance: Unknown
Status: Unknown
--
Impossible to override
The bug has been forwarded upstream.
--
'use_action_appearance' property changes location when saving file
https://bugs.launchpad.net/bugs/612383
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glade-3 in ubuntu.
--
desktop-bugs
The bug has been forwarded upstream.
--
'translatable' property of GtkAction labels lost when saving
https://bugs.launchpad.net/bugs/612374
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glade-3 in ubuntu.
--
desktop-bugs mailing list
Public bug reported:
Binary package hint: glade-3
When using objects of type GtkAction in a GtkBuilder file, the attribute
'translatable' of 'label' properties is reproducibly lost when saving
the file using glade. This is extremely annoying as those attributes
need to be restored manually in a
** Attachment added: demo.ui
http://launchpadlibrarian.net/52839509/demo.ui
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/52839369/Dependencies.txt
--
'translatable' property of GtkAction labels lost when saving
https://bugs.launchpad.net/bugs/612374
You received
Public bug reported:
Binary package hint: glade-3
When saving a GtkBuilder UI file, 'use_action_appearance' properties (or
'related_action', respectively) reproducibly change their position in
the list of properties of widgets related to a GtkAction. This is
annoying because it clutters diffs
** Attachment added: demo.ui
http://launchpadlibrarian.net/52841817/demo.ui
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/52841644/Dependencies.txt
** Description changed:
Binary package hint: glade-3
- After applying changes to a GtkBuilder UI file,
** Changed in: lottanzb (Ubuntu Lucid)
Importance: Undecided = Medium
** Changed in: lottanzb (Ubuntu Lucid)
Status: New = Fix Released
** Changed in: lottanzb (Ubuntu Lucid)
Assignee: (unassigned) = Severin Heiniger (lantash)
--
Widget names not set when using GtkBuilder
https
I can confirm this bug on Lucid with the latest version of rhythmbox
(0.12.7-0ubuntu7) installed.
@kristoffer: The problem is not related to the locale used of your
system, as it can also be reproduced when launching rhythmbox in English
using LANGUAGE=C rhythmbox.
** Changed in: rhythmbox
** Changed in: lottanzb (Ubuntu)
Status: Triaged = Fix Released
--
Widget names not set when using GtkBuilder
https://bugs.launchpad.net/bugs/507739
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gtk+2.0 in ubuntu.
--
*** This bug is a duplicate of bug 507739 ***
https://bugs.launchpad.net/bugs/507739
This bug has been fixed in LottaNZB 0.5.3. Unfortunately, the package
hasn't arrived in Ubuntu 10.04 yet. For the time being, you can install
the package provided at http://www.lottanzb.org/downloads/ubuntu/.
** Changed in: lottanzb
Status: Fix Committed = Fix Released
--
Widget names not set when using GtkBuilder
https://bugs.launchpad.net/bugs/507739
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gtk+2.0 in ubuntu.
--
desktop-bugs
*** This bug is a duplicate of bug 507739 ***
https://bugs.launchpad.net/bugs/507739
There's an error in the commands mentioned above. If you're interested
in running LottaNZB on Ubuntu 10.04 at this point of time, you should
enter:
bzr branch lp:lottanzb/0.5
cd 0.5
./run-lottanzb.sh
**
** Changed in: lottanzb (Ubuntu)
Status: Invalid = Won't Fix
** Changed in: lottanzb (Ubuntu)
Status: Won't Fix = Triaged
** Changed in: lottanzb (Ubuntu)
Importance: Undecided = Medium
** Changed in: lottanzb (Ubuntu)
Assignee: (unassigned) = Severin Heiniger (lantash
*** This bug is a duplicate of bug 507739 ***
https://bugs.launchpad.net/bugs/507739
You're welcome. I'm not the only LottaNZB developer, but apparently the
one with the least number of hobbies beside LottaNZB. :-P
--
lottanzb crashed with AttributeError in _autoconnect_by_method_name()
I can confirm that the patch works perfectly. Great work! Is there any
chance that this change will be uploaded to Ubuntu Karmic as a SRU? The
fact that the LottaNZB Inhibit suspending plug-in will only work on
Ubuntu 9.04 and 10.04 renders it useless for many people at this point
of time.
--
*** This bug is a duplicate of bug 507739 ***
https://bugs.launchpad.net/bugs/507739
There's no need to close the ticket as the bug has already been marked
as a duplicate. Thanks for giving the latest code a try! It's good to
hear that it works for you.
--
lottanzb crashed with
Thanks alot for taking care of this, Chris! I'll give the patch a try
tomorrow.
--
Inhibit suspending (flag 0x4) not working over DBus
https://bugs.launchpad.net/bugs/510907
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
After having a look at gnome-power-manager's source code, I also noticed
that gpm_manager_is_inhibit_valid is a stub. Implementing it also
requires gpm-session.c to be changed, because the term inhibited is
limited to the concept of session timeouts there. I tried to implement
it but
Reported upstream.
** Bug watch added: GNOME Bug Tracker #607748
https://bugzilla.gnome.org/show_bug.cgi?id=607748
** Also affects: gnome-power via
https://bugzilla.gnome.org/show_bug.cgi?id=607748
Importance: Unknown
Status: Unknown
--
Inhibit suspending (flag 0x4) not working
Public bug reported:
Binary package hint: gnome-session
While porting the Inhibit suspending LottaNZB plug-in (written in
Python) from the old org.freedesktop.PowerManagement.Inhibit API to the
new org.gnome.SessionManager API introduced in Karmic, I noticed that
after successfully passing the
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/38200394/Dependencies.txt
--
Inhibit suspending (flag 0x4) not working over DBus
https://bugs.launchpad.net/bugs/510907
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
I just ported the Python testcase to raw C code. The bug can also be
reproduced here. Everything is fine in Karmic, but in Lucid, the widget
names are not set.
This means that it's not actually a bug in PyGTK, but GTK itself.
--
Widget names not set when using GtkBuilder
C test-case. Compile it using
gcc testcase.c -Wall -o testcase `pkg-config --cflags --libs gtk+-2.0`
and make sure that 'testcase.ui' is in the same directory as 'testcase'
when executing it.
** Attachment added: testcase.c
http://launchpadlibrarian.net/38001124/testcase.c
** Also affects:
The bug has been reported upstream.
** Bug watch added: GNOME Bug Tracker #607221
https://bugzilla.gnome.org/show_bug.cgi?id=607221
** Also affects: gtk via
https://bugzilla.gnome.org/show_bug.cgi?id=607221
Importance: Unknown
Status: Unknown
--
Widget names not set when using
** Changed in: gtk+2.0 (Ubuntu)
Status: New = Invalid
** Changed in: pygtk (Ubuntu)
Status: New = Invalid
--
Widget names not set when using GtkBuilder
https://bugs.launchpad.net/bugs/507739
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
** Changed in: lottanzb
Status: Triaged = In Progress
** Changed in: lottanzb
Assignee: (unassigned) = Severin Heiniger (lantash)
** Changed in: lottanzb
Importance: Undecided = Critical
** Changed in: lottanzb
Milestone: None = 0.5.3
--
Widget names not set when using GtkBuilder
** Changed in: lottanzb
Status: In Progress = Fix Committed
--
Widget names not set when using GtkBuilder
https://bugs.launchpad.net/bugs/507739
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gtk+2.0 in ubuntu.
--
desktop-bugs
I'd be glad if someone confirmed the bug so that it could be forwarded
upstream.
** Also affects: pygtk (Ubuntu)
Importance: Undecided
Status: New
--
Widget names not set when using gtk.Builder
https://bugs.launchpad.net/bugs/507739
You received this bug notification because you are a
I know that me-too comments are not particularly useful, but I think
it's time to make this rather trivial change. Are there any valid
reasons that this hasn't been done in previous release cycles?
--
downloads should go to $HOME/Downloads : XDG_DOWNLOAD_DIR should be set to
$HOME/Downloads
Well, looks like I should have read the comments at
brainstorm.ubuntu.com. Are there any Ubuntu deverlopers (preferably
usability experts ;-)) who could say a word or two about this issue?
--
downloads should go to $HOME/Downloads : XDG_DOWNLOAD_DIR should be set to
$HOME/Downloads
This bug has somehow been fixed. As I mentioned above, LottaNZB works
just fine using Python 2.6.
** Changed in: lottanzb
Status: New = Invalid
** Changed in: pygobject (Ubuntu)
Status: Incomplete = Invalid
--
Segfault starting with 2.16.1-0ubuntu2 using Python 2.5
According to a message by Matthias Klose in ubuntu-devel, the Python
interpreter will be updated from 2.5.4 to 2.6 within the next days and
numerous packages will be rebuilt for that purpose. Since the bug only
affects Python 2.5 I assume that everything will be fine after the
transition. I'll
Public bug reported:
A few days ago, the development version of the PyGTK application
LottaNZB 0.5 (https://code.edge.launchpad.net/~lottanzb/lottanzb/main)
stopped working because of a segmentation fault during startup. I was
able to track down the problem:
2.16.1-0ubuntu1: Works fine both
Changelog of python-gobject_2.16.1-0ubuntu2:
https://edge.launchpad.net/ubuntu/jaunty/+source/pygobject/2.16.1-0ubuntu2
* Remove explicit dependencies on python2.5.
* Rename -dbg extensions for python2.6 as well. LP: #333557.
** Also affects: lottanzb
Importance: Undecided
Status:
I seem to have found a solution. Right now, the GObjectSingletonMeta
metaclass is part of the util module. Moving it to the core module where
it is actually used by the App class solved the problem. This is totally
weird.
I was able to create a simple script that demonstrates the problem.
demo.py
Forgot to remove unnecessary stuff from the demo.py file. Download this
one and not the one above.
** Attachment added: demo.py
http://launchpadlibrarian.net/23146820/demo.py
--
Segfault starting with 2.16.1-0ubuntu2 using Python 2.5
https://bugs.launchpad.net/bugs/334784
You received this
...and the demo_util.py file.
** Attachment added: demo_util.py
http://launchpadlibrarian.net/23146823/demo_util.py
--
Segfault starting with 2.16.1-0ubuntu2 using Python 2.5
https://bugs.launchpad.net/bugs/334784
You received this bug notification because you are a member of Ubuntu
Desktop
The most interesting thing about it is that the order of the three
import statements in demo.py has an effect on what happens:
# Finally leads to the segfault described in this bug report.
from kiwi.environ import Application
from gobject import property, GObject
from demo_util import
@Matthias:
I've downloaded the required files from
https://edge.launchpad.net/ubuntu/jaunty/+source/pygobject/2.16.1-0ubuntu1,
built it using dpkg-source -x and installed the package using dpkg
--install --force-all (which replaced the ubuntu2 version). Everything
was fine after this. Upgrading
lant...@gauss:~/Desktop$ python demo.py # Using 2.16.1-0ubuntu2.
Segmentation fault (core dumped)
lant...@gauss:~/Desktop$ sudo dpkg --install --force-all
python-gobject_2.16.1-0ubuntu1_amd64.deb
[...]
Vorbereiten zum Ersetzen von python-gobject 2.16.1-0ubuntu2 (durch
Sorry for bothering you once more. I'm not quite sure what to think
about it. In addition to the ubuntu1, I built the ubuntu2 pacakge by
myself a few minutes ago, and now it looks as if the application
segfaults if either the self-built ubuntu1 package (why did this work
before?!) or the official
** Attachment added: test_pygtk_crash.py
http://launchpadlibrarian.net/18289262/test_pygtk_crash.py
** Description changed:
As a developer of LottaNZB (a PyGTK app), I recently gave our
application a try on Ubuntu Intrepid, with the latest updates applied.
The application unexpectedly
** Attachment added: filechooser.glade
http://launchpadlibrarian.net/18289267/filechooser.glade
--
MRO error crash when accessing the 'focus_widget' property of a file selection
dialog
https://bugs.launchpad.net/bugs/279579
You received this bug notification because you are a member of
Filed upstream: http://bugzilla.gnome.org/show_bug.cgi?id=555384
--
MRO error crash when accessing the 'focus_widget' property of a file selection
dialog
https://bugs.launchpad.net/bugs/279579
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug
Public bug reported:
As a developer of LottaNZB (a PyGTK app), I recently gave our
application a try on Ubuntu Intrepid, with the latest updates applied.
The application unexpectedly crashed when opening the file selection
dialog with the following error message:
TypeError: Cannot create a
** Attachment added: CoreDump.gz
http://launchpadlibrarian.net/17888604/CoreDump.gz
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/17888605/Dependencies.txt
** Attachment added: Disassembly.txt
http://launchpadlibrarian.net/17888606/Disassembly.txt
** Attachment
This annoying bug in gvfs seems to be fixed now. Many thanks to the
developers who have been working on it.
--
gedit crashed with SIGSEGV in g_datalist_id_set_data_full()
https://bugs.launchpad.net/bugs/187766
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
** Description changed:
Evince starts with wild swapping and finally crashed on my machine when
Zooming
the attached PDF-File to 400%.
- http://bugzilla.gnome.org/show_bug.cgi?id=321138:
http://bugzilla.gnome.org/show_bug.cgi?id=321138
--
Evince crashes when zooming PDF-File to 400%
** Description changed:
Binary package hint: evince
- Evince does not seems to load normally, but can not display pdf file
- pages. Display space is blank.
+ Evince seems to load normally, but can not display pdf file pages.
+ Display space is blank.
ProblemType: Bug
Architecture:
I can confirm that this bug must have been introduced in a recent update
in Hardy. The keyboard layout settings behave quite strange at the
moment. The keyboard layout is resetted to the standard US layout after
every reboot although the layout manager still displays Switzerland.
To fix this
62 matches
Mail list logo
