Package: xserver-xorg-video-all
Followup-For: Bug #873578
X-Debbugs-Cc: nils+debian-report...@dieweltistgarnichtso.net
Dear Maintainer,
Itai Shaked wrote:
> I think it is safe to assume that in 2017, the vast majority of Debian
> users will have hardware meeting this criteria, so having
> `x
Your message dated Mon, 14 Oct 2013 19:03:28 +
with message-id
and subject line Bug#714379: fixed in weston 1.3.0-1
has caused the Debian Bug report #714379,
regarding weston: README.Debian gives bad suggestion to make weston suid root
to be marked as done.
This means that you claim that the
Hi,
I was installing a Debian system from scratch and there is something at
libgl1-mesa-dri package that may not be following the "xorg-driver-video-.."
packages.
When installing xserver-xorg package the xserver-xorg-video is obviously
required. And xserver-xorg-video gives us the option to
Package: weston
Version: 1.1.1-1
The README.Debian file needs to be updated, running weston as root or
making it suid is no longer necessary. Running weston from the local
console is possible via weston-launch if weston-launch is suid root and
the user
- is a member of the weston-launch group, o
Package: x11-xserver-utils
Version: 7.7~3
Severity: wishlist
some days ago, a program called "x-on-resize" was published[1], which
complements xrandr with a listening mode: x-on-resize keeps running and
prints text or executes other scripts as soon as the X configuration
changes.
as it is a usefu
in my case X freezes and i'm not dropped to the login manager. i have antiX
sid with slim login manager all up to date.
i have read this on phoronix some time ago
http://www.phoronix.com/scan.php?page=news_item&px=MTAyMTA
it talks about the 965g driver being dropped from the mainline mesa. maybe
th
Package: xserver-xorg-video-radeon
Version: 1:6.14.2-1
Severity: wishlist
On a note related to #576229, it would be nice to clarify the suggestion
of firmware on two points:
1. The current suggestion is on firmware-linux, which is a metapackage
depending on firmware-linux-free and firmware
Alex Deucher writes:
> There were some pll regressions in 2.6.37. Try 2.6.38-rc4 or newer.
> For reference:
> https://bugzilla.kernel.org/show_bug.cgi?id=26552
Actually, all this was on 2.6.32-5. I didn't keep 2.6.37
around. I'll try .38 too.
--
To UNSUBSCRIBE, email to debian-x-requ...@lis
On Fri, Feb 11, 2011 at 5:06 PM, Gábor Melis wrote:
> GSR writes:
>
>> Hi,
>> daen...@debian.org (2011-02-11 at 1035.03 +0100):
>>> On Fre, 2011-02-11 at 05:54 +0100, GSR wrote:
>>> > Could you check MigrationHeuristic setting? And try with "greedy"?
>>> This option doesn't have any effect with c
GSR writes:
> Hi,
> daen...@debian.org (2011-02-11 at 1035.03 +0100):
>> On Fre, 2011-02-11 at 05:54 +0100, GSR wrote:
>> > Could you check MigrationHeuristic setting? And try with "greedy"?
>> This option doesn't have any effect with current upstream xserver and
>> KMS, and even with older xser
Hi,
daen...@debian.org (2011-02-11 at 1035.03 +0100):
> On Fre, 2011-02-11 at 05:54 +0100, GSR wrote:
> > Could you check MigrationHeuristic setting? And try with "greedy"?
> This option doesn't have any effect with current upstream xserver and
> KMS, and even with older xservers where it accident
On Fre, 2011-02-11 at 05:54 +0100, GSR wrote:
>
> Could you check MigrationHeuristic setting? And try with "greedy"?
This option doesn't have any effect with current upstream xserver and
KMS, and even with older xservers where it accidentally had an effect,
it's probably better to use the radeon
Hi:
Could you check MigrationHeuristic setting? And try with "greedy"?
---8<---
Section "Device"
...
Driver "radeon"
...
# Option "MigrationHeuristic" "smart" # Near as slow as with
default/always http://nouveau.freedesktop.org/wiki/EXA
Opt
On Tue, Apr 13, 2010 at 5:51 PM, Andres Cimmarusti
wrote:
> I have a similar card (also the xpress 200m), I will try to reproduce this
> bug. However, Rodrigo's Xorg0.log shows all these warnings and errors.
>
> (WW) RADEON(0): Direct rendering disabled
>
> (II) RADEON(0): XAA Render acceleration
On Tue, 13 Apr 2010 12:01:55 -0400, Andres wrote in message
:
> Could you try renaming your xorg.conf and use the default settings to
> see if the same happens?
..tested, I'll stick with my good old xorg.conf
with my nice 2048x1536...@59.4hz modeline. ;o)
> Also, there is a new version in sid
Could you try renaming your xorg.conf and use the default settings to see if
the same happens?
Also, there is a new version in sid of the radeon driver. Try it!, along
with sid's 2.6.32-11 kernel.
If it's no longer an issue, can I close this bug?
Andres
I have a similar card (also the xpress 200m), I will try to reproduce
this bug. However, Rodrigo's Xorg0.log shows all these warnings and
errors.
(WW) RADEON(0): Direct rendering disabled
(II) RADEON(0): XAA Render acceleration unsupported on Radeon
9500/9700 and newer. Please use EXA instead.
(II
I'm not very knowledgeable, but I've had my share of problems with ATI
Xpress 200m rc410. My card is actually detected as: ATI Radeon xpress 200m
PCIE 5955 by lspci
In my case a fresh installed of Squeeze a few months back had none of the
problems you're having, but I did get this error in xorg0.l
Hello, thanks for the information.
In a similar way as reported by Harris
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=546588#30
my own situation improved a lot with linux-image-2.6.32-trunk-686
and firmware-linux.
Ric
--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a s
Hi,
daen...@debian.org (2010-03-28 at 1513.22 +0200):
> On Sun, 2010-03-28 at 05:30 +0200, GSR wrote:
> > I was reading the list of radeon reports and found yours. Time ago I
> > experienced a problem with similar symptoms, that got fixed by adding
> > Option "MigrationHeuristic" "greedy" (that go
On Sun, 2010-03-28 at 05:30 +0200, GSR wrote:
>
> I was reading the list of radeon reports and found yours. Time ago I
> experienced a problem with similar symptoms, that got fixed by adding
> Option "MigrationHeuristic" "greedy" (that go back to XAA, as other
> person suggested).
What do you me
Hi:
I was reading the list of radeon reports and found yours. Time ago I
experienced a problem with similar symptoms, that got fixed by adding
Option "MigrationHeuristic" "greedy" (that go back to XAA, as other
person suggested). Maybe your case is the same.
I got the idea to test that option fro
Hi,
X11 7.5 Amd64 experimental has been broken for weeks with a lot of
packages missing including
xserver-xorg-core, xserver-video-intel, ...
Current status breaks mouse and keyboard quite badly as you have to find
the right /dev/input/eventX devices to get keyboard and mouse again.
I can o
<>
D G wrote:
> By the way: a bug for 2:2.0.0-2: when you wander onto an inactive window, the
> mouse pointer disappears.
>
Please do not mix reports since it messes up the contents of the
original bug, while this new bug will end up being forgotten. If this
problem still happens with latest 2:2.
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 sur
D G wrote:
>> 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 reall
>
> 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
On Fri, Jul 23, 2004, Hile Tuohela wrote:
> The files are available with a html README from
> http://hile.dyndns.org/xkb-thinkpad.tgz
This page does no more exist. Please next time attach the file.
I am closing the bug, since there is no more input. Feel free to reopen
the bug if you reproduce i
after lunch one thinks better
the line
DI_KEYMAP="${DI_KEYMAP##-latin1}"
is ment to remove the -latin1 parts
but ## deletes from the left.
if one replaces with
DI_KEYMAP="${DI_KEYMAP%%-latin1}"
it works as expected.
Ronny Aasen
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject o
On Thu, Aug 31, 2006 at 12:15:05PM +0200, Fathi Boudra wrote:
> hi,
>
> sorry to send you directly this mail but as i didn't received any reply about:
> http://lists.debian.org/debian-x/2006/08/msg00080.html
>
> any comments ?
Not really... if you want to send a patch for the issue we can apply
hi,
> At line 11 of /usr/share/doc/xserver-xorg-input-synaptics/README.Debian
> I have:
>
>If you want to be able to change driver parameters without restarting
>the X server, enable the "SHMConfig" option in the X configuration
>file. You can then use the "synclient" program to query
Package: xlibs
Version: 6.9.0.dfsg.1-6
Severity: wishlist
Tags: patch
Hi,
I personally really like to use my Capslock as Super to manage all kinds
of window manager stuff and program starting shortcuts, as well as
deskbar-applet and tomboy global binding. I also perfer non-dead-keys
and chose the
David Nusinow wrote:
> On Mon, Jul 04, 2005 at 02:50:31PM -0400, Nathanael Nerode wrote:
>> This is just a suggestion.
>>
>> I think these two items, scheduled for 6.8.2-2, really ought to be done
>> before the first upload to unstable, just to avoid potential serio
On Mon, Jul 04, 2005 at 02:50:31PM -0400, Nathanael Nerode wrote:
> This is just a suggestion.
>
> I think these two items, scheduled for 6.8.2-2, really ought to be done
> before the first upload to unstable, just to avoid potential serious breakage.
> The rest of the items lo
This is just a suggestion.
I think these two items, scheduled for 6.8.2-2, really ought to be done
before the first upload to unstable, just to avoid potential serious breakage.
The rest of the items look like they're reasonable to postpone.
--- TODO2005-07-04 14:42:29.617091629
Package: xlibs
Version: 4.3.0.dfsg.1-6
Severity: wishlist
Tags: patch
I have written a small set of xkb rules to enable the extra keys
on thinkpad laptops (keysyms 233 and 234). The rules implement
new keyboard model 'thinkpad'.
The files are available with a html README from
http://hile.dyndns
Michel Dänzer <[EMAIL PROTECTED]> writes:
> So, has anyone tried my suggested fix? That would be more useful than
> pointing others to this bug...
I had planned to do so this week, actually. I just need to clear space
to build it on my laptop.
--
ilmari
So, has anyone tried my suggested fix? That would be more useful than
pointing others to this bug...
--
Earthling Michel Dänzer | Debian (powerpc), X and DRI developer
Libre software enthusiast| http://svcs.affero.net/rm.php?r=daenzer
uot;John R. Daily" <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: xserver-xfree86: Suggestion for smarter recognition of non-debconf
XF86Config configs
X-Mailer: reportbug 2.29
Date: Tue, 07 Oct 2003 11:56:25 -0500
Delivered-To: [EMAIL PROTECTED]
X-
Package: xserver-xfree86
Version: 4.2.1-11
Severity: wishlist
When deciding whether the user has made changes outside the DEBCONF
block in the old-style XF86Config file, it should be possible to
identify un-commented, non-whitespace lines outside that block.
-- System Information:
Debian Release:
Package: xserver-xfree86
Version: 4.2.1-11
Severity: wishlist
When deciding whether the user has made changes outside the DEBCONF
block in the old-style XF86Config file, it should be possible to
identify un-commented, non-whitespace lines outside that block.
-- System Information:
Debian Release:
>> Arthur Peters <[EMAIL PROTECTED]> writes:
> I don't think it would be too hard to build such a package from the X
> sources. Almost every thing you would need is in the directory [X
> source]/programs/Xserver/hw/xfree86/os-support/linux/drm/kernel you
> just need to package the Imake genera
>> Arthur Peters <[EMAIL PROTECTED]> writes:
> I don't think it would be too hard to build such a package from the X
> sources. Almost every thing you would need is in the directory [X
> source]/programs/Xserver/hw/xfree86/os-support/linux/drm/kernel you
> just need to package the Imake gener
On Mon, Oct 09, 2000 at 09:11:38PM +0200, Marcelo E. Magallon wrote:
> For indirect rendering, the application talks to the X server via the
> GLX protocol (there's no library talking to the hardware in this case).
> The server decodes the GLX requests and renders them appropriately
> (which me
On Mon, Oct 09, 2000 at 12:01:14PM -0600, Joshua Shagam wrote:
> > I'm still apprehensive about moving *_dri.so out of /usr/X11R6/lib/modules.
> > If they aren't really X server modules, then they don't belong in that
> > directory (maybe /usr/lib/xlibmesa3 ?). Should I ask upstream?
>
> Ur, alth
On Mon, Oct 09, 2000 at 09:11:38PM +0200, Marcelo E. Magallon wrote:
> For indirect rendering, the application talks to the X server via the
> GLX protocol (there's no library talking to the hardware in this case).
> The server decodes the GLX requests and renders them appropriately
> (which m
On Mon, Oct 09, 2000 at 12:01:14PM -0600, Joshua Shagam wrote:
> > I'm still apprehensive about moving *_dri.so out of /usr/X11R6/lib/modules.
> > If they aren't really X server modules, then they don't belong in that
> > directory (maybe /usr/lib/xlibmesa3 ?). Should I ask upstream?
>
> Ur, alt
>> Branden Robinson <[EMAIL PROTECTED]> writes:
> I'm still apprehensive about moving *_dri.so out of
> /usr/X11R6/lib/modules. If they aren't really X server modules, then
> they don't belong in that directory (maybe /usr/lib/xlibmesa3 ?).
> Should I ask upstream?
I don't understand in wha
On Mon, Oct 09, 2000 at 11:20:37AM -0500, Branden Robinson wrote:
> On Mon, Oct 09, 2000 at 09:17:05AM -0600, Joshua Shagam wrote:
> > It's not the compiled code which has to match between DRI and DRM,
> > just the interface. I'm using a DRM module compiled along with my
> > 2.4.0-test8 kernel jus
From: Sven Heyll <[EMAIL PROTECTED]>
Subject: Suggestion
Date: 09 Oct 2000 11:16:40 -0100
> Hi,
>
> why not splitting the xfree86-server package, so that the drm/dri stuff
> is in an extra package and can be compiled before installing. Dri
> modules have to be
> compile
> On Mon, Oct 09, 2000 at 09:17:05AM -0600, Joshua Shagam wrote:
> > It's not the compiled code which has to match between DRI and DRM,
> > just the interface. I'm using a DRM module compiled along with my
> > 2.4.0-test8 kernel just fine with the precompiled mga.so and mga_dri.so
> > which came i
>> Branden Robinson <[EMAIL PROTECTED]> writes:
> I'm still apprehensive about moving *_dri.so out of
> /usr/X11R6/lib/modules. If they aren't really X server modules, then
> they don't belong in that directory (maybe /usr/lib/xlibmesa3 ?).
> Should I ask upstream?
I don't understand in wh
On Mon, Oct 09, 2000 at 09:17:05AM -0600, Joshua Shagam wrote:
> It's not the compiled code which has to match between DRI and DRM,
> just the interface. I'm using a DRM module compiled along with my
> 2.4.0-test8 kernel just fine with the precompiled mga.so and mga_dri.so
> which came in the X pa
On Mon, Oct 09, 2000 at 11:20:37AM -0500, Branden Robinson wrote:
> On Mon, Oct 09, 2000 at 09:17:05AM -0600, Joshua Shagam wrote:
> > It's not the compiled code which has to match between DRI and DRM,
> > just the interface. I'm using a DRM module compiled along with my
> > 2.4.0-test8 kernel ju
From: Sven Heyll <[EMAIL PROTECTED]>
Subject: Suggestion
Date: 09 Oct 2000 11:16:40 -0100
> Hi,
>
> why not splitting the xfree86-server package, so that the drm/dri stuff
> is in an extra package and can be compiled before installing. Dri
> modules have to be
> On Mon, Oct 09, 2000 at 09:17:05AM -0600, Joshua Shagam wrote:
> > It's not the compiled code which has to match between DRI and DRM,
> > just the interface. I'm using a DRM module compiled along with my
> > 2.4.0-test8 kernel just fine with the precompiled mga.so and mga_dri.so
> > which came
On Mon, Oct 09, 2000 at 11:16:40AM -0100, Sven Heyll wrote:
> Hi,
>
> why not splitting the xfree86-server package, so that the drm/dri stuff
> is in an extra package and can be compiled before installing. Dri
> modules have to be
> compiled with the corresponding drm version, which is provided
On Mon, Oct 09, 2000 at 09:17:05AM -0600, Joshua Shagam wrote:
> It's not the compiled code which has to match between DRI and DRM,
> just the interface. I'm using a DRM module compiled along with my
> 2.4.0-test8 kernel just fine with the precompiled mga.so and mga_dri.so
> which came in the X p
On Mon, Oct 09, 2000 at 11:16:40AM -0100, Sven Heyll wrote:
> Hi,
>
> why not splitting the xfree86-server package, so that the drm/dri stuff
> is in an extra package and can be compiled before installing. Dri
> modules have to be
> compiled with the corresponding drm version, which is provided
ins debian specific config file
templates ("xc/config/.../host.def" ... etc) and
perl script may askyou quesations like "Do you have a < ...> card
?" "Should <...> be activated ?" etc
very simple and basic.
Just a suggestion,
regards Sven Heyll
ins debian specific config file
templates ("xc/config/.../host.def" ... etc) and
perl script may askyou quesations like "Do you have a < ...> card
?" "Should <...> be activated ?" etc
very simple and basic.
Just a suggestion,
regards Sven H
62 matches
Mail list logo
