Bug#692196: Debian installer 7.0 beta 3 on sparc Ultra 2 fails

[D G Teed]

Package: installation-reports

Boot method: boot cdrom with net install version of ISO for installer 7, beta 
3, sparc
Image version: 
http://cdimage.debian.org/cdimage/wheezy_di_beta3/sparc/iso-cd/debian-wheezy-DI-b3-sparc-netinst.iso
Date: Nov 2, 2012

Machine: Sun Ultra 2 
Processor: 2 x 400 Mhz

Memory: 1 GB
Partitions: 2 internal SCSI disks, left 10 MB free at disk start.  RAID 1 
partitions for
 /boot 90 MB
 / 30 GB
 /tmp   2 GB
 non-RAID swap partition with remaining space on each disk.

Each file system was set as ext3.

Output of lspci -knn (or lspci -nn): non-working, cannot produce

Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[O]
Configure network:  [O]
Detect CD:  [O]
Load installer modules: [O]
Detect hard drives: [O]
Partition hard drives:  [O]
Install base system:[O]
Clock/timezone setup:   [O]
User/password setup:[O]
Install tasks:  [E]
Install boot loader:[ ]
Overall install:[ ]

Comments/Problems: System hung during package installs for Desktop Environment, 
SSH services
and basic system package sets.  System hang was reproducible at same spot.
Watched VT screen of F4 and there was no kernel dump or error.
The system became unresponsive.  Pressing numlock or caps lock
had no effect on LED for same.  One first attempt, used apt repo at Dal.ca.  On 
second
attempt used apt repo at uwaterloo.ca Computer Science club.  No difference.

Sorry I don't have the final line of the package that was being downloaded
at the time the system stopped responding.  I can tell you it did download
perhaps 100 to 300 packages before it seized.  It gave no error.  It behaved
as if it was taking a long time to download or whatever, except
that when I checked after 30 minutes or so of no progress, I saw the keyboard
wasn't responding with the standard numlock/capslock LED test of system health.
Control-Alt F1, etc. were also attempted to see what another VT might show.
Finally, a Stop-A was done, which should cause the PROM to pop us out to a ok >
prompt, and it did nothing.

This failure was observed twice, once with the progress bar view,
and once with the details view from F4 virtual terminal.

System seemed healthy prior to install attempt - it had been running Solaris 10 
with ZFS
mirrored RAID on same disks for a few years and no hardware problems.

--Donald Teed


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#606350: [Pkg-samba-maint] Bug#606350: sasl2-bin: "Too many open files" error with PAM - recovery with saslauthd restart

[D G Teed]

I installed these packages from sid this morning, onto
an otherwise squeeze based system:

samba-common2:3.5.6~dfsg-4
samba-common-bin2:3.5.6~dfsg-4
libwbclient02:3.5.6~dfsg-4
winbind 2:3.5.6~dfsg-4

I can see the pam library file is updated:

ls -l /lib/security/pam_winbind.so
-rw-r--r-- 1 root root 60168 Jan 15 16:04 /lib/security/pam_winbind.so

winbind and saslauthd are restarted.

Six hours later I check and the number of fd files
and links is static at 8 files under each /proc//fd
where  is a process id from saslauthd

Based on prior experiences with the bug (leak growth appears
within a few  minutes), this bug is fixed in these package releases.

--Donald

Bug#606350: [Pkg-samba-maint] Bug#606350: sasl2-bin: "Too many open files" error with PAM - recovery with saslauthd restart

[D G Teed]

On Mon, Jan 3, 2011 at 2:37 AM, Christian PERRIER wrote:

>
> Eh, that's really strange, but thanks for the detailed investigation.
>
> Could you check whether you still experience the bug with the
> 3.5.6~dfsg-3 packages? I suppose this is indeed what you're doing
> right now...
>
>
I'm afraid the bug reappears with these packages:

samba-common2:3.5.6~dfsg-3
samba-common-bin2:3.5.6~dfsg-3~test1
libwbclient02:3.5.6~dfsg-3
winbind 2:3.5.6~dfsg-3

I am seeing a growth in fd links.  Also the pipes left open
are visible from running: netstat -e | grep winbind
It reports dozens of lines like:

unix  3  [ ] STREAM CONNECTED 72840600
/var/run/samba/winbindd_privileged/pipe
unix  3  [ ] STREAM CONNECTED 72819898
/var/run/samba/winbindd_privileged/pipe
unix  3  [ ] STREAM CONNECTED 72811786
/var/run/samba/winbindd_privileged/pipe
unix  3  [ ] STREAM CONNECTED 72799966
/var/run/samba/winbindd_privileged/pipe
unix  3  [ ] STREAM CONNECTED 72765262
/var/run/samba/winbindd_privileged/pipe

When I used all packages ending with ~test1 , I never catch any
dangling pipes like this from netstat report.

I'm up to 71 open fd links to sockets from 5 saslauthd processes
since this morning (relatively slow as students and faculty are not back
yet).

--Donald

Bug#606350: [Pkg-samba-maint] Bug#606350: sasl2-bin: "Too many open files" error with PAM - recovery with saslauthd restart

[D G Teed]

On Wed, Dec 22, 2010 at 2:05 AM, Christian PERRIER wrote:

>
>
> Did you have any chance to test the amd64 packages I poointed you to?
>
> This fix is a good candidate for squeeze but I would like to have
> success reports before requesting a freeze exception to the release team.
>

I've tested the test packages:

libwbclient0
samba-common
samba-common-bin
smbclient
winbind

They have worked well with saslauthd and there is no longer growth in the
file descriptors after a couple of days running.

Regards,

--Donald

Bug#606350: [Pkg-samba-maint] Bug#606350: sasl2-bin: "Too many open files" error with PAM - recovery with saslauthd restart

[D G Teed]

On Thu, Dec 9, 2010 at 5:00 PM, Christian PERRIER wrote:

>
> Hello,
>
> On 
> http://people.debian.org/~bubulle/samba-test/,
> you'll soon find
> packages which you may want to try. I just applied the patch from
> Samba's Bugzilla and recompiled these package.
>
> They're currently being uploaded and should be ready to download in
> about 10 minutes or so.
>
> If they fix this file descriptors leak problem, please report.
>
>
Hello,

