On 10/24/05, Dennis J Perkins [EMAIL PROTECTED] wrote:
I've found that gdm doesn't call .xinitrc for some reason, so
dbus-launch never runs.
This is true, gdm does not behave the same way as issuing startx from
the console. But you can get it to do what you want. I have dbus
running right now
I was just wondering: have I said something wrong in my previous
post in this thread?
Why no answers from anyone in ten days?
Luca
--
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
On Mon, 2005-10-24 at 21:11 -0600, Dennis J Perkins wrote:
I've found that gdm doesn't call .xinitrc for some reason, so
dbus-launch never runs.
Ah, you're using GDM to start Gnome - I'd missed that. In that case, try
the attached patch, which modifies GDM's Xsession file to run
dbus-launch
Recently, Somebody Somewhere wrote these words
I was just wondering: have I said something wrong in my previous
post in this thread?
Why no answers from anyone in ten days?
Ok. Take as much from the list below as fits.
/begin nag
This list works by people volunteering personal time to help
Hi
You can do the same thing in cups with
lpadmin -p jerrypc -m laserjet.ppd.gz -v socket://[ip_address].
The only trick is finding the correct ppd for your printer. The conversion
problem is pretty much the same for cups or lprng.
Cheers for your reply jerry.
But I think my issue is
On Tue, 25 Oct 2005, Luca Dionisi wrote:
I was just wondering: have I said something wrong in my previous
post in this thread?
Why no answers from anyone in ten days?
Luca
Probably because *nobody* here knows anything about libc5.
Ken
--
das eine Mal als Tragödie, das andere Mal als Farce
On Tue, 2005-10-25 at 11:39 +0100, Ken Moffat wrote:
On Tue, 25 Oct 2005, Luca Dionisi wrote:
I was just wondering: have I said something wrong in my previous
post in this thread?
Why no answers from anyone in ten days?
Luca
Probably because *nobody* here knows anything about
On 10/25/05, Rainer Peter Feller
[EMAIL PROTECTED] wrote:
On Tue, 2005-10-25 at 11:39 +0100, Ken Moffat wrote:
Probably because *nobody* here knows anything about libc5.
or nobody wants to admit that s/he is that old that s/he knows anything
about libc5
Grazie
Luca
--
Hi again
I had this with a canon bjc4000.
Everyone told me I had the wrong ppd file. I never solved it.
I was printing locally, so I had other options. I went away and never
came back.
Well, in my case it was the 'wrong' ppd file that was the issue. I
noticed that on Slackware (where
On Mon, Oct 24, 2005 at 08:32:41PM +0200, channelzero wrote:
Am Montag 24 Oktober 2005 18:01 schrieb Jonas Norlander:
Any idea why I got this error in make check?
Do you have dejagnu package installed?
Yes it is installed.
[EMAIL PROTECTED]:~# runtest --version
WARNING: Couldn't find the
On Tue, Oct 25, 2005 at 02:45:16PM +0200, Jonas Norlander wrote:
On Mon, Oct 24, 2005 at 08:32:41PM +0200, channelzero wrote:
Am Montag 24 Oktober 2005 18:01 schrieb Jonas Norlander:
Any idea why I got this error in make check?
Do you have dejagnu package installed?
Yes it is
On 10/25/05, Simon Scheiwiller [EMAIL PROTECTED] wrote:
the configure script for transcode 0.6.14 looks for the lzo headers in
/usr/include. when i pass the option --with-lzo-includes=/usr/include/lzo,
it looks for the headers in /usr/include/lzo/include.
is there a patch for transcode for
On 10/25/05, Randy McMurchy [EMAIL PROTECTED] wrote:
Changing the defaults may not work however. The problem is because
I believe Transcode wants LZO-1 and the OP has LZO-2 installed.
Sometimes, just getting configure to see the changes isn't enough.
There is a reason the LZO maintainer uses
Thus spoke Dan Nicholson:
On 10/25/05, Randy McMurchy [EMAIL PROTECTED] wrote:
Changing the defaults may not work however. The problem is because
I believe Transcode wants LZO-1 and the OP has LZO-2 installed.
Sometimes, just getting configure to see the changes isn't enough.
There is a
Dan Nicholson wrote these words on 10/25/05 17:28 CST:
Ahh. I've never used LZO or even knew there were multiple versions of
it.
I ran into this last time I installed Transcode. Another alternative
for the OP is to install the most recent version of Transcode. They
are up to 1.0.1 as of now.
More problems here:
first, I get that error:
gcc -DHAVE_CONFIG_H -I. -I. -I.. -Wall -D_LARGEFILE_SOURCE
-D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -g -O2 -MT bitstream.lo -MD
-MP -MF .deps/bitstream.Tpo -c bitstream.c -fPIC -DPIC -o
.libs/bitstream.o
In file included from bitstream.c:36:
On 10/25/05, Randy McMurchy [EMAIL PROTECTED] wrote:
Dan Nicholson wrote these words on 10/25/05 17:28 CST:
I ran into this last time I installed Transcode. Another alternative
for the OP is to install the most recent version of Transcode. They
are up to 1.0.1 as of now. You can find it at:
Thus spoke Dan Nicholson:
Step up to 1.0.1. It built cleanly with no patching, and it found all
my multitude of plugins. With the exception of libpostproc (from
MPlayer). Here's the configure statement I used:
./configure --prefix=/usr --enable-netstrem --enable-libpostproc \
After digging around, I couldn't find any info other than what debian
gave. I've weeded out their extra junk and made an LFS-conforming patch
for anyone who uses sudo. I've also emailed the sudo list for their take
on this vulnerability and it's proposed fix.
--
Archaic
Want control,
19 matches
Mail list logo
