@Pobice: Could you perhaps post a plugins-extra-package in your PPA
built for totem 2.28? I can't seem to get this working myself.
--
mythtv pluggin missing due to missing build deps
https://bugs.launchpad.net/bugs/365750
You received this bug notification because you are a member of Ubuntu
Deskt
So I tried to rip a .deb from Lucid and found out that the mythtv plugin is not
included there as well.
--> not fixed in Lucid
--
mythtv pluggin missing due to missing build deps
https://bugs.launchpad.net/bugs/365750
You received this bug notification because you are a member of Ubuntu
Desktop
Public bug reported:
Binary package hint: gnome-power-manager
On a laptop system (LG S1 with ATI Radeon 9600 mobility) the VGA output
is getting "blanked" when the option to blank the screen on laptop lid
close is selected. At first sight this might not seem to be a bug, but
it is a real problem
I hate to say it, but my current (1.1.0-0ubuntu1) nautilus-sendto still
gives me the "Obex Push file transfer unsupported" error on a current
intrepid (bluez 4.12) install. Sending via tray icon ("Send files to
device") works however...
--
Look into switching to bluez 4.x
https://bugs.launchpad.n
Public bug reported:
Binary package hint: nautilus-sendto
My Evolution addressbook has its contents sorted in the "Lastname,
Firstname"-scheme. When I select contacts from the addressbook as
recipients for mail, Evolution simply writes a comma-separated list of
"Firstname Lastname". So far everyt
Additional observation: Last night, I sent my laptop to hibernate and
accidentally switched to console output. For some time, nothing happened
(the system looked quite crashed) but then, a few messages popped up on
my screen which I was able to quickly grab with (*cough*) my cellphone.
Anyways, thi
To trigger this bug on my hardy system, I simply have to do the following:
- in nautilusselect a file I want to send by mail
- right-click and select "send-to"
- choose "evolution mail" in the dropdown menu
- enter a few letters in the address field and select an entry from the list
like "Gehl, Be
*** This bug is a duplicate of bug 186450 ***
https://bugs.launchpad.net/bugs/186450
Public bug reported:
Binary package hint: deskbar-applet
I was just starting an app (firefox 3.0 to be precise) from the deskbar-
UI with some system load in the background (rhytmbox web radio, skype,
evolut
*** This bug is a duplicate of bug 186450 ***
https://bugs.launchpad.net/bugs/186450
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/11871789/Dependencies.txt
** Attachment added: "ProcMaps.txt"
http://launchpadlibrarian.net/11871790/ProcMaps.txt
** Attachment ad
Public bug reported:
Binary package hint: gnome-power-manager
Suspending/resuming with "/etc/acpi/sleep.sh" script works, as does
suspend/resume over HAL via "pm-suspend". However, when suspending using
the gnome-power-manager (via panel applet, power button or similar
events), after resume only
** Attachment added: "acpi-support"
http://launchpadlibrarian.net/12694316/acpi-support
** Description changed:
Binary package hint: gnome-power-manager
Suspending/resuming with "/etc/acpi/sleep.sh" script works, as does
suspend/resume over HAL via "pm-suspend". However, when suspend
Thanks for the hint - alas, it doesn't apply to my problem.
"lshal | grep quirk" gives empty results and manually adding
"power_management.quirk.vbe_post = false" via a .fdi file does not
improve the situation. No resume after suspend from g-p-m.
However I am now pretty sure that for some reason,
Well, I played around with the quirks a litte (nice collection of useful
info, thanks!) but I am not sure if that leads to anything since "pm-
suspend" without any called quirks suspends and resumes fine - so no
quirks should be necessary, right?
Somewhere in one of the fdi files I found some LG-s
@awen
That's what keeps puzzling me: "lshal | grep quirk" shows no results -
so g-p-m should go down to suspend (using hal) without quirks and
therefore just like "pm-suspend" without any arguments. However, it
shows a scrambled VESA-buffer-window just as I get it when using "pm-
suspend --quirk-v
Ok, I realize how much there is, I do not know about my system (even
though location and file name of the log are perfectly logical...).
Alas, the pm-suspend.log (see attached) to my eyes does not show
anything but "OK"-type status messages.
Anyways, I dug around a little in the g-p-m documentati
I ran "dbus-monitor" while suspending via dbus-command. The last
(relevant - pidgin is kind of chatty) few lines are attached as a log
file.
** Attachment added: "dbus-monitor.log"
http://launchpadlibrarian.net/12727384/dbus-monitor.log
--
Resume from standby works with "pm-suspend" but not w
Good point - I was not aware that g-p-m also uses the pm-suspend file.
The file I attached was probably from g-p-m, so I deleted it and ran pm-
suspend. The logfile (attached) shows a difference because there are
also (surprise) OKs from the resume hooks...
** Attachment added: "pm-suspend.log"
@FrejSoya:
So it's opt-out rather than opt-in? Gee! I thought that only applied to spam...
;-)
Ok, let me see. The negative logic means, I have to initialize every
single quirk with "false" to get a pristine quirk-free suspend. Would
the fdi-file attached do the job? (I'll try in a minute...)
**
@FrejSoya
Well, lshal gives the following:
power_management.quirk.dpms_on = false (bool)
power_management.quirk.dpms_suspend = false (bool)
power_management.quirk.radeon_off = false (bool)
power_management.quirk.s3_bios = false (bool)
power_management.quirk.s3_mode = false (bool)
@awen
Ok, I've finished celebrating the first successful suspend/resume with g-p-m
since I switched to Linux... :-)
a) /root/pm-suspend.log is empty when using your (quite elegant) pm-suspend
script
b) with the original pm-suspend symlink, suspend AND resume work just fine!
So as far as I am co
*** This bug is a duplicate of bug 198808 ***
https://bugs.launchpad.net/bugs/198808
As I already tried to explain: My hardware doesn't seem to need any
quirks to successfully suspend and resume. However, even with all quirks
set to "false" (see above), HAL still wanted to use some quirks
(inc
I can also confirm the "long sleep time" factor. As soon as my laptop
(hardy, fglrx from restricted modules) sleeps for more than a few hours,
the error message comes up - plus I cannot shut down from gpm anymore.
--
[Hardy] Message: "Suspend Problem. Your computer failed to suspend"
https://bugs
22 matches
Mail list logo
