date:20231027

[Desktop-packages] [Bug 1858199] Re: bugs in libvdpau_radeonsi.so and amdgpu(or radeon) driver freeze the system

2023-10-27 Thread Launchpad Bug Tracker

[Expired for mesa (Ubuntu) because there has been no activity for 60
days.]

** Changed in: mesa (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1858199

Title:
  bugs in libvdpau_radeonsi.so  and amdgpu(or radeon) driver  freeze the
  system

Status in mesa package in Ubuntu:
  Expired

Bug description:
  1. In 4.15 kernel serires ,vlc or mpv  video player  with  hardware
  acceleration  output   will freeze  the system  in minutes ,the
  desktop screen  display content was frozen  ,but  sometime   the audio
  will continue to play for about 10 seconds  to one miniute,then the
  system dead。I have to  reset the machine to reboot. When upgrade to
  5.3.24 kernel,amdgpu  still hanged immediately,but play video through
  vdpau  in radeon driver the system will no hang immediately,the
  freqency of hanging  is  about serveral  times a day。  some times web
  browser in virtualbox guest  randomly hangs the system。

  2. installing  amdgpu-pro driver  download from amd official site
  (version of  18.40-697810,18.50-756341,19.10-785425,19.30-934563) are
  all the same problem with above.

  3. remove   libvdpau_radeonsi.so.1.0.0  in the system   from  ubuntu
  or installed  in /opt/amdgpu by amdgpu-pro driver  solved the problem
  .   the system  has never  been freezing for several weeks ,but the
  problem happened again  when I  restore the libvdpau_radeonsi.so file。

  4.When use amdgpu driver  the vlc output sound  via  display output port 
(through an active  hdmi adaptor to hdmi monitor) was glitches ,the sound seem 
missing or dropped in every 2~3 seconds，but when use radeon driver  the sound 
was normal.the audio problem is the same with 4.15 kernel when using kernel 
5.3.24. But  mplayer sound  is always  good ,testing with  audio output  of  
pulseaduio  and alsa ,the kernel driver only affected the sound of  vlc (tested 
with all available audio output ),the other applications was normal.
   
  5. Test with the ubuntu 19.10 live image desktop  is the same problem。

  6. My system  have four  monitors,graphics card is R7 360 ,recognized as 
(from lspci) :
  6.02:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Cape Verde PRO [Radeon HD 7750/8740 / R7 250E].
  infomation from uname -a :
  Linux smzhou-desktop 5.3.0-24-lowlatency #26~18.04.2-Ubuntu SMP PREEMPT Tue 
Nov 26 14:39:35 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1858199/+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 1835315] Re: Vulkan funcionality broken when mesa is compiled with LLVM 8 in some programs

2023-10-27 Thread Launchpad Bug Tracker

[Expired for mesa (Ubuntu) because there has been no activity for 60
days.]

** Changed in: mesa (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1835315

Title:
  Vulkan funcionality broken when mesa is compiled with LLVM 8 in some
  programs

Status in mesa package in Ubuntu:
  Expired

Bug description:
  Ubuntu version: 18.04.2 LTS

  Mesa version: 19.0.2
  Mesa-vulkan-driver version: 19.0.2, POLARIS10, DRM 3.27.0, 5.0.0-20-generic, 
LLVM 8.0.0)
  Video card: AMD RX 580 8GB, 

  There is an issue when the Vulkan mesa RADV drivers are compiled with
  LLVM 8, due to an LLVM 8 bug, resulting in no visual output in some
  programs using the RADV Vulkan backend

  Upgrading to a mesa build compiled with LLVM 9, or reverting back to
  the bionic version from bionic-updates (which uses LLVM 6) fixes the
  problem.

  Using the AMDVLK vulkan driver workarounds the problem too.

  The program I have personally tested is RPCS3


  I could put additional info about the LLVM bug but at this moment I do
  not have the upstream reference

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1835315/+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 1873562] Re: package libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 failed to install/upgrade: unable to make backup link of './usr/lib/i386-linux-gnu/dri/kms_swrast_dri.so' before instal

2023-10-27 Thread Launchpad Bug Tracker

[Expired for mesa (Ubuntu) because there has been no activity for 60
days.]

** Changed in: mesa (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1873562

Title:
  package libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 failed to install/upgrade:
  unable to make backup link of './usr/lib/i386-linux-
  gnu/dri/kms_swrast_dri.so' before installing new version: Input/output
  error

Status in mesa package in Ubuntu:
  Expired

Bug description:
  After running

  $ sudo apt full-upgrade

  Could be contributing factor to Chromium crashing tabs randomly.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17
  Uname: Linux 4.15.0-20-lowlatency i686
  NonfreeKernelModules: overlay
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: i386
  CasperVersion: 1.394
  CompositorRunning: None
  Date: Sat Apr 18 03:59:22 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ErrorMessage: unable to make backup link of 
'./usr/lib/i386-linux-gnu/dri/kms_swrast_dri.so' before installing new version: 
Input/output error
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05cb]
  LiveMediaBuild: Ubuntu-Studio 18.04 LTS "Bionic Beaver" - Release i386 
(20180426)
  MachineType: Dell Inc. Latitude E7440
  ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true 
file=/cdrom/preseed/ubuntustudio.seed boot=casper initrd=/casper/initrd.lz 
quiet splash --- BOOT_IMAGE=/casper/vmlinuz
  Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.3
   apt  1.6.1
  SourcePackage: mesa
  Title: package libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 failed to install/upgrade: 
unable to make backup link of './usr/lib/i386-linux-gnu/dri/kms_swrast_dri.so' 
before installing new version: Input/output error
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/01/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 03HFCG
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd05/01/2014:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn03HFCG:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7440
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1873562/+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 1889052] Re: 20.10: vlc crashes with seg fault when a video should be played

2023-10-27 Thread Launchpad Bug Tracker

[Expired for mesa (Ubuntu) because there has been no activity for 60
days.]

