[Expired for Ubuntu because there has been no activity for 60 days.]
** Changed in: ubuntu
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2071535
Title:
The driv
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.
>
--
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.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
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 stati
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 chang
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 seem
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.
