[Touch-packages] [Bug 932900] Re: Unity freeze, crashes when trying to restart - GPU lockup with IPEHR: 0x7a000002

[Launchpad Bug Tracker]

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/932900

Title:
  Unity freeze, crashes when trying to restart - GPU lockup with IPEHR:
  0x7a02

Status in mesa package in Ubuntu:
  Expired
Status in unity package in Ubuntu:
  Invalid

Bug description:
  Unity froze on my when initiating the workspace switcher (which had
  been working previously in the same session).  I switched to
  ctrl+alt+F1 to get to a command prompt, ran unity --replace, but that
  kept crashing.

  Output from unity --replace:

  unity-panel-service: no process found
  Checking if settings need to be migrated ...no
  Checking if internal files need to be migrated ...no
  Backend : gconf
  Integration : true
  Profile : unity
  Adding plugins
  Initializing core options...done
  compiz (core) - Error: Couldn't load plugin 'bailer'
  compiz (core) - Error: Couldn't load plugin 'detection'
  Initializing composite options...done
  Initializing opengl options...done
  Initializing decor options...done
  Initializing vpswitch options...done
  Initializing move options...done
  Initializing place options...done
  Initializing grid options...done
  Initializing annotate options...done
  Initializing snap options...done
  Initializing obs options...done
  Initializing session options...done
  Initializing mousepoll options...done
  Initializing resize options...done
  Initializing animation options...done
  Initializing workarounds options...done
  Initializing gnomecompat options...done
  compiz (expo) - Warn: failed to bind image to texture
  Initializing expo options...done
  Initializing ezoom options...done
  Initializing wall options...done
  Initializing fade options...done
  Initializing scale options...done

  Screen geometry changed:
 0x0x1280x800

  intel_do_flush_locked failed: Input/output error

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: unity 5.2.0-0ubuntu4
  ProcVersionSignature: Ubuntu 3.2.0-16.25-generic-pae 3.2.6
  Uname: Linux 3.2.0-16-generic-pae i686
  NonfreeKernelModules: wl
  .tmp.unity.support.test.0:
   
  ApportVersion: 1.91-0ubuntu1
  Architecture: i386
  CompizPlugins: 
[core,bailer,detection,composite,opengl,decor,vpswitch,compiztoolbox,move,place,grid,annotate,snap,obs,session,mousepoll,resize,regex,imgpng,animation,workarounds,gnomecompat,expo,ezoom,wall,fade,scale,unityshell,scaleaddon,scalefilter]
  CompositorRunning: compiz
  Date: Wed Feb 15 12:06:36 2012
  DistUpgraded: Log time: 2012-01-23 11:49:43.962217
  DistroCodename: precise
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller 
(primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller])
 Subsystem: Dell Latitude D630 [1028:01f9]
 Subsystem: Dell Device [1028:01f9]
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  MachineType: Dell Inc. Latitude D630
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-16-generic-pae 
root=UUID=cdf53458-c5c8-4260-9504-6da8a8a22fd1 ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: Upgraded to precise on 2012-01-23 (22 days ago)
  dmi.bios.date: 06/20/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 0KU184
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd06/20/2008:svnDellInc.:pnLatitudeD630:pvr:rvnDellInc.:rn0KU184:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Latitude D630
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.7.0~bzr2995-0ubuntu1
  version.libdrm2: libdrm2 2.4.30-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 8.0~rc2-0ubuntu5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 8.0~rc2-0ubuntu5
  version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 
1:2.6.99.901+git20120126-0ubuntu2
  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-1ubuntu3
  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/932900/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1070178] Re: plz hlp compiz note working

[Launchpad Bug Tracker]

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1070178

Title:
  plz hlp compiz note working

Status in mesa package in Ubuntu:
  Expired

Bug description:
  enabel 3d driver for sis671 dispaly driver

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: xorg 1:7.6+12ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-32.51-generic-pae 3.2.30
  Uname: Linux 3.2.0-32-generic-pae i686
  .tmp.unity.support.test.1:
   
  ApportVersion: 2.0.1-0ubuntu14
  Architecture: i386
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: None
  Date: Tue Oct 23 10:39:38 2012
  DistUpgraded: Fresh install
  DistroCodename: precise
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need an easy workaround
  GraphicsCard:
   Silicon Integrated Systems [SiS] 771/671 PCIE VGA Display Adapter 
[1039:6351] (rev 10) (prog-if 00 [VGA controller])
 Subsystem: Benq Corporation Device [17ff:0595]
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423)
  MachineType: BenQ JoyBook A53
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-32-generic-pae 
root=UUID=4a2043cf-1c7f-41de-aa14-16d8f40c8904 ro quiet splash vt.handoff=7
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/30/2008
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 1.02
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: JoyBook A53
  dmi.board.vendor: BenQ
  dmi.board.version: Hippo 3.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: BenQ
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr1.02:bd03/30/2008:svnBenQ:pnJoyBookA53:pvr1.02:rvnBenQ:rnJoyBookA53:rvrHippo3.0:cvnBenQ:ct1:cvrN/A:
  dmi.product.name: JoyBook A53
  dmi.product.version: 1.02
  dmi.sys.vendor: BenQ
  version.compiz: compiz 1:0.9.7.8-0ubuntu1.4
  version.libdrm2: libdrm2 2.4.32-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.4-0ubuntu0.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.4-0ubuntu0.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10.8
  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.2
  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/1070178/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1176818] Re: upgrade to 13.4: wrong/strange behavior opengl es vertex shader

[Launchpad Bug Tracker]

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1176818

Title:
  upgrade to 13.4: wrong/strange behavior opengl es vertex shader

Status in mesa package in Ubuntu:
  Expired

Bug description:
  Graphics: Intel® 965GM 
  I suspect (I am not a mesa etc. specialist) sth wrong in the mesa lib, 
because opengl ES isn't working correctly any more.
  I had a WebGL app running nicely in FireFox and Chromium (Ubuntu 12.10).
  I upgraded from 12.10(64bits) to 13.4 (64bits).
  Now it does not work correctly any more in FireFox as well as Chromium.
  No errors, but serious wrong behavior.
  It still works correctly on other machines (ubuntu 12.04/FireFox, 
macBook/FireFox, windows/Chromium).
  The bug turns up in the following lines of the vertex shader (coming from 
javascript/WebGL)
  ---
  uniform mediump vec3 criticalHeights;
  attribute mediump  vec3 vertex;
  ...
  if(criticalHeights[2] > vertex.z )
  {varAmbientLight = redAmbientLight; varDiffuseLight = redDiffuseLight;};
   }
  ---
  criticalHeights[2] and vertex.z vary between -100 and + a few hundred.
  the 'if' statement always returns true, even with extreme values like 
-100.0 < vertex.z or criticalHeights[2] > 100.0
  Please find attached output of glxinfo.
  Thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1176818/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1187077] Re: package libgl1-mesa-dri failed to install/upgrade: trying to overwrite shared '/etc/drirc', which is different from other instances of package libgl1-mesa-dri:amd64

[Launchpad Bug Tracker]

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1187077

Title:
  package libgl1-mesa-dri failed to install/upgrade: trying to overwrite
  shared '/etc/drirc', which is different from other instances of
  package libgl1-mesa-dri:amd64

Status in mesa package in Ubuntu:
  Expired

Bug description:
  Happened after installing fglrx-updates.

  ProblemType: Package
  DistroRelease: Ubuntu 13.04
  Package: libgl1-mesa-dri 9.1.1-0ubuntu3
  ProcVersionSignature: Ubuntu 3.8.0-23.34-generic 3.8.11
  Uname: Linux 3.8.0-23-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Mon Jun  3 18:35:36 2013
  DistUpgraded: 2013-06-01 18:31:15,548 DEBUG enabling apt cron job
  DistroCodename: raring
  DistroVariant: ubuntu
  DkmsStatus: fglrx-updates, 9.012, 3.8.0-23-generic, x86_64: installed
  DpkgTerminalLog:
   Preparing to replace libgl1-mesa-dri:amd64 9.1.1-0ubuntu3 (using 
.../libgl1-mesa-dri_9.1.1-0ubuntu3_amd64.deb) ...
   Unpacking replacement libgl1-mesa-dri:amd64 ...
   dpkg: error processing 
/var/cache/apt/archives/libgl1-mesa-dri_9.1.1-0ubuntu3_amd64.deb (--unpack):
trying to overwrite shared '/etc/drirc', which is different from other 
instances of package libgl1-mesa-dri:amd64
  DuplicateSignature:
   Unpacking replacement libgl1-mesa-dri:amd64 ...
   dpkg: error processing 
/var/cache/apt/archives/libgl1-mesa-dri_9.1.1-0ubuntu3_amd64.deb (--unpack):
trying to overwrite shared '/etc/drirc', which is different from other 
instances of package libgl1-mesa-dri:amd64
  ErrorMessage: trying to overwrite shared '/etc/drirc', which is different 
from other instances of package libgl1-mesa-dri:amd64
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:056e]
   Advanced Micro Devices [AMD] nee ATI Thames XT [Radeon HD 7670M] [1002:6840] 
(prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:056e]
  InstallationDate: Installed on 2012-09-07 (268 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  JockeyStatus:
   kmod:fglrx - Video driver for the AMD graphics accelerators (Proprietary, 
Disabled, Not in use)
   kmod:fglrx_updates - ATI Fire GL (Proprietary, Enabled, Not in use)
  MachineType: Dell Inc. Vostro 3560
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.8.0-23-generic 
root=UUID=ee915b12-aec5-4d5c-868e-82e41c81b4da ro quiet splash vt.handoff=7
  SourcePackage: mesa
  Title: package libgl1-mesa-dri 9.1.1-0ubuntu3 failed to install/upgrade: 
trying to overwrite shared '/etc/drirc', which is different from other 
instances of package libgl1-mesa-dri: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 raring on 2013-06-01 (2 days ago)
  dmi.bios.date: 05/17/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 0C05GV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A07
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd05/17/2012:svnDellInc.:pnVostro3560:pvrA07:rvnDellInc.:rn0C05GV:rvrA00:cvnDellInc.:ct8:cvrA07:
  dmi.product.name: Vostro 3560
  dmi.product.version: A07
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1
  version.fglrx-installer: fglrx-installer N/A
  version.ia32-libs: ia32-libs 20090808ubuntu36
  version.libdrm2: libdrm2 2.4.43-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.1-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.1-0ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.6-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.7-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1187077/+subscriptions


-- 
Mailing list: 

[Touch-packages] [Bug 1129289] Re: Could not find glGetError

[Launchpad Bug Tracker]

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1129289

Title:
  Could not find glGetError

Status in mesa package in Ubuntu:
  Expired

Bug description:
  Hello. I tried to launch some games based on Source engine (native) on my 
linux desktop. And in all i see one error: Could not find glGetError. I 
reported it to game developers, they said that its drivers bug. I have Ubuntu 
12.10 with linux-3.5.0-23-generic, Intel Atom n450 with Intel GMA3150. Added 
ppa:xorg-edgers/ppa.
  My /etc/X11/xorg.conf:
  Section "Device"
 Identifier  "Card0"
 Driver  "intel"
 Option  "AccelMethod"  "sna"
  EndSection

  Xorg: X.Org X Server 1.13.1.901 (1.13.2 RC 1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1129289/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1142305] Re: Running 32 bit software in 64 bit 12.04.2 with quantal xorg+kernel doesn't work with i965

[Launchpad Bug Tracker]

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1142305

Title:
  Running 32 bit software in 64 bit 12.04.2 with quantal  xorg+kernel
  doesn't work with i965

Status in mesa package in Ubuntu:
  Expired

Bug description:
  Running 32 bit software which uses OpenGL doesn't work anymore after
  updating to quantal kernel+xorg in Ubuntu 12.04.2 64 bit. 64 Bit
  software work fine. Seems to be a problem with the i965 driver.

  LIBGL_DEBUG=verbose  google-earth 
  ERROR: ld.so: object '/opt/lib/libmediaclient.so' from /etc/ld.so.preload 
cannot be preloaded: ignored.
  libGL: OpenDriver: trying /usr/lib/i386-linux-gnu/dri/tls/i965_dri.so
  libGL: OpenDriver: trying /usr/lib/i386-linux-gnu/dri/i965_dri.so
  libGL error: dlopen /usr/lib/i386-linux-gnu/dri/i965_dri.so failed 
(/usr/lib/i386-linux-gnu/dri/i965_dri.so: undefined symbol: 
drm_intel_gem_bo_map_unsynchronized)

  
  libgl1-mesa-dri-lts-quantal:i386: 9.0.2-0ubuntu0.1~precise1
  libgl1-mesa-glx-lts-quantal:i386: 9.0.2-0ubuntu0.1~precise1
  xserver-xorg-video-intel-lts-quantal: 2:2.20.9-0ubuntu2~precise2
  libdrm-intel1:i386:  2.4.39-0ubuntu0.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1142305/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1232395] Re: check_gl_texture_size crashed with SIGSEGV in do_winsys_init()

[Launchpad Bug Tracker]

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1232395

Title:
  check_gl_texture_size crashed with SIGSEGV in do_winsys_init()

Status in mesa package in Ubuntu:
  Expired

Bug description:
  I don't know what cause the problem

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: libgnome-desktop-3-7 3.8.4-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-9.16-generic 3.11.2
  Uname: Linux 3.11.0-9-generic x86_64
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: amd64
  Date: Sat Sep 28 10:37:26 2013
  ExecutablePath: /usr/lib/libgnome-desktop-3-7/check_gl_texture_size
  InstallationDate: Installed on 2013-09-22 (5 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130905)
  MarkForUpload: True
  ProcCmdline: /usr/lib/libgnome-desktop-3-7/check_gl_texture_size
  ProcEnviron:
   
  SegvAnalysis:
   Segfault happened at: 0x7f55c727a549 : mov
(%rax),%r8d
   PC (0x7f55c727a549) ok
   source "(%rax)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%r8d" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-desktop3
  StacktraceTop:
   radeon_drm_winsys_create () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/mesa/libGL.so.1
  Title: check_gl_texture_size crashed with SIGSEGV in 