This is awesome.  I'd like to test this.  Can we get the
packages built for amd64 where it is required?

Bug#606350: sasl2-bin: "Too many open files" error with PAM - recovery with saslauthd restart

[D G Teed]

On Wed, Dec 8, 2010 at 5:53 PM, Russ Allbery  wrote:

>
> Looks like a file descriptor leak in pam_winbind.  I think saslauthd isn't
> at fault here.
>
>
I did a test today...  I noticed the number of fds had grown overnight by
20 to 40 per process.   I did a restart of winbind and looked at the fds
under
the saslauthd processes.  It didn't change.

Both winbind and saslauthd must be restarted as the workaround.
Restarting winbind closes only the streams reported as
/var/run/samba/winbindd_privileged/pipe .

Developers would likely expect this, but I mention it here in case it might
help others caught by the issue.

Bug#606350: sasl2-bin: "Too many open files" error with PAM - recovery with saslauthd restart

[D G Teed]

On Wed, Dec 8, 2010 at 10:02 PM, Russ Allbery  wrote:

>
>
> I'll reassign it.  I wanted to see if anyone disagreed with me first.  :)
>
> --
> Russ Allbery (r...@debian.org)   
> 
> >
>

This might be the same as the samba bug reported upstream against Debian 5:
https://bugzilla.samba.org/show_bug.cgi?id=7265<%20https://bugzilla.samba.org/show_bug.cgi?id=7265>

That is showing a bug against samba 3.4, however it is
status NEW, from March this year.  A patch is mentioned.
I don't see why there would be a delay to release it.

This bug would effect apache, cyrus email, and many SMTP
services using authentication, so I'd think it should be a priority to fix.

--Donald

Bug#606350: sasl2-bin: "Too many open files" error with PAM - recovery with saslauthd restart

[D G Teed]

On Wed, Dec 8, 2010 at 5:53 PM, Russ Allbery  wrote:

> D G Teed  writes:
>
> > I also count 200 connections like this:
>
> > unix  3  [ ] STREAM CONNECTED 39854981
> > /var/run/samba/winbindd_privileged/pipe
>
> > Most users are simply using port 25 and would not be authenticating,
> > so I know these numbers cannot be current connections.
>
> Looks like a file descriptor leak in pam_winbind.  I think saslauthd isn't
> at fault here.
>
>
Is there a way the bug report can shuffle along to becoming a winbind
bug report, or should I re-report it, referring to this bug report?

--Donald

Bug#606350: sasl2-bin: "Too many open files" error with PAM - recovery with saslauthd restart

[D G Teed]

On Wed, Dec 8, 2010 at 4:23 PM, Dan White  wrote:

> On 08/12/10 15:33 -0400, D G Teed wrote:
>
>> Here is what one of the directories looked like:
>>
>> ls -l 15950/fd
>>
>> total 0
>> lrwx-- 1 root root 64 Dec  8 13:52 0 -> /dev/null
>> lrwx-- 1 root root 64 Dec  8 13:52 1 -> /dev/null
>> lrwx-- 1 root root 64 Dec  7 15:47 10 -> socket:[38109596]
>> lrwx-- 1 root root 64 Dec  7 15:47 11 -> socket:[38112677]
>> lrwx-- 1 root root 64 Dec  8 13:52 12 -> socket:[38129166]
>> lrwx-- 1 root root 64 Dec  8 13:52 13 -> socket:[38177341]
>> lrwx-- 1 root root 64 Dec  8 13:52 14 -> socket:[38198508]
>> lrwx-- 1 root root 64 Dec  8 13:52 15 -> socket:[38256709]
>> lrwx-- 1 root root 64 Dec  8 13:52 16 -> socket:[38307912]
>> lrwx-- 1 root root 64 Dec  8 13:52 17 -> socket:[38351349]
>> lrwx-- 1 root root 64 Dec  8 13:52 18 -> socket:[38378460]
>>
>
> Try doing a 'netstat -e' and see if you can match some of those sockets up
> with a connection, and see if you can determine what it's being used for,
> and what connection state it's in.
>
> I'm hoping you can tie the down to a particular type of connection, say,
> your pam_winbind attempts. If that's the case, then the problem might be
> due to a bug in that specific pam module, or could be due to a bug in the
> way saslauthd uses pam.
>

OK...

I've checked one process and here is what the matches look like:

