[Desktop-packages] [Bug 1884364] Re: package tex-common 6.13 failed to install/upgrade: installed tex-common package post-installation script subprocess returned error exit status 1
[Expired for tex-common (Ubuntu) because there has been no activity for 60 days.] ** Changed in: tex-common (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tex-common in Ubuntu. https://bugs.launchpad.net/bugs/1884364 Title: package tex-common 6.13 failed to install/upgrade: installed tex- common package post-installation script subprocess returned error exit status 1 Status in tex-common package in Ubuntu: Expired Bug description: Processing triggers for tex-common (6.13) ... Running updmap-sys. This may take some time... updmap-sys failed. Output has been stored in /tmp/updmap.hALzKUDl Please include this file if you report a bug. Sometimes, not accepting conffile updates in /etc/texmf/updmap.d causes updmap-sys to fail. Please check for files with extension .dpkg-dist or .ucf-dist in this directory dpkg: error processing package tex-common (--configure): installed tex-common package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: tex-common E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 20.04 Package: tex-common 6.13 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Jun 20 21:11:32 2020 ErrorMessage: installed tex-common package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-06-19 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: tex-common Title: package tex-common 6.13 failed to install/upgrade: installed tex-common package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1884364/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1884437] Re: Windows are resized and reordered upon resume from lock or suspend
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- 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/1884437 Title: Windows are resized and reordered upon resume from lock or suspend Status in gnome-shell package in Ubuntu: Expired Bug description: After a resume from a lock/suspend, windows sizes are changed, fonts are incorrect sizes (until mouse over), and windows have moved from the secondary monitor to the primary monitor. This happens every time the displays have been off (from a suspend or lock screen). AMD graphics with dual 4K displays. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jun 21 07:46:41 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: asus-wmi-sensors, b6c25d2, 5.4.0-21-generic, x86_64: installed asus-wmi-sensors, b6c25d2, 5.4.0-33-generic, x86_64: installed asus-wmi-sensors, b6c25d2, 5.4.0-37-generic, x86_64: installed virtualbox, 6.1.6, 5.4.0-33-generic, x86_64: installed virtualbox, 6.1.6, 5.4.0-37-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Vega 10 XL/XT [Radeon RX Vega 56/64] [1002:687f] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Vega 10 XL/XT [Radeon RX Vega 56/64] [1462:3680] InstallationDate: Installed on 2020-03-07 (105 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200304) MachineType: System manufacturer System Product Name ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_xbqp91@/vmlinuz-5.4.0-21-generic root=ZFS=rpool/ROOT/ubuntu_xbqp91 ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/13/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5406 dmi.board.asset.tag: Default string dmi.board.name: PRIME X470-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5406:bd11/13/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX470-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1884437/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1884547] Re: can't activate the bluethooth headsed with a2dp sound
[Expired for bluez (Ubuntu) because there has been no activity for 60 days.] ** Changed in: bluez (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1884547 Title: can't activate the bluethooth headsed with a2dp sound Status in bluez package in Ubuntu: Expired Bug description: I follow this bug, and still happend https://bugs.launchpad.net/ubuntu/+source/bluez/+filebug/e91ee546 -b48f-11ea-a86b-68b5996a96c8 dpkg --status bluez | grep '^Version:' Version: 5.53-0ubuntu3 cat /etc/*-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=20.04 DISTRIB_CODENAME=focal DISTRIB_DESCRIPTION="Ubuntu 20.04 LTS" NAME="Ubuntu" VERSION="20.04 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04 LTS" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=focal UBUNTU_CODENAME=focal ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jun 22 10:54:05 2020 InstallationDate: Installed on 2020-05-19 (33 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20NYS04V00 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-37-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/27/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2JET87W (1.65 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NYS04V00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2JET87W(1.65):bd03/27/2020:svnLENOVO:pn20NYS04V00:pvrThinkPadT490s:rvnLENOVO:rn20NYS04V00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T490s dmi.product.name: 20NYS04V00 dmi.product.sku: LENOVO_MT_20NY_BU_Think_FM_ThinkPad T490s dmi.product.version: ThinkPad T490s dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: 04:ED:33:30:BC:12 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:2532201 acl:38232 sco:36899 events:9437 errors:0 TX bytes:4236888 acl:2223 sco:36783 commands:6938 errors:0 mtime.conffile..etc.bluetooth.input.conf: 2020-06-10T09:52:46.145873 mtime.conffile..etc.bluetooth.main.conf: 2020-06-04T16:03:04.084396 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1884547/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding
I'm seeing the same problem. Debug information below.
LIBVA_MESSAGING_LEVEL=2 snap run chromium
[20382:20382:0821/200854.560443:ERROR:sandbox_linux.cc(374)]
InitializeSandbox() called with multiple threads in process gpu-process.
[20548:13:0821/200904.074169:ERROR:batching_media_log.cc(38)] MediaEvent:
{"error":"{\"causes\":[{\"causes\":[],\"data\":{},\"stack\":[{\"file\":\"../../media/filters/decrypting_video_decoder.cc\",\"line\":53}],\"status_code\":264,\"status_message\":\"\"}],\"data\":{\"Decoder
name\":\"DecryptingVideoDecoder\"},\"stack\":[{\"file\":\"../../media/filters/decoder_selector.cc\",\"line\":172}],\"status_code\":265,\"status_message\":\"\"}"}
[20248:20383:0821/200904.173566:ERROR:object_proxy.cc(622)] Failed to call
method: org.freedesktop.PowerManagement.Inhibit.Inhibit: object_path=
/org/freedesktop/PowerManagement/Inhibit:
org.freedesktop.DBus.Error.AccessDenied: An AppArmor policy prevents this
sender from sending this message to this recipient; type="method_call",
sender=":1.504" (uid=1000 pid=20248
comm="/snap/chromium/1260/usr/lib/chromium-browser/chrom"
label="snap.chromium.chromium (enforce)")
interface="org.freedesktop.PowerManagement.Inhibit" member="Inhibit" error
name="(unset)" requested_reply="0"
destination="org.freedesktop.PowerManagement" (uid=1000 pid=1571
comm="xfce4-power-manager " label="unconfined")
[20248:20383:0821/200904.173588:ERROR:power_save_blocker_linux.cc(373)] No
response to Inhibit() request!
[20248:20383:0821/200904.379145:ERROR:object_proxy.cc(622)] Failed to call
method: org.freedesktop.PowerManagement.Inhibit.Inhibit: object_path=
/org/freedesktop/PowerManagement/Inhibit:
org.freedesktop.DBus.Error.AccessDenied: An AppArmor policy prevents this
sender from sending this message to this recipient; type="method_call",
sender=":1.505" (uid=1000 pid=20248
comm="/snap/chromium/1260/usr/lib/chromium-browser/chrom"
label="snap.chromium.chromium (enforce)")
interface="org.freedesktop.PowerManagement.Inhibit" member="Inhibit" error
name="(unset)" requested_reply="0"
destination="org.freedesktop.PowerManagement" (uid=1000 pid=1571
comm="xfce4-power-manager " label="unconfined")
[20248:20383:0821/200904.379183:ERROR:power_save_blocker_linux.cc(373)] No
response to Inhibit() request!
[20248:20248:0821/200913.822437:ERROR:event_router.cc(713)] Event dispatched
while shutting down extensions browser client.
libva info: VA-API version 1.8.0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_8
libva info: va_openDriver() returns 0
vainfo: VA-API version: 1.8 (libva 2.1.0)
vainfo: Driver version: Intel iHD driver for Intel(R) Gen Graphics - 20.2.pre
(f403839f)
vainfo: Supported profile and entrypoints
VAProfileNone : VAEntrypointVideoProc
VAProfileNone : VAEntrypointStats
VAProfileMPEG2Simple: VAEntrypointVLD
VAProfileMPEG2Simple: VAEntrypointEncSlice
VAProfileMPEG2Main : VAEntrypointVLD
VAProfileMPEG2Main : VAEntrypointEncSlice
VAProfileH264Main : VAEntrypointVLD
VAProfileH264Main : VAEntrypointEncSlice
VAProfileH264Main : VAEntrypointFEI
VAProfileH264Main : VAEntrypointEncSliceLP
VAProfileH264High : VAEntrypointVLD
VAProfileH264High : VAEntrypointEncSlice
VAProfileH264High : VAEntrypointFEI
VAProfileH264High : VAEntrypointEncSliceLP
VAProfileVC1Simple : VAEntrypointVLD
VAProfileVC1Main: VAEntrypointVLD
VAProfileVC1Advanced: VAEntrypointVLD
VAProfileJPEGBaseline : VAEntrypointVLD
VAProfileJPEGBaseline : VAEntrypointEncPicture
VAProfileH264ConstrainedBaseline: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline: VAEntrypointFEI
VAProfileH264ConstrainedBaseline: VAEntrypointEncSliceLP
VAProfileVP8Version0_3 : VAEntrypointVLD
VAProfileVP8Version0_3 : VAEntrypointEncSlice
VAProfileHEVCMain : VAEntrypointVLD
VAProfileHEVCMain : VAEntrypointEncSlice
VAProfileHEVCMain : VAEntrypointFEI
VAProfileHEVCMain10 : VAEntrypointVLD
VAProfileHEVCMain10 : VAEntrypointEncSlice
VAProfileVP9Profile0: VAEntrypointVLD
VAProfileVP9Profile2: VAEntrypointVLD
audio_buffering_state {"state":"BUFFERING_HAVE_ENOUGH"}
dimensions "1920x988"
duration243.981
error
"{\"causes\":[{\"causes\":[],\"data\":{},\"stack\":[{\"file\":\"../../media/filters/decrypting_video_decoder.cc\",\"line\":53}],\"status_code\":264,\"status_message\":\"\"}],\"data\":{\"Decoder
name\":\"DecryptingVideoDe
[Desktop-packages] [Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding
* now not working -- 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/1816497 Title: [snap] vaapi chromium no video hardware decoding Status in chromium-browser package in Ubuntu: In Progress Bug description: News : - Candidate Chromium 83 Snap with vaapi enabled can be installed with : sudo snap install --channel=candidate/vaapi chromium Check that your vidéo is gpu decoded but checking "MojoVideoDecoder" in about:media-internals Widevine DRM streams will have DecryptingVideoDecoder Please report success/failure with - distro version - GPU Hardware used - Codec used --Original Bug report - Libva is no longer working for snap installed chromium 72.0.3626.109 (Official Build) snap (64-bit) I followed this instruction sudo snap install --channel=candidate/vaapi chromium My amdgpu can use libva `vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM 3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1) vainfo: Supported profile and entrypoints VAProfileMPEG2Simple: VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointVLD VAProfileVC1Simple : VAEntrypointVLD VAProfileVC1Main: VAEntrypointVLD VAProfileVC1Advanced: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice VAProfileH264Main : VAEntrypointVLD VAProfileH264Main : VAEntrypointEncSlice VAProfileH264High : VAEntrypointVLD VAProfileH264High : VAEntrypointEncSlice VAProfileHEVCMain : VAEntrypointVLD VAProfileHEVCMain10 : VAEntrypointVLD VAProfileJPEGBaseline : VAEntrypointVLD VAProfileNone : VAEntrypointVideoProc` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding
Was working last week even with vp9:
vainfo output:
libva info: VA-API version 1.7.0
libva info: User environment variable requested driver 'iHD'
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_7
libva info: va_openDriver() returns 0
vainfo: VA-API version: 1.7 (libva 2.9.0.pre1)
vainfo: Driver version: Intel iHD driver for Intel(R) Gen Graphics - 20.1.1 ()
vainfo: Supported profile and entrypoints
VAProfileNone : VAEntrypointVideoProc
VAProfileNone : VAEntrypointStats
VAProfileMPEG2Simple: VAEntrypointVLD
VAProfileMPEG2Simple: VAEntrypointEncSlice
VAProfileMPEG2Main : VAEntrypointVLD
VAProfileMPEG2Main : VAEntrypointEncSlice
VAProfileH264Main : VAEntrypointVLD
VAProfileH264Main : VAEntrypointEncSlice
VAProfileH264Main : VAEntrypointFEI
VAProfileH264Main : VAEntrypointEncSliceLP
VAProfileH264High : VAEntrypointVLD
VAProfileH264High : VAEntrypointEncSlice
VAProfileH264High : VAEntrypointFEI
VAProfileH264High : VAEntrypointEncSliceLP
VAProfileVC1Simple : VAEntrypointVLD
VAProfileVC1Main: VAEntrypointVLD
VAProfileVC1Advanced: VAEntrypointVLD
VAProfileJPEGBaseline : VAEntrypointVLD
VAProfileJPEGBaseline : VAEntrypointEncPicture
VAProfileH264ConstrainedBaseline: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline: VAEntrypointFEI
VAProfileH264ConstrainedBaseline: VAEntrypointEncSliceLP
VAProfileVP8Version0_3 : VAEntrypointVLD
VAProfileVP8Version0_3 : VAEntrypointEncSlice
VAProfileHEVCMain : VAEntrypointVLD
VAProfileHEVCMain : VAEntrypointEncSlice
VAProfileHEVCMain : VAEntrypointFEI
VAProfileHEVCMain10 : VAEntrypointVLD
VAProfileHEVCMain10 : VAEntrypointEncSlice
VAProfileVP9Profile0: VAEntrypointVLD
VAProfileVP9Profile2: VAEntrypointVLD
media-internals Stuff:
render_id: 24
player_id: 43
origin_url: https://www.youtube.com/
kFrameUrl: https://www.youtube.com/watch?v=tEK7GIefwZE
kFrameTitle:
url: blob:https://www.youtube.com/28d56b05-cb4e-4d58-abc1-a85d8b4d578a
info: Selected video track: [1]
pipeline_state: kPlaying
kVideoTracks: [object Object]
kAudioTracks: [object Object]
kIsAudioDecryptingDemuxerStream: false
kAudioDecoderName: FFmpegAudioDecoder
kIsPlatformAudioDecoder: false
error:
{"causes":[{"causes":[],"data":{},"stack":[{"file":"../../media/filters/decrypting_video_decoder.cc","line":53}],"status_code":264,"status_message":""}],"data":{"Decoder
name":"DecryptingVideoDecoder"},"stack":[{"file":"../../media/filters/decoder_selector.cc","line":172}],"status_code":265,"status_message":""}
kIsVideoDecryptingDemuxerStream: false
kVideoDecoderName: VpxVideoDecoder
kIsPlatformVideoDecoder: false
event: kPlay
audio_buffering_state: [object Object]
dimensions: 1920x1080
kResolution: 1920x1080
video_buffering_state: [object Object]
pipeline_buffering_state: [object Object]
duration: 799.461
--
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/1816497
Title:
[snap] vaapi chromium no video hardware decoding
Status in chromium-browser package in Ubuntu:
In Progress
Bug description:
News :
- Candidate Chromium 83 Snap with vaapi enabled can be installed with
:
sudo snap install --channel=candidate/vaapi chromium
Check that your vidéo is gpu decoded but checking "MojoVideoDecoder"
in about:media-internals
Widevine DRM streams will have DecryptingVideoDecoder
Please report success/failure with
- distro version
- GPU Hardware used
- Codec used
--Original Bug report -
Libva is no longer working for snap installed chromium 72.0.3626.109
(Official Build) snap (64-bit)
I followed this instruction
sudo snap install --channel=candidate/vaapi chromium
My amdgpu can use libva
`vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM
3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1)
vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple: VAEntrypointVLD
VAProfileMPEG2Main : VAEntrypointVLD
VAProfileVC1Simple : VAEntrypointVLD
VAProfileVC1Main: VAEntrypointVLD
VAProfileVC1Advanced: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEn
[Desktop-packages] [Bug 1892427] Re: [amdgpu] HDMI connected TV wakeup problems
> I wonder though if this is also a problem with the TV failing to sleep > correctly > and instead disconnecting from the computer... " I tried turning the TV off with the remote, then turning the TV back on. Looks like the same (or similar) condition. All the windows on the second display lost their geometry. I can see them in the launcher view, but they are gone somewhere. Perhaps their coordinates have traveled off-screen? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1892427 Title: [amdgpu] HDMI connected TV wakeup problems Status in xserver-xorg-video-amdgpu package in Ubuntu: Incomplete Bug description: The setup here is critical to understanding the problem. A laptop is connected via HDMI to a TV monitor. Two displays are thus available to the OS. Everything works great both in mirror display and regular display. At the end of day, I lock the user account and the display manager (DM) tells the monitors to blank (sleep?). When I touch the DM and login the laptop display livens up and looks good. However, the TV display often doesn't and I need to wake up the TV with the TV control stick. This works OK, and the second display comes back. And all the windows associated with that display return from sleep OK. *HOWEVER*, all the geometry for those windows (term windows is one example) are lost. I can see the windows in the term overview, but I cant get to them on the second display. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-112.113~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-112-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.24 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Aug 20 17:00:58 2020 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Carrizo [1002:9874] (rev c8) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Carrizo [103c:8348] InstallationDate: Installed on 2018-04-20 (853 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) MachineType: HP HP Laptop 17-ak0xx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-112-generic root=UUID=79cc5ed4-f740-450d-9a89-c5b4f899d10e ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/02/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.06 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8348 dmi.board.vendor: HP dmi.board.version: 42.20 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.06:bd11/02/2017:svnHP:pnHPLaptop17-ak0xx:pvrType1ProductConfigId:rvnHP:rn8348:rvr42.20:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 17-ak0xx dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz 1:0.9.12.3+16.04.20171116-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Wed Aug 5 16:27:12 2020 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2 xserver.video_driver: amdgpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1892427/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1850753] Re: Ubuntu 19.10 cannot set background to solid color
Looks like the removal of the solid background option was one dev's dictatorial and narrow-minded decision. What can I say. Enjoy open source. https://www.reddit.com/r/gnome/comments/dayto8/can_someone_point_me_to_the_train_of/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1850753 Title: Ubuntu 19.10 cannot set background to solid color Status in gnome-control-center: Fix Released Status in gnome-control-center package in Ubuntu: Won't Fix Bug description: The settings Background only allows setting to a picture, not a solid color. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1850753/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892400] Re: Open text files with File manager (mouse won't release)
** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1892400 Title: Open text files with File manager (mouse won't release) Status in nautilus package in Ubuntu: New Bug description: When you open Text File from File Manager mouse cursor hangs until time outs. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.4-0~ubuntu18.04.5 ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18 Uname: Linux 4.15.0-112-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 20 19:01:13 2020 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'288' b'org.gnome.nautilus.window-state' b'geometry' b"'864x458+697+195'" b'org.gnome.nautilus.desktop' b'trash-icon-visible' b'false' b'org.gnome.nautilus.list-view' b'default-visible-columns' b"['name', 'size', 'type', 'date_modified']" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where', 'date_modified_with_time', 'recency']" InstallationDate: Installed on 2017-08-07 (1109 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: nautilus UpgradeStatus: Upgraded to bionic on 2020-05-25 (87 days ago) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1892400/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
** Information type changed from Public Security to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 Status in Pop!_OS: New Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Status in linux package in Arch Linux: Confirmed Status in linux package in Fedora: Confirmed Bug description: Hello The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at all (pointer and click never move when touchpad is touched). This has been reported by other users in various websites, with various linux systems including other Ubuntu systems, but I saw no launchpad bug so I post one. Example of websites covering the issue : - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly the same laptop) - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar laptop) xinput indentifies it as MSFT0001:00 04F3:3140 Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer (2)] ⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Ideapad extra buttons id=15 [slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=18 [slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] Thanks a lot for your time. It does not help, but I can confirm what was reported on askubuntu by another user : the touchpad does work on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1567 F pulseaudio /dev/snd/controlC1: nicolas1567 F pulseaudio /dev/snd/controlC2: nicolas1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 10 20:14:25 2020 InstallationDate: Installed on 2020-07-02 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 82B5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN19WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion 5 15ARH05 dmi.modalias: dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05: dmi.product.family: Legion 5 15ARH05 dmi.product.name: 82B5 dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_Legion 5 15ARH05 dmi.product.version: Lenovo Legion 5 15ARH05 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 A
[Desktop-packages] [Bug 1892439] Re: [Lenovo ThinkPad T410s, Intel IbexPeak HDMI, Digital Out, HDMI] No sound at all
Try to load the i915 module early: echo "i915" | sudo tee -a /etc/initramfs-tools/modules sudo update-initramfs -u -k all See if HDMI/DP audio is available after reboot. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1892439 Title: [Lenovo ThinkPad T410s, Intel IbexPeak HDMI, Digital Out, HDMI] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: ThinkPad T410s. No audio from DisplayPort. Can't even select it as the audio source. Video works fine ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: voorhees857 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Aug 20 21:46:38 2020 InstallationDate: Installed on 2020-08-04 (16 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: voorhees857 F pulseaudio Symptom_Jack: Digital Out, HDMI Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [2901A3U, Intel IbexPeak HDMI, Digital Out, HDMI] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/07/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6UET38WW (1.16 ) dmi.board.name: 2901A3U dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6UET38WW(1.16):bd06/07/2010:svnLENOVO:pn2901A3U:pvrThinkPadT410s:rvnLENOVO:rn2901A3U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T410s dmi.product.name: 2901A3U dmi.product.version: ThinkPad T410s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1892439/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1818938] Re: Found storing user fingerprints as raw image files
** Changed in: libfprint Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/1818938 Title: Found storing user fingerprints as raw image files Status in libfprint: Fix Released Status in libfprint package in Ubuntu: Triaged Bug description: Dear all, Currently, libfprint saves a fingerprint image (FP1 or 2?) to a file on the host without any encryption. Once fingerprint has been leaked, victims are leaked for the rest of life since it lasts for a life. It is necessary to prepare for the problem. Especially, when I use `fp_print_data_save()` using libfprint library for enrolling my fingerprints, the image is saved in user’s home directory without any protection scheme. Though `fprintd` generates fingerprint image with root permission for protecting the file from attackers, it is not of itself sufficient. FYI, similar issues on Android have been reported and cryptographic operations are introduced to encrypt fingerprint (see [1-2]). [1] https://www.blackhat.com/docs/us-15/materials/us-15-Zhang-Fingerprints-On-Mobile-Devices-Abusing-And-Leaking-wp.pdf [2] https://www.zdnet.com/article/hackers-can-remotely-steal-fingerprints-from-android-phones/ Lastly, is it a kind of `CWE-311: Missing Encryption of Sensitive Data`? (see https://cwe.mitre.org/data/definitions/311.html) Many thanks!! To manage notifications about this bug go to: https://bugs.launchpad.net/libfprint/+bug/1818938/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1819406] Re: Found broken a feature for fingerprint image obfuscation
** Changed in: libfprint Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/1819406 Title: Found broken a feature for fingerprint image obfuscation Status in libfprint: Fix Released Status in libfprint package in Ubuntu: Confirmed Bug description: Dear all, In this package, a random seed is used for generation key for obfuscating a fingerprint image in uru4000 driver. Unfortunately, it seems that the seed always exhibits the same sequence of numbers each time since it is generated from rand() in libc by default. Then I reported this issue to the upstream with the patch. However, the maintainer insists that the obfuscation-feature can be broken since the key for encryption is composed of just 4-bytes length. Thus, there is no need to patch about random seed anyway. It's pretty weird to say that. Would it be all right if I leave this as it is? Many thanks!! To manage notifications about this bug go to: https://bugs.launchpad.net/libfprint/+bug/1819406/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1822590] Re: Found storing user fingerprints without encryption
** Changed in: fprintd Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fprintd in Ubuntu. https://bugs.launchpad.net/bugs/1822590 Title: Found storing user fingerprints without encryption Status in fprintd: Fix Released Status in apparmor package in Ubuntu: Won't Fix Status in fprintd package in Ubuntu: Triaged Status in Debian: Confirmed Bug description: Dear all, I would like to report a new issue as follows. ‘fprintd’ saves a fingerprint data, ISO/IEC 19794-2 formatted, to a file on the host without any encryption. Though fprintd generates fingerprint image with root permission for protecting the file from attackers, it is not of itself sufficient. It is well known threat model that a formatted fingerprint data can be restored to original image about a decade ago. [1-4] are presented to create sophisticated and natural-looking fingerprints only from the numerical template data format as defined in ISO/IEC 19794-2. They also successfully evaluated these approaches against a number of undisclosed state-of-the-art algorithms and the NIST Fingerprint Image Software. We need improvements of those issues. [1] R. Cappelli et al., “Fingerprint Image Reconstruction from Standard Templates”, IEEE Trans. on Pattern Analysis and Machine Intelligence, vol.29, no.9, pp.1489-1503, 2007. [2] A. Ross et al., “From template to image: Reconstructing fingerprints from minutiae points”, IEEE Trans on Pattern Analysis and Machine Intelligence, vol.29, no.4, pp.544-560, 2007. [3] R. Cappelli et al., “Can Fingerprints be reconstructed from ISO Templates?”, IEEE ICARCV 2006. [4] J. Feng et al., “Fingerprint Reconstruction: From Minutiae to Phase”, IEEE Trans on Pattern Analysis and Machine Intelligence, vol.33, no.2, pp.209-223, 2011. Sincerely, Seong-Joong Kim To manage notifications about this bug go to: https://bugs.launchpad.net/fprintd/+bug/1822590/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1878974] Re: Unable to use HP USB Printer in Ubuntu 20.04 - apear to be hplip issues
ippusbxd has known problems and it will get replaced by ipp-usb where these problems are solved. See the MIR for ipp-usb, bug 1891157. With this replacement driverless printing will work correctly and so most modern HP printers will work without HPLIP at all. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1878974 Title: Unable to use HP USB Printer in Ubuntu 20.04 - apear to be hplip issues Status in HPLIP: New Status in hplip package in Ubuntu: Incomplete Bug description: Hi, I am unable to connect and print with a HP USB Pinter on Ubuntu 20.04, Spent some time troubleshooting with the default (previously current) drivers hplip ver. 3.20.3 , but Ubuntu 20.04 does not seem to be supported officially due to missing dependencies. Errors about missing pyqt4 dependencies among others. When using the hplip ver. 3.20.3 from the Ubuntu Repo printer is found but fails to print. Just noticed similar bug filed, 690720 , and saw note that new hplip ver. 3.20.5 was just released and supports Ubuntu 20.04 When trying to install new package hplip ver. 3.20.5 with the .run script provided by HP I am unable to complete installatoin as it reports unmet dependency of pyqt5 , even though package python3-pyqt5 is installed on system. https://developers.hp.com/hp-linux-imaging-and-printing/gethplip Maybe the repo just needs to be updated with a newer build (3.20.5) to install on my system, or is there something that can be done in the meantime. Below hp-check -t when using the repo hplip ver. 3.20.3 , == Saving output in log file: /root/hp-check.log HP Linux Imaging and Printing System (ver. 3.20.3) Dependency/Version Check Utility ver. 15.1 Copyright (c) 2001-18 HP Development Company, LP This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to distribute it under certain conditions. See COPYING file for more details. Note: hp-check can be run in three modes: 1. Compile-time check mode (-c or --compile): Use this mode before compiling the HPLIP supplied tarball (.tar.gz or .run) to determine if the proper dependencies are installed to successfully compile HPLIP. 2. Run-time check mode (-r or --run): Use this mode to determine if a distro supplied package (.deb, .rpm, etc) or an already built HPLIP supplied tarball has the proper dependencies installed to successfully run. 3. Both compile- and run-time check mode (-b or --both) (Default): This mode will check both of the above cases (both compile- and run-time dependencies). Check types: a. EXTERNALDEP - External Dependencies b. GENERALDEP - General Dependencies (required both at compile and run time) c. COMPILEDEP - Compile time Dependencies d. [All are run-time checks] PYEXT SCANCONF QUEUES PERMISSION Status Types: OK MISSING - Missing Dependency or Permission or Plug-in INCOMPAT - Incompatible dependency-version or Plugin-version warning: ubuntu-20.04 version is not supported. Using ubuntu-19.10 versions dependencies to verify and install... --- | SYSTEM INFO | --- Kernel: 5.4.0-29-generic #33-Ubuntu SMP Wed Apr 29 14:32:27 UTC 2020 GNU/Linux Host: judith-mini Proc: 5.4.0-29-generic #33-Ubuntu SMP Wed Apr 29 14:32:27 UTC 2020 GNU/Linux Distribution: ubuntu 20.04 Bitness: 64 bit
[Desktop-packages] [Bug 1877798] Re: The "areas" click-method doesn't work with "SynPS/2 Synaptics TouchPad" on "Clevo N141ZU" laptop
I forgot to mention that I'm running: * Ubuntu 20.04.1 * xserver-xorg-input-libinput 0.29.0-1 * libinput-bin 1.15.5-1 * libinput10:amd64 1.15.5-1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1877798 Title: The "areas" click-method doesn't work with "SynPS/2 Synaptics TouchPad" on "Clevo N141ZU" laptop Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Bug description: I'm trying to switch from the "fingers" click-method to the "areas" click-method, because tapping with three fingers is awkward and I find that my three-fingers taps are rarely registered as such. * "fingers": single-finger tap for a click, two-finger tap for a right click, three-finger tap for a middle click * "areas": tap in the lower right corner for a right click, tap in the upper right corner for a middle click After running the following command: gsettings set org.gnome.desktop.peripherals.touchpad click-method \ "'areas'" I can verify with gsettings get... that the click-method is now "areas", however tapping in the lower/upper right corners of the touchpad does not elicit the expected right/middle clicks, whereas tapping with two fingers elicits a right click. This remains the case even after rebooting the computer. It's as if the click-method was ignored and defaulted to "fingers". I couldn't find any similar bug reports and don't know how to investigate this problem further. I assume this problem is specific to my hardware, otherwise it would have been noticed already. I attach the output of the following commands: cat /proc/bus/input/devices xinput --list xinput --list-props 13 # where 13 is the touchpad's ID Should I report this issue to upstream libinput (www.freedesktop.org/wiki/Software/libinput)? Or could this be something to do with GNOME instead? Using Ubuntu 20.04 with libinput 1.15.5-1 and xserver-xorg-input- libinput 0.29.0-1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/1877798/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1877798] Re: The "areas" click-method doesn't work with "SynPS/2 Synaptics TouchPad" on "Clevo N141ZU" laptop
I have the same problem with touchpad in laptop "Lenovo Yoga Slim 7 14 with Ryzen 4700u". My Ubuntu 20.04 setting is "Tweaks => Keyboard & Mouse => Mouse Click Emulation => Area". With this setting: Three finger tap works as a middle click and two finger tap works as a right click which is actually incorrect behavior. I would like to use upper right corner for middle click. I tried to install "xserver-xorg-input-synaptics", but it doesn't fix it. The upper right corner tap worked well with my previous laptop HP Envy 13" Skylake, with installed package "xserver-xorg-input-synaptics", in Ubuntu 20.04. So the issue is HW dependent. ** Attachment added: "/proc/bus/input/devices" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/1877798/+attachment/5403559/+files/input_devices.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1877798 Title: The "areas" click-method doesn't work with "SynPS/2 Synaptics TouchPad" on "Clevo N141ZU" laptop Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Bug description: I'm trying to switch from the "fingers" click-method to the "areas" click-method, because tapping with three fingers is awkward and I find that my three-fingers taps are rarely registered as such. * "fingers": single-finger tap for a click, two-finger tap for a right click, three-finger tap for a middle click * "areas": tap in the lower right corner for a right click, tap in the upper right corner for a middle click After running the following command: gsettings set org.gnome.desktop.peripherals.touchpad click-method \ "'areas'" I can verify with gsettings get... that the click-method is now "areas", however tapping in the lower/upper right corners of the touchpad does not elicit the expected right/middle clicks, whereas tapping with two fingers elicits a right click. This remains the case even after rebooting the computer. It's as if the click-method was ignored and defaulted to "fingers". I couldn't find any similar bug reports and don't know how to investigate this problem further. I assume this problem is specific to my hardware, otherwise it would have been noticed already. I attach the output of the following commands: cat /proc/bus/input/devices xinput --list xinput --list-props 13 # where 13 is the touchpad's ID Should I report this issue to upstream libinput (www.freedesktop.org/wiki/Software/libinput)? Or could this be something to do with GNOME instead? Using Ubuntu 20.04 with libinput 1.15.5-1 and xserver-xorg-input- libinput 0.29.0-1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/1877798/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1877798] Re: The "areas" click-method doesn't work with "SynPS/2 Synaptics TouchPad" on "Clevo N141ZU" laptop
** Attachment added: "xinput --list" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/1877798/+attachment/5403560/+files/xinput_list.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1877798 Title: The "areas" click-method doesn't work with "SynPS/2 Synaptics TouchPad" on "Clevo N141ZU" laptop Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Bug description: I'm trying to switch from the "fingers" click-method to the "areas" click-method, because tapping with three fingers is awkward and I find that my three-fingers taps are rarely registered as such. * "fingers": single-finger tap for a click, two-finger tap for a right click, three-finger tap for a middle click * "areas": tap in the lower right corner for a right click, tap in the upper right corner for a middle click After running the following command: gsettings set org.gnome.desktop.peripherals.touchpad click-method \ "'areas'" I can verify with gsettings get... that the click-method is now "areas", however tapping in the lower/upper right corners of the touchpad does not elicit the expected right/middle clicks, whereas tapping with two fingers elicits a right click. This remains the case even after rebooting the computer. It's as if the click-method was ignored and defaulted to "fingers". I couldn't find any similar bug reports and don't know how to investigate this problem further. I assume this problem is specific to my hardware, otherwise it would have been noticed already. I attach the output of the following commands: cat /proc/bus/input/devices xinput --list xinput --list-props 13 # where 13 is the touchpad's ID Should I report this issue to upstream libinput (www.freedesktop.org/wiki/Software/libinput)? Or could this be something to do with GNOME instead? Using Ubuntu 20.04 with libinput 1.15.5-1 and xserver-xorg-input- libinput 0.29.0-1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/1877798/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1877798] Re: The "areas" click-method doesn't work with "SynPS/2 Synaptics TouchPad" on "Clevo N141ZU" laptop
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xserver-xorg-input-libinput (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1877798 Title: The "areas" click-method doesn't work with "SynPS/2 Synaptics TouchPad" on "Clevo N141ZU" laptop Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Bug description: I'm trying to switch from the "fingers" click-method to the "areas" click-method, because tapping with three fingers is awkward and I find that my three-fingers taps are rarely registered as such. * "fingers": single-finger tap for a click, two-finger tap for a right click, three-finger tap for a middle click * "areas": tap in the lower right corner for a right click, tap in the upper right corner for a middle click After running the following command: gsettings set org.gnome.desktop.peripherals.touchpad click-method \ "'areas'" I can verify with gsettings get... that the click-method is now "areas", however tapping in the lower/upper right corners of the touchpad does not elicit the expected right/middle clicks, whereas tapping with two fingers elicits a right click. This remains the case even after rebooting the computer. It's as if the click-method was ignored and defaulted to "fingers". I couldn't find any similar bug reports and don't know how to investigate this problem further. I assume this problem is specific to my hardware, otherwise it would have been noticed already. I attach the output of the following commands: cat /proc/bus/input/devices xinput --list xinput --list-props 13 # where 13 is the touchpad's ID Should I report this issue to upstream libinput (www.freedesktop.org/wiki/Software/libinput)? Or could this be something to do with GNOME instead? Using Ubuntu 20.04 with libinput 1.15.5-1 and xserver-xorg-input- libinput 0.29.0-1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/1877798/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1877798] Re: The "areas" click-method doesn't work with "SynPS/2 Synaptics TouchPad" on "Clevo N141ZU" laptop
** Attachment added: "xinput --list-props 12" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/1877798/+attachment/5403561/+files/xinput_list_props_12.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1877798 Title: The "areas" click-method doesn't work with "SynPS/2 Synaptics TouchPad" on "Clevo N141ZU" laptop Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Bug description: I'm trying to switch from the "fingers" click-method to the "areas" click-method, because tapping with three fingers is awkward and I find that my three-fingers taps are rarely registered as such. * "fingers": single-finger tap for a click, two-finger tap for a right click, three-finger tap for a middle click * "areas": tap in the lower right corner for a right click, tap in the upper right corner for a middle click After running the following command: gsettings set org.gnome.desktop.peripherals.touchpad click-method \ "'areas'" I can verify with gsettings get... that the click-method is now "areas", however tapping in the lower/upper right corners of the touchpad does not elicit the expected right/middle clicks, whereas tapping with two fingers elicits a right click. This remains the case even after rebooting the computer. It's as if the click-method was ignored and defaulted to "fingers". I couldn't find any similar bug reports and don't know how to investigate this problem further. I assume this problem is specific to my hardware, otherwise it would have been noticed already. I attach the output of the following commands: cat /proc/bus/input/devices xinput --list xinput --list-props 13 # where 13 is the touchpad's ID Should I report this issue to upstream libinput (www.freedesktop.org/wiki/Software/libinput)? Or could this be something to do with GNOME instead? Using Ubuntu 20.04 with libinput 1.15.5-1 and xserver-xorg-input- libinput 0.29.0-1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/1877798/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1878974] Re: Unable to use HP USB Printer in Ubuntu 20.04 - apear to be hplip issues
I was unable to print and scan with my HP Photosmart 5524 on two PCs with Kubuntu 20.04. But I fixed the problem today by purging the ippusbxd package. Everything is now working fine! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1878974 Title: Unable to use HP USB Printer in Ubuntu 20.04 - apear to be hplip issues Status in HPLIP: New Status in hplip package in Ubuntu: Incomplete Bug description: Hi, I am unable to connect and print with a HP USB Pinter on Ubuntu 20.04, Spent some time troubleshooting with the default (previously current) drivers hplip ver. 3.20.3 , but Ubuntu 20.04 does not seem to be supported officially due to missing dependencies. Errors about missing pyqt4 dependencies among others. When using the hplip ver. 3.20.3 from the Ubuntu Repo printer is found but fails to print. Just noticed similar bug filed, 690720 , and saw note that new hplip ver. 3.20.5 was just released and supports Ubuntu 20.04 When trying to install new package hplip ver. 3.20.5 with the .run script provided by HP I am unable to complete installatoin as it reports unmet dependency of pyqt5 , even though package python3-pyqt5 is installed on system. https://developers.hp.com/hp-linux-imaging-and-printing/gethplip Maybe the repo just needs to be updated with a newer build (3.20.5) to install on my system, or is there something that can be done in the meantime. Below hp-check -t when using the repo hplip ver. 3.20.3 , == Saving output in log file: /root/hp-check.log HP Linux Imaging and Printing System (ver. 3.20.3) Dependency/Version Check Utility ver. 15.1 Copyright (c) 2001-18 HP Development Company, LP This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to distribute it under certain conditions. See COPYING file for more details. Note: hp-check can be run in three modes: 1. Compile-time check mode (-c or --compile): Use this mode before compiling the HPLIP supplied tarball (.tar.gz or .run) to determine if the proper dependencies are installed to successfully compile HPLIP. 2. Run-time check mode (-r or --run): Use this mode to determine if a distro supplied package (.deb, .rpm, etc) or an already built HPLIP supplied tarball has the proper dependencies installed to successfully run. 3. Both compile- and run-time check mode (-b or --both) (Default): This mode will check both of the above cases (both compile- and run-time dependencies). Check types: a. EXTERNALDEP - External Dependencies b. GENERALDEP - General Dependencies (required both at compile and run time) c. COMPILEDEP - Compile time Dependencies d. [All are run-time checks] PYEXT SCANCONF QUEUES PERMISSION Status Types: OK MISSING - Missing Dependency or Permission or Plug-in INCOMPAT - Incompatible dependency-version or Plugin-version warning: ubuntu-20.04 version is not supported. Using ubuntu-19.10 versions dependencies to verify and install... --- | SYSTEM INFO | --- Kernel: 5.4.0-29-generic #33-Ubuntu SMP Wed Apr 29 14:32:27 UTC 2020 GNU/Linux Host: judith-mini Proc: 5.4.0-29-generic #33-Ubuntu SMP Wed Apr 29 14:32:27 UTC 2020 GNU/Linux Distribution: ubuntu 20.04 Bitness: 64 bit --- | HPLIP CONFIGURATION | --- HPLIP-Version: H
[Desktop-packages] [Bug 1841745] Re: Update to 1.2.0
This bug was fixed in the package libxt - 1:1.2.0-1 --- libxt (1:1.2.0-1) unstable; urgency=medium * New upstream release. (Closes: #962735)(LP: #1841745) * control, rules: Use debhelper-compat, bump to 12. * signing-key: Updated. * control: Bump policy to 4.5.0. * Update vcs urls. * Migrate to dbgsym package. -- Timo Aaltonen Mon, 17 Aug 2020 15:04:51 +0300 ** Changed in: libxt (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxt in Ubuntu. https://bugs.launchpad.net/bugs/1841745 Title: Update to 1.2.0 Status in libxt package in Ubuntu: Fix Released Status in libxt package in Debian: New Bug description: The new version has non trivial change and is not in Debian/Fedora yet To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxt/+bug/1841745/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1875528] Re: Extra frozen / stuck mouse cursor after auto screen lock / sleep
I'm also seeing this problem with 20.04.1 with all the latest patches. I have an AMD GPU (Vega 64), and dual monitors (5k2k and 4k, with display scaling 125%). Interestingly the extra cursor shows up larger than my normal cursor, and doesn't show up in screen shots like the normal cursor. -- 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/1875528 Title: Extra frozen / stuck mouse cursor after auto screen lock / sleep Status in Mutter: Unknown Status in mutter package in Ubuntu: Confirmed Bug description: Expected: After my computer had gone to sleep and I log in I should see only a single active mouse cursor. What happened instead: After my computer had gone to sleep and I logged in I noticed a second frozen/stuck mouse cursor was on screen and was rendered in one place over any active application windows. I recently upgraded to 20.04 from 19.10 but the same issue was occurring in 19.10 as well. Logging out completely then logging back in again removed the extra frozen cursor. lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 apt-cache policy mutter mutter: Installed: 3.36.1-3ubuntu3 Candidate: 3.36.1-3ubuntu3 Version table: *** 3.36.1-3ubuntu3 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.1-3ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Apr 27 19:53:03 2020 InstallationDate: Installed on 2019-03-09 (415 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: mutter UpgradeStatus: Upgraded to focal on 2020-04-28 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1875528/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892510] Re: Refresh rate locked to 24hz only on Ubuntu
Thanks, this worked. ** Changed in: xorg (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1892510 Title: Refresh rate locked to 24hz only on Ubuntu Status in xorg package in Ubuntu: Fix Released Bug description: Ubuntu will not let me run my monitor at 1080p 60Hz, only 24hz, yet other OS like Kali and Windows are capable of running 1080p60 with no problems. I cannot find 60hz in xrandr or display settings, and monitors.xml editing returns nothing. I have tried updating my BIOS, my TV settings, my graphics drivers and everything else.. no luck. Running Ubuntu 20.04 LTS with Budgie. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None Date: Fri Aug 21 15:33:35 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.10, 5.4.0-42-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] [1002:98e4] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Stoney [Radeon R2/R3/R4/R5 Graphics] [17aa:3801] InstallationDate: Installed on 2020-08-06 (14 days ago) InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO INVALID ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: \\boot\vmlinuz-5.4.0-42-generic root=UUID=328af68c-944b-4618-83e7-bcf0237143b9 ro quiet splash vt.handoff=7 initrd=boot\initrd.img-5.4.0-42-generic SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/01/2019 dmi.bios.vendor: LENOVO dmi.bios.version: 1PCN72WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo LV1145 dmi.modalias: dmi:bvnLENOVO:bvr1PCN72WW:bd11/01/2019:svnLENOVO:pnINVALID:pvrLenovoLV1155:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoLV1145: dmi.product.family: IDEAPAD dmi.product.name: INVALID dmi.product.sku: LENOVO_BI_IDEAPAD1P dmi.product.version: Lenovo LV1155 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1892510/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892514] Re: pulseaudio-dlna No longer available in packages Kubuntu 20.04.1
The package was removed in 20.04 because it was not ported to python3 until after the deadline to sync from Debian. ** Package changed: pulseaudio (Ubuntu) => pulseaudio-dlna (Ubuntu) ** Changed in: pulseaudio-dlna (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1892514 Title: pulseaudio-dlna No longer available in packages Kubuntu 20.04.1 Status in pulseaudio-dlna package in Ubuntu: Confirmed Bug description: Hello I was advised to declare a bug for this problem following 'answer' : Missing package pulseaudio-dlna on Kubuntu 20.04 Asked by patked 2 hours ago Hello The package "pulseaudio-dlna' is missing on Kubuntu 20.04. But i can find it on Debian library and it's run ok after install manually Could you make it on standard package Kunbuntu ? Best regards _ information "answer" : pulseaudio-dlna (0.5.3+git20200329-0.1) unstable; urgency=medium * Non-maintainer upload. * New upstream release: The official upstream repository seems to be inactive (https://github.com/masmu/pulseaudio-dlna, last commit from 2017 at the time of writing this), but there is a fork with some recent activity (https://github.com/joecksma/pulseaudio-dlna) and, in particular, a port to Python 3. The upstream tarball for this release is taken from https://github.com/joecksma/ pulseaudio-dlna/tarball/823ad4c67e360d6d57543c1889b9d066194f32b5 (without the whitespace in the URL). The current maintainer of this package seems to have made an error in the last release: There has never been a 0.5.3 upstream release, at least there is no 0.5.3 tag in the official upstream repository. I'm keeping the 0.5.3 for now, however, because this is only a NMU and I don't want to change/break the versioning scheme in an NMU. (Closes: #894806, #937339, #890283, #882998) * Update dependencies to Python 3 versions. * Upgrade to debhelper compat level 12. * Upgrade to Standards-Version 4.5.0. * Update debian/copyright. * Add Vcs-Git and Vcs-Browser fields in debian/control. -- Fabian Wolff Sun, 29 Mar 2020 22:02:05 +0200 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio-dlna/+bug/1892514/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892510] Re: Refresh rate locked to 24hz only on Ubuntu
https://wiki.ubuntu.com/X/Config/Resolution#Adding_undetected_resolutions Have you tried to add the resolution manually with xrandr as explained in the ^link? Example (but make sure you use the numbers cvt gives you and not those below): $ cvt 1920 1080 60 Modeline "1920x1080_60" 173.00 1920 2048 2248 2576 1080 1083 1088 1120 -hsync +vsync $ xrandr --newmode "1920x1080_60" 173.00 1920 2048 2248 2576 1080 1083 1088 1120 -hsync +vsync $ xrandr --addmode HDMI-A-0 1920x1080_60 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1892510 Title: Refresh rate locked to 24hz only on Ubuntu Status in xorg package in Ubuntu: New Bug description: Ubuntu will not let me run my monitor at 1080p 60Hz, only 24hz, yet other OS like Kali and Windows are capable of running 1080p60 with no problems. I cannot find 60hz in xrandr or display settings, and monitors.xml editing returns nothing. I have tried updating my BIOS, my TV settings, my graphics drivers and everything else.. no luck. Running Ubuntu 20.04 LTS with Budgie. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None Date: Fri Aug 21 15:33:35 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.10, 5.4.0-42-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] [1002:98e4] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Stoney [Radeon R2/R3/R4/R5 Graphics] [17aa:3801] InstallationDate: Installed on 2020-08-06 (14 days ago) InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO INVALID ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: \\boot\vmlinuz-5.4.0-42-generic root=UUID=328af68c-944b-4618-83e7-bcf0237143b9 ro quiet splash vt.handoff=7 initrd=boot\initrd.img-5.4.0-42-generic SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/01/2019 dmi.bios.vendor: LENOVO dmi.bios.version: 1PCN72WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo LV1145 dmi.modalias: dmi:bvnLENOVO:bvr1PCN72WW:bd11/01/2019:svnLENOVO:pnINVALID:pvrLenovoLV1155:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoLV1145: dmi.product.family: IDEAPAD dmi.product.name: INVALID dmi.product.sku: LENOVO_BI_IDEAPAD1P dmi.product.version: Lenovo LV1155 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1892510/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892458] Re: Cannot change from one language format to another for example from English US to English UK in the language tab of language-selector-gnome
Good. The reason for this solution is to make it possible to enable fallback languages when your desired language is not fully translated. (Can say that you were not the first who made this mistake.) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/1892458 Title: Cannot change from one language format to another for example from English US to English UK in the language tab of language-selector- gnome Status in language-selector package in Ubuntu: Invalid Bug description: Ubuntu automatically sets the English US language as the system language for the region that I reside in which mainly the English UK language as one of its official languages but not the English US language. When using the Language Support app to attempt to change the system language and regional formats to English UK, the English UK option is greyed out and cannot be selected in the Languages tab. To properly change the language in Ubuntu, I used the Gnome settings to change the language and the regional formats, restarted the shell, and used the Language Support app to apply the regional formats system- wide so that it can apply to the display manager as well. In Xubuntu or any other official Ubuntu flavour that uses the Ubiquity installer for installation and only uses the gnome language selector for language and region formats selection. Changing from one format of a language to another for example from English US to English UK is not possible graphically with the Language Support app alone because the desired language format, for example, English UK is greyed out and not selectable. The attached screenshot illustrates the issue but in this case, attempting to change from English UK to English US by using the language support app alone to attempt the language change. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: language-selector-gnome 0.204 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Aug 21 08:41:06 2020 InstallationDate: Installed on 2020-08-21 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: language-selector UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1892458/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892510] Re: Refresh rate locked to 24hz only on Ubuntu
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1892510 Title: Refresh rate locked to 24hz only on Ubuntu Status in xorg package in Ubuntu: New Bug description: Ubuntu will not let me run my monitor at 1080p 60Hz, only 24hz, yet other OS like Kali and Windows are capable of running 1080p60 with no problems. I cannot find 60hz in xrandr or display settings, and monitors.xml editing returns nothing. I have tried updating my BIOS, my TV settings, my graphics drivers and everything else.. no luck. Running Ubuntu 20.04 LTS with Budgie. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None Date: Fri Aug 21 15:33:35 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.10, 5.4.0-42-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] [1002:98e4] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Stoney [Radeon R2/R3/R4/R5 Graphics] [17aa:3801] InstallationDate: Installed on 2020-08-06 (14 days ago) InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO INVALID ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: \\boot\vmlinuz-5.4.0-42-generic root=UUID=328af68c-944b-4618-83e7-bcf0237143b9 ro quiet splash vt.handoff=7 initrd=boot\initrd.img-5.4.0-42-generic SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/01/2019 dmi.bios.vendor: LENOVO dmi.bios.version: 1PCN72WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo LV1145 dmi.modalias: dmi:bvnLENOVO:bvr1PCN72WW:bd11/01/2019:svnLENOVO:pnINVALID:pvrLenovoLV1155:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoLV1145: dmi.product.family: IDEAPAD dmi.product.name: INVALID dmi.product.sku: LENOVO_BI_IDEAPAD1P dmi.product.version: Lenovo LV1155 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1892510/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892510] [NEW] Refresh rate locked to 24hz only on Ubuntu
You have been subscribed to a public bug: Ubuntu will not let me run my monitor at 1080p 60Hz, only 24hz, yet other OS like Kali and Windows are capable of running 1080p60 with no problems. I cannot find 60hz in xrandr or display settings, and monitors.xml editing returns nothing. I have tried updating my BIOS, my TV settings, my graphics drivers and everything else.. no luck. Running Ubuntu 20.04 LTS with Budgie. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None Date: Fri Aug 21 15:33:35 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.10, 5.4.0-42-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] [1002:98e4] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Stoney [Radeon R2/R3/R4/R5 Graphics] [17aa:3801] InstallationDate: Installed on 2020-08-06 (14 days ago) InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO INVALID ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: \\boot\vmlinuz-5.4.0-42-generic root=UUID=328af68c-944b-4618-83e7-bcf0237143b9 ro quiet splash vt.handoff=7 initrd=boot\initrd.img-5.4.0-42-generic SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/01/2019 dmi.bios.vendor: LENOVO dmi.bios.version: 1PCN72WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo LV1145 dmi.modalias: dmi:bvnLENOVO:bvr1PCN72WW:bd11/01/2019:svnLENOVO:pnINVALID:pvrLenovoLV1155:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoLV1145: dmi.product.family: IDEAPAD dmi.product.name: INVALID dmi.product.sku: LENOVO_BI_IDEAPAD1P dmi.product.version: Lenovo LV1155 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- Refresh rate locked to 24hz only on Ubuntu https://bugs.launchpad.net/bugs/1892510 You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1879968] Re: copy/paste still sometimes fails in LibreOffice on mutter 3.36.2
I just did a right click copy and paste in writer and it works the 1st time, 2nd time it uses the 1st copy not the 2nd. And so on. All said to be fixed in the next version - at this rate in a month or 2. -- 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/1879968 Title: copy/paste still sometimes fails in LibreOffice on mutter 3.36.2 Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Committed Bug description: In Ubuntu 19.10 and 20.04 there was a bug that caused copy and paste operations to fail pretty often: the text that was pasted was not the text that was just copied. See the long discussion at bug #1852183. The bug was recently marked closed, since the package mutter - 3.36.2-1ubuntu1~20.04.1 landed in focal-updates and makes the bug occur much less frequently. Unfortunately the bug still exists, and is not difficult to reproduce. I am running Ubuntu 20.04 and have the new 3.36.2-1ubuntu1~20.04.1 version of mutter. I just opened two LibreOffice Writer windows side by side, and repeatedly selected some text in the left window, copied it, then attempted to paste it into the right window. In my experiment, approximately 1 in every 20 paste operations failed: it did not paste the text that was just copied, but instead the text that was copied before that. Now, an error rate of 1 in 20 may not seem so bad. On the other hand, if you spend all day writing a document and copy and paste dozens of times during the day, then you may hit this bug multiple times per day (as I have been recently), which is a significant annoyance. I tested in LibreOffice since that is where I have seen the bug most often, but I have also seen it occur in other applications as well. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1879968/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892458] Re: Cannot change from one language format to another for example from English US to English UK in the language tab of language-selector-gnome
I attempted to drag a language format to the top before the bug report but nothing happened and attempted to drag again recently but it works as long as the green line is visible at the top before releasing the left mouse button. Marked it as invalid. The Language support app's first impression may confuse new users. Marked it as invalid because I am used to selecting a language instead of dragging the language to the top. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/1892458 Title: Cannot change from one language format to another for example from English US to English UK in the language tab of language-selector- gnome Status in language-selector package in Ubuntu: Invalid Bug description: Ubuntu automatically sets the English US language as the system language for the region that I reside in which mainly the English UK language as one of its official languages but not the English US language. When using the Language Support app to attempt to change the system language and regional formats to English UK, the English UK option is greyed out and cannot be selected in the Languages tab. To properly change the language in Ubuntu, I used the Gnome settings to change the language and the regional formats, restarted the shell, and used the Language Support app to apply the regional formats system- wide so that it can apply to the display manager as well. In Xubuntu or any other official Ubuntu flavour that uses the Ubiquity installer for installation and only uses the gnome language selector for language and region formats selection. Changing from one format of a language to another for example from English US to English UK is not possible graphically with the Language Support app alone because the desired language format, for example, English UK is greyed out and not selectable. The attached screenshot illustrates the issue but in this case, attempting to change from English UK to English US by using the language support app alone to attempt the language change. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: language-selector-gnome 0.204 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Aug 21 08:41:06 2020 InstallationDate: Installed on 2020-08-21 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: language-selector UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1892458/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892458] Re: Cannot change from one language format to another for example from English US to English UK in the language tab of language-selector-gnome
** Changed in: language-selector (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/1892458 Title: Cannot change from one language format to another for example from English US to English UK in the language tab of language-selector- gnome Status in language-selector package in Ubuntu: Invalid Bug description: Ubuntu automatically sets the English US language as the system language for the region that I reside in which mainly the English UK language as one of its official languages but not the English US language. When using the Language Support app to attempt to change the system language and regional formats to English UK, the English UK option is greyed out and cannot be selected in the Languages tab. To properly change the language in Ubuntu, I used the Gnome settings to change the language and the regional formats, restarted the shell, and used the Language Support app to apply the regional formats system- wide so that it can apply to the display manager as well. In Xubuntu or any other official Ubuntu flavour that uses the Ubiquity installer for installation and only uses the gnome language selector for language and region formats selection. Changing from one format of a language to another for example from English US to English UK is not possible graphically with the Language Support app alone because the desired language format, for example, English UK is greyed out and not selectable. The attached screenshot illustrates the issue but in this case, attempting to change from English UK to English US by using the language support app alone to attempt the language change. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: language-selector-gnome 0.204 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Aug 21 08:41:06 2020 InstallationDate: Installed on 2020-08-21 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: language-selector UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1892458/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1885234] Re: package zsys 0.4.6 failed to install/upgrade: installed zsys package post-installation script subprocess returned error exit status 1
This is fixed in 0.4.7. ** Changed in: zsys (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to zsys in Ubuntu. https://bugs.launchpad.net/bugs/1885234 Title: package zsys 0.4.6 failed to install/upgrade: installed zsys package post-installation script subprocess returned error exit status 1 Status in zsys package in Ubuntu: Fix Released Bug description: Occurred during initial apt upgrade after enabling focal-proposed. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: zsys 0.4.6 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Jun 25 21:39:26 2020 ErrorMessage: installed zsys package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-06-07 (18 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_a7b04u@/vmlinuz-5.4.0-33-generic root=ZFS=rpool/ROOT/ubuntu_a7b04u ro quiet splash Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: zfs-initramfs 0.8.3-1ubuntu12.1 zfsutils-linux 0.8.3-1ubuntu12.1 SourcePackage: grub2 Title: package zsys 0.4.6 failed to install/upgrade: installed zsys package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ZFSImportedPools: NAMESIZE ALLOC FREE CKPOINT EXPANDSZ FRAGCAP DEDUPHEALTH ALTROOT rpool 107G 82.4G 24.6G- -55%76% 1.00xONLINE - ZFSListcache-bpool: bpool/boot off on on off on off on off - none bpool/BOOT noneoff on on off on off on off - none bpool/BOOT/ubuntu_a7b04u /boot on on on off on off on off - none To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zsys/+bug/1885234/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892514] [NEW] pulseaudio-dlna No longer available in packages Kubuntu 20.04.1
Public bug reported: Hello I was advised to declare a bug for this problem following 'answer' : Missing package pulseaudio-dlna on Kubuntu 20.04 Asked by patked 2 hours ago Hello The package "pulseaudio-dlna' is missing on Kubuntu 20.04. But i can find it on Debian library and it's run ok after install manually Could you make it on standard package Kunbuntu ? Best regards _ information "answer" : pulseaudio-dlna (0.5.3+git20200329-0.1) unstable; urgency=medium * Non-maintainer upload. * New upstream release: The official upstream repository seems to be inactive (https://github.com/masmu/pulseaudio-dlna, last commit from 2017 at the time of writing this), but there is a fork with some recent activity (https://github.com/joecksma/pulseaudio-dlna) and, in particular, a port to Python 3. The upstream tarball for this release is taken from https://github.com/joecksma/ pulseaudio-dlna/tarball/823ad4c67e360d6d57543c1889b9d066194f32b5 (without the whitespace in the URL). The current maintainer of this package seems to have made an error in the last release: There has never been a 0.5.3 upstream release, at least there is no 0.5.3 tag in the official upstream repository. I'm keeping the 0.5.3 for now, however, because this is only a NMU and I don't want to change/break the versioning scheme in an NMU. (Closes: #894806, #937339, #890283, #882998) * Update dependencies to Python 3 versions. * Upgrade to debhelper compat level 12. * Upgrade to Standards-Version 4.5.0. * Update debian/copyright. * Add Vcs-Git and Vcs-Browser fields in debian/control. -- Fabian Wolff Sun, 29 Mar 2020 22:02:05 +0200 ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1892514 Title: pulseaudio-dlna No longer available in packages Kubuntu 20.04.1 Status in pulseaudio package in Ubuntu: New Bug description: Hello I was advised to declare a bug for this problem following 'answer' : Missing package pulseaudio-dlna on Kubuntu 20.04 Asked by patked 2 hours ago Hello The package "pulseaudio-dlna' is missing on Kubuntu 20.04. But i can find it on Debian library and it's run ok after install manually Could you make it on standard package Kunbuntu ? Best regards _ information "answer" : pulseaudio-dlna (0.5.3+git20200329-0.1) unstable; urgency=medium * Non-maintainer upload. * New upstream release: The official upstream repository seems to be inactive (https://github.com/masmu/pulseaudio-dlna, last commit from 2017 at the time of writing this), but there is a fork with some recent activity (https://github.com/joecksma/pulseaudio-dlna) and, in particular, a port to Python 3. The upstream tarball for this release is taken from https://github.com/joecksma/ pulseaudio-dlna/tarball/823ad4c67e360d6d57543c1889b9d066194f32b5 (without the whitespace in the URL). The current maintainer of this package seems to have made an error in the last release: There has never been a 0.5.3 upstream release, at least there is no 0.5.3 tag in the official upstream repository. I'm keeping the 0.5.3 for now, however, because this is only a NMU and I don't want to change/break the versioning scheme in an NMU. (Closes: #894806, #937339, #890283, #882998) * Update dependencies to Python 3 versions. * Upgrade to debhelper compat level 12. * Upgrade to Standards-Version 4.5.0. * Update debian/copyright. * Add Vcs-Git and Vcs-Browser fields in debian/control. -- Fabian Wolff Sun, 29 Mar 2020 22:02:05 +0200 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1892514/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1885234] Re: package zsys 0.4.6 failed to install/upgrade: installed zsys package post-installation script subprocess returned error exit status 1
Does not sound like a grub issue at all, and there has been no progress on fixing it, so reassigning to zsys and setting back to New ** Package changed: grub2 (Ubuntu) => zsys (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to zsys in Ubuntu. https://bugs.launchpad.net/bugs/1885234 Title: package zsys 0.4.6 failed to install/upgrade: installed zsys package post-installation script subprocess returned error exit status 1 Status in zsys package in Ubuntu: Fix Released Bug description: Occurred during initial apt upgrade after enabling focal-proposed. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: zsys 0.4.6 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Jun 25 21:39:26 2020 ErrorMessage: installed zsys package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-06-07 (18 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_a7b04u@/vmlinuz-5.4.0-33-generic root=ZFS=rpool/ROOT/ubuntu_a7b04u ro quiet splash Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: zfs-initramfs 0.8.3-1ubuntu12.1 zfsutils-linux 0.8.3-1ubuntu12.1 SourcePackage: grub2 Title: package zsys 0.4.6 failed to install/upgrade: installed zsys package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ZFSImportedPools: NAMESIZE ALLOC FREE CKPOINT EXPANDSZ FRAGCAP DEDUPHEALTH ALTROOT rpool 107G 82.4G 24.6G- -55%76% 1.00xONLINE - ZFSListcache-bpool: bpool/boot off on on off on off on off - none bpool/BOOT noneoff on on off on off on off - none bpool/BOOT/ubuntu_a7b04u /boot on on on off on off on off - none To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zsys/+bug/1885234/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1885234] [NEW] package zsys 0.4.6 failed to install/upgrade: installed zsys package post-installation script subprocess returned error exit status 1
You have been subscribed to a public bug: Occurred during initial apt upgrade after enabling focal-proposed. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: zsys 0.4.6 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Jun 25 21:39:26 2020 ErrorMessage: installed zsys package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-06-07 (18 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_a7b04u@/vmlinuz-5.4.0-33-generic root=ZFS=rpool/ROOT/ubuntu_a7b04u ro quiet splash Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: zfs-initramfs 0.8.3-1ubuntu12.1 zfsutils-linux 0.8.3-1ubuntu12.1 SourcePackage: grub2 Title: package zsys 0.4.6 failed to install/upgrade: installed zsys package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ZFSImportedPools: NAMESIZE ALLOC FREE CKPOINT EXPANDSZ FRAGCAP DEDUPHEALTH ALTROOT rpool 107G 82.4G 24.6G- -55%76% 1.00xONLINE - ZFSListcache-bpool: bpool /boot off on on off on off on off - none bpool/BOOT noneoff on on off on off on off - none bpool/BOOT/ubuntu_a7b04u /boot on on on off on off on off - none ** Affects: zsys (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal package-from-proposed -- package zsys 0.4.6 failed to install/upgrade: installed zsys package post-installation script subprocess returned error exit status 1 https://bugs.launchpad.net/bugs/1885234 You received this bug notification because you are a member of Desktop Packages, which is subscribed to zsys in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1888575] Re: Split motd-news config into a new package
There are two things missing for this to be testable: a) the motd-news-config NEW package needs to be accepted b) it needs to be moved into main c) ubuntu-meta needs to be accepted as well (my mistake there, I missed the bug number in d/changelog in the xenial and bionic uploads) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1888575 Title: Split motd-news config into a new package Status in base-files package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: In Progress Status in base-files source package in Xenial: Fix Committed Status in ubuntu-meta source package in Xenial: In Progress Status in base-files source package in Bionic: Fix Committed Status in ubuntu-meta source package in Bionic: In Progress Status in base-files source package in Focal: Fix Committed Status in ubuntu-meta source package in Focal: In Progress Status in base-files source package in Groovy: Fix Released Status in ubuntu-meta source package in Groovy: In Progress Bug description: [Impact] The motd-news script is largely useless for desktop users, as they rarely login via a text console. It makes more sense for server users. We can use package dependencies to have the motd-news script enabled on servers, but disabled on desktops, and still handle upgrades. This is the plan: - move /etc/default/motd-news from base-files into a new binary package (motd-news-config, produced by src:base-files) - have ubuntu-server depend on motd-news-config - have base-files break current ubuntu-server, so that if base-files if upgraded and ubuntu-server is installed, ubuntu-server will also be upgraded to the new version which has the depends on motd-news-config Care must be taken to preserve a changed /etc/default/motd-news when the upgrade installs the new motd-news-config package. For example, on a server that has set ENABLED=0 in /etc/default/motd-news and upgrades to the new base-files and ubuntu-server, and gets the new motd-config- news package, ENABLED=0 must remain set. [Test Case] a) base-files installed, ubuntu-server installed, unmodified /e/d/motd-news apt install base-files - upgrades ubuntu-server - installs motd-news-config - /e/d/motd-news remains, motd-news remains enabled b) base-files installed, ubuntu-server installed, modified /e/d/motd-news apt install base-files - upgrades ubuntu-server - installs motd-news-config - /e/d/motd-news remains with the original modification c) base-files installed, ubuntu-server not installed, unmodified /e/d/motd-news apt install base-files - upgrades base-files - removes /e/d/motd-news - motd-news is disabled d) base-files installed, ubuntu-server not installed, modified /e/d/motd-news apt install base-files - upgrades base-files - /e/d/motd-news gets renamed to backup - motd-news is disabled e) removing motd-news-config will also remove ubuntu-server (since it's a depends, and not a recommends) f) upgrading just ubuntu-server should pull motd-news-config in, and force-upgrade base-files g) Removing motd-news-server leaves /e/d/motd-news around; purging motd-news-server removes the /e/d/motd-news config file h) base-files installed, ubuntu-server installed, removed /e/d/motd-news - apt install base-files - upgrades base-files, upgrades ubuntu-server, installs motd-news-config - /e/d/motd-news is installed with ENABLED=0 i) base-files installed, ubuntu-server NOT installed, removed e/d/motd-news - apt install base-files - base-files is upgraded - no /e/d/motd-news is installed, motd-news remains disabled j) Perform a release upgrade from the previous ubuntu release to the one being tested while having ubuntu-server NOT installed (or use a desktop install). At the end, motd-news should be disabled. Verify with: $ sudo /etc/update-motd.d/50-motd-news --force $ (no output) [Regression Potential] This update is about config file ownership transfer: /e/d/motd-news belonged to base-files, now it belongs to motd-news-config. We tried to handle two important cases here: a) /e/d/motd-news config was changed while it belonged to base-files. For example, an user could have set ENABLED=0. We need to transfer that change to the motd-news-config package when it is installed, otherwise this SRU would jsut re-enabled motd-news. This is handled in d/motd-news-config.postinst's configure case. b) /e/d/motd-news config file was *removed* while it belonged to base-files. In such a case, a normal upgrade of the package (base-files in this example) would not reinstate the file. Much less this upgrade here, which has an explicit rm_conffile maintscript-helper for it. But the motd-news-config package that could be installed in the transaction would place the default config file back, and the default is ENABLED=1. Thus, a
[Desktop-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
** Tags added: originate-from-1892498 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. Status in OEM Priority Project: Triaged Status in gdm3 package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Status in grub2 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Bug description: [ Impact ] In some platforms with specific Nvidia cards, auto-login will fail due to the old vt-handoff patch in grub2. [ Test Case ] 1. Boot ubuntu into desktop environment. 2. Enabled auto login in System->Users 3. Reboot the system [Expected result] System will boot into desktop environment without the login page. [Actual result] System boots to login page, and can't login to desktop environment with the correct password. [ Regression potential ] Low, the patch just removes vt.handoff part in grub2 package, and I can't find any regression in several runs of stress tests. PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1845801 --- I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 19:55:42 2019 DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2019-09-14 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7A67 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago) dmi.bios.date: 01/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: Default string dmi.board.name: H270I GAMING PRO AC (MS-7A67) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7A67 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-a
[Desktop-packages] [Bug 1705593] Re: Drag language items fails on 17.10
Tried this with Ubuntu on Wayland on 20.04. The issue seems to be gone. Closing. ** Changed in: language-selector (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/1705593 Title: Drag language items fails on 17.10 Status in language-selector package in Ubuntu: Fix Released Bug description: On 17.10 I can't drag a language item upwards to make it the current display language. The UI works partially, i.e. I can drag the top item downwards, and I can also drag the "English" item downwards, so if you are patient enough it's possible to work around the problem. This issue is present with GNOME shell. If I install unity-session and switch to Unity, the language-selector-gnome UI works as usual. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1705593/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1879968] Re: copy/paste still sometimes fails in LibreOffice on mutter 3.36.2
Ubuntu 20.04, mutter 3.36.4 I did some testing with libreoffice (calc, writer) and it seems that the bug is solved for me (I didn't try wine). -- 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/1879968 Title: copy/paste still sometimes fails in LibreOffice on mutter 3.36.2 Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Committed Bug description: In Ubuntu 19.10 and 20.04 there was a bug that caused copy and paste operations to fail pretty often: the text that was pasted was not the text that was just copied. See the long discussion at bug #1852183. The bug was recently marked closed, since the package mutter - 3.36.2-1ubuntu1~20.04.1 landed in focal-updates and makes the bug occur much less frequently. Unfortunately the bug still exists, and is not difficult to reproduce. I am running Ubuntu 20.04 and have the new 3.36.2-1ubuntu1~20.04.1 version of mutter. I just opened two LibreOffice Writer windows side by side, and repeatedly selected some text in the left window, copied it, then attempted to paste it into the right window. In my experiment, approximately 1 in every 20 paste operations failed: it did not paste the text that was just copied, but instead the text that was copied before that. Now, an error rate of 1 in 20 may not seem so bad. On the other hand, if you spend all day writing a document and copy and paste dozens of times during the day, then you may hit this bug multiple times per day (as I have been recently), which is a significant annoyance. I tested in LibreOffice since that is where I have seen the bug most often, but I have also seen it occur in other applications as well. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1879968/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892458] Re: Cannot change from one language format to another for example from English US to English UK in the language tab of language-selector-gnome
Thanks for your report. Please note that you are supposed to drag the language you want to use to the top of the list, not just click on it. Can you try that and let us know if it works. ** Changed in: language-selector (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/1892458 Title: Cannot change from one language format to another for example from English US to English UK in the language tab of language-selector- gnome Status in language-selector package in Ubuntu: Incomplete Bug description: Ubuntu automatically sets the English US language as the system language for the region that I reside in which mainly the English UK language as one of its official languages but not the English US language. When using the Language Support app to attempt to change the system language and regional formats to English UK, the English UK option is greyed out and cannot be selected in the Languages tab. To properly change the language in Ubuntu, I used the Gnome settings to change the language and the regional formats, restarted the shell, and used the Language Support app to apply the regional formats system- wide so that it can apply to the display manager as well. In Xubuntu or any other official Ubuntu flavour that uses the Ubiquity installer for installation and only uses the gnome language selector for language and region formats selection. Changing from one format of a language to another for example from English US to English UK is not possible graphically with the Language Support app alone because the desired language format, for example, English UK is greyed out and not selectable. The attached screenshot illustrates the issue but in this case, attempting to change from English UK to English US by using the language support app alone to attempt the language change. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: language-selector-gnome 0.204 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Aug 21 08:41:06 2020 InstallationDate: Installed on 2020-08-21 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: language-selector UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1892458/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892439] Re: [Lenovo ThinkPad T410s, Intel IbexPeak HDMI, Digital Out, HDMI] No sound at all
[4.722425] snd_hda_codec_hdmi hdaudioC0D3: No i915 binding for Intel HDMI/DP codec [4.722861] hdaudio hdaudioC0D3: Unable to bind the codec ** Summary changed: - [2901A3U, Intel IbexPeak HDMI, Digital Out, HDMI] No sound at all + [Lenovo ThinkPad T410s, Intel IbexPeak HDMI, Digital Out, HDMI] No sound at all ** Changed in: alsa-driver (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1892439 Title: [Lenovo ThinkPad T410s, Intel IbexPeak HDMI, Digital Out, HDMI] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: ThinkPad T410s. No audio from DisplayPort. Can't even select it as the audio source. Video works fine ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: voorhees857 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Aug 20 21:46:38 2020 InstallationDate: Installed on 2020-08-04 (16 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: voorhees857 F pulseaudio Symptom_Jack: Digital Out, HDMI Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [2901A3U, Intel IbexPeak HDMI, Digital Out, HDMI] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/07/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6UET38WW (1.16 ) dmi.board.name: 2901A3U dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6UET38WW(1.16):bd06/07/2010:svnLENOVO:pn2901A3U:pvrThinkPadT410s:rvnLENOVO:rn2901A3U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T410s dmi.product.name: 2901A3U dmi.product.version: ThinkPad T410s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1892439/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1888575] Please test proposed package
Hello Andreas, or anyone else affected, Accepted base-files into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/base- files/10.1ubuntu2.10 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: base-files (Ubuntu Xenial) Status: In Progress => Fix Committed ** Tags added: verification-needed-xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1888575 Title: Split motd-news config into a new package Status in base-files package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: In Progress Status in base-files source package in Xenial: Fix Committed Status in ubuntu-meta source package in Xenial: In Progress Status in base-files source package in Bionic: Fix Committed Status in ubuntu-meta source package in Bionic: In Progress Status in base-files source package in Focal: Fix Committed Status in ubuntu-meta source package in Focal: In Progress Status in base-files source package in Groovy: Fix Released Status in ubuntu-meta source package in Groovy: In Progress Bug description: [Impact] The motd-news script is largely useless for desktop users, as they rarely login via a text console. It makes more sense for server users. We can use package dependencies to have the motd-news script enabled on servers, but disabled on desktops, and still handle upgrades. This is the plan: - move /etc/default/motd-news from base-files into a new binary package (motd-news-config, produced by src:base-files) - have ubuntu-server depend on motd-news-config - have base-files break current ubuntu-server, so that if base-files if upgraded and ubuntu-server is installed, ubuntu-server will also be upgraded to the new version which has the depends on motd-news-config Care must be taken to preserve a changed /etc/default/motd-news when the upgrade installs the new motd-news-config package. For example, on a server that has set ENABLED=0 in /etc/default/motd-news and upgrades to the new base-files and ubuntu-server, and gets the new motd-config- news package, ENABLED=0 must remain set. [Test Case] a) base-files installed, ubuntu-server installed, unmodified /e/d/motd-news apt install base-files - upgrades ubuntu-server - installs motd-news-config - /e/d/motd-news remains, motd-news remains enabled b) base-files installed, ubuntu-server installed, modified /e/d/motd-news apt install base-files - upgrades ubuntu-server - installs motd-news-config - /e/d/motd-news remains with the original modification c) base-files installed, ubuntu-server not installed, unmodified /e/d/motd-news apt install base-files - upgrades base-files - removes /e/d/motd-news - motd-news is disabled d) base-files installed, ubuntu-server not installed, modified /e/d/motd-news apt install base-files - upgrades base-files - /e/d/motd-news gets renamed to backup - motd-news is disabled e) removing motd-news-config will also remove ubuntu-server (since it's a depends, and not a recommends) f) upgrading just ubuntu-server should pull motd-news-config in, and force-upgrade base-files g) Removing motd-news-server leaves /e/d/motd-news around; purging motd-news-server removes the /e/d/motd-news config file h) base-files installed, ubuntu-server installed, removed /e/d/motd-news - apt install base-files - upgrades base-files, upgrades ubuntu-server, installs motd-news-config - /e/d/motd-news is installed with ENABLED=0 i) base-files installed, ubuntu-server NOT installed, removed e/d/motd-news - apt install base-files - base-files is upgraded - no /e/d/motd-news is installed, motd-news remains disabled j) Perform a release upgrade from the previous ubuntu release to the one being tested while having ubuntu-server NOT installed (o
[Desktop-packages] [Bug 1888575] Please test proposed package
Hello Andreas, or anyone else affected, Accepted base-files into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/base- files/9.4ubuntu4.13 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-xenial. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1888575 Title: Split motd-news config into a new package Status in base-files package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: In Progress Status in base-files source package in Xenial: Fix Committed Status in ubuntu-meta source package in Xenial: In Progress Status in base-files source package in Bionic: Fix Committed Status in ubuntu-meta source package in Bionic: In Progress Status in base-files source package in Focal: Fix Committed Status in ubuntu-meta source package in Focal: In Progress Status in base-files source package in Groovy: Fix Released Status in ubuntu-meta source package in Groovy: In Progress Bug description: [Impact] The motd-news script is largely useless for desktop users, as they rarely login via a text console. It makes more sense for server users. We can use package dependencies to have the motd-news script enabled on servers, but disabled on desktops, and still handle upgrades. This is the plan: - move /etc/default/motd-news from base-files into a new binary package (motd-news-config, produced by src:base-files) - have ubuntu-server depend on motd-news-config - have base-files break current ubuntu-server, so that if base-files if upgraded and ubuntu-server is installed, ubuntu-server will also be upgraded to the new version which has the depends on motd-news-config Care must be taken to preserve a changed /etc/default/motd-news when the upgrade installs the new motd-news-config package. For example, on a server that has set ENABLED=0 in /etc/default/motd-news and upgrades to the new base-files and ubuntu-server, and gets the new motd-config- news package, ENABLED=0 must remain set. [Test Case] a) base-files installed, ubuntu-server installed, unmodified /e/d/motd-news apt install base-files - upgrades ubuntu-server - installs motd-news-config - /e/d/motd-news remains, motd-news remains enabled b) base-files installed, ubuntu-server installed, modified /e/d/motd-news apt install base-files - upgrades ubuntu-server - installs motd-news-config - /e/d/motd-news remains with the original modification c) base-files installed, ubuntu-server not installed, unmodified /e/d/motd-news apt install base-files - upgrades base-files - removes /e/d/motd-news - motd-news is disabled d) base-files installed, ubuntu-server not installed, modified /e/d/motd-news apt install base-files - upgrades base-files - /e/d/motd-news gets renamed to backup - motd-news is disabled e) removing motd-news-config will also remove ubuntu-server (since it's a depends, and not a recommends) f) upgrading just ubuntu-server should pull motd-news-config in, and force-upgrade base-files g) Removing motd-news-server leaves /e/d/motd-news around; purging motd-news-server removes the /e/d/motd-news config file h) base-files installed, ubuntu-server installed, removed /e/d/motd-news - apt install base-files - upgrades base-files, upgrades ubuntu-server, installs motd-news-config - /e/d/motd-news is installed with ENABLED=0 i) base-files installed, ubuntu-server NOT installed, removed e/d/motd-news - apt install base-files - base-files is upgraded - no /e/d/motd-news is installed, motd-news remains disabled j) Perform a release upgrade from the previous ubuntu release to the one being tested while having ubuntu-server NOT installed (or use a desktop install). At the end, motd-news should be disabled. Verify with: $ sudo /etc/update-motd.d/50-motd-news --fo
[Desktop-packages] [Bug 1888575] Re: Split motd-news config into a new package
Hello Andreas, or anyone else affected, Accepted base-files into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/base- files/11ubuntu5.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: base-files (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-focal ** Changed in: base-files (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1888575 Title: Split motd-news config into a new package Status in base-files package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: In Progress Status in base-files source package in Xenial: Fix Committed Status in ubuntu-meta source package in Xenial: In Progress Status in base-files source package in Bionic: Fix Committed Status in ubuntu-meta source package in Bionic: In Progress Status in base-files source package in Focal: Fix Committed Status in ubuntu-meta source package in Focal: In Progress Status in base-files source package in Groovy: Fix Released Status in ubuntu-meta source package in Groovy: In Progress Bug description: [Impact] The motd-news script is largely useless for desktop users, as they rarely login via a text console. It makes more sense for server users. We can use package dependencies to have the motd-news script enabled on servers, but disabled on desktops, and still handle upgrades. This is the plan: - move /etc/default/motd-news from base-files into a new binary package (motd-news-config, produced by src:base-files) - have ubuntu-server depend on motd-news-config - have base-files break current ubuntu-server, so that if base-files if upgraded and ubuntu-server is installed, ubuntu-server will also be upgraded to the new version which has the depends on motd-news-config Care must be taken to preserve a changed /etc/default/motd-news when the upgrade installs the new motd-news-config package. For example, on a server that has set ENABLED=0 in /etc/default/motd-news and upgrades to the new base-files and ubuntu-server, and gets the new motd-config- news package, ENABLED=0 must remain set. [Test Case] a) base-files installed, ubuntu-server installed, unmodified /e/d/motd-news apt install base-files - upgrades ubuntu-server - installs motd-news-config - /e/d/motd-news remains, motd-news remains enabled b) base-files installed, ubuntu-server installed, modified /e/d/motd-news apt install base-files - upgrades ubuntu-server - installs motd-news-config - /e/d/motd-news remains with the original modification c) base-files installed, ubuntu-server not installed, unmodified /e/d/motd-news apt install base-files - upgrades base-files - removes /e/d/motd-news - motd-news is disabled d) base-files installed, ubuntu-server not installed, modified /e/d/motd-news apt install base-files - upgrades base-files - /e/d/motd-news gets renamed to backup - motd-news is disabled e) removing motd-news-config will also remove ubuntu-server (since it's a depends, and not a recommends) f) upgrading just ubuntu-server should pull motd-news-config in, and force-upgrade base-files g) Removing motd-news-server leaves /e/d/motd-news around; purging motd-news-server removes the /e/d/motd-news config file h) base-files installed, ubuntu-server installed, removed /e/d/motd-news - apt install base-files - upgrades base-files, upgrades ubuntu-server, installs motd-news-config - /e/d/motd-news is installed with ENABLED=0 i) base-files installed, ubuntu-server NOT installed, removed e/d/motd-news - apt install base-files - base-files is upgraded - no /e/d/motd-news is installed, motd-news remains di
[Desktop-packages] [Bug 1892419] Re: Displayport is not working
Here is the file ** Attachment added: "drm-status.txt" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1892419/+attachment/5403413/+files/drm-status.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1892419 Title: Displayport is not working Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: Can't get dysplayport to recognize. It is not the cable since I tested it on another PC ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Aug 20 16:54:01 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 4th Gen Core Processor Integrated Graphics Controller [103c:1993] InstallationDate: Installed on 2020-08-20 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Hewlett-Packard HP ProBook 650 G1 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=adbe32f1-2fcd-4bb7-b8d0-7e8db010d123 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2015 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L77 Ver. 01.32 dmi.board.name: 1993 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 16.3C dmi.chassis.asset.tag: 5CG5203T6Z dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL77Ver.01.32:bd03/25/2015:svnHewlett-Packard:pnHPProBook650G1:pvrA3009DD10303:rvnHewlett-Packard:rn1993:rvrKBCVersion16.3C:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP ProBook 650 G1 dmi.product.sku: K4L00UT#ABA dmi.product.version: A3009DD10303 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1892419/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892484] Re: Screen Sharing option is missing in 20.10, but exists in 20.04.
And now I can't proceed because it won't launch at all (bug 1892486). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1892484 Title: Screen Sharing option is missing in 20.10, but exists in 20.04. Status in gnome-control-center package in Ubuntu: New Bug description: Screen Sharing option is missing in 20.10, but exists in 20.04. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-control-center 1:3.37.90-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu44 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Aug 21 18:08:23 2020 InstallationDate: Installed on 2020-07-16 (36 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200507) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1892484/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892484] [NEW] Screen Sharing option is missing in 20.10, but exists in 20.04.
Public bug reported: Screen Sharing option is missing in 20.10, but exists in 20.04. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-control-center 1:3.37.90-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu44 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Aug 21 18:08:23 2020 InstallationDate: Installed on 2020-07-16 (36 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200507) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1892484 Title: Screen Sharing option is missing in 20.10, but exists in 20.04. Status in gnome-control-center package in Ubuntu: New Bug description: Screen Sharing option is missing in 20.10, but exists in 20.04. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-control-center 1:3.37.90-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu44 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Aug 21 18:08:23 2020 InstallationDate: Installed on 2020-07-16 (36 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200507) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1892484/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892484] Re: Screen Sharing option is missing in 20.10, but exists in 20.04.
I've never actually used it before so I don't know all the steps. But the change in the GUI seems suspicious. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1892484 Title: Screen Sharing option is missing in 20.10, but exists in 20.04. Status in gnome-control-center package in Ubuntu: New Bug description: Screen Sharing option is missing in 20.10, but exists in 20.04. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-control-center 1:3.37.90-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu44 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Aug 21 18:08:23 2020 InstallationDate: Installed on 2020-07-16 (36 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200507) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1892484/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892440] Re: [focal] [nvidia] Mutter 3.36.4-0ubuntu0.20.04.2 small text in Ubuntu 20.04 with nvidia cards
Marco Trevisan will save us! Grazie mille! ;) -- 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/1892440 Title: [focal] [nvidia] Mutter 3.36.4-0ubuntu0.20.04.2 small text in Ubuntu 20.04 with nvidia cards Status in mutter package in Ubuntu: Confirmed Bug description: The package mutter version (3.36.4-0ubuntu0.20.04.2) for Ubuntu 20.04 causes small text in GNOME Shell menu with NVIDIA cards. With a previous version (3.36.4-0ubuntu0.20.04.1) all works fine. The problem is after update to the (3.36.4-0ubuntu0.20.04.2). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-18 (2 days ago) InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" (20200815) NonfreeKernelModules: nvidia_modeset nvidia Package: mutter 3.36.4-0ubuntu0.20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-15T17:44:36 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892440] Re: [focal] [nvidia] Mutter 3.36.4-0ubuntu0.20.04.2 small text in Ubuntu 20.04 with nvidia cards
** Changed in: mutter (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- 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/1892440 Title: [focal] [nvidia] Mutter 3.36.4-0ubuntu0.20.04.2 small text in Ubuntu 20.04 with nvidia cards Status in mutter package in Ubuntu: Confirmed Bug description: The package mutter version (3.36.4-0ubuntu0.20.04.2) for Ubuntu 20.04 causes small text in GNOME Shell menu with NVIDIA cards. With a previous version (3.36.4-0ubuntu0.20.04.1) all works fine. The problem is after update to the (3.36.4-0ubuntu0.20.04.2). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-18 (2 days ago) InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" (20200815) NonfreeKernelModules: nvidia_modeset nvidia Package: mutter 3.36.4-0ubuntu0.20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-15T17:44:36 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1864778] Re: Intel Drivers Artifacts after Mesa-Dev Update
I have the same issue on Thinkpad X250 on 20.04 with the following config: ``` Section "Device" Identifier "Intel Graphics" Driver "intel" Option "AccelMethod" "uxa" Option "TearFree" "true" EndSection ``` resulting in being unable to use plasma wayland sessions, random system freezes and strong flickering in sddm. purging `xserver-xorg-video- intel` solved the issue for me -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1864778 Title: Intel Drivers Artifacts after Mesa-Dev Update Status in xserver-xorg-video-intel package in Ubuntu: Confirmed Bug description: After the update from the 20.04 LTS fresh live image from 19.3.3-1ubuntu1 to 20.0.0-1ubuntu1 mesa I get serious artifacts on startup when using the intel driver instead of modesetting. These artifacts go away when I enable Option AccelMethod "uxa" but persist if the default, "sna" or the other modes are used "none", "off", "blt". These pixels appear throughout the experience of using Ubuntu and generate in sporadic places. The font also looks completely broken. I've never had this issue before with the Intel drivers. I have Skylake HD 530. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1864778/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1838152] Re: gnome-shell freezes on notification arrival (fixed upstream)
Yes, I wanted to keep the changes minimal initially, as the reporter mentioned that that commit was enough, but I can reiterate with the whole change that is in fact complete with the whole set. -- 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/1838152 Title: gnome-shell freezes on notification arrival (fixed upstream) Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: In Progress Status in gnome-shell source package in Disco: Fix Released Status in gnome-shell source package in Eoan: Fix Released Bug description: [ Description ] Sometimes certain notifications make the desktop unresponsive for a few seconds and then gnome-shell crashes and all extensions are reloaded. [ Test case ] Install gsconnect extension in gnome-shell: https://extensions.gnome.org/extension/1319/gsconnect/ - Start Up system - first Notification from connected device - Hangs for about 20 sec + This should not happen [ Regression potential ] Persistent state is not kept, although the patch is living upstream for many cycles already, so it's pretty safe. - I have found an upstream bug with a patch, but it's probably not in the Ubuntu's package. I thought of creating an issue in case it is something not known. https://gitlab.gnome.org/GNOME/gnome-shell/issues/470 https://gitlab.gnome.org/GNOME/gnome- shell/commit/86a00b6872375a266449beee1ea6d5e94f1ebbcb In my case it happens only with the notifications of gsconnect and maybe android studio. I have reproduced the problem in gsconnect in case it helps. https://github.com/andyholmes/gnome-shell-extension-gsconnect/issues/549 the error is: lug 27 19:55:56 ghv gnome-shell[4071]: Object Meta.Background (0x55ce6b4cf300), has been already deallocated - impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Ubuntu 18.04 gnome-shell Version: 3.28.4-0ubuntu18.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1838152/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872802] Re: Resizing any window will randomly result in graphics corruption for a fraction of a second
** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872802/+attachment/5403355/+files/journal.txt -- 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/1872802 Title: Resizing any window will randomly result in graphics corruption for a fraction of a second Status in gnome-shell package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: When resizing any window in any direction the window can appear glitchy as presented in the screenshot. This glitchy appearance is restored immediately. The issue seems to be seen less often when the CPU is utilized more heavily, as when I recorded the screen with OBS to grab the screenshot. The screenshots shows gnome-system-monitor, but I could trigger it with Firefox, gnome-terminal and others. No such issues were experienced with previously installed Ubuntu Mate or Windows 10. Graphics: Mesa Intel® HD Graphics 620 (KBL GT2) on the Intel® Core™ i5-7200U CPU @ 2.50GHz × 4 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 14 20:45:47 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872802/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872802] Re: Resizing any window will randomly result in graphics corruption for a fraction of a second
I just recently switched to PopOS and it has the same issue in gnome, if that helps. -- 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/1872802 Title: Resizing any window will randomly result in graphics corruption for a fraction of a second Status in gnome-shell package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: When resizing any window in any direction the window can appear glitchy as presented in the screenshot. This glitchy appearance is restored immediately. The issue seems to be seen less often when the CPU is utilized more heavily, as when I recorded the screen with OBS to grab the screenshot. The screenshots shows gnome-system-monitor, but I could trigger it with Firefox, gnome-terminal and others. No such issues were experienced with previously installed Ubuntu Mate or Windows 10. Graphics: Mesa Intel® HD Graphics 620 (KBL GT2) on the Intel® Core™ i5-7200U CPU @ 2.50GHz × 4 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 14 20:45:47 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872802/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872802] Re: Resizing any window will randomly result in graphics corruption for a fraction of a second
** Attachment added: "lspcik.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872802/+attachment/5403356/+files/lspcik.txt -- 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/1872802 Title: Resizing any window will randomly result in graphics corruption for a fraction of a second Status in gnome-shell package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: When resizing any window in any direction the window can appear glitchy as presented in the screenshot. This glitchy appearance is restored immediately. The issue seems to be seen less often when the CPU is utilized more heavily, as when I recorded the screen with OBS to grab the screenshot. The screenshots shows gnome-system-monitor, but I could trigger it with Firefox, gnome-terminal and others. No such issues were experienced with previously installed Ubuntu Mate or Windows 10. Graphics: Mesa Intel® HD Graphics 620 (KBL GT2) on the Intel® Core™ i5-7200U CPU @ 2.50GHz × 4 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 14 20:45:47 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872802/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892440] Re: [focal] [nvidia] Mutter 3.36.4-0ubuntu0.20.04.2 small text in Ubuntu 20.04 with nvidia cards
Cristiano Nunes (cfgnunes) wrote: "I have two computers here, the bug occur with only the computer with NVIDIA card." I have same issue on intel laptop with intel graphics. But I not use gdm, I use lightdm and x11 session. Maybe using gdm hides this issue on non-nvidia as gdm starts in wayland mode and then smoothly starts gnome shell. But with nvidia gdm (or lightdm on intel in my case) starts with x11 mode and then start separate ubuntu x11 session. -- 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/1892440 Title: [focal] [nvidia] Mutter 3.36.4-0ubuntu0.20.04.2 small text in Ubuntu 20.04 with nvidia cards Status in mutter package in Ubuntu: Confirmed Bug description: The package mutter version (3.36.4-0ubuntu0.20.04.2) for Ubuntu 20.04 causes small text in GNOME Shell menu with NVIDIA cards. With a previous version (3.36.4-0ubuntu0.20.04.1) all works fine. The problem is after update to the (3.36.4-0ubuntu0.20.04.2). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-18 (2 days ago) InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" (20200815) NonfreeKernelModules: nvidia_modeset nvidia Package: mutter 3.36.4-0ubuntu0.20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-15T17:44:36 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892440] Re: [focal] [nvidia] Mutter 3.36.4-0ubuntu0.20.04.2 small text in Ubuntu 20.04 with nvidia cards
Not only nvidia, I have this issue on intel laptop. See my comment here - https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1887998/comments/10 -- 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/1892440 Title: [focal] [nvidia] Mutter 3.36.4-0ubuntu0.20.04.2 small text in Ubuntu 20.04 with nvidia cards Status in mutter package in Ubuntu: Confirmed Bug description: The package mutter version (3.36.4-0ubuntu0.20.04.2) for Ubuntu 20.04 causes small text in GNOME Shell menu with NVIDIA cards. With a previous version (3.36.4-0ubuntu0.20.04.1) all works fine. The problem is after update to the (3.36.4-0ubuntu0.20.04.2). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-18 (2 days ago) InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" (20200815) NonfreeKernelModules: nvidia_modeset nvidia Package: mutter 3.36.4-0ubuntu0.20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-15T17:44:36 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887998] Re: Update to 3.36.4 and SRU it
^^^ Please use bug 1892440 to discuss that. Not here. -- 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/1887998 Title: Update to 3.36.4 and SRU it Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: Fix Released Bug description: [ Impact ] That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/mutter/-/commits/3.36.4 [ Test case ] The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME GNOME Shell and its components should continue working [ Regression potential ] There have been fixes in X11 screencasting and touch-interaction, so ensure there are no problems with those. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1887998/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