** Changed in: mesa (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1889052

Title:
  20.10: vlc crashes with seg fault when a video should be played

Status in mesa package in Ubuntu:
  Expired

Bug description:
  When I try to play "any" video vlc crashes with a seg fault.

  Tested: 
  - mkv + h.264
  - mp4 + h.264
  - wmv

  Maybe it's a good idea to choose a different vlc release for the
  repos?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: vlc 3.0.9.2-1
  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.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Mon Jul 27 17:27:42 2020
  SourcePackage: vlc
  UpgradeStatus: Upgraded to focal on 2020-07-24 (3 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1889052/+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 1892985] Re: package libegl-mesa0 20.0.8-0ubuntu1~18.04.1 [modified: usr/share/glvnd/egl_vendor.d/50_mesa.json] failed to install/upgrade: trying to overwrite shared '/usr/shar

2023-10-27 Thread Launchpad Bug Tracker

[Expired for mesa (Ubuntu) because there has been no activity for 60
days.]

** Changed in: mesa (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1892985

Title:
  package libegl-mesa0 20.0.8-0ubuntu1~18.04.1 [modified:
  usr/share/glvnd/egl_vendor.d/50_mesa.json] failed to install/upgrade:
  trying to overwrite shared
  '/usr/share/glvnd/egl_vendor.d/50_mesa.json', which is different from
  other instances of package libegl-mesa0:armhf

Status in mesa package in Ubuntu:
  Expired

Bug description:
  Keeps reporting when I teamviewer and service also crashses

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libegl-mesa0 20.0.8-0ubuntu1~18.04.1 [modified: 
usr/share/glvnd/egl_vendor.d/50_mesa.json]
  Uname: Linux 4.9.140-tegra aarch64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.16
  Architecture: arm64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Aug 26 03:19:43 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ErrorMessage: trying to overwrite shared 
'/usr/share/glvnd/egl_vendor.d/50_mesa.json', which is different from other 
instances of package libegl-mesa0:armhf
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   
  ProcKernelCmdLine: root=/dev/mmcblk0p1 rw rootwait rootfstype=ext4 
console=ttyTCU0,115200n8 console=tty0 fbcon=map:0 net.ifnames=0 rootfstype=ext4 
video=tegrafb no_console_suspend=1 earlycon=tegra_comb_uart,mmio32,0x0c168000 
gpt tegra_fbmem=0x80@0xa069c000 lut_mem=0x2008@0xa0697000 
usbcore.old_scheme_first=1 tegraid=19.1.2.0.0 maxcpus=8 boot.slot_suffix= 
boot.ratchetvalues=0.4.2 vpr_resize sdhci_tegra.en_boot_part_access=1quiet 
root=/dev/mmcblk0p1 rw rootwait rootfstype=ext4 console=ttyTCU0,115200n8 
console=tty0 fbcon=map:0 net.ifnames=0 rootfstype=ext4
  Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.3
   apt  1.6.12ubuntu0.1
  SourcePackage: mesa
  Title: package libegl-mesa0 20.0.8-0ubuntu1~18.04.1 [modified: 
usr/share/glvnd/egl_vendor.d/50_mesa.json] failed to install/upgrade: trying to 
overwrite shared '/usr/share/glvnd/egl_vendor.d/50_mesa.json', which is 
different from other instances of package libegl-mesa0:armhf
  UpgradeStatus: No upgrade log present (probably fresh install)
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.101-2~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1892985/+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 1965608] Re: Crash in gbm_dri_bo_import on ASPEED + AMDGPU system

2023-10-27 Thread Launchpad Bug Tracker

[Expired for mesa (Ubuntu) because there has been no activity for 60
days.]

** Changed in: mesa (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1965608

Title:
  Crash in gbm_dri_bo_import on ASPEED + AMDGPU system

Status in mesa package in Ubuntu:
  Expired

Bug description:
  I have a server machine with an ASPEED BMC (kernel driver `ast`) and a
  Radeon Pro WX 4100 (driver `amdgpu`).  If I try to log into a KDE
  Wayland session or a Gnome Wayland session, it crashes back to the
  login screen, with the same innermost level in the traceback.

  What I'd like to be able to do: if a monitor is connected to the AMD
  GPU, then show the login screen on that, and maybe duplicate it on the
  BMC.  If no external monitor is connected, show it only on the BMC.
  Ideally, it should switch on the fly, but at the very least, it
  shouldn't crash.

  Note that in Xorg sessions, it doesn't crash, but xrandr only shows
  outputs from the AMD GPU.  If I do xrandr --listproviders, I see that
  the `ast` has no capabilities.

  Provider 0: id: 0x58 cap: 0x9, Source Output, Sink Offload crtcs: 5 outputs: 
4 associated providers: 0 name:AMD Radeon (TM) Pro WX 4100 @ pci::0e:00.0
  Provider 1: id: 0x99 cap: 0x0 crtcs: 1 outputs: 1 associated providers: 0 
name:modesetting

  It really would be nice to support using it as a dumb output like
  DisplayLink, even if it has to allow tearing or drop many frames.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: libgbm1 21.2.6-0ubuntu0.1
  ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19
  Uname: Linux 5.13.0-35-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  BootLog:
   
  CasperMD5CheckResult: unknown
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sat Mar 19 00:09:57 2022
  DistUpgraded: 2022-03-15 02:09:53,367 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: impish
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   ASPEED Technology, Inc. ASPEED Graphics Family [1a03:2000] (rev 41) (prog-if 
00 [VGA controller])
 Subsystem: ASPEED Technology, Inc. ASPEED Graphics Family [1a03:2000]
   Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Radeon Pro WX 4100] 
[1002:67e3] (prog-if 00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Radeon Pro WX 
4100] [1002:0b0d]
  InstallationDate: Installed on 2016-10-27 (1969 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   LANGUAGE=en_US:en
   LANG=en_US.UTF-8
   TERM=xterm-256color
   PATH=(custom, no user)
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-35-generic 
root=UUID=c4c2bc1a-635a-4890-9b75-207bd66db859 ro usbcore.autosuspend=0 
earlycon console=ttyS1,115200n8 console=tty0 intel_iommu=on amd_iommu=on 
plymouth.ignore-serial-consoles pstore.backend=efi drm.debug=0x104 
video=efifb:off thunderbolt.dyndbg pcie_ports=native 
pci=assign-busses,hpbussize=0x33,realloc,hpmmiosize=256M,hpmmioprefsize=1G
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: mesa
  UpgradeStatus: Upgraded to impish on 2022-03-15 (3 days ago)
  dmi.bios.date: 08/19/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: L1.43
  dmi.board.name: X570D4U-2L2T
  dmi.board.vendor: ASRockRack
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 2
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrL1.43:bd08/19/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRockRack:rnX570D4U-2L2T:rvr:cvnToBeFilledByO.E.M.:ct2:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz 1:0.9.14.1+21.10.20210501-0ubuntu1
  version.libdrm2: libdrm2 2.4.107-8ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.6-0ubuntu0.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
  version.xserver-xorg-video-nouveau:

[Desktop-packages] [Bug 2040450] Re: Ubuntu 23.10 Latvian keyboard layout (apostrophe) broken

2023-10-27 Thread Arnis Voitkāns

When I manually added these variables to /etc/environment file, accents
started to work properly in Wayland session:

INPUT_METHOD=ibus
GTK_IM_MODULE=ibus
QT_IM_MODULE=ibus
XMODIFIERS=@im=ibus

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to wayland in Ubuntu.
https://bugs.launchpad.net/bugs/2040450

Title:
  Ubuntu 23.10 Latvian keyboard layout (apostrophe) broken

Status in wayland package in Ubuntu:
  Confirmed

Bug description:
  When using keyboard layout Latvian (apostrophe), when writing accented 
  characters like "š", second character is outputed accented, too.

  When writing, for example, 'so, šō is outputted (should be šo)

  When testing keyboard during Ubuntu 23.10 installation and choosing 
  Latvian (apostrophe) layout, the behaviour was correct.

    affects ubuntu/mantic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/2040450/+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 2040450] Re: Ubuntu 23.10 Latvian keyboard layout (apostrophe) broken

2023-10-27 Thread Arnis Voitkāns

It seems it is somehow related to Wayland session - bug appears when
Wayland session is enabled, and if I switch to X11 session, bug
disappears.

** Package changed: libxkbcommon (Ubuntu) => wayland (Ubuntu)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libxkbcommon in Ubuntu.
https://bugs.launchpad.net/bugs/2040450

Title:
  Ubuntu 23.10 Latvian keyboard layout (apostrophe) broken

Status in wayland package in Ubuntu:
  Confirmed

Bug description:
  When using keyboard layout Latvian (apostrophe), when writing accented 
  characters like "š", second character is outputed accented, too.

  When writing, for example, 'so, šō is outputted (should be šo)

  When testing keyboard during Ubuntu 23.10 installation and choosing 
  Latvian (apostrophe) layout, the behaviour was correct.

    affects ubuntu/mantic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/2040450/+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 2041706] [NEW] Weird screen glitches in firefox snap