/proc/15951/fd# for socket in `ls -l | cut -d' ' -f12 | sed 's/socket:\[// ;
s/\]//'`
> do
> netstat -e | grep $socket
> done
unix  2  [ ] STREAM CONNECTED 38129397
unix  3  [ ] STREAM CONNECTED 40572411
unix  3  [ ] STREAM CONNECTED 40583464
unix  3  [ ] STREAM CONNECTED 40602800
unix  3  [ ] STREAM CONNECTED 40649673
unix  3  [ ] STREAM CONNECTED 40667667
unix  2  [ ] STREAM CONNECTED 38134508
unix  2  [ ] STREAM CONNECTED 38137874
unix  2  [ ] STREAM CONNECTED 38144166
unix  2  [ ] STREAM CONNECTED 38145796
unix  2  [ ] STREAM CONNECTED 38164643
unix  2  [ ] STREAM CONNECTED 38182983
unix  2  [ ] STREAM CONNECTED 38198634
unix  2  [ ] STREAM CONNECTED 38212091
unix  2  [ ] STREAM CONNECTED 38284314
unix  2  [ ] STREAM CONNECTED 38310069
unix  2  [ ] STREAM CONNECTED 38337364
unix  2  [ ] STREAM CONNECTED 38378155
unix  2  [ ] STREAM CONNECTED 38401805
unix  2  [ ] STREAM CONNECTED 38411640
unix  2  [ ] STREAM CONNECTED 38427190
unix  2  [ ] STREAM CONNECTED 38437192
unix  2  [ ] STREAM CONNECTED 38494440
unix  2  [ ] STREAM CONNECTED 38522319
unix  2  [ ] STREAM CONNECTED 38548115
unix  2  [ ] DGRAM38091087
unix  2  [ ] STREAM CONNECTED 38554551
unix  2  [ ] STREAM CONNECTED 38561940
unix  2  [ ] STREAM CONNECTED 38581911
unix  2  [ ] STREAM CONNECTED 38596779
unix  2  [ ] STREAM CONNECTED 38618951
unix  2  [ ] STREAM CONNECTED 38751702
unix  2  [ ] STREAM CONNECTED 38790002
unix  2  [ ] STREAM CONNECTED 38796236
unix  2  [ ] STREAM CONNECTED 38840751
unix  2  [ ] STREAM CONNECTED 38867792
unix  2  [ ] STREAM CONNECTED 38892274
unix  2  [ ] STREAM CONNECTED 38934651
unix  2  [ ] STREAM CONNECTED 38951610
unix  2  [ ] STREAM CONNECTED 38978113
unix  2  [ ] STREAM CONNECTED 38994165
unix  2  [ ] STREAM CONNECTED 39011149
unix  2  [ ] STREAM CONNECTED 39018267
unix  2  [ ] STREAM CONNECTED 39028043
unix  2  [ ] STREAM CONNECTED 39031157
unix  2  [ ] STREAM CONNECTED 39075371
unix  2  [ ] STREAM CONNECTED 39135341
unix  2  [ ] STREAM CONNECTED 39386630
unix  2  [ ] STREAM CONNECTED 39513199
unix  2  [ ] STREAM CONNECTED 39530596
unix  2  [ ] STREAM CONNECTED 39543718
unix  2  [ ] STREAM CONNECTED 39550671
unix  2  [ ] STREAM CONNECTED 39597986
unix  2  [ ] STREAM CONNECTED 39691351
unix  2  [ ] STREAM 

Bug#427494: Precise issue...

[D G]

Ati (open source driver): Metacity works. Compiz and Beryl don't work

fglrx (last version): does not work at all with this card

> 
>   Hi !
> 
> You are not clear enough with your last message.
> 
> The question is to know wether the ATI driver works but beryl not or if it 
> does not work at all...
> 
> Romain

_
With Windows Live Hotmail, you can personalize your inbox with your favorite 
color.
www.windowslive-hotmail.com/learnmore/personalize.html?locale=en-us&ocid=TXT_TAGLM_HMWL_reten_addcolor_0607

Bug#427494: fglrx-driver: Version 8.37.6-1: no screen found

[D G]

Thank you for your reply.

> 
> The mentioned driver does not support this card. Support for Radeon
> 8550/9000/9200 has been dropped after driver version 8.28.8. Please read
> the release notes of the ATI drivers. But your card should be perfectly
> supported by the open radeon(5) driver. 

Maybe it should, but it doesn't :-( . Beryl does not work with the ati open 
source driver. Indeed, I tried fglrx because, by searching on google, people 
recommended to use fglrx for Beryl instead of ati. I started a thread on 
http://forums.debian.net/viewtopic.php?t=15707

So it is up to you. You can close the bug and I submit a bug against 
xserver-xorg-video-ati, or if (and only if) you still want to work on this bug, 
I can send the log for you (sorry for the silly question but, where can I find 
the log? And, how can I manage in text mode to save it?).

Yours,

David 
_
Express yourself instantly with MSN Messenger! Download today it's FREE!
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/

Bug#425882: 2:2.0.0-3 not bad, but doesn't solve it

[D G]

> we forward the bug report it on
> bugzilla.freedesktop.org and wait for upstream developer to fix it.

It would be brilliant that the Debian community were able to do better than the 
upstream :-D

> 
> If your bug is the same than one above, then upstream is already
> notified of your problem and there is no need to notify it again unless
> we have some interesting detail to add to the discussion. 

I think that this thread would be interesting for them. Nevertheless, I am 
enclosing some pieces of extra info at the end of this mail

> That's why I'd like to know whether you think you
> problem is explained there.

In principle it looks the same. But, who knows

> 
> Even outside of beryl/compiz? XAANoOffscreenPixmaps might help for these
> compositing window manager, but should not bring any improvement in
> regular window managers (and hurts basic 3D performance).

With metacity, videos (or rather, this particular video) is OK, so there is 
nothing to fix with metacity.

Now, some pieces of extra information:

1) At boot, it reads something like "skipping blacklisted module i8xx_tco". Is 
it right?

2) On one on the former threads, it read how to change by hand the linear 
allocation. I played around, setting very big numbers. Although the problem 
with videos was NOT fixed, gnome was much faster; as it should be, because the 
computer is Pentium dual core with 2 GB RAM. So it looks like if the graphic 
driver were slowing down all the usage (so I could have purchased a cheaper 
computer :-D ).

3) The output when starting Beryl:

$ beryl-manager
$ libGL warning: 3D driver claims to not support visual 0x66
**
* Beryl system compatibility check   *
**

Detected xserver: AIGLX

Checking Display :0.0 ...

Checking for XComposite extension   : passed (v0.3)
Checking for XDamage extension  : passed
Checking for RandR extension: passed
Checking for XSync extension: passed

Checking Screen 0 ...

libGL warning: 3D driver claims to not support visual 0x66
Checking for GLX_SGIX_fbconfig  : passed
Checking for GLX_EXT_texture_from_pixmap: passed
Checking for non power of two texture support   : passed
Checking maximum texture size   : passed (2048x2048)

libGL warning: 3D driver claims to not support visual 0x66



_
Express yourself instantly with MSN Messenger! Download today it's FREE!
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/

Bug#425882: 2:2.0.0-3 not bad, but doesn't solve it

[D G]

Thank you.

> 
> This error points me to the following bugs:
> https://bugs.freedesktop.org/show_bug.cgi?id=9930
> https://bugs.freedesktop.org/show_bug.cgi?id=10912
> You might want to look at them.

Then, what do you mean? Do you mean that it is a bug on another package, not on 
xserver-xorg-video-intel?

