> It should be packaged on its own (it's in Marillat's repository, IIRC),
> but certainly not in xbase-clients.
Why's that? xvinfo is also in xbase-clients.
Either way, it's not in the archive yet. I'd package it separately, just
don't want to step on anyone's toes.
Michael
--
To UN
Package: xbase-clients
Version: 4.3.0.dfsg.1-14
Severity: wishlist
Please add the xvattr tool
(http://freshmeat.net/projects/xvattr/?topic_id=100%2C125)
to xbase-clients. It's useful to tweak XV stuff at runtime without server
restart, for instance to get xine running on the external CRTC port
i
> this bug should have been fixed in 4.3.0-3. The build of xfree86_4.3.0-3 (in
> pbuilder chroot) will probably fail due to a bug in tetex-bin (2.0.2-8),
> though.
How very encouraging. We're not using pbuilder, though.
I'll shut my autobuilder down for the time being, until after 4.3.0-3 has
bee
The libx11-6 postrm script still dies (with my change applied) because
/usr/X11R6/lib is the _only_ line in ld.so.conf, and the output file is
empty after the fgrep -v. set -e makes the postrm script die.
Suggested change:
fgrep -qsvx "$dir" "$ldsoconf" > "$ldsoconf.dpkg-tmp" || echo "empty
Package: libx11-6
Version: 4.3.0-2
Severity: critical
quoting the postrm script:
# is the line present?
if fgrep -qsx "$dir" "$ldsoconf"; then
# are there any shared objects in the directory?
if [ "$(echo "$dir"/lib*.so.*.*)" = "$dir/lib*.so.*.*" ]; then
# glob expansion produce
> I and the other folks at the X Strike Force need to know the following
> things:
>
> 1) whether or not this program works when you run it without arguments
Runs without any problem ("read of /dev/mem returned 1") on PPC Powerbook
1999 "Lombard" (ran it multiple times, before and after sleep mode
> > > I'll try your kernel patch -- should I also perhaps try the 2.4 kernel?
> >
> > Try the 2.4 kernel first. If that doesn't fix it, my patch won't either.
>
> Sorry, I went ahead and stuck with kernel 2.2.19 with your patch.
>
> Your patch fixed it. Should I file a bug against the pmac to a
> > > I'll try your kernel patch -- should I also perhaps try the 2.4 kernel?
> >
> > Try the 2.4 kernel first. If that doesn't fix it, my patch won't either.
>
> Sorry, I went ahead and stuck with kernel 2.2.19 with your patch.
>
> Your patch fixed it. Should I file a bug against the pmac to
> > should have read X -probeonly (where did that go?), sorry.
>
> That crashes it as well. I just tested with xserver-xfree86 4.1.0-5
> and -6, same results.
>
> I'll try your kernel patch -- should I also perhaps try the 2.4 kernel?
Try the 2.4 kernel first. If that doesn't fix it, my patch w
> > should have read X -probeonly (where did that go?), sorry.
>
> That crashes it as well. I just tested with xserver-xfree86 4.1.0-5
> and -6, same results.
>
> I'll try your kernel patch -- should I also perhaps try the 2.4 kernel?
Try the 2.4 kernel first. If that doesn't fix it, my patch
> > Please send the full X server log (the section about PCI device
> > probing/fixup might prove interesting)
>
> I can't, due to the kernel crash which occurs when running this.
Sorry, I forgot how bad this can be... Does it also panic with X
> Should I file a bug on kernel-image-2.2.19-pmac
> > I can't, due to the kernel crash which occurs when running this.
>
> Sorry, I forgot how bad this can be... Does it also panic with X
should have read X -probeonly (where did that go?), sorry.
Michael
> > Please send the full X server log (the section about PCI device
> > probing/fixup might prove interesting)
>
> I can't, due to the kernel crash which occurs when running this.
Sorry, I forgot how bad this can be... Does it also panic with X
> Should I file a bug on kernel-image-2.2.19-pmac
> > I can't, due to the kernel crash which occurs when running this.
>
> Sorry, I forgot how bad this can be... Does it also panic with X
should have read X -probeonly (where did that go?), sorry.
Michael
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe".
> Distribution: pure 'testing'
> Version: 4.1.0-2
> Kernel: kernel-image-2.2.19-pmac 2.2.19-2
>
> Installing the new xserver-xfree86 4.1.0-2 from unstable causes an
> error:
>
> (WW) ATI: PCI/AGP Mach64 in slot 0:17:0 could not be detected!
> (EE) No devices detected.
>
> With a subsequ
> Distribution: pure 'testing'
> Version: 4.1.0-2
> Kernel: kernel-image-2.2.19-pmac 2.2.19-2
>
> Installing the new xserver-xfree86 4.1.0-2 from unstable causes an
> error:
>
> (WW) ATI: PCI/AGP Mach64 in slot 0:17:0 could not be detected!
> (EE) No devices detected.
>
> With a subseq
> 1. at wakeup, after sleep, the computer crashes! [kernel]
Each time? Only after sleep for a long time?
> 2. one single touch of the trackpad is like a double-click [kernel]
Use trackpad notap, perhaps. Should be in pmac-utils.
> 3. group of pixels change color, like moving around [both fbdev
> 1. at wakeup, after sleep, the computer crashes! [kernel]
Each time? Only after sleep for a long time?
> 2. one single touch of the trackpad is like a double-click [kernel]
Use trackpad notap, perhaps. Should be in pmac-utils.
> 3. group of pixels change color, like moving around [both fbdev
> Some Mach64 based chips cause problems with 2.2 kernels so he might need to
> also use a 2.4 one or a patch from Michael Schmitz (check the -powerpc
> archives).
Or use yaboot.
Michael
> Some Mach64 based chips cause problems with 2.2 kernels so he might need to
> also use a 2.4 one or a patch from Michael Schmitz (check the -powerpc
> archives).
Or use yaboot.
Michael
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe"
> > Appears to be a memory/swap related problem. Open up another tty and run
> > 'top' while the make is going on, and watch your total free memory and your
> > total free swap..they might get too small for cc to run
> > successfully. (VM is the virtual memory driver)
>
> Tried that; I di
> > Appears to be a memory/swap related problem. Open up another tty and run
> > 'top' while the make is going on, and watch your total free memory and your
> > total free swap..they might get too small for cc to run
> > successfully. (VM is the virtual memory driver)
>
> Tried that; I d
> >Yeap thats the problem, looking at Franz's patch it seems that if
> > keyboard_sends_linux_keycodes doesn't exist, the server assumes AT keycodes.
> > I am not sure how to handle APUS as well, even the pmac test through xkb
> > will only work if xkb is enabled (not always the case), i think
> >Yeap thats the problem, looking at Franz's patch it seems that if
> > keyboard_sends_linux_keycodes doesn't exist, the server assumes AT keycodes.
> > I am not sure how to handle APUS as well, even the pmac test through xkb
> > will only work if xkb is enabled (not always the case), i think
> > > The ATI Mach64 driver is known broken in these packages. We're working
> > > on a viable solution to it. Sorry.
> >
> > I'll resync with Ani Joshi's source sometime soon and try if that's hosed
> > as well. I had it working as late as July 18, maybe something broke after
> > that date.
>
> > > The ATI Mach64 driver is known broken in these packages. We're working
> > > on a viable solution to it. Sorry.
> >
> > I'll resync with Ani Joshi's source sometime soon and try if that's hosed
> > as well. I had it working as late as July 18, maybe something broke after
> > that date.
>
> The ATI Mach64 driver is known broken in these packages. We're working
> on a viable solution to it. Sorry.
I'll resync with Ani Joshi's source sometime soon and try if that's hosed
as well. I had it working as late as July 18, maybe something broke after
that date.
> > Found a Mach64 on a P
> The ATI Mach64 driver is known broken in these packages. We're working
> on a viable solution to it. Sorry.
I'll resync with Ani Joshi's source sometime soon and try if that's hosed
as well. I had it working as late as July 18, maybe something broke after
that date.
> > Found a Mach64 on a
> > In that case, I plan to drop Xlib libc5-compatibility for m68k in woody.
> >
> > We might as well retain it in potato, this close to the release.
> Michael, did you read Brandens announcement by now?
Yep (the URL you quoted, if that's what you mean; there were no
'corrections').
> Please, no
29 matches
Mail list logo