2023-10-27 Thread Sameer Sharma

Public bug reported:

Steps to reproduce:

Usual steps.

Install firefox snap (stable or esr) and enable hardware acceleration. 
Minimize browser through panel.
Maximize browser through panel.
(This is the best use-case to detect it although it does frequently occurs for 
short time between using the browser casually too.)

Actual results:

Screen feels like crashing/weird colours are produced, i.e, i don't have a 
specific word to define it though the attached video should help understand my 
issue better.
Only happens if hardware acceleration is enabled.

Expected results:

The browser should work fine how its expected to with hardware acceleration 
enabled.
Without hardware acceleration the browser works fine.
The issue is with hardware acceleration probably. 

Technical Details: 
- Using Xubuntu 22.04.3
- Firefox is installed as snap.
- Using Intel celeron N4500.
- Enabled xfce compositing with vblank mode set off, though without compoisting 
also its same.
- Only specific to firefox snap, other snaps and browsers like chromium works 
fine.

** Affects: firefox (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/2041706

Title:
  Weird screen glitches in firefox snap

Status in firefox package in Ubuntu:
  New

Bug description:
  Steps to reproduce:

  Usual steps.

  Install firefox snap (stable or esr) and enable hardware acceleration. 
  Minimize browser through panel.
  Maximize browser through panel.
  (This is the best use-case to detect it although it does frequently occurs 
for short time between using the browser casually too.)

  Actual results:

  Screen feels like crashing/weird colours are produced, i.e, i don't have a 
specific word to define it though the attached video should help understand my 
issue better.
  Only happens if hardware acceleration is enabled.

  Expected results:

  The browser should work fine how its expected to with hardware acceleration 
enabled.
  Without hardware acceleration the browser works fine.
  The issue is with hardware acceleration probably. 

  Technical Details: 
  - Using Xubuntu 22.04.3
  - Firefox is installed as snap.
  - Using Intel celeron N4500.
  - Enabled xfce compositing with vblank mode set off, though without 
compoisting also its same.
  - Only specific to firefox snap, other snaps and browsers like chromium works 
fine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2041706/+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 2041706] Re: Weird screen glitches in firefox snap

2023-10-27 Thread Sameer Sharma

** Attachment added: "Example Video."

https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2041706/+attachment/5713896/+files/glitch-2023-10-27_22.09.05.mkv

--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/2041706

Title:
Weird screen glitches in firefox snap

Status in firefox package in Ubuntu:
New

Bug description:
Steps to reproduce:

Usual steps.

Install firefox snap (stable or esr) and enable hardware acceleration.
Minimize browser through panel.
Maximize browser through panel.
(This is the best use-case to detect it although it does frequently occurs
for short time between using the browser casually too.)

Actual results:

Screen feels like crashing/weird colours are produced, i.e, i don't have a
specific word to define it though the attached video should help understand my
issue better.
Only happens if hardware acceleration is enabled.

