I've been aware of it for a while now. There was no real hurry to fix it
because dpkg-dev itself was failing (see debbugs#565712).
--
Lintian strings scripts cannot handle spaces in path names
https://bugs.launchpad.net/bugs/540342
You received this bug notification because you are a member of
Without testing it at all in Ubuntu, this sounds like the libedit bug
(which I don't know how/why somebody at Ubuntu assumed it was fixed).
Calling php from a compgen script work fine in Debian, another
indication that it might be the libedit bug.
--
PHP process output (?) that breaks bash
Without testing it at all in Ubuntu, this sounds like the libedit bug
(which I don't know how/why somebody at Ubuntu assumed it was fixed).
Calling php from a compgen script work fine in Debian, another
indication that it might be the libedit bug.
--
PHP process output (?) that breaks bash
Does by any chance your script is under ~/public_html? if that's so, it
is not a bug, check /usr/share/doc/php5-common/NEWS.Debian.gz
--
libapache2-mod-php5 is no longer working correctly on lucid
https://bugs.launchpad.net/bugs/531150
You received this bug notification because you are a member
Does by any chance your script is under ~/public_html? if that's so, it
is not a bug, check /usr/share/doc/php5-common/NEWS.Debian.gz
--
libapache2-mod-php5 is no longer working correctly on lucid
https://bugs.launchpad.net/bugs/531150
You received this bug notification because you are a member
of this issue we should probably come up with a
better way to deal with these Ubuntu-specific exceptions. Probably
something at the Lintian::Tag layer.
Cheers,
--
Raphael Geissert - Debian Developer
www.debian.org - get.debian.net
--
lintian should not complain about upstart jobs not looking like init
Jos, would be great if you could provide a test too (take a look at
t/tests/).
But taking a look at the implementation:
Once upstart-job is included in Debian and made the default it will
return the LSB headers when called with a special argument (I don't
remeber the details right now). As such,
** Also affects: ureadahead
Importance: Undecided
Status: New
--
man page needs to be updated
https://bugs.launchpad.net/bugs/482767
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: ureadahead
The man page still states that the pack list is removed/regenerated if
it is a month old, but the code has been modified to only remove it
after a year.
** Affects: ureadahead (Ubuntu)
Importance: Undecided
Status: New
--
man
2009/11/1 Xenophon email.xenop...@gmail.com:
Raphael, I added your PPA and upgraded to your build of openchrome. No
luck :( I still can't get past the login screen and the loading window.
Xorg.0.log attached. If you'd like any other logs, please let me know.
Yes, please attach the
I'm happy to stick around and get this solved completely. But in the
interim, could somebody suggest a way to get my display back with VESA?
I don't mind 640x480 resolution etc. while I try to find a solution.
Could you please try with the version of the driver available from my
ppa? it is
I've uploaded the latest rev to my ppa for jaunty and karmic:
https://launchpad.net/~atomo64/+archive/ppa
--
[P4M900] [HP 2133] resolution problem starting X with the wlan network
controler activated
https://bugs.launchpad.net/bugs/355918
You received this bug notification because you are a
** Changed in: ffmpeg-php (Ubuntu)
Status: New = Invalid
--
Impossible to install php5-ffmpeg
https://bugs.launchpad.net/bugs/370801
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
The bug was caused by the -via driver being also present on the
installed system (say you installed it, or something did). As Xorg
matched the PCI id for both, openchrome and via, drivers it chose to use
via, and not openchrome. Removing the via package should be more than
enough.
--
[HARDY]
** Changed in: xserver-xorg-video-openchrome (Ubuntu)
Assignee: (unassigned) = Raphael Geissert (atomo64)
Status: Triaged = In Progress
--
Xorg freezes on start. Black screen with waiting cursor. Unichrome video,
worked on hardy.
https://bugs.launchpad.net/bugs/274340
You received
Updated package which is said to fix the bug is to be uploaded soon
** Changed in: xserver-xorg-video-openchrome (Ubuntu)
Status: Confirmed = In Progress
--
incorrect screen detection [openchrome]
https://bugs.launchpad.net/bugs/182778
You received this bug notification because you are a
Thomas, could you please test the package of intrepid or, even better,
jaunty? In case you really need to stay with hardy then this looks like
the patch fixing the bug:
http://www.openchrome.org/trac/changeset/508/trunk
--
Screen corruption
https://bugs.launchpad.net/bugs/222132
You received
Hi,
[...]
Since Feisty, no LiveCD is usable with a KM400 video card and vesa. Same
problem when switching to vesa on an installed distro, I get the classic
[...]
I fail to see how this is related to -openchrome, am I missing
something?
--
Via KM400 : no matching mode for vesa
2008/12/16 Bartosz gan...@poczta.onet.pl:
I run Hardy Heron (LiveCD) and install above openchrome 0.2.903 [...]
0.2.903+svn685-1+hardy1_i386.deb
Next I restarted X by using the CTRL+ALT+BACKSPACE shortcut.
The new drivers works fine (the X not freeze).
As I expected :)
Only one bug
Done, revision 685 for hardy is being built as I type. Package can be
found at https://launchpad.net/~atomo64/+archive
--
Xorg freezes on start. Black screen with waiting cursor. Unichrome video,
worked on hardy.
https://bugs.launchpad.net/bugs/274340
You received this bug notification because
I won't repeat myself over and over again: the issue has its origins
in Xorg itself in version 7.5
I don't know much about X.org and EXA and don't have time to learn
about them. I'll prod Xavier to see if he can suggest some other
change in X.org.
An alternative is to downgrade to X.org 7.4 and
2008/11/9 Paul Sinnett [EMAIL PROTECTED]:
I tried the patch suggested in the openSUSE bug report [...] but without much
luck on
my Acer 1392LC laptop using the openchrome driver.
Thanks for testing the patch.
I've forwarded your comments to upstream and am now waiting for a reply.
--
Xorg
** Bug watch added: Novell/SUSE Bugzilla #435791
https://bugzilla.novell.com/show_bug.cgi?id=435791
** Also affects: opensuse via
https://bugzilla.novell.com/show_bug.cgi?id=435791
Importance: Unknown
Status: Unknown
--
Xorg freezes on start. Black screen with waiting cursor.
2008/10/26 Rafał Próchniak [EMAIL PROTECTED]:
[...]
2. Xorg.conf with XaaNoImageWriteRect only: normal quality, broken
cursor.
3. Xorg.conf with XaaNoImageWriteRect and SWCursor (haven't tried that
one before): normal quality, cursor working.
Could you please try with the new package from
Rafał, could you please tell me what version of xserver-xorg-core you
have?
'apt-cache policy xserver-xorg-core' will tell you. If you are still
using a version below 2:1.5.2-1 update it, try again, and report back
please.
--
intrepid can't start with via vn896 vga
** Bug watch added: OpenChrome Trac #262
http://www.openchrome.org/trac/ticket/262
** Also affects: openchrome via
http://www.openchrome.org/trac/ticket/262
Importance: Unknown
Status: Unknown
--
intrepid can't start with via vn896 vga
https://bugs.launchpad.net/bugs/273775
You
Ok, could you please provide the output of 'ls /etc/rc2.d' and 'apt-
cache policy xserver-xorg libdrm2'?
And could you also please try by adding the following line to the Device
section in /etc/x11/xorg.conf?
Option XaaNoImageWriteRect
--
intrepid can't start with via vn896 vga
@Johan Walles: Xavier asked to *retry*, he didn't in any way imply that
it was fixed (although it might be :).
Could you please try the package at [1]? it is the latest revision by
upstream.
[1] https://launchpad.net/~atomo64/+archive
--
incorrect screen detection [openchrome]
From the attachment:
xserver-xorg:
Installed: 1:7.4~5ubuntu2
That seems to be the source of the problem (will have to wait until
u-foka confirms he is also using 7.4): there are some issues (aka
bugs) in xorg 7.4 with XAA. The other bug reported against -openchrome
related to gdm has more
29 matches
Mail list logo
