Referring to comment #2, a sentence could be added to the documentation,
and/or the tool-tip could be updated.
--
favorite status message feature is not documented
https://bugs.launchpad.net/bugs/580882
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
By documentation, I refer to the content shown by the Help program
that opens when I click the Help -- Contents menu in Empathy.
Sure, this whishlist item could be reported upstream.
--
favorite status message feature is not documented
https://bugs.launchpad.net/bugs/580882
You received this
** Changed in: empathy (Ubuntu)
Status: Incomplete = New
--
favorite status message feature is not documented
https://bugs.launchpad.net/bugs/580882
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to empathy in ubuntu.
--
Public bug reported:
Binary package hint: empathy
Use case: I am a user with some knowledge of IM, but facing empathy for
the first time, and I don't know what a favorite status is for. (How
can I use it? are my favourite statuses stored somewhere? Will other
people see my favorite statuses in a
Sorry for being incomplete. When I choose a custom status, a greyed-out
star appears close to it. A tool-tip says Click to make this status a
favorite. By experimenting (clicking on the star) I discovered that a
starred custom status gets put among the selectable statuses. If I un-
start that
I was affected by this bug, and I can confirm that on the remote machine
the ~/.dbus directory was owned by root. By changing the owner to
myself the problem is solved.
For some reason some people got the ~/.dbus ownership unwillingly
changed, can't tell in which package, but this is certainly a
Please, when this bug is fixed, also provide a way to revert the user
made workarounds.
For example, when fixing the bug, a pop-up window may say: If you
disabled compiz because of the flash bug, you can now safely re-enable
it. Or, for workaround 3, the package installer may silently modify the
I buy your point. Nevertheless, at least the users should be notified
when the problem will be solved (not only by marking this bug as
solved), so that they can revert their workarounds. Otherwise it is very
likely that the fix will go unnoticed and many workarounds will remain
in place
Actually, I can reproduce this bug even after I deleted my old
configuration (that is, when the default configuration is in place).
Steps to reproduce the bug on my system:
1) rm -r ~/.gconf/apps/panel/ # restore default configuration
2) killall gconfd-2 # make sure the new configuration is
I started having this bug by just removing the notification area. After
notification area was removed, gnome-panel started crashing, and now it
crashes every time it starts up.
Attached please find my .xsession-errors.
Please note that this bug is currently making my system completely
unusable
I do have a dual screen config, but accessibility options are not
enabled anywhere.
As a work around, I just deleted everything under ~/.gconf/apps/panel/,
then restarder gconf2-d. That solved the problem by restoring the
panel to the pristine default condition. Accidentaly, this also solved
the
11 matches
Mail list logo
