Your message dated Tue, 27 Jun 2006 22:56:54 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#370614: xbase-clients: upgrade X.org 7: us_intl keyboard
stopped to work
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt w
--- The message cannot be delivered to the following address. ---
[EMAIL PROTECTED]Permanent error involving remote host.
550 5.7.0 Access Denied
Reporting-MTA: blockade@licef.teluq.uquebec.ca
Final-Recipient: rfc822;gpaquett@licef.teluq.uquebec.ca
Action: failed
Status: 5.1.1
Diagnostic-Code
Julien Cristau writes ("Re: Bug#375667: x11-common and xserver-xorg
unupgradeable due to mutual deathgrip"):
> (c) using aptitude (or maybe apt-get) which can upgrade these packages
> without problems.
apt* just `cope' with this problem by running dpkg with --force
options. Ie, they decide that
Package: xserver-xorg
Version: 1:7.0.22
Severity: important
The top of my xorg.conf file contains the following information:
# If you have edited this file but would like it to be automatically updated
# again, run the following commands as root:
#
# cp /etc/X11/xorg.conf /etc/X11/xorg.conf.cus
On Tue, Jun 27, 2006 at 15:08:33 +0100, Ian Jackson wrote:
> Package: x11-common, xserver-xorg
> Version: 7.0.22, 7.0.22
>
[snip]
>
> It is not possible to upgrade these packages without either
> (a) deinstalling nearly the entire system or (b) using a --force
> option to dpkg to force violation
Package: x11-common, xserver-xorg
Version: 7.0.22, 7.0.22
anarres# dpkg -i pool/main/x/xorg/x11-common_7.0.22_i386.deb
dpkg: considering removing xserver-common in favour of x11-common ...
dpkg: no, cannot remove xserver-common (--auto-deconfigure will help):
xnest depends on xserver-common
xse
Package: x11-common
Version: 7.0.22
anarres# dpkg -i pool/main/x/xorg/xserver-xorg_7.0.22_all.deb
dpkg: regarding .../xserver-xorg_7.0.22_all.deb containing xserver-xorg,
pre-dependency problem:
xserver-xorg pre-depends on x11-common (>= 7.0.0-0ubuntu3)
x11-common is installed, but is version
On Tue, Jun 27, 2006 at 11:38:15AM +0200, Michel Dänzer wrote:
> On Mon, 2006-06-26 at 08:03 +0200, Marcel Sebek wrote:
> >
> > I upgraded kernel to 2.6.17 and xserver stopped working. I tried both
> > DRI enabled and disabled. I also tried disabling all modules and removing
> > all font director
On Tue, 2006-06-27 at 12:02 +0200, martin f krafft wrote:
>
> also sprach Michel Dänzer <[EMAIL PROTECTED]> [2006.06.27. +0200]:
> > Sounds like https://bugs.freedesktop.org/show_bug.cgi?id=2859 , i.e. the
> > accelerator stealing too much bandwidth from the display controller to
> > keep up t
On Mon, 2006-06-26 at 08:03 +0200, Marcel Sebek wrote:
>
> I upgraded kernel to 2.6.17 and xserver stopped working. I tried both
> DRI enabled and disabled. I also tried disabling all modules and removing
> all font directories, it didn't help.
>
> The Xserver receives SIGSEG:
>
> Backtrace:
>
Thanks for your response, Michel!
also sprach Michel Dänzer <[EMAIL PROTECTED]> [2006.06.27. +0200]:
> Sounds like https://bugs.freedesktop.org/show_bug.cgi?id=2859 , i.e. the
> accelerator stealing too much bandwidth from the display controller to
> keep up the signal.
Except this is with th
Processing commands for [EMAIL PROTECTED]:
> merge 363120 374839
Bug#363120: xserver-xorg-video-ati: Suspend and Resume broken
Bug#374839: xserver-xorg-core: rapid scrolling or repainting scrambles xterm or
emacs display
Bug#364043: xserver-xorg: apm resume does not work since update to xorg 7
Bu
On Tue, 2006-06-27 at 00:45 +0200, martin f krafft wrote:
> also sprach martin f krafft <[EMAIL PROTECTED]> [2006.06.09.2013 +0200]:
> > It works, but every now and then, screen0's monitor will just blank
> > for a second, then come back up. It'll do that 3-7 times, then it'll
> > be fine for a whi
13 matches
Mail list logo
