[Bug 1964554] Re: Brasero does not burn ISO IMAGE. Error message; "SCSI error on write(0,16): See MMC specs: Sense Key 5 "Illegal request"
Hi, C. Clear wrote: > What does doing a power off/on cycle entail ??? Just a shutdown so that the burner drive has no electrical power. If in doubt whether the power is really off, press the drive's eject button. The drive should not react. Have a nice day :) Thomas -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to brasero in Ubuntu. https://bugs.launchpad.net/bugs/1964554 Title: Brasero does not burn ISO IMAGE. Error message; "SCSI error on write(0,16): See MMC specs: Sense Key 5 "Illegal request" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/1964554/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1964682] Re: IBus not starting properly at login with gnome-shell 42
A no-change rebuild of ibus doesn't help. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1964682 Title: IBus not starting properly at login with gnome-shell 42 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964682/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1964554] Re: Brasero does not burn ISO IMAGE. Error message; "SCSI error on write(0,16): See MMC specs: Sense Key 5 "Illegal request"
Thanks for getting back to me. So a question to ask *Brasero's bad read attempt spoiled the two ASUS drives until they got a power-off-on cycle. If the drive is built into the computer this means a power-off-on cycle of the computer, i fear* What does doing a power off/on cycle entail ??? Disconnecting the Drive and computer from power and replugging it in or something more complex ?? On Sat, Mar 12, 2022 at 5:30 PM Thomas Schmitt <1964...@bugs.launchpad.net> wrote: > Hi, > > C. Clear wrote: > > Drive type : vendor 'ASUS' product 'BW-16D1HT' revision '3.10' > > That would match the Debian bug of last year. > > > > Did try Nero for Linux and had the same > > result as I did with Brasero. > > Keep in mind that in the Debian bug scenario Brasero's bad read attempt > spoiled the two ASUS drives until they got a power-off-on cycle. If the > drive is built into the computer this means a power-off-on cycle of the > computer, i fear. (I have mine in a USB box. That eases the problem.) > > It was enough to show Brasero a CD burnt with wite type TAO to let the > drive go mad. It was not necessary to make a burn attempt. > The only workaround was to blank CD-RW by other programs before giving > them to Brasero for being re-written. > > Unfortunately TAO is the write type used by Brasero itself. Other programs > may choose SAO with the consequence that those CDs don't let the drive go > mad, even when they get shown to Brasero. > > > Have a nice day :) > > Thomas > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1964554 > > Title: > Brasero does not burn ISO IMAGE. Error message; "SCSI error on > write(0,16): See MMC specs: Sense Key 5 "Illegal request" > > Status in brasero package in Ubuntu: > New > > Bug description: > > BraseroLibburn SCSI error condition on command 2Ah WRITE(10): See MMC > specs: Sense Key 5 "Illegal request", ASC 21 ASCQ 04. > BraseroLibburn called brasero_job_set_current_action > BraseroLibburn Libburn reported an error SCSI error on write(0,16): See > MMC specs: Sense Key 5 "Illegal request", ASC 21 ASCQ 04. > BraseroLibburn called brasero_job_error > BraseroLibburn finished with an error > BraseroLibburn asked to stop because of an error > error = 1 > message = "SCSI error on write(0,16): See MMC specs: Sense Key 5 > "Illegal request", ASC 21 ASCQ 04." > BraseroLibburn stopping > Session error : SCSI error on write(0,16): See MMC specs: Sense Key 5 > "Illegal request", ASC 21 ASCQ 04. (brasero_burn_record brasero-burn.c:2856) > --- > ProblemType: Bug > ApportVersion: 2.20.9-0ubuntu7.27 > Architecture: amd64 > CurrentDesktop: ubuntu:GNOME > DistroRelease: Ubuntu 18.04 > InstallationDate: Installed on 2021-01-31 (403 days ago) > InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 > (20190805) > Package: brasero 3.12.1-4ubuntu2 > PackageArchitecture: amd64 > ProcEnviron: >TERM=xterm-256color >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > ProcVersionSignature: Ubuntu 5.4.0-100.113~18.04.1-generic 5.4.166 > Tags: bionic > Uname: Linux 5.4.0-100-generic x86_64 > UpgradeStatus: No upgrade log present (probably fresh install) > UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo > _MarkForUpload: True > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/1964554/+subscriptions > > -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to brasero in Ubuntu. https://bugs.launchpad.net/bugs/1964554 Title: Brasero does not burn ISO IMAGE. Error message; "SCSI error on write(0,16): See MMC specs: Sense Key 5 "Illegal request" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/1964554/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1964675] Re: Window dragging lag when rendering 3d objects. (GNOME 42, NVIDIA, glxgear, pymol)
Many error messages: [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0400] Failed to grab modeset ownership -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1964675 Title: Window dragging lag when rendering 3d objects. (GNOME 42, NVIDIA, glxgear, pymol) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964675/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1964554] Re: Brasero does not burn ISO IMAGE. Error message; "SCSI error on write(0,16): See MMC specs: Sense Key 5 "Illegal request"
Hi, C. Clear wrote: > Drive type : vendor 'ASUS' product 'BW-16D1HT' revision '3.10' That would match the Debian bug of last year. > Did try Nero for Linux and had the same > result as I did with Brasero. Keep in mind that in the Debian bug scenario Brasero's bad read attempt spoiled the two ASUS drives until they got a power-off-on cycle. If the drive is built into the computer this means a power-off-on cycle of the computer, i fear. (I have mine in a USB box. That eases the problem.) It was enough to show Brasero a CD burnt with wite type TAO to let the drive go mad. It was not necessary to make a burn attempt. The only workaround was to blank CD-RW by other programs before giving them to Brasero for being re-written. Unfortunately TAO is the write type used by Brasero itself. Other programs may choose SAO with the consequence that those CDs don't let the drive go mad, even when they get shown to Brasero. Have a nice day :) Thomas -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to brasero in Ubuntu. https://bugs.launchpad.net/bugs/1964554 Title: Brasero does not burn ISO IMAGE. Error message; "SCSI error on write(0,16): See MMC specs: Sense Key 5 "Illegal request" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/1964554/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 184547]
I am facing this issue only in google chrome. https://pickyourprop.com/search-properties/ -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to epiphany-browser in Ubuntu. https://bugs.launchpad.net/bugs/184547 Title: epiphany-gecko crashed with SIGSEGV while resizing fonts with Ctrl+MouseWheel To manage notifications about this bug go to: https://bugs.launchpad.net/epiphany-browser/+bug/184547/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1964675] Re: Window dragging lag when rendering 3d objects. (GNOME 42, NVIDIA, glxgear, pymol)
** Tags removed: ubuntu22.04 ** Tags added: jammy ** Tags added: gnome42 ** Tags added: nvidia ** Tags removed: gnome42 ** Tags added: gnome ** Tags added: vsync -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1964675 Title: Window dragging lag when rendering 3d objects. (GNOME 42, NVIDIA, glxgear, pymol) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964675/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1964554] Re: Brasero does not burn ISO IMAGE. Error message; "SCSI error on write(0,16): See MMC specs: Sense Key 5 "Illegal request"
Hi Thomas; Thank you very much for getting back to me. So will try to answer your questions. Some of which may be delayed due to me having to run test. *- What is the vendor, model, revision of your drive. You may obtain it from the empty drive by* xorriso : NOTE : Disc status unsuitable for writing Drive current: -outdev '/dev/sr0' Media current: is not recognizable Media status : is not present Drive type : vendor 'ASUS' product 'BW-16D1HT' revision '3.10' *- Do you experience the problem with CD-R or CD-RW media ? If so:* * - What happens if you use a writable DVD medium instead ?* * - Does it help to blank the CD medium before using it with Brasero:* * xorriso -outdev /dev/sr0 -blank as_needed* Will Run these test shortly and get back to you with the results *- Do you experience the problem with other GUI programs like K3B or Xfburn ? - Do you experience the problem with a run of xorriso ? ISO="...path.to.your.iso.image.file..." xorriso -as cdrecord -v dev=/dev/sr0 blank=as_needed "$ISO"* Have not tried K3B or Xfburn. Did try Nero for Linux and had the same result as I did with Brasero. Thank you very much for the assistance. Talk shortly. On Fri, Mar 11, 2022 at 3:10 AM Thomas Schmitt <1964...@bugs.launchpad.net> wrote: > Hi, > > the error message stems from the burner drive and was forwarded by libburn > to Brasero. Strangely the code ASC=21 , ASCQ=04 is not specified in in > the SCSI specs for optical drives (MMC). > In the overall error code list > https://www.t10.org/lists/asc-num.htm > it is listed for other device classes as > 21h/04h DZ UNALIGNED WRITE COMMAND > > I know this error code from > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998718 > with > Drive type : vendor 'ASUS' product 'DRW-24D5MT' revision '2.00' > Brasero crashed at that occasion before it could start to write. > The indirect reason seems to be a bad READ CD command which Brasero > emitted on its own (i.e. not via libburn). It brings the firmware of > two ASUS drives to a state from where it throws that error code. > (Mine is a BW-16D1HT with firmware 1.01.) > It happens only with CD media which were written by write type TAO. > > So (assuming that the drive has address /dev/sr0): > > - What is the vendor, model, revision of your drive. > You may obtain it from the empty drive by > > xorriso -outdev /dev/sr0 -toc | grep 'Drive type' > > - Do you experience the problem with CD-R or CD-RW media ? > If so: > > - What happens if you use a writable DVD medium instead ? > > - Does it help to blank the CD medium before using it with Brasero: > > xorriso -outdev /dev/sr0 -blank as_needed > > - Do you experience the problem with other GUI programs like K3B or > Xfburn ? > > - Do you experience the problem with a run of xorriso ? > > ISO="...path.to.your.iso.image.file..." > xorriso -as cdrecord -v dev=/dev/sr0 blank=as_needed "$ISO" > > > Have a nice day :) > > Thomas > > > ** Bug watch added: Debian Bug tracker #998718 >https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998718 > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1964554 > > Title: > Brasero does not burn ISO IMAGE. Error message; "SCSI error on > write(0,16): See MMC specs: Sense Key 5 "Illegal request" > > Status in brasero package in Ubuntu: > New > > Bug description: > > BraseroLibburn SCSI error condition on command 2Ah WRITE(10): See MMC > specs: Sense Key 5 "Illegal request", ASC 21 ASCQ 04. > BraseroLibburn called brasero_job_set_current_action > BraseroLibburn Libburn reported an error SCSI error on write(0,16): See > MMC specs: Sense Key 5 "Illegal request", ASC 21 ASCQ 04. > BraseroLibburn called brasero_job_error > BraseroLibburn finished with an error > BraseroLibburn asked to stop because of an error > error = 1 > message = "SCSI error on write(0,16): See MMC specs: Sense Key 5 > "Illegal request", ASC 21 ASCQ 04." > BraseroLibburn stopping > Session error : SCSI error on write(0,16): See MMC specs: Sense Key 5 > "Illegal request", ASC 21 ASCQ 04. (brasero_burn_record brasero-burn.c:2856) > --- > ProblemType: Bug > ApportVersion: 2.20.9-0ubuntu7.27 > Architecture: amd64 > CurrentDesktop: ubuntu:GNOME > DistroRelease: Ubuntu 18.04 > InstallationDate: Installed on 2021-01-31 (403 days ago) > InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 > (20190805) > Package: brasero 3.12.1-4ubuntu2 > PackageArchitecture: amd64 > ProcEnviron: >TERM=xterm-256color >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > ProcVersionSignature: Ubuntu 5.4.0-100.113~18.04.1-generic 5.4.166 > Tags: bionic > Uname: Linux 5.4.0-100-generic x86_64 > UpgradeStatus: No upgrade log present (probably fresh install) > UserGroups: adm cdrom dip lpadmin plugdev sambashar
[Bug 1872141] Re: evolution-source-registry crashed with SIGSEGV in invoke_set_property_in_idle_cb()
This happened using ubuntu 22.04 development version. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1872141 Title: evolution-source-registry crashed with SIGSEGV in invoke_set_property_in_idle_cb() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1872141/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1910938] Re: Text is missing from shell panel and menus
Just got a new Lenovo Thinkpad and using Ubuntu 20.04, and I think I'm seeing a very similar issue. After leaving the laptop on for so long eventually a ton of the text menues and displays either show NO text at all, or half of the characters are missing. I'll attempt a screenshot the next time it happens, it doesn't take longer than a day it seems as already reported. I also use Discord so I wonder if that is part of the culprit as well. Will try using without Discord for about a day. I have found a simple logout/login is enough to fix all text menues. So it doesn't seem a full reboot is strictly necessary. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1910938 Title: Text is missing from shell panel and menus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1910938/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1964682] [NEW] IBus not starting properly at login with gnome-shell 42
Public bug reported: To get to the state in the bug summary I did: 1. Installed Ubuntu via the 220312 ISO 2. Made sure that all packages were updated 3. Installed ibus-libpinyin, re-logged in, and added "Intelligent Pinyin" to the input sources 4. Enabled -proposed 5. Run this command: sudo apt install gnome-shell gnome-shell-common gir1.2-mutter-10 libmutter-10-0 mutter-common 6. Rebooted Now, once logged in, gnome-shell does not include "Intelligent Pinyin" in the input source menu. Several expected processes are missing: $ ps aux | grep ibus gunnar 3057 0.0 0.0 232404 7984 ?Sl 20:05 0:00 ibus-daemon --panel disable -r --xim gunnar 3076 0.0 0.0 157280 6228 ?Sl 20:05 0:00 /usr/libexec/ibus-memconf gunnar 5117 0.0 0.0 24492 2776 pts/0S+ 20:06 0:00 grep --color=auto ibus If I start ibus-setup it shows the attached dialog. From there I can click "Yes" and successfully start IBus that way, and then it works as expected. Note that im-config is not involved. Nowadays, on GNOME desktops, we rely completely on the GNOME mechanisms for starting and configuring IBus. One thought is that ibus upstream has not released since August 20. Can it possibly be that some unreleased upstream ibus commits are needed for gnome-shell 42? https://github.com/ibus/ibus/commits/master ** Affects: gnome-shell (Ubuntu) Importance: High Status: New ** Affects: ibus (Ubuntu) Importance: High Status: New ** Tags: jammy rls-jj-incoming ** Attachment added: "ibus-setup_response.png" https://bugs.launchpad.net/bugs/1964682/+attachment/5568298/+files/ibus-setup_response.png ** Also affects: ibus (Ubuntu) Importance: Undecided Status: New ** Changed in: ibus (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1964682 Title: IBus not starting properly at login with gnome-shell 42 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964682/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1964679] Re: gnome-panel crashed with signal 5 in g_settings_get_value()
** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-panel in Ubuntu. https://bugs.launchpad.net/bugs/1964679 Title: gnome-panel crashed with signal 5 in g_settings_get_value() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1964679/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1964678] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast()
** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1964678 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964678/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1964675] [NEW] Window dragging lag when rendering 3d objects. (GNOME 42, NVIDIA, glxgear, pymol)
Public bug reported: OS/software: Ubuntu Jammy Jellyfish (development branch), GNOME 42.beta, X11, NVIDIA-driver-510 (510.54) Hardware: Intel® Xeon(R) CPU E5-1650 v2 @ 3.50GHz × 12, 31,3 GiB RAM, NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] How to reproduce: open glxgear, on the same workspace, move any window, there is badly dragging lag. But there is no lag if move window on a different workspace. CPU/GPU usages are normal (<3%). Disable Sync to VBlank in NVIDIA Settings can solve this issue, but CPU/GPU usages are abornmally high (single core CPU>80%, GPU>10% only for glxgear). Both NVIDIA-driver-510 and NVIDIA-driver-470 have the same issue. But another Intel-GPU based laptop works fine. This is not a glxgear bug, as other realtime 3D rendering (PyMOL, Blender...) casue the same issue. Possible reasons I guess: NVIDIA driver bug, kernel bug, or GNOME 42 bug. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: ubuntu22.04 ** Summary changed: - Window dragging lag when rendering 3d objects. + Window dragging lag when rendering 3d objects. (GNOME 42, NVIDIA) ** Summary changed: - Window dragging lag when rendering 3d objects. (GNOME 42, NVIDIA) + Window dragging lag when rendering 3d objects. (GNOME 42, NVIDIA, glxgear, pymol) ** Tags added: 22.04 ubuntu ** Tags removed: 22.04 ubuntu ** Tags added: ubuntu22.04 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1964675 Title: Window dragging lag when rendering 3d objects. (GNOME 42, NVIDIA, glxgear, pymol) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964675/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1923033] Re: Archive manager drag to extract doesn't work on Gnome with Wayland
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: file-roller (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/1923033 Title: Archive manager drag to extract doesn't work on Gnome with Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/file-roller/+bug/1923033/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1923033] Re: Archive manager drag to extract doesn't work on Gnome with Wayland
Upstream issue in comment #3 was marked as a duplicate of https://gitlab.gnome.org/GNOME/file-roller/-/issues/4 ** Bug watch added: gitlab.gnome.org/GNOME/file-roller/-/issues #4 https://gitlab.gnome.org/GNOME/file-roller/-/issues/4 ** Also affects: file-roller via https://gitlab.gnome.org/GNOME/file-roller/-/issues/4 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/1923033 Title: Archive manager drag to extract doesn't work on Gnome with Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/file-roller/+bug/1923033/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1721049] Re: "Got unknown content type text/html" error viewing flatpack packages
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-software (Ubuntu Artful) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1721049 Title: "Got unknown content type text/html" error viewing flatpack packages To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1721049/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1926256] Re: Pasted text in the terminal is always highlighted and selected
Still a problem for Ubuntu MATE 22.04 LTS. Please fix it on distro level. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1926256 Title: Pasted text in the terminal is always highlighted and selected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1926256/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1964393] Re: gnome-shell crashed with assertion failure in meta_kms_update_set_power_save: !update->plane_assignments
I saw on https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1441#note_1289561 that you introduced a new environment variable MUTTER_DEBUG_DISABLE_TRIPLE_BUFFERING and subscribed to jammy-proposed to try it out. The problem does not occur since the updates! I haven't even set the environment variable. Updated packages were: 2022-03-12 10:59:50 install libadwaita-1-0:amd64 1.1~rc-1 2022-03-12 10:59:50 install gir1.2-adw-1:amd64 1.1~rc-1 2022-03-12 10:59:50 install libopengl0:amd64 1.4.0-1 2022-03-12 10:59:50 install libmutter-10-0:amd64 42~beta-1ubuntu1 2022-03-12 10:59:50 install gir1.2-mutter-10:amd64 42~beta-1ubuntu1 2022-03-12 10:59:52 install xcvt:amd64 0.1.1-3 I also installed lutris since I reproduced the bug, probably uninteresting, but mention it nevertheless due to mesa-utils. 2022-03-11 20:25:52 install fluid-soundfont-gm:all 3.1-5.3 2022-03-11 20:25:53 install fluid-soundfont-gs:all 3.1-5.3 2022-03-11 20:25:53 install libz-mingw-w64:all 1.2.11+dfsg-3 2022-03-11 20:25:53 install libwine-development:amd64 6.0+repack-1ubuntu1 2022-03-11 20:25:58 install python3-lxml:amd64 4.8.0-1 2022-03-11 20:25:58 install python3-setproctitle:amd64 1.2.2-2 2022-03-11 20:25:58 install python3-magic:all 2:0.4.24-2 2022-03-11 20:25:58 install mesa-utils:amd64 8.4.0-1build1 2022-03-11 20:25:58 install lutris:all 0.5.9.1-1 2022-03-11 20:25:58 install python3-soupsieve:all 2.3.1-1 2022-03-11 20:25:58 install python3-bs4:all 4.10.0-2 2022-03-11 20:25:58 install python3-evdev:amd64 1.4.0+dfsg-1build1 2022-03-11 20:25:58 install python3-webencodings:all 0.5.1-4 2022-03-11 20:25:58 install python3-html5lib:all 1.1-3 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1964393 Title: gnome-shell crashed with assertion failure in meta_kms_update_set_power_save: !update->plane_assignments To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964393/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