radeon_drm_winsys_create()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1232395/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1267384] Re: 8086:29b2 [HP Compaq dc7800 Convertible Minitower PC] 82Q35 graphics acceleration performance worse than it could be

[Launchpad Bug Tracker]

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1267384

Title:
  8086:29b2 [HP Compaq dc7800 Convertible Minitower PC] 82Q35 graphics
  acceleration performance worse than it could be

Status in mesa package in Ubuntu:
  Expired

Bug description:
  Summary: X performance is very bad on my HP Compaq dc7800p desktop
  computer. For example moving windows is jerky and glxgears in full
  screen only achieve 15 fps. The problem exists at least since 11.10.
  The problem still exists in 14.04 daily-live 2014-01-08.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu7
  ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4
  Uname: Linux 3.12.0-7-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.12.7-0ubuntu6
  Architecture: amd64
  CasperVersion: 1.336ubuntu1
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Jan  9 08:51:29 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 82Q35 Express Integrated Graphics Controller [8086:29b2] 
(rev 02) (prog-if 00 [VGA controller])
     Subsystem: Hewlett-Packard Company Device [103c:2819]
  LiveMediaBuild: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64+mac (20140108)
  MachineType: Hewlett-Packard HP Compaq dc7800p Convertible Minitower
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper 
initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/18/2008
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 786F1 v01.24
  dmi.board.asset.tag: CZC8163N0C
  dmi.board.name: 0AACh
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: CZC8163N0C
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786F1v01.24:bd03/18/2008:svnHewlett-Packard:pnHPCompaqdc7800pConvertibleMinitower:pvr:rvnHewlett-Packard:rn0AACh:rvr:cvnHewlett-Packard:ct6:cvr:
  dmi.product.name: HP Compaq dc7800p Convertible Minitower
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.50-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.0.1-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.0.1-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.907-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu1
  xserver.bootTime: Thu Jan  9 08:51:02 2014
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   26507
   vendor NEC
  xserver.version: 2:1.14.5-1ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1267384/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1365403] Re: unity / compiz crash when switching resolution

[Launchpad Bug Tracker]

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1365403

Title:
  unity / compiz crash when switching resolution

Status in mesa package in Ubuntu:
  Expired

Bug description:
  When using unity / compiz on top of llvmpipe and switching resolution
  from something lower to 1600x1200 (This is a virtual machine, so this
  happens regularly), compiz crashes.

  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04

  libgl1-mesa-dri:
Installed: 10.1.3-0ubuntu0.1

  Expected:
  compiz shouldn't crash.


  (gdb) bt
  #0  __memcpy_sse2_unaligned ()
  at ../sysdeps/x86_64/multiarch/memcpy-sse2-unaligned.S:33
  #1  0x7fd2432f991e in ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
  #2  0x7fd2432fa412 in ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
  #3  0x7fd2432f9abe in ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
  #4  0x7fd2432fa984 in XPutImage ()
 from /usr/lib/x86_64-linux-gnu/libX11.so.6
  #5  0x7fd22fb8a576 in ?? () from /usr/lib/x86_64-linux-gnu/mesa/libGL.so.1
  #6  0x7fd22e5a7d5d in ?? ()
 from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
  #7  0x7fd22e5a8460 in ?? ()
 from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
  #8  0x7fd22e5a7e48 in ?? ()
 from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
  #9  0x7fd22fddb281 in GLXDoubleBuffer::blit(CompRegion const&) const ()
 from /usr/lib/compiz/libopengl.so
  #10 0x7fd22fdd94da in 
PrivateGLScreen::paintOutputs(std::list >&, unsigned int, CompRegion const&) ()
 from /usr/lib/compiz/libopengl.so
  #11 0x7fd23c5f944f in CompositeScreen::paint(std::list >&, unsigned int) () from 
/usr/lib/compiz/libcomposite.so
  #12 0x7fd23c5fcaf2 in CompositeScreen::handlePaintTimeout() ()
 from /usr/lib/compiz/libcomposite.so
  ---Type  to continue, or q  to quit---
  #13 0x7fd2441777ed in CompTimer::triggerCallback() ()
 from /usr/lib/libcompiz_core.so.ABI-20140123
  #14 0x7fd24417789f in CompTimeoutSource::callback() ()
 from /usr/lib/libcompiz_core.so.ABI-20140123
  #15 0x7fd244176dfd in CompTimeoutSource::dispatch(sigc::slot_base*) ()
 from /usr/lib/libcompiz_core.so.ABI-20140123
  #16 0x7fd24266335f in Glib::Source::dispatch_vfunc(_GSource*, int 
(*)(void*), void*) () from /usr/lib/x86_64-linux-gnu/libglibmm-2.4.so.1
  #17 0x7fd242155ce5 in g_main_context_dispatch ()
 from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #18 0x7fd242156048 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #19 0x7fd24215630a in g_main_loop_run ()
 from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #20 0x7fd24413215b in 
compiz::private_screen::EventManager::startEventLoop(_XDisplay*) () from 
/usr/lib/libcompiz_core.so.ABI-20140123
  #21 0x00401981 in main ()
  (gdb)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1365403/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1521806] Re: undefined reference to glProgramUniform3fv when building opengl app

[Launchpad Bug Tracker]

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1521806

Title:
  undefined reference to  glProgramUniform3fv when building opengl app

Status in mesa package in Ubuntu:
  Expired

Bug description:
  A library which is being developed against the nvidia libGL.so fails to link 
against mesa's libGL.so.
  The linker complains:

  foo: undefined reference to `glProgramUniform1fv'
  foo: undefined reference to `glProgramUniform1i'
  foo: undefined reference to `glProgramUniform2fv'
  foo: undefined reference to `glProgramUniform3fv'
  foo: undefined reference to `glProgramUniform4fv'
  foo: undefined reference to `glProgramUniformMatrix3fv'
  foo: undefined reference to `glProgramUniformMatrix4fv'
  foo: undefined reference to `glXCreateContextAttribsARB'

  Is this expected behavior, punishing the developer for not using an extension 
loader, or something?
  Or should mesa export everything nvidia exports?

  Sounds like it's expected behavior, given 
http://sourceforge.net/p/mesa3d/mailman/message/26157363/
  but I thought I'd file it in case some other OpenGL noob runs into it.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: libgl1-mesa-dev 10.1.3-0ubuntu0.4
  ProcVersionSignature: Ubuntu 3.13.0-55.92-generic 3.13.11-ckt20
  Uname: Linux 3.13.0-55-generic x86_64
  NonfreeKernelModules: veth aufs xt_CHECKSUM iptable_mangle ipt_MASQUERADE 
iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack 
xt_tcpudp bridge stp llc iptable_filter ip_tables x_tables rfcomm bnep 
bluetooth coretemp crct10dif_pclmul crc32_pclmul ghash_clmulni_intel 
vmw_balloon aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd 
serio_raw vmwgfx ppdev ttm parport_pc lp parport drm shpchp mac_hid vmw_vmci 
i2c_piix4 psmouse vmw_pvscsi vmxnet3 mptspi e1000 floppy mptscsih mptbase 
pata_acpi
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  Date: Tue Dec  1 15:29:17 2015
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1521806/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1335602] Re: ' X acceleration library -- runtime' update prevents Utopic from booting

[Launchpad Bug Tracker]

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1335602

Title:
  ' X acceleration library -- runtime' update prevents Utopic from
  booting

Status in mesa package in Ubuntu:
  Expired

Bug description:
  Installing the ' Ubuntu-gnome base/X acceleration library -- runtime update' 
in Ubuntu Utopic will prevent Ubuntu Utopic to boot. 
  Booting does stop after the message: ' Restoring resolver state [ok].

  Running Utopic in a virtual machine (VMware Workstation 10) under Ubuntu 
Trusty
  Intel® Core™ i7-4771 CPU @ 3.50GHz × 8 
  15,6 GiB Memory 
  GeForce GTX 660/PCIe/SSE2
  64-bit

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1335602/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1567749] Re: screen artifacts when playing runescape (java client)

[Launchpad Bug Tracker]

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1567749

Title:
  screen artifacts when playing runescape (java client)

Status in mesa package in Ubuntu:
  Expired

Bug description:
  I get screen artifacts in the game Runescape, when playing on Ubuntu
  16.04 Xenial Xerus, this happened right after the update to mesa
  1.2.0-1ubuntu1 so it's a regression in this version of mesa.

  Glad you updated though, but since this is a dot-zero release it needs
  to be patched with fixes from git until they officially release
  another bugfix release.

  Bug is not reported upstream AFAIK.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1567749/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1648533] Re: package libgl1-mesa-dri:amd64 11.2.0-1ubuntu2.2 failed to install/upgrade: problemas com dependências - a deixar por configurar

[Launchpad Bug Tracker]

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1648533

Title:
  package libgl1-mesa-dri:amd64 11.2.0-1ubuntu2.2 failed to
  install/upgrade: problemas com dependências - a deixar por configurar

Status in mesa package in Ubuntu:
  Expired

Bug description:
  I don't know

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libgl1-mesa-dri:amd64 11.2.0-1ubuntu2.2
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Tue Dec  6 17:50:32 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ErrorMessage: problemas com dependências - a deixar por configurar
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] 4th Gen Core Processor 
Integrated Graphics Controller [1462:1109]
 Subsystem: Micro-Star International Co., Ltd. [MSI] GM107M [GeForce GTX 
860M] [1462:1109]
  InstallationDate: Installed on 2016-11-15 (22 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Micro-Star International Co., Ltd. GE70 2PE
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-53-generic 
root=UUID=14471d52-d1c0-4adc-b139-2067cc55be55 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: mesa
  Title: package libgl1-mesa-dri:amd64 11.2.0-1ubuntu2.2 failed to 
install/upgrade: problemas com dependências - a deixar por configurar
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/28/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E1759IMS.515
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-1759
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:0.B
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE1759IMS.515:bd03/28/2014:svnMicro-StarInternationalCo.,Ltd.:pnGE702PE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1759:rvrREV0.B:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
  dmi.product.name: GE70 2PE
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Thu Dec  8 15:03:05 2016
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
   Unknown chipset: NV117
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5941 
   vendor CMN
  xserver.version: 2:1.18.4-0ubuntu0.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1648533/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1620212] Re: package libgl1-mesa-glx:i386 11.2.0-1ubuntu2.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting con

[Launchpad Bug Tracker]

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1620212

Title:
  package libgl1-mesa-glx:i386 11.2.0-1ubuntu2.2 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in mesa package in Ubuntu:
  Expired

Bug description:
  package libgl1-mesa-glx:i386 11.2.0-1ubuntu2.2 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libgl1-mesa-glx:i386 11.2.0-1ubuntu2.2
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Sep  5 09:56:05 2016
  DistUpgraded: 2016-04-21 23:10:04,794 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: xenial
  DistroVariant: ubuntu
  DpkgHistoryLog:
   Start-Date: 2016-09-05  09:54:58
   Commandline: aptdaemon role='role-commit-packages' sender=':1.102'
   Install: linux-image-4.4.0-37-generic:i386 (4.4.0-37.56, automatic), 
linux-image-extra-4.4.0-37-generic:i386 (4.4.0-37.56, automatic), 
linux-headers-4.4.0-37-generic:i386 (4.4.0-37.56, automatic), 
linux-headers-4.4.0-37:i386 (4.4.0-37.56, automatic)
   Upgrade: linux-headers-generic:i386 (4.4.0.36.38, 4.4.0.37.39), 
linux-libc-dev:i386 (4.4.0-36.55, 4.4.0-37.56), linux-image-generic:i386 
(4.4.0.36.38, 4.4.0.37.39), snapd:i386 (2.13, 2.14.2~16.04), libapparmor1:i386 
(2.10.95-0ubuntu2.2, 2.10.95-0ubuntu2.3), libappstream-glib8:i386 
(0.5.13-1ubuntu2, 0.5.13-1ubuntu3), libapparmor-perl:i386 (2.10.95-0ubuntu2.2, 
2.10.95-0ubuntu2.3), apparmor:i386 (2.10.95-0ubuntu2.2, 2.10.95-0ubuntu2.3), 
accountsservice:i386 (0.6.40-2ubuntu11.1, 0.6.40-2ubuntu11.2), 
linux-generic:i386 (4.4.0.36.38, 4.4.0.37.39), libaccountsservice0:i386 
(0.6.40-2ubuntu11.1, 0.6.40-2ubuntu11.2)
  DuplicateSignature:
   package:libgl1-mesa-glx:i386:11.2.0-1ubuntu2.2
   Processing triggers for man-db (2.7.5-1) ...
   dpkg: error processing package libgl1-mesa-glx:i386 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  GraphicsCard:
   Intel Corporation 4 Series Chipset Integrated Graphics Controller 
[8086:2e22] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] 4 Series Chipset Integrated Graphics 
Controller [1025:023c]
 Subsystem: Acer Incorporated [ALI] 4 Series Chipset Integrated Graphics 
