[Desktop-packages] [Bug 1967707] Re: Nvidia Wayland sessions sometimes flood the log with "clutter_frame_clock_notify_presented: code should not be reached"

2023-01-02 Thread Daniel van Vugt
Comment #3 is bug 1968040, not this one.

Comment #4 is bug 1999830, not this one.

But certainly this bug 1967707 occurs after other bugs have occurred.

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

Title:
  Nvidia Wayland sessions sometimes flood the log with
  "clutter_frame_clock_notify_presented: code should not be reached"

Status in Mutter:
  New
Status in mutter package in Ubuntu:
  Triaged

Bug description:
  Nvidia Wayland sessions sometimes flood the log with:

  [   13.105877] computer gnome-shell[1264]: 
(../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented:
 code should not be reached
  [   13.106163] computer gnome-shell[1264]: 
(../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented:
 code should not be reached
  [   13.112490] computer gnome-shell[1264]: 
(../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented:
 code should not be reached
  [   13.125302] computer gnome-shell[1264]: 
(../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented:
 code should not be reached
  [   13.142242] computer gnome-shell[1264]: 
(../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented:
 code should not be reached

  I've been seeing the issue for months although it only seems to happen
  *after* something has gone wrong in mutter. Not by default.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1967707/+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 1929209] Re: [i915] external monitor goes black for several seconds at a time, randomly

2023-01-02 Thread Daniel van Vugt
"Fix released" for mutter 43.0 only because a workaround was added,
which you can configure in ~/.config/monitors.xml as

  
...
8
  

But it may not help everyone. It didn't solve my issues. And so the bug
is still open for the Linux kernel.

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

Title:
  [i915] external monitor goes black for several seconds at a time,
  randomly

Status in linux package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  At times it is completely debilitating; at other times it does not happen for 
hours.
  The physical connections are clean and solid.

   I guess the attachments will show that I'm using Intel graphics
  hardware.  The monitor is a very popular Samsung one.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106
  Uname: Linux 5.4.0-73-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.17
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 20 16:56:04 2021
  DistUpgraded: 2020-06-01 15:46:34,953 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 6.1.16, 5.4.0-73-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
     Subsystem: Lenovo HD Graphics 5500 [17aa:5036]
  InstallationDate: Installed on 2019-01-24 (847 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: LENOVO 20BXCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-73-generic 
root=UUID=a6081f39-700f-4698-bda4-464e53d9d229 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-06-01 (353 days ago)
  dmi.bios.date: 09/13/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET66WW (1.30 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BXCTO1WW
  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:bvrJBET66WW(1.30):bd09/13/2017:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450s
  dmi.product.name: 20BXCTO1WW
  dmi.product.sku: LENOVO_MT_20BX_BU_Think_FM_ThinkPad T450s
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.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/1929209/+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 1929209] Re: [i915] external monitor goes black for several seconds at a time, randomly

2023-01-02 Thread Daniel van Vugt
I feel your pain, having suffered the same issue just a few seconds ago.
Although there's a chance we're seeing the same symptoms with different
root causes so please be sure to open your own bug by running:

  ubuntu-bug linux

Start by testing different display cables/connection types.

** Changed in: mutter (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  [i915] external monitor goes black for several seconds at a time,
  randomly

Status in linux package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  At times it is completely debilitating; at other times it does not happen for 
hours.
  The physical connections are clean and solid.

   I guess the attachments will show that I'm using Intel graphics
  hardware.  The monitor is a very popular Samsung one.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106
  Uname: Linux 5.4.0-73-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.17
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 20 16:56:04 2021
  DistUpgraded: 2020-06-01 15:46:34,953 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 6.1.16, 5.4.0-73-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
     Subsystem: Lenovo HD Graphics 5500 [17aa:5036]
  InstallationDate: Installed on 2019-01-24 (847 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: LENOVO 20BXCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-73-generic 
root=UUID=a6081f39-700f-4698-bda4-464e53d9d229 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-06-01 (353 days ago)
  dmi.bios.date: 09/13/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET66WW (1.30 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BXCTO1WW
  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:bvrJBET66WW(1.30):bd09/13/2017:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450s
  dmi.product.name: 20BXCTO1WW
  dmi.product.sku: LENOVO_MT_20BX_BU_Think_FM_ThinkPad T450s
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.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/1929209/+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 1902094] Re: High Xorg and gnome-shell CPU usage while Sound Settings opened

2023-01-02 Thread Daniel van Vugt
** Tags added: lunar

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

Title:
  High Xorg and gnome-shell CPU usage while Sound Settings opened

Status in gnome-control-center:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Triaged

Bug description:
  Several days ago I found huge lags over all system on my Ubuntu
  20.04.1 LTS. Today I think found the problem, but not the reason. So
  when I open Settings -> Sound menu, the CPU usage comes to about 100%.
  If I close Settings window or go to other tab, it becomes OK. Nothing
  special in my sound configuration - monitor and notebook with built in
  audio and Bluetooth headset. Same worked just fine on Ubuntu 18.04
  LTS.

  xorg:
Installed: 1:7.7+19ubuntu14
Candidate: 1:7.7+19ubuntu14
Version table:
   *** 1:7.7+19ubuntu14 500
  500 http://ru.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/gpu0'
  .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/mig'
  .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  450.80.02  Wed Sep 23 
01:13:39 UTC 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 29 18:27:20 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 450.80.02, 5.4.0-52-generic, x86_64: installed
   virtualbox, 6.1.10, 5.4.0-51-generic, x86_64: installed
   virtualbox, 6.1.10, 5.4.0-52-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 630 (Mobile) [1028:0824]
 Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:0824]
  InstallationDate: Installed on 2020-09-12 (47 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Dell Inc. G5 5587
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=UUID=ef73abac-57c7-4134-90f3-1f52f41127a8 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/11/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.9.0
  dmi.board.name: 03PVDF
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.9.0:bd02/11/2019:svnDellInc.:pnG55587:pvr:rvnDellInc.:rn03PVDF:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: GSeries
  dmi.product.name: G5 5587
  dmi.product.sku: 0824
  dmi.sys.vendor: Dell Inc.
  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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
  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/gnome-control-center/+bug/1902094/+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 1960590] Re: gnome-shell crashed with SIGSEGV in cogl_gl_framebuffer_bind() from _cogl_driver_gl_flush_framebuffer_state() from cogl_context_flush_framebuffer_state() from cogl

2023-01-02 Thread Daniel van Vugt
** Tags added: nvidia

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

Title:
  gnome-shell crashed with SIGSEGV in cogl_gl_framebuffer_bind() from
  _cogl_driver_gl_flush_framebuffer_state() from
  cogl_context_flush_framebuffer_state() from cogl_framebuffer_clear4f()
  from clutter_layer_node_pre_draw()

Status in Mutter:
  New
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
41.3-1ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/4f89714feb56bfeca16dbf20580cd82c75a2d6d1 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1960590/+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 1972977] Re: gnome-shell crashed (out of memory) with SIGSEGV in crocus_begin_query() from crocus_begin_query() from crocus_end_query() from crocus_end_query() from tc_call_end

2023-01-02 Thread Daniel van Vugt
I've only been monitoring crash reports to verify the fix worked in
kinetic and later. Although anecdotally I recall one or two users of
Haswell or older saying it happened frequently for them. I guess we
could try such an older system and monitor for the gnome-shell memory
leak that should precede the crash.

(Sorry for the delay - it was a long end of year break)

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

Title:
  gnome-shell crashed (out of memory) with SIGSEGV in
  crocus_begin_query() from crocus_begin_query() from crocus_end_query()
  from crocus_end_query() from tc_call_end_query()

Status in Mesa:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Jammy:
  Fix Committed

Bug description:
  [Impact]
  Gnome-shell is crashing on older gen Intel hw due to a memory leak.

  [Fix]
  An upstream commit that fixes the memleak in the crocus driver (which is only 
used on Intel 4th gen chips and older)

  [Test case]
  Either test this on an old Intel or see if there's a dent in the reported 
crashes.

  [Where things could go wrong]
  Mainly if this would not fix the crashes.

  --
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
42.0-2ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/d8aa1211f7e8b219a4ee6dcae294ac16decd7fe3 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1972977/+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 1990341] Re: [FeatureFreeze Exceptions] Support to install nvidia driver by allowing list

2023-01-02 Thread jeremyszu
** Description changed:

  > If the upload is a new upstream microrelease, the relevant part of the
  upstream changelog and/or release notes
  
  Upstream commit: https://github.com/tseliot/ubuntu-drivers-
  common/commit/a7d2d39805e995ed0e655de123b4bb6cff4e6434
  
  > An explanation of the testing which has been performed on the new
  version in Ubuntu, including verification that the new package:
  
  For this feature which only impact if the target system has a custom
  file "/etc/custom_supported_gpus.json"
  
  If the file presents, it will effect packages_for_modalias() and
  _is_runtimepm_supported(). Both functions are important when "ubuntu-
  driver install" a nvidia driver.
  
  For installing nvidia driver, u-d-c has several test in autopkgtest which 
contains:
  * different branch type: LTS/PB/NFB/Legacy..
  * different version type: 390/470/495/510..
  * For this particular feature, we created a new autopkgtest 
test_system_driver_packages_force_install_nvidia() which not only secure this 
FFE but each version bump.
  which contains:
  1. Normal case (Stock ubuntu), without /etc/customized_supported_gpus.json in 
the system.
  2. If /etc/custom_supported_gpus.json contains incorrect json field / format.
  3. /etc/custom_supported_gpus.json point to the older version than candidate.
  4. /etc/custom_supported_gpus.json point to the same version than candidate.
  5. /etc/custom_supported_gpus.json point to a non-exist version of 
ubuntu-archive (source list).
  
  and you can see from "buildlog" attachment, all passed as well as
  "test_system_driver_packages_force_install_nvidia()"
  
  Refer https://github.com/tseliot/ubuntu-drivers-common/pull/71 for more
  details.
  
  > state the reason why you feel it is necessary (other bugs it fixes,
  etc.)
  
  related bug: https://bugs.launchpad.net/ubuntu/+bug/1
  
  In NVIDIA new GPU release cycle, NVIDIA ships their new GPUs to OEM/ODM for 
production.
  In the meantime, NVIDIA usually notify OEM/ODM/Canonical (under NDA) to use a 
specific nvidia version to development/production.
  
  NVIDIA and OEN/ODM will announce the next generation combination at the
  same time usually when the factory ready to ship the product.
  
  We made Ubuntu as a leading distribution supports many cutting edge
  devices, it's time to have an official way to make the nvidia
  installation consistent in unannounced (yet) nvidia devices to support
  OEM/ODM factory shipment for our growing counterparts.
  
  > attach (as files)
  > diff of the Upstream ChangeLog (not debian/changelog)
  > diff -u -{old-version,new-version}/ChangeLog > changelog.diff
  note that the ChangeLog sometimes is called CHANGES, is missing or the 
tarball merely has a NEWS file.
  > the NEWS file, if you think that this information helps reviewing your 
request (true for most gnome packages)
  
  N/A, FWIK, u-d-c hasn't an official release note something like "NEWS"
  
  > build log (as file)
  
  Please refer the attachment "buildlog"
  
  > install log
  
  Please refer the attachment "installlog"
  
  > mention what testing you've done to see that it works
  
  TBC, I'll provide soon.
  
  > subscribe (do not assign to) the 'ubuntu-release' team.
  
  TBC, will subscribe them after completing the materials.
+ 
+ ---
+ 
+ [Additional information]
+ * Jammy MP: https://github.com/tseliot/ubuntu-drivers-common/pull/81

** Description changed:

  > If the upload is a new upstream microrelease, the relevant part of the
  upstream changelog and/or release notes
  
  Upstream commit: https://github.com/tseliot/ubuntu-drivers-
  common/commit/a7d2d39805e995ed0e655de123b4bb6cff4e6434
  
  > An explanation of the testing which has been performed on the new
  version in Ubuntu, including verification that the new package:
  
  For this feature which only impact if the target system has a custom
  file "/etc/custom_supported_gpus.json"
  
  If the file presents, it will effect packages_for_modalias() and
  _is_runtimepm_supported(). Both functions are important when "ubuntu-
  driver install" a nvidia driver.
  
  For installing nvidia driver, u-d-c has several test in autopkgtest which 
contains:
  * different branch type: LTS/PB/NFB/Legacy..
  * different version type: 390/470/495/510..
  * For this particular feature, we created a new autopkgtest 
test_system_driver_packages_force_install_nvidia() which not only secure this 
FFE but each version bump.
  which contains:
  1. Normal case (Stock ubuntu), without /etc/customized_supported_gpus.json in 
the system.
  2. If /etc/custom_supported_gpus.json contains incorrect json field / format.
  3. /etc/custom_supported_gpus.json point to the older version than candidate.
  4. /etc/custom_supported_gpus.json point to the same version than candidate.
  5. /etc/custom_supported_gpus.json point to a non-exist version of 
ubuntu-archive (source list).
  
  and you can see from "buildlog" attachment, all passed as well as
  

[Desktop-packages] [Bug 1990341] Re: [FeatureFreeze Exceptions] Support to install nvidia driver by allowing list

2023-01-02 Thread jeremyszu
** Description changed:

  > If the upload is a new upstream microrelease, the relevant part of the
  upstream changelog and/or release notes
  
  Upstream commit: https://github.com/tseliot/ubuntu-drivers-
  common/commit/a7d2d39805e995ed0e655de123b4bb6cff4e6434
  
  > An explanation of the testing which has been performed on the new
  version in Ubuntu, including verification that the new package:
  
- I will build a version soon. TBC
+ For this feature which only impact if the target system has a custom
+ file "/etc/custom_supported_gpus.json"
+ 
+ If the file presents, it will effect packages_for_modalias() and
+ _is_runtimepm_supported(). Both functions are important when "ubuntu-
+ driver install" a nvidia driver.
+ 
+ For installing nvidia driver, u-d-c has several test in autopkgtest which 
contains:
+ * different branch type: LTS/PB/NFB/Legacy..
+ * different version type: 390/470/495/510..
+ * For this particular feature, we created a new autopkgtest 
test_system_driver_packages_force_install_nvidia() which not only secure this 
FFE but each version bump.
+ which contains:
+ 1. Normal case (Stock ubuntu), without /etc/customized_supported_gpus.json in 
the system.
+ 2. If /etc/custom_supported_gpus.json contains incorrect json field / format.
+ 3. /etc/custom_supported_gpus.json point to the older version than candidate.
+ 4. /etc/custom_supported_gpus.json point to the same version than candidate.
+ 5. /etc/custom_supported_gpus.json point to a non-exist version of 
ubuntu-archive (source list).
+ 
+ and you can see from "buildlog" attachment, all passed as well as
+ "test_system_driver_packages_force_install_nvidia()"
+ 
+ Refer https://github.com/tseliot/ubuntu-drivers-common/pull/71 for more
+ details.
  
  > state the reason why you feel it is necessary (other bugs it fixes,
  etc.)
  
  related bug: https://bugs.launchpad.net/ubuntu/+bug/1
  
  In NVIDIA new GPU release cycle, NVIDIA ships their new GPUs to OEM/ODM for 
production.
  In the meantime, NVIDIA usually notify OEM/ODM/Canonical (under NDA) to use a 
specific nvidia version to development/production.
  
  NVIDIA and OEN/ODM will announce the next generation combination at the
  same time usually when the factory ready to ship the product.
  
  We made Ubuntu as a leading distribution supports many cutting edge
  devices, it's time to have an official way to make the nvidia
  installation consistent in unannounced (yet) nvidia devices to support
  OEM/ODM factory shipment for our growing counterparts.
  
  > attach (as files)
  > diff of the Upstream ChangeLog (not debian/changelog)
  > diff -u -{old-version,new-version}/ChangeLog > changelog.diff
  note that the ChangeLog sometimes is called CHANGES, is missing or the 
tarball merely has a NEWS file.
  > the NEWS file, if you think that this information helps reviewing your 
request (true for most gnome packages)
  
  N/A, FWIK, u-d-c hasn't an official release note something like "NEWS"
  
  > build log (as file)
  
- As the attachment "buildlog"
+ Please refer the attachment "buildlog"
  
  > install log
  
- TBC, I'll provide soon.
+ Please refer the attachment "installlog"
  
  > mention what testing you've done to see that it works
  
  TBC, I'll provide soon.
  
  > subscribe (do not assign to) the 'ubuntu-release' team.
  
  TBC, will subscribe them after completing the materials.

** Attachment added: "installlog"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1990341/+attachment/5638895/+files/installlog

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

Title:
  [FeatureFreeze Exceptions] Support to install nvidia driver by
  allowing list

Status in OEM Priority Project:
  In Progress
Status in ubuntu-drivers-common package in Ubuntu:
  New

Bug description:
  > If the upload is a new upstream microrelease, the relevant part of
  the upstream changelog and/or release notes

  Upstream commit: https://github.com/tseliot/ubuntu-drivers-
  common/commit/a7d2d39805e995ed0e655de123b4bb6cff4e6434

  > An explanation of the testing which has been performed on the new
  version in Ubuntu, including verification that the new package:

  For this feature which only impact if the target system has a custom
  file "/etc/custom_supported_gpus.json"

  If the file presents, it will effect packages_for_modalias() and
  _is_runtimepm_supported(). Both functions are important when "ubuntu-
  driver install" a nvidia driver.

  For installing nvidia driver, u-d-c has several test in autopkgtest which 
contains:
  * different branch type: LTS/PB/NFB/Legacy..
  * different version type: 390/470/495/510..
  * For this particular feature, we created a new autopkgtest 
test_system_driver_packages_force_install_nvidia() which not only secure this 
FFE but each version bump.
  which contains:
  1. Normal case (Stock ubuntu), without 

[Desktop-packages] [Bug 1990341] Re: [FeatureFreeze Exceptions] Support to install nvidia driver by allowing list

2023-01-02 Thread jeremyszu
build log

** Description changed:

  > If the upload is a new upstream microrelease, the relevant part of the
  upstream changelog and/or release notes
  
  Upstream commit: https://github.com/tseliot/ubuntu-drivers-
  common/commit/a7d2d39805e995ed0e655de123b4bb6cff4e6434
  
  > An explanation of the testing which has been performed on the new
  version in Ubuntu, including verification that the new package:
  
  I will build a version soon. TBC
  
  > state the reason why you feel it is necessary (other bugs it fixes,
  etc.)
  
  related bug: https://bugs.launchpad.net/ubuntu/+bug/1
  
  In NVIDIA new GPU release cycle, NVIDIA ships their new GPUs to OEM/ODM for 
production.
  In the meantime, NVIDIA usually notify OEM/ODM/Canonical (under NDA) to use a 
specific nvidia version to development/production.
  
  NVIDIA and OEN/ODM will announce the next generation combination at the
  same time usually when the factory ready to ship the product.
  
  We made Ubuntu as a leading distribution supports many cutting edge
  devices, it's time to have an official way to make the nvidia
  installation consistent in unannounced (yet) nvidia devices to support
  OEM/ODM factory shipment for our growing counterparts.
  
  > attach (as files)
  > diff of the Upstream ChangeLog (not debian/changelog)
  > diff -u -{old-version,new-version}/ChangeLog > changelog.diff
  note that the ChangeLog sometimes is called CHANGES, is missing or the 
tarball merely has a NEWS file.
  > the NEWS file, if you think that this information helps reviewing your 
request (true for most gnome packages)
  
  N/A, FWIK, u-d-c hasn't an official release note something like "NEWS"
  
  > build log (as file)
  
- TBC, I'll provide soon.
+ As the attachment "buildlog"
  
  > install log
  
  TBC, I'll provide soon.
  
  > mention what testing you've done to see that it works
  
  TBC, I'll provide soon.
  
  > subscribe (do not assign to) the 'ubuntu-release' team.
  
  TBC, will subscribe them after completing the materials.

** Attachment added: "buildlog"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1990341/+attachment/5638891/+files/buildlog_ubuntu-jammy-amd64.ubuntu-drivers-common_1%200.9.6.2~0.22.04.1+lp1990341_BUILDING.txt.gz

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

Title:
  [FeatureFreeze Exceptions] Support to install nvidia driver by
  allowing list

Status in OEM Priority Project:
  In Progress
Status in ubuntu-drivers-common package in Ubuntu:
  New

Bug description:
  > If the upload is a new upstream microrelease, the relevant part of
  the upstream changelog and/or release notes

  Upstream commit: https://github.com/tseliot/ubuntu-drivers-
  common/commit/a7d2d39805e995ed0e655de123b4bb6cff4e6434

  > An explanation of the testing which has been performed on the new
  version in Ubuntu, including verification that the new package:

  I will build a version soon. TBC

  > state the reason why you feel it is necessary (other bugs it fixes,
  etc.)

  related bug: https://bugs.launchpad.net/ubuntu/+bug/1

  In NVIDIA new GPU release cycle, NVIDIA ships their new GPUs to OEM/ODM for 
production.
  In the meantime, NVIDIA usually notify OEM/ODM/Canonical (under NDA) to use a 
specific nvidia version to development/production.

  NVIDIA and OEN/ODM will announce the next generation combination at
  the same time usually when the factory ready to ship the product.

  We made Ubuntu as a leading distribution supports many cutting edge
  devices, it's time to have an official way to make the nvidia
  installation consistent in unannounced (yet) nvidia devices to support
  OEM/ODM factory shipment for our growing counterparts.

  > attach (as files)
  > diff of the Upstream ChangeLog (not debian/changelog)
  > diff -u -{old-version,new-version}/ChangeLog > changelog.diff
  note that the ChangeLog sometimes is called CHANGES, is missing or the 
tarball merely has a NEWS file.
  > the NEWS file, if you think that this information helps reviewing your 
request (true for most gnome packages)

  N/A, FWIK, u-d-c hasn't an official release note something like "NEWS"

  > build log (as file)

  As the attachment "buildlog"

  > install log

  TBC, I'll provide soon.

  > mention what testing you've done to see that it works

  TBC, I'll provide soon.

  > subscribe (do not assign to) the 'ubuntu-release' team.

  TBC, will subscribe them after completing the materials.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1990341/+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 1966635] Re: can't move file/directory by drag and drop by using touch monitor

2023-01-02 Thread Andy Chi
** Tags added: originate-from-2000750

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

Title:
  can't move file/directory by drag and drop by using touch monitor

Status in Mutter:
  New
Status in OEM Priority Project:
  Confirmed
Status in mutter package in Ubuntu:
  New
Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  Can't move file/directory by drag and drop by using a touch monitor

  OS: 22.04, up to date @ Mar 28, 2022.
  nautilus: 1:42~rc-1-ubuntu1
  mode: wayland

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1966635/+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 872868] Re: Mesa: Enable HW video decoding

2023-01-02 Thread Bug Watch Updater
** Changed in: mesa (Debian)
   Status: New => Fix Released

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

Title:
  Mesa: Enable HW video decoding

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa package in Debian:
  Fix Released

Bug description:
  Radeon r600g (and maybe r300 and nouveau) driver in upstream mesa +
  xorg-video-* git have (partial) support for XvMC, Vdpau and VAAPI.
  Support can be enabled at compile time.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/872868/+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 2000869] [NEW] Java missing in Writer, periodically asked even after months resolved

2023-01-02 Thread Hernan
Public bug reported:

I still continue to receive the same warning message, periodically (some 
months) in LibreOffice Writer.
The message says I have to specify the Java for my system, even though I have 
already done it months ago.
Last time (02-January-2023) happened when I wanted to resize an image.

My system and Writer versions:


-- OS:
cat /etc/os-release

NAME="Ubuntu"
VERSION="20.04.5 LTS (Focal Fossa)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 20.04.5 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

--LibreOffice version:
snap find libreoffice
Name  VersionPublisher   Notes  Summary
libreoffice   7.4.3.2canonical✓  -  LibreOffice is a free and open 
source office suite


Version: 7.4.3.2 / LibreOffice Community
Build ID: 8d7af0b9f05ca3f6bf3593323f061d3291e2ce28
CPU threads: 4; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: it-IT (en_US.UTF-8); UI: en-US
Calc: threaded


Thank for your support
Hernan Vago

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


** Tags: java snap

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

Title:
  Java missing in Writer, periodically asked even after months resolved

Status in libreoffice package in Ubuntu:
  New

Bug description:
  I still continue to receive the same warning message, periodically (some 
months) in LibreOffice Writer.
  The message says I have to specify the Java for my system, even though I have 
already done it months ago.
  Last time (02-January-2023) happened when I wanted to resize an image.

  My system and Writer versions:

  
  -- OS:
  cat /etc/os-release

  NAME="Ubuntu"
  VERSION="20.04.5 LTS (Focal Fossa)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 20.04.5 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

  --LibreOffice version:
  snap find libreoffice
  Name  VersionPublisher   Notes  Summary
  libreoffice   7.4.3.2canonical✓  -  LibreOffice is a free and open 
source office suite

  
  Version: 7.4.3.2 / LibreOffice Community
  Build ID: 8d7af0b9f05ca3f6bf3593323f061d3291e2ce28
  CPU threads: 4; OS: Linux 5.15; UI render: default; VCL: gtk3
  Locale: it-IT (en_US.UTF-8); UI: en-US
  Calc: threaded

  
  Thank for your support
  Hernan Vago

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2000869/+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 892476]

