** Tags removed: eoan
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1871262
Title:
gnome-shell crashes in meta_window_set_stack_position_no_sync:
assertion 'window->stack_position
** Tags removed: eoan
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1861542
Title:
gnome-shell crashed with SIGSEGV (when using touchscreen) in
meta_window_updates_are_frozen
** Tags removed: eoan
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1878776
Title:
gnome-shell crashed with SIGSEGV in g_type_check_instance() from
g_signal_connect_data()
** Tags removed: eoan
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1868293
Title:
gnome-shell crashed in meta_workspace_index: Workspace does not exist
to index!
Status in
Still having this problem in 2020 (18.04)
Spent the last 4-5 hours trying to fix it.
Just found this thread.
Not sure how relevant (new to Ubuntu/Linux since 2019), but I noticed this...
When running 'sudo lspci -v'
BEFORE SUSPEND/SLEEP
00:1f.3 Audio device: Intel Corporation 100 Series/C230
verified on a chroot, there were file conflicts until focal-proposed was
enabled, then 'apt -f install' fixed the state.
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal
--
You received this bug notification because you are
The attachment "usb-libusb.c.patch" seems to be a patch. If it isn't,
please remove the "patch" flag from the attachment, remove the "patch"
tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the
team.
[This is an automated message performed by a Launchpad user owned by
reply #30,
Agree, I think we should add GUI option for user to set it.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1890772
Title:
Some external 4K monitor is not working properly
We have prepared a patch for the package in Ubuntu 18.04 (CUPS 2.2.7).
We would like to request to include a solution like this for at least
Ubuntu 18.04.
We also made a pull request in the official CUPS repository:
https://github.com/apple/cups/issues/5817
I guess Windows is good at compatibility and defaulting to 8bpc is safe.
But unless we have a GUI that allows users to then select 10bpc,
defaulting to 8bpc is not something we should do.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Yeah the world is full of subtle connection problems. In this particular
case, dropping back to 8bps would fix it. But I'm not sure how we would
detect that, or if it's even the right thing to do in most cases.
--
You received this bug notification because you are a member of Desktop
Packages,
Yeah the world is full of subtle connection problems. In this particular
case, dropping back to 8bpc would fix it. But I'm not sure how we would
detect that automatically, or if it's even the right thing to do in most
cases.
--
You received this bug notification because you are a member of
Regaring comment #26, I am using PX UH-1.2MX HDMI 2.0 certified Premium
High Speed cable so the cable's quality should not be a problem.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
My monitor is EDID 1.3 and it has the same problem.
edid-decode (hex):
00 ff ff ff ff ff ff 00 41 0c 8f c1 bd 07 00 00
08 1d 01 03 80 3c 22 78 2a 67 a1 a5 55 4d a2 27
0e 50 54 bf ef 00 d1 c0 b3 00 95 00 81 80 81 40
81 c0 01 01 01 01 4d d0 00 a0 f0 70 3e 80 30 20
35 00 55 50 21 00 00 1a a3 66
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1890772
Title:
Some external 4K monitor is
If so that kind of feedback isn't constructive, and this bug report
isn't the right place for it.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1886414
Title:
the chromium
I reckon he means get rid of snap caused it turned a trivial task into a
difficult one.
On Fri, 7 Aug 2020, 08:10 Olivier Tilloy, <1886...@bugs.launchpad.net>
wrote:
> Sorry, I'm not sure what you mean with that last comment. Can you please
> elaborate?
>
> --
> You received this bug
Thanks that does seem to be an old EDID v1.3 with no defined bit depth.
But there are some vendor-specific blocks there that do advertise
support for 10bpc and 12bpc.
In this case I think it's correct to try and default to 10bpc or 12bpc.
It's probably only the cable or dongle letting it down. I
I found that `find /sys | grep edid$ | xargs file -i` will always report
the file is empty.
Please use `find /sys | grep edid$ | xargs cat` to find out which one is
non-empty and attach the EDID here.
--
You received this bug notification because you are a member of Desktop
Packages, which is
Upload the problem edid.
** Attachment added: "edid of the display with problem"
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1890772/+attachment/5399493/+files/edid-problem
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
I forgot a display signal doesn't include any alpha channel, so yeah 8
bpc will require less bandwidth than 10 bpc.
The maximum capability of the monitor should be advertised in its EDID.
At least modern monitors do. You can check it using the 'edid-decode'
command and grepping for 'bits per
101 - 121 of 121 matches
Mail list logo