> 
> Does it help if you remove "XAANoOffscreenPixmaps" from your config? If
> I remember correctly, this option may hurt 2D.

No The content inside the windows disappears. X becomes unusable!

Thank you,

David

_
With Windows Live Hotmail, you can personalize your inbox with your favorite 
color.
www.windowslive-hotmail.com/learnmore/personalize.html?locale=en-us&ocid=TXT_TAGLM_HMWL_reten_addcolor_0607

Bug#425882: 2:2.0.0-3 not bad, but doesn't solve it

[D G]

 
> Does the crash report any X-related error in the terminal where you
> launched Xine?

Here the output (with version 2:2.0.0-3 of the driver):

$ totem file.avi
The program 'totem' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
  (Details: serial 72 error_code 11 request_code 141 minor_code 19)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)


> 
> Ok, might be yet another XV problem then. Please try with 2:2.0.0-3, it
> got some new XV-relate fixes.
> 

I am afraid it is the same. With x11 output OK. With xv, crash in less than one 
second. Here the output for the two possibilities (with driver 2:2.0.0-3):

$ gmplayer -vo x11 file.avi 
MPlayer 1.0rc1-4.1.2-DFSG-free (C) 2000-2006 MPlayer Team
CPU: Genuine Intel(R) CPU   T2060  @ 1.60GHz (Family: 6, Model: 14, 
Stepping: 12)
CPUflags:  MMX: 1 MMX2: 1 3DNow: 0 3DNow2: 0 SSE: 1 SSE2: 1
Compiled with runtime CPU detection.
mplayer: could not connect to socket
mplayer: No such file or directory
Failed to open LIRC support. You will not be able to use your remote control.

Playing file.avi.
AVI file format detected.
VIDEO:  [MJPG]  320x240  24bpp  15.237 fps  1968.3 kbps (240.3 kbyte/s)
==
Opening video decoder: [ffmpeg] FFmpeg's libavcodec codec family
[mjpeg @ 0x87fff1c]mjpeg: using external huffman table
Selected video codec: [ffmjpeg] vfm: ffmpeg (FFmpeg MJPEG decoder)
==
==
Opening audio decoder: [pcm] Uncompressed PCM audio decoder
AUDIO: 11025 Hz, 1 ch, s16le, 176.4 kbit/100.00% (ratio: 22050->22050)
Selected audio codec: [pcm] afm: pcm (Uncompressed PCM)
==
[AO OSS] audio_setup: Can't open audio device /dev/dsp: Device or resource busy
AO: [alsa] 48000Hz 1ch s16le (2 bytes per sample)
Starting playback...
VDec: vo config request - 320 x 240 (preferred colorspace: Planar 422P)
Could not find matching colorspace - retrying with -vf scale...
Opening video filter: [scale]
VDec: using Planar 422P as output csp (no 1)
Movie-Aspect is undefined - no prescaling applied.
SwScaler: using unscaled yuv422p -> rgb32 special converter
VO: [x11] 320x240 => 320x240 BGRA 
A:  19.8 V:  19.8 A-V:  0.003 ct:  0.071 302/302  4%  2%  0.7% 0 0  
 

Exiting... (Quit)
$ gmplayer -vo xv file.avi 
MPlayer 1.0rc1-4.1.2-DFSG-free (C) 2000-2006 MPlayer Team
CPU: Genuine Intel(R) CPU   T2060  @ 1.60GHz (Family: 6, Model: 14, 
Stepping: 12)
CPUflags:  MMX: 1 MMX2: 1 3DNow: 0 3DNow2: 0 SSE: 1 SSE2: 1
Compiled with runtime CPU detection.
mplayer: could not connect to socket
mplayer: No such file or directory
Failed to open LIRC support. You will not be able to use your remote control.

Playing file.avi.
AVI file format detected.
VIDEO:  [MJPG]  320x240  24bpp  15.237 fps  1968.3 kbps (240.3 kbyte/s)
==
Opening video decoder: [ffmpeg] FFmpeg's libavcodec codec family
[mjpeg @ 0x87fff1c]mjpeg: using external huffman table
Selected video codec: [ffmjpeg] vfm: ffmpeg (FFmpeg MJPEG decoder)
==
==
Opening audio decoder: [pcm] Uncompressed PCM audio decoder
AUDIO: 11025 Hz, 1 ch, s16le, 176.4 kbit/100.00% (ratio: 22050->22050)
Selected audio codec: [pcm] afm: pcm (Uncompressed PCM)
==
[AO OSS] audio_setup: Can't open audio device /dev/dsp: Device or resource busy
AO: [alsa] 48000Hz 1ch s16le (2 bytes per sample)
Starting playback...
VDec: vo config request - 320 x 240 (preferred colorspace: Planar 422P)
Could not find matching colorspace - retrying with -vf scale...
Opening video filter: [scale]
VDec: using Planar 422P as output csp (no 1)
Movie-Aspect is undefined - no prescaling applied.
SwScaler: reducing / aligning filtersize 1 -> 4
SwScaler: reducing / aligning filtersize 1 -> 4
SwScaler: reducing / aligning filtersize 1 -> 1
SwScaler: reducing / aligning filtersize 9 -> 8

SwScaler: BICUBIC scaler, from yuv422p to yuv420p using MMX2
SwScaler: using 4-tap MMX scaler for horizontal luminance scaling
SwScaler: using 4-tap MMX scaler for horizontal chrominance scaling
SwScaler: using 1-tap MMX "scaler" for vertical scaling (YV12 like)
Sw

Bug#425882: 2:2.0.0-2 looks the same for me + suggestion

[D G]

Thank you for the reply. By the way: a bug for 2:2.0.0-2: when you wander onto 
an inactive window, the mouse pointer disappears.

Anyway, I have downgraded to the driver in unstable, bacause of serious 
problems with the one in experimental (eg, ctrl+alt+F1 and you are done :-)  ).

> 
> I am sure resizing windows is supposed to be fast as of now. Lots of
> people have seen it being slow,