2023-01-02 Thread Libreoffice-z
*** Bug 152838 has been marked as a duplicate of this bug. ***

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

Title:
  [Upstream] Regular expression "\n" in replace field inputs "\n"
  instead of paragraph break

Status in LibreOffice:
  Confirmed
Status in libreoffice package in Ubuntu:
  Triaged

Bug description:
  1) lsb_release -rd
  Description:Ubuntu 11.10
  Release:11.10

  2) apt-cache policy libreoffice-calc
  libreoffice-calc:
Installed: 1:3.4.4-0ubuntu1~ppa1
Candidate: 1:3.4.4-0ubuntu1~ppa1
Version table:
   *** 1:3.4.4-0ubuntu1~ppa1 0
  500 http://ppa.launchpad.net/libreoffice/ppa/ubuntu/ oneiric/main i386
  Packages
  100 /var/lib/dpkg/status
   1:3.4.3-3ubuntu2 0
  500 http://us.archive.ubuntu.com/ubuntu/ oneiric/main i386 Packages

  3) What is expected to happen in LibreOffice Calc is when one of the cells
  contains a line break -> Edit -> Find and Replace... -> in the "Search for"
  drop down \n -> in the "Replace with" drop down \n -> Regular expression 
button
  checked is the line break is replaced with a paragraph break as noted in
  http://help.libreoffice.org/Common/List_of_Regular_Expressions

  4) What happens instead is the line break is replaced with the
  characters \n

  ProblemType: BugDistroRelease: Ubuntu 11.10
  Package: libreoffice-calc 1:3.4.3-3ubuntu2
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic x86_64
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  Date: Sat Nov 19 13:02:28 2011
  EcryptfsInUse: YesInstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - 
