On Thursday 03 June 2010 04:17:19, Rene Engelhard wrote:
> severity 584322 important
> tag 584322 + unreproducible
> tag 584322 + moreinfo
> thanks
> 
> On Thu, Jun 03, 2010 at 03:23:40AM -0400, Chris Knadle wrote:
> > Package: openoffice.org-writer
> > Version: 1:3.2.0-10
> > Severity: grave
> > Tags: sid
> 
> That means 3.2.0-9 from testing works?. (That's what those infos say)

I do not have a box in Testing, so I have not tested 3.2.0-9 in it.  Tagging 
the problem as 'sid' was probably an error on my part.  [Thanks for that 
pointer.]

> > Justification: renders package unusable
> 
> For you maybe. There have been 7 days now without a report like
> this so it doesn't seem to be a general problem. Inflated severities
> are not good.

Not an easy call.  The behavior I see seems like it's grave, so I think the 
severity was right, just maybe not the particular package the bug is under.
I just don't know how to track down which package it should be under instead 
in this case.

> Nvidia? ATIs fglrx? compiz? Something else broken in use?

I normally use the proprietary 'nvidia' driver, however I've tested with both 
the 'nv' driver and the 'vesa' driver and get the exact same error when using 
those drivers too.  :-(

> > ckna...@trelane:~$ oowriter
> > ckna...@trelane:~$ X-Error: BadMatch (invalid parameter attributes)
> > 
> >         Major opcode: 59 (X_SetClipRectangles)
> >         Resource ID:  0x4e000ac
> >         Serial No:    5542 (5542)
> > 
> > ------------------------------------------
> 
> Works here (tm)

Understood.



[from your 2nd mail]:
....
> > Thankfully none of the OO.org programs are critical for me at this
> > time, so for instance if you'd like me to remove particular OO.org
> > extensions and retest I can do that.
> 
> Please do.

As this seems X related I'm not sure removing OO.org extensions would help.  
If you think it will, can you suggest which ones I should remove?

> Please also try on other X setups if you use either nvidia
> or fglrx or compiz.

I don't use compiz nor the compositing built-in to KDE4.  I'm attaching my 
xorg.conf file -- it's short.

  -- Chris

--

Chris Knadle
chris.kna...@coredump.us
# nvidia-settings: X configuration file generated by nvidia-settings
# nvidia-settings:  version 1.0  (bui...@ninsei)  Tue Jun 24 18:11:48 UTC 2008

Section "ServerLayout"
    Identifier     "Layout0"
    Screen      0  "Screen0" 0 0
    InputDevice    "Keyboard0" "CoreKeyboard"
    InputDevice    "Mouse0" "CorePointer"
EndSection

#Section "Files"
#    RgbPath         "/usr/X11R6/lib/X11/rgb"
#EndSection

Section "Module"
    Load           "dbe"
    Load           "extmod"
    Load           "type1"
    Load           "freetype"
    Load           "glx"
EndSection

#Section "ServerFlags"
#    Option         "Xinerama" "0"
#EndSection

Section "InputDevice"
    # generated from default
    Identifier     "Mouse0"
    Driver         "mouse"
    Option         "Protocol" "auto"
    Option         "Device" "/dev/psaux"
    Option         "Emulate3Buttons" "no"
    Option         "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"
    # generated from default
    Identifier     "Keyboard0"
    Driver         "kbd"
EndSection

Section "Monitor"
    # HorizSync source: edid, VertRefresh source: edid
    Identifier     "Monitor0"
    VendorName     "Unknown"
    ModelName      "IBM"
    HorizSync       53.2 - 63.9
    VertRefresh     50.0 - 60.0
    Option         "DPMS"
EndSection

Section "Device"
    Identifier     "Videocard0"
#    Driver         "nvidia"
#    Driver         "vesa"
    Driver         "nv"
    VendorName     "NVIDIA Corporation"
    BoardName      "Quadro FX 570M"
EndSection

Section "Screen"
    Identifier     "Screen0"
    Device         "Videocard0"
    Monitor        "Monitor0"
    DefaultDepth    16
    Option         "TwinView" "1"
    # Option         "metamodes" "DFP-0: 1280x1024 +0+0, DFP-1: 1280x1024 +0+0"
    Option         "metamodes" "CRT: 1280x1024 +0+0, DFP: 1280x1024 +0+0"
    SubSection     "Display"
        Depth       16
    EndSubSection
EndSection

Reply via email to