remember: with the obsolete -modesetting driver, that is OK. Maybe this one 
needs rechecking and see which feature from the obsolete one is missing in the 
new one (but be careful, with -modesetting, the colours of the AVI were 
horrible).

> What about other operations instead of resize, for
> instance move? 

That's OK. I mean, if you stare at the window border as it is waving, you see 
that the refresh is not perfect. But, in general, moving is OK.

> Which beryl and compiz packages/versions did you try?

Beryl: 0.3.0.x from [EMAIL PROTECTED] (ie, from sidux). Compiz (only once, just 
for checking): the one in unstable.

> What about videos outside of both beryl and compiz ? 

OK, but after installing xine from experimental. With the one in unstable, the 
image freezes after a few seconds (on metacity, in Beryl it crashes from the 
beginning).

> Which video plugin
> are you using when playing these videos? For instance, in mplayer, you
> can do mplayer -vo x11 foo.avi to use the x11 plugin. Please try at
> least x11 and xv.

Wow! With x11, even on Beryl,  mplayer works! But it is the only one that 
works in beryl. Totem (with xine) and vlc hang. Idem gmplayer with xv. Look,

$ gmplayer -vo xv file.avi 
MPlayer 1.0rc1-4.1.2-DFSG-free (C) 2000-2006 MPlayer Team
CPU: Genuine Intel(R) CPU   T2060  @ 1.60GHz (Family: 6, Model: 14, 
Stepping: 12)
CPUflags:  MMX: 1 MMX2: 1 3DNow: 0 3DNow2: 0 SSE: 1 SSE2: 1
Compiled with runtime CPU detection.
mplayer: could not connect to socket
mplayer: No such file or directory
Failed to open LIRC support. You will not be able to use your remote control.

Playing file.avi
AVI file format detected.
VIDEO:  [MJPG]  320x240  24bpp  15.237 fps  1968.3 kbps (240.3 kbyte/s)
==
Opening video decoder: [ffmpeg] FFmpeg's libavcodec codec family
[mjpeg @ 0x87fff1c]mjpeg: using external huffman table
Selected video codec: [ffmjpeg] vfm: ffmpeg (FFmpeg MJPEG decoder)
==
==
Opening audio decoder: [pcm] Uncompressed PCM audio decoder
AUDIO: 11025 Hz, 1 ch, s16le, 176.4 kbit/100.00% (ratio: 22050->22050)
Selected audio codec: [pcm] afm: pcm (Uncompressed PCM)
==
AO: [oss] 11025Hz 1ch s16le (2 bytes per sample)
Starting playback...
VDec: vo config request - 320 x 240 (preferred colorspace: Planar 422P)
Could not find matching colorspace - retrying with -vf scale...
Opening video filter: [scale]
VDec: using Planar 422P as output csp (no 1)
Movie-Aspect is undefined - no prescaling applied.
SwScaler: reducing / aligning filtersize 1 -> 4
SwScaler: reducing / aligning filtersize 1 -> 4
SwScaler: reducing / aligning filtersize 1 -> 1
SwScaler: reducing / aligning filtersize 9 -> 8

SwScaler: BICUBIC scaler, from yuv422p to yuv420p using MMX2
SwScaler: using 4-tap MMX scaler for horizontal luminance scaling
SwScaler: using 4-tap MMX scaler for horizontal chrominance scaling
SwScaler: using 1-tap MMX "scaler" for vertical scaling (YV12 like)
SwScaler: 320x240 -> 320x240
VO: [xv] 320x240 => 320x240 Planar YV12 
[ws] Error in display.
[ws]  Error code: 11 ( BadAlloc (insufficient resources for operation) )
[ws]  Request code: 141
[ws]  Minor code: 19
[ws]  Modules: flip_page


_
News, entertainment and everything you care about at Live.com. Get it now!
http://www.live.com/getstarted.aspx

Bug#425882: 2:2.0.0-2 looks the same for me + suggestion

[D G]

> 
> A new update of the driver (2:2.0.0-2, based on current upstream git
> snapshot) is currently pending in incoming (incoming.debian.org) and
> will enter experimental tonight. You might want to give it a try, in
> case it helps.
> 

Thank you for the effort.

Not really, this version seems not to give any difference: beryl is still 
bloated (eg, when resizing a window) and AVI videos do not play either on Beryl 
or Compiz.

Maybe an interesting point to start from is that, with the (obsolete) package 
xserver-xorg-video-i810-modesetting from unstable, Beryl works OK and AVI 
videos do play on Beryl. The bad point here was that the colours for the AVI 
files were horrible. 

But the two positive points about that package could be a good starting point.
_
Explore the seven wonders of the world
http://search.msn.com/results.aspx?q=7+wonders+world&mkt=en-US&form=QBRE

Bug#425882: xserver-xorg-video-i810: Out of video RAM with a 256 MB Intel GMA 950

[D G]

Thank you for your quick reply.  

> Is this the amount of Video RAM or regular RAM? 

I'm flattered. Don't overestimate my knowledge :-) How can I know that? (I said 
video RAM because it was what the xine maintainer claimed).

> Do you have a setting
> for AGP aperture in the BIOS?

How can I know that? So far I just know that it is set on the BIOS to 256 M 
(the maximum).

> > xserver-xorg-video-i810-modesetting from experimental does not work on my 
> > computer. xserver-xorg-video-i810-modesetting from unstable works OK
> 
> These packages are obsoletes.
> 
> xserver-xorg-video-intel still has several bugs unfortunately...

Now I have installed xserver-xorg-video-intel and xserver-xorg-video-i810, both 
packages. That's OK, isn't it?

> 
> Please send the output of
> /usr/share/bug/xserver-xorg-core/script 3>&1
> so that we see your config and log (after reistalling
> xserver-xorg-video-intel).
> 

I am sending this mail only to you because I do not know if this ouput could 
have any confidencial information. If not, you can put it in the bug thread.

Contents of /var/lib/x11/X.roster:
xserver-xorg

/etc/X11/X target does not match checksum in /var/lib/x11/X.md5sum.