Release amd64 (20101007)SourcePackage: libreoffice
  UpgradeStatus: Upgraded to oneiric on 2011-10-16 (34 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/892476/+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 1832426] Re: "Program" is not responding when debugging in gdb

2023-01-02 Thread ekso
I also have this problem when hitting a breakpoint in Unreal 5.1 from
JetBrains Rider 2022.3.1 while in vanilla Ubuntu 22.04. When the window
shows it actually makes the mouse pointer disappear and I have to rely
on the keyboard to "Force Quit" to get the pointer back.

The "Disable Force Quit or Wait" gnome-shell extension does work and
solves the problem: https://extensions.gnome.org/extension/2257/disable-
force-quit-or-wait-button/

With that being said, I have to agree with Daniel van Vugt on comment
#4, the status on Unreal PID does change from "S" to "t" when the
breakpoint is hit.

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

Title:
  "Program" is not responding when debugging in gdb

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  I believe this is a regression for ​​bug 1740869:
   is not responding window is constantly showing when debugging a 
program

  I'm debugging my c++ sdl2 program in gdb and when I hit a breakpoint
  this window shows up and I can't get it to stop asking me to close the
  program.

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  Description:  Ubuntu 19.04
  Release:  19.04

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  gnome-shell:
    Installed: 3.32.1-1ubuntu1~19.04.1
    Candidate: 3.32.1-1ubuntu1~19.04.1
    Version table:
   *** 3.32.1-1ubuntu1~19.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu disco-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.32.0+git20190410-1ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages

  3) What you expected to happen
  When I hit a breakpoint in gdb, the program should stop.

  4) What happened instead
  The program stops and ubuntu asks me if i want to kill the program.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.1-1ubuntu1~19.04.1
  ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8
  Uname: Linux 5.0.0-16-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 11 22:03:44 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-06-08 (4 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  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/1832426/+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


Re: [Desktop-packages] [Bug 2000396] [NEW] installing snap chromium trashed my pre-snap files

2023-01-02 Thread Kathleen Caywood
On 1/2/23 06:49, Nathan Teodosio wrote:
> Thanks for the report Kathleen, and sorry to hear that your
> configuration was affected.
>
>   > Most of my bookmarks, passwords, etc., from the pre-snap version of
>   > chromium are gone
>
> How did you conclude this? Was it by observing Chromium itself, or did
> you inspect the filesystem to ascertain it?

I had been having frequent hangs with my 4-year-old Ryzen 5 1400 
system.  In the process of debugging, I replaced my boot drive, which 
also had /home on it.  When I installed ubuntu a year ago, I downloaded 
and installed chromium from your website.  It was not the snap version.

This time I reinstalled after installing the new drive (500G M.2), and 
the ubuntu installer did not install chromium.  I went looking, and it 
appeared that snap-chromium was now the preferred version, so I 
installed it.

When I did, I found I no longer had any bookmarks, passwords, etc., and 
inspected the file system.  Please do not try to lay this at the feet of 
the M.2 drive or the ubuntu installer.

>
> The Chromium deb stores its configuration files in
> $HOME/.config/chromium, whereas the snap in $HOME/snap/chromium/common.
>

-- 
  Kathleen M. Caywood, emailkmcayw...@cox.net

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

Title:
  installing snap chromium trashed my pre-snap files

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Most of my bookmarks, passwords, etc., from the pre-snap version of
  chromium are gone since I installed snap chromium.

  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

  
  chromium-browser:
Installed: 1:85.0.4183.83-0ubuntu2
Candidate: 1:85.0.4183.83-0ubuntu2
Version table:
   *** 1:85.0.4183.83-0ubuntu2 500
  500 http://us.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages
  100 /var/lib/dpkg/status

  I expected my most recent bookmarks and files to be accessible after
  replacing the non-snap chromium with the snap chromium

  Instead, the only version of book marks, configuration, passwords,
  etc., are several years old

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2000396/+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 2000868] [NEW] backport required for virtio_gpu_dri.so

