synaptics looses/hangs mouse
Hello, I recently upgraded my vaio z505 je from sarge to etch. Worked mostly flawless. One thing I noticed was the the mouse tapping was very sensitive, which was annoying. After digging somewhat in google, I found that the Sony has an ALPS mouse topsi:~# cat /proc/bus/input/devices [...] I: Bus=0011 Vendor=0002 Product=0008 Version= N: Name=PS/2 Mouse P: Phys=isa0060/serio1/input1 S: Sysfs=/class/input/input2 H: Handlers=event2 ts0 mouse0 B: EV=7 B: KEY=7 0 0 0 0 0 0 0 0 B: REL=3 I: Bus=0011 Vendor=0002 Product=0008 Version=7321 N: Name=AlpsPS/2 ALPS GlidePoint P: Phys=isa0060/serio1/input0 S: Sysfs=/class/input/input3 H: Handlers=event3 ts1 mouse1 B: EV=f B: KEY=420 0 7 0 0 0 0 0 0 0 0 B: REL=3 B: ABS=103 topsi:~# and I should used the synaptics input driver in xorg I added a new input device to /etc/X11/xorg.conf Section InputDevice Driver synaptics Identifier SMouse Option Protocol auto-dev # Option AccelFactor 0.0010 # Option BottomEdge 4200 # Option Device /dev/psaux # Option Emulate3Buttons on # Option Finger 25 30 # Option FingerHigh 30 # Option FingerLow 25 # Option InputFashion Mouse # Option LeftEdge 1700 # Option MaxSpeed 0.12 # Option MaxTapMove 220 # Option MaxTapTime 180 # Option ClickTime 100 # Option MinSpeed 0.06 # Option Name Synaptics;Touchpad # Option RightEdge 5300 Option SHMConfig on # Option TopEdge 1700 # Option VertScrollDelta 100 Option ZAxisMapping 4 5 EndSection which replaced the old configured PS2 mouse Section InputDevice Identifier Configured Mouse Driver mouse Option CorePointer Option Device/dev/psaux Option Protocol PS/2 Option Emulate3Buttons true Option ZAxisMapping 4 5 EndSection in the ServerLayout Section ServerLayout Identifier Default Layout Screen Default Screen InputDevice Generic Keyboard # InputDevice Configured Mouse InputDevice SMouse EndSection Now I have a mouse which stops working after approximately 30 seconds of usage. /var/log/Xorg.0.log shows (**) Generic Keyboard: Core Keyboard (**) Option Protocol standard (**) Generic Keyboard: Protocol: standard (**) Option AutoRepeat 500 30 (**) Option XkbRules xfree86 (**) Generic Keyboard: XkbRules: xfree86 (**) Option XkbModel pc102 (**) Generic Keyboard: XkbModel: pc102 (**) Option XkbLayout us (**) Generic Keyboard: XkbLayout: us (**) Option CustomKeycodes off (**) Generic Keyboard: CustomKeycodes disabled (II) Synaptics touchpad driver version 0.14.6 (1406) (--) SMouse auto-dev sets device to /dev/input/event3 (**) Option Device /dev/input/event3 (**) Option SHMConfig on (--) SMouse touchpad found (**) Option Protocol PS/2 (**) Configured Mouse: Device: /dev/psaux (**) Configured Mouse: Protocol: PS/2 (**) Option CorePointer (**) Configured Mouse: Core Pointer (**) Option Device /dev/psaux (**) Option Emulate3Buttons true (**) Configured Mouse: Emulate3Buttons, Emulate3Timeout: 50 (**) Option ZAxisMapping 4 5 (**) Configured Mouse: ZAxisMapping: buttons 4 and 5 (**) Configured Mouse: Buttons: 9 (II) XINPUT: Adding extended input device Configured Mouse (type: MOUSE) (II) XINPUT: Adding extended input device SMouse (type: MOUSE) (II) XINPUT: Adding extended input device Generic Keyboard (type: KEYBOARD) Synaptics DeviceInit called SynapticsCtrl called. (II) Configured Mouse: ps2EnableDataReporting: succeeded Could not init font path element /usr/share/fonts/X11/TTF/, removing from list! Could not init font path element /usr/share/fonts/X11/OTF, removing from list! Could not init font path element /usr/share/fonts/X11/CID/, removing from list! Synaptics DeviceOn called (--) SMouse auto-dev sets device to /dev/input/event3 (**) Option Device /dev/input/event3 (--) SMouse touchpad found Any hints where to dig deeper are welcome Many thanks, Rainer -- Rainer Dorsch Alzentalstr. 28 D-71083 Herrenberg 07032-919495 jabber: [EMAIL PROTECTED] GPG Fingerprint: 5966 C54C 2B3C 42CC 1F4F 8F59 E3A8 C538 7519 141E Full GPG key: http://pgp.mit.edu/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#390496: Compiz fails on supersavage on T23 Thinkpad
* DW Price wrote: Package: compiz Version: 0.0.13+git20060928-2 video: S3 Inc. SuperSavage IX/C SDR - T23 Thinkpad kernel: 2.6.18-1-686 #1 SMP Sun Sep 24 13:48:23 UTC 2006 i686 GNU/Linux X Window System Version 7.1.1 ** on running compiz --replace: (gtk-window-decorator:15178): Gtk-WARNING **: Unable to locate theme engine in module_path: clearlooks, libGL warning: 3D driver claims to not support visual 0x4b /usr/bin/compiz.real: Support for non power of two textures missing ^ This indicates that the driver probably doesn't support textures with dimensions that are not powers of two. This is required for compiz to work. I guess this could be reassigned to the S3 driver and have the severity reduced to wishlist perhaps. Anyone? - Thierry signature.asc Description: Digital signature
X Strike Force X.Org X11 SVN commit: r3687 - in trunk/debian/xorg/debian: . po
Author: bubulle Date: 2006-10-08 07:56:28 -0400 (Sun, 08 Oct 2006) New Revision: 3687 Modified: trunk/debian/xorg/debian/changelog trunk/debian/xorg/debian/po/nb.po Log: Norwegian Bokm?\195?\165l translation update Modified: trunk/debian/xorg/debian/changelog === --- trunk/debian/xorg/debian/changelog 2006-10-08 05:34:15 UTC (rev 3686) +++ trunk/debian/xorg/debian/changelog 2006-10-08 11:56:28 UTC (rev 3687) @@ -4,6 +4,7 @@ - Italian. Closes: #391497 - Russian. Closes: #391563 - Catalan. Closes: #372262 +- Norwegian Bokmål. Closes: #391683 [ David Nusinow ] * Add grace6's sarge version to the long list of conflicted packages. Thanks Modified: trunk/debian/xorg/debian/po/nb.po === --- trunk/debian/xorg/debian/po/nb.po 2006-10-08 05:34:15 UTC (rev 3686) +++ trunk/debian/xorg/debian/po/nb.po 2006-10-08 11:56:28 UTC (rev 3687) @@ -1,28 +1,28 @@ -# translation of xserver-xorg_debian_nb.po to Norwegian Bokmål -# -#Translators, if you are not familiar with the PO format, gettext -#documentation is worth reading, especially sections dedicated to -#this format, e.g. by running: -# info -n '(gettext)PO Files' -# info -n '(gettext)Header Entry' -#Some information specific to po-debconf are available at -#/usr/share/doc/po-debconf/README-trans -# or http://www.debian.org/intl/l10n/po-debconf/README-trans# -#Developers do not need to manually edit POT or PO files. -# Bjørn Steensrud [EMAIL PROTECTED], 2006. -# +# translation of xserver-xorg_debian_nb.po to Norwegian Bokmål +# +#Translators, if you are not familiar with the PO format, gettext +#documentation is worth reading, especially sections dedicated to +#this format, e.g. by running: +# info -n '(gettext)PO Files' +# info -n '(gettext)Header Entry' +#Some information specific to po-debconf are available at +#/usr/share/doc/po-debconf/README-trans +# or http://www.debian.org/intl/l10n/po-debconf/README-trans# +#Developers do not need to manually edit POT or PO files. +# +# Bjørn Steensrud [EMAIL PROTECTED], 2006. msgid msgstr Project-Id-Version: xserver-xorg_debian_nb\n Report-Msgid-Bugs-To: \n POT-Creation-Date: 2006-09-17 09:13+0200\n -PO-Revision-Date: 2006-05-30 11:51+0200\n +PO-Revision-Date: 2006-10-03 19:49+0200\n Last-Translator: Bjørn Steensrud [EMAIL PROTECTED]\n Language-Team: Norwegian Bokmål [EMAIL PROTECTED]\n MIME-Version: 1.0\n Content-Type: text/plain; charset=UTF-8\n Content-Transfer-Encoding: 8bit\n -X-Generator: KBabel 1.10\n +X-Generator: KBabel 1.11.2\n #. Type: select #. Choices @@ -143,7 +143,7 @@ #. Description #: ../x11-common.templates:6001 msgid Cannot remove /usr/X11R6/bin directory -msgstr +msgstr Kan ikke slette mappa /usr/X11R6/bin #. Type: note #. Description @@ -155,6 +155,11 @@ are currently in the directory out of the way so that the installation can complete. If you like, you may move them back after the symlink is in place. msgstr +Denne oppgraderingen krever at mappa /usr/X11R6/bin slettes og erstattes +med en symbolsk lenke. Det ble forsøkt gjort, men lyktes ikke, mest trolig +fordi mappa ikke er tom ennå. Du må flytte de filene som er igjen i mappa +ut av veien slik at installasjonen kan fortsette. Hvis du vil kan du flytte dem +tilbake etter at lenka er på plass. #. Type: note #. Description @@ -164,6 +169,9 @@ Please re-run your upgrade procedure after you have cleaned out the directory. msgstr +Denne pakkeinstallasjonen vil nå avslutte som mislykket slik at du +kan gjøre dette. Kjør oppgraderingen om igjen etter at du har tømt +mappa. #. Type: boolean #. Description @@ -422,7 +430,7 @@ #. Description #: ../xserver-xorg.templates:9001 msgid Generic Video Card -msgstr +msgstr Standard videokort #. Type: select #. Description @@ -786,8 +794,7 @@ #. Type: string #. Description #: ../xserver-xorg.templates:18001 -msgid -Users of U.S. English keyboards should generally leave this entry blank. +msgid Users of U.S. English keyboards should generally leave this entry blank. msgstr De som bruker U.S. engelsk tastatur bør la dette være tomt. #. Type: string @@ -1014,8 +1021,7 @@ #. Type: boolean #. Description #: ../xserver-xorg.templates:24001 -msgid -If autodetection fails, you will be asked for information about the monitor. +msgid If autodetection fails, you will be asked for information about the monitor. msgstr Hvis automatisk oppdaging mislykkes blir du spurt om opplysninger om skjermen. @@ -1160,7 +1166,7 @@ #. Description #: ../xserver-xorg.templates:29001 msgid Generic Monitor -msgstr +msgstr Standard skjerm #. Type: boolean #. Description @@ -1360,3 +1366,5 @@ #~ msgstr #~ Opptil 14 tommer (355 mm), 15 tommer (380 mm), 17 tommer (430 mm), 19-20 #~ tommer
Processed: setting package to libglu1-xorg libglu1-xorg-dev x11-common xlibmesa-dri xlibmesa-gl xlibmesa-gl-dev xlibmesa-glu xlibs-data xlibs-static-dev xorg xorg-dev xserver-xfree86 xserver-xorg xser
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.9.21 package libglu1-xorg libglu1-xorg-dev x11-common xlibmesa-dri xlibmesa-gl xlibmesa-gl-dev xlibmesa-glu xlibs-data xlibs-static-dev xorg xorg-dev xserver-xfree86 xserver-xorg xserver-xorg-input-all xserver-xorg-video-all x-window-system x-window-system-core Ignoring bugs not assigned to: xorg xlibmesa-dri xserver-xorg-input-all xserver-xorg-video-all xlibmesa-gl xlibs-static-dev xorg-dev xserver-xfree86 x11-common xlibmesa-gl-dev xlibs-data xserver-xorg x-window-system-core libglu1-xorg-dev x-window-system xlibmesa-glu libglu1-xorg tags 390943 + pending Bug#390943: x11-common: sarge to etch upgrade fails (/usr/X11R6 issue) There were no tags set. Tags added: pending tags 391563 + pending Bug number 391563 belongs to package xserver-xorg-input-kbd, skipping. tags 391683 + pending Bug#391683: Norwegian Bokmål translation for xorg Tags were: d-i l10n patch Tags added: pending End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#379480: (no subject)
On Wed, Sep 20, 2006 at 09:59:44PM +0200, Ji?? Pale?ek wrote: Could you try upgrading xserver-xorg-xxx to unstable version to see whether the problem persists in later versions? Just tried -- again -- upgrading xserver-xorg-core to sid. aptitude added a number of dependencies, and the upgrade worked this time. However, the bug is still present. Mousee frose while using Mozilla, keyboard still worked except fot the ctl-alt combinations for switching consoles, and ctl-alt-backspace for killing X, Did a hardware reset to shut down and reboot. Back to running Ubuntu. Do we need one of the fixes Ubuntu developers should be feeding back to Debian in comprehensible form? -- hendrik -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Feature Freeze
On Sun, Oct 08, 2006 at 11:22:33PM +0200, Michel Dänzer wrote: On Sat, 2006-10-07 at 19:05 -0400, David Nusinow wrote: What do I do if you decided that, the new i810 driver is a good idea too? And the new ati driver? FWIW, the latter should be a very good idea, as it's mostly just fixes, a couple of which are critical. Great, I was going to ask your opinion on this. It looked like the right move to push for it, and I'm glad you think the same. The former isn't necessarily a bad idea either, the minor version bump has no meaning beyond the added SAREA fields. Ok, I'll test it locally and push it if it's good to go. I'd like to get a modesetting package available as well. - David Nusinow -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
libxv 1:1.0.2-1 MIGRATED to testing
FYI: The status of the libxv source package in Debian's testing distribution has changed. Previous version: 1:1.0.1-5 Current version: 1:1.0.2-1 -- This email is automatically generated; [EMAIL PROTECTED] is responsible. See http://people.debian.org/~henning/trille/ for more information. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
x11proto-gl 1.4.8-1 MIGRATED to testing
FYI: The status of the x11proto-gl source package in Debian's testing distribution has changed. Previous version: 1.4.6-2 Current version: 1.4.8-1 -- This email is automatically generated; [EMAIL PROTECTED] is responsible. See http://people.debian.org/~henning/trille/ for more information. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
xfonts-100dpi 1:1.0.0-3 MIGRATED to testing
FYI: The status of the xfonts-100dpi source package in Debian's testing distribution has changed. Previous version: 1:1.0.0-2 Current version: 1:1.0.0-3 -- This email is automatically generated; [EMAIL PROTECTED] is responsible. See http://people.debian.org/~henning/trille/ for more information. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
xfonts-75dpi 1:1.0.0-3 MIGRATED to testing
FYI: The status of the xfonts-75dpi source package in Debian's testing distribution has changed. Previous version: 1:1.0.0-2 Current version: 1:1.0.0-3 -- This email is automatically generated; [EMAIL PROTECTED] is responsible. See http://people.debian.org/~henning/trille/ for more information. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
xfonts-scalable 1:1.0.0-5 MIGRATED to testing
FYI: The status of the xfonts-scalable source package in Debian's testing distribution has changed. Previous version: 1:1.0.0-4 Current version: 1:1.0.0-5 -- This email is automatically generated; [EMAIL PROTECTED] is responsible. See http://people.debian.org/~henning/trille/ for more information. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
xfonts-cyrillic 1:1.0.0-4 MIGRATED to testing
FYI: The status of the xfonts-cyrillic source package in Debian's testing distribution has changed. Previous version: 1:1.0.0-3 Current version: 1:1.0.0-4 -- This email is automatically generated; [EMAIL PROTECTED] is responsible. See http://people.debian.org/~henning/trille/ for more information. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Teamwork (was: Feature Freeze)
On Sunday 08 October 2006 04:19, David Nusinow wrote: If you have concrete suggestions for how to handle these things in the future, and even right now, please post them in a reasonable manner. Maybe some insight in how this works in the Debian Installer team may help. Note that every team (and every release manager) is different, but basic ideas should still be applicable. Both projects (D-I and XFS) are somewhat comparable, especially since XOrg has gone modular. One important difference is of course that a lot of D-I is original, Debian-specific code while XOrg is mostly just packaging. Tracking changes For the D-I repo we have _loads_ of people with commit access, mostly translators but also a fair number of porters and (past) developers. This means that an important tool to keep track for the RM are the CIA commit messages on #debian-boot and the mails that are sent to p.qa.d.o (the PTS) for each SVN commit. We do not have max size limit on the mails, which is possible because they are not sent directly to the d-boot list, but through the PTS. As RM I at least quickly take a look at all commits that are not purely translation updates (which luckily are easily recognizable). The main purpose is to follow what is happening, but a second goal is peer review of changes so we can hopefully catch errors early and to check for consistency between components. How closely I look depends on who made the commit and which component was changed (I tend to look less closely at architecture specific components than general ones). Joey Hess and Colin Watson also check commits in this way, but possibly more selectively. Committing changes -- In principle almost all packages are team maintained and have the d-boot list as Maintainer and one or more developers as Uploaders. In practice a lot of components (or in some cases specific parts of components [1]) have one (maybe two) main maintainer(s) who take care of it. In these cases the main maintainer normally has the freedom to upload when he wants. If changes are invasive or when we are close to preparing a release, he will often ping me (as RM) first. A lot of D-I components are fairly mature and abandoned' to general maintenance. In those cases anybody can commit, but uploading will mostly be left to me as RM [2]. I will check with the committer before uploading if I'm unsure of the status of such pending changes and will often test changes locally before uploading. A few senior team members (joeyh, kamion, tbm) will also uploaded when needed, especially if there are no (or only trivial) pending changes by others. I also track pending uploads of arch specific packages and will mostly ping the relevant porters if an upload is needed for a release (e.g. because of translation updates). I try to encourage sending patches to the BTS or the list for comments before committing if people are unsure of their changes. Releasing - In general active team members will know when a release is coming up. However, I try to clearly announce when preparation for a release is actually started and the schedule I hope to follow, and to send updates when needed. I try also to explicitly mention planned freezes and make requests to not upload without contacting me first. We also keep a wiki page for each release: http://wiki.debian.org/DebianInstaller/EtchRC1Prep I have some tools available that help me to track pending (translation) changes and version differences between unstable and testing (important as udebs currently don't migrate automatically). QA and teamwork --- As RM you sometimes find yourself in a position where someone is making life for the team as a whole (and the RM in particular) harder than necessary, either by regularly committing low quality or untested patches or by not having enough consideration for the juggling act an RM of a large or complex project has to perform or by in general not behaving as a team member. In those cases IMO the RM _has_ to speak up and may, after consulting with other (senior) team members, eventually be forced to take action. I don't think I need to give an example here. Hope this helps, FJP [1] Good example is cdebconf where the GTK frontend has a separate maintainer from the general code and other frontends. [2] Because of this both Joey (as previous RM) and I are uploaders for most components as this is needed for bug closure and I will add myself when needed. pgp4NymdfG71t.pgp Description: PGP signature
Bug#391505: libGLcore.so: undefined symbol: _glapi_Dispatch
On Sat, Oct 07, 2006 at 09:48:46PM -0400, David Nusinow wrote: aiui, You really shouldn't be loading that module. Remove or comment out the line to load it in your xorg.conf. OK, it still gets loaded later, but without the error. Thanks, -ryan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#126519: penny gerwer Superintendent Assistant
Hi penny gerwer. Would you like to generate at least 1.5K to 3.5K daily just for returning phone calls? Give us a call : 800-301-3784 If you have a telephone and can return calls you are fully qualified. Thanks, Davis Jefferson -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#391052: ctrl-alt-+/- thing
On Sat, 2006-10-07 at 10:20 -0700, Matt Taggart wrote: For the problem of ctrl-alt-+/- not working... grepper on #debian-x noticed the following in Xorg.log and I see it too, RADEONHandleMessage(0, KeyEventMessage, -VMode, retmsg) RADEONHandleMessage(0, KeyEventMessage, +VMode, retmsg) grepper also reports seeing the problem with an nv based system (although I assume the log entries are different). See https://bugs.freedesktop.org/show_bug.cgi?id=7097 . -- Earthling Michel Dänzer | http://tungstengraphics.com Libre software enthusiast | Debian, X and DRI developer
Bug#390271: Resizing and scrolling very slow with r200
On Sun, 2006-10-08 at 18:18 +0200, Michel Dänzer wrote: On Sat, 2006-10-07 at 21:35 -0400, David Nusinow wrote: Ideally though, just editing currently broken-for-EXA patch so that it's only on when XAA is enabled is probably a better hack. Indeed. Actually, it should also be verified that disabling offscreen pixmaps is even necessary or a good idea with XAA on integrated chipsets, in particular i[89]xx. -- Earthling Michel Dänzer | http://tungstengraphics.com Libre software enthusiast | Debian, X and DRI developer
Bug#379480: (no subject)
On Sun, Oct 08, 2006 at 09:41:51AM -0400, [EMAIL PROTECTED] wrote: On Wed, Sep 20, 2006 at 09:59:44PM +0200, Ji?? Pale?ek wrote: Could you try upgrading xserver-xorg-xxx to unstable version to see whether the problem persists in later versions? Just tried -- again -- upgrading xserver-xorg-core to sid. aptitude added a number of dependencies, and the upgrade worked this time. However, the bug is still present. Mousee frose while using Mozilla, keyboard still worked except fot the ctl-alt combinations for switching consoles, and ctl-alt-backspace for killing X, Did a hardware reset to shut down and reboot. Back to running Ubuntu. Do we need one of the fixes Ubuntu developers should be feeding back to Debian in comprehensible form? I'm going to go through the ubuntu patches at some point soon and start pulling them for our release. It'd be nice to know what patch you need exactly if you could get that for us... - David Nusinow -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#390496: Compiz fails on supersavage on T23 Thinkpad
reassign 390496 xserver-xorg-core kthxbye On Sun, 2006-10-08 at 12:37 +0200, Thierry Reding wrote: * DW Price wrote: Package: compiz Version: 0.0.13+git20060928-2 video: S3 Inc. SuperSavage IX/C SDR - T23 Thinkpad kernel: 2.6.18-1-686 #1 SMP Sun Sep 24 13:48:23 UTC 2006 i686 GNU/Linux X Window System Version 7.1.1 ** on running compiz --replace: (gtk-window-decorator:15178): Gtk-WARNING **: Unable to locate theme engine in module_path: clearlooks, libGL warning: 3D driver claims to not support visual 0x4b /usr/bin/compiz.real: Support for non power of two textures missing ^ This indicates that the driver probably doesn't support textures with dimensions that are not powers of two. This is required for compiz to work. I guess this could be reassigned to the S3 driver and have the severity reduced to wishlist perhaps. Anyone? Actually, it looks like compiz doesn't require this at all but that the AIGLX function DoGetDrawableAttributes() sets the texture target to GLX_TEXTURE_RECTANGLE_EXT regardless of whether the driver supports that. So I'm reassigning this bug to xserver-xorg-core. An upstream wishlist report against the Mesa savage driver might also be a good idea though as NPOT textures would be more resource efficient with compiz. -- Earthling Michel Dänzer | http://tungstengraphics.com Libre software enthusiast | Debian, X and DRI developer
Bug#390496: Compiz fails on supersavage on T23 Thinkpad
severity 390496 wishlist retitle 390496 Please support textures that are not powers of two reassign 390496 xserver-xorg-video-savage thanks On Sun, Oct 08, 2006 at 12:37:17PM +0200, Thierry Reding wrote: * DW Price wrote: Package: compiz Version: 0.0.13+git20060928-2 video: S3 Inc. SuperSavage IX/C SDR - T23 Thinkpad kernel: 2.6.18-1-686 #1 SMP Sun Sep 24 13:48:23 UTC 2006 i686 GNU/Linux X Window System Version 7.1.1 ** on running compiz --replace: (gtk-window-decorator:15178): Gtk-WARNING **: Unable to locate theme engine in module_path: clearlooks, libGL warning: 3D driver claims to not support visual 0x4b /usr/bin/compiz.real: Support for non power of two textures missing ^ This indicates that the driver probably doesn't support textures with dimensions that are not powers of two. This is required for compiz to work. I guess this could be reassigned to the S3 driver and have the severity reduced to wishlist perhaps. Anyone? Sounds good to me :-) - David Nusinow -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#390496: Compiz fails on supersavage on T23 Thinkpad
Processing commands for [EMAIL PROTECTED]: severity 390496 wishlist Bug#390496: Compiz fails on supersavage on T23 Thinkpad Severity set to `wishlist' from `normal' retitle 390496 Please support textures that are not powers of two Bug#390496: Compiz fails on supersavage on T23 Thinkpad Changed Bug title. reassign 390496 xserver-xorg-video-savage Bug#390496: Please support textures that are not powers of two Bug reassigned from package `compiz' to `xserver-xorg-video-savage'. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Feature Freeze
On Sat, Oct 07, 2006 at 10:19:02PM -0400, David Nusinow wrote: If you have concrete suggestions for how to handle these things in the future, and even right now, please post them in a reasonable manner. I won't reply to the thread for a little while (probably some days) to give myself the chance to calm down and figure out some ways for this to work well for everyone. I'd appreciate any help you guys could offer to make a workable solution for all of us. Ok... let me try this again without the psychotic power tripping... I'd like to really start doing a feature freeze on most of our packages. The whole of the archive is going in to freeze for etch in a few days anyway, so we need to keep new upstream versions out of unstable during that time so we can deliver bugfixes that are candidates for the etch release. I'd like to keep experimental as open as usual for more fun stuff. 7.2 is looking more sexy with XACE and Randr 1.2, so getting it moving will be fun. As Drew pointed out, we're missing some updates that do need to get done. I did a few updates last night of the input drivers, but there's a few missing still. When it was just me doing everything for 7.0, I could keep track in my head of what was going on. That's obviously not going to work now. As a possible solution, I created a wiki page based on the one Drew did as an attempt to help coordinate driver uploads [0]. It is located at http://wiki.debian.org/XStrikeForce/ReleaseStatus. The basic idea is documented at the top of the page. It's meant to be a reflection of consensus of where we're at with respect to freezing packages for release. We can also use this in between Debian releases in order to coordinate new upstream releases, ensuring that they migrate to testing before we start pushing new stuff in to unstable. The way I envision it working is that we discuss first, on-list, if it's time to start a freezing process. This should be pretty obvious to all of us, so I don't see it being a real problem. When anyone feels like a package is ready to be frozen, they just edit the page and include in the comment for the change why they want to freeze the package. If it's a problem, then we discuss it on-list and figure out a solution. We should also discuss on-list what sort of freeze it's going to be. For example, I feel that currently we're only fit to freeze on new features on our core packages (libs, server, drivers, main apps) but not for anything else. This should be documented at the head of the page. Coordinating all this should be easy if you just subscribe to the page. The current state of the page is simply the way I see it right now. If there's something that needs to be done, please change or add it. I didn't add things like apps because I'm lazy, so if you want to add them go for it [1]. This isn't meant to be a word of law sort of thing, just a way for us to coordinate and have a single place to look at. If you guys disagree with going after the feature freeze, please discuss it and let me know why. If you don't think the wiki page is a good move, let me know that it's crack and we'll just delete it and get on with our lives. If no one has any strong opinions, I'm going to assume we're all ok with this and go on from there. This isn't going to be the end of me trying to figure out a good way for this all to work, but I'm hoping it's a positive start. - David Nusinow [0] I thought this was a very good idea, but I had learned from the experience of doing 7.0 that it's way easier to just set a for loop to build all the drivers at once and then upload them. The idea should work better here, where we can't use simple things like for loops. [1] xterm needs an update, and compiz should ship with 0.2 for example... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#390929: compiz: Another window manager is already running on screen: 0
Hi Thierry, Then this could indicate that whatever window manager you're using does not support being replaced. If deleting kdesktoprc does help, this may be a KDE bug. Could be... Did you manage to reproduce it? Radu -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
