The driver doesn't support transparency

[Ward Rogers]

Not much to add. Trying to get it to work with terminal and it's just fairly primitive with respect to options.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: xorg 1:7.7+23ubuntu3
ProcVersionSignature: Ubuntu 6.8.0-36.36-generic 6.8.4
Uname: Linux 6.8.0-36-generic x86_64
ApportVersion: 2.28.1-0ubuntu3
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Jun 30 14:56:05 2024
DistUpgraded: Fresh install
DistroCodename: noble
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] 4th Gen Core Processor Integrated Graphics Controller [1462:10e9]
InstallationDate: Installed on 2024-06-30 (0 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
MachineType: Micro-Star International Co., Ltd. CR70 2M/CX70 2OC/CX70 2OD
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=<set>
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-36-generic root=UUID=2f10bdc0-6f51-4fe2-af14-dfb69d05a40b ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/21/2014
dmi.bios.release: 4.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: E1758IMS.10G
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: MS-1758
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: REV:1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: CR70 2M/CX70 2OC/CX70 2OD
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE1758IMS.10G:bd02/21/2014:br4.6:svnMicro-StarInternationalCo.,Ltd.:pnCR702M/CX702OC/CX702OD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1758:rvrREV1.0:cvnCR702M/CX702OC/CX702OD:ct10:cvrN/A:skuTobefilledbyO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: CR70 2M/CX70 2OC/CX70 2OD
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: REV:1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.120-2build1
version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1build1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

[Daniel van Vugt (vanvugt)]

Terminal transparency is not directly a driver feature. It's implemented in the app and the compositor via OpenGL. And if OpenGL or the driver was broken in this area then a lot more than Terminal transparency would be broken...

If only the Terminal is affected then I think it would be bug 561370.

Also can you provide a screenshot?

[Ward Rogers (andrew-colley)]

I see.

It's hard to provide a screenshot to recreate the issue. I should have
been clearer. The problem is that one can't seem to have complete
control of transparency level. It's always tricky because you have to
contend with altered results (YMMV) depending on background, but that to
me seemed to be the bug.

Thanks for explaining the nuances of it. I wasn't aware I was reporting
a driver bug.

Andrew

On 1/07/2024 3:22 pm, Daniel van Vugt wrote:
> Terminal transparency is not directly a driver feature. It's implemented
> in the app and the compositor via OpenGL. And if OpenGL or the driver
> was broken in this area then a lot more than Terminal transparency would
> be broken...
>
> If only the Terminal is affected then I think it would be bug 561370.
>
> Also can you provide a screenshot?
>
>
> ** Package changed: xorg (Ubuntu) => ubuntu
>
> ** Changed in: ubuntu
> Status: New => Incomplete
>

[Daniel van Vugt (vanvugt)]

It sounds most like bug 561370 to me, but that appears to have gone quiet and become unreproducible to me for a few years. So maybe bug 561370 was already fixed...

There is a small chance this is driver related. Intel 4th gen chips will be forced to use an unusual driver due to architectural changes in Mesa in recent years.

I suggest the way forward is to wait for it to happen again and if it can't be captured in a screenshot or screencast then try to take a photo or video of it using a phone.

[Ward Rogers (andrew-colley)]

I think you are right. It will either be digested by the system and
fixed or it won't. It's not critical, I'm sure.

There is one thing I'm curious about that you may or may not be able to
help with. I'm getting some odd results when I try to update some
repositories. Connection refused on static IP at home but fine with
mobile hotspot. I don't suppose the supps use bitninja, do they?

On 1/07/2024 3:55 pm, Daniel van Vugt wrote:
> It sounds most like bug 561370 to me, but that appears to have gone
> quiet and become unreproducible to me for a few years. So maybe bug
> 561370 was already fixed...
>
> There is a small chance this is driver related. Intel 4th gen chips will
> be forced to use an unusual driver due to architectural changes in Mesa
> in recent years.
>
> I suggest the way forward is to wait for it to happen again and if it
> can't be captured in a screenshot or screencast then try to take a photo
> or video of it using a phone.
>

[Daniel van Vugt (vanvugt)]

I don't know anything about that connection issue but also this bug isn't the right place to discuss it.

If you can take a photo of the Terminal bug and attach it here then please do.

[Ward Rogers (andrew-colley)]

I apologise. I'll try to post it correctly next time.

On 1/07/2024 5:12 pm, Daniel van Vugt wrote:
> I don't know anything about that connection issue but also this bug
> isn't the right place to discuss it.
>
> If you can take a photo of the Terminal bug and attach it here then
> please do.
>