2023-01-02 Thread mohan43u
Public bug reported:

Hi,

xorg crashing when using modsetting with virtio_gpu_dri as graphics
driver in kvm guest. Kindly look into this conversation

https://gitlab.freedesktop.org/virgl/virglrenderer/-/issues/291#note_1701920

I think we need to backport
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/19655 to fix
this issue.

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

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

Title:
  backport required for virtio_gpu_dri.so

Status in mesa package in Ubuntu:
  New

Bug description:
  Hi,

  xorg crashing when using modsetting with virtio_gpu_dri as graphics
  driver in kvm guest. Kindly look into this conversation

  https://gitlab.freedesktop.org/virgl/virglrenderer/-/issues/291#note_1701920

  I think we need to backport
  https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/19655 to fix
  this issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2000868/+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 1998409] Re: [snap] chromium fails to start: unsupported version 0 of Verneed record

2023-01-02 Thread Dmitriy Gorbenko
Some articles say the issue is SNAP related, and I saw a patch to the SNAP 
daemon which fixes it.
Sorry, I don't remember the link to that post.

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

Title:
  [snap] chromium fails to start: unsupported version 0 of Verneed
  record

Status in chromium-browser package in Ubuntu:
  New
Status in firefox package in Ubuntu:
  New

Bug description:
  Description:Ubuntu 22.04.1 LTS
  Release:22.04
  Just updated before trying to run the chromium.

  $ chromium-browser

  /bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8)
  mkdir: error while loading shared libraries: 
/snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: 
unsupported version 0 of Verneed record
  mkdir: error while loading shared libraries: 
/snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: 
unsupported version 0 of Verneed record
  mkdir: error while loading shared libraries: 
/snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: 
unsupported version 0 of Verneed record
  sed: error while loading shared libraries: 
/snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: 
unsupported version 0 of Verneed record
  md5sum: error while loading shared libraries: 
/snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: 
unsupported version 0 of Verneed record
  cp: error while loading shared libraries: 
/snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: 
unsupported version 0 of Verneed record
  md5sum: error while loading shared libraries: 
/snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: 
unsupported version 0 of Verneed record
  xdg-user-dirs-update: error while loading shared libraries: 
/snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: 
unsupported version 0 of Verneed record
  rm: error while loading shared libraries: 
/snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: 
unsupported version 0 of Verneed record
  mkdir: error while loading shared libraries: 
/snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: 
unsupported version 0 of Verneed record
  /snap/chromium/2221/snap/command-chain/desktop-launch: line 406: 
/home/USER/snap/chromium/2221/.config/fontconfig/fonts.conf: No such file or 
directory
  ln: error while loading shared libraries: 
/snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: 
unsupported version 0 of Verneed record
  ln: error while loading shared libraries: 
/snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: 
unsupported version 0 of Verneed record
  rm: error while loading shared libraries: 
/snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: 
unsupported version 0 of Verneed record
  mkdir: error while loading shared libraries: 
/snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: 
unsupported version 0 of Verneed record
  rm: error while loading shared libraries: 
/snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: 
unsupported version 0 of Verneed record
  rm: error while loading shared libraries: 
/snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: 
unsupported version 0 of Verneed record
  ln: error while loading shared libraries: 
/snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: 
unsupported version 0 of Verneed record
  mkdir: error while loading shared libraries: 
/snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: 
unsupported version 0 of Verneed record
  mkdir: error while loading shared libraries: 
/snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: 
unsupported version 0 of Verneed record
  rm: error while loading shared libraries: 
/snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: 
unsupported version 0 of Verneed record
  ln: error while loading shared libraries: 
/snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: 
unsupported version 0 of Verneed record
  /snap/chromium/2221/snap/command-chain/desktop-launch: line 500: 
/home/USER/snap/chromium/common/.cache/gdk-pixbuf-loaders.cache: No such file 
or directory
  rm: error while loading shared libraries: 
/snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: 
unsupported version 0 of Verneed record
  
/snap/chromium/2221/gnome-platform/usr/lib/x86_64-linux-gnu/glib-2.0/gio-querymodules:
 error while loading shared libraries: 
/snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: 
unsupported version 0 of Verneed record
  mkdir: error while loading shared libraries: 

[Desktop-packages] [Bug 1063991] Re: mupen64plus crashes with illegal instruction

2023-01-02 Thread Oibaf
Is this still an issue?

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

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

Title:
  mupen64plus crashes with illegal instruction

Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  haver@gamemaster:~$ mupen64plus n64/Mario_Kart_64/Mario\ Kart\ 64\ 
\(USA\).n64 
   __  __ __   _  _     _ 
  |  \/  |_   _ _ __   ___ _ __  / /_ | || | |  _ \| |_   _ ___ 
  | |\/| | | | | '_ \ / _ \ '_ \| '_ \| || |_| |_) | | | | / __|  
  | |  | | |_| | |_) |  __/ | | | (_) |__   _|  __/| | |_| \__ \  
  |_|  |_|\__,_| .__/ \___|_| |_|\___/   |_| |_|   |_|\__,_|___/  
   |_| http://code.google.com/p/mupen64plus/  
  Mupen64Plus Console User-Interface Version 1.99.4

  UI-console: attached to core library 'Mupen64Plus Core' version 1.99.4
  Includes support for Dynamic Recompiler.
  Core: Goodname: Mario Kart 64 (U) [!]
  Core: Name: MARIOKART64
  Core: MD5: 3A67D9986F54EB282924FCA4CD5F6DFF
  Core: CRC: 3e5055b6 2e92da52
  Core: Imagetype: .v64 (byteswapped)
  Core: Rom size: 12582912 bytes (or 12 Mb or 96 Megabits)
  Core: Version: 1446
  Core: Manufacturer: Nintendo
  Core: Country: USA
  UI-Console: Cheat codes disabled.
  UI-console: using Video plugin: 'Mupen64Plus OpenGL Video Plugin by Rice' 
v1.99.4
  UI-console: using Audio plugin: 'Mupen64Plus SDL Audio Plugin' v1.99.4
  Input: N64 Controller #1: Forcing default keyboard configuration
  Input: Using auto-configuration for device 'Keyboard'
  UI-console: using Input plugin: 'Mupen64Plus SDL Input Plugin' v1.99.4
  UI-console: using RSP plugin: 'Hacktarux/Azimer High-Level Emulation RSP 
Plugin' v1.99.4
  Input: N64 Controller #1: Using keyboard/mouse
  Input: 1 controller(s) found, 1 plugged in and usable in the emulator
  Input: Mupen64Plus SDL Input Plugin version 1.99.4 initialized.
  Video: SSE processing enabled.
  Video: Found ROM 'Mario Kart 64', CRC b655503e52da922e-45
  Video: Enabled hacks for game: 'MARIOKART64'
  Video: Initializing OpenGL Device Context.
  Core: Setting 32-bit video mode: 640x480
  Video: Using OpenGL: Tungsten Graphics, Inc - Mesa DRI Intel(R) 945G  : 1.4 