Expected results:

The browser should work fine how its expected to with hardware acceleration
enabled.
Without hardware acceleration the browser works fine.
The issue is with hardware acceleration probably.

Technical Details:
- Using Xubuntu 22.04.3
- Firefox is installed as snap.
- Using Intel celeron N4500.
- Enabled xfce compositing with vblank mode set off, though without
compoisting also its same.
- Only specific to firefox snap, other snaps and browsers like chromium works
fine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2041706/+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 2039804] Re: Data loss: qpdf discards the character in a binary string following an octal quoted character with 1 or 2 digits

2023-10-27 Thread Till Kamppeter

Thanks, Jay, marking as verified ...

** Tags removed: verification-needed verification-needed-lunar 
verification-needed-mantic
** Tags added: verification-done verification-done-lunar 
verification-done-mantic

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to qpdf in Ubuntu.
https://bugs.launchpad.net/bugs/2039804

Title:
  Data loss: qpdf discards the character in a binary string following an
  octal quoted character with 1 or 2 digits

Status in Qpdf:
  Fix Released
Status in qpdf package in Ubuntu:
  Fix Committed
Status in qpdf source package in Lunar:
  Fix Committed
Status in qpdf source package in Mantic:
  Fix Committed
Status in qpdf package in Debian:
  Confirmed

Bug description:
  Notes:

  * I am the upstream author and debian maintainer for qpdf.
  * This bug has been fixed in debian unstable and testing with version 11.6.3, 
but because 24.04 is not yet open, it has not synced. This should not block 
fixing 23.04 and 22.04. I have uploaded 11.6.3 to my ppa: 
https://launchpad.net/~qpdf/+archive/ubuntu/qpdf
  * I am attaching debdiffs for lunar and mantic

  Upstream bug https://github.com/qpdf/qpdf/issues/1050 revealed a bug
  in qpdf's lexical layer that would cause qpdf to discard the character
  in a binary string following an octal quoted character with 1 or 2
  digits. The PDF spec allows octal digits to be \d, \dd, or \ddd, and
  allows the first two forms if the next character is other than an
  octal digit. Most PDF writers never use the \d or \dd forms, but some
  do. With default options, qpdf does not parse or alter strings inside
  content streams, so this bug is not likely to affect page content.
  However, binary strings of this sort are common in the document /ID
  and may also appear in metadata for encrypted files. In some cases,
  such as the file in #1050, this bug can cause error, in this case,
  because the discarded character was the string end delimiter. In most
  case, this bug results in silent data loss. The fix is very small and
  locally contained. The upstream fix includes several new test cases,
  but the patch I will include to fix the issue only includes the
  relevant code change.

  I also reported this as a debian bug: https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=1054158

  It was approved as a stable update by debian:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054119

  [ Impact ]

  The bug could result in silent corruption of binary strings in PDF
  metadata. It could also result in failure of qpdf to process a valid
  file. Data loss justifies a stable update.

  [ Test Plan ]

  The test file in https://github.com/qpdf/qpdf/issues/1050 can be used
  to prove that the bug exists in versions >= 11.0.0 and <= 11.6.2 and
  that the bug is fixed in 11.6.3.

  The upstream fix includes several additional automated test cases.
  These are not included in the patch, but they are included in the
  upstream commit that fixes the bug:
  https://github.com/qpdf/qpdf/commit/1ecc6bb29e24a4f89470ff91b2682b46e0576ad4

  How to test the SRU package on Ubuntu manually (copied from Jay's
  comment #6 below):

  Running `qpdf --check 018.pdf` where `018.pdf` is the file attached to
  the upstream bug will reproduce the issue. With the current version in
  22.04 and 23.04, you will see something like this:

  ```
  WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110340): EOF while 
reading token
  WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110830): unexpected 
EOF
  WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110830): parse 
error while reading object
  WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110830): expected 
endobj
  WARNING: /tmp/z/018.pdf: file is damaged
  WARNING: /tmp/z/018.pdf (offset 110267): xref not found
  WARNING: /tmp/z/018.pdf: Attempting to reconstruct cross-reference table
  qpdf: /tmp/z/018.pdf: unable to find trailer dictionary while recovering 
damaged file
  ```

  After the fix, you will see
  ```
  checking /home/ejb/Downloads/018.pdf
  PDF Version: 1.7
  File is not encrypted
  File is not linearized
  No syntax or stream encoding errors found; the file may still contain
  errors that qpdf cannot detect
  ```
  (obviously with the full paths based on whatever you call the file).

  [ Where problems could occur ]

  This fix has a very low risk of causing a regression. The fix is very
  localized to qpdf's lexical layer and is in a code path that only
  occurs when a 1-digit or 2-digit octal quoted character is terminated
  by other than an octal digit. This is the first bug in qpdf's lexical
  layer in many years. It was introduced by a pull request from a
  reliable and consistent contributor who has made may improvements to
  qpdf's performance. The fix follows the established pattern of how to
  handle instances in which a character triggers a state change and has
  to be reprocessed in the new state.

  qpdf

[Desktop-packages] [Bug 1973084] Re: transmission-daemon high RAM usage

2023-10-27 Thread Andreas Hasenack

Marius, Andrey

thanks for your contribution!

I uploaded jammy and lunar packages to this ppa[1], with amd64 and arm64
builds, with the gentoo patch replacing the one we had in the package.

Marius, I changed the d/changelog text a bit, I hope you don't mind, but
please let me know if you have concerns. I want to make sure to give
credit to everybody involved, and keep your name in the changelog entry
so this upload goes to you when it's sponsored.

The PPAs are a bit slow, since we just opened the next ubuntu release
(noble) for development, so give them some time.

Here are the branches from which I built these packages:

- jammy: 
https://code.launchpad.net/~ahasenack/ubuntu/+source/transmission/+git/transmission/+ref/jammy-transmission-memleak-1973084
- lunar: 
https://code.launchpad.net/~ahasenack/ubuntu/+source/transmission/+git/transmission/+ref/lunar-transmission-memleak-1973084

Mantic and later are at version 4.0.2, and focal and earlier are at
2.94, so I believe they are not affected. The problematic openssl3 patch
is in neither.

If these work for you guys, then we can start preparing for an SRU,
which would definitely be worth it.

1. https://launchpad.net/~ahasenack/+archive/ubuntu/transmission-
memleak-1973084/

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to transmission in Ubuntu.
https://bugs.launchpad.net/bugs/1973084

Title:
  transmission-daemon high RAM usage

Status in transmission package in Ubuntu:
  Confirmed
Status in transmission source package in Jammy:
  New
Status in transmission source package in Lunar:
  New
Status in transmission package in Debian:
  New

Bug description:
  Transmission uses a lot of RAM in ubuntu 22.04 server (arm64) runnign
  on a Raspberry Pi 4.

  It "eats" RAM and the RAM usage grows each hour until it crashes the
  system.

  I sideloaded transmission-daemon and its dependancies from debian 11
  (arm64) locked the packages so apt won't update them and, ever since,
  this issue hasn't happened.

  
  Description:Ubuntu 22.04 LTS
  Release:22.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1973084/+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 1973084] Re: transmission-daemon high RAM usage

2023-10-27 Thread Bug Watch Updater

** Changed in: transmission (Debian)
   Status: Unknown => New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to transmission in Ubuntu.
https://bugs.launchpad.net/bugs/1973084

Title:
  transmission-daemon high RAM usage

Status in transmission package in Ubuntu:
  Confirmed
Status in transmission source package in Jammy:
  New
Status in transmission source package in Lunar:
  New
Status in transmission package in Debian:
  New

Bug description:
  Transmission uses a lot of RAM in ubuntu 22.04 server (arm64) runnign
  on a Raspberry Pi 4.

  It "eats" RAM and the RAM usage grows each hour until it crashes the
  system.

  I sideloaded transmission-daemon and its dependancies from debian 11
  (arm64) locked the packages so apt won't update them and, ever since,
  this issue hasn't happened.

  
  Description:Ubuntu 22.04 LTS
  Release:22.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1973084/+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 2039804] Re: Data loss: qpdf discards the character in a binary string following an octal quoted character with 1 or 2 digits

2023-10-27 Thread Jay Berkenbilt

I have verified by running manual tests on a docker image of 23.04 and
23.10 after manually installing the packages as downloaded from
https://bugs.launchpad.net/ubuntu/+source/qpdf by verifying that I could
reproduce the bug, then install the updated libqpdf package, then
verifying that the bug was fixed.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to qpdf in Ubuntu.
https://bugs.launchpad.net/bugs/2039804

Title:
  Data loss: qpdf discards the character in a binary string following an
  octal quoted character with 1 or 2 digits

Status in Qpdf:
  Fix Released
Status in qpdf package in Ubuntu:
  Fix Committed
Status in qpdf source package in Lunar:
  Fix Committed
Status in qpdf source package in Mantic:
  Fix Committed
Status in qpdf package in Debian:
  Confirmed

Bug description:
  Notes:

  * I am the upstream author and debian maintainer for qpdf.
  * This bug has been fixed in debian unstable and testing with version 11.6.3, 
but because 24.04 is not yet open, it has not synced. This should not block 
fixing 23.04 and 22.04. I have uploaded 11.6.3 to my ppa: 
https://launchpad.net/~qpdf/+archive/ubuntu/qpdf
  * I am attaching debdiffs for lunar and mantic

  Upstream bug https://github.com/qpdf/qpdf/issues/1050 revealed a bug
  in qpdf's lexical layer that would cause qpdf to discard the character
  in a binary string following an octal quoted character with 1 or 2
  digits. The PDF spec allows octal digits to be \d, \dd, or \ddd, and
  allows the first two forms if the next character is other than an
  octal digit. Most PDF writers never use the \d or \dd forms, but some
  do. With default options, qpdf does not parse or alter strings inside
  content streams, so this bug is not likely to affect page content.
  However, binary strings of this sort are common in the document /ID
  and may also appear in metadata for encrypted files. In some cases,
  such as the file in #1050, this bug can cause error, in this case,
  because the discarded character was the string end delimiter. In most
  case, this bug results in silent data loss. The fix is very small and
  locally contained. The upstream fix includes several new test cases,
  but the patch I will include to fix the issue only includes the
  relevant code change.

  I also reported this as a debian bug: https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=1054158

  It was approved as a stable update by debian:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054119

  [ Impact ]

  The bug could result in silent corruption of binary strings in PDF
  metadata. It could also result in failure of qpdf to process a valid
  file. Data loss justifies a stable update.

  [ Test Plan ]

  The test file in https://github.com/qpdf/qpdf/issues/1050 can be used
  to prove that the bug exists in versions >= 11.0.0 and <= 11.6.2 and
  that the bug is fixed in 11.6.3.

  The upstream fix includes several additional automated test cases.
  These are not included in the patch, but they are included in the
  upstream commit that fixes the bug:
  https://github.com/qpdf/qpdf/commit/1ecc6bb29e24a4f89470ff91b2682b46e0576ad4

  How to test the SRU package on Ubuntu manually (copied from Jay's
  comment #6 below):

  Running `qpdf --check 018.pdf` where `018.pdf` is the file attached to
  the upstream bug will reproduce the issue. With the current version in
  22.04 and 23.04, you will see something like this:

  ```
  WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110340): EOF while 
reading token
  WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110830): unexpected 
EOF
  WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110830): parse 
error while reading object
  WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110830): expected 
endobj
  WARNING: /tmp/z/018.pdf: file is damaged
  WARNING: /tmp/z/018.pdf (offset 110267): xref not found
  WARNING: /tmp/z/018.pdf: Attempting to reconstruct cross-reference table
  qpdf: /tmp/z/018.pdf: unable to find trailer dictionary while recovering 
damaged file
  ```

  After the fix, you will see
  ```
  checking /home/ejb/Downloads/018.pdf
  PDF Version: 1.7
  File is not encrypted
  File is not linearized
  No syntax or stream encoding errors found; the file may still contain
  errors that qpdf cannot detect
  ```
  (obviously with the full paths based on whatever you call the file).

  [ Where problems could occur ]

  This fix has a very low risk of causing a regression. The fix is very
  localized to qpdf's lexical layer and is in a code path that only
  occurs when a 1-digit or 2-digit octal quoted character is terminated
  by other than an octal digit. This is the first bug in qpdf's lexical
  layer in many years. It was introduced by a pull request from a
  reliable and consistent contributor who has made may improvements to
  qpdf's performance. The fix follows the established pattern of how to
  handle instances in

[Desktop-packages] [Bug 1973084] Re: transmission-daemon high RAM usage

2023-10-27 Thread Andreas Hasenack

** Also affects: transmission (Ubuntu Lunar)
   Importance: Undecided
   Status: New

** Also affects: transmission (Ubuntu Jammy)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to transmission in Ubuntu.
https://bugs.launchpad.net/bugs/1973084

Title:
  transmission-daemon high RAM usage

Status in transmission package in Ubuntu:
  Confirmed
Status in transmission source package in Jammy:
  New
Status in transmission source package in Lunar:
  New
Status in transmission package in Debian:
  Unknown

Bug description:
  Transmission uses a lot of RAM in ubuntu 22.04 server (arm64) runnign
  on a Raspberry Pi 4.

  It "eats" RAM and the RAM usage grows each hour until it crashes the
  system.

  I sideloaded transmission-daemon and its dependancies from debian 11
  (arm64) locked the packages so apt won't update them and, ever since,
  this issue hasn't happened.

  
  Description:Ubuntu 22.04 LTS
  Release:22.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1973084/+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 1946215] Re: transmission: Fail to build against OpenSSL 3.0

2023-10-27 Thread Andreas Hasenack

https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1973084 is
the memleak bug report.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to transmission in Ubuntu.
https://bugs.launchpad.net/bugs/1946215

Title:
  transmission: Fail to build against OpenSSL 3.0

Status in transmission package in Ubuntu:
  Fix Released

Bug description:
  Hello,

  As part of a rebuild against OpenSSL3, this package failed to build on one or
  several architectures. You can find the details of the rebuild at 

  https://people.canonical.com/~schopin/rebuilds/openssl-3.0.0-impish.html

  or for the amd64 failed build, directly at

  
https://launchpad.net/~schopin/+archive/ubuntu/openssl-3.0.0/+build/22099409/+files/buildlog_ubuntu-
  impish-amd64.transmission_3.00-1ubuntu2.0~ssl3ppa1.1_BUILDING.txt.gz

  We're planning to transition to OpenSSL 3.0 for the 22.04 release, and 
consider
  this issue as blocking for this transition.

  You can find general migration informations at
  https://www.openssl.org/docs/manmaster/man7/migration_guide.html
  For your tests, you can build against libssl-dev as found in the PPA
  schopin/openssl-3.0.0

  This has been fixed upstream, currently on master:
  https://github.com/transmission/transmission/pull/1788

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1946215/+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 1973084] Re: transmission-daemon high RAM usage

2023-10-27 Thread Andreas Hasenack

** Bug watch added: Debian Bug tracker #1051056
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051056

** Also affects: transmission (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051056
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to transmission in Ubuntu.
https://bugs.launchpad.net/bugs/1973084

Title:
  transmission-daemon high RAM usage

Status in transmission package in Ubuntu:
  Confirmed
Status in transmission package in Debian:
  Unknown

Bug description:
  Transmission uses a lot of RAM in ubuntu 22.04 server (arm64) runnign
  on a Raspberry Pi 4.

  It "eats" RAM and the RAM usage grows each hour until it crashes the
  system.

  I sideloaded transmission-daemon and its dependancies from debian 11
  (arm64) locked the packages so apt won't update them and, ever since,
  this issue hasn't happened.

  
  Description:Ubuntu 22.04 LTS
  Release:22.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1973084/+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 2039187] Re: Thunderbird doesn't accept URI attachments anymore

2023-10-27 Thread Andreas Hasenack

Hi Nathan,

I see that the discussion on the upstream PR[1] is still ongoing, and
there isn't consensus yet.

I think it's best to put this on hold until a conclusion is reached, and
then this can move forward. I'll therefore unsubscribe sponsors for now.
Please subscribe again once a decision has been reached on how to
proceed.


1. https://github.com/flatpak/xdg-desktop-portal-gtk/pull/447

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xdg-desktop-portal-gtk in Ubuntu.
https://bugs.launchpad.net/bugs/2039187

Title:
  Thunderbird doesn't accept URI attachments anymore

Status in xdg-desktop-portal-gtk package in Ubuntu:
  Confirmed
Status in xdg-desktop-portal-gtk source package in Focal:
  New
Status in xdg-desktop-portal-gtk source package in Jammy:
  New
Status in xdg-desktop-portal-gtk source package in Lunar:
  New
Status in xdg-desktop-portal-gtk source package in Mantic:
  Confirmed

Bug description:
  The desktop portal constructs an mailto: url with an attachment= but
  thunderbird upstream explicitly decided to not allow adding files from
  an URL for security reasons.

  One can still use the -compose option though, as this patch does.

  Test case
  -

  * Install the proposed package.
  * Log out and back in.
  * Set Thunberbird as default client in Gnome Control Panel.
  * Open Nautilus and try to attach two files to the same email. They can be 
creatively named, it should not break on weird characters.
  * Thunderbird should open with the corresponding files attached.
  * [For regression testing] Set Evolution as the default.
  * Open Nautilus and try to attach two files to the same email. They can be 
creatively named, it should not break on weird characters. It only attaches one 
file, this is however not a regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/2039187/+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 2041690] [NEW] Cannot open internal or screen laptop

2023-10-27 Thread RoeunPacharoth

Public bug reported:

After I use the secondary screen, the primary screen stops working, and
the problem is nvidia

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.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  535.113.01  Tue Sep 12 
19:41:24 UTC 2023
 GCC version:
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Oct 27 23:58:39 2023
DistUpgraded: 2023-10-14 21:42:04,522 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation TigerLake-H GT1 [UHD Graphics] [8086:9a60] (rev 01) (prog-if 
00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] TigerLake-H GT1 [UHD Graphics] [1025:153b]
 NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] [10de:1f9d] (rev 
a1) (prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] TU117M [GeForce GTX 1650 Mobile / Max-Q] 
[1025:1544]
InstallationDate: Installed on 2023-05-20 (160 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic 
root=UUID=8806d2d2-440c-4fb8-bfae-fce3d6fc0f20 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to mantic on 2023-10-14 (13 days ago)
XorgConf:
 
dmi.bios.date: 06/22/2022
dmi.bios.release: 1.18
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.18
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Kamiq_TLS
dmi.board.vendor: TGL
dmi.board.version: V1.18
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.18
dmi.ec.firmware.release: 1.10
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.18:bd06/22/2022:br1.18:efr1.10:svnAcer:pnNitroAN517-54:pvrV1.18:rvnTGL:rnKamiq_TLS:rvrV1.18:cvnAcer:ct10:cvrV1.18:sku:
dmi.product.family: Nitro 5
dmi.product.name: Nitro AN517-54
dmi.product.sku: 
dmi.product.version: V1.18
dmi.sys.vendor: Acer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
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:21.1.7-3ubuntu2.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-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug mantic 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/2041690

Title:
  Cannot open internal or screen laptop

Status in xorg package in Ubuntu:
  New

Bug description:
  After I use the secondary screen, the primary screen stops working,
  and the problem is nvidia

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .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  535.113.01  Tue Sep 12 
19:41:24 UTC 2023
   GCC version:
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 27 23:58:39 2023
  DistUpgraded: 2023-10-14 21:42:04,522 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: mantic
  DistroVariant: ubuntu

[Desktop-packages] [Bug 2041680] [NEW] Stack trace not included in GNOME Shell crash report in JournalErrors

2023-10-27 Thread Benjamin Drung

Public bug reported:

1. Use Ubuntu 23.10 with all updates
2. kill gnome-shell: killall -11 gnome-shell
3. log-in again
4. Wait for the apport crash window for reporting
5. Show details

The JournalErrors does not contain the stack trace, but now I found it
in ShellJournal:

 [   87.744546] ubuntu-2304-2 gnome-shell[1048]: GNOME Shell crashed with 
signal 11
 [   87.744546] ubuntu-2304-2 gnome-shell[1048]: == Stack trace for context 
0x56355c3ca0f0 ==
 [   87.745201] ubuntu-2304-2 gnome-shell[1048]: #0   56355c491fe8 i   
resource:///org/gnome/shell/ui/init.js:21 (2b3376570ba0 @ 48)

The crash is not logged with a high enough severity to let it appear in
JournalErrors.

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: New

-- 
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/2041680

Title:
  Stack trace not included in GNOME Shell crash report in JournalErrors

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  1. Use Ubuntu 23.10 with all updates
  2. kill gnome-shell: killall -11 gnome-shell
  3. log-in again
  4. Wait for the apport crash window for reporting
  5. Show details

  The JournalErrors does not contain the stack trace, but now I found it
  in ShellJournal:

   [   87.744546] ubuntu-2304-2 gnome-shell[1048]: GNOME Shell crashed with 
signal 11
   [   87.744546] ubuntu-2304-2 gnome-shell[1048]: == Stack trace for context 
0x56355c3ca0f0 ==
   [   87.745201] ubuntu-2304-2 gnome-shell[1048]: #0   56355c491fe8 i   
resource:///org/gnome/shell/ui/init.js:21 (2b3376570ba0 @ 48)

  The crash is not logged with a high enough severity to let it appear
  in JournalErrors.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2041680/+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 1901385] Re: System freezes on drag and move a file from desktop

2023-10-27 Thread Dipak Bist

*** This bug is a duplicate of bug 1880405 ***
https://bugs.launchpad.net/bugs/1880405

 sudo snap install postman
error: cannot perform the following tasks:
- Run configure hook of "postman" snap if present (run hook "configure": cannot 
locate base snap core18: No such file or directory)

-- 
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/1901385

Title:
  System freezes on drag and move a file from desktop

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Whenever I drag a file from a desktop and move it to the nautilus
  folder window, the system freezes and I can't do anything, just moving
  the mouse.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: nautilus 1:3.38.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 25 08:43:47 2020
  InstallationDate: Installed on 2018-04-29 (910 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to groovy on 2020-10-23 (1 days ago)
  usr_lib_nautilus:
   evince3.38.0-1
   file-roller   3.38.0-1
   nautilus-extension-gnome-terminal 3.38.0-1ubuntu1
   nautilus-share0.7.3-2ubuntu3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1901385/+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 2034477] Re: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop

2023-10-27 Thread Mario Limonciello

Please also take this fix at the same time for this same laptop.  It
will fix s2idle for it.

https://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-
drivers-x86.git/commit/?h=fixes=3bde7ec13c971445faade32172cb0b4370b841d9

** Changed in: libinput (Ubuntu)
   Status: Confirmed => Invalid

** Package changed: linux-signed-hwe-6.2 (Ubuntu) => linux (Ubuntu)

** No longer affects: linux-signed-oem-6.5 (Ubuntu)

** Also affects: linux-oem-6.1 (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: linux-oem-6.5 (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: linux-hwe-6.2 (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Mantic)
   Importance: Undecided
   Status: New

** Also affects: libinput (Ubuntu Mantic)
   Importance: Undecided
   Status: New

** Also affects: linux-oem-6.1 (Ubuntu Mantic)
   Importance: Undecided
   Status: New

** Also affects: linux-hwe-6.2 (Ubuntu Mantic)
   Importance: Undecided
   Status: New

** Also affects: linux-oem-6.5 (Ubuntu Mantic)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Lunar)
   Importance: Undecided
   Status: New

** Also affects: libinput (Ubuntu Lunar)
   Importance: Undecided
   Status: New

** Also affects: linux-oem-6.1 (Ubuntu Lunar)
   Importance: Undecided
   Status: New

** Also affects: linux-hwe-6.2 (Ubuntu Lunar)
   Importance: Undecided
   Status: New

** Also affects: linux-oem-6.5 (Ubuntu Lunar)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Also affects: libinput (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Also affects: linux-oem-6.1 (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Also affects: linux-hwe-6.2 (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Also affects: linux-oem-6.5 (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Noble)
   Importance: Undecided
   Status: Confirmed

** Also affects: libinput (Ubuntu Noble)
   Importance: Undecided
   Status: Invalid

** Also affects: linux-oem-6.1 (Ubuntu Noble)
   Importance: Undecided
   Status: New

** Also affects: linux-hwe-6.2 (Ubuntu Noble)
   Importance: Undecided
   Status: New

** Also affects: linux-oem-6.5 (Ubuntu Noble)
   Importance: Undecided
   Status: New

** No longer affects: libinput (Ubuntu)

** Changed in: linux (Ubuntu Mantic)
   Status: New => Confirmed

** Changed in: linux (Ubuntu Lunar)
   Status: New => Confirmed

** Changed in: linux (Ubuntu Jammy)
   Status: New => Confirmed

** No longer affects: linux-oem-6.1 (Ubuntu Lunar)

** No longer affects: linux-oem-6.1 (Ubuntu Mantic)

** No longer affects: linux-oem-6.1 (Ubuntu Noble)

** No longer affects: linux-oem-6.5 (Ubuntu Lunar)

** No longer affects: libinput (Ubuntu Jammy)

** No longer affects: libinput (Ubuntu Lunar)

** No longer affects: libinput (Ubuntu Mantic)

** No longer affects: libinput (Ubuntu Noble)

** No longer affects: linux-hwe-6.2 (Ubuntu Lunar)

** No longer affects: linux-hwe-6.2 (Ubuntu Mantic)

** No longer affects: linux-hwe-6.2 (Ubuntu Noble)

** No longer affects: linux-oem-6.5 (Ubuntu Mantic)

** No longer affects: linux-oem-6.5 (Ubuntu Noble)

** Changed in: linux-oem-6.5 (Ubuntu Jammy)
   Status: New => Confirmed

** Changed in: linux-oem-6.1 (Ubuntu Jammy)
   Status: New => Confirmed

** Changed in: linux-hwe-6.2 (Ubuntu Jammy)
   Status: New => Confirmed

** Changed in: linux-oem-6.1 (Ubuntu)
   Status: New => Invalid

** Changed in: linux-hwe-6.2 (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libinput in Ubuntu.
https://bugs.launchpad.net/bugs/2034477

Title:
  Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop

Status in ideapad-laptop:
  New
Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-6.2 package in Ubuntu:
  Invalid
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux-oem-6.5 package in Ubuntu:
  New
Status in linux source package in Jammy:
  Confirmed
Status in linux-hwe-6.2 source package in Jammy:
  Confirmed
Status in linux-oem-6.1 source package in Jammy:
  Confirmed
Status in linux-oem-6.5 source package in Jammy:
  Confirmed
Status in linux source package in Lunar:
  Confirmed
Status in linux source package in Mantic:
  Confirmed
Status in linux source package in Noble:
  Confirmed
Status in Fedora:
  New

Bug description:
  Hello.

  Ubuntu 22.04.3 with (later upgraded to kernel 6.2.0-32-generic) was
  installed in rewly purchased LENOVO V15 GEN4 AMN (AMD Ryzen 5 7520u)
  laptop and it was noticed that keyboard, touchpad and microphone are
  not working. The keyboard and touchpad work fine in BIOS setup and
  till GRUB (command

[Desktop-packages] [Bug 2034477] Re: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop

2023-10-27 Thread Mario Limonciello

Here is the upstream patch for this issue:

https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?h=x86/urgent=38d54ecfe293ed8bb26d05e6f0270a0aaa6656c6

** Also affects: linux via
   https://bugzilla.kernel.org/show_bug.cgi?id=218003
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libinput in Ubuntu.
https://bugs.launchpad.net/bugs/2034477

Title:
  Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop

Status in ideapad-laptop:
  New
Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-6.2 package in Ubuntu:
  Invalid
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux-oem-6.5 package in Ubuntu:
  New
Status in linux source package in Jammy:
  Confirmed
Status in linux-hwe-6.2 source package in Jammy:
  Confirmed
Status in linux-oem-6.1 source package in Jammy:
  Confirmed
Status in linux-oem-6.5 source package in Jammy:
  Confirmed
Status in linux source package in Lunar:
  Confirmed
Status in linux source package in Mantic:
  Confirmed
Status in linux source package in Noble:
  Confirmed
Status in Fedora:
  New

Bug description:
  Hello.

  Ubuntu 22.04.3 with (later upgraded to kernel 6.2.0-32-generic) was
  installed in rewly purchased LENOVO V15 GEN4 AMN (AMD Ryzen 5 7520u)
  laptop and it was noticed that keyboard, touchpad and microphone are
  not working. The keyboard and touchpad work fine in BIOS setup and
  till GRUB (command line). It was found that when external devices such
  as keyboard, mouse and microphone are connected through USB and 3.5
  jack, respectively, these work just fine. To confirm these are not
  hardware problems, Microsoft Windows 11  (Home) was installed in
  another disk partition and observed all these working alright. Hence a
  bug is being reported to draw attention of the concerned team and I
  request them to refer this issue and do the needful at the earliest.

  Regards,
  Pradip Kumar Das

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-32-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep  6 08:04:42 2023
  InstallationDate: Installed on 2023-08-14 (22 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-6.2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ideapad-laptop/+bug/2034477/+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

67 matches

Mail list logo