I filed an upstream bug report,
including more workarounds and possibly a link to the commit that caused
the regression.
https://github.com/mate-desktop/marco/issues/548
I'm seeing a similar problem here with older nvidia cards.
Could you try this?
1. Login with metacity
2. Open a terminal
3. Run: marco --no-composite --replace
For me, both metacity and `marco --no-composite` works fine.
While the default `marco --composite`,
* Crashes Xorg on TNT2
* Doesn't
Package: marco
Followup-For: Bug #885947
Version: 1.22.2-1
Dear Maintainer.
> This might really be a X driver specific issue.
Perhaps, but as I said in message #30 "The PC woks fine in Debian 9, and
too in Debian 10 testing with mate 1.18.1-3, just until I update to the
following versions."
On Sa 10 Aug 2019 15:32:19 CEST, Y G2709 wrote:
Package: marco
Followup-For: Bug #885947
Version: 1.22.2-1
Dear Maintainer, after updating marco to the latest version 1.22.2-1 and
returning the default Window Manager from metacity to marco and restart,
follow the same problem.
Even on a
Package: marco
Followup-For: Bug #885947
Version: 1.22.2-1
Dear Maintainer, after updating marco to the latest version 1.22.2-1 and
returning the default Window Manager from metacity to marco and restart,
follow the same problem.
Even on a clean disk, after installing a fresh DVD image from
Package: marco
Followup-For: Bug #885947
Version: 1.20.3-1
(I send this out of reporbug because I can not use it because due to
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905737)
Dear Maintainer, on the regular disk, after updating marco to the
latest version 1.20.3-1 and returning the
Package: marco
Followup-For: Bug #885947
(I send this out of reporbug because I can not use it due to
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905737)
Dear Maintainer, after updating marco to 1.20.2-1 and replacing marco
with metacity (installed version 1:3.28.0-1) and changing back to
Hi,
On Mo 23 Jul 2018 20:25:14 CEST, Santiago wrote:
Package: marco
Version: 1.18.1-3
Followup-For: Bug #885947
Dear Maintainer, if I upgrade the following retained packages to the
latest version, follow the same problem.
marco (1.18.1-3 => 1.20.2-1)
marco-common (1.18.1-3 =>
Package: marco
Version: 1.18.1-3
Followup-For: Bug #885947
Thanks for answering and for the questions.
> Also, I assume, you are on Debian buster, correct?
lsb_release -ds
Debian GNU/Linux testing (buster)
cat /etc/debian_version
buster/sid
> And what are the versions of the underlying
Hi,
On Mi 02 Mai 2018 10:34:08 CEST, Santiago wrote:
Package: marco
Version: 1.18.1-3
Followup-For: Bug #885947
Dear Maintainer, if I upgrade the following retained packages to the
latest version, follow the same problem.
marco (1.18.1-3 => 1.20.1-2)
marco-common (1.18.1-3 => 1.20.1-2)
Package: marco
Version: 1.18.1-3
Followup-For: Bug #885947
Dear Maintainer, if I upgrade the following retained packages to the latest
version, follow the same problem.
marco (1.18.1-3 => 1.20.1-2)
marco-common (1.18.1-3 => 1.20.1-2)
libmarco-private1 (1.18.1-3 => 1.20.1-2)
Regards.
--
Package: marco
Version: 1.18.1-3
Followup-For: Bug #885947
Dear Maintainer, if I upgrade the following retained packages to the latest
version, follow the same problem.
marco (1.18.1-3 => 1.20.1-1)
marco-common (1.18.1-3 => 1.20.1-1)
libmarco-private1 (1.18.1-3 => 1.20.1-1)
Regards.
--
Package: marco
Followup-For: Bug #885947
Dear Maintainer, if I upgrade the following retained packages to the latest
version, follow the same problem.
marco (1.18.1-3 => 1.20.0-2)
marco-common (1.18.1-3 => 1.20.0-2)
libmarco-private1 (1.18.1-3 => 1.20.0-2)
Regards.
-- System Information:
13 matches
Mail list logo
