The documentation patch is wrong. Notification is a client/server
infrastructure, and it is up to the server to respect or ignore certain
client requests (such as timeout settings, amonst others). The man page
of the client cannot possibly know which server the user is using. Thus,
currently
I had positive reports from users that were using libindicate 0.5, so
it's now picked up upstream.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/715257
Title:
multi-notification plugin indicator
Sounds better, doesn't it?
No, it does not. At least not to me. If you think talking to people like
that is good, we'll see how far that gets you. Good luck.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
It's not necessary anymore in this case, but for future reference: If
it's not a distribution-issue but an upstream change in the library that
causes these kinds of problems (as in this case with the .pc file
rename), it would be nice to notify upstream of the library user (i.e.
Claws Mail)
I can't install libindicate 0.5 right now, but if somebody can confirm
that it is compatible to 0.4 I'll add support for it to the build
system.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/715257
@Adrian Roman:
what you say below about being the controlling jerk
What you might have not realized is that this phrase was a quote from
comment #168. But I'm glad we agree that this is not a nice way to
communicate.
The point is: If somebody agues that if developers for project xy don't
add
@Mike Hartman: I told you already in comment #158 where that deeply
buried configuration option in a text file somewhere is that lets you
choose your notification daemon.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Mike Hartman: I don't see anyone forcing you to do anything. I was
merely suggesting a way to solve the problem you and others here seem to
be facing. Clearly, you're not interested in selecting a suitable daemon
out of the many that exist - including a modified notify-osd ppa that
does exactly
The Wastebasket has no way to sort by deleted date.
If it did, then this improvement would be a lot less urgent, IMHO
Please read what I wrote. Quoting myself:
In fact, current Nautilus git master has trashed-on column in list view, and
(irrespective of the view) sorts the trashcan by reversed
That's a pretty ridiculous thing to suggest to developers planning to
distribute their code
If you plan to distribute something, you'll have to live with the
lowest-common-denominator problem, and cannot rely on implementation
details. Just like everywhere else.
I don't see how it's ridiculous
The open source philosophy has nothing to do with configurability,
options, or features. I wonder where that idea comes from.
--
notify-send ignores the expire timeout parameter
https://bugs.launchpad.net/bugs/390508
You received this bug notification because you are a member of Ubuntu
Bugs,
The first line of the Desktop Notifications Specification says
In my copy, the first line says that it is a draft (!) document for
async event notifications.
The first line of the Desktop Notifications Specification says,
The following messages MUST be supported by all implementations.
There
The always_use_location_entry gconf key does not determine whether the
location bar is visible or not, it just toggles between breadcrumb
navigation and text entry. The visibility itself is set by View -
Location Bar.
--
path location bar of Nautilus doesn't appear by default when configured so
Suppose that you have 1500+ items in your trash bin.
You pressed DEL without noticing which file it was.
A warning for every single move-to-trash operation to fix this
problematic usecase is implementing a cruel workaround instead of fixing
the issues (in this case trash view usability). In
...so, how does one create one of these instant-confirmation bubbles?
The design spec for notify-osd has been linked several times in the comments of
this report. I'll paste the link again for your convenience, even though usage
questions seem off-topic in a bug tracker:
@Walter_I
In my oppinion, David Siegel's remark is absolutely correct, and you are wrong.
It's not as simple as you put it. Whether or not copying in parallel takes
significantly longer depends on a number of factors (is target and/or source on
a slow network connection, am I copying from a CD
@Darshaka Pathirana:
How can you full ACK a statement that you oppose in your very next sentence?
Walter proposed to ALWAYS queue files, which is definitely not a good idea. Do
something more than just always process in parallel or always queue, be it to
ask the user, have some smart logic or a
@Heather Van Wilde
To do what you recommend, any application would have
to create their own notification system to do exactly what
notify-osd does, but is unable to interact with it.
No, that's not true. You can trust me on that - as it happens, I wrote
notification spec integration for
@Airton Torres:
Fiddling with timeouts sounds like an exceptionally strange way to solve
that particular issue. So, you'd still like to have tens or hundreds of
bubbles, flickering unreadably on your screen with short timeouts?
Doesn't make any sense to me.
Developers already have a way to avoid
@Adrian Roman:
Weird analogy. You can do the same with notify-osd as you can do with other
default applications: Replace it with an alternative from the repository if you
don't like the feature set. notification-daemon would be an alternative to
notify-osd that offers the features you want. Why
Guys, you just don't seem to get that notify-osd is about unification
and consistency amongst applications using it. It's fundamental design
point is to NOT allow applications to use it in different ways, and also
not to let the user configure it extensively. In this light, what you
request as a
Totally wrong
No, it's not. Denying reality may be fun, but it's not helpful. I was not
talking about what you'd like, but about what notify-osd is aiming at. It is
part of project Ayatana, and here's a statement about configurability in that
project:
Patrick: Your assumption is wrong to start with. The bug is not in GTK+,
but in Eclipse.
Starting from 2.18 on, GTK+ changed some of its internal behaviour
(google for client side windows). This change is intentional, and
needed for other development. It doesn't make any difference to programs
Ubuntu folks can't fix bugs in software that you download from
eclipse.org or zend.org. It's up to them to fix the software they offer.
The Eclipse package in the repo contains the workaround, and I don't see
what else could possibly be done on Ubuntu's side.
--
Buttons in Eclipse not working
@kikl: Completely unrelated to whether it's a good idea to get undo
dialogs/bars on moving to trash or not, Nautilus's trash display does
indeed have poor usability. No deletion date grouping, sorting or even
displaying. Also, one can't really know where the files are going to be
restored to. That
I think Nautilus' behaviour is correct. The behaviour is by design, and
the confirm_trash option is doing what it is supposed to do: Request
confirmation for the non-revertable actions Delete Trash and Delete
files, but not for the revertable Move to trash. And guys, please
stop speaking for the
The bug description reveals a misunderstanding of the permissions
system. File creation and deletion are operations on the _containing
directory_ and are affected by the permissions set on that directory.
You can create and delete files if you have +w on the parent directory.
File permissions, on
The upstream bug was http://bugzilla.gnome.org/show_bug.cgi?id=577139,
and it's fixed in the repo.
Nautilus still doesn't allow extensions to register shortcuts (which has
conflict potential with builtin shortcuts or other extensions), but now
users can assign a shortcut themselves.
** Bug watch
Both patches have been accepted, and will be included in the next
Nautilus version (likely already the one shipping with Gnome 2.26.1, due
in a few days).
--
Modified keyboard shortcuts not remembered
https://bugs.launchpad.net/bugs/151407
You received this bug notification because you are a
You're right that Nautilus doesn't save and restore the keyboard
shortcuts across restarts. You may call that a missing feature. I've
sent a patch to implement this (and a related feature: the ability to
assign keyboard shortcuts to scripts) to the Nautilus list. We'll see if
it gets accepted.
--
Hi Mike,
maybe I have a fundamental misunderstanding of how things work here, but
I can't really follow your reasoning.
Support means that individual packages get updates and fixes when
security issues have been discovered.
The various kinds of Ubuntu flavors are just different in installer
Public bug reported:
LTS versions of the Ubuntu server edition is advertised with 5 years of
support (security updates), while the desktop edition features 3 years
of support.
Now, since server and desktop edition share the same repositories, how
do I know whether my installation only consists
Submitted upstream (Bug #504049 in GNOME bugzilla)
--
Inconsistency with Nautilus dragdrop and ACL
https://bugs.launchpad.net/bugs/137458
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
Public bug reported:
Binary package hint: nautilus
I am using Nautilus in connection with Eiciel for ACL support (what is
the status of Nautilus' native ACL support anyways? I heard it should be
there from GNOME 2.16 on...). When I copy a directory with files from a
partition that was not
Thanks for your efforts, Scott.
--
poker2d crashes during startup
https://bugs.launchpad.net/bugs/126268
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Thanks. I cannot test Gutsy right now, so I can not yet confirm that
this problem is fixed. Would it be possible to upload the fixed version
to Feisty also? After all, Feisty is current stable, and poker-network
is not usable on it with that bug.
--
poker2d crashes during startup
Public bug reported:
On a fresh install of python-poker2d, during startup of poker2d, I can
see the main window appearing and immediately disappearing again.
Started from a console, the following traceback is reported:
Traceback (most recent call last):
File
Public bug reported:
Binary package hint: aqbanking16-qt-wizard
When I try to set up a new user with the AqBanking QT Wizard, it dumps core.
The bahavior is repeatable. Steps for me to reproduce:
Start the wizard
User - New user
HBCI backend
Setup PIN/TAN
Enter bank and user information (tried
It seems like it can't connect to my bank server. The bank server
hostname was auto-filled in after I entered the bank number and chose my
bank (with online banking) from the list.
Output of
$ LANG=C /usr/lib/aqbanking/plugins/16/wizards/qt3-wizard 2 stderr.log
is attached.
** Attachment
** Attachment added: $ strace /usr/lib/aqbanking/plugins/16/wizards/qt3-wizard
2 strace.log
http://librarian.launchpad.net/7054061/strace.log.bz2
--
Core dump when setting up new user.
https://launchpad.net/bugs/98896
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Backtrace obtained with gdb
** Attachment added: Backtrace
http://librarian.launchpad.net/7054062/backtrace.log
--
Core dump when setting up new user.
https://launchpad.net/bugs/98896
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
The auto-filled in bank server was not completely correct. The wizard
works fine if the correct address is manually filled in, so this is not
a major bug. Still, it should not crash in case of an incorrect server
address.
--
Core dump when setting up new user.
https://launchpad.net/bugs/98896
What exactly was fixed for Feisty? I have an up-to-date Feisty, and I
still can't use HBCI from GnuCash. There just doesn't seem to be any
menu item connected to HBCI.
--
HBCI banking doesn't work due to dependency problems (aqbanking problem)
https://launchpad.net/bugs/31789
--
ubuntu-bugs
Public bug reported:
Binary package hint: fast-user-switch-applet
On Feisty, since a recent upgrade, the fast user switch applet causes
50% processor load on my AMD64 dual core when it is added to a gnome
panel.
** Affects: fast-user-switch-applet (Ubuntu)
Importance: Undecided
I had the same problem as the original poster on an AMD64. Since a
recent update, however, I don't have a splash screen at all anymore. The
screen remains dark (with a blinking cursor in the top left corner)
during startup and shutdown of the computer. Everything works fine, just
the splash does
I assume this is with feisty, as I have the same issue on feisty.
Yes, this is on feisty indeed, sorry for not mentioning it before. It is
a Herd 1 installation, kept up-to-date with apt-get.
--
usplash appears black and white (grayscale) on amd64
https://launchpad.net/bugs/67545
--
I can confirm this behavior. The sources - window closes immediately
after selecting it from Synaptic. This is on a fresh Feisty install
(with Herd 1) on AMD64.
--
Software Sources Window Closes Upon Opening
https://launchpad.net/bugs/71983
--
ubuntu-bugs mailing list
Public bug reported:
See http://trac.galago-project.org/ticket/86 for a problem description
and a patch.
Possible solutions:
- apply the patch from above bug report
- upgrade to 0.4.3 (where this patch is already included)
** Affects: libnotify (Ubuntu)
Importance: Undecided
48 matches
Mail list logo
