[Ubuntu-x-swat] [Bug 1069056] Re: Vdpau doesn't work.
[Expired for libvdpau (Ubuntu) because there has been no activity for 60 days.] ** Changed in: libvdpau (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libvdpau in Ubuntu. https://bugs.launchpad.net/bugs/1069056 Title: Vdpau doesn't work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvdpau/+bug/1069056/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1403418] Re: Graphic issues on the VLC media player with VDPAU
[Expired for libvdpau (Ubuntu) because there has been no activity for 60 days.] ** Changed in: libvdpau (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libvdpau in Ubuntu. https://bugs.launchpad.net/bugs/1403418 Title: Graphic issues on the VLC media player with VDPAU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvdpau/+bug/1403418/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1973093] [NEW] xmessage loses text area as buttons are added and -g
Public bug reported: xmessage text gets obscured with option combinations using buttons and geometry specifications. Quick background: xmessage creates a new grey window with a white text box inside it. Without -buttons, the white text box usually spans the full width of the grey window that contains it, leaving no margins. Things start going wrong when you start specifying -buttons or -g (geometry), and text can end up being obscured. Problem #1: If the width of all the buttons you specify makes the grey window wider than the text, the white text box does not increase in width to match. You end up with an undesirable wide grey margin on the right side of the white text box. If you resize the window, making it less wide, the grey margin does not narrow; it moves in and covers and obscures the text, even though there is plenty of room for the text. Suggested Fix #1: The white text box must always be created the same width as the window that contains it, with no useless grey margin to the right. Narrowing the width of the window should not cause text to be obscured by a wide and useless fixed grey margin. Reproduce: xmessage -buttons 1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20 "123456789" Problem #2: If you add a -g (geometry) option and specify just the width (not the height) for a window with buttons wider than the text box, the obscuring grey margin persists. If you add a "-g NNN" option, where NNN is the width that xmessage would have chosen itself, then you get exactly the same unpleasant behaviour as Problem #1 above. If you increase the NNN to be wider that what xmessage would have used, then both the window and the text box width are created increased by that amount, as if you had resized the window with a mouse. The useless grey margin to the right of the text box stays the same width, just as in Problem #1. If you decrease the NNN to be narrower that what xmessage would have used, then both the window and the text box width are created decreased by that amount, as if you had resized the window with a mouse. Not all buttons will show; this is expected. What is not expected is that the useless grey margin to the right of the text box stays the same width, and so it now overwrites and obscures the text, even though there is plenty of room for the text. If you resize the window back so that all the buttons show, all the text also shows and we're back to Problem #1 above. Suggested Fix #2: Same as above. Reproduce (width 541 is my xmessage chosen width for font "fixed"): xmessage -g 400 -buttons 1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20 "123456789" xmessage -g 541 -buttons 1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20 "123456789" xmessage -g 700 -buttons 1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20 "123456789" Problem #3: If you add a -g option and specify both the width *and* the height for a window with buttons wider than the text, things get much worse. If you add a "-g NNNx55" option, where NNN is the width that xmessage would have chosen itself and "55" is about the same height, you would expect to get exactly the same results as if you didn't specify any geometry at all. That's not what happens. You get a fixed-width text window about 12 characters wide, with a huge grey margin on the right. It doesn't matter what size text you specify; the white text box will be created about 12 characters wide and any text to the right of that will be masked and obscured by the wide grey margin. Changing the width of the window has all the problems of Problems #1 and #2 above. Suggested Fix #3: Same as above. Specifying a geometry that is identical to what xmessage would have chosen itself should create an identical window. Text should not be obscured. Reproduce (width 541 is my xmessage chosen width for font "fixed"): xmessage -g 541x55 -buttons 1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20 "123456789-123 YOU DON'T SEE THIS" ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: x11-utils 7.7+5build2 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed May 11 17:12:52 2022 DistUpgraded: 2022-04-04 16:21:26,723 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: v4l2loopback/0.12.5, 5.15.0-29-generic, x86_64: installed v4l2loopback/0.12.5, 5.15.0-30-generic, x86_64: installed GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Fujitsu Limited. 2nd Generation Core Processor Family Integrated Graphics Controller [10cf:15f5] InstallationDate: Installed on 2020-09-08 (610 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64
[Ubuntu-x-swat] [Bug 1946359] Re: [MIR] vulkan-tools
** Tags added: sec-979 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to vulkan in Ubuntu. https://bugs.launchpad.net/bugs/1946359 Title: [MIR] vulkan-tools To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vulkan/+bug/1946359/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1971042] Re: remap Fn+F3 to gnome-power-statistics instead of no-use OSD ( L322X 22.04 )
It works now. Can't remember if I reboot. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xwayland in Ubuntu. https://bugs.launchpad.net/bugs/1971042 Title: remap Fn+F3 to gnome-power-statistics instead of no-use OSD ( L322X 22.04 ) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xwayland/+bug/1971042/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1971479] Re: ADT failure to apply buildfix on Bionic (390.147-0ubuntu0.18.04.1)
Since we don't build i386 for lrm, I have released bionic as this issue isn't related to the kernel release. But when testing I did find that this issue can still be reproduced and leads to a build failure. I tested this with 4.15.0-176 in a i386 VM and could reproduce the failure to apply the buildfix which seems to lead to a build failure. ** Attachment added: "nvidia_file_2.txt" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1971479/+attachment/5588603/+files/nvidia_file_2.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1971479 Title: ADT failure to apply buildfix on Bionic (390.147-0ubuntu0.18.04.1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1971479/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1840473] Re: Don't draw | character on the screen while key is typed. :-)
** Bug watch added: Red Hat Bugzilla #2083314 https://bugzilla.redhat.com/show_bug.cgi?id=2083314 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1840473 Title: Don't draw | character on the screen while key is typed. :-) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1840473/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1840473]
| character is bent! duplicate of bug: https://bugzilla.redhat.com/show_bug.cgi?id=2083314 (bent numbers and capital letters) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1840473 Title: Don't draw | character on the screen while key is typed. :-) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1840473/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1840473]
Nope, what feels off about animated "|" character I think is that it needs to be hidden and only appear in animation form when user hasn't typed around 30 seconds or 15 seconds. :) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1840473 Title: Don't draw | character on the screen while key is typed. :-) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1840473/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1972977] Re: gnome-shell crashed with SIGSEGV in crocus_begin_query() from crocus_begin_query() from crocus_end_query() from crocus_end_query() from tc_call_end_query()
** Summary changed: - /usr/bin/gnome-shell:11:crocus_begin_query:crocus_begin_query:crocus_end_query:crocus_end_query:tc_call_end_query + gnome-shell crashed with SIGSEGV in crocus_begin_query() from crocus_begin_query() from crocus_end_query() from crocus_end_query() from tc_call_end_query() ** Package changed: gnome-shell (Ubuntu) => mesa (Ubuntu) ** Tags added: crocus -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1972977 Title: gnome-shell crashed with SIGSEGV in crocus_begin_query() from crocus_begin_query() from crocus_end_query() from crocus_end_query() from tc_call_end_query() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1972977/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1972977] [NEW] gnome-shell crashed with SIGSEGV in crocus_begin_query() from crocus_begin_query() from crocus_end_query() from crocus_end_query() from tc_call_end_query()
You have been subscribed to a public bug: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 42.0-2ubuntu1, the problem page at https://errors.ubuntu.com/problem/d8aa1211f7e8b219a4ee6dcae294ac16decd7fe3 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Tags: jammy -- gnome-shell crashed with SIGSEGV in crocus_begin_query() from crocus_begin_query() from crocus_end_query() from crocus_end_query() from tc_call_end_query() https://bugs.launchpad.net/bugs/1972977 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1971712] Re: Add support for Intel DG2
** Description changed: [Impact] Ubuntu 22.04 does not support Intel DG2-based hw which is released later this year. - [Fix] Mesa: needs a bunch of patches backported to 22.0.x, will be upstream in 22.1 or 22.2 kernel: use a dkms provided by Intel and integrated in the OEM kernel source, the module will be shipped in a separate modules package - [Test case] Boot a system with a DG2-based GPU, check that native graphics drivers - are used + are used. + Test mesa also on gen9-gen12 GPU's to verify that there are no + regressions even though the backports are for DG2. [What could go wrong] The Mesa patches are only for DG2 support, should not affect other hardware at all. The kernel driver is in a separate package which isn't installed by default except preinstall machines with this hardware. So other users are not affected. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1971712 Title: Add support for Intel DG2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.17/+bug/1971712/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
