Thanks, I can confirm that rolling back to xserver-xorg-core 2:1.19.6-1
fixes the problem for me for now.
On Sun, Aug 5, 2018 at 3:55 PM Sven Joachim wrote:
> Control: reassign -1 xserver-xorg-core
> Control: forcemerge 900550 -1
>
> On 2018-08-05 15:43 -0400, Eric Cooper wrote:
&
Package: xserver-xorg-video-nouveau
Version: 1:1.0.15-3
Severity: important
I did an "apt-get upgrade" today that installed new
xserver-xorg-{core,nouveau} packages. Now X does not start on my system.
The same segmentation fault occurs every time I run "startx".
-- Package-specific info:
Package: libdrm-nouveau2
Version: 2.4.92-1
Severity: important
This has been happening frequently, but not repeatably so far.
It seems to be triggered by something Chromium is doing when I have
lots of browser windows and tabs open.
I've included the portion of syslog when this occurs.
Once it
Package: xserver-xorg-video-nouveau
Version: 1:1.0.13-3
Severity: normal
If I create an "Android virtual device" with hardware graphics
acceleration (from the Android Studio "AVD Manager"), my desktop locks
up within a few seconds. The following messages appeared in the log
the last two times I
Package: xserver-xorg-video-nouveau
Version: 1:1.0.11-1+b1
Severity: normal
I get these error messages and then the graphics system is unresponsive:
[287179.390141] nouveau E[ PFIFO][:01:00.0] read fault at 0xe9
[PAGE_NOT_PRESENT] from PCE0/PCOPY0 on channel 0x001fdb2000 [DRM]
Package: libdrm-nouveau2
Version: 2.4.65-3
Severity: normal
My graphics system occasionally locks up, with error messages like the
following in the log:
[163467.868937] nouveau E[ PFIFO][:01:00.0] read fault at 0xe4f000
[PAGE_NOT_PRESENT] from PCE0/PCOPY0 on channel 0x001fdb2000 [DRM]
Package: xserver-xorg-video-nouveau
Version: 1:1.0.11-1+b1
Severity: normal
When I use chromium as my default browser, my system eventually
freezes, with the error messages listed below. I'm currently using
chromium 44.0.2403.157-1 from sid, but the version from testing causes
the same problem.
--- Please enter the report below this line. ---
With the updated radeon driver the cairo rendering error is fixed, and this
bug
disappeared. Thanks.
I'm using the nouveau driver and the problem is still here.
--
Eric Cooper e c c @ c m u . e d u
--
To UNSUBSCRIBE, email
On Wed, May 09, 2012 at 09:51:45PM -0400, Eric Cooper wrote:
This problem has not recurred since I power-cycled my computer.
And now that I've been using it for a day or so, the problem is
back. I guess it required some pattern of resource usage.
--
Eric Cooper e c c @ c m u . e d
This problem has not recurred since I power-cycled my computer.
--
Eric Cooper e c c @ c m u . e d u
--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org
Package: xserver-xorg-video-nouveau
Severity: normal
I'm now seeing the same behavior after switching to the proprietary nvidia
driver, so I don't think I can blame it on nouveau :-). Feel free to
close this.
--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of
Package: xserver-xorg-video-nouveau
Version: 1:0.0.15+git20100329+7858345-5
Severity: important
My X session starts up OK, but after an unpredictable amount of time
(minutes or hours), the left monitor (DVI-I-2) goes black and shows a
message saying:
Out of range signal.
Cannot display
Package: xutils-dev
Version: 1:7.1.ds-2
Severity: normal
$ cleanlinks
Removing empty directories ...
find: warning: you have specified the -depth option after a non-option argument
-type, but options are not positional (-depth affects tests specified before it
as well as those specified after
Package: xorg-x11
Severity: minor
After doing debuild clean, the debian directory still contains
various -dbg subdirectories that were not present when the source
package was first unpacked.
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (990,
Package: xnest
Version: 6.8.2.dfsg.1-6
Severity: grave
Justification: renders package unusable
I do:
$ Xnest :1
$ xterm -display :1
Then, in the xterm window within the Xnest window, when I try to use
control characters like ^U, only lowercase 'u' is received and echoed.
-- System
Package: xfonts-100dpi
Version: 4.3.0.dfsg.1-14
Severity: normal
When doing dpkg -P xfonts-100dpi (same for -75dpi), I got:
dpkg - warning: while removing xfonts-100dpi, directory
`/usr/X11R6/lib/X11/fonts/100dpi' not empty so not removed.
# ls 100dpi/
fonts.cache-1
-- System Information:
fonts cache...
HOME=/root fc-cache -f -v 1/var/log/fontconfig.log 21 || (printf
failed.\nSee /var/log/fontconfig.log for more information.\n; exit 1)
printf done.\n
fi
exit 0
Doing dpkg-reconfigure fontconfig recreates the fonts.cache-1 files
everywhere.
--
Eric Cooper
In both 4.0.3 and 4.1.0, the X server would spin using 100% of the CPU
on my IBM ThinkPad 600 (NM 2160). Turning on Option NoAccel stopped
this, but performance was unacceptable. None of the various xaaNo*
options I found in the archives seemed to help.
Finally, I found that using
In both 4.0.3 and 4.1.0, the X server would spin using 100% of the CPU
on my IBM ThinkPad 600 (NM 2160). Turning on Option NoAccel stopped
this, but performance was unacceptable. None of the various xaaNo*
options I found in the archives seemed to help.
Finally, I found that using
19 matches
Mail list logo
