Bug#1065666: Compiz 0.8.18 appears to be broken in testing

2024-03-08 Thread James Bielefeldt
Hi
This address is listed as a maintainer on the Compiz package search page.
0.8.18 black screens on boot after a recent update when building a iso with
livebuild. I have been building the xfce-Compiz iso for about 4 months
without issue. The xfce (testing amd64) iso is built without errors, but it
is unusable with the black screen. Rebuilding the source package does not
fix it. I cant seem to get any more info with the black screen,
ctrl+alt+F(any number) stays a black screen and booting into safe mode also
results in a black screen. Xfce images without compiz build and work fine.

Thanks
Jim


Bug#1065666: Compiz 0.8.18 appears to be broken in testing

2024-03-08 Thread James Bielefeldt
Not sure if this helps, but I keep package lists of each build. Here is 
a diff of 2/24 build (works) vs 3/24 (broken). 
https://spins.tuxfamily.org/package-list-diff.txt I dont know if any 
changes would break compiz, but at least its more info.


Jim

On 3/6/24 11:25, Steve Langasek wrote:

On Wed, Mar 06, 2024 at 06:19:48PM +0100, Colomban Wendling wrote:

Le 06/03/2024 à 17:31, Steve Langasek a écrit :

On Wed, Mar 06, 2024 at 03:46:41PM +0100, Colomban Wendling wrote:

Anyway, I'm CCing Steve (who did the unstable NMU) and Samuel in case they
have extra clues.

The only change in the NMU was to rename the libdecoration0 package to
libdecoration0t64 for the 64-bit time_t transition.  Unless this managed to
break the *contents* of that package (i.e. the library has gone missing),
this should not have had any effect on the behavior of compiz.

So the package has not been rebuilt with different flags or anything?

Not *deliberately* as part of this upload.  The only change to flags should
be on 32-bit architectures, excluding i386.  I have assumed you are not
trying to run compiz on one of these archs!

But the toolchain also evolves over time, so this could certainly be a
misbuild due to underlying changes.


Anyway, I hardly expect this to be an issue, I just wanted to eliminate the
only Compiz-side change that happened in the last months.






Bug#1065666: Compiz 0.8.18 appears to be broken in testing

2024-03-08 Thread Colomban Wendling

Le 06/03/2024 à 16:59, James Bielefeldt a écrit :
I am using testing. I create Debian spins that are rolling release based 
on testing.
it's the same package in standard testing and unstable to my knowledge. 


Unstable recently got 2:0.8.18-5.1 -- yet as Steve said, it should not 
affect anything.


they all have the same version number. The package is also seriously 
outdated. Compiz is at 9.14 but the package is 8 point something.


Well, yes and no.  Compiz is a complicated beast, and version 0.9 is a 
C++ rewrite by Ubuntu, that is now basically unmaintained.  Compiz 0.8, 
also known as "compiz reloaded", is the pre-Ubuntu rewrite and has been 
continued separately.


Effectively nowadays it's 2 different (yet similar) software, and 0.9 is 
mostly discontinued, and 0.8 is maintained albeit not seeing muhc 
activity lately.



I tried to build it from the Ubuntu sources, but they errored out and are
beyond me. My main thing is themeing and polishing the desktop. I do 
have a live build script if you want it. Just not sure how I'd get it to 
you.


I don't think I'd have the time to dive this deep, and it would help 
immensely if you could try and gather some more information as to why 
Compiz is having issues.


Logs from the kernel, X and the Xfce sessions are likely the most 
interesting bits where you might find more information to pinpoint the 
issue.


Failing that, one interesting thing you could possibly attempt is to see 
whether an image with the exact same set of packages work fine if you 
don't *run* Compiz.  Basically build the Compiz image, and simply adjust 
the configuration not to run it (but use e.g. xfwm4).
You could also try and play with the Compiz plugins and configuration to 
see if one in particular is at fault, or if it's the core itself.


Regards,
Colomban



Bug#1065666: Compiz 0.8.18 appears to be broken in testing

2024-03-08 Thread Colomban Wendling

Hello James,

Unfortunately I can't test this for the moment, but:

Le 06/03/2024 à 15:03, James Bielefeldt a écrit :
This address is listed as a maintainer on the Compiz package search 
page. 0.8.18 black screens on boot after a recent update when building a 
iso with livebuild. I have been building the xfce-Compiz iso for about 4 
months without issue. The xfce (testing amd64) iso is built without 
errors, but it is unusable with the black screen. Rebuilding the source 
package does not fix it.


Are you sure you're not using unstable?  FWIW, there's no recent changes 
to the Compiz packages in testing, last ones were from about a year ago.


However, there's a large transition currently happening in unstable, 
which affects Compiz as well.  Maybe it could have an unknown side 
effect you're seeing?


I cant seem to get any more info with the black 
screen, ctrl+alt+F(any number) stays a black screen and booting into 
safe mode also results in a black screen. Xfce images without compiz 
build and work fine.


Maybe you could try SSHing to the machine to gather more data?  Or 
possibly access the logs any other way?


It could possibly be fairly unrelated to Compiz itself, but rather 
something else in the graphic stack (OpenGL?  so maybe mesa, the kernel 
or something?) that affects Compiz more than others?


Anyway, I'm CCing Steve (who did the unstable NMU) and Samuel in case 
they have extra clues.


Note that you probably should report a bug, although it's understandably 
harder with scarce data to reference.


Regards,
Colomban



Bug#1065666: Compiz 0.8.18 appears to be broken in testing

2024-03-08 Thread Colomban Wendling

Le 06/03/2024 à 17:31, Steve Langasek a écrit :

On Wed, Mar 06, 2024 at 03:46:41PM +0100, Colomban Wendling wrote:

Anyway, I'm CCing Steve (who did the unstable NMU) and Samuel in case they
have extra clues.


The only change in the NMU was to rename the libdecoration0 package to
libdecoration0t64 for the 64-bit time_t transition.  Unless this managed to
break the *contents* of that package (i.e. the library has gone missing),
this should not have had any effect on the behavior of compiz.


So the package has not been rebuilt with different flags or anything?

Anyway, I hardly expect this to be an issue, I just wanted to eliminate 
the only Compiz-side change that happened in the last months.


Colomban



Bug#1065666: Compiz 0.8.18 appears to be broken in testing

2024-03-08 Thread Steve Langasek
On Wed, Mar 06, 2024 at 03:46:41PM +0100, Colomban Wendling wrote:
> Anyway, I'm CCing Steve (who did the unstable NMU) and Samuel in case they
> have extra clues.

The only change in the NMU was to rename the libdecoration0 package to
libdecoration0t64 for the 64-bit time_t transition.  Unless this managed to
break the *contents* of that package (i.e. the library has gone missing),
this should not have had any effect on the behavior of compiz.

> Note that you probably should report a bug, although it's understandably
> harder with scarce data to reference.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: PGP signature


Bug#1065666: Compiz 0.8.18 appears to be broken in testing

2024-03-08 Thread Steve Langasek
On Wed, Mar 06, 2024 at 06:19:48PM +0100, Colomban Wendling wrote:
> Le 06/03/2024 à 17:31, Steve Langasek a écrit :
> > On Wed, Mar 06, 2024 at 03:46:41PM +0100, Colomban Wendling wrote:
> > > Anyway, I'm CCing Steve (who did the unstable NMU) and Samuel in case they
> > > have extra clues.

> > The only change in the NMU was to rename the libdecoration0 package to
> > libdecoration0t64 for the 64-bit time_t transition.  Unless this managed to
> > break the *contents* of that package (i.e. the library has gone missing),
> > this should not have had any effect on the behavior of compiz.

> So the package has not been rebuilt with different flags or anything?

Not *deliberately* as part of this upload.  The only change to flags should
be on 32-bit architectures, excluding i386.  I have assumed you are not
trying to run compiz on one of these archs!

But the toolchain also evolves over time, so this could certainly be a
misbuild due to underlying changes.

> Anyway, I hardly expect this to be an issue, I just wanted to eliminate the
> only Compiz-side change that happened in the last months.


-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: PGP signature