X server symlink status:
lrwxrwxrwx 1 root root 13 2007-04-15 20:03 /etc/X11/X -> /usr/bin/Xorg
-rwxr-xr-x 1 root root 1736280 2007-05-16 14:44 /usr/bin/Xorg

Contents of /var/lib/x11/xorg.conf.roster:
xserver-xorg

VGA-compatible devices on PCI bus:
00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS/940GML 
Express Integrated Graphics Controller (rev 03)

/etc/X11/xorg.conf does not match checksum in /var/lib/x11/xorg.conf.md5sum.

Xorg X server configuration file status:
-rw-r--r-- 1 root root 3511 2007-05-10 19:17 /etc/X11/xorg.conf

Contents of /etc/X11/xorg.conf:
# /etc/X11/xorg.conf (xorg X Window System server configuration file)
#
# This file was generated by dexconf, the Debian X Configuration tool, using
# values from the debconf database.
#
# Edit this file with caution, and see the /etc/X11/xorg.conf manual page.
# (Type "man /etc/X11/xorg.conf" at the shell prompt.)
#
# This file is automatically updated on xserver-xorg package upgrades *only*
# if it has not been modified since the last upgrade of the xserver-xorg
# package.
#
# If you have edited this file but would like it to be automatically updated
# again, run the following command:
#   sudo dpkg-reconfigure -phigh xserver-xorg

Section "Files"
FontPath"/usr/share/fonts/X11/misc"
FontPath"/usr/X11R6/lib/X11/fonts/misc"
FontPath"/usr/share/fonts/X11/cyrillic"
FontPath"/usr/X11R6/lib/X11/fonts/cyrillic"
FontPath"/usr/share/fonts/X11/100dpi/:unscaled"
FontPath"/usr/X11R6/lib/X11/fonts/100dpi/:unscaled"
FontPath"/usr/share/fonts/X11/75dpi/:unscaled"
FontPath"/usr/X11R6/lib/X11/fonts/75dpi/:unscaled"
FontPath"/usr/share/fonts/X11/Type1"
FontPath"/usr/X11R6/lib/X11/fonts/Type1"
FontPath"/usr/share/fonts/X11/100dpi"
FontPath"/usr/X11R6/lib/X11/fonts/100dpi"
FontPath"/usr/share/fonts/X11/75dpi"
FontPath"/usr/X11R6/lib/X11/fonts/75dpi"
# path to defoma fonts
FontPath"/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"
EndSection

Section "Module"
Load"i2c"
Load"bitmap"
Load"ddc"
Load"dri"
Load"extmod"
Load"freetype"
Load"glx"
Load"int10"
Load"vbe"
EndSection

Section "InputDevice"
Identifier  "Generic Keyboard"
Driver  "kbd"
Option  "CoreKeyboard"
Option  "XkbRules"  "xorg"
Option  "XkbModel"  "pc105"
Option  "XkbLayout" "es"
EndSection

Section "InputDevice"
Identifier  "Configured Mouse"
Driver  "mouse"
Option  "CorePointer"
Option  "Device""/dev/input/mice"
Option  "Protocol"  "ImPS/2"
Option  "Emulate3Buttons"   "true"
EndSection

Section "InputDevice"
Identifier  "Synaptics Touchpad"
Driver  "synaptics"
Option  "SendCoreEvents""true"
Option  "Device""/dev/psaux"
Option  "Protocol"  "auto-dev"
Option  "HorizScrollDelta"  "0"
EndSection

Section "Device"
Identifier  "Intel Corporation Mobile 945GM/GMS/940GML Express 
Integrated Graphics Controller"
Driver  "i810"
BusID   "PCI:0:2:0"
Option "XAANoOffscreenPixmaps" "true"
# Add the following to your Device section in /etc/X11/xorg.conf if you 
wish to have window decorations. 
Option "AddARGBGLXVisuals"
EndSection

Section "Monitor"

Bug#425451: Totem crashes when trying to play video

[D G]

> 
> Does this also happen if you don't use beryl, like metacity?

With Beryl, it crashed from the beginning. With metacity, a few seconds OK, 
then the video freezes, and the sound continues correctly.

> Does it
> only happen on that screen resolution?

After lowering the resolution I get the same.


> Could you please install libxine1 and libxine1-ffmpeg from
> debian/experimental and check if the bug still happens?

Wow! It works on Metacity. 

But not on Beryl. With Beryl, it keeps on crashing from the beginning.

On the other hand, I have only tested it with one video (this computer is new), 
I don't know whether it works correctly in general.
_
Connect to the next generation of MSN Messenger 
http://imagine-msn.com/messenger/launch80/default.aspx?locale=en-us&source=wlmailtagline

Bug#425470: Correction: it is very buggy :-)

[D G]

Sorry, it wasn't my fault. There are several bugs:

1) Change the minutes manually and do nothing, just wait a few seconds: it will 
be restored to the former value. If you want to correct the time, you have to 
proceed very quickly.

2) Although you have changed manually, the clock in the panel takes too long to 
update. "synchronize now" updates the panel *only sometimes*.

3) Change the time manually, if the clock in the panel is updated close the 
window. Then reopen the settings and change from manual to synchronize with 
servers. It will claim that ntp is not working (sometimes, other times it won't 
complain :-D  ).

_
Connect to the next generation of MSN Messenger 
http://imagine-msn.com/messenger/launch80/default.aspx?locale=en-us&source=wlmailtagline

Bug#425470: Not possible adjust time by clicking on the clock

[D G]

Yes, I see that I have to run ntpd at root :-D

But, why isn't it started at boot time?

On the other hand, I think ntpd does not work behind a proxy.

Maybe both issues should be posted to ntp bugs??


> This seems to work fine for me. Is the ntp service running? What version
> of system-tools-backends do you have?
> 

_
Connect to the next generation of MSN Messenger 
http://imagine-msn.com/messenger/launch80/default.aspx?locale=en-us&source=wlmailtagline

Bug#425464: totem-xine: Totem crashes when trying to play video

[D G]

Thank you

So, what shall I do? Shall I run dpkg-reconfigure xserver-xorg and, when asked 
about the memory for graphics, shall I enter 256 MB (that is the amount of the 
card), instead of leaving it blank?

