*** This bug is a duplicate of bug 773686 ***
https://bugs.launchpad.net/bugs/773686
** This bug is no longer a duplicate of bug 668639
banshee lirc extension doesn't work
** This bug has been marked a duplicate of bug 773686
banshee-extension-lirc depends on wrong liblircclient library
*** This bug is a duplicate of bug 773686 ***
https://bugs.launchpad.net/bugs/773686
Yes, installing the liblircclient-dev package solves the problem.
Marking this bug as duplicate.
** This bug has been marked a duplicate of bug 773686
banshee-extension-lirc depends on wrong liblircclient
I can confirm this bug is still present in natty 11.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/668639
Title:
banshee lirc extension doesn't work
--
ubuntu-bugs mailing list
*** This bug is a duplicate of bug 668639 ***
https://bugs.launchpad.net/bugs/668639
** This bug has been marked a duplicate of bug 668639
banshee lirc extension doesn't work
* You can subscribe to bug 668639 by following this link:
I confirm the bug is still present with easytag 2.1.6. A file edited
with easytag shows the previous id3 tags in rhythmbox.
Any procedure to delete/reset *all* tags in a file, and to write them
just once?
** Changed in: easytag (Ubuntu)
Status: Fix Released = Confirmed
--
id3 tag
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
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
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
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, even though I, myself started complaining about this bug being
marked as invalid, I encourage everyone to respect the developer's
effort. He proved himself to be active in solving the bug, and willing
to cooperate.
I still do not agree with the current status, and I believe there is a
Maybe there's something I'm missing now. Why is the bug closed? On
systems with different configurations than having `lo' in
/etc/network/interfaces the bug is still present.
If such different configurations are wrong, then some policy should
avoid the user making such changes to the file (e.g.
Same here on Karmic Linux 2.6.31-17-generic #54-Ubuntu SMP Thu Dec 10
17:01:44 UTC 2009 x86_64 GNU/Linux
$ lsusb
Bus 002 Device 003: ID 046d:0870 Logitech, Inc. QuickCam Express
$ hal-find-by-capability --capability video4linux.video_capture
What data are missing to let this bug be solved? I happen to have such a
webcam, and I can try to help if needed.
--
hal does not detect Quickcam Express as v4l-device
https://bugs.launchpad.net/bugs/196811
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Hi all,
as I am still experiencing this (annoying but not critical) bug, is
there any update about the patch being accepted upstream, and thus the
bug being fixed in Ubuntu? Thank you.
Regards,
Alfredo
--
shutdown asks for password with only 1 user logged in
Some thoughts about this issue.
1) When no /etc/network/interfaces is available, It seems that upstart is
waiting for lo to be brought up before starting services; however network
manager, responsible for bringing up lo is not started by upstart; creating the
circular dependency.
2) When
Does your /etc/network/interfaces file contain the following lines?
auto lo
iface lo inet loopback
I have two machines where this workaround is actually working. (But your
experience may tell that my hints are in the wrong direction)
Anyway, I agree this bug is in fact critical, and my
I managed to have access to a machine where the bug does not show up.
That machine has a /etc/network/interfaces file containing exactly the
auto lo \\ iface lo inet loopback lines.
So this seems to be a relevant clue to bug hunting. In which way this
file interferes with localhost being brought
Please increase the importance of the bug, since it is really critical
for remotely administrated server systems! If for any reason the server
is rebooted, it cannot be administrated remotely (sshd does not start),
nor other services (e.g. web servers, sql servers etc) are started,
making the
I added the
auto lo
iface lo inet loopback
lines to /etc/network/interfaces file to one of the two server machines
(still no access to the other one, one day downtime now...): now the
services are starting up normally at boot -- but network manager
disappeared from the control panel (NM service
*** This bug is a duplicate of bug 497299 ***
https://bugs.launchpad.net/bugs/497299
** This bug has been marked a duplicate of bug 497299
upstart not starting init-scripts (event net-device-up IFACE=lo missing)
--
CUPS not start automatically
https://bugs.launchpad.net/bugs/486229
You
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
So, it seems to me that this is an upstream bug (because they should
switch to the new fullscreen mode). Has this bug already be reported
to upstream?
--
MythTV doesn't go full screen without desktop visual effects off
https://bugs.launchpad.net/bugs/348934
You received this bug notification
Just to be more precise, you don't need to click and hold left button
over the menu. The steps you need to do are (from
https://bugzilla.gnome.org/show_bug.cgi?id=577139):
1. set /desktop/gnome/interface/can_change_accels true (gconf editor); or go to
System - Preferences - Appearance, switch to
26 matches
Mail list logo