Controller [1025:023c]
  InstallationDate: Installed on 2014-10-30 (675 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 
(20140722.2)
  MachineType: Acer Veriton M480G
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic 
root=UUID=db60e17a-b45f-4cfd-8d1f-d19aef55821e ro splash quiet
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: mesa
  Title: package libgl1-mesa-glx:i386 11.2.0-1ubuntu2.2 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: Upgraded to xenial on 2016-04-21 (136 days ago)
  XorgLogOld:
   
  dmi.bios.date: 08/07/2009
  dmi.bios.vendor: Acer
  dmi.bios.version: P01-A3
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: Veriton M480
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAcer:bvrP01-A3:bd08/07/2009:svnAcer:pnVeritonM480G:pvr:rvnAcer:rnVeritonM480:rvr:cvnAcer:ct3:cvr:
  dmi.product.name: Veriton M480G
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.12.2+16.04.20160801.3-0ubuntu1
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Mon Sep  5 09:09:47 2016
  

[Touch-packages] [Bug 1654783] Re: package libxatracker2:amd64 11.2.0-1ubuntu2 failed to install/upgrade: package libxatracker2:amd64 is not ready for configuration cannot configure (current status 'h

[Launchpad Bug Tracker]

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1654783

Title:
  package libxatracker2:amd64 11.2.0-1ubuntu2 failed to install/upgrade:
  package libxatracker2:amd64 is not ready for configuration  cannot
  configure (current status 'half-installed')

Status in mesa package in Ubuntu:
  Expired

Bug description:
  At to install

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libxatracker2:amd64 11.2.0-1ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sat Jan  7 16:46:51 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ErrorMessage: package libxatracker2:amd64 is not ready for configuration  
cannot configure (current status 'half-installed')
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family 
Integrated Graphics Controller [103c:1659]
   Advanced Micro Devices, Inc. [AMD/ATI] Seymour [Radeon HD 6400M/7400M 
Series] [1002:6760] (rev ff) (prog-if ff)
  InstallationDate: Installed on 2017-01-07 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=6612b251-bfdc-45dd-a8b0-a31a76c9008f ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15ubuntu0.2
  SourcePackage: mesa
  Title: package libxatracker2:amd64 11.2.0-1ubuntu2 failed to install/upgrade: 
package libxatracker2:amd64 is not ready for configuration  cannot configure 
(current status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/05/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.1B
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1659
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 10.31
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.1B:bd10/05/2011:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvr058E1124471620100:rvnHewlett-Packard:rn1659:rvr10.31:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion dv7 Notebook PC
  dmi.product.version: 058E1124471620100
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sat Jan  7 16:36:06 2017
  xserver.configfile: default
  xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5913 
   vendor CMO
  xserver.version: 2:1.18.4-0ubuntu0.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1654783/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1656674] Re: package libxatracker2:amd64 11.2.0-1ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting config

[Launchpad Bug Tracker]

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1656674

Title:
  package libxatracker2:amd64 11.2.0-1ubuntu2 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in mesa package in Ubuntu:
  Expired

Bug description:
  i was running sudo apt-get install mesa-utils for working with my amd
  driver

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libxatracker2:amd64 11.2.0-1ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.4
  AptOrdering:
   mesa-utils: Install
   libxatracker2: Configure
   mesa-utils: Configure
   NULL: ConfigurePending
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sun Jan 15 09:27:42 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: ndiswrapper, 1.59, 4.4.0-59-generic, x86_64: installed
  DuplicateSignature:
   package:libxatracker2:amd64:11.2.0-1ubuntu2
   Processing triggers for man-db (2.7.5-1) ...
   dpkg: error processing package libxatracker2:amd64 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Kabini [Radeon HD 8400 / R3 Series] 
[1002:9830] (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Kabini [Radeon HD 8400 / R3 Series] 
[1025:0800]
  InstallationDate: Installed on 2017-01-15 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Gateway DX4375G
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic.efi.signed 
root=UUID=82028627-51f0-4612-98d1-f0557bc85e0c ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.18
  SourcePackage: mesa
  Title: package libxatracker2:amd64 11.2.0-1ubuntu2 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/27/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P11-A3
  dmi.board.name: DX4375G
  dmi.board.vendor: Gateway
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gateway
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP11-A3:bd06/27/2013:svnGateway:pnDX4375G:pvr:rvnGateway:rnDX4375G:rvr:cvnGateway:ct3:cvr:
  dmi.product.name: DX4375G
  dmi.sys.vendor: Gateway
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sun Jan 15 09:14:23 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.3-1ubuntu2.2
  xserver.video_driver: radeon

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1656674/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1877879] Re: segfault in iris_dri.so

[Launchpad Bug Tracker]

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1877879

Title:
  segfault in iris_dri.so

Status in mesa package in Ubuntu:
  Expired

Bug description:
  As of Ubuntu 20.04, on intel graphics with intel driver (not
  modesetting), I got segfault whenever anything tries to use GL.

  This happens unless I export MESA_LOADER_DRIVER_OVERRIDE=i965. One
  says that it does not happen with modesetting driver.

  (gdb) run
  Starting program: /usr/bin/glxgears 
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  [New Thread 0x717cf700 (LWP 97070)]
  [New Thread 0x7fffebfff700 (LWP 97071)]
  [New Thread 0x70fce700 (LWP 97072)]
  [New Thread 0x7fffeb7fe700 (LWP 97073)]

  Thread 1 "glxgears" received signal SIGSEGV, Segmentation fault.
  0x76a7e1d4 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
  (gdb) where
  #0  0x76a7e1d4 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
  #1  0x76c42de4 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
  #2  0x76a59e5d in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
  #3  0x76a5aa95 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
  #4  0x76099774 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
  #5  0x711e in ?? ()
  #6  0x6c88 in ?? ()
  #7  0x77ace0b3 in __libc_start_main (main=0x6410, argc=1, 
argv=0x7fffe698, init=, fini=, 
rtld_fini=, stack_end=0x7fffe688) at ../csu/libc-start.c:308
  #8  0x6f0a in ?? ()
  (gdb) 

  I believe, this is a bug in mesa tracked here:
  https://gitlab.freedesktop.org/mesa/mesa/issues/1358

  packages versions:
  libgl1-mesa-dri:amd64 20.0.4-2ubuntu1 
amd64 
  xserver-xorg-video-intel  2:2.99.917+git20200226-1
amd64
  xserver-xorg-core 2:1.20.8-2ubuntu2   
amd64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1877879/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2040037] Re: Xorg crash

[BertN45]

** Description changed:

  The first login of my Xubuntu 23.10 VBox VM fails. The second login seems OK, 
but all programs I start at login are started twice, like e.g conky. It results 
in 100% cpu load on one core.
- The system displays an error message for ~2 seconds and it says something 
like: "VBoxclient can't connect to X server".  
+ The system displays an error message for ~2 seconds and it says something 
like: "VBoxclient can't connect to X server".
  The error also occurs on a fresh install.
+ 
+ Some additional info:
+ - The login loop also happens on Ubuntu 23.10 VM when started with Xorg, but 
here it keeps looping.
+ - A comparable error occurs on Ubuntu Unity 23.10 VM, on the first screen no 
login box will be presented. On the second boot the login screen is presented 
and the login seems normal. 
+ 
+ Note that the same Vbox release 7.0.12 has no issues with flavors of
+ 22.04 LTS nor with 20.04 LTS.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Fri Oct 20 20:55:33 2023
  DistUpgraded: Fresh install
  DistroCodename: mantic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
-  VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
-Subsystem: VMware SVGA II Adapter [15ad:0405]
+  VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
+    Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2023-05-10 (163 days ago)
  InstallationMedia: Xubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230510)
  Lsusb:
-  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
-  Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
-  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
-  /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
-  /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M
-  |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
+  /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
+  /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M
+  |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic 
root=UUID=68afebf4-295a-4f3d-b521-36f13d8e060d ro quiet splash
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.115-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2040037

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  New

Bug description:
  The first login of my Xubuntu 23.10 VBox VM fails. The second login seems OK, 
but all programs I start at login are started twice, like e.g conky. It results 
in 100% cpu load on one core.
  The system displays an error message for ~2 seconds and it says something 
like: "VBoxclient can't connect to X server".
  The error also occurs on a fresh install.

  Some additional info:
  - The login loop also happens on Ubuntu 23.10 VM when started with Xorg, but 
here it keeps looping.
  - A comparable error occurs on Ubuntu Unity 23.10 VM, on the first screen no 
login box will be presented. On the second boot the login screen is 

[Touch-packages] [Bug 2040037] [NEW] Xorg crash

[BertN45]

Public bug reported:

The first login of my Xubuntu 23.10 VBox VM fails. The second login seems OK, 
but all programs I start at login are started twice, like e.g conky. It results 
in 100% cpu load on one core.
The system displays an error message for ~2 seconds and it says something like: 
"VBoxclient can't connect to X server".  
The error also occurs on a fresh install.

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: XFCE
Date: Fri Oct 20 20:55:33 2023
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
   Subsystem: VMware SVGA II Adapter [15ad:0405]
InstallationDate: Installed on 2023-05-10 (163 days ago)
InstallationMedia: Xubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230510)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
 /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
 /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M
 |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic 
root=UUID=68afebf4-295a-4f3d-b521-36f13d8e060d ro quiet splash
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku:
dmi.product.family: Virtual Machine
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug crash mantic ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2040037

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  New

Bug description:
  The first login of my Xubuntu 23.10 VBox VM fails. The second login seems OK, 
but all programs I start at login are started twice, like e.g conky. It results 
in 100% cpu load on one core.
  The system displays an error message for ~2 seconds and it says something 
like: "VBoxclient can't connect to X server".  
  The error also occurs on a fresh install.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Fri Oct 20 20:55:33 2023
  DistUpgraded: Fresh install
  DistroCodename: mantic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2023-05-10 (163 days ago)
  InstallationMedia: Xubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230510)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic 

[Touch-packages] [Bug 2040017] Re: package libasound2-plugins 1.2.7.1-1ubuntu2 failed to install/upgrade: trying to overwrite shared '/etc/alsa/conf.d/99-pulseaudio-default.conf.example', which is dif

[Ubuntu Foundations Team Bug Bot]