Or, shall I do it by hand on xorg.conf? How?


> 
> I have already seen this on a i955GM graphics card. The solution is to
> increase the available video memory (these controllers use shared system
> memory) with the VideoRAM option in xorg.conf.
> 

_
Invite your mail contacts to join your friends list with Windows Live Spaces. 
It's easy!
http://spaces.live.com/spacesapi.aspx?wx_action=create&wx_url=/friends.aspx&mkt=en-us

Bug#425559: Shell output

[D G]

After closing Icedove, I get this on the shell

sh: paperconf: command not found

I do not know whether it has something to do.
_
News, entertainment and everything you care about at Live.com. Get it now!
http://www.live.com/getstarted.aspx

Bug#425559: Not possible to compose in Icedove 2

[D G]

Package: Icedove
Version: 2.0.0.0-3

When trying to compose an email, you get a window "An error occurred while 
creating a message compose window. Please try again". 

On the terminal, no message is shown.
_
Explore the seven wonders of the world
http://search.msn.com/results.aspx?q=7+wonders+world&mkt=en-US&form=QBRE

Bug#425552: Scrolling doesn't work in Icedove 2

[D G]

Package: Icedove
Version: 2.0.0.0-3

I have icedove and icedove-gnome-support, both 2.0.0.0-3.

The scrolling wheel of the mouse, if you want to move up and down, has no 
effect.
_
Explore the seven wonders of the world
http://search.msn.com/results.aspx?q=7+wonders+world&mkt=en-US&form=QBRE

Bug#425470: Not possible adjust time by clicking on the clock

[D G]

This issue is almost solved. The dialog opens and it uses the usual gnome 
granting rights utility (brilliant).

But, if I select manual to change it once, and then I select synchronize, it 
claims "ntp support not installed", although I do have the package ntp 
installed.

On the other hand, it seems that synchronization does not work when you are 
behind a proxy.






> Subject: Re: Bug#425470: Not possible adjust time by clicking on the clock
> From: [EMAIL PROTECTED]
> To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Date: Tue, 22 May 2007 10:20:57 +0200
> 
> Le lundi 21 mai 2007 à 23:11 +0200, D G a écrit :
> > Package: gnome-system-tools Version: 2.18.1-1 If you select System ->
> > Administration -> Time and Date, it works. If you run time-admin as
> > root, it works too. But, if you right click on the clock and select
> > "Adjust date and time", you get "You are not allowed to access the
> > system configuration" (exactly the same if you run time-admin as non
> > root).
> 
> Could you try again with gnome-panel 2.18.1-2 ? It should have fixed
> this issue.
> > 
> > __
> > Discover the new Windows Vista Learn more!
> 
> No thanks.
> 
> -- 
>  .''`.
> : :' :  We are debian.org. Lower your prices, surrender your code.
> `. `'   We will add your hardware and software distinctiveness to
>   `-our own. Resistance is futile.
> 

_
Invite your mail contacts to join your friends list with Windows Live Spaces. 
It's easy!
http://spaces.live.com/spacesapi.aspx?wx_action=create&wx_url=/friends.aspx&mkt=en-us

Bug#425464: Bug#425451: Totem crashes when trying to play video

[D G]

Hello,

>  Thanks for your report; please use the reportbug tool to file bug; 

I have used now the command reportbug. Is it correct? (it is the first time I 
am asked to do so).

Is it the same if I use gnome-reportbug?

> what is your xine version?

Do you mean the version of libxine1? It is 1.1.2+dfsg-4

> 
>Thanks,
> -- 
> Loïc Minier

_
Discover the new Windows Vista
http://search.msn.com/results.aspx?q=windows+vista&mkt=en-US&form=QBRE

Bug#425472: Dependencies of liferea not satisfied in sid

[D G]

Package: liferea
Version: 1.2.14-1

If you want to upgrade to this new version, you have to delete the 
liferea-xulrunner that is currently in sid (new version of liferea-xulrunner is 
not in sid yet).
_
News, entertainment and everything you care about at Live.com. Get it now!
http://www.live.com/getstarted.aspx

Bug#425471: gnome-games-data conflicts with gnome-games in sid

[D G]

Package: gnome-games-data
Version: 1:2.18.1-2

If you want to upgrade to this new version, you have to remove the gnome-games 
and gnome-desktop-environment that are currently in sid.
_
Connect to the next generation of MSN Messenger 
http://imagine-msn.com/messenger/launch80/default.aspx?locale=en-us&source=wlmailtagline

Bug#425470: Not possible adjust time by clicking on the clock

[D G]

Package: gnome-system-tools
Version: 2.18.1-1

If you select System -> Administration -> Time and Date, it works. If you run 
time-admin as root, it works too. 

But, if you right click on the clock and select "Adjust date and time", you get 
"You are not allowed to access the system configuration" (exactly the same if 
you run time-admin as non root).
_
Discover the new Windows Vista
http://search.msn.com/results.aspx?q=windows+vista&mkt=en-US&form=QBRE

Bug#425451: Totem crashes when trying to play video

[D G]

Package: totem-xine
Version: 2.16.6-1

I use Debian unstable, my graphic card is VGA compatible controller: Intel 
Corporation Mobile 945GM/GMS/940GML Express Integrated Graphics Controller (rev 
03), I use Beryl, and the screen resolution is 1280x800.

I tried to open an .avi file (I have the w32codecs installed) and totem 
crashed. The output on the shell is

The program 'totem' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
  (Details: serial 67 error_code 11 request_code 141 minor_code 19)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

_
Invite your mail contacts to join your friends list with Windows Live Spaces. 
It's easy!
http://spaces.live.com/spacesapi.aspx?wx_action=create&wx_url=/friends.aspx&mkt=en-us

Bug#424864: Bad fonts with latest version

[D G]

Package: msttcorefonts
Version: 2.0

A way to reproduce it: if you login in hotmail, the bold fonts "My messages" 
are blurred, and the uppercase W is horrible. You can see a snapshot from 
another person on http://forums.debian.net/viewtopic.php?p=72010#72010


