Attached is current monitors.xml
Removing this file from ~/.config/ prevents expression of the bug.
** Attachment added: "monitors.xml"
http://launchpadlibrarian.net/45029089/monitors.xml
--
[i945] [i945GME,nomodeset] mouse cursor invisible
https://bugs.launchpad.net/bugs/475917
You received
Upgraded the affected machine to Lucid overnight. The problem remains.
Opening gnome-display-properties and changing screen refresh rate brings
on this bug. Mouse cursor disappears until user locks screen or
otherwise triggers mode change..
Deleting ~/.config/monitors.xml prevents the issue...
I can confirm Beni's experience.
Deleting ~/.config/monitors.xml fixes this issue on all user accounts on
my machine with an Intel 82845G/GL onboard graphics chip, 32-bit Karmic.
So gnome-display-properties is triggering this bug, even if it's not
directly responsible for the expression of the bu
Never mind. I just compared the dependencies. Not a great idea to have
people replacing most of the guts of karmic's Gnome through a PPA, I'd
expect.
--
Dual Monitor Background Support
https://bugs.launchpad.net/bugs/153793
You received this bug notification because you are a member of Ubuntu
B
Excellent!
Does anyone have this backported for karmic in a PPA? Alternately, I'd
be willing to give it a go myself with a little bit of mentoring.
--
Dual Monitor Background Support
https://bugs.launchpad.net/bugs/153793
You received this bug notification because you are a member of Ubuntu
Bug
One thing we could look into is the twisted libraries. It looks from
the source like apt-proxy uses twisted for most of its networking
features. Twisted is still under active development:
http://twistedmatrix.com/
One thing I don't know is if apt-proxy circa 2005 isn't fouling up
somehow with tw
After some cursory reading of the code and consulting some Python
resources, I don't think I'm up to this challenge in a language I'm this
unfamiliar with yet.
--
apt-proxy hangs when client aborting download
https://bugs.launchpad.net/bugs/83783
You received this bug notification because you
I can confirm this bug. It's a headache, because I'd like to use apt-
proxy to let my high school classroom full of machines tax our
overburdened school connection less. It works brilliantly except when it
hangs spectacularly, and I ideally want a server I can just forget
about.
I'm trying out Eli
I guess I'm a little behind the times on where to get the hardy-proposed
packages. I'd like to just grab .debs as I want them.. but if there's a
repo I have to add, I'll do that too.
Tried to add hardy-proposed as a repo, but the only version of
audacious-crossfade that Synaptic sees is the broke
We're shipping a plugin that breaks the parent program today.
There's a simple solution listed here by William Pitcock roughly one
month ago: rebuild the plugin with updated source so that the program
and plugin are on the same page.
I tested this again today. Installing audacious-crossfade cause
I'd hoped that fixing https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/211592";>Bug
211592 today meant that all was well and this bug would be fixed.
Alas, this bug remains for my ice1712 based card.
The workaround posted here remains the only way to have working
Pulseaudio. (that I know
Seems to me that this bug does exist.
** Changed in: audacious (Ubuntu)
Status: New => Confirmed
--
Audacious not launching (Segmentation Fault)
https://bugs.launchpad.net/bugs/208425
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
I uninstalled audacious-crossfade, and audacious now works properly.
I'm using the one from the repository, not compiling my own.
So is there a way to get the audacious-crossfade package updated, or
move this bug to that package?
--
Audacious not launching (Segmentation Fault)
https://bugs.laun
I can confirm this.
Uninstalling and reinstalling Audacious through apt doesn't fix it.
I moved ~/.config/audacious/ to a backup and started audacious to see if
corrupted settings were to blame
[EMAIL PROTECTED]:~$ audacious
Segmentation fault (core dumped)
A new ~/.config/audacious/ had been c
Ugly work around for an maudio Delta 44 here:
https://tango.0pointer.de/pipermail/pulseaudio-
discuss/2008-January/001240.html
Basically having to manually etch a static config into a config file in
/etc
--
Pulseaudio fails to initialize Audiophile 2496
https://bugs.launchpad.net/bugs/178442
Yo
This problem also exists on the M-Audio Delta 410 which uses the same
driver and is quite similar (from the computer's perspective) to the
Audiophile 2496 I believe.
There isn't a control named "Master" or "PCM" on the Delta 410. The
relevant channels are "DAC" and "DAC 1" through "DAC 7" for a
16 matches
Mail list logo