** Package changed: ubuntu => alsa-plugins (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-plugins in Ubuntu.
https://bugs.launchpad.net/bugs/2040017

Title:
  package libasound2-plugins 1.2.7.1-1ubuntu2 failed to install/upgrade:
  trying to overwrite shared '/etc/alsa/conf.d/99-pulseaudio-
  default.conf.example', which is different from other instances of
  package libasound2-plugins:i386

Status in alsa-plugins package in Ubuntu:
  New

Bug description:
  I dont know much about

  ProblemType: Package
  DistroRelease: Ubuntu 23.10
  Package: libasound2-plugins 1.2.7.1-1ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Sat Oct 21 02:05:11 2023
  DuplicateSignature:
   package:libasound2-plugins:1.2.7.1-1ubuntu2
   Unpacking libasound2-plugins:i386 (1.2.7.1-1ubuntu2) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-KQ6wMx/50-libasound2-plugins_1.2.7.1-1ubuntu2_i386.deb 
(--unpack):
trying to overwrite shared 
'/etc/alsa/conf.d/99-pulseaudio-default.conf.example', which is different from 
other instances of package libasound2-plugins:i386
  ErrorMessage: trying to overwrite shared 
'/etc/alsa/conf.d/99-pulseaudio-default.conf.example', which is different from 
other instances of package libasound2-plugins:i386
  InstallationDate: Installed on 2022-12-23 (301 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.22.0ubuntu1
   apt  2.7.3
  SourcePackage: alsa-plugins
  Title: package libasound2-plugins 1.2.7.1-1ubuntu2 failed to install/upgrade: 
trying to overwrite shared 
'/etc/alsa/conf.d/99-pulseaudio-default.conf.example', which is different from 
other instances of package libasound2-plugins:i386
  UpgradeStatus: Upgraded to mantic on 2023-10-20 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-plugins/+bug/2040017/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2040017] [NEW] package libasound2-plugins 1.2.7.1-1ubuntu2 failed to install/upgrade: trying to overwrite shared '/etc/alsa/conf.d/99-pulseaudio-default.conf.example', which is d

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I dont know much about

ProblemType: Package
DistroRelease: Ubuntu 23.10
Package: libasound2-plugins 1.2.7.1-1ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
Date: Sat Oct 21 02:05:11 2023
DuplicateSignature:
 package:libasound2-plugins:1.2.7.1-1ubuntu2
 Unpacking libasound2-plugins:i386 (1.2.7.1-1ubuntu2) ...
 dpkg: error processing archive 
/tmp/apt-dpkg-install-KQ6wMx/50-libasound2-plugins_1.2.7.1-1ubuntu2_i386.deb 
(--unpack):
  trying to overwrite shared 
'/etc/alsa/conf.d/99-pulseaudio-default.conf.example', which is different from 
other instances of package libasound2-plugins:i386
ErrorMessage: trying to overwrite shared 
'/etc/alsa/conf.d/99-pulseaudio-default.conf.example', which is different from 
other instances of package libasound2-plugins:i386
InstallationDate: Installed on 2022-12-23 (301 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.22.0ubuntu1
 apt  2.7.3
SourcePackage: alsa-plugins
Title: package libasound2-plugins 1.2.7.1-1ubuntu2 failed to install/upgrade: 
trying to overwrite shared 
'/etc/alsa/conf.d/99-pulseaudio-default.conf.example', which is different from 
other instances of package libasound2-plugins:i386
UpgradeStatus: Upgraded to mantic on 2023-10-20 (0 days ago)

** Affects: alsa-plugins (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package mantic need-duplicate-check package-conflict
-- 
package libasound2-plugins 1.2.7.1-1ubuntu2 failed to install/upgrade: trying 
to overwrite shared '/etc/alsa/conf.d/99-pulseaudio-default.conf.example', 
which is different from other instances of package libasound2-plugins:i386
https://bugs.launchpad.net/bugs/2040017
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to alsa-plugins in Ubuntu.

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2040020] [NEW] [82WR, Realtek ALC287, Speaker, Internal] No sound at all

[Corwin Cimler]

Public bug reported:

Legion-Pro-7-16IRX8 has no sound from built-in speakers, sound works
over bluetooth and monitor speakers.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: alsa-base 1.0.25+dfsg-0ubuntu7
ProcVersionSignature: Ubuntu 6.2.0-35.35~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-35-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  bamm   2380 F pulseaudio
 /dev/snd/controlC1:  bamm   2380 F pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Oct 20 17:02:36 2023
InstallationDate: Installed on 2023-10-20 (0 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
PackageArchitecture: all
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  bamm   2380 F pulseaudio
 /dev/snd/controlC1:  bamm   2380 F pulseaudio
Symptom_Jack: Speaker, Internal
Symptom_Type: No sound at all
Title: [82WR, Realtek ALC287, Speaker, Internal] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/20/2023
dmi.bios.release: 1.38
dmi.bios.vendor: LENOVO
dmi.bios.version: KWCN38WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76461 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Legion Pro 7 16IRX8
dmi.ec.firmware.release: 1.38
dmi.modalias: 
dmi:bvnLENOVO:bvrKWCN38WW:bd06/20/2023:br1.38:efr1.38:svnLENOVO:pn82WR:pvrLegionPro716IRX8:rvnLENOVO:rnLNVNB161216:rvrSDK0T76461WIN:cvnLENOVO:ct10:cvrLegionPro716IRX8:skuLENOVO_MT_82WR_BU_idea_FM_LegionPro716IRX8:
dmi.product.family: Legion Pro 7 16IRX8
dmi.product.name: 82WR
dmi.product.sku: LENOVO_MT_82WR_BU_idea_FM_Legion Pro 7 16IRX8
dmi.product.version: Legion Pro 7 16IRX8
dmi.sys.vendor: LENOVO

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/2040020

Title:
  [82WR, Realtek ALC287, Speaker, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Legion-Pro-7-16IRX8 has no sound from built-in speakers, sound works
  over bluetooth and monitor speakers.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 6.2.0-35.35~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-35-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bamm   2380 F pulseaudio
   /dev/snd/controlC1:  bamm   2380 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 20 17:02:36 2023
  InstallationDate: Installed on 2023-10-20 (0 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bamm   2380 F pulseaudio
   /dev/snd/controlC1:  bamm   2380 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [82WR, Realtek ALC287, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/20/2023
  dmi.bios.release: 1.38
  dmi.bios.vendor: LENOVO
  dmi.bios.version: KWCN38WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76461 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion Pro 7 16IRX8
  dmi.ec.firmware.release: 1.38
  dmi.modalias: 
dmi:bvnLENOVO:bvrKWCN38WW:bd06/20/2023:br1.38:efr1.38:svnLENOVO:pn82WR:pvrLegionPro716IRX8:rvnLENOVO:rnLNVNB161216:rvrSDK0T76461WIN:cvnLENOVO:ct10:cvrLegionPro716IRX8:skuLENOVO_MT_82WR_BU_idea_FM_LegionPro716IRX8:
  dmi.product.family: Legion Pro 7 16IRX8
  dmi.product.name: 82WR
  dmi.product.sku: LENOVO_MT_82WR_BU_idea_FM_Legion Pro 7 16IRX8
  dmi.product.version: Legion Pro 7 16IRX8
  dmi.sys.vendor: LENOVO

To manage notifications 

[Touch-packages] [Bug 2040019] [NEW] Bash environment gets corrupted

[Charles Evans]

Public bug reported:

bash 5.1-6ubuntu1 (jammy)
After loading about 1000 aliases totaling 50kB
Setting 200 vars totaling 20kB (half from default profile)
And 1200 functions totaling 400kB (~100/72kB default completions) 
After running the occasional basic (but lengthy) scripts with no recursion, 
runtimes under 1 minute, all under 1 second CPU time in bash,
10-20 times a day for less than a month,

bash starts losing functions and variables and aliases.

Nothing in dmesg or syslog
System is otherwise stable:
-Memtest runs multiple passes ok
-Several GB of apt updates all verify no errors
-Checkrestart did not show any copies of bash needing restarts
-no suspends, no remote shell
-weekly apt updates run in this bash shell

kernel 6.2.0-32 generic
libc6 2.35-0ubuntu3.4

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bash in Ubuntu.
https://bugs.launchpad.net/bugs/2040019

Title:
  Bash environment gets corrupted

Status in bash package in Ubuntu:
  New

Bug description:
  bash 5.1-6ubuntu1 (jammy)
  After loading about 1000 aliases totaling 50kB
  Setting 200 vars totaling 20kB (half from default profile)
  And 1200 functions totaling 400kB (~100/72kB default completions) 
  After running the occasional basic (but lengthy) scripts with no recursion, 
runtimes under 1 minute, all under 1 second CPU time in bash,
  10-20 times a day for less than a month,

  bash starts losing functions and variables and aliases.

  Nothing in dmesg or syslog
  System is otherwise stable:
  -Memtest runs multiple passes ok
  -Several GB of apt updates all verify no errors
  -Checkrestart did not show any copies of bash needing restarts
  -no suspends, no remote shell
  -weekly apt updates run in this bash shell

  kernel 6.2.0-32 generic
  libc6 2.35-0ubuntu3.4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/2040019/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2040016] [NEW] no sound

[wlady]

Public bug reported:

no sound. all is ok ,, sound no

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: alsa-base 1.0.25+dfsg-0ubuntu7
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC2:  emika  1177 F wireplumber
 /dev/snd/controlC0:  emika  1177 F wireplumber
 /dev/snd/pcmC0D3p:   emika  1174 F...m pipewire
 /dev/snd/seq:emika  1174 F pipewire
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Fri Oct 20 22:16:00 2023
InstallationDate: Installed on 2023-10-20 (0 days ago)
InstallationMedia: Kubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231010)
PackageArchitecture: all
ProcEnviron:
 LANG=cs_CZ.UTF-8
 LANGUAGE=
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
SourcePackage: alsa-driver
Symptom: audio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/20/2022
dmi.bios.release: 15.10
dmi.bios.vendor: Insyde
dmi.bios.version: F.10
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 8A1B
dmi.board.vendor: HP
dmi.board.version: 17.25
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 17.25
dmi.modalias: 
dmi:bvnInsyde:bvrF.10:bd10/20/2022:br15.10:efr17.25:svnHP:pnHP25515.6inchG9NotebookPC:pvrType1ProductConfigId:rvnHP:rn8A1B:rvr17.25:cvnHP:ct10:cvrChassisVersion:sku6S6E5EA#ABD:
dmi.product.family: 103C_5336AN HP 200
dmi.product.name: HP 255 15.6 inch G9 Notebook PC
dmi.product.sku: 6S6E5EA#ABD
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug mantic

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/2040016

Title:
  no sound

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  no sound. all is ok ,, sound no

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  emika  1177 F wireplumber
   /dev/snd/controlC0:  emika  1177 F wireplumber
   /dev/snd/pcmC0D3p:   emika  1174 F...m pipewire
   /dev/snd/seq:emika  1174 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Fri Oct 20 22:16:00 2023
  InstallationDate: Installed on 2023-10-20 (0 days ago)
  InstallationMedia: Kubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231010)
  PackageArchitecture: all
  ProcEnviron:
   LANG=cs_CZ.UTF-8
   LANGUAGE=
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: alsa-driver
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/20/2022
  dmi.bios.release: 15.10
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.10
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8A1B
  dmi.board.vendor: HP
  dmi.board.version: 17.25
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 17.25
  dmi.modalias: 
dmi:bvnInsyde:bvrF.10:bd10/20/2022:br15.10:efr17.25:svnHP:pnHP25515.6inchG9NotebookPC:pvrType1ProductConfigId:rvnHP:rn8A1B:rvr17.25:cvnHP:ct10:cvrChassisVersion:sku6S6E5EA#ABD:
  dmi.product.family: 103C_5336AN HP 200
  dmi.product.name: HP 255 15.6 inch G9 Notebook PC
  dmi.product.sku: 6S6E5EA#ABD
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2040016/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2039752] Re: package openssh-server 1:9.0p1-1ubuntu8.5 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit status

[Steve Langasek]

Why did you have tinysshd installed in your container? That's not part
of a default Ubuntu system.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/2039752

Title:
  package openssh-server 1:9.0p1-1ubuntu8.5 failed to install/upgrade:
  installed openssh-server package post-installation script subprocess
  returned error exit status 1

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  I don't known, but the system report the bug

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: openssh-server 1:9.0p1-1ubuntu8.5
  ProcVersionSignature: Ubuntu 6.2.0-34.34-generic 6.2.16
  Uname: Linux 6.2.0-34-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Thu Oct 19 09:27:02 2023
  ErrorMessage: installed openssh-server package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2023-10-18 (0 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.21ubuntu1
   apt  2.6.0ubuntu0.1
  SourcePackage: openssh
  Title: package openssh-server 1:9.0p1-1ubuntu8.5 failed to install/upgrade: 
installed openssh-server package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2039752/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap

[Georgia Garcia]

Reuploading because I had a conflicting version with what was rejected
in -proposed

** Patch added: "evince_42.3-0ubuntu3.2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1794064/+attachment/5711859/+files/evince_42.3-0ubuntu3.2.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1794064

Title:
  Clicking a hyperlink in a PDF fails to open it if the default browser
  is a snap

Status in apparmor package in Ubuntu:
  Fix Released
Status in evince package in Ubuntu:
  Fix Released
Status in apparmor source package in Jammy:
  Fix Committed
Status in evince source package in Jammy:
  In Progress
Status in apparmor source package in Lunar:
  Fix Released
Status in evince source package in Lunar:
  Fix Released
Status in apparmor package in Debian:
  Fix Released
Status in evince package in Debian:
  Confirmed

Bug description:
  [Impact]

   * Users cannot open a hyperlink in a PDF opened with evince when the default 
browser is a snap.
   * The fix creates a snap_browsers abstraction on AppArmor which can be used 
in a transition for when the browser is executed. The snap_browsers abstraction 
provides the minimal amount of permissions required to execute a browser 
provided through snaps. This is a workaround since AppArmor currently does not 
provide mediation/filtering on enhanced environment variables.

  [Test Plan]

   * Make sure the default browser is provided through the snap store.
   * Open a PDF that contains a hyperlink using evince and click on the URL.
   * The browser should open the requested URL. 

  [Where problems could occur]

   * If the browser or snap core update to have new requirements for
  opening a browser, then the current policy could become obsolete and
  will need to be updated again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1996087] Re: Ensure supported codenames are accurate

[Simon Quigley]

** Changed in: vim (Ubuntu Lunar)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/1996087

Title:
  Ensure supported codenames are accurate

Status in vim package in Ubuntu:
  Fix Committed
Status in vim source package in Focal:
  Fix Released
Status in vim source package in Jammy:
  Fix Released
Status in vim source package in Kinetic:
  Won't Fix
Status in vim source package in Lunar:
  Fix Released

Bug description:
  In several stable releases of Ubuntu, Vim has information regarding
  releases that are outdated. It would be optimal for Vim to grab this
  data from distro-info-data (or similar), but unfortunately that is not
  the case. Therefore, the list needs to be updated.

  There is a minimal regression potential here; Vim simply reads a
  statically-set Perl array to determine if the release in the changelog
  and sources.list is supported or not. Any regression would present
  itself in external tooling that detects text highlighting, which is
  not a case I think we support in Ubuntu.

  A simple way to test this update is to download a package from the
  Lunar archive, and open the changelog with Vim. Instead of the
  changelog release (e.g. "lunar") showing as red, it should show as
  blue. I would also suggest editing sources.list, to ensure e.g. Eoan
  shows as EOL.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1996087/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2040011] [NEW] [SRU] Ensure supported codenames are accurate

[Simon Quigley]

Public bug reported:

In several stable releases of Ubuntu, Vim has information regarding
releases that are outdated. It would be optimal for Vim to grab this
data from distro-info-data (or similar), but unfortunately that is not
the case. Therefore, the list needs to be updated.

There is a minimal regression potential here; Vim simply reads a
statically-set Perl array to determine if the release in the changelog
and sources.list is supported or not. Any regression would present
itself in external tooling that detects text highlighting, which is not
a case I think we support in Ubuntu.

A simple way to test this update is to download a package from the Lunar
archive, and open the changelog with Vim. Instead of the changelog
release (e.g. "noble") showing as red, it should show as blue. I would
also suggest editing sources.list, to ensure e.g. Eoan shows as EOL.

** Affects: vim (Ubuntu)
 Importance: Wishlist
 Assignee: Simon Quigley (tsimonq2)
 Status: In Progress

** Affects: vim (Ubuntu Focal)
 Importance: Wishlist
 Assignee: Simon Quigley (tsimonq2)
 Status: In Progress

** Affects: vim (Ubuntu Jammy)
 Importance: Wishlist
 Assignee: Simon Quigley (tsimonq2)
 Status: In Progress

** Affects: vim (Ubuntu Lunar)
 Importance: Wishlist
 Assignee: Simon Quigley (tsimonq2)
 Status: In Progress

** Affects: vim (Ubuntu Mantic)
 Importance: Wishlist
 Assignee: Simon Quigley (tsimonq2)
 Status: In Progress

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

** Also affects: vim (Ubuntu Focal)
   Importance: Undecided
   Status: New

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

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

** Changed in: vim (Ubuntu Focal)
 Assignee: (unassigned) => Simon Quigley (tsimonq2)

** Changed in: vim (Ubuntu Jammy)
 Assignee: (unassigned) => Simon Quigley (tsimonq2)

** Changed in: vim (Ubuntu Lunar)
 Assignee: (unassigned) => Simon Quigley (tsimonq2)

** Changed in: vim (Ubuntu Mantic)
 Assignee: (unassigned) => Simon Quigley (tsimonq2)

** Changed in: vim (Ubuntu Focal)
   Status: New => In Progress

** Changed in: vim (Ubuntu Jammy)
   Status: New => In Progress

** Changed in: vim (Ubuntu Lunar)
   Status: New => In Progress

** Changed in: vim (Ubuntu Mantic)
   Status: New => In Progress

** Changed in: vim (Ubuntu Focal)
   Importance: Undecided => Wishlist

** Changed in: vim (Ubuntu Jammy)
   Importance: Undecided => Wishlist

** Changed in: vim (Ubuntu Lunar)
   Importance: Undecided => Wishlist

** Changed in: vim (Ubuntu Mantic)
   Importance: Undecided => Wishlist

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/2040011

Title:
  [SRU] Ensure supported codenames are accurate

Status in vim package in Ubuntu:
  In Progress
Status in vim source package in Focal:
  In Progress
Status in vim source package in Jammy:
  In Progress
Status in vim source package in Lunar:
  In Progress
Status in vim source package in Mantic:
  In Progress

Bug description:
  In several stable releases of Ubuntu, Vim has information regarding
  releases that are outdated. It would be optimal for Vim to grab this
  data from distro-info-data (or similar), but unfortunately that is not
  the case. Therefore, the list needs to be updated.

  There is a minimal regression potential here; Vim simply reads a
  statically-set Perl array to determine if the release in the changelog
  and sources.list is supported or not. Any regression would present
  itself in external tooling that detects text highlighting, which is
  not a case I think we support in Ubuntu.

  A simple way to test this update is to download a package from the
  Lunar archive, and open the changelog with Vim. Instead of the
  changelog release (e.g. "noble") showing as red, it should show as
  blue. I would also suggest editing sources.list, to ensure e.g. Eoan
  shows as EOL.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vim/+bug/2040011/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap

[Georgia Garcia]

** Patch removed: "evince_42.3-0ubuntu3.1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1794064/+attachment/5711419/+files/evince_42.3-0ubuntu3.1.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1794064

Title:
  Clicking a hyperlink in a PDF fails to open it if the default browser
  is a snap

Status in apparmor package in Ubuntu:
  Fix Released
Status in evince package in Ubuntu:
  Fix Released
Status in apparmor source package in Jammy:
  Fix Committed
Status in evince source package in Jammy:
  In Progress
Status in apparmor source package in Lunar:
  Fix Released
Status in evince source package in Lunar:
  Fix Released
Status in apparmor package in Debian:
  Fix Released
Status in evince package in Debian:
  Confirmed

Bug description:
  [Impact]

   * Users cannot open a hyperlink in a PDF opened with evince when the default 
browser is a snap.
   * The fix creates a snap_browsers abstraction on AppArmor which can be used 
in a transition for when the browser is executed. The snap_browsers abstraction 
provides the minimal amount of permissions required to execute a browser 
provided through snaps. This is a workaround since AppArmor currently does not 
provide mediation/filtering on enhanced environment variables.

  [Test Plan]

   * Make sure the default browser is provided through the snap store.
   * Open a PDF that contains a hyperlink using evince and click on the URL.
   * The browser should open the requested URL. 

  [Where problems could occur]

   * If the browser or snap core update to have new requirements for
  opening a browser, then the current policy could become obsolete and
  will need to be updated again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2039873] Re: liblxc-dev was built with LXC_DEVEL=1 in Ubuntu Jammy/Kinetic