On the same forum, they claim that, if you downgrade to version 1.8, the 
problem is solved.


_
Moda para esta temporada. Ponte al día de todas las tendencias. 
http://www.msn.es/Mujer/moda/default.asp




--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#422097: Gdm badly configured after upgrade

[D G]

Package: gdm
Version: 2.18.1-1

I selected to replace my current configuration with the configuration 
provided by the maintainer. Then, gdm intended to start Xclient script 
instead of gnome, and failed to start the Xclient script.


_
¿Estás pensando en cambiar de coche? Todas los modelos de serie y extras en 
MSN Motor. http://motor.msn.es/researchcentre/




--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#394821: Proprietary driver from Matrox resolved the problem

[D G Teed]

A user at DebianHelp.org suggested I try the Matrox driver from
Matrox.  Earlier I did a compile from Debian sources at sarge1
release level and it did not resolve the problem.  I worked
in vesa mode for a couple of days before installing the Matrox
proprietary driver, which resolves the issue for me.  However
I believe mga driver was working without this driver from
Matrox prior to the update.

See this thread for some potential leads on what nm tracing revealed:

http://www.debianhelp.org/node/1603#comment-1225


--Donald Teed


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#394821: mga_drv unresolved symbols after 4.3.0.dfsg.1-14sarge2 upgrade

[D G Teed]

Package: xserver-xfree86
Version: 4.3.0.dfsg.1-14sarge2

I have a G400 that was working fine in the most previous
release (sarge1?) of xfree86 group of packages in Debian 3.1 stable.

On the first reboot following the upgrade to 4.3.0.dfsg.1-14sarge2
of the series of related xfree86 packages, X refuses to
run, with errors like so:

XFree86 Version 4.3.0.1 (Debian 4.3.0.dfsg.1-14sarge2 20061002194300
[EMAIL PROTECTED])
Release Date: 15 August 2003
X Protocol Version 11, Revision 0, Release 6.6
Build Operating System: Linux 2.6.18-1-686 i686 [ELF] Build Date: 02 October 
2006


Module Loader present
OS Kernel: Linux version 2.6.16.18 ([EMAIL PROTECTED]) (gcc
version 3.3.5 (Debian 1:3.3.5-13)) #1 SMP PREEMPT Sun Oct 22 12:47:58
ADT 2006 Markers: (--) probed, (**) from config file, (==) default setting,
 (++) from command line, (!!) notice, (II) informational,
 (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/XFree86.0.log", Time: Sun Oct 22 23:52:30 2006
(==) Using config file: "/etc/X11/XF86Config-4"
Skipping "/usr/X11R6/lib/modules/extensions/libGLcore.a:m_debug_clip.o":
No symbols found
Skipping "/usr/X11R6/lib/modules/extensions/libGLcore.a:m_debug_norm.o":
No symbols found
Skipping
"/usr/X11R6/lib/modules/extensions/libGLcore.a:m_debug_xform.o":  No
symbols found
Skipping
"/usr/X11R6/lib/modules/extensions/libGLcore.a:m_debug_vertex.o":  No
symbols found
Skipping "/usr/X11R6/lib/modules/fonts/libspeedo.a:spencode.o":  No
symbols found
(WW) MGA(0): Failed to set up write-combining range
(0xf800,0x200)
Required symbol MGAValidateMode from module
/usr/X11R6/lib/modules/drivers/mga_drv.o is unresolved!
Required symbol MGASetMode from module
/usr/X11R6/lib/modules/drivers/mga_drv.o is unresolved!
Required symbol MGASetMode from module
/usr/X11R6/lib/modules/drivers/mga_drv.o is unresolved!
Required symbol MGASetMode from module
/usr/X11R6/lib/modules/drivers/mga_drv.o is unresolved!
Required symbol MGASetMode from module
/usr/X11R6/lib/modules/drivers/mga_drv.o is unresolved!
Required symbol MGASetMode from module
/usr/X11R6/lib/modules/drivers/mga_drv.o is unresolved!
Required symbol MGASetMode from module
/usr/X11R6/lib/modules/drivers/mga_drv.o is unresolved!
Required symbol MGASetMode from module
/usr/X11R6/lib/modules/drivers/mga_drv.o is unresolved!
Required symbol MGASetMode from module
/usr/X11R6/lib/modules/drivers/mga_drv.o is unresolved!
Required symbol MGASetMode from module
/usr/X11R6/lib/modules/drivers/mga_drv.o is unresolved!
Required symbol MGASetMode from module
/usr/X11R6/lib/modules/drivers/mga_drv.o is unresolved!
Required symbol MGACloseLibrary from module
/usr/X11R6/lib/modules/drivers/mga_drv.o is unresolved!
Required symbol HALSetDisplayStart from module
/usr/X11R6/lib/modules/drivers/mga_drv.o is unresolved!
Required symbol HALSetDisplayStart from module
/usr/X11R6/lib/modules/drivers/mga_drv.o is unresolved!
Required symbol MGAGetHardwareInfo from module
/usr/X11R6/lib/modules/drivers/mga_drv.o is unresolved!
Required symbol MGAOpenLibrary from module
/usr/X11R6/lib/modules/drivers/mga_drv.o is unresolved!
Required symbol MGAGetBOARDHANDLESize from module
/usr/X11R6/lib/modules/drivers/mga_drv.o is unresolved!

...and a few more lines like these before "Fatal server error".

Everything was fine with the same XF86Config file
previously.  If I switch to vesa, X starts OK.
However I need dual monitors so mga is a must.

It appears that Debian's Xfree86 sources are unique,
so compiling a solution as per http://dri.freedesktop.org/wiki/Building
doesn't seem to be an option within Debian stable.

I tried downgrading to sarge1, but it has not helped:

for pack in `COLUMNS=200 dpkg -l | grep x | grep 4.3.0.dfsg.1-14sarge2 | awk 
'{print $2}'`; do apt-get -y install --reinstall $pack=4.3.0.dfsg.1-14sarge1; 
done



Any more information needed, please ask me...

--Donald Teed


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]