Mesa 8.0.4
  Video: OpenGL Combiner: Fragment Program
  Audio: Initializing SDL audio subsystem...
  /dev/mixer: : No such file or directory
  Core: Starting R4300 emulator: Dynamic Recompiler
  Core: R4300: starting 64-bit dynamic recompiler at: 0x7fa578049200
  /dev/mixer: : No such file or directory
  Illegal instruction (core dumped)

  The window is popping up and after a while I am seeing an illegal
  instruction error.

  Here the end of the strace run:

  stat("/home/haver", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
  stat("/home", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
  stat("/home/haver", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
  stat("/home/haver/.local", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
  stat("/home/haver/.local/share", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
  stat("/home/haver/.local/share/mupen64plus", {st_mode=S_IFDIR|0700, 
st_size=4096, ...}) = 0
  stat("/home/haver/.local/share/mupen64plus/", {st_mode=S_IFDIR|0700, 
st_size=4096, ...}) = 0
  stat("/home", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
  stat("/home/haver", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
  stat("/home/haver/.local", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
  stat("/home/haver/.local/share", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
  stat("/home/haver/.local/share/mupen64plus", {st_mode=S_IFDIR|0700, 
st_size=4096, ...}) = 0
  stat("/home/haver/.local/share/mupen64plus/save", {st_mode=S_IFDIR|0700, 
st_size=4096, ...}) = 0
  stat("/home/haver/.local/share/mupen64plus/save/", {st_mode=S_IFDIR|0700, 
st_size=4096, ...}) = 0
  open("/home/haver/.local/share/mupen64plus/save/Mario Kart 64 (U) [!].mpk", 
O_RDONLY) = 9
  fstat(9, {st_mode=S_IFREG|0664, st_size=131072, ...}) = 0
  mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7ff9f327b000
  read(9, 
"\201\1\2\3\4\5\6\7\10\t\n\v\f\r\16\17\20\21\22\23\24\25\26\27\30\31\32\33\34\35\36\37"...,
 32768) = 32768
  read(9, 
"\201\1\2\3\4\5\6\7\10\t\n\v\f\r\16\17\20\21\22\23\24\25\26\27\30\31\32\33\34\35\36\37"...,
 32768) = 32768
  read(9, 
"\201\1\2\3\4\5\6\7\10\t\n\v\f\r\16\17\20\21\22\23\24\25\26\27\30\31\32\33\34\35\36\37"...,
 32768) = 32768
  read(9, 
"\201\1\2\3\4\5\6\7\10\t\n\v\f\r\16\17\20\21\22\23\24\25\26\27\30\31\32\33\34\35\36\37"...,
 32768) = 32768
  close(9)= 0
  munmap(0x7ff9f327b000, 4096)= 0
  open("/home/haver/.local/share/mupen64plus/save/Mario Kart 64 (U) [!].mpk", 
O_WRONLY|O_CREAT|O_TRUNC, 0666) = 9
  fstat(9, {st_mode=S_IFREG|0664, st_size=0, ...}) = 0
  mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 

[Desktop-packages] [Bug 1068553] Re: package libgl1-mesa-dri 9.0-0ubuntu1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libgl1-mesa-dri/changelog.Debian.gz', which is different

2023-01-02 Thread Oibaf
10+ years old upgrade bug. Is it still an issue?

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

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

Title:
  package libgl1-mesa-dri 9.0-0ubuntu1 failed to install/upgrade: trying
  to overwrite shared '/usr/share/doc/libgl1-mesa-
  dri/changelog.Debian.gz', which is different from other instances of
  package libgl1-mesa-dri:amd64

Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  This was an automatic bug report.

  ProblemType: Package
  DistroRelease: Ubuntu 12.10
  Package: libgl1-mesa-dri 9.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
  Uname: Linux 3.5.0-17-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  304.51  Tue Sep 18 17:16:56 
PDT 2012
   GCC version:  gcc version 4.7.2 (Ubuntu/Linaro 4.7.2-2ubuntu1)
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.6.1-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  Date: Fri Oct 19 22:51:29 2012
  DistUpgraded: 2012-10-19 22:38:49,539 DEBUG enabling apt cron job
  DistroCodename: quantal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia-current-updates, 304.51, 3.2.0-32-generic, x86_64: installed
   nvidia-current-updates, 304.51, 3.5.0-17-generic, x86_64: installed
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libgl1-mesa-dri/changelog.Debian.gz', which is different from 
other instances of package libgl1-mesa-dri:amd64
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GF114 [GeForce GTX 560 Ti] [10de:1200] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. Device [1462:2384]
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  JockeyStatus:
   kmod:nvidia_experimental_304 - Experimental NVIDIA binary Xorg driver, 
kernel module and VDPAU library (Proprietary, Disabled, Not in use)
   kmod:nvidia_current - NVIDIA binary Xorg driver, kernel module and VDPAU 
library (Proprietary, Disabled, Not in use)
   kmod:nvidia_current_updates - nvidia_current_updates (Proprietary, Enabled, 
Not in use)
  MachineType: Gigabyte Technology Co., Ltd. EX38-DQ6
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic 
root=UUID=a4f5de5c-8804-4fe0-a0f1-22ca034917f3 ro quiet splash elevator=deadline
  SourcePackage: mesa
  Title: package libgl1-mesa-dri 9.0-0ubuntu1 failed to install/upgrade: trying 
to overwrite shared '/usr/share/doc/libgl1-mesa-dri/changelog.Debian.gz', which 
is different from other instances of package libgl1-mesa-dri:amd64
  UpgradeStatus: Upgraded to quantal on 2012-10-19 (0 days ago)
  dmi.bios.date: 04/24/2009
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F4B
  dmi.board.name: EX38-DQ6
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF4B:bd04/24/2009:svnGigabyteTechnologyCo.,Ltd.:pnEX38-DQ6:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEX38-DQ6:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: EX38-DQ6
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.8.4-0ubuntu3
  version.ia32-libs: ia32-libs 20090808ubuntu36
  version.libdrm2: libdrm2 2.4.39-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.0-0ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.99.99~git20120913.8637f772-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.2-0ubuntu3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1068553/+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 1071531] Re: package libgl1-mesa-dri 8.0.3+8.0.2-0ubuntu3.2 failed to install/upgrade: libgl1-mesa-dri:amd64. The i386 packages seem to conflict with my 64-bit AMD machine and

2023-01-02 Thread Oibaf
Is this still an issue?

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

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

Title:
  package libgl1-mesa-dri 8.0.3+8.0.2-0ubuntu3.2 failed to
  install/upgrade: libgl1-mesa-dri:amd64. The i386 packages seem to
  conflict with my 64-bit AMD machine and disable Synaptic.

Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  I keep getting constant error messages that tell me that Ubuntu
  Software Center will not function until these unmet dependencies are
  resolved, and they can't be resolved.

  ProblemType: Package
  DistroRelease: Ubuntu 12.04
  Package: libgl1-mesa-dri 8.0.3+8.0.2-0ubuntu3.2
  ProcVersionSignature: Ubuntu 3.2.0-27.43-generic 3.2.21
  Uname: Linux 3.2.0-27-generic x86_64
  NonfreeKernelModules: fglrx
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.0.1-0ubuntu11
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  Date: Thu Oct 25 18:49:42 2012
  DistUpgraded: Fresh install
  DistroCodename: precise
  DistroVariant: ubuntu
  DkmsStatus:
   fglrx-updates, 8.960, 3.2.0-23-generic, x86_64: installed
   fglrx-updates, 8.960, 3.2.0-24-generic, x86_64: installed
   fglrx-updates, 8.960, 3.2.0-27-generic, x86_64: installed
  DpkgTerminalLog:
   dpkg: error processing libgl1-mesa-dri:i386 (--configure):
libgl1-mesa-dri:i386 8.0.2-0ubuntu3.1 cannot be configured because 
libgl1-mesa-dri:amd64 is in a different version (8.0.3+8.0.2-0ubuntu3.2)
   dpkg: error processing libgl1-mesa-dri (--configure):
libgl1-mesa-dri:amd64 8.0.3+8.0.2-0ubuntu3.2 cannot be configured because 
libgl1-mesa-dri:i386 is in a different version (8.0.2-0ubuntu3.1)
  ErrorMessage: libgl1-mesa-dri:amd64 8.0.3+8.0.2-0ubuntu3.2 cannot be 
configured because libgl1-mesa-dri
  ExtraDebuggingInterest: I just need an easy workaround
  GraphicsCard:
   Advanced Micro Devices [AMD] nee ATI Device [1002:9647] (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company Device [103c:169b]
  JockeyStatus:
   xorg:fglrx_updates - ATI/AMD proprietary FGLRX graphics driver (post-release 
updates) (Proprietary, Disabled, Not in use)
   xorg:fglrx - ATI/AMD proprietary FGLRX graphics driver (Proprietary, 
Disabled, Not in use)
  MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-27-generic 
root=UUID=34B0B293B0B25AD6 loop=/hostname/disks/root.disk ro quiet splash 
vt.handoff=7
  SourcePackage: mesa
  Title: package libgl1-mesa-dri 8.0.3+8.0.2-0ubuntu3.2 failed to 
install/upgrade: libgl1-mesa-dri:amd64 8.0.3+8.0.2-0ubuntu3.2 cannot be 
configured because libgl1-mesa-dri
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/16/2012
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.46
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 169B
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 18.1A
  dmi.chassis.asset.tag: 5CG2070LFS
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.46:bd01/16/2012:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr06901320461620100:rvnHewlett-Packard:rn169B:rvrKBCVersion18.1A:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion g6 Notebook PC
  dmi.product.version: 06901320461620100
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.7.8-0ubuntu1.2
  version.fglrx-installer: fglrx-installer N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.32-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.3+8.0.2-0ubuntu3.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10.6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1.2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.14.99~git20111219.aacbd629-0ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:0.0.16+git20111201+b5534a1-1build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1071531/+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 1080575] Re: package libglapi-mesa 9.0-0ubuntu1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libglapi-mesa/changelog.Debian.gz', which is different fro

2023-01-02 Thread Oibaf
Is this still an issue?

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

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

Title:
  package libglapi-mesa 9.0-0ubuntu1 failed to install/upgrade: trying
  to overwrite shared '/usr/share/doc/libglapi-
  mesa/changelog.Debian.gz', which is different from other instances of
  package libglapi-mesa:amd64

Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  crash after upgrade from 12.04 to 12.10

  ProblemType: Package
  DistroRelease: Ubuntu 12.10
  Package: libglapi-mesa 9.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7
  Uname: Linux 3.5.0-18-generic x86_64
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  Date: Sun Nov 18 01:42:18 2012
  DistUpgraded: 2012-11-18 01:33:26,098 DEBUG enabling apt cron job
  DistroCodename: quantal
  DistroVariant: ubuntu
  DkmsStatus:
   fglrx, 9.000, 3.5.0-18-generic, x86_64: installed
   virtualbox, 4.1.18, 3.2.0-33-generic, x86_64: installed
   virtualbox, 4.1.18, 3.5.0-18-generic, x86_64: installed
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libglapi-mesa/changelog.Debian.gz', which is different from 
other instances of package libglapi-mesa:amd64
  GraphicsCard:
   Advanced Micro Devices [AMD] nee ATI RS880 [Radeon HD 4250] [1002:9715] 
(prog-if 00 [VGA controller])
 Subsystem: ASRock Incorporation Device [1849:9715]
  InstallationDate: Installed on 2011-10-13 (402 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-18-generic 
root=UUID=2c4c4398-c1f6-4a17-b94d-505bec8059e9 ro quiet splash vt.handoff=7
  SourcePackage: mesa
  Title: package libglapi-mesa 9.0-0ubuntu1 failed to install/upgrade: trying 
to overwrite shared '/usr/share/doc/libglapi-mesa/changelog.Debian.gz', which 
is different from other instances of package libglapi-mesa:amd64
  UnitySupportTest:
   Error: command ['/usr/lib/nux/unity_support_test', '-p', '-f'] failed with 
exit code 1: X Error of failed request:  BadRequest (invalid request code or no 
such operation)
 Major opcode of failed request:  153 (GLX)
 Minor opcode of failed request:  19 (X_GLXQueryServerString)
 Serial number of failed request:  22
 Current serial number in output stream:  22
  UpgradeStatus: Upgraded to quantal on 2012-11-17 (1 days ago)
  dmi.bios.date: 06/24/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.20
  dmi.board.name: 880GXH/USB3
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.20:bd06/24/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn880GXH/USB3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: 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.8.4+bzr3407-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.39-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.0-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.2-0ubuntu3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1080575/+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 1162784] Re: [i915] SIGBUS X11 crash from libglx

2023-01-02 Thread Oibaf
The referenced commit is now included in every Ubutu supported version.
Please reopen if the problem still happens with a supported Ubuntu release.

** Changed in: mesa (Ubuntu)
   Status: New => Fix Released

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

Title:
  [i915] SIGBUS  X11 crash from libglx

Status in mesa package in Ubuntu:
  Fix Released

Bug description:
  I have a proprietary application crashing on SIGBUS during a  /dev/dri/card0  
ioctl
  Unfortunately that provides no information at all

  I tried with LIBGL_ALWAYS_INDIRECT=y and the X11 crashed.
  Full Xorg logfile is attached.

  When the X11 crashes this way, I immediately restart it and start the 
application, there is a chance of the error not happening.
  But if there is an Xv client / flashplayer running on another VT, it never 
works.

  ubuntu-bug does not work, reported as #1150335

  This was happening both on Quantal and Raring.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1162784/+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 2000849] Re: [snap] Request: open (and close) stable/ubuntu-23.04 track

2023-01-02 Thread Nathan Teodosio
** Changed in: chromium-browser (Ubuntu)
   Status: New => Triaged

** Changed in: chromium-browser (Ubuntu)
 Assignee: (unassigned) => Nathan Teodosio (nteodosio)

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

Title:
  [snap] Request: open (and close) stable/ubuntu-23.04 track

Status in chromium-browser package in Ubuntu:
  Triaged

Bug description:
  Hi Chromium Maintainers!

  In an effort to revive Edubuntu [1], we (the Edubuntu Team, which
  consists of my wife and I so far) wish to seed both Firefox and
  Chromium. This is because Chromium will be better supported in the
  classroom for collaboration on Google Docs and other web-based
  applications. This was brought to our attention recently in the
  Discourse discussion [2]. We discussed it amongst ourselves and
  decided this was probably a good idea.

  However, once we're approved for official flavor status and have .iso
  images building daily, in order to seed Chromium, it will need a
  stable/ubuntu-yy.mm track opened and closed just like the Firefox team
  does it now.

  There is no immediate rush on this, but I figured the sooner I brought
  this issue forward the better.

  [1] https://discourse.ubuntu.com/t/announcing-edubuntu-revival/32929
  [2] https://discourse.ubuntu.com/t/announcing-edubuntu-revival/32929/13

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2000849/+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


Re: [Desktop-packages] [Bug 2000396] [NEW] installing snap chromium trashed my pre-snap files

2023-01-02 Thread Nathan Teodosio
Thanks for the report Kathleen, and sorry to hear that your 
configuration was affected.

 > Most of my bookmarks, passwords, etc., from the pre-snap version of
 > chromium are gone

How did you conclude this? Was it by observing Chromium itself, or did 
you inspect the filesystem to ascertain it?

The Chromium deb stores its configuration files in 
$HOME/.config/chromium, whereas the snap in $HOME/snap/chromium/common.

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

Title:
  installing snap chromium trashed my pre-snap files

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Most of my bookmarks, passwords, etc., from the pre-snap version of
  chromium are gone since I installed snap chromium.

  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

  
  chromium-browser:
Installed: 1:85.0.4183.83-0ubuntu2
Candidate: 1:85.0.4183.83-0ubuntu2
Version table:
   *** 1:85.0.4183.83-0ubuntu2 500
  500 http://us.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages
  100 /var/lib/dpkg/status

  I expected my most recent bookmarks and files to be accessible after
  replacing the non-snap chromium with the snap chromium

  Instead, the only version of book marks, configuration, passwords,
  etc., are several years old

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2000396/+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 1998409] Re: [snap] chromium fails to start: unsupported version 0 of Verneed record

2023-01-02 Thread Nathan Teodosio
https://forum.snapcraft.io/t/unsupported-version-0-of-verneed-record-
linux-6-0 suggests it could be a kernel problem.

Try their suggestion there: Either upgrading to 6.0.7 or downgrading to
the 5 series.

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

Title:
  [snap] chromium fails to start: unsupported version 0 of Verneed
  record

Status in chromium-browser package in Ubuntu:
  New
Status in firefox package in Ubuntu:
  New

Bug description:
  Description:Ubuntu 22.04.1 LTS
  Release:22.04
  Just updated before trying to run the chromium.

  $ chromium-browser

  /bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8)
  mkdir: error while loading shared libraries: 
/snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: 
unsupported version 0 of Verneed record
  mkdir: error while loading shared libraries: 
/snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: 
unsupported version 0 of Verneed record
  mkdir: error while loading shared libraries: 
/snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: 
unsupported version 0 of Verneed record
  sed: error while loading shared libraries: 
/snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: 
unsupported version 0 of Verneed record
  md5sum: error while loading shared libraries: 
/snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: 
unsupported version 0 of Verneed record
  cp: error while loading shared libraries: 
/snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: 
unsupported version 0 of Verneed record
  md5sum: error while loading shared libraries: 
/snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: 
unsupported version 0 of Verneed record
  xdg-user-dirs-update: error while loading shared libraries: 
/snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: 
unsupported version 0 of Verneed record
  rm: error while loading shared libraries: 
/snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: 
unsupported version 0 of Verneed record
  mkdir: error while loading shared libraries: 
/snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: 
unsupported version 0 of Verneed record
  /snap/chromium/2221/snap/command-chain/desktop-launch: line 406: 
/home/USER/snap/chromium/2221/.config/fontconfig/fonts.conf: No such file or 
directory
  ln: error while loading shared libraries: 
/snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: 
unsupported version 0 of Verneed record
  ln: error while loading shared libraries: 
/snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: 
unsupported version 0 of Verneed record
  rm: error while loading shared libraries: 
/snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: 
unsupported version 0 of Verneed record
  mkdir: error while loading shared libraries: 
/snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: 
unsupported version 0 of Verneed record
  rm: error while loading shared libraries: 
/snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: 
unsupported version 0 of Verneed record
  rm: error while loading shared libraries: 
/snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: 
unsupported version 0 of Verneed record
  ln: error while loading shared libraries: 
/snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: 
unsupported version 0 of Verneed record
  mkdir: error while loading shared libraries: 
/snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: 
unsupported version 0 of Verneed record
  mkdir: error while loading shared libraries: 
/snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: 
unsupported version 0 of Verneed record
  rm: error while loading shared libraries: 
/snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: 
unsupported version 0 of Verneed record
  ln: error while loading shared libraries: 
/snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: 
unsupported version 0 of Verneed record
  /snap/chromium/2221/snap/command-chain/desktop-launch: line 500: 
/home/USER/snap/chromium/common/.cache/gdk-pixbuf-loaders.cache: No such file 
or directory
  rm: error while loading shared libraries: 
/snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: 
unsupported version 0 of Verneed record
  
/snap/chromium/2221/gnome-platform/usr/lib/x86_64-linux-gnu/glib-2.0/gio-querymodules:
 error while loading shared libraries: 
/snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: 
unsupported version 0 of Verneed record
  mkdir: error while loading shared libraries: 

[Desktop-packages] [Bug 1998409] Re: [snap] chromium fails to start: unsupported version 0 of Verneed record

2023-01-02 Thread Nathan Teodosio
** Also affects: firefox (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  [snap] chromium fails to start: unsupported version 0 of Verneed
  record

Status in chromium-browser package in Ubuntu:
  New
Status in firefox package in Ubuntu:
  New

Bug description:
  Description:Ubuntu 22.04.1 LTS
  Release:22.04
  Just updated before trying to run the chromium.

  $ chromium-browser

  /bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8)
  mkdir: error while loading shared libraries: 
/snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: 
unsupported version 0 of Verneed record
  mkdir: error while loading shared libraries: 
/snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: 
unsupported version 0 of Verneed record
  mkdir: error while loading shared libraries: 
/snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: 
unsupported version 0 of Verneed record
  sed: error while loading shared libraries: 
/snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: 
unsupported version 0 of Verneed record
  md5sum: error while loading shared libraries: 
/snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: 
unsupported version 0 of Verneed record
  cp: error while loading shared libraries: 
/snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: 
unsupported version 0 of Verneed record
  md5sum: error while loading shared libraries: 
/snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: 
unsupported version 0 of Verneed record
  xdg-user-dirs-update: error while loading shared libraries: 
/snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: 
unsupported version 0 of Verneed record
  rm: error while loading shared libraries: 
/snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: 
unsupported version 0 of Verneed record
  mkdir: error while loading shared libraries: 
/snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: 
unsupported version 0 of Verneed record
  /snap/chromium/2221/snap/command-chain/desktop-launch: line 406: 
/home/USER/snap/chromium/2221/.config/fontconfig/fonts.conf: No such file or 
directory
  ln: error while loading shared libraries: 
/snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: 
unsupported version 0 of Verneed record
  ln: error while loading shared libraries: 
/snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: 
unsupported version 0 of Verneed record
  rm: error while loading shared libraries: 
/snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: 
unsupported version 0 of Verneed record
  mkdir: error while loading shared libraries: 
/snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: 
unsupported version 0 of Verneed record
  rm: error while loading shared libraries: 
/snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: 
unsupported version 0 of Verneed record
  rm: error while loading shared libraries: 
/snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: 
unsupported version 0 of Verneed record
  ln: error while loading shared libraries: 
/snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: 
unsupported version 0 of Verneed record
  mkdir: error while loading shared libraries: 
/snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: 
unsupported version 0 of Verneed record
  mkdir: error while loading shared libraries: 
/snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: 
unsupported version 0 of Verneed record
  rm: error while loading shared libraries: 
/snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: 
unsupported version 0 of Verneed record
  ln: error while loading shared libraries: 
/snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: 
unsupported version 0 of Verneed record
  /snap/chromium/2221/snap/command-chain/desktop-launch: line 500: 
/home/USER/snap/chromium/common/.cache/gdk-pixbuf-loaders.cache: No such file 
or directory
  rm: error while loading shared libraries: 
/snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: 
unsupported version 0 of Verneed record
  
/snap/chromium/2221/gnome-platform/usr/lib/x86_64-linux-gnu/glib-2.0/gio-querymodules:
 error while loading shared libraries: 
/snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: 
unsupported version 0 of Verneed record
  mkdir: error while loading shared libraries: 
/snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: 
unsupported version 0 of Verneed record
  dirname: error 

[Desktop-packages] [Bug 2000175] Re: [snap] latest/candidate/hwacc channel cause lots of Apparmor noise

2023-01-02 Thread Nathan Teodosio
Thanks for the report.

For the record, I also don't have those igfx files, but I cannot
reproduce the bug.

% uname -a
Linux canonical 5.19.0-18-generic #18-Ubuntu SMP PREEMPT_DYNAMIC Wed Sep 21 
15:44:03 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

% snap list chromium_hwcand core20 snapd
Name Version RevTrackingPublisher   Notes
chromium_hwcand  108.0.5359.124  2254   latest/candidate/…  canonical✓  -
core20   202212121778   latest/stable   canonical✓  base
snapd2.5817950  latest/beta canonical✓  snapd

** Changed in: chromium-browser (Ubuntu)
   Importance: Undecided => Low

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

Title:
  [snap] latest/candidate/hwacc channel cause lots of Apparmor noise

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  # Issue description

  After installing chromium with hwacc (snap refresh chromium --channel
  latest/candidate/hwacc) I notice a lot of those new messages in dmesg:

  Dec 20 13:38:13 sdeziel-lemur kernel: audit: type=1400 
audit(1671561493.126:3297): apparmor="DENIED" operation="mknod" 
profile="snap.chromium.chromium" name="/etc/igfx_user_feature.txt" pid=515408 
comm="chrome" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000
  Dec 20 13:38:13 sdeziel-lemur kernel: audit: type=1400 
audit(1671561493.126:3298): apparmor="DENIED" operation="mknod" 
profile="snap.chromium.chromium" name="/etc/igfx_user_feature_next.txt" 
pid=515408 comm="chrome" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000

  
  Those 2 files do not exist in the host's filesystem:

  $ ls /etc/igfx_user_feature.txt /etc/igfx_user_feature_next.txt
  ls: cannot access '/etc/igfx_user_feature.txt': No such file or directory
  ls: cannot access '/etc/igfx_user_feature_next.txt': No such file or directory

  
  # Additional information
  $ uname -a
  Linux sdeziel-lemur 5.15.0-56-generic #62-Ubuntu SMP Tue Nov 22 19:54:14 UTC 
2022 x86_64 x86_64 x86_64 GNU/Linux

  $ lsb_release -rd
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

  $ snap list chromium core20 snapd
  Name  Version   RevTrackingPublisher   Notes
  chromium  107.0.5304.121-hwacc  2224   latest/candidate/…  canonical✓  -
  core2020221123  1738   latest/stable   canonical✓  base
  snapd 2.57.617883  latest/stable   canonical✓  snapd

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2000175/+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 2000862] [NEW] Nautilus search start tracker-miner-fs everytime

2023-01-02 Thread Florent Mertens
Public bug reported:

Everytime I enter a text in Nautilus to start a search, tracker-miner-fs
starts, crawling the filesystem for 10-15 mins. No search results are
shown before the process finish. However, if I start a search from the
command line using tracker3 it works as expected, if I start a search
from gnome-shell it works as expected, and with the nightly version of
nautilus (flatpak) it works as expected as well.

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: nautilus 1:43.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7
Uname: Linux 5.19.0-26-generic x86_64
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Jan  2 11:38:22 2023
GsettingsChanges:
 b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'"
 b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
 b'org.gnome.nautilus.window-state' b'initial-size' b'(1248, 638)'
InstallationDate: Installed on 2022-02-25 (310 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
SourcePackage: nautilus
UpgradeStatus: Upgraded to kinetic on 2022-10-09 (84 days ago)
usr_lib_nautilus:
 file-roller   43.0-1
 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1
 nautilus-share0.7.5-0.1

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


** Tags: amd64 apport-bug kinetic wayland-session

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

Title:
  Nautilus search start tracker-miner-fs everytime

Status in nautilus package in Ubuntu:
  New

Bug description:
  Everytime I enter a text in Nautilus to start a search, tracker-miner-
  fs starts, crawling the filesystem for 10-15 mins. No search results
  are shown before the process finish. However, if I start a search from
  the command line using tracker3 it works as expected, if I start a
  search from gnome-shell it works as expected, and with the nightly
  version of nautilus (flatpak) it works as expected as well.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: nautilus 1:43.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7
  Uname: Linux 5.19.0-26-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan  2 11:38:22 2023
  GsettingsChanges:
   b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'"
   b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
   b'org.gnome.nautilus.window-state' b'initial-size' b'(1248, 638)'
  InstallationDate: Installed on 2022-02-25 (310 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to kinetic on 2022-10-09 (84 days ago)
  usr_lib_nautilus:
   file-roller   43.0-1
   nautilus-extension-gnome-terminal 3.46.2-1ubuntu1
   nautilus-share0.7.5-0.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2000862/+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 2000860] [NEW] Metadata will not send to iceast

2023-01-02 Thread Pakon
Public bug reported:

The Metadata will not transfered to icecast. (e.g. Album, Title, Author
and so on)

The last know working version was: libshout3_2.4.1-2_amd64

Thank you

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


** Tags: icecast2

** Tags added: icecast2

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

Title:
  Metadata will not send to iceast

Status in libshout package in Ubuntu:
  New

Bug description:
  The Metadata will not transfered to icecast. (e.g. Album, Title,
  Author and so on)

  The last know working version was: libshout3_2.4.1-2_amd64

  Thank you

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libshout/+bug/2000860/+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 1922414] Re: ssh-agent fails to start (has_option: command not found)

2023-01-02 Thread Arjan
Hi,

a 'meetoo' for ubuntu 22.10, using sddm/plasma-x11

Can sddm please be added to the 'Affects'?

Did notice the has_option not found in .xsession-errors
and applied workaround as suggested by Boris Steiner above, but had to make a 
small fixup to the script:

OPTIONS="$(
  if [ -r "$OPTIONFILE" ]; then
cat "$OPTIONFILE"
  fi
  if [ -d /etc/X11/Xsession.options.d ]; then
run-parts --list --regex '\.conf$' /etc/X11/Xsession.options.d | xargs -d 
'\n' cat
  fi
)"

#check if has_option is already defined; if not, define

has_option 2>&1 > /dev/null || has_option() {
  # Ensure that a later no-foo overrides an earlier foo
  if [ "$(echo "$OPTIONS" | grep -Eo "^(no-)?$1\>" | tail -n 1)" = "$1" ]; then
return 0
  else
return 1
  fi
}

Notice the 
has_option 2>&1
instead of
has_option 2>1

original proposed version will create file '1' in your home folder

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

Title:
  ssh-agent fails to start (has_option: command not found)

Status in Light Display Manager:
  New
Status in gdm3 package in Ubuntu:
  Fix Released
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I have been using ssh-agent for years and since I upgraded my system
  to Ubuntu 21.04/groovy, ssh-agent fails to start.

  Here is the error message:

  # journalctl | grep ssh-agent
  [...]
  Apr 02 20:16:32 vougeot /usr/libexec/gdm-x-session[3752]: 
/etc/X11/Xsession.d/90x11-common_ssh-agent: line 9: has_option: command not 
found

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: x11-common 1:7.7+22ubuntu1
  Uname: Linux 5.11.11-05-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu61
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Sat Apr  3 09:02:46 2021
  Dependencies: lsb-base 11.1.0ubuntu2
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  DkmsStatus:
   tuxedo-keyboard, 3.0.4, 5.11.0-13-generic, x86_64: installed
   tuxedo-keyboard, 3.0.4, 5.11.0-13-lowlatency, x86_64: installed
   tuxedo-keyboard, 3.0.4, 5.11.11-05-lowlatency, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation TigerLake GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) 
(prog-if 00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer Iris Xe Graphics [1558:51a1]
  MachineType: TUXEDO TUXEDO InfinityBook S 15 Gen6
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.11-05-lowlatency 
root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor 
quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/07/2020
  dmi.bios.release: 7.3
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.03RTR
  dmi.board.name: NS50MU
  dmi.board.vendor: TUXEDO
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.2
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.03RTR:bd09/07/2020:br7.3:efr7.2:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50MU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: TUXEDO InfinityBook S 15 Gen6
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: TUXEDO
  version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu4
  version.libdrm2: libdrm2 2.4.104-1build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-1
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.1-1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.10-3ubuntu5
  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-2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

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