[Aleksandr Mikhalitsyn]

I have updated a debdiff and removed the boilerplate comment in
`0002-Ubuntu-set-LXC_DEVEL-to-0.patch as suggested by Simon Déziel

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/2039873

Title:
  liblxc-dev was built with LXC_DEVEL=1 in Ubuntu Jammy/Kinetic

Status in lxc package in Ubuntu:
  New

Bug description:
  Dear colleagues,

  As I can see from:
  - 
https://git.launchpad.net/ubuntu/+source/lxc/tree/configure?h=applied/ubuntu/jammy
  - 
https://git.launchpad.net/ubuntu/+source/lxc/tree/configure?h=applied/ubuntu/kinetic

  LXC 5.0.0 was built with LXC_DEVEL=1 set. But for release build we
  should have LXC_DEVEL=0.

  LXC_DEVEL is a variable that appears in the /usr/include/lxc/version.h
  and then can be (and actually it is) used by other projects to detect
  if liblxc-dev is a development build or stable.

  Having LXC_DEVEL=1 makes problems for the users who want to build projects 
those are depend on liblxc
  from source (for example, LXD, go-lxc: 
https://github.com/canonical/lxd/pull/12420).

  Q: Why it was not a problem for so long?
  A: Because LXC API was stable for a long time, but recently we have extended 
liblxc API (https://github.com/lxc/lxc/pull/4260) and dependant package go-lxc 
was updated too (https://github.com/lxc/go-lxc/pull/166).
  This change was developed properly to be backward compatible with the old 
versions of liblxc. But, there is a problem. If LXC_DEVEL=1 then the macro 
check VERSION_AT_LEAST 
(https://github.com/lxc/go-lxc/blob/ccae595aa49e779f7ecc9250329967aa546acd31/lxc-binding.h#L7)
 is disabled. That's why we should *not* have LXC_DEVEL=1 for *any* release 
build of LXC.

  And also, as I can see the source code that was used to build LXC
  5.0.0 in Jammy/Kinetic is not precisely the same as in the official
  LXC 5.0.0 tag (https://github.com/lxc/lxc/tree/lxc-5.0.0).

  I understand that Jammy is a LTS release and making any changes is a
  problem and we should go through the SRU process. But I believe that
  we have to do something at least with LXC_DEVEL to make things work
  properly.

  Kind regards,
  Alex

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/2039873/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2039873] Re: liblxc-dev was built with LXC_DEVEL=1 in Ubuntu Jammy/Kinetic

[Aleksandr Mikhalitsyn]

** Patch removed: "set LXC_DEVEL to 0"
   
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/2039873/+attachment/5711815/+files/debdiff.diff

** Patch added: "set LXC_DEVEL to 0"
   
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/2039873/+attachment/5711843/+files/debdiff.diff

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/2039873

Title:
  liblxc-dev was built with LXC_DEVEL=1 in Ubuntu Jammy/Kinetic

Status in lxc package in Ubuntu:
  New

Bug description:
  Dear colleagues,

  As I can see from:
  - 
https://git.launchpad.net/ubuntu/+source/lxc/tree/configure?h=applied/ubuntu/jammy
  - 
https://git.launchpad.net/ubuntu/+source/lxc/tree/configure?h=applied/ubuntu/kinetic

  LXC 5.0.0 was built with LXC_DEVEL=1 set. But for release build we
  should have LXC_DEVEL=0.

  LXC_DEVEL is a variable that appears in the /usr/include/lxc/version.h
  and then can be (and actually it is) used by other projects to detect
  if liblxc-dev is a development build or stable.

  Having LXC_DEVEL=1 makes problems for the users who want to build projects 
those are depend on liblxc
  from source (for example, LXD, go-lxc: 
https://github.com/canonical/lxd/pull/12420).

  Q: Why it was not a problem for so long?
  A: Because LXC API was stable for a long time, but recently we have extended 
liblxc API (https://github.com/lxc/lxc/pull/4260) and dependant package go-lxc 
was updated too (https://github.com/lxc/go-lxc/pull/166).
  This change was developed properly to be backward compatible with the old 
versions of liblxc. But, there is a problem. If LXC_DEVEL=1 then the macro 
check VERSION_AT_LEAST 
(https://github.com/lxc/go-lxc/blob/ccae595aa49e779f7ecc9250329967aa546acd31/lxc-binding.h#L7)
 is disabled. That's why we should *not* have LXC_DEVEL=1 for *any* release 
build of LXC.

  And also, as I can see the source code that was used to build LXC
  5.0.0 in Jammy/Kinetic is not precisely the same as in the official
  LXC 5.0.0 tag (https://github.com/lxc/lxc/tree/lxc-5.0.0).

  I understand that Jammy is a LTS release and making any changes is a
  problem and we should go through the SRU process. But I believe that
  we have to do something at least with LXC_DEVEL to make things work
  properly.

  Kind regards,
  Alex

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/2039873/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2039873] Re: liblxc-dev was built with LXC_DEVEL=1 in Ubuntu Jammy/Kinetic

[Aleksandr Mikhalitsyn]

Simon wanted to make a debdiff for this issue because he has an
experience with that.

This is debdiff from me but this is the 1st debdiff in my life. Most
likely I did something wrong :-)

What I did:

1. set email and name

$ export DEBEMAIL="y...@email.com"
$ export DEBFULLNAME="Your Name"

2. pull source package

$ pull-lp-source liblxc-dev jammy

3. make required source modifications

4. edit debian/changelog file properly and not forget to add LP issue
link

$ debchange

5. form local source changes into patch

$ dpkg-source --commit

6. create a source package from sources

$ debuild -S -d

7. build a binary package and test it

$ debuild
$ dpkg -i your_package.deb

8. create a debdiff:

$ debdiff lxc_5.0.0~git2209-g5a7b9ce67-0ubuntu1.dsc
lxc_5.0.0~git2209-g5a7b9ce67-0ubuntu2.dsc > debdiff.diff

Huge thanks to Stéphane Graber for initial instructions about the
procedure.

** Patch added: "set LXC_DEVEL to 0"
   
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/2039873/+attachment/5711815/+files/debdiff.diff

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/2039873

Title:
  liblxc-dev was built with LXC_DEVEL=1 in Ubuntu Jammy/Kinetic

Status in lxc package in Ubuntu:
  New

Bug description:
  Dear colleagues,

  As I can see from:
  - 
https://git.launchpad.net/ubuntu/+source/lxc/tree/configure?h=applied/ubuntu/jammy
  - 
https://git.launchpad.net/ubuntu/+source/lxc/tree/configure?h=applied/ubuntu/kinetic

  LXC 5.0.0 was built with LXC_DEVEL=1 set. But for release build we
  should have LXC_DEVEL=0.

  LXC_DEVEL is a variable that appears in the /usr/include/lxc/version.h
  and then can be (and actually it is) used by other projects to detect
  if liblxc-dev is a development build or stable.

  Having LXC_DEVEL=1 makes problems for the users who want to build projects 
those are depend on liblxc
  from source (for example, LXD, go-lxc: 
https://github.com/canonical/lxd/pull/12420).

  Q: Why it was not a problem for so long?
  A: Because LXC API was stable for a long time, but recently we have extended 
liblxc API (https://github.com/lxc/lxc/pull/4260) and dependant package go-lxc 
was updated too (https://github.com/lxc/go-lxc/pull/166).
  This change was developed properly to be backward compatible with the old 
versions of liblxc. But, there is a problem. If LXC_DEVEL=1 then the macro 
check VERSION_AT_LEAST 
(https://github.com/lxc/go-lxc/blob/ccae595aa49e779f7ecc9250329967aa546acd31/lxc-binding.h#L7)
 is disabled. That's why we should *not* have LXC_DEVEL=1 for *any* release 
build of LXC.

  And also, as I can see the source code that was used to build LXC
  5.0.0 in Jammy/Kinetic is not precisely the same as in the official
  LXC 5.0.0 tag (https://github.com/lxc/lxc/tree/lxc-5.0.0).

  I understand that Jammy is a LTS release and making any changes is a
  problem and we should go through the SRU process. But I believe that
  we have to do something at least with LXC_DEVEL to make things work
  properly.

  Kind regards,
  Alex

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/2039873/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1781975] Re: please blacklist Prusa Research devices

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to modemmanager in Ubuntu.
https://bugs.launchpad.net/bugs/1781975

Title:
  please blacklist Prusa Research devices

Status in modemmanager package in Ubuntu:
  Confirmed

Bug description:
  Please add the following Prusa Research devices to the blacklist.
  These devices are Arduino based, there were many requests before to
  blacklist the Arduino based devices.

  VID 2c99
  PID 0001: product string "Original Prusa i3 MK2"
  PID 0002: product string "Original Prusa i3 MK3"
  PID 0003: product string "Original Prusa i3 MK3 Multi Material 2.0 upgrade 
(bootloader)"
  PID 0004: product string "Original Prusa i3 MK3 Multi Material 2.0 upgrade"

  or better blacklist all the PIDs of the VID 2c99.

  Thank you

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1781975/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1907878] Re: wrong var declaration in if-up.d/resolved (nm-dispatcher[54417]: /etc/network/if-up.d/resolved: 12: mystatedir: not found)

[Timo Aaltonen]

Hello Jacopo, or anyone else affected,

Accepted ifupdown into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/ifupdown/0.8.36+nmu1ubuntu3.1 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
jammy to verification-done-jammy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-jammy. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: ifupdown (Ubuntu Jammy)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-jammy

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/1907878

Title:
  wrong var declaration in if-up.d/resolved (nm-dispatcher[54417]:
  /etc/network/if-up.d/resolved: 12: mystatedir: not found)

Status in ifupdown package in Ubuntu:
  Fix Released
Status in ifupdown source package in Jammy:
  Fix Committed

Bug description:
  Syslog error:

     nm-dispatcher[...]: /etc/network/if-up.d/resolved: 12: mystatedir:
  not found

  I think it's because of this line:

    if systemctl is-enabled systemd-resolved > /dev/null 2>&1; then
    mystatedir statedir ifindex interface <- this 
is interpreted as a 'mystatedir' command and fails

    interface=$IFACE
    if [ ! "$interface" ]; then

  Perhaps the intention was to 'export mystatedir statedir ...'

  SRU for Jammy:

  [ Impact ]

 * /etc/network/if-{up,down}.d/resolved have a mistype:
 
 mystatedir statedir ifindex interface
 
 And when this line is executed, mystatedir is not found (not a valid 
command)
 and it generates an error log in /var/log/syslog and the terminal output. 
 It's not fatal, and the rest of the code gets executed, but it generates 
the
 message.
 
 # ifup ens3
 /etc/network/if-up.d/resolved: 12: mystatedir: not found

 # ifdown ens3
 /etc/network/if-down.d/resolved: 12: mystatedir: not found 
 
 The fix accepted in kinetic is only to remove this line. The same fix can 
be
 applied to Jammy.
 
  [ Test Plan ]

 With the new package installed, remove netplan configuration and add a 
valid
 /etc/network/interfaces file and then use the commands:
 
 # ifdown 
 # ifup 
 
 And confirm the messages are not displayed and the network configuration
 succeeds.
 
  [ Where problems could occur ]

 If mystatedir would be a valid command or function, which is not the case,
 that could break the script.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1907878/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1981103] Please test proposed package

[Timo Aaltonen]

Hello Uwe, or anyone else affected,

Accepted ifupdown into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/ifupdown/0.8.36+nmu1ubuntu3.1 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
jammy to verification-done-jammy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-jammy. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/1981103

Title:
  System with DNS server in /etc/network/interfaces has bogus systemd-
  resolved config after  upgrade to 22.04

Status in ifupdown package in Ubuntu:
  Fix Released
Status in ifupdown source package in Focal:
  Fix Released
Status in ifupdown source package in Jammy:
  Fix Committed
Status in ifupdown source package in Lunar:
  Fix Committed

Bug description:
  [ Impact ]
  ifupdown configurations will stop having a working DNS server on upgrade

  [ Test Plan ]
  Upgrading from an Ubuntu 18.04 or earlier release, bounce a network interface 
with configured DNS server:

  root@pangaea-pm:~# ifdown ens13; ifup ens13
  /etc/network/if-down.d/resolved: 12: mystatedir: not found
  /etc/network/if-up.d/resolved: 12: mystatedir: not found
  /etc/network/if-up.d/resolved: 71: DNS: not found
  /etc/network/if-up.d/resolved: 1: /run/network/ifupdown-inet-ens13: 
DNS=134.102.20.20 134.102.200.14: not found
  /etc/network/if-up.d/resolved: 2: /run/network/ifupdown-inet-ens13: 
DOMAINS=marum.de: not found
  Failed to parse DNS server address: DNS
  Failed to set DNS configuration: Invalid argument

  This should result in no errors, and in a valid network configuration with 
working DNS resolution.
  It's likely that existing netplan configuration needs to be removed and 
migrated to classic ifupdown scripts before running the test above.

  [ Where problems could occur ]
  Although we're only fixing the resolved scripts, more complex network setups 
might see regressions in DNS resolution for some cases. We should pay special 
attention to bridges or virtual interfaces that have been configured through 
ifupdown, as well as validate the other scripts under /etc/network/if-up.d/

  [ Other Info ]
  Description:Ubuntu 22.04 LTS
  Release:22.04

  ifupdown:
    Installed: 0.8.36+nmu1ubuntu3
    Candidate: 0.8.36+nmu1ubuntu3
    Version table:
   *** 0.8.36+nmu1ubuntu3 500
  500 http://de.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages
  100 /var/lib/dpkg/status

  After upgrading a server with classic ifupdown configuration after
  reboot the machine had no valid dns servers anymore.

  The problem is that the state file created by ifupdown using
  /etc/network/if-up.d/resolved looks like this:

  root@pangaea-pm:~# cat /run/network/ifupdown-inet-ens13
  "DNS"="134.102.20.20 134.102.200.14"
  "DOMAINS"="marum.de"

  The script later sources this file and causes the following errors,
  easy to see when you execute this:

  root@pangaea-pm:~# ifdown ens13; ifup ens13
  /etc/network/if-down.d/resolved: 12: mystatedir: not found
  /etc/network/if-up.d/resolved: 12: mystatedir: not found
  /etc/network/if-up.d/resolved: 71: DNS: not found
  /etc/network/if-up.d/resolved: 1: /run/network/ifupdown-inet-ens13: 
DNS=134.102.20.20 134.102.200.14: not found
  /etc/network/if-up.d/resolved: 2: /run/network/ifupdown-inet-ens13: 
DOMAINS=marum.de: not found
  Failed to parse DNS server address: DNS
  Failed to set DNS configuration: Invalid argument

  This happened to me on three different servers, so this is a serious
  bug and should be fixed before 22.04 upgrades are allowed for
  everybody. Most servers provided by data centers like Hetzner
  (Germany) are configure like that. After a do-release-upgrade you have
  no working DNS anymore, unless you disable systemd-resolved. I don't
  want to use netplan, so changing to this is no option.

  The fix is easy - remove the quotes in the script on the left side
  "$DNS" => $DNS; same for DOMAINS:

  if  [ -n "$NEW_DNS" 

[Touch-packages] [Bug 1981103] Re: System with DNS server in /etc/network/interfaces has bogus systemd-resolved config after upgrade to 22.04

[Timo Aaltonen]

Hello Uwe, or anyone else affected,

Accepted ifupdown into lunar-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/ifupdown/0.8.36+nmu1ubuntu4.1 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
lunar to verification-done-lunar. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-lunar. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: ifupdown (Ubuntu Lunar)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-lunar

** Changed in: ifupdown (Ubuntu Jammy)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-jammy

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/1981103

Title:
  System with DNS server in /etc/network/interfaces has bogus systemd-
  resolved config after  upgrade to 22.04

Status in ifupdown package in Ubuntu:
  Fix Released
Status in ifupdown source package in Focal:
  Fix Released
Status in ifupdown source package in Jammy:
  Fix Committed
Status in ifupdown source package in Lunar:
  Fix Committed

Bug description:
  [ Impact ]
  ifupdown configurations will stop having a working DNS server on upgrade

  [ Test Plan ]
  Upgrading from an Ubuntu 18.04 or earlier release, bounce a network interface 
with configured DNS server:

  root@pangaea-pm:~# ifdown ens13; ifup ens13
  /etc/network/if-down.d/resolved: 12: mystatedir: not found
  /etc/network/if-up.d/resolved: 12: mystatedir: not found
  /etc/network/if-up.d/resolved: 71: DNS: not found
  /etc/network/if-up.d/resolved: 1: /run/network/ifupdown-inet-ens13: 
DNS=134.102.20.20 134.102.200.14: not found
  /etc/network/if-up.d/resolved: 2: /run/network/ifupdown-inet-ens13: 
DOMAINS=marum.de: not found
  Failed to parse DNS server address: DNS
  Failed to set DNS configuration: Invalid argument

  This should result in no errors, and in a valid network configuration with 
working DNS resolution.
  It's likely that existing netplan configuration needs to be removed and 
migrated to classic ifupdown scripts before running the test above.

  [ Where problems could occur ]
  Although we're only fixing the resolved scripts, more complex network setups 
might see regressions in DNS resolution for some cases. We should pay special 
attention to bridges or virtual interfaces that have been configured through 
ifupdown, as well as validate the other scripts under /etc/network/if-up.d/

  [ Other Info ]
  Description:Ubuntu 22.04 LTS
  Release:22.04

  ifupdown:
    Installed: 0.8.36+nmu1ubuntu3
    Candidate: 0.8.36+nmu1ubuntu3
    Version table:
   *** 0.8.36+nmu1ubuntu3 500
  500 http://de.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages
  100 /var/lib/dpkg/status

  After upgrading a server with classic ifupdown configuration after
  reboot the machine had no valid dns servers anymore.

  The problem is that the state file created by ifupdown using
  /etc/network/if-up.d/resolved looks like this:

  root@pangaea-pm:~# cat /run/network/ifupdown-inet-ens13
  "DNS"="134.102.20.20 134.102.200.14"
  "DOMAINS"="marum.de"

  The script later sources this file and causes the following errors,
  easy to see when you execute this:

  root@pangaea-pm:~# ifdown ens13; ifup ens13
  /etc/network/if-down.d/resolved: 12: mystatedir: not found
  /etc/network/if-up.d/resolved: 12: mystatedir: not found
  /etc/network/if-up.d/resolved: 71: DNS: not found
  /etc/network/if-up.d/resolved: 1: /run/network/ifupdown-inet-ens13: 
DNS=134.102.20.20 134.102.200.14: not found
  /etc/network/if-up.d/resolved: 2: /run/network/ifupdown-inet-ens13: 
DOMAINS=marum.de: not found
  Failed to parse DNS server address: DNS
  Failed to set DNS configuration: Invalid argument

  This happened to me on three different servers, so this is a serious
  bug and should be fixed before 22.04 upgrades are allowed for
  everybody. Most servers provided by data centers like Hetzner
  (Germany) are configure like that. After a 

[Touch-packages] [Bug 2039873] Re: liblxc-dev was built with LXC_DEVEL=1 in Ubuntu Jammy/Kinetic

[Aleksandr Mikhalitsyn]

We have discussed that in the #lxd-dev IRC with Simon but I decided to
post it here for others.

It looks like we need to patch 3 places:
https://git.launchpad.net/ubuntu/+source/lxc/tree/configure.ac?h=applied/ubuntu/jammy#n3
https://git.launchpad.net/ubuntu/+source/lxc/tree/configure?h=applied/ubuntu/jammy#n3498
https://git.launchpad.net/ubuntu/+source/lxc/tree/src/lxc/version.h?h=applied/ubuntu/jammy#n6

For some reason, the sources which are used for Jammy LXC 5.0.0 use
autoconf/automake build system, at the same time upstream
https://github.com/lxc/lxc/tree/lxc-5.0.0 uses meson.

removing
https://git.launchpad.net/ubuntu/+source/lxc/tree/debian/patches/0003-meson-
Set-DEVEL-flag-post-release.patch won't help as we don't use meson.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/2039873

Title:
  liblxc-dev was built with LXC_DEVEL=1 in Ubuntu Jammy/Kinetic

Status in lxc package in Ubuntu:
  New

Bug description:
  Dear colleagues,

  As I can see from:
  - 
https://git.launchpad.net/ubuntu/+source/lxc/tree/configure?h=applied/ubuntu/jammy
  - 
https://git.launchpad.net/ubuntu/+source/lxc/tree/configure?h=applied/ubuntu/kinetic

  LXC 5.0.0 was built with LXC_DEVEL=1 set. But for release build we
  should have LXC_DEVEL=0.

  LXC_DEVEL is a variable that appears in the /usr/include/lxc/version.h
  and then can be (and actually it is) used by other projects to detect
  if liblxc-dev is a development build or stable.

  Having LXC_DEVEL=1 makes problems for the users who want to build projects 
those are depend on liblxc
  from source (for example, LXD, go-lxc: 
https://github.com/canonical/lxd/pull/12420).

  Q: Why it was not a problem for so long?
  A: Because LXC API was stable for a long time, but recently we have extended 
liblxc API (https://github.com/lxc/lxc/pull/4260) and dependant package go-lxc 
was updated too (https://github.com/lxc/go-lxc/pull/166).
  This change was developed properly to be backward compatible with the old 
versions of liblxc. But, there is a problem. If LXC_DEVEL=1 then the macro 
check VERSION_AT_LEAST 
(https://github.com/lxc/go-lxc/blob/ccae595aa49e779f7ecc9250329967aa546acd31/lxc-binding.h#L7)
 is disabled. That's why we should *not* have LXC_DEVEL=1 for *any* release 
build of LXC.

  And also, as I can see the source code that was used to build LXC
  5.0.0 in Jammy/Kinetic is not precisely the same as in the official
  LXC 5.0.0 tag (https://github.com/lxc/lxc/tree/lxc-5.0.0).

  I understand that Jammy is a LTS release and making any changes is a
  problem and we should go through the SRU process. But I believe that
  we have to do something at least with LXC_DEVEL to make things work
  properly.

  Kind regards,
  Alex

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/2039873/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2039752] Re: package openssh-server 1:9.0p1-1ubuntu8.5 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit status

[Mitchell Dzurick]

@Markle Liu if you still have your system in the affected state, could
you please give the output of these following commands?

# systemctl status ssh.{socket,service} tinysshd.socket
# lsof -i :22
# systemctl list-units | grep ssh

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/2039752

Title:
  package openssh-server 1:9.0p1-1ubuntu8.5 failed to install/upgrade:
  installed openssh-server package post-installation script subprocess
  returned error exit status 1

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  I don't known, but the system report the bug

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: openssh-server 1:9.0p1-1ubuntu8.5
  ProcVersionSignature: Ubuntu 6.2.0-34.34-generic 6.2.16
  Uname: Linux 6.2.0-34-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Thu Oct 19 09:27:02 2023
  ErrorMessage: installed openssh-server package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2023-10-18 (0 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.21ubuntu1
   apt  2.6.0ubuntu0.1
  SourcePackage: openssh
  Title: package openssh-server 1:9.0p1-1ubuntu8.5 failed to install/upgrade: 
installed openssh-server package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2039752/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2039752] Re: package openssh-server 1:9.0p1-1ubuntu8.5 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit status

[Mitchell Dzurick]

Interesting, I tried in a new LXC container and I see it working now.
$ lxc launch ubuntu:lunar l
$ lxc shell l
# apt install -y openssh-client=1:9.0p1-1ubuntu8 -y --allow-downgrades
# apt install -y openssh-sftp-server=1:9.0p1-1ubuntu8 -y --allow-downgrades
# apt install -y openssh-server=1:9.0p1-1ubuntu8 -y --allow-downgrades
# apt install -y openssh-server=1:9.0p1-1ubuntu8.5 -y


In my original container, the upgrade failed because tinysshd.socket was using 
port 22 so when openssh-server.postinst attempted to run `deb-systemd-invoke 
restart ssh.socket` it failed due to resource issues (port 22 already being 
used) which caused dpkg to fail. I assume this is the same case in the bug 
report

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/2039752

Title:
  package openssh-server 1:9.0p1-1ubuntu8.5 failed to install/upgrade:
  installed openssh-server package post-installation script subprocess
  returned error exit status 1

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  I don't known, but the system report the bug

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: openssh-server 1:9.0p1-1ubuntu8.5
  ProcVersionSignature: Ubuntu 6.2.0-34.34-generic 6.2.16
  Uname: Linux 6.2.0-34-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Thu Oct 19 09:27:02 2023
  ErrorMessage: installed openssh-server package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2023-10-18 (0 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.21ubuntu1
   apt  2.6.0ubuntu0.1
  SourcePackage: openssh
  Title: package openssh-server 1:9.0p1-1ubuntu8.5 failed to install/upgrade: 
installed openssh-server package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2039752/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2039752] Re: package openssh-server 1:9.0p1-1ubuntu8.5 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit status

[Mitchell Dzurick]

I only see those errors in a container. When I launch a VM to try this,
I see no errors.

$ lxc launch ubuntu:lunar l-vm --vm
$ lxc shell l-vm
# apt install -y openssh-client=1:9.0p1-1ubuntu8 -y --allow-downgrades
# apt install -y openssh-sftp-server=1:9.0p1-1ubuntu8 -y --allow-downgrades
# apt install -y openssh-server=1:9.0p1-1ubuntu8 -y --allow-downgrades
# apt install -y openssh-server=1:9.0p1-1ubuntu8.5
...
Setting up openssh-client (1:9.0p1-1ubuntu8.5) ...
Setting up openssh-sftp-server (1:9.0p1-1ubuntu8.5) ...
Setting up openssh-server (1:9.0p1-1ubuntu8.5) ...
rescue-ssh.target is a disabled or a static unit not running, not starting it.
Processing triggers for man-db (2.11.2-1) ...
Processing triggers for ufw (0.36.1-4.1ubuntu0.1) ...
Scanning processes...   
  
Scanning linux images...
  

Running kernel seems to be up-to-date.

No services need to be restarted.

No containers need to be restarted.

No user sessions are running outdated binaries.

No VM guests are running outdated hypervisor (qemu) binaries on this
host.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/2039752

Title:
  package openssh-server 1:9.0p1-1ubuntu8.5 failed to install/upgrade:
  installed openssh-server package post-installation script subprocess
  returned error exit status 1

Status in openssh package in Ubuntu:
  New

Bug description:
  I don't known, but the system report the bug

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: openssh-server 1:9.0p1-1ubuntu8.5
  ProcVersionSignature: Ubuntu 6.2.0-34.34-generic 6.2.16
  Uname: Linux 6.2.0-34-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Thu Oct 19 09:27:02 2023
  ErrorMessage: installed openssh-server package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2023-10-18 (0 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.21ubuntu1
   apt  2.6.0ubuntu0.1
  SourcePackage: openssh
  Title: package openssh-server 1:9.0p1-1ubuntu8.5 failed to install/upgrade: 
installed openssh-server package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2039752/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2039752] Re: package openssh-server 1:9.0p1-1ubuntu8.5 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit status

[Mitchell Dzurick]

Relevant Dpkg errors:

openssh-server (1:9.0p1-1ubuntu8.5) over (1:9.0p1-1ubuntu8)
...
Setting up openssh-server (1:9.0p1-1ubuntu8.5) ...
rescue-ssh.target is a disabled or a static unit not running, not starting it.
Could not execute systemctl:  at /usr/bin/deb-systemd-invoke line 145.
dpkg: error processing package openssh-server (--configure):
 installed openssh-server package post-installation script subprocess returned 
error exit status 1

So this error was seen when upgrading from the release version of
openssh in Lunar to the current latest version in updates.

I tried to reproduce in an lxc container. Had to downgrade 2 packages like so:
$ lxc launch ubuntu:lunar l
$ lxc shell l
# apt install -y openssh-sftp-server=1:9.0p1-1ubuntu8 -y --allow-downgrades
# apt install -y openssh-client=1:9.0p1-1ubuntu8 -y --allow-downgrades

upon downgrading openssh-server I see this error

Selecting previously unselected package openssh-server.
(Reading database ... 33940 files and directories currently installed.)
Preparing to unpack .../openssh-server_1%3a9.0p1-1ubuntu8_amd64.deb ...
Unpacking openssh-server (1:9.0p1-1ubuntu8) ...
Setting up openssh-server (1:9.0p1-1ubuntu8) ...
rescue-ssh.target is a disabled or a static unit not running, not starting it.
Could not execute systemctl:  at /usr/bin/deb-systemd-invoke line 145.
dpkg: error processing package openssh-server (--configure):
 installed openssh-server package post-installation script subprocess returned 
error exit stat
us 1
dmesg: read kernel buffer failed: Operation not permitted
 Processing triggers 
for man-db (2.11.
2-1) ...
Processing triggers for ufw (0.36.1-4.1ubuntu0.1) ...
Errors were encountered while processing:
 openssh-server
needrestart is being skipped since dpkg has failed
E: Sub-process /usr/bin/dpkg returned an error code (1)


Attempting to upgrade to 8.5 I see:

root@l:~# apt-cache policy openssh-server
Setting up openssh-client (1:9.0p1-1ubuntu8.5) ...
Setting up openssh-sftp-server (1:9.0p1-1ubuntu8.5) ...
Setting up openssh-server (1:9.0p1-1ubuntu8.5) ...
rescue-ssh.target is a disabled or a static unit not running, not starting it.
Could not execute systemctl:  at /usr/bin/deb-systemd-invoke line 145.
dpkg: error processing package openssh-server (--configure):
 installed openssh-server package post-installation script subprocess returned 
error exit stat
us 1
dmesg: read kernel buffer failed: Operation not permitted
 Processing triggers 
for man-db (2.11.
2-1) ...
Processing triggers for ufw (0.36.1-4.1ubuntu0.1) ...
Errors were encountered while processing:
 openssh-server
needrestart is being skipped since dpkg has failed
E: Sub-process /usr/bin/dpkg returned an error code (1)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/2039752

Title:
  package openssh-server 1:9.0p1-1ubuntu8.5 failed to install/upgrade:
  installed openssh-server package post-installation script subprocess
  returned error exit status 1

Status in openssh package in Ubuntu:
  New

Bug description:
  I don't known, but the system report the bug

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: openssh-server 1:9.0p1-1ubuntu8.5
  ProcVersionSignature: Ubuntu 6.2.0-34.34-generic 6.2.16
  Uname: Linux 6.2.0-34-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Thu Oct 19 09:27:02 2023
  ErrorMessage: installed openssh-server package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2023-10-18 (0 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.21ubuntu1
   apt  2.6.0ubuntu0.1
  SourcePackage: openssh
  Title: package openssh-server 1:9.0p1-1ubuntu8.5 failed to install/upgrade: 
installed openssh-server package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2039752/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2039252] Re: [needs-packaging] The packages ntp and ntpsec are not equivalent

[Jonathan Ferguson]

I found the thread on the Debian Developers' Mailing List that Richard
Laager (rlaager) mentioned.  https://lists.debian.org/debian-
devel/2022/01/msg00172.html

I read through all of the replies in the aforementioned thread.

There is this devastating nugget that is not expounded upon and is the same 
crux I am bringing to the Ubuntu community's attention:
"Sounds good, I'd like to have a few more reviewers though. ntp is aged, but 
according to popcon the transition could affect ~25% of the Debian 
installations."  https://lists.debian.org/debian-devel/2022/01/msg00211.html

I believe that it is critical that Ubuntu makes available the most
feature complete standards complying NTP daemon.  https://www.rfc-
editor.org/rfc/rfc5905

The present LTS, 22.04, has the original ntp package.  To advert
disaster for a substantial number of users, Ubuntu will need the
original ntp package available when 24.04LTS is released.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ntp in Ubuntu.
https://bugs.launchpad.net/bugs/2039252

Title:
  [needs-packaging] The packages ntp and ntpsec are not equivalent

Status in NTP:
  New
Status in ntp package in Ubuntu:
  Confirmed
Status in ntp package in Debian:
  Confirmed

Bug description:
  I recently did an install of Ubuntu 23.04 and then configured ntp as I have 
been doing so for more than 8 years.
  With previous versions of Debian and Ubuntu using the real ntp package, the 
details at https://wiki.ubuntu.com/JonathanFerguson/NTP?action=recall=38 
created the desired results.
  I updated the details at https://wiki.ubuntu.com/JonathanFerguson/NTP with 
the new location of ntp.conf, after restarting I noticed that the resultant 
output was missing requisite details.

  
  Compare the following and the lack of ".MCST." and ".ACST.":

  Original ntp on Apollo-Lake-N3150
  jonathan@Apollo-Lake-N3450:~$ lsb_release -rd
  Description:Ubuntu 22.04.3 LTS
  Release:22.04
  jonathan@Apollo-Lake-N3450:~$ ntpq -p
   remote   refid  st t when poll reach   delay   offset  jitter
  ==
   0.ubuntu.pool.n .POOL.  16 p-   6400.000   +0.000   0.000
   1.ubuntu.pool.n .POOL.  16 p-   6400.000   +0.000   0.000
   2.ubuntu.pool.n .POOL.  16 p-   6400.000   +0.000   0.000
   3.ubuntu.pool.n .POOL.  16 p-   6400.000   +0.000   0.000
   ntp.ubuntu.com  .POOL.  16 p-   6400.000   +0.000   0.000
   ntp.mcast.net   .MCST.  16 M-   6400.000   +0.000   0.000
   ff0e::101   .MCST.  16 M-   6400.000   +0.000   0.000
   ntp.mcast.net   .ACST.  16 a-   6400.000   +0.000   0.000
   ff0e::101   .ACST.  16 a-   6400.000   +0.000   0.000
  *time.cloudflare 10.242.8.77  3 u  469 1024  367  234.691   -0.929  67.380
  +2001-44b8-2100- 42.3.115.79  2 u  581 1024  377  487.209  +55.669  57.154
  +2001-44b8-2100- 4.179.66.17  3 u  215 1024  377  489.637  +57.002  35.399
  jonathan@Apollo-Lake-N3450:~$

  NTPsec on Braswell-N3150
  jonathan@Braswell-N3150:~$ lsb_release -rd
  No LSB modules are available.
  Description:Ubuntu 23.04
  Release:23.04
  jonathan@Braswell-N3150:~$ ntpq -p
   remote   refid  st t when poll reach 
  delay   offset   jitter
  
===
   0.ubuntu.pool.ntp.org   .POOL.  16 p-  2560  
 0.   0.   0.0002
   1.ubuntu.pool.ntp.org   .POOL.  16 p-  2560  
 0.   0.   0.0002
   2.ubuntu.pool.ntp.org   .POOL.  16 p-  2560  
 0.   0.   0.0002
   3.ubuntu.pool.ntp.org   .POOL.  16 p-   640  
 0.   0.   0.0002
  +prod-ntp-5.ntp1.ps5.canonical.com   37.15.221.1892 u  141 1024  367 
383.4932 -19.6895  35.0534
  *time.tfmcloud.au203.35.83.2422 u  325 1024  367 
325.9317  -0.1496  43.0522
  +any.time.nl 133.243.238.243  2 u  158 1024  373 
300.7941 -20.8962 136.1422
  +ntp2.its.waikato.ac.nz  .GPS.1 u  363 1024  377 
356.5361 -18.2740 140.5984
  +2001-44b8-2100-3f00---007b-0004 42.3.115.79  2 u  214 1024  367 
490.3898  28.3416   2.7728
  +tic.ntp.telstra.net 203.35.83.2422 u   13 1024  367 
566.0744 -14.1332   6.0377
  +863xqmprtfqv69pv7nwc.ip6.superloop.au   192.168.1.1  2 u   79 1024  367 
330.2658 -14.3483  16.2172
  +gps-ads.10mrlp.juneks.com.au.PPS.1 u  271 1024  367 
443.4812 -71.8020  44.6332
  +x.ns.gin.ntt.net129.250.35.222   2 u   57 1024  367  

[Touch-packages] [Bug 2039868] Re: amdgpu reset during usage of firefox

[Pirouette Cacahuète]

Thanks, I'll try and keep you updated, however I am also facing bug
2039958 (probably a dupe of bug 2034619), so I might still need GNOME
45.1 to be released.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2039868

Title:
  amdgpu reset during usage of firefox

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  New

Bug description:
  Running nightly on 23.10 (since monday), I have been experiencing a
  few amdgpu resets in the past hours

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-9-generic 6.5.0-9.9
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 19 18:26:43 2023
  HibernationDevice: RESUME=/dev/mapper/vg--ubuntu-lv--ubuntu--swap
  InstallationDate: Installed on 2022-07-04 (472 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-9-generic 
root=/dev/mapper/vg--ubuntu-lv--ubuntu--root ro rootflags=subvol=@ quiet splash 
resume=/dev/mapper/vg--ubuntu-lv--ubuntu--swap vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-9-generic N/A
   linux-backports-modules-6.5.0-9-generic  N/A
   linux-firmware   20230919.git3672ccab-0ubuntu2.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to mantic on 2023-10-16 (3 days ago)
  dmi.bios.date: 05/15/2023
  dmi.bios.release: 1.24
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1MET54W (1.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21A0CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.24
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1MET54W(1.24):bd05/15/2023:br1.24:efr1.24:svnLENOVO:pn21A0CTO1WW:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A0CTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a:
  dmi.product.family: ThinkPad P14s Gen 2a
  dmi.product.name: 21A0CTO1WW
  dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a
  dmi.product.version: ThinkPad P14s Gen 2a
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2039868/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2039868] Re: amdgpu reset during usage of firefox

[Mario Limonciello]

6.5.6 has the fix for preemption issue, it should get fixed when stable
updates come in Mantic.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2039868

Title:
  amdgpu reset during usage of firefox

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  New

Bug description:
  Running nightly on 23.10 (since monday), I have been experiencing a
  few amdgpu resets in the past hours

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-9-generic 6.5.0-9.9
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 19 18:26:43 2023
  HibernationDevice: RESUME=/dev/mapper/vg--ubuntu-lv--ubuntu--swap
  InstallationDate: Installed on 2022-07-04 (472 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-9-generic 
root=/dev/mapper/vg--ubuntu-lv--ubuntu--root ro rootflags=subvol=@ quiet splash 
resume=/dev/mapper/vg--ubuntu-lv--ubuntu--swap vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-9-generic N/A
   linux-backports-modules-6.5.0-9-generic  N/A
   linux-firmware   20230919.git3672ccab-0ubuntu2.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to mantic on 2023-10-16 (3 days ago)
  dmi.bios.date: 05/15/2023
  dmi.bios.release: 1.24
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1MET54W (1.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21A0CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.24
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1MET54W(1.24):bd05/15/2023:br1.24:efr1.24:svnLENOVO:pn21A0CTO1WW:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A0CTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a:
  dmi.product.family: ThinkPad P14s Gen 2a
  dmi.product.name: 21A0CTO1WW
  dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a
  dmi.product.version: ThinkPad P14s Gen 2a
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2039868/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1091645] Re: When ISP changes dynamic IP address avahi-daemon changes Zeroconf host name

[Summia]

https://ownsby.com/, your website is exceptional! The aesthetics are
stunning, and the content is enriching. Navigating through your pages is
a pleasure. Thank you for this fantastic online experience!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to avahi in Ubuntu.
https://bugs.launchpad.net/bugs/1091645

Title:
  When ISP changes dynamic IP address avahi-daemon changes Zeroconf host
  name

Status in avahi package in Ubuntu:
  Confirmed

Bug description:
  I have a home network with several Ubuntu and one Mac OS X machine.
  Internet access is via VDSL with dynamic IP addresses, amd the ISP
  changes the IP address every night, around 4am. ISP is Deutsche
  Telekom in Germany. On my Ubuntu (Quantal) machines, connecting to the
  network only via ethernet (wired, W-Fi connection turned off on the
  machines, due to bug 1083565) avahi-daemon sometimes switches the
  Zeroconf hostname from the originally given one (like "till-hp") to a
  name with an added number, (like "till-hp-2"). This happens on the
  nightly IP address change as the attached syslog shows. Problem is
  that on clients I cannot refer to the Zeroconf names as they can
  change on the next day. If I restart avahi-daemon during the day the
  Zeroconf name gets reset to the original.

  It is possible that bug 1083565 is this one in reality, but I am not
  absolutely sure.

  As BonJour replaces the IPP-based CUPS broadcasting for printer
  discovery from CUPS 1.6.x on, avahi must be made more reliable.

  Also Zeroconf as replacement for DNS on the local network, to avoid
  the need that home users have to register host names on the router,
  need a reliable Avahi in term of the Zeroconf host names.

  In the attached syslog, aroung 4:18am the following appears (machine
  set up with "till-hp" as host name):

  --
  Dec 17 04:09:41 till-hp avahi-daemon[822]: Registering new address record for 
2002:5ddb:9586:0:7c4d:f18c:29e3:8b33 on eth0.*.
  Dec 17 04:09:42 till-hp NetworkManager[853]:  Policy set 'Wired 
connection 1' (eth0) as default for IPv6 routing and DNS.
  Dec 17 04:09:43 till-hp avahi-daemon[822]: Withdrawing address record for 
2002:5ddb:9586:0:e0b8:4178:444a:af6c on eth0.
  Dec 17 04:17:01 till-hp CRON[3993]: (root) CMD ( cd / && run-parts --report 
/etc/cron.hourly)
  Dec 17 04:18:45 till-hp avahi-daemon[822]: Withdrawing address record for 
2002:5ddb:9586:0:7c4d:f18c:29e3:8b33 on eth0.
  Dec 17 04:18:45 till-hp avahi-daemon[822]: Registering new address record for 
2002:5ddb:9586:0:7c4d:f18c:29e3:8b33 on eth0.*.
  Dec 17 04:18:45 till-hp avahi-daemon[822]: Registering new address record for 
2002:5ddb:9586:0:e0b8:4178:444a:af6c on eth0.*.
  Dec 17 04:18:45 till-hp avahi-daemon[822]: Registering new address record for 
fe80::20f:b0ff:fe6e:a460 on eth0.*.
  Dec 17 04:18:46 till-hp NetworkManager[853]:  Policy set 'Wired 
connection 1' (eth0) as default for IPv6 routing and DNS.
  Dec 17 04:18:46 till-hp avahi-daemon[822]: Registering new address record for 
fd00::20f:b0ff:fe6e:a460 on eth0.*.
  Dec 17 04:18:46 till-hp avahi-daemon[822]: Withdrawing address record for 
2002:5ddb:9586:0:7c4d:f18c:29e3:8b33 on eth0.
  Dec 17 04:18:46 till-hp avahi-daemon[822]: Withdrawing address record for 
2002:5ddb:9586:0:e0b8:4178:444a:af6c on eth0.
  Dec 17 04:18:46 till-hp avahi-daemon[822]: Withdrawing address record for 
2002:5ddb:9586:0:20f:b0ff:fe6e:a460 on eth0.
  Dec 17 04:18:46 till-hp avahi-daemon[822]: Withdrawing address record for 
fe80::20f:b0ff:fe6e:a460 on eth0.
  Dec 17 04:18:46 till-hp avahi-daemon[822]: Withdrawing workstation service 
for eth1. http://somapills.net
  Dec 17 04:18:46 till-hp avahi-daemon[822]: Withdrawing address record for 
192.168.178.34 on eth0.
  Dec 17 04:18:46 till-hp avahi-daemon[822]: Withdrawing workstation service 
for eth0.
  Dec 17 04:18:46 till-hp avahi-daemon[822]: Withdrawing workstation service 
for lo.
  Dec 17 04:18:46 till-hp avahi-daemon[822]: Host name conflict, retrying with 
till-hp-2
  Dec 17 04:18:46 till-hp avahi-daemon[822]: Registering new address record for 
fd00::20f:b0ff:fe6e:a460 on eth0.*.
  Dec 17 04:18:46 till-hp avahi-daemon[822]: Registering new address record for 
192.168.178.34 on eth0.IPv4.
  Dec 17 04:18:46 till-hp avahi-daemon[822]: Registering HINFO record with 
values 'I686'/'LINUX'.
  Dec 17 04:18:47 till-hp avahi-daemon[822]: Registering new address record for 
fd00::7c4d:f18c:29e3:8b33 on eth0.*.
  Dec 17 04:18:47 till-hp avahi-daemon[822]: Leaving mDNS multicast group on 
interface eth0.IPv6 with address 2002:5ddb:9586:0:e0b8:4178:444a:af6c.
  Dec 17 04:18:47 till-hp avahi-daemon[822]: Joining mDNS multicast group on 
interface eth0.IPv6 with address fd00::7c4d:f18c:29e3:8b33.
  Dec 17 04:18:47 till-hp avahi-daemon[822]: Withdrawing address record for 
fd00::7c4d:f18c:29e3:8b33 on eth0.
  Dec 17 04:18:47 till-hp avahi-daemon[822]: Registering new address record for 

[Touch-packages] [Bug 2036358] Re: systemd wait-online now times out after jammy and lunar upgrade

[Isaac True]

systemd 249.11-0ubuntu3.11 does *not* solve the issue for me. I seem to
be running into the same situation as Werner in #32 where `optional:
true` from the netplan config is not being respected.

systemd-networkd-wait-online seems to ignore `RequiredForOnline=no` in
the .network config.

Netplan config:

ubuntu@ubuntu:~$ sudo netplan get
network:
  version: 2
  ethernets:
eth0:
  optional: true
  dhcp4: true
  dhcp6: true
pfe:
  match:
name: "pfe*"
  optional: true
  dhcp4: true
  dhcp6: true

systemd-networkd configs:

ubuntu@ubuntu:~$ grep '' /run/systemd/network/10-netplan-*
/run/systemd/network/10-netplan-eth0.network:[Match]
/run/systemd/network/10-netplan-eth0.network:Name=eth0
/run/systemd/network/10-netplan-eth0.network:
/run/systemd/network/10-netplan-eth0.network:[Link]
/run/systemd/network/10-netplan-eth0.network:RequiredForOnline=no
/run/systemd/network/10-netplan-eth0.network:
/run/systemd/network/10-netplan-eth0.network:[Network]
/run/systemd/network/10-netplan-eth0.network:DHCP=yes
/run/systemd/network/10-netplan-eth0.network:LinkLocalAddressing=ipv6
/run/systemd/network/10-netplan-eth0.network:
/run/systemd/network/10-netplan-eth0.network:[DHCP]
/run/systemd/network/10-netplan-eth0.network:RouteMetric=100
/run/systemd/network/10-netplan-eth0.network:UseMTU=true
/run/systemd/network/10-netplan-pfe.network:[Match]
/run/systemd/network/10-netplan-pfe.network:Name=pfe*
/run/systemd/network/10-netplan-pfe.network:
/run/systemd/network/10-netplan-pfe.network:[Link]
/run/systemd/network/10-netplan-pfe.network:RequiredForOnline=no
/run/systemd/network/10-netplan-pfe.network:
/run/systemd/network/10-netplan-pfe.network:[Network]
/run/systemd/network/10-netplan-pfe.network:DHCP=yes
/run/systemd/network/10-netplan-pfe.network:LinkLocalAddressing=ipv6
/run/systemd/network/10-netplan-pfe.network:
/run/systemd/network/10-netplan-pfe.network:[DHCP]
/run/systemd/network/10-netplan-pfe.network:RouteMetric=100
/run/systemd/network/10-netplan-pfe.network:UseMTU=true

eth0 is configured:
ubuntu@ubuntu:~$ networkctl list
IDX LINK  TYPE OPERATIONAL SETUP
  1 loloopback carrier unmanaged
  2 eth0  etherroutableconfigured
  3 can0  can  off unmanaged
  4 can1  can  off unmanaged
  5 llcecan0  can  off unmanaged
  6 llcecan1  can  off unmanaged
  7 llcecan2  can  off unmanaged
  8 llcecan3  can  off unmanaged
  9 llcecan4  can  off unmanaged
 10 llcecan5  can  off unmanaged
 11 llcecan6  can  off unmanaged
 12 llcecan7  can  off unmanaged
 13 llcecan8  can  off unmanaged
 14 llcecan9  can  off unmanaged
 15 llcecan10 can  off unmanaged
 16 llcecan11 can  off unmanaged
 17 llcecan13 can  off unmanaged
 18 llcecan14 can  off unmanaged
 19 llcecan15 can  off unmanaged
 20 pfe0  etherdegradedconfiguring
 21 pfe1  etherno-carrier  configuring
 22 pfe2  etherno-carrier  configuring

22 links listed.


systemd-networkd-wait-online times out:

ubuntu@ubuntu:~$ sudo SYSTEMD_LOG_LEVEL=debug 
/lib/systemd/systemd-networkd-wait-online --timeout=10
Found link 22
Found link 21
Found link 20
Found link 19
Found link 18
Found link 17
Found link 16
Found link 15
Found link 14
Found link 13
Found link 12
Found link 11
Found link 10
Found link 9
Found link 8
Found link 7
Found link 6
Found link 5
Found link 4
Found link 3
Found link 2
Found link 1
llcecan2: link is not managed by networkd (yet?).
llcecan0: link is not managed by networkd (yet?).
llcecan7: link is not managed by networkd (yet?).
llcecan9: link is not managed by networkd (yet?).
llcecan4: link is not managed by networkd (yet?).
llcecan10: link is not managed by networkd (yet?).
pfe1: link is ignored
can0: link is not managed by networkd (yet?).
pfe0: link is ignored
llcecan3: link is not managed by networkd (yet?).
eth0: link is ignored
llcecan11: link is not managed by networkd (yet?).
llcecan6: link is not managed by networkd (yet?).
lo: link is ignored
llcecan13: link is not managed by networkd (yet?).
llcecan1: link is not managed by networkd (yet?).
can1: link is not managed by networkd (yet?).
pfe2: link is ignored
llcecan14: link is not managed by networkd (yet?).
llcecan8: link is not managed by networkd (yet?).
llcecan15: link is not managed by networkd (yet?).
llcecan5: link is not managed by networkd (yet?).
Timeout occurred while waiting for network connectivity.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2036358

Title:
  systemd wait-online now times out after jammy and lunar upgrade

Status in systemd package in Ubuntu:
  Invalid
Status in systemd source package in Jammy:
  Fix Committed
Status in systemd source 

[Touch-packages] [Bug 1775457] Re: /usr/bin/pip3:ImportError:/usr/bin/pip3@9

[Bug Watch Updater]

** Changed in: pip
   Status: Unknown => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1775457

Title:
  /usr/bin/pip3:ImportError:/usr/bin/pip3@9

Status in pip:
  Fix Released
Status in apport package in Ubuntu:
  New
Status in python-pip package in Ubuntu:
  Invalid

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
python-pip.  This problem was most recently seen with package version 
9.0.1-2.3~ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/4e26eab10247fe3383fb8c84ca8a0d8eb21abc83 
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/pip/+bug/1775457/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2036358] Re: systemd wait-online now times out after jammy and lunar upgrade

[Oscar Guertler]

Currently experiencing the same issue as @wharnisch2 on ubuntu 22.04.3
5.15.0-86-generic with systemd 249 (249.11-0ubuntu3.10) on a somewhat
fresh install (few weeks old)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2036358

Title:
  systemd wait-online now times out after jammy and lunar upgrade

Status in systemd package in Ubuntu:
  Invalid
Status in systemd source package in Jammy:
  Fix Committed
Status in systemd source package in Lunar:
  Fix Committed

Bug description:
  [NOTE]

  If you are running a desktop system and you see this issue, you should
  run:

  $ systemctl disable --now systemd-networkd.service

  This will disable systemd-networkd and associated units, including
  systemd-networkd-wait-online.service. NetworkManager and systemd-
  networkd should not be running at the same time. On desktop,
  NetworkManager is the default network stack.

  [Impact]

  When all interfaces are "not required for online", e.g. when they are
  marked "optional: true" in netplan, systemd-networkd-wait-online will
  timeout. Or, in other words, systemd-networkd-wait-online will timeout
  even though all interfaces are ignored, hence none of them will ever
  be marked as "ready." Depending on what units depend on network-
  online.target, this can delay boot by 120 seconds (the default timeout
  for systemd-networkd-wait-online).

  [Test Plan]

  1. Create a new LXD container. These instructions assume jammy is the
  release, but the same can be done for lunar.

  $ lxc launch ubuntu-daily:jammy jammy
  $ lxc exec jammy bash

  2. Once in the container, modify the default /etc/netplan/10-lxc.yaml
  so that eth0 is configured with "optional: true":

  $ vi /etc/netplan/50-cloud-init.yaml # Use whatever editor you like
  $ cat /etc/netplan/50-cloud-init.yaml
  network:
    version: 2
    ethernets:
  eth0:
    dhcp4: true
    dhcp-identifier: mac
    optional: true

  3. Re-generate and apply the netplan configuration.

  $ netplan generate
  $ netplan apply

  4. Manually run systemd-networkd-wait-online, and observe that all
  links are ignored, and the command times out:

  $ SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-networkd-wait-online 
--timeout=10
  Found link lo(1)
  Found link eth0(19)
  lo: link is ignored
  eth0: link is ignored
  Timeout occurred while waiting for network connectivity.

  [Where problems could occur]

  This patch partially re-instates a patch remove in bug 1982218.
  However, instead of exiting if all links are unmanaged, we exit if all
  links are ignored in manager_configured(). If the patch was wrong, we
  may re-introduce bug 1982218, so as part of this SRU verification,
  that bug should be tested too. Any other regressions would also be
  related to systemd-networkd-wait-online behavior.

  [Original Description]

  On Ubuntu 22.04 desktop system using network-manager and upgrading to
  systemd 249.11-0ubuntu3.10, wait-online now times out which prevents
  logins (GDM, ssh, console) until it does time out. This seems to be
  introduced by the change for
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982218.

  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982218/comments/21
  also mentioned the problem on Lunar.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2036358/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp