[Touch-packages] [Bug 1556452] Re: 4K@60Hz DisplayPort 1.2 loses output modes

[Launchpad Bug Tracker]

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

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

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

Title:
  4K@60Hz DisplayPort 1.2 loses output modes

Status in xorg package in Ubuntu:
  Expired

Bug description:
  I have a Dell UP2414Q 24" 4K display panel. The only way to achieve
  60Hz refresh on it, is to use DisplayPort 1.2 MST.

  Due to MST, this results in two screens with 1920x2160 resolution
  being exposed to X. In order to get back to a proper rendering where
  it looks like a single display, one must either use Xinerama (with
  NVidia) or Xorg 3.18 and the new xrandr with support for configuring
  monitors in RandR 1.5 (with Intel). In both of these configurations,
  if the monitor itself is powered off, the output modes will disappear
  from xrandr, and when the monitor is powered back on, it behaves as
  though no output is being sent to it over the DisplayPort connection.
  When connecting with ssh to debug, running DISPLAY=:0 xrandr says that
  the two outputs exist, but no modes are configured, and indeed it does
  not list any. If however, instead of powering the monitor off, it is
  left on while away, this does not occur upon return, and the display
  works normally as when it was left.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4
  Uname: Linux 4.4.0-12-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sat Mar 12 12:26:16 2016
  DistUpgraded: 2016-03-10 16:26:10,719 DEBUG failed to SystemUnLock() (E:Not 
locked)
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.16, 4.4.0-11-generic, x86_64: installed
   virtualbox, 5.0.16, 4.4.0-11-lowlatency, x86_64: installed
   virtualbox, 5.0.16, 4.4.0-12-generic, x86_64: installed
   virtualbox, 5.0.16, 4.4.0-12-lowlatency, x86_64: installed
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Xeon E3-1200 v3/4th 
Gen Core Processor Integrated Graphics Controller [1462:7919]
  InstallationDate: Installed on 2012-10-21 (1237 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MachineType: MSI MS-7919
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-12-generic 
root=UUID=167bf6e1-727f-4db1-b2f9-c496700b301b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-03-10 (1 days ago)
  dmi.bios.date: 04/30/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97M GAMING (MS-7919)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.0:bd04/30/2014:svnMSI:pnMS-7919:pvr1.0:rvnMSI:rnZ97MGAMING(MS-7919):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.name: MS-7919
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz 1:0.9.12.2+16.04.20160209-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.2-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.2-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.1-1ubuntu4
  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.6.1-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160218-1ubuntu3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sat Mar 12 11:07:14 2016
  xserver.configfile: default
  xserver.devices:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.1-1ubuntu4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1556452/+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 1444880] Re: xrandr report inverted gamma values

[Launchpad Bug Tracker]

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

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

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

Title:
  xrandr report inverted gamma values

Status in xorg package in Ubuntu:
  Expired

Bug description:
  $ xrandr --output VGA1  --gamma 1:1:1.7
  $ xrandr --verbose | grep -iE '(gamma|bright)'
  Gamma:  1.0:1.0:1.7
  Brightness: 1.0
  Gamma:  1.0:1.0:0.59
  Brightness: 1.0
  $ xrandr --output VGA1  --gamma 1:1:.6
  $ xrandr --verbose | grep -iE '(gamma|bright)'
  Gamma:  1.0:1.0:1.7
  Brightness: 1.0
  Gamma:  1.0:1.0:1.7
  Brightness: 1.0

  As you can see in output of commands above, "Gamma" values printed by
  xrandr --verbose are exactly the invert of the values set: 1/... Appart for value 1.0 which is correct.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1444880/+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 1590457] Re: Switching to proprietary nvidia driver prevents compiz from starting

[Launchpad Bug Tracker]

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

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

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

Title:
  Switching to proprietary nvidia driver prevents compiz from starting

Status in xorg package in Ubuntu:
  Expired

Bug description:
  After enabling proprietary driver nvidia 361.42 in unity-control-
  center and rebooting, compiz fails to start.  I'm able to login.  I
  see my wallpaper and desktop icons, but there's no window manager or
  panel.

  A manual fix that worked in the past was
  right-click, open terminal
  enter commands:
  dconf reset -f /org/compiz/
  setsid unity

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-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
  CurrentDesktop: Unity
  Date: Wed Jun  8 09:06:57 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-22-generic, x86_64: installed
   nvidia-361, 361.42, 4.4.0-22-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 
00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd Skylake Integrated Graphics 
[144d:c12b]
 Subsystem: Samsung Electronics Co Ltd GM107M [GeForce GTX 950M] [144d:c12b]
  InstallationDate: Installed on 2015-12-22 (168 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 940Z5L
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed 
root=UUID=24c27814-5135-4a80-9ce1-b932e2513949 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/11/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P06AFC.091.160311.SH
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP940Z5L-X01US
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGL8554A1H-C01-G001-S0001+10.0.10240
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP06AFC.091.160311.SH:bd03/11/2016:svnSAMSUNGELECTRONICSCO.,LTD.:pn940Z5L:pvrP06AFC:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP940Z5L-X01US:rvrSGL8554A1H-C01-G001-S0001+10.0.10240:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
  dmi.product.name: 940Z5L
  dmi.product.version: P06AFC
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  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: Wed Jun  8 09:04:53 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   16714 
   vendor SDC
  xserver.version: 2:1.18.3-1ubuntu2.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1590457/+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 1581745] Re: 3rd monitor can't display full-resolution with amdgpu and R9 380

[Launchpad Bug Tracker]

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

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

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

Title:
  3rd monitor can't display full-resolution with amdgpu and R9 380

Status in xorg package in Ubuntu:
  Expired

Bug description:
  I have an AMD R9 380. This card under Windows displays full resolution
  (1920x1200x60) all 3 of my monitors perfectly. The connection setup is
  2 x DVI, 1 Display Port with an active adaptor convered to DVI.

  Using AMDGPU, the 3rd monitor is properly detected, it's resolution is
  detected and the card attempts to drive it, but the monitor cannot
  sync the display signal and flickers endlessly trying to do so.

  Dropping the 3rd monitor resolution to 1650x1080x60 displays an image,
  but obviously not at full resolution.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Sat May 14 15:51:03 2016
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1581745/+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 1584238] Re: RADEON(G0): [XvMC] Failed to initialize extension. AND CRTC 64

[Launchpad Bug Tracker]

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

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

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

Title:
  RADEON(G0): [XvMC] Failed to initialize extension. AND CRTC 64

Status in xorg package in Ubuntu:
  Expired

Bug description:
  **UPDATED AS REQUESTED**

  7/02: The display setting commands are to change the display
  orientation (I want to rotate the display 90' clockwise). Two
  displays, on the same graphics card, the primary card as listed in the
  BIOS, will respond to those commands. However, the displays on the
  secondary card will not respond. And if I try to select those displays
  the system crashes or is unable to make the change.

  I have had consistent issues in both 14.04 (even with FGLRX installed)
  and 16.04 with the graphics card labeled as secondary in the BIOS
  correctly displaying or even responding to display setting commands in
  Unity.

  LSPCI Info
  00:00.0 Host bridge: Intel Corporation 4th Gen Core Processor DRAM Controller 
(rev 06)
  00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor 
PCI Express x16 Controller (rev 06)
  00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen 
Core Processor Integrated Graphics Controller (rev 06)
  00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core 
Processor HD Audio Controller (rev 06)
  00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family 
USB xHCI (rev 04)
  00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series 
Chipset Family MEI Controller #1 (rev 04)
  00:16.3 Serial controller: Intel Corporation 8 Series/C220 Series Chipset 
Family KT Controller (rev 04)
  00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I217-LM 
(rev 04)
  00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family 
USB EHCI #2 (rev 04)
  00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High 
Definition Audio Controller (rev 04)
  00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI 
Express Root Port #1 (rev d4)
  00:1c.4 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI 
Express Root Port #5 (rev d4)
  00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family 
USB EHCI #1 (rev 04)
  00:1f.0 ISA bridge: Intel Corporation Q87 Express LPC Controller (rev 04)
  00:1f.2 SATA controller: Intel Corporation 8 Series/C220 Series Chipset 
Family 6-port SATA Controller 1 [AHCI mode] (rev 04)
  00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family SMBus 
Controller (rev 04)
  01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Caicos XTX [Radeon HD 8490 / R5 235X OEM]
  01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Caicos HDMI 
Audio [Radeon HD 6400 Series]
  03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Caicos XTX [Radeon HD 8490 / R5 235X OEM]
  03:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Caicos HDMI 
Audio [Radeon HD 6400 Series]

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri May 20 18:22:07 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  InstallationDate: Installed on 2016-05-05 (15 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. OptiPlex 9020
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=baa78b6c-e47e-4119-af45-1c2ee756768a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/05/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0XCR8D
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A03
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd12/05/2013:svnDellInc.:pnOptiPlex9020:pvr01:rvnDellInc.:rn0XCR8D:rvrA03:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex 9020
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  

[Touch-packages] [Bug 1585094] Re: Random stuck keys on Lenovo Yoga 13

[Launchpad Bug Tracker]

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

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

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

Title:
  Random stuck keys on Lenovo Yoga 13

Status in xorg package in Ubuntu:
  Expired

Bug description:
  pressing arrow keys leads randomly to the effect of stuck number key
  and produces output in consoles or text editors like: "22" or
  "88". Pressing some other key stops the infinite flooding.

  This may (or not) be related to the following flooding in
  /var/log/system

  May 24 10:01:30 yogi kernel: [ 3816.438579] atkbd serio0: Unknown key pressed 
(translated set 2, code 0xbe on isa0060/serio0).
  May 24 10:01:30 yogi kernel: [ 3816.438603] atkbd serio0: Use 'setkeycodes 
e03e ' to make it known.
  May 24 10:01:30 yogi kernel: [ 3816.443504] atkbd serio0: Unknown key 
released (translated set 2, code 0xbe on isa0060/serio0).
  May 24 10:01:30 yogi kernel: [ 3816.443516] atkbd serio0: Use 'setkeycodes 
e03e ' to make it known.

  
  these messages are generated approximately each 200 msec. If the former is 
not related to stuck key problem, please, ignore.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue May 24 09:45:39 2016
  DistUpgraded: 2016-04-24 00:21:19,103 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:3977]
  InstallationDate: Installed on 2013-11-17 (918 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: LENOVO 2191
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed 
root=UUID=f6200601-c430-459d-abab-c6d45f1e147a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-04-23 (30 days ago)
  dmi.bios.date: 02/28/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 66CN55WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193WIN8 STD MLT
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Yoga 13
  dmi.modalias: 
dmi:bvnLENOVO:bvr66CN55WW:bd02/28/2013:svnLENOVO:pn2191:pvrLenovoIdeaPadYoga13:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadYoga13:
  dmi.product.name: 2191
  dmi.product.version: Lenovo IdeaPad Yoga 13
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  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: Tue May 24 08:57:44 2016
  xserver.configfile: default
  xserver.errors: SynPS/2 Synaptics TouchPad: Read error 19
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 864 
   vendor LGD
  xserver.version: 2:1.18.3-1ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1585094/+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 1592519] Re: [radeon] sumo2 locks up and fails to train displayport during boot (panel turns off)

[Launchpad Bug Tracker]

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

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

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

Title:
  [radeon] sumo2 locks up and fails to train displayport during boot
  (panel turns off)

Status in xorg package in Ubuntu:
  Expired

Bug description:
  Problem: Laptop panel turns off during boot, which makes the laptop
  unusable.

  Expected Results: Laptop panel is ON when I boot without "nomodeset",
  and I can use graphical UI.

  Guys from #radeon channel on "irc.freenode.net" said:
   radeon :00:01.0 is the sumo2 and it locks up
   radeon :01:00.0 is the caicos but there seems to be no problem 
with it
   the problem is the sumo crashing and failing to train displayport
   as it's the travis bridge it's trying to modeset which is the panel
   fixing the travis bridge is the first problem

  I also tried the latest (v4.7-rc3) manually installed kernel,
  confirmed that the bug remains, and submitted the bug here
  https://bugs.freedesktop.org/show_bug.cgi?id=96527 .

  WORKAORUND: Use kernel parameter nomodeset when booting. UI works with
  this kernel parameter but it's not usable as it's very slow.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Tue Jun 14 21:33:48 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Sumo [Radeon HD 6380G] [1002:9643] 
(prog-if 00 [VGA controller])
     Subsystem: Hewlett-Packard Company Sumo [Radeon HD 6380G] [103c:168c]
   Advanced Micro Devices, Inc. [AMD/ATI] Seymour [Radeon HD 6400M/7400M 
Series] [1002:6760] (rev ff) (prog-if ff)
  InstallationDate: Installed on 2016-06-12 (2 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Hewlett-Packard HP ProBook 4535s
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic 
root=UUID=74aa7181-639e-464e-b1e1-2af72c4b6e35 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/11/2015
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68CPC Ver. F.60
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 168B
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 32.1D
  dmi.chassis.asset.tag: CNU13746LQ
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68CPCVer.F.60:bd03/11/2015:svnHewlett-Packard:pnHPProBook4535s:pvrA402:rvnHewlett-Packard:rn168B:rvrKBCVersion32.1D:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP ProBook 4535s
  dmi.product.version: A402
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  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: Tue Jun 14 21:32:36 2016
  xserver.configfile: default
  xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension.
  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/xorg/+bug/1592519/+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 1606122] Re: Cairo drawing coordinates are broken w/nouveau (affects xfwm4)

[Launchpad Bug Tracker]

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

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

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

Title:
  Cairo drawing coordinates are broken w/nouveau (affects xfwm4)

Status in xorg package in Ubuntu:
  Expired

Bug description:
  I'm using xfwm4 with Xubuntu 16.04.  With compositing enabled, and
  when I cycle through windows with Alt-Tab, xfwm4 draws an opaque
  rectangle bordering a candidate window, and it fills that rectangle
  with a semi-transparent blue color.  When I use the nouveau driver,
  the filled rectangle is clipped.  The problem does not reproduce with
  the proprietary nvidia driver.

  It seems as though a drawing command should be issued using a window-
  relative coordinate, but sometimes is instead issued using a screen-
  relative coordinate.

  I extracted relevant bits of xfwm4 into a small test program that
  reproduces the problem.  The test program creates a transparent
  XWindow at (100,100) with size (210,210).  It draws six rectangles
  centered inside the window of varying parameters.  Two of them are
  drawn at the wrong place.

  xfwm4 should be off-the-hook, I think, unless it's doing something
  wrong (e.g. unspecified/undefined behavior).

  $ lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  $ apt-cache policy xserver-xorg-video-nouveau
  xserver-xorg-video-nouveau:
Installed: 1:1.0.12-1build2
Candidate: 1:1.0.12-1build2
Version table:
   *** 1:1.0.12-1build2 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  $ apt-cache policy xfwm4
  xfwm4:
Installed: 4.12.3-1ubuntu2
Candidate: 4.12.3-1ubuntu2
Version table:
   *** 4.12.3-1ubuntu2 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status

  I created a video demonstrating the problem in xfwm4:
  https://www.youtube.com/watch?v=8dZN80tMA6M.  If you look closely, you
  can see that the opaque blue border is positioned correctly, while the
  semi-transparent overlay isn't.

  FWIW, I'm using an NVIDIA GeForce GTX 750 Ti card.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon Jul 25 00:50:21 2016
  InstallationDate: Installed on 2016-07-19 (6 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1606122/+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 1607966] Re: X doesn't start with r128 driver with PM 3, 1 PPC ATI Rage

[Launchpad Bug Tracker]

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

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

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

Title:
  X doesn't start with r128 driver with PM 3,1 PPC ATI Rage

Status in xorg package in Ubuntu:
  Expired

Bug description:
  I was working on bug #1541082 which was reporting "blotchy" graphics
  images on my PowerMac3,1 with Rage ATI Pro 128 card . . . and got the
  suggestion to try to add the "r128" driver, which I did.  After that
  the display went black.  After fiddling around with it, I removed the
  r128 driver, made an xorg.conf file . . . and after numerous attempts
  to get the display back, today I got "fbdev" and mode "1920 x 1200" to
  bring the GUI back online . . . but, there was another "xorg" crash on
  reboot, which I reported, along with filing this bug against the r128
  module for this PPC machine.

  F

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-31.50-powerpc-smp 4.4.13
  Uname: Linux 4.4.0-31-powerpc-smp ppc
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: powerpc
  BootLog:
   fsck from util-linux 2.27.1
   /dev/sda13: clean, 182266/1458176 files, 1099215/5826607 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: MATE
  Date: Fri Jul 29 14:34:22 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Rage 128 PRO AGP 4x TMDS 
[1002:5046] (prog-if 00 [VGA controller])
  InstallationDate: Installed on 2016-01-31 (179 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha powerpc 
(20160123)
  Lsusb:
   Bus 002 Device 004: ID 047d:1029 Kensington Mouse*in*a*Box Optical Elite
   Bus 002 Device 003: ID 05ac:0201 Apple, Inc. USB Keyboard [Alps or Logitech, 
M2452]
   Bus 002 Device 002: ID 05ac:1001 Apple, Inc. Keyboard Hub [ALPS]
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  ProcKernelCmdLine: root=UUID=4eb514e5-48d7-4e99-a402-5294c80e78cc ro quiet 
splash
  Renderer: Software
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  version.compiz: compiz 1:0.9.12.2+16.04.20160714-0ubuntu1
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  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 N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Fri Jul 29 14:15:13 2016
  xserver.configfile: /etc/X11/xorg.conf
  xserver.devices:
   inputAlps Electric Apple USB Keyboard KEYBOARD, id 6
   inputKensington  USB/PS2 Wheel Mouse MOUSE, id 7
   inputPMU  KEYBOARD, id 8
  xserver.errors: AIGLX: reverting to software rendering
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.3-1ubuntu2.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1607966/+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 1639203] Re: mouse cursor flashing on laptop screen after adding second monitor through usb 3.0 displaylink monitor

[Launchpad Bug Tracker]

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

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

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

Title:
  mouse cursor flashing on laptop screen after adding second monitor
  through usb 3.0 displaylink monitor

Status in xorg package in Ubuntu:
  Expired

Bug description:
  Mouse cursor flashes when moved on the laptop screen after connecting
  a second monitor via DisplayLink USB 3.0 interface. The cursor flashes
  both when connecting the screen via VGA and HDMI.

  However, when the screen is connected directly to the VGA or HDMI
  ports on laptop, bypassing the DisplayLink adapter, the flashing does
  not occur. Similarly, the cursor never flashes on the second screen.

  The system is Ubuntu 16.04 LTS on Dell Latitude E5470 with integrated
  Intel graphic card.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Nov  4 11:40:32 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 
00 [VGA controller])
     Subsystem: Dell Skylake Integrated Graphics [1028:06de]
  InstallationDate: Installed on 2016-08-22 (74 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. Latitude E5470
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic 
root=UUID=6b6cd5e0-5e92-462d-b229-6e50476e309d ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/15/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.3
  dmi.board.name: 0C8FKJ
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.3:bd06/15/2016:svnDellInc.:pnLatitudeE5470:pvr:rvnDellInc.:rn0C8FKJ:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E5470
  dmi.sys.vendor: Dell Inc.
  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.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: Fri Nov  4 11:38:14 2016
  xserver.configfile: default
  xserver.errors: modeset(G0): glamor initialization failed
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   61460
   vendor DEL
  xserver.version: 2:1.18.3-1ubuntu2.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1639203/+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 1623339] Re: The system is running in low-graphics mode (Ubuntu 16.04, ARM64 platform, AST2400 VGA chip)

[Launchpad Bug Tracker]

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

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

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

Title:
  The system is running in low-graphics mode  (Ubuntu 16.04, ARM64
  platform, AST2400 VGA chip)

Status in xorg package in Ubuntu:
  Expired

Bug description:
  I use netboot to install Ubuntu 16.04 in Cavium ThunderX 8800 platform
  (ARM64 core) with AST2400 VGA chip and I see "The system is running in
  low graphics mode". How can I fix this issue?

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic aarch64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: arm64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Wed Sep 14 14:02:23 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   ASPEED Technology, Inc. ASPEED Graphics Family [1a03:2000] (rev 30) (prog-if 
00 [VGA controller])
 Subsystem: ASPEED Technology, Inc. ASPEED Graphics Family [1a03:2000]
  MachineType: Cavium ThunderX CRB
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic 
root=UUID=513a25ac-9bd5-49b5-a6cb-4298036c6abd ro splash quiet vt.handoff=7
  Renderer: Software
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.11
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: To be filled by O.E.M.
  dmi.board.vendor: To be filled by O.E.M.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 0
  dmi.chassis.vendor: Cavium
  dmi.chassis.version: To be filled by O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd12/12/2012:svnCavium:pnThunderXCRB:pvrTobefilledbyO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnCavium:ct0:cvrTobefilledbyO.E.M.:
  dmi.product.name: ThunderX CRB
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Cavium
  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.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.1
  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 N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Thu Sep  8 09:56:09 2016
  xserver.configfile: default
  xserver.devices:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.3-1ubuntu2.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1623339/+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 1639582] Re: Problems with nvidia (xorg automatic diagnosis data)

[Launchpad Bug Tracker]

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

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

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

Title:
  Problems with nvidia (xorg automatic diagnosis data)

Status in xorg package in Ubuntu:
  Expired

Bug description:
  Error messages on boot.

  Today couldn't log in.

  Re-installed drivers for nvidia manually.
  Then blank desktop.
  Now changed from unity to gnome.

  Works ok, but error messages on boot persist.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic i686
  NonfreeKernelModules: nvidia_uvm nvidia
  .proc.driver.nvidia.gpus..03.00.0: Error: [Errno 21] Ist ein Verzeichnis: 
'/proc/driver/nvidia/gpus/:03:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86 Kernel Module  340.98  Mon Sep 19 16:44:35 PDT 
2016
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.2)
  .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: None
  Date: Sun Nov  6 15:29:39 2016
  DistUpgraded: 2016-07-30 20:41:40,733 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-31-generic, i686: installed
   nvidia-340, 340.98, 4.4.0-31-generic, i686: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation C79 [GeForce 9100M G] [10de:086e] (rev b1) (prog-if 00 
[VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] C79 [GeForce 9100M G] 
[1462:7621]
  InstallationDate: Installed on 2015-05-01 (554 days ago)
  InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release i386 
(20140807.1)
  MachineType: MEDIONPC MS-7621
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic 
root=UUID=74d7770e-5d40-4ec0-8e44-64c36a2d8164 ro splash quiet
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-07-30 (98 days ago)
  dmi.bios.date: 03/09/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A7621MLN.207
  dmi.board.name: MS-7621
  dmi.board.vendor: MEDIONPC
  dmi.board.version: 2.1
  dmi.chassis.type: 3
  dmi.chassis.vendor: MEDIONPC
  dmi.chassis.version: 2.1
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA7621MLN.207:bd03/09/2010:svnMEDIONPC:pnMS-7621:pvr2.1:rvnMEDIONPC:rnMS-7621:rvr2.1:cvnMEDIONPC:ct3:cvr2.1:
  dmi.product.name: MS-7621
  dmi.product.version: 2.1
  dmi.sys.vendor: MEDIONPC
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.1
  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: Sun Nov  6 15:26:53 2016
  xserver.configfile: default
  xserver.errors: open /dev/fb0: No such file or directory
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.4-0ubuntu0.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1639582/+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 1657903] Re: XRandR failed: XRandR returned error code 1: X Error of failed request: BadValue (integer parameter out of range for operation)

[Launchpad Bug Tracker]

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

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

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

Title:
  XRandR failed: XRandR returned error code 1: X Error of failed
  request: BadValue (integer parameter out of range for operation)

Status in xorg package in Ubuntu:
  Expired

Bug description:
  What happens when using a StarTech device (Product ID: USB3SDOCKDD)
  with either the DisplayLink driver from StarTech's website (1.1.62),
  or the latest from DisplayLink's website (1.2.65), is when I attach
  the USB 3.0 cord to the USB 3.0 port on my laptop for the first time
  after a reboot, open arandr, open the attached StarTech.sh file, and
  click Apply, the Dell E2414Ht monitor VGA connected on the left is the
  primary and the laptop display is the secondary on the right.

  However, if I disconnect the USB cord, then reconnect, and then re-apply the 
file, I get a pop up noting:
  
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1657903/+attachment/4806499/+files/screenshot.png

  XRandR failed: XRandR returned error code 1: X Error of failed request:
  BadValue (integer parameter out of range for operation)
   Major opcode of failed request: 140 (RANDR)
   Minor opcode of failed request: 7 (RRSetScreenSize)
   Value in failed request: 0x0
   Serial number of failed request: 42
   Current serial number in output stream: 43

  The two DisplayLink driver versions tested:
  sudo displaylink-installer
  DisplayLink Linux Software 1.1.62 install script called:
  Distribution discovered: Ubuntu 16.04.1 LTS

  sudo displaylink-installer
  DisplayLink Linux Software 1.2.65 install script called:
  Distribution discovered: Ubuntu 16.04.1 LTS

  WORKAROUND: Restart the computer after disconnecting the USB cord.

  WORKAROUND: Go to Applications > System Tools > System Settings >
  Displays and make only the Dell monitor as On > click Apply > then
  make the Built-in Display On > click Apply. This is the only way to
  make the Dell monitor the primary, and the laptop the secondary as
  there are no general options, and the app makes the Built-in Display
  the primary by default, with no General options to change this.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  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.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Thu Jan 19 16:17:34 2017
  DistUpgraded: 2016-01-20 03:32:27,395 DEBUG enabling apt cron job
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: Toshiba America Info Systems 4th Gen Core Processor Integrated 
Graphics Controller [1179:f840]
  InstallationDate: Installed on 2015-12-18 (398 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: TOSHIBA Satellite S55-C
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-59-generic 
root=/dev/mapper/ubuntu--vg-root ro ipv6.disable=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-01-20 (365 days ago)
  dmi.bios.date: 10/14/2015
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 5.10
  dmi.board.name: 06F1
  dmi.board.vendor: FF50
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis ManuFacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr5.10:bd10/14/2015:svnTOSHIBA:pnSatelliteS55-C:pvrPSPTJU-006005:rvnFF50:rn06F1:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite S55-C
  dmi.product.version: PSPTJU-006005
  dmi.sys.vendor: TOSHIBA
  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.2
  

[Touch-packages] [Bug 1644063] Re: nouveau locking up glslideshow after some time

[Launchpad Bug Tracker]

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

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

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

Title:
  nouveau locking up glslideshow after some time

Status in xorg package in Ubuntu:
  Expired

Bug description:
  XFCE4 / desktop becomes unresponsive (no mouse or keyboard) after running 
glslideshow for some time.
  The time range is unknown.
  Happening 100% of every session.
  The screensaver is NOT set to power off.
  Litelocker not being used.
  Video card temperature is low.
  I can ssh into locked up system.
  dmesg reports nouveau fatal error.
  xdiagnose is installed

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Tue Nov 22 21:15:10 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation G71 [GeForce 7900 GS] [10de:0292] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: NVIDIA Corporation G71 [GeForce 7900 GS] [10de:0370]
  InstallationDate: Installed on 2016-11-05 (17 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic 
root=UUID=9b509dd9-28f8-42d9-bd9f-c2fa7eb33811 ro vebose=1 drm.debug=0xe 
plymouth:debug
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/09/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0605
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: A8R-MVP
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0605:bd12/09/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnA8R-MVP:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  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: Tue Nov 22 21:09:03 2016
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputAT Translated Set 2 keyboard KEYBOARD, id 8
   inputImExPS/2 Logitech Wheel Mouse MOUSE, id 9
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.2
  xserver.video_driver: nouveau

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1644063/+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 1662042] Re: Black screen after resuming from sleep with nvidia drivers on 16.04

[Launchpad Bug Tracker]

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

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

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

Title:
  Black screen after resuming from sleep with nvidia drivers on 16.04

Status in xorg package in Ubuntu:
  Expired

Bug description:
  This happens on an ASUS ZenBook UX303UB, with nvidia-375 installed.
  I'm able to connect to the host through SSH. I have run the apport-bug tool 
when the display was black.

  The problem is not present when I switch back to using the Intel GPU
  using Nvidia's tool (through nvidia-prime).

  So far, I have done the following tests, following reports from other users:
  - Switched to kernel 4.8
  - Tried with both nvidia-370 and nvidia-375
  - Tried with fix to backlight 
(http://askubuntu.com/questions/820955/blank-screen-after-resume-dell-m5510-ubuntu-16-04/823523)
  - Configured ligthdm idle-timeout to 3 seconds and see if the display came 
back  (due to an old bug affecting older versions)

  Bumblebee is not installed.

  I have seen several issues / questions that seems similar to this one,
  but I couldn't find a solution / workaround, other than disabling
  Nvidia's GPU.

  I appreciate any help to debug this.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-34.36~16.04.1-generic 4.8.11
  Uname: Linux 4.8.0-34-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  375.26  Thu Dec  8 18:36:43 
PST 2016
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4)
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Sun Feb  5 22:16:19 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-62-generic, x86_64: installed
   bbswitch, 0.8, 4.8.0-34-generic, x86_64: installed
   nvidia-375, 375.26, 4.8.0-34-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Skylake Integrated Graphics [1043:1b1d]
 Subsystem: ASUSTeK Computer Inc. GM108M [GeForce 940M] [1043:1b1d]
  InstallationDate: Installed on 2016-08-18 (172 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 005: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 03eb:8b0d Atmel Corp. 
   Bus 001 Device 002: ID 04f2:b56b Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX303UB
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-34-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash acpi_backlight=none acpi_osi= 
vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/02/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX303UB.206
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX303UB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX303UB.206:bd03/02/2016:svnASUSTeKCOMPUTERINC.:pnUX303UB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303UB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX303UB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  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.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  

[Touch-packages] [Bug 1665629] Re: external HDMI doesnt function properly

[Launchpad Bug Tracker]

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

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

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

Title:
  external HDMI doesnt function properly

Status in xorg package in Ubuntu:
  Expired

Bug description:
  New clean install of 16.04 on dell Inspiron N5110 laptop,when External HDMI 
Monitor plugged in
   display randomly switches from laptop screen to hdmi screen ,
   changing resolution, 
  changing display mode,
  display positioning,
  whether the internal or external display is enabled or not, 
  and other things all display settings related, ie size of iconts, font and 
title bars.
  All this happens AUTOMATICALLY and without notice.
  This does not stop, it makes it look like the computer is Haunted.
   How do I fix this???

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1665629/+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 1666771] Re: Nvidia 378.13 (Patched) + Kernel 4.10(RC8)

[Launchpad Bug Tracker]

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

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

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

Title:
  Nvidia 378.13 (Patched) + Kernel 4.10(RC8)

Status in xorg package in Ubuntu:
  Expired

Bug description:
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
  [   243.735] (WW) `fonts.dir' not found (or not valid) in 
"/usr/share/fonts/X11/cyrillic".
  [   243.735] (WW) `fonts.dir' not found (or not valid) in 
"/usr/share/fonts/X11/100dpi/".
  [   243.735] (WW) `fonts.dir' not found (or not valid) in 
"/usr/share/fonts/X11/75dpi/".
  [   243.735] (WW) `fonts.dir' not found (or not valid) in 
"/usr/share/fonts/X11/100dpi".
  [   243.735] (WW) `fonts.dir' not found (or not valid) in 
"/usr/share/fonts/X11/75dpi".
  [   243.735] (WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' or 
'vmmouse' will be disabled.
  [   243.735] (WW) Disabling Keyboard0
  [   243.735] (WW) Disabling Mouse0
  [   243.834] (WW) xf86OpenConsole: setpgid failed: Operation not permitted
  [   243.834] (WW) xf86OpenConsole: setsid failed: Operation not permitted
  [   243.995] (WW) Falling back to old probe method for fbdev
  [   243.996] (WW) Falling back to old probe method for vesa
  [   243.997] (WW) Warning, couldn't open module glamoregl
  [   244.578] (WW) evdev: E-Signal/A-One USB Gaming Mouse: ignoring absolute 
axes.


  01:00.0 VGA compatible controller [0300]: NVIDIA Corporation Device 
[10de:1c03] (rev a1) (prog-if 00 [VGA controller])
Flags: bus master, fast devsel, latency 0, IRQ 50
Memory at fd00 (32-bit, non-prefetchable) [size=16M]
Memory at c000 (64-bit, prefetchable) [size=256M]
Memory at d000 (64-bit, prefetchable) [size=32M]
I/O ports at e000 [size=128]
Expansion ROM at 000c [disabled] [size=128K]
Capabilities: [60] Power Management version 3
Capabilities: [68] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [78] Express Legacy Endpoint, MSI 00
Capabilities: [100] Virtual Channel
Capabilities: [250] Latency Tolerance Reporting
Capabilities: [128] Power Budgeting 
Capabilities: [420] Advanced Error Reporting
Capabilities: [600] Vendor Specific Information: ID=0001 Rev=1 Len=024 

Capabilities: [900] #19
Kernel driver in use: nouveau
Kernel modules: nvidiafb, nouveau, nvidia_drm, nvidia

  
  name of display: :0
  Xlib:  extension "GLX" missing on display ":0".
  Xlib:  extension "GLX" missing on display ":0".
  Xlib:  extension "GLX" missing on display ":0".
  Xlib:  extension "GLX" missing on display ":0".
  Xlib:  extension "GLX" missing on display ":0".
  Xlib:  extension "GLX" missing on display ":0".
  Xlib:  extension "GLX" missing on display ":0".
  Error: couldn't find RGB GLX visual or fbconfig
  Xlib:  extension "GLX" missing on display ":0".
  Xlib:  extension "GLX" missing on display ":0".

  Xlib:  extension "GLX" missing on display ":0".
  Xlib:  extension "GLX" missing on display ":0".
  Xlib:  extension "GLX" missing on display ":0".
  Xlib:  extension "GLX" missing on display ":0".
  Xlib:  extension "GLX" missing on display ":0".
  Xlib:  extension "GLX" missing on display ":0".
  Xlib:  extension "GLX" missing on display ":0".
  Xlib:  extension "GLX" missing on display ":0".
  marc@Drthrax-Fixe:~$ glxgears 
  Xlib:  extension "GLX" missing on display ":0".
  Error: couldn't get an RGB, Double-buffered visual

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  Uname: Linux 4.10.0-041000rc8-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Wed Feb 22 07:02:00 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 378.13, 4.10.0-041000rc8-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard: NVIDIA Corporation Device [10de:1c03] (rev a1) (prog-if 00 [VGA 
controller])
  InstallationDate: Installed on 2017-02-21 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  ProcEnviron:
   LANGUAGE=fr_FR
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-041000rc8-generic 
root=UUID=af0ea833-acc7-4f5d-89b5-646908b7ed3a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UnitySupportTest: Error: command ['/usr/lib/nux/unity_support_test', '-p', 
'-f'] failed with exit code 5: Error: GLX is not available on the system
  UpgradeStatus: No upgrade 

[Touch-packages] [Bug 1670216] Re: Cannot load radeon drivers

[Launchpad Bug Tracker]

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

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

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

Title:
  Cannot load radeon drivers

Status in xorg package in Ubuntu:
  Expired

Bug description:
  lsb_release -rd
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

  apt-cache policy xorg
  xorg:
Instalado: 1:7.7+13ubuntu3
Candidato: 1:7.7+13ubuntu3
Tabela de Versão:
   *** 1:7.7+13ubuntu3 500
  500 http://pt.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  The following error occurs at genymotion start
  libGL error: unable to load driver: radeonsi_dri.so
  libGL error: driver pointer missing
  libGL error: failed to load driver: radeonsi
  libGL error: unable to load driver: swrast_dri.so
  libGL error: failed to load driver: swrast

  it occurs to in android AVD emulator before applying the following 
workaround, a bit different now since the folders names changed:
  cd $ANDROID_HOME/android-sdk-linux_x86/tools/lib64/libstdc++
  $ mv libstdc++.so.6 libstdc++.so.6.bak
  $ ln -s /usr/lib64/libstdc++.so.6 
$ANDROID_HOME/android-sdk-linux_x86/tools/lib64/libstdc++
  seen in here 
http://stackoverflow.com/questions/36554322/cannot-start-emulator-in-android-studio-2-0

  It seems to be something about hardware acceleration since if it is
  disabled in android AVD emulator the emulator work fine. If is started
  from the command line with the option -use-system-lib: emulator -use-
  system-libs -avd YOUR_VIRTUAL_DEVICE_NAME it work too.

  A process to replicate the bug is install Ubuntu 16.04.1 LTS, then
  virtualbox with apt and then install genymotion-2.8.1_x64.bin, at
  least it was that I used. This way the emulator works. After this if
  you update the Ubuntu with sudo apt update | sudo apt upgrade the
  error appears.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  Uname: Linux 4.4.0-64-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sun Mar  5 23:29:14 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.0.32, 4.4.0-64-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Kabini [Radeon HD 8330] [1002:9832] 
(prog-if 00 [VGA controller])
 Subsystem: Toshiba America Info Systems Kabini [Radeon HD 8330] [1179:fa34]
  InstallationDate: Installed on 2017-03-05 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: TOSHIBA SATELLITE C50D-A-110
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic.efi.signed 
root=UUID=e9ba2d60-3ce1-4aab-aa2c-62d55f0ad0ad ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/21/2014
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 1.30
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: PT10AN
  dmi.board.vendor: AMD
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr1.30:bd05/21/2014:svnTOSHIBA:pnSATELLITEC50D-A-110:pvrPSCH2E-00700GEP:rvnAMD:rnPT10AN:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: SATELLITE C50D-A-110
  dmi.product.version: PSCH2E-00700GEP
  dmi.sys.vendor: TOSHIBA
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  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.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sun Mar  5 23:27:21 2017
  xserver.configfile: default
  xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  

[Touch-packages] [Bug 1685727] Re: Poor performance with displaylink

[Launchpad Bug Tracker]

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

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

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

Title:
  Poor performance with displaylink

Status in xorg package in Ubuntu:
  Expired

Bug description:
  When driving monitors via a displaylink usb3 hub performance drops to
  an unacceptable level. The cursor blinks and I'm unable to reconfigure
  the screens in "Screen Display" as it errors.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-46.49~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-46-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  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
  CurrentDesktop: Unity
  Date: Mon Apr 24 08:20:59 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0740]
  InstallationDate: Installed on 2017-04-20 (3 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: Dell Inc. Inspiron 13-5378
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-46-generic.efi.signed 
root=UUID=57d61b9e-75ba-4fa1-a744-b38b4da80f4e ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/13/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.1
  dmi.board.name: 0YNG98
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.1:bd02/13/2017:svnDellInc.:pnInspiron13-5378:pvr:rvnDellInc.:rn0YNG98:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 13-5378
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1685727/+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 1685775] Re: Can't use VGA

[Launchpad Bug Tracker]

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

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

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

Title:
  Can't use VGA

Status in xorg package in Ubuntu:
  Expired

Bug description:
  Hi,

  when i connect an external screen, throught VGA , my laptop (DELL
  Latitude E6410 ) doesn't detect it.

  typing  xrandr -q  in terminal give me :

  xrandr: Failed to get size of gamma for output default
  Screen 0: minimum 1280 x 800, current 1280 x 800, maximum 1280 x 800
  default connected primary 1280x800+0+0 0mm x 0mm
 1280x800  76.00* 

  thanks for your help

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  Uname: Linux 4.9.0-040900-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Apr 24 12:07:49 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   i915-4.6.3-4.4.0, 1, 4.4.0-71-generic, x86_64: installed
   i915-4.6.3-4.4.0, 1, 4.4.0-72-generic, x86_64: installed
   virtualbox, 5.0.36, 4.4.0-72-generic, x86_64: installed
   virtualbox, 5.0.36, 4.9.0-040900-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Dell Latitude E6410 [1028:040a]
  InstallationDate: Installed on 2016-06-26 (302 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Latitude E6410
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.9.0-040900-generic 
root=/dev/mapper/ubuntu--vg-root ro nomodeset
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgConf:
   Section "Device"
   Identifier "My device"
   Driver "intel"
   EndSection
  dmi.bios.date: 08/10/2010
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.asset.tag: 111737
  dmi.board.name: 0667CC
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A03
  dmi.chassis.asset.tag: 111737
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd08/10/2010:svnDellInc.:pnLatitudeE6410:pvr0001:rvnDellInc.:rn0667CC:rvrA03:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6410
  dmi.product.version: 0001
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  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.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Mon Apr 24 11:31:32 2017
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   No devices detected.
   open /dev/dri/card0: No such file or directory
   open /dev/dri/card0: No such file or directory
   Screen 0 deleted because of no matching config section.
   AIGLX: reverting to software rendering
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.4-0ubuntu0.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1685775/+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 1693139] Re: Installing graphic driver does not working

[Launchpad Bug Tracker]

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

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

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

Title:
  Installing graphic driver does not working

Status in xorg package in Ubuntu:
  Expired

Bug description:
  Installing graphic driver does not working. I have tried several ways
  to fix the issue. But found there is a bug. Because of the driver is
  missing, OS not detecting the monitor and not detecting resolution.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.6
  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: Wed May 24 14:21:20 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-78-generic, x86_64: installed
   i915-4.6.3-4.4.0, 1, 4.4.0-75-generic, x86_64: installed
   i915-4.6.3-4.4.0, 1, 4.4.0-77-generic, x86_64: installed
   i915-4.6.3-4.4.0, 1, 4.4.0-78-generic, x86_64: installed
   nvidia-381, 381.22, 4.4.0-78-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0152] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor 
Graphics Controller [8086:2031]
  InstallationDate: Installed on 2017-05-02 (22 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic 
root=UUID=d9f20750-d784-4a20-9d08-15c4595d71c1 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/23/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: KCH7710H.86A.0104.2012.1123.1027
  dmi.board.name: DH77KC
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG39641-401
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrKCH7710H.86A.0104.2012.1123.1027:bd11/23/2012:svn:pn:pvr:rvnIntelCorporation:rnDH77KC:rvrAAG39641-401:cvn:ct3:cvr:
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  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.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Wed May 24 10:02:06 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.4-0ubuntu0.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1693139/+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 1694017] Re: nvidia driver installation causing X.org to freeze

[Launchpad Bug Tracker]

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

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

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

Title:
  nvidia driver installation causing X.org to freeze

Status in xorg package in Ubuntu:
  Expired

Bug description:
  Hi,
  Please let me know if you need any other info than the attached information.
  Thanks
  Br
  aksgaur

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  Uname: Linux 4.8.0-36-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  375.39  Tue Jan 31 20:47:00 
PST 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sat May 27 14:01:19 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:050e]
   NVIDIA Corporation GF108M [GeForce GT 540M] [10de:0df4] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Dell GF108M [GeForce GT 540M] [1028:050e]
  InstallationDate: Installed on 2017-05-01 (26 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: Dell Inc. Dell System XPS L502X
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-36-generic 
root=UUID=e35ef27e-882a-4ccf-9430-7246671359cb ro rootflags=subvol=@ quiet 
splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/07/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 0NJT03
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd09/07/2012:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0NJT03:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Dell System XPS L502X
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1694017/+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 1694109] Re: X server freezes with all NVIDIA open source driver releases (340.102, 375.66, 381.22)

[Launchpad Bug Tracker]

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

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

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

Title:
  X server freezes with all NVIDIA open source driver releases (340.102,
  375.66, 381.22)

Status in xorg package in Ubuntu:
  Expired

Bug description:
  Hello,

  I have Dell XPX L502X with Nvidia GT 540M card i.e. 6 years old
  hardware whose driver is still not working, this is amazing :(

  The X server freezes with all NVIDIA open source driver releases
  (340.102, 375.66, 381.22). This report is for NVIDIA driver version
  340.102.

  X Server freezes at any time keyboard and mouse hangs and last resort
  used to be to power down with power key forcefully which may destroy
  HDD also :(

  I even tried proprietary NVIDIA drivers also but they had shown the
  same behaviour.

  Without the NVIDIA drivers in place I can't use CUDA toolkit.

  Please let me know if someone need any further info apart from attached file.
  Thanks

  Br
  aksgaur

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  Uname: Linux 4.8.0-36-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.102  Mon Jan 16 13:06:29 
PST 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sun May 28 11:42:45 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.8.0-36-generic, x86_64: installed
   bbswitch, 0.8, 4.8.0-53-generic, x86_64: installed
   nvidia-340, 340.102, 4.8.0-36-generic, x86_64: installed
   nvidia-340, 340.102, 4.8.0-53-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:050e]
   NVIDIA Corporation GF108M [GeForce GT 540M] [10de:0df4] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Dell GF108M [GeForce GT 540M] [1028:050e]
  InstallationDate: Installed on 2017-05-01 (26 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: Dell Inc. Dell System XPS L502X
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-36-generic 
root=UUID=e35ef27e-882a-4ccf-9430-7246671359cb ro rootflags=subvol=@ quiet 
splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/07/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 0NJT03
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd09/07/2012:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0NJT03:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Dell System XPS L502X
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1694109/+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 1694254] Re: Requested size (2944, 1080) exceeds 3D hardware limit

[Launchpad Bug Tracker]

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

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

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

Title:
  Requested size (2944, 1080) exceeds 3D hardware limit

Status in xorg package in Ubuntu:
  Expired

Bug description:
  IBM T60 laptop (1024x768), and an external monitor, Benq E2200HDA
  (1920x1080) connected.

  Displays with expected resolutions only if one above/below the other,
  not left or right.

  Xrandr say:
  Screen 0: minimum 8 x 8, current 1920 x 1848, maximum 32767 x 32767
  LVDS1 connected primary 1024x768+0+0 (normal left inverted right x axis y 
axis) 286mm x 214mm
 1024x768  60.00*+  50.00  
 800x600   60.3256.25  
 640x480   60.0059.94  
 512x384   60.00  
  DVI1 disconnected (normal left inverted right x axis y axis)
  VGA1 connected 1920x1080+0+768 (normal left inverted right x axis y axis) 
476mm x 268mm
 1920x1080 59.96*+
 1680x1050 59.95  
 1280x1024 75.0260.02  
 1440x900  74.9859.89  
 1280x960  60.00  
 1280x800  59.81  
 1152x864  75.00  
 1152x720  59.97  
 1024x768  75.0860.00  
 832x624   74.55  
 800x600   75.0060.32  
 640x480   75.0060.00  
 720x400   70.08  
 1920x1080_60.00  59.96  
  VIRTUAL1 disconnected (normal left inverted right x axis y axis)

  Forcing fitting any screen left/right of the other results in black
  screen with xrandr.

  Trying to fit them left/right with System Settings > Screen Display says:
   
GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._gsd_2drr_2derror_2dquark.Code3: 
Requested size (2944, 1080) exceeds 3D hardware limit (2048, 2048). You must 
either rearrange the displays so that they fit within a (2048, 2048) square.

  System:
  - Ubuntu 16.04.2 LTS 
  - expected to happen: built up screen and VGA1 fits left/right as it works 
with XP.
  - what happenes: see above.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.6
  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
  CurrentDesktop: Unity
  Date: Mon May 29 12:06:57 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics 
Controller [8086:27a2] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Lenovo ThinkPad R60/T60/X60 series [17aa:201a]
 Subsystem: Lenovo ThinkPad R60/T60/X60 series [17aa:201a]
  InstallationDate: Installed on 2017-05-23 (5 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  MachineType: LENOVO 19524TC
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic 
root=UUID=f2865c0e-961d-4c45-8734-4152a94446fa ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/21/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 79ETE7WW (2.27 )
  dmi.board.name: 19524TC
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr79ETE7WW(2.27):bd03/21/2011:svnLENOVO:pn19524TC:pvrThinkPadT60:rvnLENOVO:rn19524TC:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 19524TC
  dmi.product.version: ThinkPad T60
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  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.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Mon May 29 11:24:21 2017
  xserver.configfile: default
  xserver.errors:
   

[Touch-packages] [Bug 1702827] Re: X fails to set DPI correctly

[Launchpad Bug Tracker]

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

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

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

Title:
  X fails to set DPI correctly

Status in xorg package in Ubuntu:
  Expired

Bug description:
  I have the common problem of everything being too small when switching
  to a 4K monitor.  One issue is that X is setting DPI to 96 instead of
  157 for my 28" 4K monitor.

  This is a Radeon RX480 and I've installed xserver-xorg-hwe.  If I run
  get-edid | parse-edid, the correct display dimensions are returned
  (620x340mm).  I see:

  This is read-edid version 3.0.2. Prepare for some fun.
  Attempting to use i2c interface
  No EDID on bus 1
  No EDID on bus 2
  No EDID on bus 3
  No EDID on bus 4
  No EDID on bus 5
  No EDID on bus 6
  No EDID on bus 7
  No EDID on bus 8
  No EDID on bus 9
  1 potential busses found: 0
  256-byte EDID successfully retrieved from i2c bus 0
  Looks like i2c was successful. Have a good day.
  Checksum Correct

  Section "Monitor"
Identifier "MP Monitor"
ModelName "MP Monitor"
VendorName "RX_"
# Monitor Manufactured week 41 of 2016
# EDID version 1.3
# Digital Display
DisplaySize 620 340
Gamma 2.20
Option "DPMS" "true"
Horizsync 23-80
VertRefresh 30-160
# Maximum pixel clock is 600MHz
#Not giving standard mode: 1280x720, 60Hz
#Not giving standard mode: 1280x1024, 60Hz
#Not giving standard mode: 1440x900, 60Hz
#Not giving standard mode: 1600x900, 60Hz
#Not giving standard mode: 1680x1050, 60Hz
#Not giving standard mode: 1920x1080, 60Hz
#Not giving standard mode: 1920x1200, 60Hz

#Extension block found. Parsing...
  #WARNING: I may have missed a mode (CEA mode 97)
  #DOUBLE WARNING: It's your first mode, too, so this may actually be important.
  #WARNING: I may have missed a mode (CEA mode 96)
  #WARNING: I may have missed a mode (CEA mode 101)
  #WARNING: I may have missed a mode (CEA mode 102)
  #WARNING: I may have missed a mode (CEA mode 93)
  #WARNING: I may have missed a mode (CEA mode 94)
  #WARNING: I may have missed a mode (CEA mode 95)
  #WARNING: I may have missed a mode (CEA mode 98)
Modeline"Mode 18" 148.50 1920 2008 2052 2200 1080 1084 1089 
1125 +hsync -vsync 
Modeline"Mode 0" 297.00 3840 3888 3920 4400 2160 2163 2169 2250 
+hsync -vsync 
Modeline"Mode 1" 241.50 2560 2608 2640 2720 1440 1443 1449 1481 
+hsync -vsync 
Modeline"Mode 2" 148.500 1920 2008 2052 2200 1080 1084 1089 
1125 +hsync +vsync
Modeline"Mode 3" 74.250 1920 2008 2052 2200 1080 1082 1087 1125 
+hsync +vsync interlace
Modeline"Mode 4" 74.250 1280 1390 1420 1650 720 725 730 750 
+hsync +vsync
Modeline"Mode 5" 27.027 720 736 798 858 480 489 495 525 -hsync 
-vsync
Modeline"Mode 6" 27.027 720 736 798 858 480 489 495 525 -hsync 
-vsync
Modeline"Mode 7" 27.027 1440 1478 1602 1716 480 484 487 525 
-hsync -vsync interlace
Modeline"Mode 8" 27.000 1440 1464 1590 1728 576 578 581 625 
-hsync -vsync interlace
Modeline"Mode 9" 25.200 640 656 752 800 480 490 492 525 -hsync 
-vsync
Modeline"Mode 10" 148.500 1920 2448 2492 2640 1080 1084 1089 
1125 +hsync +vsync
Modeline"Mode 11" 27.000 720 732 796 864 576 581 586 625 -hsync 
-vsync
Modeline"Mode 12" 74.250 1280 1720 1760 1980 720 725 730 750 
+hsync +vsync
Modeline"Mode 13" 74.250 1920 2448 2492 2640 1080 1082 1089 
1125 +hsync +vsync interlace
Modeline"Mode 14" 74.250 1920 2558 2602 2750 1080 1084 1089 
1125 +hsync +vsync
Modeline"Mode 15" 27.000 1440 1464 1590 1728 576 578 581 625 
-hsync -vsync interlace
Modeline"Mode 16" 27.000 720 732 796 864 576 581 586 625 -hsync 
-vsync
Modeline"Mode 17" 27.027 1440 1478 1602 1716 480 484 487 525 
-hsync -vsync interlace
Modeline"Mode 19" 148.50 1920 1968 2000 2640 1080 1084 1089 
1125 +hsync -vsync 
Modeline"Mode 20" 74.25 1920 2008 2052 2200 540 542 547 562 
+hsync +vsync interlace
Option "PreferredMode" "Mode 18"
  EndSection

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-58-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: 

[Touch-packages] [Bug 1703098] Re: No X if resuming when "Configure new displays when connected" unchecked

[Launchpad Bug Tracker]

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

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

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

Title:
  No X if resuming when "Configure new displays when connected"
  unchecked

Status in xorg package in Ubuntu:
  Expired

Bug description:
  This system normally has two displays connected which are always on.
  This problem arose when a TV was connected as a third display. It was
  preferred to have the TV left "disabled" by unchecking "Use this
  display" when it was not needed, but leaving its cable connected.
  However at each startup a GUI will be presented asking for display
  configuration because the option in Display settings for "Configure
  new displays when connected" is checked.

  If the option for "Connfigure new displays when connected" is then
  unchecked and the system is hibernated, then on resume X will not
  start. The only thing that can be done is to start a new terminal
  session and then startx will bring up a desktop. However the
  applications that were restored in the resume aren't accessible from
  this desktop session that has been manually started.

  The following were tried until the system was found to be resuming:
  1. Disconnected the third display
  2. Checked the option for "Configure new displays when connected"
  Not until both options had been tried would the system resume after 
hibernation and start X.

  lsb_release -rd
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

  apt-cache policy xorg
  xorg:
Installed: 1:7.7+13ubuntu3
Candidate: 1:7.7+13ubuntu3
Version table:
   *** 1:7.7+13ubuntu3 500
  500 http://nz.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  xrandr
  Screen 0: minimum 8 x 8, current 3600 x 1080, maximum 16384 x 16384
  DVI-I-0 disconnected (normal left inverted right x axis y axis)
  HDMI-0 connected primary 1920x1080+0+0 (normal left inverted right x axis y 
axis) 510mm x 287mm
 1920x1080 60.00*+
 1280x1024 75.0260.02  
 1152x864  75.00  
 1024x768  75.0360.00  
 800x600   75.0060.32  
 640x480   75.0059.94  
  HDMI-1 disconnected (normal left inverted right x axis y axis)
  DVI-I-1 connected 1680x1050+1920+0 (normal left inverted right x axis y axis) 
474mm x 296mm
 1680x1050 59.88*+  59.95  
 1280x1024 75.0260.02  
 1152x864  75.00  
 1024x768  75.0360.00  
 800x600   75.0060.32  
 640x480   75.0059.94  
  DP-0 disconnected (normal left inverted right x axis y axis)
  DP-1 disconnected (normal left inverted right x axis y axis)

  $ cat xorg.conf
  # nvidia-settings: X configuration file generated by nvidia-settings
  # nvidia-settings:  version 361.42  (buildd@lgw01-18)  Tue Apr  5 14:33:28 
UTC 2016

  Section "ServerLayout"
  Identifier "Layout0"
  Screen  0  "Screen0" 0 0
  InputDevice"Keyboard0" "CoreKeyboard"
  InputDevice"Mouse0" "CorePointer"
  Option "Xinerama" "0"
  EndSection

  Section "Files"
  EndSection

  Section "Module"
  Load   "dbe"
  Load   "extmod"
  Load   "type1"
  Load   "freetype"
  Load   "glx"
  EndSection

  Section "InputDevice"
  # generated from default
  Identifier "Mouse0"
  Driver "mouse"
  Option "Protocol" "auto"
  Option "Device" "/dev/psaux"
  Option "Emulate3Buttons" "no"
  Option "ZAxisMapping" "4 5"
  EndSection

  Section "InputDevice"
  # generated from default
  Identifier "Keyboard0"
  Driver "kbd"
  EndSection

  Section "Monitor"
  # HorizSync source: edid, VertRefresh source: edid
  Identifier "Monitor0"
  VendorName "Unknown"
  ModelName  "DELL P2210"
  HorizSync   30.0 - 83.0
  VertRefresh 56.0 - 75.0
  Option "DPMS"
  EndSection

  Section "Device"
  Identifier "Device0"
  Driver "nvidia"
  VendorName "NVIDIA Corporation"
  BoardName  "GeForce GTX 750"
  EndSection

  Section "Screen"
  Identifier "Screen0"
  Device "Device0"
  Monitor"Monitor0"
  DefaultDepth24
  Option "Stereo" "0"
  Option "nvidiaXineramaInfoOrder" "DFP-0"
  Option "metamodes" "DVI-I-1: nvidia-auto-select +3840+0, HDMI-0: 
nvidia-auto-select +1920+0, HDMI-1: nvidia-auto-select +0+0"
  Option "SLI" "Off"
  Option "MultiGPU" "Off"
  Option "BaseMosaic" "off"
  SubSection "Display"
  Depth   24
  EndSubSection
  EndSection

  $ nvidia-settings -q all -t

  Attributes queryable via 

[Touch-packages] [Bug 1707394] Re: DVI-I being read as DVI-D and i have no picture

[Launchpad Bug Tracker]

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

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

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

Title:
  DVI-I being read as DVI-D and i have no picture

Status in xorg package in Ubuntu:
  Expired

Bug description:
  Hi!

  I'm using Radeon R9 380X graphics card with two monitors. Before
  installing the radeon drivers, each of the monitors work properly. But
  after this, the DVI-D output is being read as DVI-I, and monitor
  attached to this port says "No signal". It only has a d-sub VGA input.
  The other monitors works fine.

  Here are the outputs of the xrandr command:

  Before installing the drivers:

  Screen 0: minimum 320 x 200, current 3840 x 1080, maximum 16384 x 16384
  DisplayPort-0 connected 1920x1080+1920+0 (normal left inverted right x axis y 
ax
  is) 477mm x 268mm
 1920x1080 60.00*+
 1600x1200 60.00  
 1680x1050 59.95  
 1280x1024 75.0260.02  
 1440x900  74.9859.89  
 1280x960  60.00  
 1280x800  59.81  
 1152x864  75.00  
 1024x768  75.0370.0760.00  
 832x624   74.55  
 800x600   72.1975.0060.3256.25  
 640x480   75.0072.8166.6759.94  
 720x400   70.08  
  HDMI-A-0 disconnected (normal left inverted right x axis y axis)
  DVI-D-0 disconnected (normal left inverted right x axis y axis)
  DVI-I-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y 
axi
  s) 477mm x 268mm
 1920x1080 60.00*+
 1680x1050 59.95  
 1280x1024 75.0260.02  
 1440x900  59.89  
 1280x960  60.00  
 1152x864  75.00  
 1024x768  75.0370.0760.00  
 832x624   74.55  
 800x600   72.1975.0060.3256.25  
 640x480   75.0072.8166.6759.94  
 720x400   70.08 

  After the installation:

  Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 16384 x 16384
  DisplayPort-0 connected primary 1920x1080+0+0 (normal left inverted right x 
axis
   y axis) 477mm x 268mm
 1920x1080 60.00*+
 1600x1200 60.00  
 1680x1050 59.95  
 1280x1024 75.0260.02  
 1440x900  74.9859.89  
 1280x960  60.00  
 1280x800  59.81  
 1152x864  75.00  
 1280x720  60.00  
 1024x768  75.0370.0760.00  
 832x624   74.55  
 800x600   72.1975.0060.3256.25  
 640x480   75.0072.8166.6759.94  
 720x400   70.08  
  HDMI-A-0 disconnected (normal left inverted right x axis y axis)
  DVI-D-0 disconnected (normal left inverted right x axis y axis)
  DVI-D-1 connected (normal left inverted right x axis y axis)
 1920x1080 60.00 +
 1680x1050 59.95  
 1280x1024 75.0260.02  
 1440x900  59.89  
 1280x960  60.00  
 1280x800  60.00  
 1152x864  75.00  
 1280x720  60.00  
 1024x768  75.0370.0760.00  
 832x624   74.55  
 800x600   72.1975.0060.3256.25  
 640x480   75.0072.8166.6759.94  
 720x400   70.08  

  By the way in practice, tho physycaly port itself is REALY a dual link DVI-D.
  Any solution?

  Thank you for the help!

  Matt

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  Uname: Linux 4.8.0-36-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sat Jul 29 15:09:32 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: amdgpu-pro, 17.30-458935, 4.8.0-36-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Tonga PRO [Radeon R9 285/380] 
[1002:6939] (rev f1) (prog-if 00 [VGA controller])
 Subsystem: PC Partner Limited / Sapphire Technology Tonga PRO [Radeon R9 
285/380] [174b:e306]
  InstallationDate: Installed on 2017-07-29 (0 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-36-generic 
root=UUID=7633e9db-735e-4db2-94f9-212b7fbcdd94 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2014
  

[Touch-packages] [Bug 1714834] Re: display is detected on a non-connected DP port

[Launchpad Bug Tracker]

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

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

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

Title:
  display is detected on a non-connected DP port

Status in xorg package in Ubuntu:
  Expired

Bug description:
  I have my screen connected to HDMI, and I also have a DP cable plugged
  in. The single screen attached gets detected twice, xrands shows both
  HDMI-1 as connected (primary) and DP-1 connected as well. If I
  disconnect the DP cable xrandr does now show it as connected anymore.
  xrandr output below:

  $ xrandr 
  Screen 0: minimum 320 x 200, current 2560 x 1440, maximum 8192 x 8192
  HDMI-1 connected primary 2560x1440+0+0 (normal left inverted right x axis y 
axis) 553mm x 311mm
 2560x1440 59.95*+
 2048x1152 60.00  
 1920x1200 59.95  
 1920x1080 60.0060.0050.0059.9430.0025.0024.00  
  29.9723.98  
 1920x1080i60.0050.0059.94  
 1600x1200 60.00  
 1680x1050 59.88  
 1280x1024 75.0260.02  
 1200x960  59.99  
 1152x864  75.00  
 1280x720  60.0050.0059.94  
 1024x768  75.0360.00  
 800x600   75.0060.32  
 720x576   50.00  
 720x576i  50.00  
 720x480   60.0059.94  
 720x480i  60.0059.94  
 640x480   75.0060.0059.94  
 720x400   70.08  
  DP-1 connected (normal left inverted right x axis y axis)
 2560x1440 59.95 +
 2048x1152 60.00  
 1920x1200 59.88  
 1920x1080 60.0050.0059.9430.0025.0024.0029.97  
  23.98  
 1920x1080i60.0050.0059.94  
 1600x1200 60.00  
 1680x1050 59.95  
 1280x1024 75.0260.02  
 1200x960  59.99  
 1152x864  75.00  
 1280x720  60.0050.0059.94  
 1024x768  75.0360.00  
 800x600   75.0060.32  
 720x576   50.00  
 720x480   60.0059.94  
 640x480   75.0060.0059.94  
 720x400   70.08  
  HDMI-2 disconnected (normal left inverted right x axis y axis)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: Budgie:GNOME
  Date: Mon Sep  4 00:45:37 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.40, 4.10.0-28-generic, x86_64: installed
   virtualbox, 5.0.40, 4.10.0-32-generic, x86_64: installed
   virtualbox, 5.0.40, 4.10.0-33-generic, x86_64: installed
   virtualbox, 5.0.40, 4.4.0-93-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1926] (rev 0a) (prog-if 
00 [VGA controller])
 Subsystem: Intel Corporation Skylake Integrated Graphics [8086:2063]
  InstallationDate: Installed on 2016-06-18 (441 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic 
root=UUID=04f11ff8-1726-4c69-9fec-69890c6d9f74 ro text
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.vendor: Intel Corp.
  dmi.board.vendor: Intel corporation
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Mon Sep  4 00:25:20 2017
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   Failed to load module "fbdev" (module does not exist, 0)
   Failed to load module "vesa" (module does not exist, 0)
   Failed to load module "fbdev" (module does not exist, 0)
   Failed to load module "vesa" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.3-1ubuntu1~16.04.2
  xserver.video_driver: modeset

To manage notifications about this bug go to:

[Touch-packages] [Bug 1716104] Re: can't get nvidia to work

[Launchpad Bug Tracker]

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

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

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

Title:
  can't get nvidia to work

Status in xorg package in Ubuntu:
  Expired

Bug description:
  I can't get the nvidia driver to work.

  When I type "prime-select intel" the system works.

  When I type "prime-select nvidia" glxinfo breaks.

  
  lsmod | grep nvidia
  nvidia_uvm688128  0
  nvidia_drm 49152  0
  nvidia_modeset843776  1 nvidia_drm
  nvidia  12984320  2 nvidia_modeset,nvidia_uvm
  drm_kms_helper155648  2 i915,nvidia_drm
  drm   364544  4 i915,drm_kms_helper,nvidia_drm

  
  > BUT: Xorg.0.log has the following errors:

  [   478.562] (EE) Failed to load module "nvidia" (module does not exist, 0)
  [   478.562] (EE) Failed to load module "nouveau" (module does not exist, 0)
  [   478.563] (EE) Failed to load module "nvidia" (module does not exist, 0)
  [   478.563] (EE) Failed to load module "nouveau" (module does not exist, 0)
  [   478.572] (EE) open /dev/fb0: No such file or directory
  [   478.572] (EE) open /dev/fb0: No such file or directory
  [   478.572] (EE) open /dev/fb0: No such file or directory
  [   478.572] (EE) open /dev/fb0: No such file or directory
  [   478.572] (EE) Screen 0 deleted because of no matching config section.
  [   478.572] (EE) Screen 0 deleted because of no matching config section.
  [   478.572] (EE) Screen 0 deleted because of no matching config section.
  [   478.572] (EE) Screen 0 deleted because of no matching config section.
  [   478.699] (EE) AIGLX: reverting to software rendering


  > I think I need to generate a valid xorg.conf file

  
  > BUT: when I execute sudo X -configure I get the following error at the 
end:

  
  List of video drivers:
amdgpu
ati
cirrus
intel
mach64
mga
neomagic
openchrome
qxl
r128
radeon
savage
siliconmotion
sisusb
trident
vmware
vesa
modesetting
fbdev
tdfx
  (++) Using config file: "/home/jccb/xorg.conf.new"
  (==) Using system config directory "/usr/share/X11/xorg.conf.d"
  Number of created screens does not match number of detected devices.
Configuration failed.
  (EE) Server terminated with error (2). Closing log file.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Uname: Linux 4.4.0-93-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.69  Wed Aug 16 19:34:54 
PDT 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4)
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sat Sep  9 11:25:06 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-93-generic, x86_64: installed
   nvidia-384, 384.69, 4.4.0-93-generic, x86_64: installed
   webcamstudio, 0.73, 3.13.0-101-generic, x86_64: installed
   webcamstudio, 0.73, 4.4.0-92-generic, x86_64: installed
   webcamstudio, 0.73, 4.4.0-93-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  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:1113]
 Subsystem: Micro-Star International Co., Ltd. [MSI] GM108M [GeForce 840M] 
[1462:1113]
  InstallationDate: Installed on 2015-01-23 (960 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Micro-Star International Co., Ltd. GP60 2PE
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic 
root=UUID=da904324-ef1b-4408-8fe7-543a661e7464 ro nomodeset=1 splash quiet
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/23/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16GHIMS.10B
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-16GH
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  

[Touch-packages] [Bug 1715633] Re: nvidia drivers...

[Launchpad Bug Tracker]

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

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

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

Title:
  nvidia drivers...

Status in xorg package in Ubuntu:
  Expired

Bug description:
  I'm trying to install the nvidia driver since days. I'm afraid that
  one of the "displays" (the intel VGA one) is not working anymore. At
  least it appears unclaimed with or without the nvidia driver.

  
  *** ANY HELP IS HIGHLY APPREACIATED, THANK YOU ***


  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Uname: Linux 4.4.0-93-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  381.26.13  Wed Aug 16 
04:02:47 PDT 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4)
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Thu Sep  7 14:54:16 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-93-generic, x86_64: installed
   nvidia-381, 381.26.13, 4.4.0-93-generic, x86_64: installed
   webcamstudio, 0.73, 3.13.0-101-generic, x86_64: installed
   webcamstudio, 0.73, 4.4.0-92-generic, x86_64: installed
   webcamstudio, 0.73, 4.4.0-93-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GconfCompiz:
   /apps/compiz-1/plugins:
     /apps/compiz-1/plugins/unityshell:
  /apps/compiz-1/plugins/unityshell/screen0:
   /apps/compiz-1/plugins/unityshell/screen0/options:
    devices_option = 0
  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:1113]
     Subsystem: Micro-Star International Co., Ltd. [MSI] GM108M [GeForce 840M] 
[1462:1113]
  InstallationDate: Installed on 2015-01-23 (958 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Micro-Star International Co., Ltd. GP60 2PE
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic 
root=UUID=da904324-ef1b-4408-8fe7-543a661e7464 ro nomodeset=1 splash quiet
  SourcePackage: xorg
  UnitySupportTest: Error: command ['/usr/lib/nux/unity_support_test', '-p', 
'-f'] failed with exit code 5: Error: GLX is not available on the system
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/23/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16GHIMS.10B
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-16GH
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16GHIMS.10B:bd10/23/2014:svnMicro-StarInternationalCo.,Ltd.:pnGP602PE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16GH:rvrREV1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: GP60 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.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.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.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Thu Sep  7 14:46:28 2017
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.3

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


-- 
Mailing list: https://launchpad.net/~touch-packages

[Touch-packages] [Bug 1718868] Re: update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults

[Launchpad Bug Tracker]

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

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

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

Title:
  update-rc.d: warning: start and stop actions are no longer supported;
  falling back to defaults

Status in xorg package in Ubuntu:
  Expired

Bug description:
  SO: Lubuntu 16.04 Xenial

  :~$ lsb_release -a
  LSB Version:  
core-9.20160110ubuntu0.2-amd64:core-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-amd64:security-9.20160110ubuntu0.2-noarch
  Distributor ID:   Ubuntu
  Description:Ubuntu 16.04
  Release:  16.04
  Codename: xenial

  
  :~$ uname -r
  4.4.0-96-generic

  
  below is a sample command where the error is displayed:

  ~$ dpkg-reconfigure keyboard-configuration
  [./ply-boot-client.c:183]   ply_boot_client_connect:could 
not connect to /org/freedesktop/plymouthd: Connection refused
  [./ply-boot-client.c:184]   
ply_boot_client_connect:trying old fallback path /ply-boot-protocol
  [./ply-boot-client.c:190]   ply_boot_client_connect:could 
not connect to /ply-boot-protocol: Connection refused
  [./plymouth.c:1121]  main:daemon not 
running
  [./plymouth.c:1124]  main:ping failed
  Your console font configuration will be updated the next time your system
  boots. If you want to update it now, run 'setupcon' from a virtual console.
  update-rc.d: warning: start and stop actions are no longer supported; falling 
back to defaults
  update-initramfs: deferring update (trigger activated)
  Elaborazione dei trigger per initramfs-tools (0.122ubuntu8.8)...
  update-initramfs: Generating /boot/initrd.img-4.4.0-96-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: x11-common 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-96.119-generic 4.4.83
  Uname: Linux 4.4.0-96-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Fri Sep 22 09:43:50 2017
  Dependencies: lsb-base 9.20160110ubuntu0.2
  InstallationDate: Installed on 2016-11-19 (306 days ago)
  InstallationMedia:
   
  PackageArchitecture: all
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-11-20 (305 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1718868/+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 1734487] Re: Nvidia optimus doesn't work for kernel later than 4.4.0-92

[Launchpad Bug Tracker]

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

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

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

Title:
  Nvidia optimus doesn't work for kernel later than 4.4.0-92

Status in xorg package in Ubuntu:
  Expired

Bug description:
  Nvidia optimus driver (intel + nvidia video cards) has been working
  perfectly until kernel 4.4.0-92. However, after updating to later
  versions (96, 98, 101) it stopped working and the system is only
  usable by command line.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-101.124-generic 4.4.95
  Uname: Linux 4.4.0-101-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:09:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.90  Tue Sep 19 19:17:35 
PDT 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5)
  ApportVersion: 2.20.1-0ubuntu2.13
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Sat Nov 25 22:23:01 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-101-generic, x86_64: installed
   nvidia-384, 384.90, 4.4.0-101-generic, x86_64: installed
   nvidia-384, 384.90, 4.4.0-92-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:3800]
 Subsystem: Lenovo GK208M [GeForce GT 730M] [17aa:3800]
  InstallationDate: Installed on 2016-11-05 (385 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 20270
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-101-generic.efi.signed 
root=UUID=e10739b9-9c0c-4937-af9d-a7784b5bd023 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/15/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7CCN34WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Cherry 4A Touch
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: IdeaPad U430 Touch
  dmi.modalias: 
dmi:bvnLENOVO:bvr7CCN34WW:bd10/15/2013:svnLENOVO:pn20270:pvrIdeaPadU430Touch:rvnLENOVO:rnCherry4ATouch:rvr31900058STD:cvnLENOVO:ct10:cvrIdeaPadU430Touch:
  dmi.product.name: 20270
  dmi.product.version: IdeaPad U430 Touch
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  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.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sat Nov 25 22:06:20 2017
  xserver.configfile: /etc/X11/xorg.conf
  xserver.devices:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1734487/+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 1736146] Re: Xorg crashed with SIGABRT [SIGSEGV in list_del() from pb_slab_reclaim()]

[Launchpad Bug Tracker]

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

** Changed in: xorg-server (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/1736146

Title:
  Xorg crashed with SIGABRT [SIGSEGV in list_del() from
  pb_slab_reclaim()]

Status in mesa package in Ubuntu:
  Expired
Status in xorg-server package in Ubuntu:
  Expired

Bug description:
  Xorg crashed with SIGABRT

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-core 2:1.19.5-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.8-0ubuntu2
  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: Mon Dec  4 14:19:40 2017
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/xorg/Xorg
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 5500 [17aa:3824]
  InstallationDate: Installed on 2015-12-14 (721 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: LENOVO 80K6
  ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
  ProcEnviron: PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=73fd1edc-d964-40d3-a1dd-b1ca4118cce6 ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
  Title: Xorg crashed with SIGABRT
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 03/19/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: C2CN17WW(V1.03)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lenovo Z51-70
  dmi.board.vendor: LENOVO
  dmi.board.version: No DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Z51-70
  dmi.modalias: 
dmi:bvnLENOVO:bvrC2CN17WW(V1.03):bd03/19/2015:svnLENOVO:pn80K6:pvrLenovoZ51-70:rvnLENOVO:rnLenovoZ51-70:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoZ51-70:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80K6
  dmi.product.version: Lenovo Z51-70
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.1+18.04.20171116-0ubuntu1
  version.libdrm2: libdrm2 2.4.88-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Mon Dec  4 14:19:47 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2
  xserver.video_driver: modeset

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1736146/+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 1736146] Re: Xorg crashed with SIGABRT [SIGSEGV in list_del() from pb_slab_reclaim()]

[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/1736146

Title:
  Xorg crashed with SIGABRT [SIGSEGV in list_del() from
  pb_slab_reclaim()]

Status in mesa package in Ubuntu:
  Expired
Status in xorg-server package in Ubuntu:
  Expired

Bug description:
  Xorg crashed with SIGABRT

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-core 2:1.19.5-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.8-0ubuntu2
  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: Mon Dec  4 14:19:40 2017
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/xorg/Xorg
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 5500 [17aa:3824]
  InstallationDate: Installed on 2015-12-14 (721 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: LENOVO 80K6
  ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
  ProcEnviron: PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=73fd1edc-d964-40d3-a1dd-b1ca4118cce6 ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
  Title: Xorg crashed with SIGABRT
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 03/19/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: C2CN17WW(V1.03)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lenovo Z51-70
  dmi.board.vendor: LENOVO
  dmi.board.version: No DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Z51-70
  dmi.modalias: 
dmi:bvnLENOVO:bvrC2CN17WW(V1.03):bd03/19/2015:svnLENOVO:pn80K6:pvrLenovoZ51-70:rvnLENOVO:rnLenovoZ51-70:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoZ51-70:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80K6
  dmi.product.version: Lenovo Z51-70
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.1+18.04.20171116-0ubuntu1
  version.libdrm2: libdrm2 2.4.88-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Mon Dec  4 14:19:47 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2
  xserver.video_driver: modeset

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1736146/+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 1890411] Re: [bionic] Xorg crashes when starting gdm3. Bug in libgl1-mesa-dri.

[Launchpad Bug Tracker]

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

** Changed in: xorg-server (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/1890411

Title:
  [bionic] Xorg crashes when starting gdm3. Bug in libgl1-mesa-dri.

Status in mesa package in Ubuntu:
  Expired
Status in xorg-server package in Ubuntu:
  Expired

Bug description:
  When ubuntu starts up, gdm3 does not start due to a crash in the the
  xserver:

  [  1271.342] (II) SELinux: Disabled on system
  [  1271.346] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
  [  1271.346] (II) AIGLX: enabled GLX_ARB_create_context
  [  1271.346] (II) AIGLX: enabled GLX_ARB_create_context_profile
  [  1271.346] (II) AIGLX: enabled GLX_EXT_create_context_es{,2}_profile
  [  1271.346] (II) AIGLX: enabled GLX_INTEL_swap_event
  [  1271.346] (II) AIGLX: enabled GLX_SGI_swap_control
  [  1271.346] (II) AIGLX: enabled GLX_EXT_framebuffer_sRGB
  [  1271.346] (II) AIGLX: enabled GLX_ARB_fbconfig_float
  [  1271.346] (II) AIGLX: enabled GLX_EXT_fbconfig_packed_float
  [  1271.346] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
  [  1271.346] (II) AIGLX: enabled GLX_ARB_create_context_robustness
  [  1271.346] (II) AIGLX: Loaded and initialized i965
  [  1271.346] (II) GLX: Initialized DRI2 GL provider for screen 0
  [  1271.348] (II) modeset(0): Damage tracking initialized
  [  1271.348] (II) modeset(0): Setting screen physical size to 508 x 317
  [  1271.352] (EE) 
  [  1271.352] (EE) Backtrace:
  [  1271.352] (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4d) [0x5649b579bacd]
  [  1271.352] (EE) 1: /usr/lib/xorg/Xorg (0x5649b55e3000+0x1bc869) 
[0x5649b579f869]
  [  1271.352] (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7f5c7d0a5000+0x128a0) [0x7f5c7d0b78a0]
  [  1271.352] (EE) 3: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so 
(0x7f5c77bfa000+0x8e8652) [0x7f5c784e2652]
  [  1271.352] (EE) 4: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so 
(0x7f5c77bfa000+0x8e877f) [0x7f5c784e277f]
  [  1271.352] (EE) 5: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so 
(0x7f5c77bfa000+0x122916) [0x7f5c77d1c916]
  [  1271.352] (EE) 6: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so 
(0x7f5c77bfa000+0x1189bc) [0x7f5c77d129bc]
  [  1271.352] (EE) 7: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so 
(0x7f5c77bfa000+0x109c1b) [0x7f5c77d03c1b]
  [  1271.352] (EE) 8: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so 
(0x7f5c77bfa000+0x279558) [0x7f5c77e73558]
  [  1271.352] (EE) 9: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so 
(0x7f5c77bfa000+0x2796e3) [0x7f5c77e736e3]
  [  1271.352] (EE) 10: /usr/lib/xorg/modules/libglamoregl.so 
(0x7f5c79937000+0x1a1ab) [0x7f5c799511ab]
  [  1271.352] (EE) 11: /usr/lib/xorg/Xorg (0x5649b55e3000+0x13ed03) 
[0x5649b5721d03]
  [  1271.352] (EE) 12: /usr/lib/xorg/Xorg (miPaintWindow+0x22f) 
[0x5649b577fd1f]
  [  1271.352] (EE) 13: /usr/lib/xorg/Xorg (miWindowExposures+0x112) 
[0x5649b577fa62]
  [  1271.352] (EE) 14: /usr/lib/xorg/Xorg (0x5649b55e3000+0xa9c41) 
[0x5649b568cc41]
  [  1271.352] (EE) 15: /usr/lib/xorg/Xorg (MapWindow+0x114) [0x5649b5665d04]
  [  1271.352] (EE) 16: /usr/lib/xorg/Xorg (0x5649b55e3000+0x56e79) 
[0x5649b5639e79]
  [  1271.352] (EE) 17: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xe7) [0x7f5c7ccd5b97]
  [  1271.352] (EE) 18: /usr/lib/xorg/Xorg (_start+0x2a) [0x5649b5623b8a]
  [  1271.352] (EE) 
  [  1271.352] (EE) Segmentation fault at address 0x4
  [  1271.352] (EE) 
  Fatal server error:
  [  1271.352] (EE) Caught signal 11 (Segmentation fault). Server aborting
  [  1271.352] (EE) 
  [  1271.352] (EE) 

  As i965_dri.so is part of the libgl-mesa-dri package I downgraded this
  specific package from version 20.0.8-0ubuntu1~18.04.1 back to
  19.2.8-0ubuntu0~18.04.3.

  This solves the problem. So I suspect that the problem is in this
  specific package.

  My machine is (uname):
  4.4.0-66-generic #87-Ubuntu SMP Fri Mar 3 15:29:05 UTC 2017 x86_64 x86_64 
x86_64 GNU/Linux

  (lspci)
  00:00.0 Host bridge: Intel Corporation 4th Gen Core Processor DRAM Controller 
(rev 06)
  00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen 
Core Processor Integrated Graphics Controller (rev 06)
  00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family 
USB xHCI (rev 05)
  00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series 
Chipset Family MEI Controller #1 (rev 04)
  00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family 
USB EHCI #2 (rev 05)
  00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High 
Definition Audio Controller (rev 05)
  00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI 
Express Root Port #1 (rev d5)
  00:1c.2 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI 
Express Root Port #3 (rev d5)
  00:1d.0 USB 

[Touch-packages] [Bug 1890411] Re: [bionic] Xorg crashes when starting gdm3. Bug in libgl1-mesa-dri.

[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/1890411

Title:
  [bionic] Xorg crashes when starting gdm3. Bug in libgl1-mesa-dri.

Status in mesa package in Ubuntu:
  Expired
Status in xorg-server package in Ubuntu:
  Expired

Bug description:
  When ubuntu starts up, gdm3 does not start due to a crash in the the
  xserver:

  [  1271.342] (II) SELinux: Disabled on system
  [  1271.346] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
  [  1271.346] (II) AIGLX: enabled GLX_ARB_create_context
  [  1271.346] (II) AIGLX: enabled GLX_ARB_create_context_profile
  [  1271.346] (II) AIGLX: enabled GLX_EXT_create_context_es{,2}_profile
  [  1271.346] (II) AIGLX: enabled GLX_INTEL_swap_event
  [  1271.346] (II) AIGLX: enabled GLX_SGI_swap_control
  [  1271.346] (II) AIGLX: enabled GLX_EXT_framebuffer_sRGB
  [  1271.346] (II) AIGLX: enabled GLX_ARB_fbconfig_float
  [  1271.346] (II) AIGLX: enabled GLX_EXT_fbconfig_packed_float
  [  1271.346] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
  [  1271.346] (II) AIGLX: enabled GLX_ARB_create_context_robustness
  [  1271.346] (II) AIGLX: Loaded and initialized i965
  [  1271.346] (II) GLX: Initialized DRI2 GL provider for screen 0
  [  1271.348] (II) modeset(0): Damage tracking initialized
  [  1271.348] (II) modeset(0): Setting screen physical size to 508 x 317
  [  1271.352] (EE) 
  [  1271.352] (EE) Backtrace:
  [  1271.352] (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4d) [0x5649b579bacd]
  [  1271.352] (EE) 1: /usr/lib/xorg/Xorg (0x5649b55e3000+0x1bc869) 
[0x5649b579f869]
  [  1271.352] (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7f5c7d0a5000+0x128a0) [0x7f5c7d0b78a0]
  [  1271.352] (EE) 3: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so 
(0x7f5c77bfa000+0x8e8652) [0x7f5c784e2652]
  [  1271.352] (EE) 4: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so 
(0x7f5c77bfa000+0x8e877f) [0x7f5c784e277f]
  [  1271.352] (EE) 5: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so 
(0x7f5c77bfa000+0x122916) [0x7f5c77d1c916]
  [  1271.352] (EE) 6: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so 
(0x7f5c77bfa000+0x1189bc) [0x7f5c77d129bc]
  [  1271.352] (EE) 7: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so 
(0x7f5c77bfa000+0x109c1b) [0x7f5c77d03c1b]
  [  1271.352] (EE) 8: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so 
(0x7f5c77bfa000+0x279558) [0x7f5c77e73558]
  [  1271.352] (EE) 9: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so 
(0x7f5c77bfa000+0x2796e3) [0x7f5c77e736e3]
  [  1271.352] (EE) 10: /usr/lib/xorg/modules/libglamoregl.so 
(0x7f5c79937000+0x1a1ab) [0x7f5c799511ab]
  [  1271.352] (EE) 11: /usr/lib/xorg/Xorg (0x5649b55e3000+0x13ed03) 
[0x5649b5721d03]
  [  1271.352] (EE) 12: /usr/lib/xorg/Xorg (miPaintWindow+0x22f) 
[0x5649b577fd1f]
  [  1271.352] (EE) 13: /usr/lib/xorg/Xorg (miWindowExposures+0x112) 
[0x5649b577fa62]
  [  1271.352] (EE) 14: /usr/lib/xorg/Xorg (0x5649b55e3000+0xa9c41) 
[0x5649b568cc41]
  [  1271.352] (EE) 15: /usr/lib/xorg/Xorg (MapWindow+0x114) [0x5649b5665d04]
  [  1271.352] (EE) 16: /usr/lib/xorg/Xorg (0x5649b55e3000+0x56e79) 
[0x5649b5639e79]
  [  1271.352] (EE) 17: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xe7) [0x7f5c7ccd5b97]
  [  1271.352] (EE) 18: /usr/lib/xorg/Xorg (_start+0x2a) [0x5649b5623b8a]
  [  1271.352] (EE) 
  [  1271.352] (EE) Segmentation fault at address 0x4
  [  1271.352] (EE) 
  Fatal server error:
  [  1271.352] (EE) Caught signal 11 (Segmentation fault). Server aborting
  [  1271.352] (EE) 
  [  1271.352] (EE) 

  As i965_dri.so is part of the libgl-mesa-dri package I downgraded this
  specific package from version 20.0.8-0ubuntu1~18.04.1 back to
  19.2.8-0ubuntu0~18.04.3.

  This solves the problem. So I suspect that the problem is in this
  specific package.

  My machine is (uname):
  4.4.0-66-generic #87-Ubuntu SMP Fri Mar 3 15:29:05 UTC 2017 x86_64 x86_64 
x86_64 GNU/Linux

  (lspci)
  00:00.0 Host bridge: Intel Corporation 4th Gen Core Processor DRAM Controller 
(rev 06)
  00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen 
Core Processor Integrated Graphics Controller (rev 06)
  00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family 
USB xHCI (rev 05)
  00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series 
Chipset Family MEI Controller #1 (rev 04)
  00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family 
USB EHCI #2 (rev 05)
  00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High 
Definition Audio Controller (rev 05)
  00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI 
Express Root Port #1 (rev d5)
  00:1c.2 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI 
Express Root Port #3 (rev d5)
  00:1d.0 USB controller: 

[Touch-packages] [Bug 2018060] Re: Merge bridge-utils from Debian unstable for mantic

[Launchpad Bug Tracker]

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

** Changed in: bridge-utils (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Merge bridge-utils from Debian unstable for mantic

Status in bridge-utils package in Ubuntu:
  Expired

Bug description:
  Scheduled-For: Backlog
  Upstream: tbd
  Debian:   1.7.1-1
  Ubuntu:   1.7.1-1ubuntu1


  There is nothing yet to merge for bridge-utils currently, but this
  ticket is filed prospectfully for tracking purposes in case a merge
  does become available later this cycle.

  If it turns out this needs a sync rather than a merge, please change
  the tag 'needs-merge' to 'needs-sync', and (optionally) update the
  title as desired.

  
  ### New Debian Changes ###

  bridge-utils (1.7.1-1) unstable; urgency=low

* New upstream version.
  Only some fixes for compilation warnings and the man page.
* Update standards version to 4.6.1, no changes needed.
* Set debhelper-compat version in Build-Depends.
* Trim trailing whitespace.

   -- Santiago García Mantiñán   Wed, 25 Jan 2023
  22:11:52 +0100

  bridge-utils (1.7-2) unstable; urgency=medium

* Add BRIDGE_DISABLE_LINKLOCAL_IPV6_ALSO_PHYS to /etc/default/bridge-utils
  to stop disabling IPv6 on physical interfaces of vlan ports if set to no. 
  Closes: #989162.
* Update interfaces man page, IPv6 works with STP on after DAD was fixed.
  Closes: #980507.
* Treat vlan ports the same as ifupdown, avoid octal vlans. Closes: #995627.
* Update NEWS file to fix us blaming the kernel for the MAC address
  selection that is really overridden by systemd.

   -- Santiago García Mantiñán   Mon, 03 Oct 2022
  23:11:46 +0200

  bridge-utils (1.7-1) unstable; urgency=medium

* New upstream version.
  Only messages related changes and compilation fixes.
* Remove preserve_gcc_flags patch (in upstream now).
* Bump standards, no change needed.
* Clarify portprio and fix example.
* Update upstream url.
* Fix NEWS versioning of last entry :-?

   -- Santiago Garcia Mantinan   Wed, 24 Feb 2021
  12:34:03 +0100

  bridge-utils (1.6-6) unstable; urgency=medium

* Fix IPv6 address getting assigned on hotplug devices.
  Closes: #980752.
* Fix waiting so that DAD works again. Closes: #982943.
* Move mac setting before brctl addif to ensure mac setting.
  Closes: #980856.
* Update documentation and add examples. Closes: #765098.
* Update manpages. Closes: #981253.
* Add a note on MTU settings. Closes: #292088.
* Hook also on down to recreate the bridge so that multiple
  stanzas work Ok on ifdown. Closes: #319832.

   -- Santiago Garcia Mantinan   Tue, 16 Feb 2021
  13:29:04 +0100

  bridge-utils (1.6-5) unstable; urgency=low

* Overload bridge_hw to allow do specify an interface as well as the
  MAC address. Closes: #966244.
* Change man page for bridge-utils-interfaces and news fileto document
  this overloading.

   -- Santiago Garcia Mantinan   Fri, 22 Jan 2021
  11:08:47 +0100

  bridge-utils (1.6-4) unstable; urgency=low

* Add en* to the device regex so that all catches them. Closes: #966319.
* Document MAC address changes on news. Closes: #980505.

   -- Santiago Garcia Mantinan   Thu, 21 Jan 2021
  10:51:31 +0100

  bridge-utils (1.6-3) unstable; urgency=medium

* Support VLAN aware setups where we need vlan filtering.
  Thanks Benedikt Spranger for the patch. Closes: #950879.
* Clarify on manual page that stp will get IPv6 lost. Closes: #736336.
* Add a 1 second sleep if hw address needs to be changed. Closes: #945466.

   -- Santiago Garcia Mantinan   Thu, 30 Apr 2020
  10:06:38 +0200

  bridge-utils (1.6-2) unstable; urgency=medium

* Bump Standards-Version.
* Preserve gcc flags set when building the lib.

   -- Santiago Garcia Mantinan   Mon, 28 Jan 2019
  00:25:14 +0100

  bridge-utils (1.6-1) unstable; urgency=low

* New upstream version.
* Change default back to not hotplug. Closes: #892277.
* Allow mtu to be set on the bridge by propagating it to the bridged
  interfaces. Closes: #661711.
* Remove kernel headers from the package.

   -- Santiago Garcia Mantinan   Tue, 15 Jan 2019
  13:18:33 +0100

  bridge-utils (1.5-16) unstable; urgency=medium

* Don't set dev globally at bridge-utils.sh. Closes: #873086.

   -- Santiago Garcia Mantinan   Sun, 08 Apr 2018
  23:06:30 +0200

  bridge-utils (1.5-15) unstable; urgency=medium


  
  ### Old Ubuntu Delta ###

  bridge-utils (1.7.1-1ubuntu1) lunar; urgency=medium

* Merge from Debian unstable, remaining changes:
  - Don't call ifup from bridge-network-interface, instead just call brctl
and let udev/upstart bring the interface up.
  - 

[Touch-packages] [Bug 2018079] Re: Merge libmnl from Debian unstable for mantic

[Launchpad Bug Tracker]

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

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

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

Title:
  Merge libmnl from Debian unstable for mantic

Status in libmnl package in Ubuntu:
  Expired

Bug description:
  Scheduled-For: Backlog
  Upstream: tbd
  Debian:   1.0.4-3
  Ubuntu:   1.0.4-3ubuntu1


  There is nothing yet to merge for libmnl currently, but this ticket is
  filed prospectfully for tracking purposes in case a merge does become
  available later this cycle.

  If it turns out this needs a sync rather than a merge, please change
  the tag 'needs-merge' to 'needs-sync', and (optionally) update the
  title as desired.

  
  ### Old Ubuntu Delta ###

  libmnl (1.0.4-3ubuntu1) kinetic; urgency=medium

* Static build does not work for libmnl (-lmnl) (LP: #1971523)

   -- Michal Maloszewski   Thu, 21 Jul
  2022 14:02:16 +0200

  libmnl (1.0.4-3build2) jammy; urgency=high

* No change rebuild for ppc64el baseline bump.

   -- Julian Andres Klode   Thu, 24 Mar 2022
  13:13:28 +0100

  libmnl (1.0.4-3build1) impish; urgency=medium

* No-change rebuild to build packages with zstd compression.

   -- Matthias Klose   Thu, 07 Oct 2021 12:16:42 +0200

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libmnl/+bug/2018079/+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 2018081] Re: Merge libseccomp from Debian unstable for mantic

[Launchpad Bug Tracker]

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

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

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

Title:
  Merge libseccomp from Debian unstable for mantic

Status in libseccomp package in Ubuntu:
  Expired

Bug description:
  Scheduled-For: Backlog
  Upstream: tbd
  Debian:   2.5.4-1
  Ubuntu:   2.5.4-1ubuntu3

  
  The NOT SERVER TEAM team has maintained this package in the past and may be 
handling this merge.

  If it turns out this needs a sync rather than a merge, please change
  the tag 'needs-merge' to 'needs-sync', and (optionally) update the
  title as desired.

  
  ### Old Ubuntu Delta ###

  libseccomp (2.5.4-1ubuntu3) lunar; urgency=medium

* Rebuild to drop Python 3.10 extension

   -- Jeremy Bicha   Tue, 28 Feb 2023 17:23:34 -0500

  libseccomp (2.5.4-1ubuntu2) lunar; urgency=medium

* No-change rebuild with Python 3.11 as supported

   -- Graham Inggs   Wed, 02 Nov 2022 10:24:36 +

  libseccomp (2.5.4-1ubuntu1) kinetic; urgency=medium

* Merge from Debian unstable; remaining changes:
  - Add autopkgtests

   -- Alex Murray   Tue, 03 May 2022 11:43:10
  +0930

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

Re: [Touch-packages] [Bug 1972131] Re: occasional flashing screen since upgrade to 22.04

[Kent Frazier]

I'm on 23.04 now (and now no longer have a touchscreen)  So can't 
test... sorry.

On 8/28/23 11:45, Oibaf wrote:
> Kent, Ubuntu 22.04 now has mesa 23.0.4-0ubuntu1~22.04.1, can you try it,
> is this still an issue for you?
>

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

Title:
  occasional flashing screen since upgrade to 22.04

Status in mesa package in Ubuntu:
  New

Bug description:
  Since upgrading to 22.04 I often experienced a flashing screen. I have
  noticed the issue in particular when I have an onboard keyboard
  displayed. Hiding the onboard keyboard and then showing the keyboard
  seems to resolve the flashing problem

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-release-upgrader-core 1:22.04.10
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Sun May  8 17:20:13 2022
  InstallationDate: Installed on 2020-07-18 (659 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: Upgraded to jammy on 2022-04-29 (9 days ago)
  VarLogDistupgradeTermlog:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1972131/+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 1641230] Re: package linux-image-4.4.0-43-generic 4.4.0-43.63 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 due to /usr/s

[Clayton M.]

I shut down the VM and used a live ISO to take a look at the filesystem.
You were correct - there is an /etc/ld.so.preload which points to
/lib/libgcwrap.so. There is also a /usr/lib/libgcwrap.so copy.

These files were marked as immutable and were not visible from the
booted system. I took a look at the cron configurations and found the
root user had an entry for "perfcc". Looking this up, perfcc/perfctl is
a crypto-miner malware.

Thanks for all your help in troubleshooting this. I hope it clarifies
for someone what may be afoot if they find libgcwrap present on their
system; there was nothing available on the popular search engines about
it.

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

Title:
  package linux-image-4.4.0-43-generic 4.4.0-43.63 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1 due to /usr/share/initramfs-tools/hooks/fsck
  failed with return 1

Status in e2fsprogs package in Ubuntu:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  Do you want to continue? [Y/n] y
  (Reading database ... 254369 files and directories currently installed.)
  Removing linux-image-extra-4.4.0-43-generic (4.4.0-43.63) ...
  run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.4.0-43-generic 
/boot/vmlinuz-4.4.0-43-generic
  run-parts: executing /etc/kernel/postinst.d/dkms 4.4.0-43-generic 
/boot/vmlinuz-4.4.0-43-generic
  Error! Your kernel headers for kernel 4.4.0-43-generic cannot be found.
  Please install the linux-headers-4.4.0-43-generic package,
  or use the --kernelsourcedir option to tell DKMS where it's located
  run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.4.0-43-generic 
/boot/vmlinuz-4.4.0-43-generic
  update-initramfs: Generating /boot/initrd.img-4.4.0-43-generic
  E: /usr/share/initramfs-tools/hooks/fsck failed with return 1.
  update-initramfs: failed for /boot/initrd.img-4.4.0-43-generic with 1.
  run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
  dpkg: error processing package linux-image-extra-4.4.0-43-generic (--remove):
   subprocess installed post-removal script returned error exit status 1
  Removing linux-image-extra-4.4.0-47-generic (4.4.0-47.68) ...
  run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.4.0-47-generic 
/boot/vmlinuz-4.4.0-47-generic
  run-parts: executing /etc/kernel/postinst.d/dkms 4.4.0-47-generic 
/boot/vmlinuz-4.4.0-47-generic
  run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.4.0-47-generic 
/boot/vmlinuz-4.4.0-47-generic
  update-initramfs: Generating /boot/initrd.img-4.4.0-47-generic
  E: /usr/share/initramfs-tools/hooks/fsck failed with return 1.
  update-initramfs: failed for /boot/initrd.img-4.4.0-47-generic with 1.
  run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
  dpkg: error processing package linux-image-extra-4.4.0-47-generic (--remove):
   subprocess installed post-removal script returned error exit status 1
  Errors were encountered while processing:
   linux-image-extra-4.4.0-43-generic
   linux-image-extra-4.4.0-47-generic
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-43-generic 4.4.0-43.63
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pezhman1535 F pulseaudio
  Date: Fri Nov 11 21:03:09 2016
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=UUID=e8c76af0-04d5-4831-a401-a0911630111c
  InstallationDate: Installed on 2016-08-27 (76 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: ASUSTeK COMPUTER INC. S300CA
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed 
root=UUID=72d332d4-9180-442f-a032-8c1b612566ec ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: initramfs-tools
  Title: package linux-image-4.4.0-43-generic 4.4.0-43.63 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/22/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: S300CA.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: S300CA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  

[Touch-packages] [Bug 2033325] Re: systemd fails to set unit as inactive when using socket activation and the main process has exited

[Bug Watch Updater]

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

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

Title:
  systemd fails to set unit as inactive when using socket activation and
  the main process has exited

Status in systemd:
  Fix Released
Status in libvirt package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  systemd 253.5 on Mantic is affected by a bug which makes it fail to
  mark a unit as inactive even when its main process exited (when using
  socket activation).  This is affecting libvirt and possibly other
  services.

  Upstream has a bug: https://github.com/systemd/systemd/issues/27953

  which has been fixed by: https://github.com/systemd/systemd/pull/28000

  To reproduce the problem:

  $ lxc launch ubuntu-daily:mantic libvirt-hang --vm
  $ lxc shell libvirt-hang
  # apt update && apt upgrade -y
  # apt install -y libvirt-daemon-system
  # systemctl status libvirtd.service

  You'll notice that there is a libvirt process running:

  ...
   CGroup: /system.slice/libvirtd.service
   ├─ 870 /usr/sbin/dnsmasq 
--conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro 
--dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
   ├─ 871 /usr/sbin/dnsmasq 
--conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro 
--dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
   └─1020 /usr/sbin/libvirtd --timeout 120
  ...

  Wait for two minutes (or edit /etc/default/libvirtd and reduce the
  timeout), then check the status again.  You'll notice that the
  libvirtd process has exited, but the unit is still marked as active:

  root@libvirt-hang:~# systemctl status libvirtd.service 
  ● libvirtd.service - Virtualization daemon
   Loaded: loaded (/lib/systemd/system/libvirtd.service; enabled; preset: 
enabled)
   Active: active (running) since Mon 2023-08-28 23:06:23 UTC; 57s ago
  TriggeredBy: ● libvirtd-admin.socket
   ● libvirtd.socket
   ● libvirtd-ro.socket
 Docs: man:libvirtd(8)
   https://libvirt.org
  Process: 1020 ExecStart=/usr/sbin/libvirtd $LIBVIRTD_ARGS (code=exited, 
status=0/SUCCESS)
 Main PID: 1020 (code=exited, status=0/SUCCESS)
Tasks: 2 (limit: 32768)
   Memory: 22.4M
  CPU: 161ms
   CGroup: /system.slice/libvirtd.service
   ├─870 /usr/sbin/dnsmasq 
--conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro 
--dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
   └─871 /usr/sbin/dnsmasq 
--conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro 
--dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
  ...

  
  libvirtd.service is socket-activated, but the fact that it is still 
considered to be active after the main process exited means that the socket 
won't be actively listening, and you end up seeing libvirt-related commands 
hang indefinitely, effectively rendering libvirt useless until you manually 
restart the service.

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/2033325/+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 2033325] [NEW] systemd fails to set unit as inactive when using socket activation and the main process has exited

[Sergio Durigan Junior]

Public bug reported:

systemd 253.5 on Mantic is affected by a bug which makes it fail to mark
a unit as inactive even when its main process exited (when using socket
activation).  This is affecting libvirt and possibly other services.

Upstream has a bug: https://github.com/systemd/systemd/issues/27953

which has been fixed by: https://github.com/systemd/systemd/pull/28000

To reproduce the problem:

$ lxc launch ubuntu-daily:mantic libvirt-hang --vm
$ lxc shell libvirt-hang
# apt update && apt upgrade -y
# apt install -y libvirt-daemon-system
# systemctl status libvirtd.service

You'll notice that there is a libvirt process running:

...
 CGroup: /system.slice/libvirtd.service
 ├─ 870 /usr/sbin/dnsmasq 
--conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro 
--dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
 ├─ 871 /usr/sbin/dnsmasq 
--conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro 
--dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
 └─1020 /usr/sbin/libvirtd --timeout 120
...

Wait for two minutes (or edit /etc/default/libvirtd and reduce the
timeout), then check the status again.  You'll notice that the libvirtd
process has exited, but the unit is still marked as active:

root@libvirt-hang:~# systemctl status libvirtd.service 
● libvirtd.service - Virtualization daemon
 Loaded: loaded (/lib/systemd/system/libvirtd.service; enabled; preset: 
enabled)
 Active: active (running) since Mon 2023-08-28 23:06:23 UTC; 57s ago
TriggeredBy: ● libvirtd-admin.socket
 ● libvirtd.socket
 ● libvirtd-ro.socket
   Docs: man:libvirtd(8)
 https://libvirt.org
Process: 1020 ExecStart=/usr/sbin/libvirtd $LIBVIRTD_ARGS (code=exited, 
status=0/SUCCESS)
   Main PID: 1020 (code=exited, status=0/SUCCESS)
  Tasks: 2 (limit: 32768)
 Memory: 22.4M
CPU: 161ms
 CGroup: /system.slice/libvirtd.service
 ├─870 /usr/sbin/dnsmasq 
--conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro 
--dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
 └─871 /usr/sbin/dnsmasq 
--conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro 
--dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
...


libvirtd.service is socket-activated, but the fact that it is still considered 
to be active after the main process exited means that the socket won't be 
actively listening, and you end up seeing libvirt-related commands hang 
indefinitely, effectively rendering libvirt useless until you manually restart 
the service.

** Affects: systemd
 Importance: Unknown
 Status: Fix Released

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

** Affects: systemd (Ubuntu)
 Importance: Critical
 Status: New

** Bug watch added: github.com/systemd/systemd/issues #27953
   https://github.com/systemd/systemd/issues/27953

** Also affects: systemd via
   https://github.com/systemd/systemd/issues/27953
   Importance: Unknown
   Status: Unknown

** Also affects: libvirt (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  systemd fails to set unit as inactive when using socket activation and
  the main process has exited

Status in systemd:
  Fix Released
Status in libvirt package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  systemd 253.5 on Mantic is affected by a bug which makes it fail to
  mark a unit as inactive even when its main process exited (when using
  socket activation).  This is affecting libvirt and possibly other
  services.

  Upstream has a bug: https://github.com/systemd/systemd/issues/27953

  which has been fixed by: https://github.com/systemd/systemd/pull/28000

  To reproduce the problem:

  $ lxc launch ubuntu-daily:mantic libvirt-hang --vm
  $ lxc shell libvirt-hang
  # apt update && apt upgrade -y
  # apt install -y libvirt-daemon-system
  # systemctl status libvirtd.service

  You'll notice that there is a libvirt process running:

  ...
   CGroup: /system.slice/libvirtd.service
   ├─ 870 /usr/sbin/dnsmasq 
--conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro 
--dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
   ├─ 871 /usr/sbin/dnsmasq 
--conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro 
--dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
   └─1020 /usr/sbin/libvirtd --timeout 120
  ...

  Wait for two minutes (or edit /etc/default/libvirtd and reduce the
  timeout), then check the status again.  You'll notice that the
  libvirtd process has exited, but the unit is still marked as active:

  root@libvirt-hang:~# systemctl status libvirtd.service 
  ● libvirtd.service - Virtualization daemon
   Loaded: loaded 

[Touch-packages] [Bug 2030788] Re: "localectl set-x11-keymap" doesn't work in mantic

[Chad Smith]

This bug is fix released in cloud-init 23.3-0ubuntu1 in Ubuntu mantic.

** Changed in: cloud-init (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  "localectl set-x11-keymap" doesn't work in mantic

Status in cloud-init package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  On the raspi arm64 server image, I used to use cloud-init's keyboard
  module to set my keyboard to GB by default. However, on mantic
  localectl (which the keyboard module uses) is now reporting:

$ localectl set-x11-keymap gb pc105
Setting X11 and console keymaps is not supported in Debian

  So ... how do I get my £ key by default now? Or should this be filed
  against systemd as well?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2030788/+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 2030684] Re: tzname[1] empty after tzset() with env TZ="UTC"

[Nick Rosbrook]

** Changed in: systemd (Ubuntu)
   Status: New => Invalid

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

Title:
  tzname[1] empty after tzset() with env TZ="UTC"

Status in django-mailman3 package in Ubuntu:
  New
Status in php8.2 package in Ubuntu:
  Triaged
Status in postgresql-15 package in Ubuntu:
  Fix Committed
Status in python-django package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Invalid
Status in tzdata package in Ubuntu:
  Fix Committed
Status in tzdata package in Debian:
  Unknown

Bug description:
  The following program prints different output when run with tzdata
  2023c-7ubuntu1 from mantic, versus tzdata 2023c-8ubuntu1 from mantic-
  proposed:

  root@mantic:~# cat bug.c 
  #include 
  #include 
  #include 
  #include 
  #include 

  int main(void) {
  int r;

  r = setenv("TZ", ":UTC", 1);
  if (r < 0) {
  printf("Failed to set TZ env var: %s\n", strerror(errno));
  return 1;
  }

  tzset();

  printf("timezone = %lu, daylight = %d\n", timezone, daylight);
  printf("tzname[0] = %s, tzname[1] = %s\n", tzname[0], tzname[1]);
  }

  root@mantic:~# gcc bug.c
  root@mantic:~# ./a.out 
  timezone = 0, daylight = 0
  tzname[0] = UTC, tzname[1] = UTC
  root@mantic:~# apt-cache policy tzdata
  tzdata:
Installed: 2023c-7ubuntu1
Candidate: 2023c-7ubuntu1
Version table:
   *** 2023c-7ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu mantic/main amd64 Packages
  100 /var/lib/dpkg/status

  If I install tzdata from mantic-proposed, I get different output:

  root@mantic:~# vi /etc/apt/sources.list
  root@mantic:~# apt update && apt install tzdata
  Hit:1 http://archive.ubuntu.com/ubuntu mantic InRelease
  Hit:2 http://security.ubuntu.com/ubuntu mantic-security InRelease
  Get:3 http://archive.ubuntu.com/ubuntu mantic-proposed InRelease [118 kB]
  Hit:4 http://archive.ubuntu.com/ubuntu mantic-updates InRelease
  Hit:5 http://archive.ubuntu.com/ubuntu mantic-backports InRelease
  Get:6 http://archive.ubuntu.com/ubuntu mantic-proposed/main amd64 Packages 
[35.9 kB]
  Get:7 http://archive.ubuntu.com/ubuntu mantic-proposed/main Translation-en 
[14.8 kB]
  Get:8 http://archive.ubuntu.com/ubuntu mantic-proposed/main amd64 DEP-11 
Metadata [2376 B]
  Get:9 http://archive.ubuntu.com/ubuntu mantic-proposed/main amd64 c-n-f 
Metadata [1004 B]
  Get:10 http://archive.ubuntu.com/ubuntu mantic-proposed/restricted amd64 
Packages [15.9 kB]
  Get:11 http://archive.ubuntu.com/ubuntu mantic-proposed/restricted 
Translation-en [3564 B]
  Get:12 http://archive.ubuntu.com/ubuntu mantic-proposed/restricted amd64 
c-n-f Metadata [336 B]
  Fetched 192 kB in 1s (324 kB/s) 
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  72 packages can be upgraded. Run 'apt list --upgradable' to see them.
  root@mantic:~# apt install tzdata=2023c-8ubuntu1
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  The following packages were automatically installed and are no longer 
required:
libefiboot1 libefivar1
  Use 'apt autoremove' to remove them.
  The following packages will be upgraded:
tzdata
  1 upgraded, 0 newly installed, 0 to remove and 72 not upgraded.
  Need to get 269 kB of archives.
  After this operation, 142 kB disk space will be freed.
  Get:1 http://archive.ubuntu.com/ubuntu mantic-proposed/main amd64 tzdata all 
2023c-8ubuntu1 [269 kB]
  Fetched 269 kB in 0s (867 kB/s)
  Preconfiguring packages ...
  (Reading database ... 39935 files and directories currently installed.)
  Preparing to unpack .../tzdata_2023c-8ubuntu1_all.deb ...
  Unpacking tzdata (2023c-8ubuntu1) over (2023c-7ubuntu1) ...
  Setting up tzdata (2023c-8ubuntu1) ...

  Current default time zone: 'Etc/UTC'
  Local time is now:  Mon Aug  7 21:18:35 UTC 2023.
  Universal Time is now:  Mon Aug  7 21:18:35 UTC 2023.
  Run 'dpkg-reconfigure tzdata' if you wish to change it.

  Scanning processes... 


 
  Scanning candidates...


 

  Restarting services...
  Service restarts being deferred:
   systemctl restart systemd-logind.service
   systemctl restart unattended-upgrades.service

  No containers need to be restarted.

  No user sessions are running outdated binaries.

  No VM guests are running outdated hypervisor (qemu) 

[Touch-packages] [Bug 1991829] Re: machinectl read-only does not work

[Nick Rosbrook]

I have verified the fix using systemd-container 249.11-0ubuntu3.10 from
jammy-proposed:

nr@clean-jammy-amd64:~$ apt-cache policy systemd-container
systemd-container:
  Installed: 249.11-0ubuntu3.10
  Candidate: 249.11-0ubuntu3.10
  Version table:
 *** 249.11-0ubuntu3.10 500
500 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages
500 http://security.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages
100 /var/lib/dpkg/status
 249.11-0ubuntu3.9 500
500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
 249.11-0ubuntu3.7 500
500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages
 249.11-0ubuntu3 500
500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
nr@clean-jammy-amd64:~$ machinectl image-status test
test
Type: directory
Path: /var/lib/machines/test
Hostname: ubuntu
  OS: Ubuntu 22.04.3 LTS
  RO: writable
 Created: Mon 2023-08-28 15:44:25 EDT; 6min ago
nr@clean-jammy-amd64:~$ machinectl read-only test
nr@clean-jammy-amd64:~$ machinectl image-status test
test
Type: directory
Path: /var/lib/machines/test
Hostname: ubuntu
  OS: Ubuntu 22.04.3 LTS
  RO: read-only
 Created: Mon 2023-08-28 15:44:25 EDT; 6min ago
nr@clean-jammy-amd64:~$ machinectl read-only test false
nr@clean-jammy-amd64:~$ machinectl image-status test
test
Type: directory
Path: /var/lib/machines/test
Hostname: ubuntu
  OS: Ubuntu 22.04.3 LTS
  RO: writable
 Created: Mon 2023-08-28 15:44:25 EDT; 8min ago


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

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

Title:
  machinectl read-only does not work

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

Bug description:
  [impact]

  machinectl read-only does not work

  [test case]

  On a system where the systemd machines dir is *not* on a btrfs volume
  (e.g. it's on a normal ext4 fs), create an image 'test' and then:

  $ sudo machinectl image-status test
  test
  Type: directory
  Path: /var/lib/machines/test
  Hostname: ubuntu
OS: Ubuntu 20.04.5 LTS
RO: writable
   Created: Wed 2022-10-05 13:41:15 EDT; 34s ago

  $ sudo machinectl read-only test
  Could not mark image read-only: Access denied

  [regression potential]

  failure marking images ro or rw

  [scope]

  this is needed in all releases that include machinectl

  this is fixed upstream by 137d162c42ed858613afc3d7493d08d4ae6d5c1b

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1991829/+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 1977630] Re: machinectl pull-tar/pull-raw Operation not permitted

[Nick Rosbrook]

I verified the fix using systemd-container 249.11-0ubuntu3.10 from
jammy-proposed:

nr@clean-jammy-amd64:~$ apt-cache policy systemd-container
systemd-container:
  Installed: 249.11-0ubuntu3.10
  Candidate: 249.11-0ubuntu3.10
  Version table:
 *** 249.11-0ubuntu3.10 500
500 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages
500 http://security.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages
100 /var/lib/dpkg/status
 249.11-0ubuntu3.9 500
500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
 249.11-0ubuntu3.7 500
500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages
 249.11-0ubuntu3 500
500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
nr@clean-jammy-amd64:~$ machinectl pull-tar --verify=no 
https://cloud-images.ubuntu.com/jammy/current/jammy-server-cloudimg-amd64-root.tar.xz
 test
Enqueued transfer job 1. Press C-c to continue download in background.
Pulling 
'https://cloud-images.ubuntu.com/jammy/current/jammy-server-cloudimg-amd64-root.tar.xz',
 saving as 'test'.
Downloading 390.1M for 
https://cloud-images.ubuntu.com/jammy/current/jammy-server-cloudimg-amd64-root.tar.xz.
HTTP request to 
https://cloud-images.ubuntu.com/jammy/current/jammy-server-cloudimg-amd64-root.nspawn
 failed with code 404.
Settings file could not be retrieved, proceeding without.
Got 1% of 
https://cloud-images.ubuntu.com/jammy/current/jammy-server-cloudimg-amd64-root.tar.xz.
 2min 45s left at 2.3M/s.
Got 2% of 
https://cloud-images.ubuntu.com/jammy/current/jammy-server-cloudimg-amd64-root.tar.xz.
 4min 4s left at 1.5M/s.
Got 3% of 
https://cloud-images.ubuntu.com/jammy/current/jammy-server-cloudimg-amd64-root.tar.xz.
 3min 34s left at 1.7M/s.
Got 4% of 
https://cloud-images.ubuntu.com/jammy/current/jammy-server-cloudimg-amd64-root.tar.xz.
 3min 5s left at 2.0M/s.
Got 5% of 
https://cloud-images.ubuntu.com/jammy/current/jammy-server-cloudimg-amd64-root.tar.xz.
 2min 36s left at 2.3M/s.
Got 6% of 
https://cloud-images.ubuntu.com/jammy/current/jammy-server-cloudimg-amd64-root.tar.xz.
 2min 10s left at 2.7M/s.
Got 9% of 
https://cloud-images.ubuntu.com/jammy/current/jammy-server-cloudimg-amd64-root.tar.xz.
 1min 47s left at 3.3M/s.
Got 11% of 
https://cloud-images.ubuntu.com/jammy/current/jammy-server-cloudimg-amd64-root.tar.xz.
 1min 34s left at 3.6M/s.
Got 13% of 
https://cloud-images.ubuntu.com/jammy/current/jammy-server-cloudimg-amd64-root.tar.xz.
 1min 21s left at 4.1M/s.
Got 16% of 
https://cloud-images.ubuntu.com/jammy/current/jammy-server-cloudimg-amd64-root.tar.xz.
 1min 10s left at 4.6M/s.
Got 18% of 
https://cloud-images.ubuntu.com/jammy/current/jammy-server-cloudimg-amd64-root.tar.xz.
 1min 3s left at 5.0M/s.
Got 21% of 
https://cloud-images.ubuntu.com/jammy/current/jammy-server-cloudimg-amd64-root.tar.xz.
 56s left at 5.4M/s.
Got 24% of 
https://cloud-images.ubuntu.com/jammy/current/jammy-server-cloudimg-amd64-root.tar.xz.
 50s left at 5.7M/s.
Got 27% of 
https://cloud-images.ubuntu.com/jammy/current/jammy-server-cloudimg-amd64-root.tar.xz.
 47s left at 6.0M/s.
Got 29% of 
https://cloud-images.ubuntu.com/jammy/current/jammy-server-cloudimg-amd64-root.tar.xz.
 43s left at 6.2M/s.
Got 32% of 
https://cloud-images.ubuntu.com/jammy/current/jammy-server-cloudimg-amd64-root.tar.xz.
 41s left at 6.3M/s.
Got 34% of 
https://cloud-images.ubuntu.com/jammy/current/jammy-server-cloudimg-amd64-root.tar.xz.
 38s left at 6.5M/s.
Got 37% of 
https://cloud-images.ubuntu.com/jammy/current/jammy-server-cloudimg-amd64-root.tar.xz.
 36s left at 6.6M/s.
Got 39% of 
https://cloud-images.ubuntu.com/jammy/current/jammy-server-cloudimg-amd64-root.tar.xz.
 34s left at 6.7M/s.
Got 41% of 
https://cloud-images.ubuntu.com/jammy/current/jammy-server-cloudimg-amd64-root.tar.xz.
 33s left at 6.7M/s.
Got 43% of 
https://cloud-images.ubuntu.com/jammy/current/jammy-server-cloudimg-amd64-root.tar.xz.
 32s left at 6.8M/s.
Got 46% of 
https://cloud-images.ubuntu.com/jammy/current/jammy-server-cloudimg-amd64-root.tar.xz.
 30s left at 6.9M/s.
Got 49% of 
https://cloud-images.ubuntu.com/jammy/current/jammy-server-cloudimg-amd64-root.tar.xz.
 27s left at 7.1M/s.
Got 53% of 
https://cloud-images.ubuntu.com/jammy/current/jammy-server-cloudimg-amd64-root.tar.xz.
 23s left at 7.5M/s.
Got 59% of 
https://cloud-images.ubuntu.com/jammy/current/jammy-server-cloudimg-amd64-root.tar.xz.
 19s left at 8.0M/s.
Got 65% of 
https://cloud-images.ubuntu.com/jammy/current/jammy-server-cloudimg-amd64-root.tar.xz.
 15s left at 8.6M/s.
Got 71% of 
https://cloud-images.ubuntu.com/jammy/current/jammy-server-cloudimg-amd64-root.tar.xz.
 12s left at 9.1M/s.
Got 78% of 
https://cloud-images.ubuntu.com/jammy/current/jammy-server-cloudimg-amd64-root.tar.xz.
 8s left at 9.6M/s.
Got 83% of 
https://cloud-images.ubuntu.com/jammy/current/jammy-server-cloudimg-amd64-root.tar.xz.
 6s left at 9.9M/s.
Got 90% of 

[Touch-packages] [Bug 1999275] Re: systemd-binfmt.service fails in tests-in-lxd

[Nick Rosbrook]

I have verified the fix using systemd 249.11-0ubuntu3.10 from jammy-
proposed:

1. Verified that boot-and-services is passing on all arches for
249.11-0ubuntu3.10: https://autopkgtest.ubuntu.com/packages/systemd.

2. Manual test:

root@jammy:~# systemd-detect-virt 
lxc
root@jammy:~# apt-cache policy systemd
systemd:
  Installed: 249.11-0ubuntu3.10
  Candidate: 249.11-0ubuntu3.10
  Version table:
 *** 249.11-0ubuntu3.10 500
500 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages
500 http://security.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages
100 /var/lib/dpkg/status
 249.11-0ubuntu3.9 500
500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
 249.11-0ubuntu3.7 500
500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages
 249.11-0ubuntu3 500
500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
root@jammy:~# systemctl status systemd-binfmt.service
● systemd-binfmt.service - Set Up Additional Binary Formats
 Loaded: loaded (/lib/systemd/system/systemd-binfmt.service; static)
Drop-In: /etc/systemd/system/systemd-binfmt.service.d
 └─override.conf
 Active: active (exited) since Mon 2023-08-28 19:22:15 UTC; 13s ago
   Docs: man:systemd-binfmt.service(8)
 man:binfmt.d(5)
 https://www.kernel.org/doc/html/latest/admin-guide/binfmt-misc.html
 https://www.freedesktop.org/wiki/Software/systemd/APIFileSystems
Process: 115 ExecStart=/lib/systemd/systemd-binfmt (code=exited, 
status=0/SUCCESS)
   Main PID: 115 (code=exited, status=0/SUCCESS)
CPU: 4ms

Aug 28 19:22:15 jammy systemd[1]: Starting Set Up Additional Binary Formats...
Aug 28 19:22:15 jammy systemd[1]: Finished Set Up Additional Binary Formats.
root@jammy:~# journalctl -t systemd-binfmt -b
Aug 28 19:22:15 jammy systemd-binfmt[115]: /proc/sys/fs/binfmt_misc is not 
mounted in read-write mode, skipping.

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

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

Title:
  systemd-binfmt.service fails in tests-in-lxd

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

Bug description:
  [Impact]

  systemd-binfmt.service fails in LXD because access
  /proc/sys/binfmt_misc is prevented by LXD apparmor config. This causes
  our autopkgtest to fail, and leaves systemd-binfmt.service in a failed
  state:

  root@jammy:~# systemctl status systemd-binfmt
  × systemd-binfmt.service - Set Up Additional Binary Formats
   Loaded: loaded (/lib/systemd/system/systemd-binfmt.service; static)
   Active: failed (Result: exit-code) since Thu 2023-08-17 18:54:18 UTC; 
1min 12s ago
 Docs: man:systemd-binfmt.service(8)
   man:binfmt.d(5)
   
https://www.kernel.org/doc/html/latest/admin-guide/binfmt-misc.html
   https://www.freedesktop.org/wiki/Software/systemd/APIFileSystems
 Main PID: 118 (code=exited, status=1/FAILURE)
  CPU: 5ms

  Aug 17 18:54:18 jammy systemd[1]: Starting Set Up Additional Binary Formats...
  Aug 17 18:54:18 jammy systemd-binfmt[118]: Failed to add binary format: 
Permission denied
  Aug 17 18:54:18 jammy systemd[1]: systemd-binfmt.service: Main process 
exited, code=exited, status=1/FAILURE
  Aug 17 18:54:18 jammy systemd[1]: systemd-binfmt.service: Failed with result 
'exit-code'.
  Aug 17 18:54:18 jammy systemd[1]: Failed to start Set Up Additional Binary 
Formats.

  [Test Plan]

  1. test_no_failed from boot-and-services should pass.
  2. Manual test:

  * Start a Jammy LXD container:

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

  * In the container, check systemd-binfmt.service:
  root@jammy:~# systemctl status systemd-binfmt
  ● systemd-binfmt.service - Set Up Additional Binary Formats
   Loaded: loaded (/lib/systemd/system/systemd-binfmt.service; static)
  Drop-In: /etc/systemd/system/systemd-binfmt.service.d
   └─override.conf
   Active: active (exited) since Thu 2023-08-17 19:01:00 UTC; 2min 27s ago
 Docs: man:systemd-binfmt.service(8)
   man:binfmt.d(5)
   
https://www.kernel.org/doc/html/latest/admin-guide/binfmt-misc.html
   https://www.freedesktop.org/wiki/Software/systemd/APIFileSystems
 Main PID: 122 (code=exited, status=0/SUCCESS)
  CPU: 5ms

  Aug 17 19:01:00 jammy systemd[1]: Starting Set Up Additional Binary Formats...
  Aug 17 19:01:00 jammy systemd[1]: Finished Set Up Additional Binary Formats.
  root@jammy:~# journalctl -t systemd-binfmt -b
  Aug 17 19:01:00 jammy systemd-binfmt[122]: /proc/sys/fs/binfmt_misc is not 
mounted in read-write mode, skipping.

  [ Where problems could 

[Touch-packages] [Bug 1835315] Re: Vulkan funcionality broken when mesa is compiled with LLVM 8 in some programs

[Luca Osvaldo Mastromatteo]

Hello, sadly I can not reproduce as I don't have the hardware anymore, I
suppose if no one else reported the issue it is solved.

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

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

Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu version: 18.04.2 LTS

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

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

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

  Using the AMDVLK vulkan driver workarounds the problem too.

  The program I have personally tested is RPCS3


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

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


-- 
Mailing list: https://launchpad.net/~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 1858199] Re: bugs in libvdpau_radeonsi.so and amdgpu(or radeon) driver freeze the system

[Oibaf]

smzhou, ubuntu 19.10 is no longer supported, can you try with a newer
Ubuntu release?


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

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

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

Status in mesa package in Ubuntu:
  Incomplete

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

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

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

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

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

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


-- 
Mailing list: https://launchpad.net/~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 1835315] Re: Vulkan funcionality broken when mesa is compiled with LLVM 8 in some programs

[Oibaf]

Luca, Ubuntu 18.04 now has mesa 20.0.8-0ubuntu1~18.04.1, is the issue
still reproducible?

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

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

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

Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu version: 18.04.2 LTS

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

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

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

  Using the AMDVLK vulkan driver workarounds the problem too.

  The program I have personally tested is RPCS3


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

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


-- 
Mailing list: https://launchpad.net/~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

[georgebenzy]

It seems like you're encountering an issue with the avahi-daemon and
Zeroconf hostname changes after your ISP changes your IP address. The
behavior you described could be related to avahi-daemon reacting to the
IP address change, resulting in a change of the Zeroconf hostname. To
address this issue, you might need to delve into the configuration of
avahi-daemon, possibly fine-tuning its behavior when the IP address
changes https://gstcalculatorau.com/

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

[Touch-packages] [Bug 1882466] Re: mythtv frontend crash when calling glClear in iris driver

[Oibaf]

Ken, Ubuntu 20.04 now has mesa 21.2.6-0ubuntu0.1~20.04.2 , can you try
it, is this still an issue for you?


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

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

Title:
  mythtv frontend crash when calling glClear in iris driver

Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  on startup, mythfrontend crashes repeatedly when calling glClear - the 
following traceback:
  Core was generated by `/usr/bin/mythfrontend.real'.
  Program terminated with signal SIGSEGV, Segmentation fault.
  #0  0x7f9495ca0838 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
  [Current thread is 1 (Thread 0x7f9551e59940 (LWP 4164))]
  (gdb) bt
  #0  0x7f9495ca0838 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
  #1  0x7f9495ca2ebf in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
  #2  0x7f9495e65de4 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
  #3  0x7f9495c7ce5d in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
  #4  0x7f9495c7da95 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
  #5  0x7f94952bc774 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
  #6  0x7f955f79e713 in QOpenGLFunctions::glClear (this=0x555cb36e8160, 
  mask=16384)
  at /usr/include/x86_64-linux-gnu/qt5/QtGui/qopenglfunctions.h:628
  #7  0x7f955f798090 in MythRenderOpenGL::ClearFramebuffer (
  this=0x555cb36e8150) at opengl/mythrenderopengl.cpp:801
  #8  0x7f955f78a3f2 in MythOpenGLPainter::Begin (this=0x555cb398dac0, 
  Parent=0x555cb399d1d0) at opengl/mythpainteropengl.cpp:136

  I can work around this problem with this:
  export MESA_LOADER_DRIVER_OVERRIDE=i965
  (then running mythfrontend works fine)

  sorry for the lack of debug symbols in iris_dri.so
  if there is a .deb around with a debug version i can generate the traceback 
again
  not sure if the problem belongs to iris_dri.so or to mythfrontend but I put 
it here due to the workaround.

  
  $ lsb_release -rd
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  $ apt-cache policy libgl1-mesa-dri
  libgl1-mesa-dri:
Installed: 20.0.4-2ubuntu1
Candidate: 20.0.4-2ubuntu1
Version table:
   *** 20.0.4-2ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

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

[Oibaf]

Likely fixed since the, can you try with a newer Ubuntu release?

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

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

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

Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  After running

  $ sudo apt full-upgrade

  Could be contributing factor to Chromium crashing tabs randomly.

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

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


-- 
Mailing list: https://launchpad.net/~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 1889052] Re: 20.10: vlc crashes with seg fault when a video should be played

[Oibaf]

DarkTrick, Ubuntu 20.04 now has mesa 21.2.6-0ubuntu0.1~20.04.2 , can you
try it, is this still an issue for you?

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

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

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

Status in mesa package in Ubuntu:
  Incomplete

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

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: vlc 3.0.9.2-1
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Mon Jul 27 17:27:42 2020
  SourcePackage: vlc
  UpgradeStatus: Upgraded to focal on 2020-07-24 (3 days ago)

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


-- 
Mailing list: https://launchpad.net/~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 1892985] Re: package libegl-mesa0 20.0.8-0ubuntu1~18.04.1 [modified: usr/share/glvnd/egl_vendor.d/50_mesa.json] failed to install/upgrade: trying to overwrite shared '/usr/share/

[Oibaf]

Likely fixed, can you try with a newer Ubuntu release?

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

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

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

Status in mesa package in Ubuntu:
  Incomplete

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

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

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


-- 
Mailing list: https://launchpad.net/~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 1931045] Re: FFMPEG silently falls back to software encoding on AMD GPU

[Oibaf]

Norbert, it looks like you were using Ubuntu 21.10, which is no longer
supported. Can you try with a newer Ubuntu release?

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

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

Title:
  FFMPEG silently falls back to software encoding on AMD GPU

Status in Mesa:
  New
Status in ffmpeg package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  FFMPEG hardware encoding fails on AMD hardware:

  Passing -hwaccel vaapi flag as per command below:

  Command used was:

  ffmpeg -hwaccel vaapi -hwaccel_device /dev/dri/renderD128
  -hwaccel_output_format vaapi -ss 15 -i input.mp4 -t 25 -c:v h264_vaapi
  -global_quality 15 -c:a copy -map 0 output.mkv

  
  Will silently fail and transcoding will be done on CPU silently when using on 
AMD GPU.

  The only sign that something is wrong is this WARNING:

  [hevc_vaapi @ 0x55f2ca003e80] Driver does not support some wanted
  packed headers (wanted 0xd, found 0x1).

  and for h264:

  Press [q] to stop, [?] for help
  [h264_vaapi @ 0x55762dd4de80] Driver does not support some wanted packed 
headers (wanted 0xd, found 0x1).

  
  During transcode operation CPU usage is high, and GPU usage is zero. FFPROBE 
on OUTPUT.MKV reports that encoder used was software.

  My syste:  Thinkpad T14s (AMD Ryzen7) Ubuntu Mate 21.04 (5.11)

  bash $ sudo inxi -x -G
  Graphics:  Device-1: Advanced Micro Devices [AMD/ATI] Renoir vendor: Lenovo 
driver: amdgpu v: kernel
     bus ID: 07:00.0
     Device-2: Chicony Integrated Camera type: USB driver: uvcvideo bus 
ID: 2-2:2
     Display: server: X.Org 1.20.11 driver: loaded: amdgpu,ati 
unloaded: fbdev,modesetting,vesa
     resolution: 1920x1080~60Hz
     OpenGL: renderer: AMD RENOIR (DRM 3.40.0 5.11.0-18-generic LLVM 
11.0.1) v: 4.6 Mesa 21.0.1
     direct render: Yes

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1931045/+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 1989964] Re: Segmentation fault crocus_dri.so (X server dies)

[Oibaf]

Simon, Ubuntu 22.04 now has mesa 23.0.4-0ubuntu1~22.04.1, can you try
it, is this still an issue for you?

** Also affects: mesa via
   https://gitlab.freedesktop.org/mesa/mesa/-/issues/7626
   Importance: Unknown
   Status: Unknown

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

Title:
  Segmentation fault crocus_dri.so (X server dies)

Status in Mesa:
  Unknown
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  The desktop session is running for 0 or more days. Suddenly the X
  server dies, and login screen reappears.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
  Uname: Linux 5.15.0-47-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: MATE
  Date: Fri Sep 16 14:45:54 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [103c:18e4]
  MachineType: Hewlett-Packard HP EliteDesk 800 G1 TWR
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-47-generic 
root=/dev/mapper/sun--vg-root ro
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/16/2015
  dmi.bios.release: 2.59
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L01 v02.59
  dmi.board.name: 18E4
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL01v02.59:bd03/16/2015:br2.59:svnHewlett-Packard:pnHPEliteDesk800G1TWR:pvr:rvnHewlett-Packard:rn18E4:rvr:cvnHewlett-Packard:ct6:cvr:skuC8N27AV:
  dmi.product.family: 103C_53307F G=D
  dmi.product.name: HP EliteDesk 800 G1 TWR
  dmi.product.sku: C8N27AV
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.1
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1989964/+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 1987792] Re: Totem and VLC crash when playing dvd with VAAPI radeon mesa drivers

[Oibaf]

Michel, Ubuntu 22.04 now has mesa 23.0.4-0ubuntu1~22.04.1, can you try
it, is this still an issue for you?

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

Title:
  Totem and VLC crash when playing dvd with VAAPI radeon mesa drivers

Status in mesa package in Ubuntu:
  New

Bug description:
  Sony laptop with AMD RV710

  Try to play a DVD with Vaapi mesa drivers installed

  ALl players crash , example with VLC (  Works great without VAAPI )

  libva info: VA-API version 1.14.0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/r600_drv_video.so
  libva info: Found init function __vaDriverInit_1_14
  libva info: va_openDriver() returns 0
  [7fd5d8085d50] main generic debug: using glconv module "glconv_vaapi_drm"
  [7fd5d8001610] main vout display debug: using vout display module "gl"
  [7fd5d4039c20] main window debug: resized to 768x576
  [7fd5d8001610] main vout display debug: VoutDisplayEvent 'resize' 768x576
  [7fd5d4028010] main video output debug: original format sz 720x576, of 
(0,0), vsz 720x576, 4cc VAOP, sar 16:15, msk r0x0 g0x0 b0x0
  [7fd5d4029610] main spu text debug: removing module "freetype"
  [7fd5d4072b40] main spu text debug: looking for text renderer module 
matching "any": 2 candidates
  [7fd5d4072b40] freetype spu text debug: Building font databases.
  [5601ed37aed0] qt interface debug: Logical video size: 768x576
  [7fd5d4039c20] main window debug: resized to 768x576
  [7fd5d8001610] main vout display debug: VoutDisplayEvent 'resize' 768x576
  [7fd5d4072b40] freetype spu text debug: Took -23713 microseconds
  [7fd5d4072b40] main spu text debug: using text renderer module "freetype"
  [7fd5d409d080] main generic debug: looking for hw decoder module matching 
"vaapi": 3 candidates
  [7fd5d409d080] main generic debug: using hw decoder module "vaapi"
  [7fd5d004efb0] avcodec decoder: Using Mesa Gallium driver 22.0.5 for AMD 
RV710 (DRM 2.50.0 / 5.15.0-46-generic, LLVM 13.0.1) for hardware decoding
  [mpeg2video @ 0x7fd5d4087d80] Format vaapi_vld chosen by get_format().
  [mpeg2video @ 0x7fd5d4087d80] Format vaapi_vld requires hwaccel 
initialisation.
  [mpeg2video @ 0x7fd5d4087d80] Using deprecated struct vaapi_context in decode.
  [mpeg2video @ 0x7fd5d4087d80] Using user-supplied decoder context: 0x15/0x16.
  [mpeg2video @ 0x7fd5d4087d80] Param buffer (type 0, 40 bytes) is 0x17.
  [mpeg2video @ 0x7fd5d4087d80] Param buffer (type 1, 288 bytes) is 0x18.
  [mpeg2video @ 0x7fd5d4087d80] Slice 0 param buffer (48 bytes) is 0x19.
  [mpeg2video @ 0x7fd5d4087d80] Slice 0 data buffer (176 bytes) is 0x1a.
  [mpeg2video @ 0x7fd5d4087d80] Slice 1 param buffer (48 bytes) is 0x1b.
  [mpeg2video @ 0x7fd5d4087d80] Slice 1 data buffer (175 bytes) is 0x1c.
  [mpeg2video @ 0x7fd5d4087d80] Slice 2 param buffer (48 bytes) is 0x1d.
  [mpeg2video @ 0x7fd5d4087d80] Slice 2 data buffer (175 bytes) is 0x1e.
  [mpeg2video @ 0x7fd5d4087d80] Slice 3 param buffer (48 bytes) is 0x1f.
  [mpeg2video @ 0x7fd5d4087d80] Slice 3 data buffer (175 bytes) is 0x20.
  [mpeg2video @ 0x7fd5d4087d80] Slice 4 param buffer (48 bytes) is 0x21.
  [mpeg2video @ 0x7fd5d4087d80] Slice 4 data buffer (175 bytes) is 0x22.
  [mpeg2video @ 0x7fd5d4087d80] Slice 5 param buffer (48 bytes) is 0x23.
  [mpeg2video @ 0x7fd5d4087d80] Slice 5 data buffer (175 bytes) is 0x24.
  [mpeg2video @ 0x7fd5d4087d80] Slice 6 param buffer (48 bytes) is 0x25.
  [mpeg2video @ 0x7fd5d4087d80] Slice 6 data buffer (175 bytes) is 0x26.
  [mpeg2video @ 0x7fd5d4087d80] Slice 7 param buffer (48 bytes) is 0x27.
  [mpeg2video @ 0x7fd5d4087d80] Slice 7 data buffer (175 bytes) is 0x28.
  [mpeg2video @ 0x7fd5d4087d80] Slice 8 param buffer (48 bytes) is 0x29.
  [mpeg2video @ 0x7fd5d4087d80] Slice 8 data buffer (175 bytes) is 0x2a.
  [mpeg2video @ 0x7fd5d4087d80] Slice 9 param buffer (48 bytes) is 0x2b.
  [mpeg2video @ 0x7fd5d4087d80] Slice 9 data buffer (175 bytes) is 0x2c.
  [mpeg2video @ 0x7fd5d4087d80] Slice 10 param buffer (48 bytes) is 0x2d.
  [mpeg2video @ 0x7fd5d4087d80] Slice 10 data buffer (175 bytes) is 0x2e.
  [mpeg2video @ 0x7fd5d4087d80] Slice 11 param buffer (48 bytes) is 0x2f.
  [mpeg2video @ 0x7fd5d4087d80] Slice 11 data buffer (175 bytes) is 0x30.
  [mpeg2video @ 0x7fd5d4087d80] Slice 12 param buffer (48 bytes) is 0x31.
  [mpeg2video @ 0x7fd5d4087d80] Slice 12 data buffer (175 bytes) is 0x32.
  [mpeg2video @ 0x7fd5d4087d80] Slice 13 param buffer (48 bytes) is 0x33.
  [mpeg2video @ 0x7fd5d4087d80] Slice 13 data buffer (175 bytes) is 0x34.
  [mpeg2video @ 0x7fd5d4087d80] Slice 14 param buffer (48 bytes) is 0x35.
  [mpeg2video @ 0x7fd5d4087d80] Slice 14 data buffer (175 bytes) is 0x36.
  [mpeg2video @ 0x7fd5d4087d80] Slice 15 param buffer (48 bytes) is 0x37.
  [mpeg2video @ 0x7fd5d4087d80] Slice 15 data buffer (571 bytes) is 0x38.
  [mpeg2video @ 0x7fd5d4087d80] 

[Touch-packages] [Bug 1965608] Re: Crash in gbm_dri_bo_import on ASPEED + AMDGPU system

[Oibaf]

Dana, Ubuntu 21.10 is no longer supported, can you try with a newer
Ubuntu if the problem is still reproducible?

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

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

Title:
  Crash in gbm_dri_bo_import on ASPEED + AMDGPU system

Status in mesa package in Ubuntu:
  Incomplete

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

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

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

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

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

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

[Touch-packages] [Bug 1972131] Re: occasional flashing screen since upgrade to 22.04

[Oibaf]

Kent, Ubuntu 22.04 now has mesa 23.0.4-0ubuntu1~22.04.1, can you try it,
is this still an issue for you?

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

Title:
  occasional flashing screen since upgrade to 22.04

Status in mesa package in Ubuntu:
  New

Bug description:
  Since upgrading to 22.04 I often experienced a flashing screen. I have
  noticed the issue in particular when I have an onboard keyboard
  displayed. Hiding the onboard keyboard and then showing the keyboard
  seems to resolve the flashing problem

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-release-upgrader-core 1:22.04.10
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Sun May  8 17:20:13 2022
  InstallationDate: Installed on 2020-07-18 (659 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: Upgraded to jammy on 2022-04-29 (9 days ago)
  VarLogDistupgradeTermlog:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1972131/+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 1982218] Re: wait-online does not correctly identify managed links

[Nick Rosbrook]

I have verified the fix using systemd 252.5-2ubuntu3.1 from lunar-
proposed:

The VM and test networks are already configured on my system:

nr@six:/t/tmp.jTS3wdPdT3$ virsh list 
 Id   NameState
---
 9clean-lunar-amd64   running

nr@six:/t/tmp.jTS3wdPdT3$ virsh net-list 
 Name  StateAutostart   Persistent

 default   active   yes yes
 no-dhcp   active   no  no

nr@six:/t/tmp.jTS3wdPdT3$ virsh net-dumpxml --network default 

  default
  04260896-2701-422d-84e0-8e0df1122db3
  

  

  
  
  
  

  

  


nr@six:/t/tmp.jTS3wdPdT3$ virsh net-dumpxml --network no-dhcp 

  no-dhcp
  2c047740-caab-4c90-8421-70da6732a759
  

  

  
  
  
  
  


Running the test case:

(Host)

nr@six:/t/tmp.jTS3wdPdT3$ virsh detach-interface clean-lunar-amd64 network
Interface detached successfully

(VM)

root@clean-lunar-amd64:/home/nr# apt-cache policy systemd
systemd:
  Installed: 252.5-2ubuntu3.1
  Candidate: 252.5-2ubuntu3.1
  Version table:
 *** 252.5-2ubuntu3.1 500
500 http://security.ubuntu.com/ubuntu lunar-proposed/main amd64 Packages
500 http://archive.ubuntu.com/ubuntu lunar-proposed/main amd64 Packages
100 /var/lib/dpkg/status
 252.5-2ubuntu3 500
500 http://archive.ubuntu.com/ubuntu lunar/main amd64 Packages
root@clean-lunar-amd64:/home/nr# cat > /etc/systemd/network/10-dhcp.network << 
EOF
[Match]
Name=en*

[Network]
DHCP=yes
EOF
root@clean-lunar-amd64:/home/nr# systemctl restart systemd-networkd

(Host)

nr@six:/t/tmp.jTS3wdPdT3$ virsh attach-interface clean-lunar-amd64 network 
no-dhcp
Interface attached successfully

(VM)

root@clean-lunar-amd64:/home/nr# networkctl 
IDX LINK TYPE OPERATIONAL SETUP  
  1 lo   loopback carrier unmanaged
  5 ens3 etherdegradedconfiguring

2 links listed.
root@clean-lunar-amd64:/home/nr# /lib/systemd/systemd-networkd-wait-online 
--any --timeout=10
Timeout occurred while waiting for network connectivity.
root@clean-lunar-amd64:/home/nr# networkctl 
IDX LINK TYPE OPERATIONAL SETUP  
  1 lo   loopback carrier unmanaged
  5 ens3 etherdegradedconfiguring

2 links listed.

(Host)

nr@six:/t/tmp.jTS3wdPdT3$ virsh attach-interface clean-lunar-amd64 network 
default
Interface attached successfully

(VM)

root@clean-lunar-amd64:/home/nr# /lib/systemd/systemd-networkd-wait-online 
--any --timeout=0
root@clean-lunar-amd64:/home/nr# echo $?
0
root@clean-lunar-amd64:/home/nr# networkctl 
IDX LINK TYPE OPERATIONAL SETUP  
  1 lo   loopback carrier unmanaged
  5 ens3 etherdegradedconfiguring
  6 ens9 etherroutableconfigured 

3 links listed.


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

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

Title:
  wait-online does not correctly identify managed links

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

Bug description:
  [Impact]

  systemd-networkd-wait-online will exit prematurely when the --any flag
  is passed, due to an incorrect patch in Ubuntu that is supposed to
  make systemd-networkd-wait-online exit when *no* links are managed.

  [Test Plan]

  This test uses a VM managed by libvirt. In this scenario we have the
  "default" network which provides DHCP to the VM, and the "no-dhcp"
  network which does not provide DHCP.

  To setup the VM (this assumes Jammy, but the same steps apply for
  Lunar using appropriate names and install media):

  1. Define the default and no-dhcp networks:

  $ cat > /tmp/net-default.xml << EOF
  
default
04260896-2701-422d-84e0-8e0df1122db3




  

  

  
  $ virsh net-create --file /tmp/net-default.xml
  $ cat > /tmp/net-default.xml << EOF
  
no-dhcp
2c047740-caab-4c90-8421-70da6732a759
  





  
  $ virsh net-create --file /tmp/net-no-dhcp.xml
  $ virsh net-start --network default
  $ virst net-start --network no-dhcp

  2. Create the VM using virt-install:

  virt-install \
  --connect=qemu:///system \
  --name=jammy \
  --arch=x86_64 \
  --cpu=host-passthrough \
  --ram=4096 \
  --vcpus=1 \
  
--disk=path=/var/lib/libvirt/images/jammy.qcow2,size=24,format=qcow2,sparse=true,bus=virtio
 \
  --virt-type=kvm \
  --accelerate \
  --hvm \
  --cdrom=/tmp/ubuntu-22.04.2-live-server-amd64.iso \
  --os-type=linux \
  --os-variant=generic \
  --graphics=spice \
  --input=tablet \
  --network=network=default,model=virtio \
  --video=qxl \
  --noreboot

  3. Complete the installation steps. Reboot the VM.

  Run the test:

  1. Detach the network interface so that the test 

[Touch-packages] [Bug 2031352] Re: Ubuntu 22.04.3 LTS stuck on power-off/reboot screen

[Juerg Haefliger]

@ianrussel your log shows:

Aug 22 09:57:02 ianrussel kernel: nouveau :01:00.0: fb: VPR locked, but no 
scrubber binary!
Aug 22 09:57:02 ianrussel kernel: BUG: kernel NULL pointer dereference, 
address: 
Aug 22 09:57:02 ianrussel kernel: #PF: supervisor instruction fetch in kernel 
mode
Aug 22 09:57:02 ianrussel kernel: #PF: error_code(0x0010) - not-present page
Aug 22 09:57:02 ianrussel kernel: PGD 0 P4D 0 
Aug 22 09:57:02 ianrussel kernel: Oops: 0010 [#1] PREEMPT SMP NOPTI
Aug 22 09:57:02 ianrussel kernel: CPU: 14 PID: 479 Comm: systemd-udevd Not 
tainted 6.2.0-26-generic #26~22.04.1-Ubuntu
Aug 22 09:57:02 ianrussel kernel: Hardware name: Dell Inc. XPS 15 9510/01V4T3, 
BIOS 1.22.0 07/13/2023
Aug 22 09:57:02 ianrussel kernel: RIP: 0010:0x0
Aug 22 09:57:02 ianrussel kernel: Code: Unable to access opcode bytes at 
0xffd6.
Aug 22 09:57:02 ianrussel kernel: RSP: 0018:b3a381f4b658 EFLAGS: 00010246
Aug 22 09:57:02 ianrussel kernel: RAX:  RBX: 9d14de9198b0 
RCX: 
Aug 22 09:57:02 ianrussel kernel: RDX: 9d14de9198d8 RSI: 9d14de9198c8 
RDI: 9d14de919800
Aug 22 09:57:02 ianrussel kernel: RBP: b3a381f4b6b8 R08: 9d14de9198b0 
R09: 
Aug 22 09:57:02 ianrussel kernel: R10:  R11:  
R12: 9d14de9198c8
Aug 22 09:57:02 ianrussel kernel: R13:  R14: 9d14de9198b0 
R15: 9d14de919808
Aug 22 09:57:02 ianrussel kernel: FS:  7f13d5a4d8c0() 
GS:9d183f78() knlGS:
Aug 22 09:57:02 ianrussel kernel: CS:  0010 DS:  ES:  CR0: 
80050033
Aug 22 09:57:02 ianrussel kernel: CR2: ffd6 CR3: 000117606004 
CR4: 00770ee0
Aug 22 09:57:02 ianrussel kernel: PKRU: 5554
Aug 22 09:57:02 ianrussel kernel: Call Trace:
Aug 22 09:57:02 ianrussel kernel:  
Aug 22 09:57:02 ianrussel kernel:  nvkm_acr_oneinit+0x502/0x710 [nouveau]
Aug 22 09:57:02 ianrussel kernel:  nvkm_subdev_oneinit_+0x4d/0x120 [nouveau]
Aug 22 09:57:02 ianrussel kernel:  nvkm_subdev_init_+0x3e/0x150 [nouveau]
Aug 22 09:57:02 ianrussel kernel:  nvkm_subdev_init+0x55/0x80 [nouveau]
Aug 22 09:57:02 ianrussel kernel:  nvkm_device_init+0x17b/0x300 [nouveau]
Aug 22 09:57:02 ianrussel kernel:  nvkm_udevice_init+0x50/0x60 [nouveau]
Aug 22 09:57:02 ianrussel kernel:  nvkm_object_init+0x40/0x210 [nouveau]
Aug 22 09:57:02 ianrussel kernel:  nvkm_ioctl_new+0x196/0x2c0 [nouveau]
Aug 22 09:57:02 ianrussel kernel:  ? __pfx_nvkm_client_child_new+0x10/0x10 
[nouveau]
Aug 22 09:57:02 ianrussel kernel:  ? __pfx_nvkm_udevice_new+0x10/0x10 [nouveau]
Aug 22 09:57:02 ianrussel kernel:  nvkm_ioctl+0x12e/0x290 [nouveau]
Aug 22 09:57:02 ianrussel kernel:  nvkm_client_ioctl+0xe/0x20 [nouveau]
Aug 22 09:57:02 ianrussel kernel:  nvif_object_ctor+0x136/0x1a0 [nouveau]
Aug 22 09:57:02 ianrussel kernel:  nvif_device_ctor+0x24/0x90 [nouveau]
Aug 22 09:57:02 ianrussel kernel:  nouveau_cli_init+0x161/0x5e0 [nouveau]
Aug 22 09:57:02 ianrussel kernel:  nouveau_drm_device_init+0x67/0x310 [nouveau]
Aug 22 09:57:02 ianrussel kernel:  nouveau_drm_probe+0x131/0x280 [nouveau]
Aug 22 09:57:02 ianrussel kernel:  local_pci_probe+0x48/0xb0
Aug 22 09:57:02 ianrussel kernel:  pci_call_probe+0x55/0x190
Aug 22 09:57:02 ianrussel kernel:  pci_device_probe+0x84/0x120
Aug 22 09:57:02 ianrussel kernel:  really_probe+0x1ea/0x450
Aug 22 09:57:02 ianrussel kernel:  __driver_probe_device+0x8a/0x1a0
Aug 22 09:57:02 ianrussel kernel:  driver_probe_device+0x23/0xd0
Aug 22 09:57:02 ianrussel kernel:  __driver_attach+0x10f/0x220
Aug 22 09:57:02 ianrussel kernel:  ? __pfx___driver_attach+0x10/0x10
Aug 22 09:57:02 ianrussel kernel:  bus_for_each_dev+0x80/0xe0
Aug 22 09:57:02 ianrussel kernel:  driver_attach+0x1e/0x30
Aug 22 09:57:02 ianrussel kernel:  bus_add_driver+0x152/0x250
Aug 22 09:57:02 ianrussel kernel:  driver_register+0x83/0x160
Aug 22 09:57:02 ianrussel kernel:  ? __pfx_init_module+0x10/0x10 [nouveau]
Aug 22 09:57:02 ianrussel kernel:  __pci_register_driver+0x68/0x80
Aug 22 09:57:02 ianrussel kernel:  nouveau_drm_init+0x177/0xff0 [nouveau]
Aug 22 09:57:02 ianrussel kernel:  do_one_initcall+0x46/0x240
Aug 22 09:57:02 ianrussel kernel:  ? kmalloc_trace+0x2a/0xb0
Aug 22 09:57:02 ianrussel kernel:  do_init_module+0x52/0x240
Aug 22 09:57:02 ianrussel kernel:  load_module+0xb96/0xd60
Aug 22 09:57:02 ianrussel kernel:  ? security_kernel_post_read_file+0x5c/0x80
Aug 22 09:57:02 ianrussel kernel:  ? kernel_read_file+0x25c/0x2b0
Aug 22 09:57:02 ianrussel kernel:  __do_sys_finit_module+0xcc/0x150
Aug 22 09:57:02 ianrussel kernel:  ? __do_sys_finit_module+0xcc/0x150
Aug 22 09:57:02 ianrussel kernel:  __x64_sys_finit_module+0x18/0x30
Aug 22 09:57:02 ianrussel kernel:  do_syscall_64+0x59/0x90
Aug 22 09:57:02 ianrussel kernel:  ? do_syscall_64+0x69/0x90
Aug 22 09:57:02 ianrussel kernel:  ? exit_to_user_mode_prepare+0xaf/0xd0
Aug 22 09:57:02 ianrussel kernel:  ? syscall_exit_to_user_mode+0x2a/0x50
Aug 22 09:57:02 

[Touch-packages] [Bug 1982218] Re: wait-online does not correctly identify managed links

[Nick Rosbrook]

I have verified the fix using systemd 249.11-0ubuntu3.10 from jammy-
proposed:

The VM and test networks are already configured on my system:

nr@six:/t/tmp.jTS3wdPdT3$ virsh list 
 Id   NameState
---
 8clean-jammy-amd64   running

nr@six:/t/tmp.jTS3wdPdT3$ virsh net-list 
 Name  StateAutostart   Persistent

 default   active   yes yes
 no-dhcp   active   no  no

nr@six:/t/tmp.jTS3wdPdT3$ virsh net-dumpxml --network default 

  default
  04260896-2701-422d-84e0-8e0df1122db3
  

  

  
  
  
  

  

  


nr@six:/t/tmp.jTS3wdPdT3$ virsh net-dumpxml --network no-dhcp 

  no-dhcp
  2c047740-caab-4c90-8421-70da6732a759
  

  

  
  
  
  
  


Running the test case:

(Host)

nr@six:/t/tmp.jTS3wdPdT3$ virsh detach-interface clean-jammy-amd64 network
Interface detached successfully

(VM)

root@clean-jammy-amd64:/home/nr# apt-cache policy systemd
systemd:
  Installed: 249.11-0ubuntu3.10
  Candidate: 249.11-0ubuntu3.10
  Version table:
 *** 249.11-0ubuntu3.10 500
500 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages
500 http://security.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages
100 /var/lib/dpkg/status
 249.11-0ubuntu3.9 500
500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
 249.11-0ubuntu3.7 500
500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages
 249.11-0ubuntu3 500
500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
root@clean-jammy-amd64:/home/nr# cat > /etc/systemd/network/10-dhcp.network << 
EOF
[Match]
Name=en*

[Network]
DHCP=yes
EOF
root@clean-jammy-amd64:/home/nr# systemctl restart systemd-networkd

(Host)

nr@six:/t/tmp.jTS3wdPdT3$ virsh attach-interface clean-jammy-amd64 network 
no-dhcp
Interface attached successfully

(VM)

root@clean-jammy-amd64:/home/nr# networkctl 
IDX LINK TYPE OPERATIONAL SETUP  
  1 lo   loopback carrier unmanaged
  3 ens3 etherdegradedconfiguring

2 links listed.
root@clean-jammy-amd64:/home/nr# /lib/systemd/systemd-networkd-wait-online 
--any --timeout 10
Timeout occurred while waiting for network connectivity.
root@clean-jammy-amd64:/home/nr# networkctl 
IDX LINK TYPE OPERATIONAL SETUP  
  1 lo   loopback carrier unmanaged
  3 ens3 ethercarrier configuring

2 links listed.

(Host)

nr@six:/t/tmp.jTS3wdPdT3$ virsh attach-interface clean-jammy-amd64 network 
default
Interface attached successfully

(VM)

root@clean-jammy-amd64:/home/nr# /lib/systemd/systemd-networkd-wait-
online --any --timeout=0

root@clean-jammy-amd64:/home/nr# echo $?
0
root@clean-jammy-amd64:/home/nr# networkctl 
IDX LINK TYPE OPERATIONAL SETUP  
  1 lo   loopback carrier unmanaged
  3 ens3 etherdegradedconfiguring
  5 ens9 etherroutableconfigured 

3 links listed.


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

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

Title:
  wait-online does not correctly identify managed links

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

Bug description:
  [Impact]

  systemd-networkd-wait-online will exit prematurely when the --any flag
  is passed, due to an incorrect patch in Ubuntu that is supposed to
  make systemd-networkd-wait-online exit when *no* links are managed.

  [Test Plan]

  This test uses a VM managed by libvirt. In this scenario we have the
  "default" network which provides DHCP to the VM, and the "no-dhcp"
  network which does not provide DHCP.

  To setup the VM (this assumes Jammy, but the same steps apply for
  Lunar using appropriate names and install media):

  1. Define the default and no-dhcp networks:

  $ cat > /tmp/net-default.xml << EOF
  
default
04260896-2701-422d-84e0-8e0df1122db3




  

  

  
  $ virsh net-create --file /tmp/net-default.xml
  $ cat > /tmp/net-default.xml << EOF
  
no-dhcp
2c047740-caab-4c90-8421-70da6732a759
  





  
  $ virsh net-create --file /tmp/net-no-dhcp.xml
  $ virsh net-start --network default
  $ virst net-start --network no-dhcp

  2. Create the VM using virt-install:

  virt-install \
  --connect=qemu:///system \
  --name=jammy \
  --arch=x86_64 \
  --cpu=host-passthrough \
  --ram=4096 \
  --vcpus=1 \
  
--disk=path=/var/lib/libvirt/images/jammy.qcow2,size=24,format=qcow2,sparse=true,bus=virtio
 \
  --virt-type=kvm \
  --accelerate \
  --hvm \
  --cdrom=/tmp/ubuntu-22.04.2-live-server-amd64.iso \
  --os-type=linux \
  --os-variant=generic \
  --graphics=spice \
  --input=tablet \
  

[Touch-packages] [Bug 2031352] Re: Ubuntu 22.04.3 LTS stuck on power-off/reboot screen

[Juerg Haefliger]

It's not trivial since it happens so infrequently. I need to think about
this.

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

Title:
  Ubuntu 22.04.3 LTS stuck on power-off/reboot screen

Status in linux-hwe-6.2 package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Invalid
Status in linux-hwe-6.2 source package in Jammy:
  Confirmed

Bug description:
  After updating to Kernel 6.2 a few days ago, I have been experiencing
  issues with my system's shutdown and reboot functions. During these
  processes, the system becomes unresponsive and hangs on a black
  screen, which displays both the Dell and Ubuntu logos. This issue is
  inconsistent; it happens sporadically. Currently, the only workaround
  I've found to successfully shut down the system is to forcibly power
  off the machine by holding down the power button for 5 seconds.

  I've also tested a fresh installation of Ubuntu 22.04.3.

  

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: systemd 249.11-0ubuntu3.9
  ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13
  Uname: Linux 6.2.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug 14 22:41:14 2023
  InstallationDate: Installed on 2023-08-14 (1 days ago)
  InstallationMedia: Ubuntu 22.04.3 2023.08.13 LTS (20230813)
  MachineType: Dell Inc. XPS 8930
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic 
root=UUID=14d1ee7a-565f-4ba4-b6dd-7bc16e487451 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/14/2023
  dmi.bios.release: 1.1
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.30
  dmi.board.name: 0T88YD
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.30:bd03/14/2023:br1.1:svnDellInc.:pnXPS8930:pvr1.1.30:rvnDellInc.:rn0T88YD:rvrA00:cvnDellInc.:ct3:cvrNotSpecified:sku0859:
  dmi.product.family: XPS
  dmi.product.name: XPS 8930
  dmi.product.sku: 0859
  dmi.product.version: 1.1.30
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2023-08-13T20:57:27
  mtime.conffile..etc.systemd.system.conf: 2023-08-13T20:57:27

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2031352/+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 2011628] Re: Apparmor Disallows Disabling Dhclient Scripts

[Steve Langasek]

This bubbled back up in the sponsorship queue due to the recent comment
activity.  However, you say:

> this "fix" just eliminates harmless warnings, which is not worth
backporting to old releases.

It appears there is nothing here to be sponsored currently, so I am
unsubscribing the ubuntu-sponsors team.  Please resubscribe us if that
changes.

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

Title:
  Apparmor Disallows Disabling Dhclient Scripts

Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in isc-dhcp source package in Focal:
  New
Status in isc-dhcp source package in Jammy:
  New
Status in isc-dhcp source package in Lunar:
  New
Status in isc-dhcp package in Debian:
  New

Bug description:
  In some cases, it may be desirable to disable dhclient scripts. By
  default /sbin/dhclient-script is used, and some others are allowed by
  the apparmor profile.

  Without Apparmor, disabling hook scripts can be accomplished with
  flags -sf /bin/true, but with apparmor enabled this gets blocked:

  execve (/bin/true, ...): Permission denied

  Unfortunately dhclient doesn't appear to provide any other mechanism
  for disabling hook scripts.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/2011628/+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 2011628] Re: Apparmor Disallows Disabling Dhclient Scripts

[Steve Langasek]

Actually, it popped back up in our queue because Christian had targeted
the bug to the stable releases - not because of the comment activity.
In any case, nothing currently here for sponsorship.

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

Title:
  Apparmor Disallows Disabling Dhclient Scripts

Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in isc-dhcp source package in Focal:
  New
Status in isc-dhcp source package in Jammy:
  New
Status in isc-dhcp source package in Lunar:
  New
Status in isc-dhcp package in Debian:
  New

Bug description:
  In some cases, it may be desirable to disable dhclient scripts. By
  default /sbin/dhclient-script is used, and some others are allowed by
  the apparmor profile.

  Without Apparmor, disabling hook scripts can be accomplished with
  flags -sf /bin/true, but with apparmor enabled this gets blocked:

  execve (/bin/true, ...): Permission denied

  Unfortunately dhclient doesn't appear to provide any other mechanism
  for disabling hook scripts.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/2011628/+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 2028180] Re: [SRU][Ubuntu 22.04] Duplicate link for NVMe device by-id

[Nick Rosbrook]

I have verified the fix on Lunar using udev 252.5-2ubuntu3.1 from lunar-
proposed:

ubuntu@ubuntu:~$ apt-cache policy udev
udev:
  Installed: 252.5-2ubuntu3.1
  Candidate: 252.5-2ubuntu3.1
  Version table:
 *** 252.5-2ubuntu3.1 500
500 http://archive.ubuntu.com/ubuntu lunar-proposed/main amd64 Packages
500 http://security.ubuntu.com/ubuntu lunar-proposed/main amd64 Packages
100 /var/lib/dpkg/status
 252.5-2ubuntu3 500
500 http://archive.ubuntu.com/ubuntu lunar/main amd64 Packages
ubuntu@ubuntu:~$ sudo nvme connect-all
ubuntu@ubuntu:~$ ls -1 /dev/disk/by-id/nvme-QEMU*
/dev/disk/by-id/nvme-QEMU_NVMe_Ctrl_deadbeef
/dev/disk/by-id/nvme-QEMU_NVMe_Ctrl_deadbeef_1

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

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

Title:
  [SRU][Ubuntu 22.04] Duplicate link for NVMe device by-id

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Jammy:
  Fix Committed
Status in systemd source package in Kinetic:
  Won't Fix
Status in systemd source package in Lunar:
  Fix Committed
Status in systemd source package in Mantic:
  Fix Released

Bug description:
  [Impact]

  When working with NVMe/TCP host functionality, connecting to NVMe
  subsystem through multiple controllers can lead to an invalid device
  link created in /dev/disc/by-id/ being created.

  Steps to reproduce:
  Step 1: Install Ubuntu 22.04 LTS (ubuntu-22.04.1-live-server-amd64) on system.
  Step 2: Install nvme-cli package, currently installed version is nvme version 
1.16
  Step 3: In the os terminal, type any nvme connect-all to connect to NVMe 
subsystems and check the duplicate entries in /dev/disk/by-id/.

  This may cause users to choose the wrong link and would not be able to
  work with it.

  [Fix]

  udev-rules: fix nvme symlink creation on namespace changes
  
https://github.com/systemd/systemd/commit/c5ba7a2a4dd19a2d31b8a9d52d3c4bdde78387f0

  [Test Plan]
  Connect to NVMe/TCP subsystem using nvme connect-all. This was tested against 
a few Dell Storage systems.

  Steps to Reproduce:
  1. Use nvme connect-all to connect to an NVMe/TCP subsystems
  2. Check /dev/disk/by-id. The symlinks for NVMe devices should have the 
namespace id appended to them. E.g., if there is /dev/disk/by-id/nvme-$FOO, 
there should be a /dev/disk/by-id/name-$FOO_$ID.

  [ Where problems could occur ]
  This issue may be experienced by users who use NVMe/TCP solutions.
  Regression risk is low, because the existing symlink pattern is kept for 
backwards compatibility. This patch adds a new symlink pattern that includes 
the namespace ID, which will remain persistent throughout a boot.

  [ Other Info ]

  Expected Behavior:
  No duplicate entries of NVMe subsystems should exist.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2028180/+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 2009743] Re: networkd: classless routes served by DHCP are created incorrectly

[Nick Rosbrook]

I have verified the fix on Jammy using systemd 249.11-0ubuntu3.10 from
jammy-proposed:

root@clean-jammy-amd64:/home/nr# apt-cache policy systemd
systemd:
  Installed: 249.11-0ubuntu3.10
  Candidate: 249.11-0ubuntu3.10
  Version table:
 *** 249.11-0ubuntu3.10 500
500 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages
100 /var/lib/dpkg/status
 249.11-0ubuntu3.9 500
500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
 249.11-0ubuntu3.7 500
500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages
 249.11-0ubuntu3 500
500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
root@clean-jammy-amd64:/home/nr# cat > 
/etc/systemd/network/25-dhcp-server-veth-peer.network << EOF
[Match]
Name=veth-peer

[Network]
IPv6AcceptRA=no
Address=2600::1/0
Address=192.168.5.1/24
EOF
root@clean-jammy-amd64:/home/nr# cat > /etc/systemd/network/25-test.network << 
EOF
[Match]
Name=veth99

[Network]
DHCP=ipv4
IPv6AcceptRA=false

[DHCPv4]
UseRoutes=yes
EOF
root@clean-jammy-amd64:/home/nr# cat > /etc/systemd/network/25-veth.netdev << 
EOF
[NetDev]
Name=veth99
Kind=veth
MACAddress=12:34:56:78:9a:bc

[Peer]
Name=veth-peer
MACAddress=12:34:56:78:9a:bd
EOF
root@clean-jammy-amd64:/home/nr# mkdir -p 
/etc/systemd/system/systemd-networkd.service.d/
root@clean-jammy-amd64:/home/nr# cat > 
/etc/systemd/system/systemd-networkd.service.d/debug.conf << EOF
[Service]
Environment=SYSTEMD_LOG_LEVEL=debug
EOF
root@clean-jammy-amd64:/home/nr# systemctl daemon-reload
root@clean-jammy-amd64:/home/nr# systemctl restart systemd-networkd
root@clean-jammy-amd64:/home/nr# mkdir -p /run/networkd-ci
root@clean-jammy-amd64:/home/nr# dnsmasq 
--log-facility=/run/networkd-ci/test-dnsmasq.log --log-queries=extra --log-dhcp 
--pid-file=/run/networkd-ci/test-dnsmasq.pid --conf-file=/dev/null 
--bind-interfaces --interface=veth-peer 
--dhcp-leasefile=/run/networkd-ci/test-dnsmasq.lease --enable-ra 
--dhcp-range=2600::10,2600::20,2m --dhcp-range=192.168.5.10,192.168.5.200,2m 
--dhcp-option=option:mtu,1492 --dhcp-option=option:router,192.168.5.1 --port=0 
--no-resolv 
--dhcp-option=option:classless-static-route,0.0.0.0/0,192.168.5.4,8.0.0.0/8,192.168.5.5,192.168.5.64/26,192.168.5.5
 &
[1] 1418
root@clean-jammy-amd64:/home/nr# 
[1]+  Donednsmasq 
--log-facility=/run/networkd-ci/test-dnsmasq.log --log-queries=extra --log-dhcp 
--pid-file=/run/networkd-ci/test-dnsmasq.pid --conf-file=/dev/null 
--bind-interfaces --interface=veth-peer 
--dhcp-leasefile=/run/networkd-ci/test-dnsmasq.lease --enable-ra 
--dhcp-range=2600::10,2600::20,2m --dhcp-range=192.168.5.10,192.168.5.200,2m 
--dhcp-option=option:mtu,1492 --dhcp-option=option:router,192.168.5.1 --port=0 
--no-resolv 
--dhcp-option=option:classless-static-route,0.0.0.0/0,192.168.5.4,8.0.0.0/8,192.168.5.5,192.168.5.64/26,192.168.5.5
root@clean-jammy-amd64:/home/nr# 
root@clean-jammy-amd64:/home/nr# 
root@clean-jammy-amd64:/home/nr# 
root@clean-jammy-amd64:/home/nr# systemctl restart systemd-networkd
root@clean-jammy-amd64:/home/nr# ip r show dev veth99 192.168.5.64/26
192.168.5.64/26 via 192.168.5.5 proto dhcp src 192.168.5.181 metric 1024 
root@clean-jammy-amd64:/home/nr# journalctl -u systemd-networkd 
--grep="veth99.*assigned network"
-- No entries --


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

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

Title:
  networkd: classless routes served by DHCP are created incorrectly

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

Bug description:
  [Impact]

  Classless static routes served by DHCP are ignored by networkd in some
  cases. Specifically, the gateway is not being set for routes whenever
  the route destination is in the assigned network. This is a regression
  in behavior since Focal.

  [Test Plan]

  This is basically taken from systemd-networkd-tests.py. Using a veth
  pair, setup dnsmasq to serve the problematic routes:

  $ cat > /etc/systemd/network/25-dhcp-server-veth-peer.network << EOF
  [Match]
  Name=veth-peer

  [Network]
  IPv6AcceptRA=no
  Address=2600::1/0
  Address=192.168.5.1/24
  EOF

  $ cat > /etc/systemd/network/25-test.network << EOF
  [Match]
  Name=veth99

  [Network]
  DHCP=ipv4
  IPv6AcceptRA=false

  [DHCPv4]
  UseRoutes=yes
  EOF

  $ cat > /etc/systemd/network/25-veth.netdev << EOF
  [NetDev]
  Name=veth99
  Kind=veth
  MACAddress=12:34:56:78:9a:bc

  [Peer]
  Name=veth-peer
  MACAddress=12:34:56:78:9a:bd
  EOF

  $ mkdir -p /etc/systemd/system/systemd-networkd.service.d/
  $ cat > /etc/systemd/system/systemd-networkd.service.d/debug.conf << EOF
  

[Touch-packages] [Bug 2009743] Re: networkd: classless routes served by DHCP are created incorrectly

[Nick Rosbrook]

I have verified the fix on Lunar using systemd 252.5-2ubuntu3.1 from
lunar-proposed:

root@clean-lunar-amd64:/home/nr# apt-cache policy systemd
systemd:
  Installed: 252.5-2ubuntu3.1
  Candidate: 252.5-2ubuntu3.1
  Version table:
 *** 252.5-2ubuntu3.1 500
500 http://archive.ubuntu.com/ubuntu lunar-proposed/main amd64 Packages
100 /var/lib/dpkg/status
 252.5-2ubuntu3 500
500 http://archive.ubuntu.com/ubuntu lunar/main amd64 Packages
root@clean-lunar-amd64:/home/nr# cat > 
/etc/systemd/network/25-dhcp-server-veth-peer.network << EOF
[Match]
Name=veth-peer

[Network]
IPv6AcceptRA=no
Address=2600::1/0
Address=192.168.5.1/24
EOF
root@clean-lunar-amd64:/home/nr# cat > /etc/systemd/network/25-test.network << 
EOF
[Match]
Name=veth99

[Network]
DHCP=ipv4
IPv6AcceptRA=false

[DHCPv4]
UseRoutes=yes
EOF
root@clean-lunar-amd64:/home/nr# cat > /etc/systemd/network/25-veth.netdev << 
EOF
[NetDev]
Name=veth99
Kind=veth
MACAddress=12:34:56:78:9a:bc

[Peer]
Name=veth-peer
MACAddress=12:34:56:78:9a:bd
EOF
root@clean-lunar-amd64:/home/nr# mkdir -p 
/etc/systemd/system/systemd-networkd.service.d/
root@clean-lunar-amd64:/home/nr# cat > 
/etc/systemd/system/systemd-networkd.service.d/debug.conf << EOF
[Service]
Environment=SYSTEMD_LOG_LEVEL=debug
EOF
root@clean-lunar-amd64:/home/nr# systemctl daemon-reload
root@clean-lunar-amd64:/home/nr# systemctl restart systemd-networkd
root@clean-lunar-amd64:/home/nr# mkdir -p /run/networkd-ci
root@clean-lunar-amd64:/home/nr# dnsmasq 
--log-facility=/run/networkd-ci/test-dnsmasq.log --log-queries=extra --log-dhcp 
--pid-file=/run/networkd-ci/test-dnsmasq.pid --conf-file=/dev/null 
--bind-interfaces --interface=veth-peer 
--dhcp-leasefile=/run/networkd-ci/test-dnsmasq.lease --enable-ra 
--dhcp-range=2600::10,2600::20,2m --dhcp-range=192.168.5.10,192.168.5.200,2m 
--dhcp-option=option:mtu,1492 --dhcp-option=option:router,192.168.5.1 --port=0 
--no-resolv 
--dhcp-option=option:classless-static-route,0.0.0.0/0,192.168.5.4,8.0.0.0/8,192.168.5.5,192.168.5.64/26,192.168.5.5
 &
[1] 2573
root@clean-lunar-amd64:/home/nr# systemctl restart systemd-networkd
root@clean-lunar-amd64:/home/nr# ip r show dev veth99 192.168.5.64/26
192.168.5.64/26 via 192.168.5.5 proto dhcp src 192.168.5.181 metric 1024 
root@clean-lunar-amd64:/home/nr# journalctl -u systemd-networkd 
--grep="veth99.*assigned network"
-- No entries --
root@clean-lunar-amd64:/home/nr# 


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

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

Title:
  networkd: classless routes served by DHCP are created incorrectly

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

Bug description:
  [Impact]

  Classless static routes served by DHCP are ignored by networkd in some
  cases. Specifically, the gateway is not being set for routes whenever
  the route destination is in the assigned network. This is a regression
  in behavior since Focal.

  [Test Plan]

  This is basically taken from systemd-networkd-tests.py. Using a veth
  pair, setup dnsmasq to serve the problematic routes:

  $ cat > /etc/systemd/network/25-dhcp-server-veth-peer.network << EOF
  [Match]
  Name=veth-peer

  [Network]
  IPv6AcceptRA=no
  Address=2600::1/0
  Address=192.168.5.1/24
  EOF

  $ cat > /etc/systemd/network/25-test.network << EOF
  [Match]
  Name=veth99

  [Network]
  DHCP=ipv4
  IPv6AcceptRA=false

  [DHCPv4]
  UseRoutes=yes
  EOF

  $ cat > /etc/systemd/network/25-veth.netdev << EOF
  [NetDev]
  Name=veth99
  Kind=veth
  MACAddress=12:34:56:78:9a:bc

  [Peer]
  Name=veth-peer
  MACAddress=12:34:56:78:9a:bd
  EOF

  $ mkdir -p /etc/systemd/system/systemd-networkd.service.d/
  $ cat > /etc/systemd/system/systemd-networkd.service.d/debug.conf << EOF
  [Service]
  Environment=SYSTEMD_LOG_LEVEL=debug
  EOF

  $ systemctl daemon-reload
  $ systemctl restart systemd-networkd
  $ mkdir -p /run/networkd-ci
  $ dnsmasq --log-facility=/run/networkd-ci/test-dnsmasq.log 
--log-queries=extra --log-dhcp --pid-file=/run/networkd-ci/test-dnsmasq.pid 
--conf-file=/dev/null --bind-interfaces --interface=veth-peer 
--dhcp-leasefile=/run/networkd-ci/test-dnsmasq.lease --enable-ra 
--dhcp-range=2600::10,2600::20,2m --dhcp-range=192.168.5.10,192.168.5.200,2m 
--dhcp-option=option:mtu,1492 --dhcp-option=option:router,192.168.5.1 --port=0 
--no-resolv 
--dhcp-option=option:classless-static-route,0.0.0.0/0,192.168.5.4,8.0.0.0/8,192.168.5.5,192.168.5.64/26,192.168.5.5
 &

  $ systemctl restart systemd-networkd

  On an affected machine, the route to 192.168.5.64 on veth99 will be
  missing it's gateway address:

  $ ip r show dev veth99 192.168.5.64/26
  192.168.5.64/26 proto dhcp scope link src 

[Touch-packages] [Bug 2031352] Re: Ubuntu 22.04.3 LTS stuck on power-off/reboot screen

[Cristiano Fraga G. Nunes]

@juergh Please, provide further information to help-us with the bug.

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

Title:
  Ubuntu 22.04.3 LTS stuck on power-off/reboot screen

Status in linux-hwe-6.2 package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Invalid
Status in linux-hwe-6.2 source package in Jammy:
  Confirmed

Bug description:
  After updating to Kernel 6.2 a few days ago, I have been experiencing
  issues with my system's shutdown and reboot functions. During these
  processes, the system becomes unresponsive and hangs on a black
  screen, which displays both the Dell and Ubuntu logos. This issue is
  inconsistent; it happens sporadically. Currently, the only workaround
  I've found to successfully shut down the system is to forcibly power
  off the machine by holding down the power button for 5 seconds.

  I've also tested a fresh installation of Ubuntu 22.04.3.

  

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: systemd 249.11-0ubuntu3.9
  ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13
  Uname: Linux 6.2.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug 14 22:41:14 2023
  InstallationDate: Installed on 2023-08-14 (1 days ago)
  InstallationMedia: Ubuntu 22.04.3 2023.08.13 LTS (20230813)
  MachineType: Dell Inc. XPS 8930
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic 
root=UUID=14d1ee7a-565f-4ba4-b6dd-7bc16e487451 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/14/2023
  dmi.bios.release: 1.1
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.30
  dmi.board.name: 0T88YD
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.30:bd03/14/2023:br1.1:svnDellInc.:pnXPS8930:pvr1.1.30:rvnDellInc.:rn0T88YD:rvrA00:cvnDellInc.:ct3:cvrNotSpecified:sku0859:
  dmi.product.family: XPS
  dmi.product.name: XPS 8930
  dmi.product.sku: 0859
  dmi.product.version: 1.1.30
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2023-08-13T20:57:27
  mtime.conffile..etc.systemd.system.conf: 2023-08-13T20:57:27

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2031352/+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 2033139] Re: ubuntu-desktop{-minimal} still depending on ghostscript-x package

[Launchpad Bug Tracker]

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

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

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

Title:
  ubuntu-desktop{-minimal} still depending on ghostscript-x package

Status in ghostscript package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  The packages ubuntu-desktop and ubuntu-desktop-minimal still depend on 
package ghostscript-x, but it's a dummy package that just points for the 
package ghostscript.
  So the idea is to change the dependency so the dummy package ghostscript-x 
can be removed safely.

  Description:  Ubuntu Mantic Minotaur (development branch)
  Release:  23.10

  Packages version: 1.516

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/2033139/+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 2033139] Re: ubuntu-desktop{-minimal} still depending on ghostscript-x package

[wontfix]

** Tags added: bitesize bloat ghostscript mantic packaging

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

Title:
  ubuntu-desktop{-minimal} still depending on ghostscript-x package

Status in ghostscript package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  The packages ubuntu-desktop and ubuntu-desktop-minimal still depend on 
package ghostscript-x, but it's a dummy package that just points for the 
package ghostscript.
  So the idea is to change the dependency so the dummy package ghostscript-x 
can be removed safely.

  Description:  Ubuntu Mantic Minotaur (development branch)
  Release:  23.10

  Packages version: 1.516

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/2033139/+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 2033139] Re: ubuntu-desktop{-minimal} still depending on ghostscript-x package

[Launchpad Bug Tracker]

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

** Changed in: ubuntu-meta (Ubuntu)
   Status: New => Confirmed

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

Title:
  ubuntu-desktop{-minimal} still depending on ghostscript-x package

Status in ghostscript package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  The packages ubuntu-desktop and ubuntu-desktop-minimal still depend on 
package ghostscript-x, but it's a dummy package that just points for the 
package ghostscript.
  So the idea is to change the dependency so the dummy package ghostscript-x 
can be removed safely.

  Description:  Ubuntu Mantic Minotaur (development branch)
  Release:  23.10

  Packages version: 1.516

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/2033139/+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 2033139] Re: ubuntu-desktop{-minimal} still depending on ghostscript-x package

[wontfix]

** Also affects: ghostscript (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  ubuntu-desktop{-minimal} still depending on ghostscript-x package

Status in ghostscript package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  The packages ubuntu-desktop and ubuntu-desktop-minimal still depend on 
package ghostscript-x, but it's a dummy package that just points for the 
package ghostscript.
  So the idea is to change the dependency so the dummy package ghostscript-x 
can be removed safely.

  Description:  Ubuntu Mantic Minotaur (development branch)
  Release:  23.10

  Packages version: 1.516

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/2033139/+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 2028180] Re: [SRU][Ubuntu 22.04] Duplicate link for NVMe device by-id

[Nick Rosbrook]

I have verified the fix using udev 249.11-0ubuntu3.10 from jammy-
proposed:

ubuntu@ubuntu:~$ apt-cache policy udev
udev:
  Installed: 249.11-0ubuntu3.10
  Candidate: 249.11-0ubuntu3.10
  Version table:
 *** 249.11-0ubuntu3.10 500
500 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages
500 http://security.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages
100 /var/lib/dpkg/status
 249.11-0ubuntu3.9 500
500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
 249.11-0ubuntu3.7 500
500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages
 249.11-0ubuntu3 500
500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
ubuntu@ubuntu:~$ nvme connect-all
ubuntu@ubuntu:~$ ls -1 /dev/disk/by-id/nvme-QEMU_NVMe*
/dev/disk/by-id/nvme-QEMU_NVMe_Ctrl_deadbeef
/dev/disk/by-id/nvme-QEMU_NVMe_Ctrl_deadbeef_1

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

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

Title:
  [SRU][Ubuntu 22.04] Duplicate link for NVMe device by-id

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Jammy:
  Fix Committed
Status in systemd source package in Kinetic:
  Won't Fix
Status in systemd source package in Lunar:
  Fix Committed
Status in systemd source package in Mantic:
  Fix Released

Bug description:
  [Impact]

  When working with NVMe/TCP host functionality, connecting to NVMe
  subsystem through multiple controllers can lead to an invalid device
  link created in /dev/disc/by-id/ being created.

  Steps to reproduce:
  Step 1: Install Ubuntu 22.04 LTS (ubuntu-22.04.1-live-server-amd64) on system.
  Step 2: Install nvme-cli package, currently installed version is nvme version 
1.16
  Step 3: In the os terminal, type any nvme connect-all to connect to NVMe 
subsystems and check the duplicate entries in /dev/disk/by-id/.

  This may cause users to choose the wrong link and would not be able to
  work with it.

  [Fix]

  udev-rules: fix nvme symlink creation on namespace changes
  
https://github.com/systemd/systemd/commit/c5ba7a2a4dd19a2d31b8a9d52d3c4bdde78387f0

  [Test Plan]
  Connect to NVMe/TCP subsystem using nvme connect-all. This was tested against 
a few Dell Storage systems.

  Steps to Reproduce:
  1. Use nvme connect-all to connect to an NVMe/TCP subsystems
  2. Check /dev/disk/by-id. The symlinks for NVMe devices should have the 
namespace id appended to them. E.g., if there is /dev/disk/by-id/nvme-$FOO, 
there should be a /dev/disk/by-id/name-$FOO_$ID.

  [ Where problems could occur ]
  This issue may be experienced by users who use NVMe/TCP solutions.
  Regression risk is low, because the existing symlink pattern is kept for 
backwards compatibility. This patch adds a new symlink pattern that includes 
the namespace ID, which will remain persistent throughout a boot.

  [ Other Info ]

  Expected Behavior:
  No duplicate entries of NVMe subsystems should exist.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2028180/+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 2033295] Re: AMDGPU: Screen frequently and suddenly freezes. Hard reboot necessary. AMD Ryzen

[GT]

Selection of specific source package: I am not sure in which package the
Linux Kernel AMD Ryzen graphic drivers are located. I chose "libdrm" as
it includes libdrm-amdgpu. I hope that this is correct.

** Package changed: ubuntu => libdrm (Ubuntu)

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

Title:
  AMDGPU: Screen frequently and suddenly freezes. Hard reboot necessary.
  AMD Ryzen

Status in libdrm package in Ubuntu:
  New

Bug description:
  Frequently, when I just use the computer, the mouse cursor freezes,
  the screen starts to flicker and freezes (screen flickers between
  entirely black and desktop visible). No interaction possible. In most
  cases Ctrl-Alt-Prnt-REISUB works to hard reboot the system.

  Frequency: Freezes happen several times a day. Unsaved work is lost.

  I noticed that:
  * The freezes usually happen when an external display is connected (it does 
not matter whether USB-C or HDMI). The freezes rarely happen when no external 
display is connected.
  * The freezes happen with Wayland and X11, with Ubuntu UI and Gnome Shell.
  * The freezes happen randomly, but I have the feeling that they happen more 
often when "something graphical" happens, e.g. when I go to the Gnome Shell 
overview, desktop switching, or when I switch to/from full screen mode, click 
on an image to scale it, or when I use map services in the web browser like 
Google Maps or radio.garden.
  * The freezes even more often happened when WebGL is active in Firefox or 
Chomium.
  * I encounter these annoying freezes already for several weeks.

  Having looked at the log files, I assume that AMDGPU is at the core of
  the problem.

  System:
  Ubuntu 23.04 (up to date), Wayland (freezes also happen with X11), Gnome 
44.3. 
  Linux 6.2.0-31-generic
  Lenovo ThinkPad T14s Gen 1 (with most recent BIOS/UEFI 1.44), AMD Ryzen™ 7 
PRO 4750U with Radeon™ Graphics × 16.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/2033295/+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 2033295] [NEW] AMDGPU: Screen frequently and suddenly freezes. Hard reboot necessary. AMD Ryzen

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Frequently, when I just use the computer, the mouse cursor freezes, the
screen starts to flicker and freezes (screen flickers between entirely
black and desktop visible). No interaction possible. In most cases Ctrl-
Alt-Prnt-REISUB works to hard reboot the system.

Frequency: Freezes happen several times a day. Unsaved work is lost.

I noticed that:
* The freezes usually happen when an external display is connected (it does not 
matter whether USB-C or HDMI). The freezes rarely happen when no external 
display is connected.
* The freezes happen with Wayland and X11, with Ubuntu UI and Gnome Shell.
* The freezes happen randomly, but I have the feeling that they happen more 
often when "something graphical" happens, e.g. when I go to the Gnome Shell 
overview, desktop switching, or when I switch to/from full screen mode, click 
on an image to scale it, or when I use map services in the web browser like 
Google Maps or radio.garden.
* The freezes even more often happened when WebGL is active in Firefox or 
Chomium.
* I encounter these annoying freezes already for several weeks.

Having looked at the log files, I assume that AMDGPU is at the core of
the problem.

System:
Ubuntu 23.04 (up to date), Wayland (freezes also happen with X11), Gnome 44.3. 
Linux 6.2.0-31-generic
Lenovo ThinkPad T14s Gen 1 (with most recent BIOS/UEFI 1.44), AMD Ryzen™ 7 PRO 
4750U with Radeon™ Graphics × 16.

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


** Tags: amdgpu bot-comment freeze
-- 
AMDGPU: Screen frequently and suddenly freezes. Hard reboot necessary. AMD Ryzen
https://bugs.launchpad.net/bugs/2033295
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to libdrm 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 2013543] Re: systemctl daemon-reexec forgets running services and starts everything new

[Nick Rosbrook]

I have verified the fix on Jammy using systemd 249.11-0ubuntu3.10 from
jammy-proposed:

nr@clean-jammy-amd64:~$ apt-cache policy systemd
systemd:
  Installed: 249.11-0ubuntu3.9
  Candidate: 249.11-0ubuntu3.10
  Version table:
 249.11-0ubuntu3.10 500
500 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages
 *** 249.11-0ubuntu3.9 500
500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
100 /var/lib/dpkg/status
 249.11-0ubuntu3.7 500
500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages
 249.11-0ubuntu3 500
500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
nr@clean-jammy-amd64:~$ cat /proc/cmdline 
BOOT_IMAGE=/boot/vmlinuz-5.19.0-45-generic 
root=UUID=32a6b55f-64d3-421b-a77d-2f9a2c6d68be ro quiet splash --- vt.handoff=7
nr@clean-jammy-amd64:~$ sudo apt install systemd -y
[sudo] password for nr: 
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages were automatically installed and are no longer required:
  libflashrom1 libftdi1-2 libllvm13 linux-headers-5.15.0-25
  linux-headers-5.15.0-25-generic linux-image-5.15.0-25-generic
  linux-modules-5.15.0-25-generic linux-modules-extra-5.15.0-25-generic
Use 'sudo apt autoremove' to remove them.
The following additional packages will be installed:
  libnss-systemd libpam-systemd libsystemd0 systemd-oomd systemd-sysv
  systemd-timesyncd
Suggested packages:
  systemd-container libtss2-rc0
The following packages will be upgraded:
  libnss-systemd libpam-systemd libsystemd0 systemd systemd-oomd systemd-sysv
  systemd-timesyncd
7 upgraded, 0 newly installed, 0 to remove and 217 not upgraded.
Need to get 5,312 kB of archives.
After this operation, 4,096 B disk space will be freed.
Get:1 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 libnss-systemd 
amd64 249.11-0ubuntu3.10 [133 kB]
Get:2 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 
systemd-timesyncd amd64 249.11-0ubuntu3.10 [31.2 kB]
Get:3 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 systemd-sysv 
amd64 249.11-0ubuntu3.10 [10.5 kB]
Get:4 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 systemd-oomd 
amd64 249.11-0ubuntu3.10 [34.8 kB]
Get:5 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 libpam-systemd 
amd64 249.11-0ubuntu3.10 [203 kB]
Get:6 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 systemd amd64 
249.11-0ubuntu3.10 [4,581 kB]
Get:7 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 libsystemd0 
amd64 249.11-0ubuntu3.10 [319 kB]
[...]
nr@clean-jammy-amd64:~$ apt-cache policy systemd
systemd:
  Installed: 249.11-0ubuntu3.10
  Candidate: 249.11-0ubuntu3.10
  Version table:
 *** 249.11-0ubuntu3.10 500
500 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages
100 /var/lib/dpkg/status
 249.11-0ubuntu3.9 500
500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
 249.11-0ubuntu3.7 500
500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages
 249.11-0ubuntu3 500
500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
nr@clean-jammy-amd64:~$ grep -Fsx systemd /run/reboot-required.pkgs
systemd
nr@clean-jammy-amd64:~$ reboot
[...]
nr@clean-jammy-amd64:~$ sudo systemctl daemon-reexec
nr@clean-jammy-amd64:~$ journalctl --grep "Found left-over process" -b 0
Aug 28 11:55:10 clean-jammy-amd64 systemd[1]: kerneloops.service: Found left-ov>
nr@clean-jammy-amd64:~$ cat /proc/1/cmdline | tr '\0' '\n'
/lib/systemd/systemd
--system
--deserialize
107
splash
---


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

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

Title:
  systemctl daemon-reexec forgets running services and starts everything
  new

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

Bug description:
  [Impact]

  Depending on the contents of /proc/cmdline, when systemd is re-
  executed with systemctl daemon-reexec, the --deserialize flag may be
  ignored because it was added after the other arguments. For example,
  if /proc/cmdline contains ---, then the re-exec cmdline might look
  like:

  $ cat /proc/1/cmdline | tr '\0' '\n' 
  /lib/systemd/systemd
  ---
  splash
  --system
  --deserialize
  54

  This causes systemd not to process the --deserialize 54 argument,
  causing it to start with a fresh state. This can cause all kinds of
  problems, and one easy symptom to see is many lines in the journal
  like:

  "$service.service: Found left-over process $pid ($service) in control
  group while starting unit. 

[Touch-packages] [Bug 2031352] Re: Ubuntu 22.04.3 LTS stuck on power-off/reboot screen

[Juerg Haefliger]

It's not a systemd issue.

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

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

Title:
  Ubuntu 22.04.3 LTS stuck on power-off/reboot screen

Status in linux-hwe-6.2 package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Invalid
Status in linux-hwe-6.2 source package in Jammy:
  Confirmed

Bug description:
  After updating to Kernel 6.2 a few days ago, I have been experiencing
  issues with my system's shutdown and reboot functions. During these
  processes, the system becomes unresponsive and hangs on a black
  screen, which displays both the Dell and Ubuntu logos. This issue is
  inconsistent; it happens sporadically. Currently, the only workaround
  I've found to successfully shut down the system is to forcibly power
  off the machine by holding down the power button for 5 seconds.

  I've also tested a fresh installation of Ubuntu 22.04.3.

  

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: systemd 249.11-0ubuntu3.9
  ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13
  Uname: Linux 6.2.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug 14 22:41:14 2023
  InstallationDate: Installed on 2023-08-14 (1 days ago)
  InstallationMedia: Ubuntu 22.04.3 2023.08.13 LTS (20230813)
  MachineType: Dell Inc. XPS 8930
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic 
root=UUID=14d1ee7a-565f-4ba4-b6dd-7bc16e487451 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/14/2023
  dmi.bios.release: 1.1
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.30
  dmi.board.name: 0T88YD
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.30:bd03/14/2023:br1.1:svnDellInc.:pnXPS8930:pvr1.1.30:rvnDellInc.:rn0T88YD:rvrA00:cvnDellInc.:ct3:cvrNotSpecified:sku0859:
  dmi.product.family: XPS
  dmi.product.name: XPS 8930
  dmi.product.sku: 0859
  dmi.product.version: 1.1.30
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2023-08-13T20:57:27
  mtime.conffile..etc.systemd.system.conf: 2023-08-13T20:57:27

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2031352/+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 2013543] Re: systemctl daemon-reexec forgets running services and starts everything new

[Nick Rosbrook]

I have verified the fix on Lunar using 252.5-2ubuntu3.1 from lunar-
proposed:

nr@clean-lunar-amd64:~$ apt-cache policy systemd
systemd:
  Installed: 252.5-2ubuntu3
  Candidate: 252.5-2ubuntu3.1
  Version table:
 252.5-2ubuntu3.1 500
500 http://archive.ubuntu.com/ubuntu lunar-proposed/main amd64 Packages
 *** 252.5-2ubuntu3 500
500 http://archive.ubuntu.com/ubuntu lunar/main amd64 Packages
100 /var/lib/dpkg/status
nr@clean-lunar-amd64:~$ cat /proc/cmdline 
BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic 
root=UUID=9122271f-96e1-4551-8279-80165b8e42b8 ro quiet splash --- vt.handoff=7
nr@clean-lunar-amd64:~$ sudo apt install systemd -y
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following additional packages will be installed:
  libnss-systemd libpam-systemd libsystemd-shared libsystemd0 libudev1 
systemd-oomd systemd-resolved systemd-sysv
  systemd-timesyncd udev
Suggested packages:
  systemd-container systemd-homed systemd-userdbd systemd-boot libqrencode4
The following packages will be upgraded:
  libnss-systemd libpam-systemd libsystemd-shared libsystemd0 libudev1 systemd 
systemd-oomd systemd-resolved
  systemd-sysv systemd-timesyncd udev
11 upgraded, 0 newly installed, 0 to remove and 76 not upgraded.
Need to get 7,789 kB of archives.
After this operation, 7,168 B of additional disk space will be used.
Get:1 http://archive.ubuntu.com/ubuntu lunar-proposed/main amd64 
systemd-timesyncd amd64 252.5-2ubuntu3.1 [33.9 kB]
Get:2 http://archive.ubuntu.com/ubuntu lunar-proposed/main amd64 systemd amd64 
252.5-2ubuntu3.1 [3,002 kB]
Get:3 http://archive.ubuntu.com/ubuntu lunar-proposed/main amd64 udev amd64 
252.5-2ubuntu3.1 [1,693 kB]
Get:4 http://archive.ubuntu.com/ubuntu lunar-proposed/main amd64 systemd-sysv 
amd64 252.5-2ubuntu3.1 [11.5 kB]
Get:5 http://archive.ubuntu.com/ubuntu lunar-proposed/main amd64 systemd-oomd 
amd64 252.5-2ubuntu3.1 [38.9 kB]
Get:6 http://archive.ubuntu.com/ubuntu lunar-proposed/main amd64 libnss-systemd 
amd64 252.5-2ubuntu3.1 [141 kB]
Get:7 http://archive.ubuntu.com/ubuntu lunar-proposed/main amd64 libpam-systemd 
amd64 252.5-2ubuntu3.1 [206 kB]
Get:8 http://archive.ubuntu.com/ubuntu lunar-proposed/main amd64 
systemd-resolved amd64 252.5-2ubuntu3.1 [288 kB]
Get:9 http://archive.ubuntu.com/ubuntu lunar-proposed/main amd64 
libsystemd-shared amd64 252.5-2ubuntu3.1 [1,834 kB]
Get:10 http://archive.ubuntu.com/ubuntu lunar-proposed/main amd64 libudev1 
amd64 252.5-2ubuntu3.1 [151 kB]
Get:11 http://archive.ubuntu.com/ubuntu lunar-proposed/main amd64 libsystemd0 
amd64 252.5-2ubuntu3.1 [390 kB]
[...]
nr@clean-lunar-amd64:~$ apt-cache policy systemd
systemd:
  Installed: 252.5-2ubuntu3.1
  Candidate: 252.5-2ubuntu3.1
  Version table:
 *** 252.5-2ubuntu3.1 500
500 http://archive.ubuntu.com/ubuntu lunar-proposed/main amd64 Packages
100 /var/lib/dpkg/status
 252.5-2ubuntu3 500
500 http://archive.ubuntu.com/ubuntu lunar/main amd64 Packages
nr@clean-lunar-amd64:~$ grep -Fsx systemd /run/reboot-required.pkgs
systemd
nr@clean-lunar-amd64:~$ reboot
[...]
nr@clean-lunar-amd64:~$ sudo systemctl daemon-reexec
nr@clean-lunar-amd64:~$ journalctl --grep "Found left-over process" -b 0
Aug 28 11:29:50 clean-lunar-amd64 systemd[1]: kerneloops.service: Found left-ov>
nr@clean-lunar-amd64:~$ cat /proc/1/cmdline | tr '\0' '\n'
/lib/systemd/systemd
--system
--deserialize
96
splash
---


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

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

Title:
  systemctl daemon-reexec forgets running services and starts everything
  new

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

Bug description:
  [Impact]

  Depending on the contents of /proc/cmdline, when systemd is re-
  executed with systemctl daemon-reexec, the --deserialize flag may be
  ignored because it was added after the other arguments. For example,
  if /proc/cmdline contains ---, then the re-exec cmdline might look
  like:

  $ cat /proc/1/cmdline | tr '\0' '\n' 
  /lib/systemd/systemd
  ---
  splash
  --system
  --deserialize
  54

  This causes systemd not to process the --deserialize 54 argument,
  causing it to start with a fresh state. This can cause all kinds of
  problems, and one easy symptom to see is many lines in the journal
  like:

  "$service.service: Found left-over process $pid ($service) in control
  group while starting unit. Ignoring."

  [Test Plan]

  1. (Only needed if your test system is not already affected) Edit the
  kernel command line to contain '---' at the end, which would trigger
  the bug. This can be done by appending '---' to
  

[Touch-packages] [Bug 2031352] Re: Ubuntu 22.04.3 LTS stuck on power-off/reboot screen

[Ian Russel Adem]

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

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

Title:
  Ubuntu 22.04.3 LTS stuck on power-off/reboot screen

Status in linux-hwe-6.2 package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in linux-hwe-6.2 source package in Jammy:
  Confirmed

Bug description:
  After updating to Kernel 6.2 a few days ago, I have been experiencing
  issues with my system's shutdown and reboot functions. During these
  processes, the system becomes unresponsive and hangs on a black
  screen, which displays both the Dell and Ubuntu logos. This issue is
  inconsistent; it happens sporadically. Currently, the only workaround
  I've found to successfully shut down the system is to forcibly power
  off the machine by holding down the power button for 5 seconds.

  I've also tested a fresh installation of Ubuntu 22.04.3.

  

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: systemd 249.11-0ubuntu3.9
  ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13
  Uname: Linux 6.2.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug 14 22:41:14 2023
  InstallationDate: Installed on 2023-08-14 (1 days ago)
  InstallationMedia: Ubuntu 22.04.3 2023.08.13 LTS (20230813)
  MachineType: Dell Inc. XPS 8930
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic 
root=UUID=14d1ee7a-565f-4ba4-b6dd-7bc16e487451 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/14/2023
  dmi.bios.release: 1.1
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.30
  dmi.board.name: 0T88YD
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.30:bd03/14/2023:br1.1:svnDellInc.:pnXPS8930:pvr1.1.30:rvnDellInc.:rn0T88YD:rvrA00:cvnDellInc.:ct3:cvrNotSpecified:sku0859:
  dmi.product.family: XPS
  dmi.product.name: XPS 8930
  dmi.product.sku: 0859
  dmi.product.version: 1.1.30
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2023-08-13T20:57:27
  mtime.conffile..etc.systemd.system.conf: 2023-08-13T20:57:27

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2031352/+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 2031683] Re: systemd FTBFS on ppc64el due to fuzzer failures

[Nick Rosbrook]

The ppc64el build of systemd 252.5-2ubuntu3.1
(https://launchpad.net/ubuntu/+source/systemd/252.5-2ubuntu3.1/+build/26537841
succeeded), with all built-time tests and fuzzers passing.

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

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

Title:
  systemd FTBFS on ppc64el due to fuzzer failures

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Lunar:
  Fix Committed

Bug description:
  [Impact]

  systemd FTBFS on ppc64el due to failing fuzz tests.

  [Test Plan]

  The build-time tests and fuzzing should pass so that the build
  ultimately passes on ppc64el.

  [Where problems could occur]

  The patch just removes the "pure" attribute from
  bus_message_type_from_string, because that attribute was incorrect for
  the behavior of the function. Hence, the regression potential should
  be limited to building the package.

  [Original Description]

  This PPA build[1] demonstrates the issue, the relevant part being:

  [ ... ]
  1061/1066 systemd:dist-check / check-help-networkctl  
 OK0.04s
  1062/1066 systemd:dist-check / check-version-networkctl   
 OK0.03s
  1063/1066 systemd:dist-check / check-help-kernel-install  
 OK0.03s
  1064/1066 systemd:dist-check / check-version-kernel-install   
 OK0.02s
  1065/1066 systemd:dist-check / check-directives   
 OK0.18s
  1066/1066 systemd:dist-check / parse-hwdb 
 OK5.43s

  Summary of Failures:

   661/1066 systemd:fuzzers / fuzz-bus-match_bugzilla1935084.input  
 FAIL  0.22s   killed by signal 11 SIGSEGV
   667/1066 systemd:fuzzers / fuzz-bus-match_test.input 
 FAIL  0.25s   killed by signal 11 SIGSEGV

  Ok: 1032
  Expected Fail:  0
  Fail:   2
  Unexpected Pass:0
  Skipped:32
  Timeout:0

  Full log written to 
/<>/obj-powerpc64le-linux-gnu/meson-logs/testlog.txt
  make[1]: *** [debian/rules:308: override_dh_auto_test] Error 2
  make[1]: Leaving directory '/<>'
  make: *** [debian/rules:312: binary-arch] Error 2
  dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit 
status 2

  This appears to be related to a toolchain change, because I get the
  same result when doing a no-change rebuild of systemd on ppc64el in
  Lunar (i.e. the FTBFS is not introduced by the changes I am testing).

  [1] https://launchpadlibrarian.net/682104329/buildlog_ubuntu-lunar-
  ppc64el.systemd_252.5-2ubuntu4~ppa11_BUILDING.txt.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2031683/+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 2023229] Re: Autopkgtest failure for tests-in-lxd

[Nick Rosbrook]

Looking at the test history for systemd
(https://autopkgtest.ubuntu.com/packages/systemd), tests-in-lxd is
passing on all arches for 252.5-2ubuntu3.1 (Lunar), and for
249.11-0ubuntu3.10 (Jammy).

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

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

Title:
  Autopkgtest failure for tests-in-lxd

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Jammy:
  Fix Committed
Status in systemd source package in Kinetic:
  Won't Fix
Status in systemd source package in Lunar:
  Fix Committed
Status in systemd source package in Mantic:
  Fix Released

Bug description:
  [Impact]
  systemd autopkgtests are failing in stable releases due to a change in LXD. 
We want the tests to be in good shape so that we can properly catch regressions 
etc. during SRUs.

  [Test Plan]

  The tests-in-lxd test should pass.

  [Where problems could occur]

  The patch adds a flag to lxc invocation in the debian/tests/tests-in-
  lxd script, so any problems would be contained to that test.

  [Original Description]

  Autopackagetests on multiple Jammy kernels show the same failure on
  the test-in-lxd test

  Error: Aliases already exists: autopkgtest/ubuntu/jammy/amd64
  autopkgtest [16:33:58]: test tests-in-lxd: ---]
  autopkgtest [16:33:58]: test tests-in-lxd:  - - - - - - - - - - results - - - 
- - - - - - -
  tests-in-lxd FAIL non-zero exit status 1

  Where the error seems to be triggered by debian/tests/tests-in-lxd

  lxc publish systemd-lxc --alias $IMAGE

  To be determined if this a problem in the autopkgtest infrastructure
  or test bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2023229/+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 2031352] Re: Ubuntu 22.04.3 LTS stuck on power-off/reboot screen

[Juerg Haefliger]

** Changed in: systemd (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  Ubuntu 22.04.3 LTS stuck on power-off/reboot screen

Status in linux-hwe-6.2 package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Invalid
Status in linux-hwe-6.2 source package in Jammy:
  Confirmed

Bug description:
  After updating to Kernel 6.2 a few days ago, I have been experiencing
  issues with my system's shutdown and reboot functions. During these
  processes, the system becomes unresponsive and hangs on a black
  screen, which displays both the Dell and Ubuntu logos. This issue is
  inconsistent; it happens sporadically. Currently, the only workaround
  I've found to successfully shut down the system is to forcibly power
  off the machine by holding down the power button for 5 seconds.

  I've also tested a fresh installation of Ubuntu 22.04.3.

  

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: systemd 249.11-0ubuntu3.9
  ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13
  Uname: Linux 6.2.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug 14 22:41:14 2023
  InstallationDate: Installed on 2023-08-14 (1 days ago)
  InstallationMedia: Ubuntu 22.04.3 2023.08.13 LTS (20230813)
  MachineType: Dell Inc. XPS 8930
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic 
root=UUID=14d1ee7a-565f-4ba4-b6dd-7bc16e487451 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/14/2023
  dmi.bios.release: 1.1
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.30
  dmi.board.name: 0T88YD
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.30:bd03/14/2023:br1.1:svnDellInc.:pnXPS8930:pvr1.1.30:rvnDellInc.:rn0T88YD:rvrA00:cvnDellInc.:ct3:cvrNotSpecified:sku0859:
  dmi.product.family: XPS
  dmi.product.name: XPS 8930
  dmi.product.sku: 0859
  dmi.product.version: 1.1.30
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2023-08-13T20:57:27
  mtime.conffile..etc.systemd.system.conf: 2023-08-13T20:57:27

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2031352/+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 2032851] Re: package apparmor 2.12-4ubuntu5.3 failed to install/upgrade: new apparmor package pre-installation script subprocess returned error exit status 1

[G]

Had this when updating from ubuntu (with unity) 18.4 to 20.04  Yesterday
(27 Aug)

Possible Work around?  
Moved bf9d6da9.0 to desktop (Moved, just in case was not a solution as had 
tried re-namaing, with no effect)
sudo apt-get install -f, then ran ok.

afterwards noted that etc/../cache/ & desktop/bf9d6da9.0 no longer
present on the system

NB - to do this had to use back version of Ubuntu, as new version did
not load.

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

Title:
  package apparmor 2.12-4ubuntu5.3 failed to install/upgrade: new
  apparmor package pre-installation script subprocess returned error
  exit status 1

Status in apparmor package in Ubuntu:
  Confirmed

Bug description:
  package install error

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: apparmor 2.12-4ubuntu5.3
  ProcVersionSignature: Ubuntu 4.15.0-213.224-generic 4.15.18
  Uname: Linux 4.15.0-213-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Thu Aug 24 02:35:35 2023
  DuplicateSignature:
   package:apparmor:2.12-4ubuntu5.3
   Preparing to unpack .../16-apparmor_2.13.3-7ubuntu5.2_amd64.deb ...
   rm: cannot remove '/etc/apparmor.d/cache/bf9d6da9.0': Is a directory
   dpkg: error processing archive 
/tmp/apt-dpkg-install-InP0fz/16-apparmor_2.13.3-7ubuntu5.2_amd64.deb (--unpack):
new apparmor package pre-installation script subprocess returned error exit 
status 1
  ErrorMessage: new apparmor package pre-installation script subprocess 
returned error exit status 1
  InstallationDate: Installed on 2023-08-22 (1 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-213-generic 
root=UUID=c5495aa8-cf2c-4042-a2ea-4533e9343808 ro quiet splash vt.handoff=1
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3.2
   apt  2.0.9
  SourcePackage: apparmor
  Syslog:
   Aug 24 02:04:25 adminn-Lenovo-V110-15ISK dbus-daemon[4678]: [session 
uid=1000 pid=4678] AppArmor D-Bus mediation is enabled
   Aug 24 02:05:26 adminn-Lenovo-V110-15ISK dbus-daemon[856]: [system] AppArmor 
D-Bus mediation is enabled
   Aug 24 02:05:31 adminn-Lenovo-V110-15ISK dbus-daemon[1021]: [session uid=124 
pid=1021] AppArmor D-Bus mediation is enabled
   Aug 24 02:06:04 adminn-Lenovo-V110-15ISK dbus-daemon[1506]: [session 
uid=1000 pid=1506] AppArmor D-Bus mediation is enabled
   Aug 24 03:39:11 adminn-Lenovo-V110-15ISK dbus-daemon[9963]: [session uid=0 
pid=9956] AppArmor D-Bus mediation is enabled
  Title: package apparmor 2.12-4ubuntu5.3 failed to install/upgrade: new 
apparmor package pre-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/apparmor/+bug/2032851/+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 2024560] Re: Check if 0010-set-language needs to be update for the new languages property

[Sebastien Bacher]

We didn't get any other reports about it so I guess it's fine now, let's
close

** Changed in: accountsservice (Ubuntu)
   Status: Incomplete => Fix Released

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

Title:
  Check if 0010-set-language needs to be update for the new languages
  property

Status in accountsservice package in Ubuntu:
  Fix Released

Bug description:
  Upstream did changes to add a languages properties

  
https://gitlab.freedesktop.org/accountsservice/accountsservice/-/commit/881e0ea7

  I've rebased 0010-set-language to apply correctly but we should review
  if we need to adapt the patch to apply a similar logic to the new
  languages property that it's doing for old language one

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/2024560/+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 2024560] Re: Check if 0010-set-language needs to be update for the new languages property

[Gunnar Hjalmarsson]

@Sebastien: Is this bug ready to be closed again?

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

Title:
  Check if 0010-set-language needs to be update for the new languages
  property

Status in accountsservice package in Ubuntu:
  Incomplete

Bug description:
  Upstream did changes to add a languages properties

  
https://gitlab.freedesktop.org/accountsservice/accountsservice/-/commit/881e0ea7

  I've rebased 0010-set-language to apply correctly but we should review
  if we need to adapt the patch to apply a similar logic to the new
  languages property that it's doing for old language one

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/2024560/+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 2033282] [NEW] package apparmor 2.12-4ubuntu5.3 failed to install/upgrade: yeni apparmor paketi pre-installation betiği alt süreci 1 hatalı çıkış kodu ile sona erdi

[cagri]

Public bug reported:

SORUN YAŞTIYOR

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: apparmor 2.12-4ubuntu5.3
ProcVersionSignature: Ubuntu 5.4.0-150.167~18.04.1-generic 5.4.233
Uname: Linux 5.4.0-150-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.29
Architecture: amd64
Date: Mon Aug 28 15:09:33 2023
ErrorMessage: yeni apparmor paketi pre-installation betiği alt süreci 1 hatalı 
çıkış kodu ile sona erdi
InstallationDate: Installed on 2023-08-28 (0 days ago)
InstallationMedia: Ubuntu 18.04.6 LTS "Bionic Beaver" - Release amd64 (20210915)
ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-150-generic 
root=UUID=cf42fc8c-3bc3-4454-8d4e-02385791533a ro quiet splash vt.handoff=7
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3.2
 apt  2.0.9
SourcePackage: apparmor
Title: package apparmor 2.12-4ubuntu5.3 failed to install/upgrade: yeni 
apparmor paketi pre-installation betiği alt süreci 1 hatalı çıkış kodu ile sona 
erdi
UpgradeStatus: Upgraded to focal on 2023-08-28 (0 days ago)

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


** Tags: amd64 apport-package focal

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

Title:
  package apparmor 2.12-4ubuntu5.3 failed to install/upgrade: yeni
  apparmor paketi pre-installation betiği alt süreci 1 hatalı çıkış kodu
  ile sona erdi

Status in apparmor package in Ubuntu:
  New

Bug description:
  SORUN YAŞTIYOR

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: apparmor 2.12-4ubuntu5.3
  ProcVersionSignature: Ubuntu 5.4.0-150.167~18.04.1-generic 5.4.233
  Uname: Linux 5.4.0-150-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.29
  Architecture: amd64
  Date: Mon Aug 28 15:09:33 2023
  ErrorMessage: yeni apparmor paketi pre-installation betiği alt süreci 1 
hatalı çıkış kodu ile sona erdi
  InstallationDate: Installed on 2023-08-28 (0 days ago)
  InstallationMedia: Ubuntu 18.04.6 LTS "Bionic Beaver" - Release amd64 
(20210915)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-150-generic 
root=UUID=cf42fc8c-3bc3-4454-8d4e-02385791533a ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3.2
   apt  2.0.9
  SourcePackage: apparmor
  Title: package apparmor 2.12-4ubuntu5.3 failed to install/upgrade: yeni 
apparmor paketi pre-installation betiği alt süreci 1 hatalı çıkış kodu ile sona 
erdi
  UpgradeStatus: Upgraded to focal on 2023-08-28 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2033282/+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 2033275] Re: Constant audio problems making Ubuntu unusable [hostname, Realtek ALC295, Speaker, Internal] fails after a while

[Ubuntu Foundations Team Bug Bot]

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

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

Title:
  Constant audio problems making Ubuntu unusable [hostname, Realtek
  ALC295, Speaker, Internal] fails after a while

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Really wanted to switch to Ubuntu but there are always some problems.
  It's frustrating. Now, sound doesn't work again (after it fixed itself
  previously for no apparent reason). It just starts playing and
  literally dies out immediately (fades into silence with weird sound
  distortion). Please help.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13
  Uname: Linux 6.2.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tobey 16688 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug 28 12:37:23 2023
  InstallationDate: Installed on 2023-03-09 (171 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_PulseAudioLog:
   
  Symptom_Type: Sound works for a while, then breaks
  Title: [hostname, Realtek ALC295, Speaker, Internal] fails after a while
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/19/2019
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX550VD.307
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX550VD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX550VD.307:bd04/19/2019:br5.12:svnASUSTeKCOMPUTERINC.:pnUX550VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX550VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: ZenBook
  dmi.product.name: UX550VD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2033275/+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 2033275] [NEW] Constant audio problems making Ubuntu unusable [hostname, Realtek ALC295, Speaker, Internal] fails after a while

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Really wanted to switch to Ubuntu but there are always some problems.
It's frustrating. Now, sound doesn't work again (after it fixed itself
previously for no apparent reason). It just starts playing and literally
dies out immediately (fades into silence with weird sound distortion).
Please help.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: alsa-base 1.0.25+dfsg-0ubuntu7
ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13
Uname: Linux 6.2.0-26-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  tobey 16688 F pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Aug 28 12:37:23 2023
InstallationDate: Installed on 2023-03-09 (171 days ago)
InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_Jack: Speaker, Internal
Symptom_PulseAudioLog:
 
Symptom_Type: Sound works for a while, then breaks
Title: [hostname, Realtek ALC295, Speaker, Internal] fails after a while
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/19/2019
dmi.bios.release: 5.12
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX550VD.307
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX550VD
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX550VD.307:bd04/19/2019:br5.12:svnASUSTeKCOMPUTERINC.:pnUX550VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX550VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
dmi.product.family: ZenBook
dmi.product.name: UX550VD
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


** Tags: amd64 apport-bug jammy
-- 
Constant audio problems making Ubuntu unusable [hostname, Realtek ALC295, 
Speaker, Internal] fails after a while
https://bugs.launchpad.net/bugs/2033275
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to alsa-driver 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 2031942] Re: AuthorizedPrincipalsCommand is ignored if AuthorizedKeysCommand is set

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~michal-maloszewski99/ubuntu/+source/openssh/+git/openssh/+merge/450039

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

Title:
  AuthorizedPrincipalsCommand is ignored if AuthorizedKeysCommand is set

Status in openssh package in Ubuntu:
  In Progress
Status in openssh source package in Jammy:
  In Progress
Status in openssh source package in Lunar:
  In Progress
Status in openssh source package in Mantic:
  In Progress

Bug description:
  Versions of OpenSSH from 8.7p1 to 9.3p1 contain the following code:

  if (*activep && options->authorized_keys_command == NULL)
  *charptr = xstrdup(str + len);

  However, this is executed for both authorized_keys_command and
  authorized_principals_command. As a result, if authorized_keys_command
  is set (for instance, if using ec2-instance-connect), any
  AuthorizedPrincipalsCommand configuration in sshd_config is ignored.
  This is fixed in 9.4p1 with the attached patch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2031942/+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 2033262] Re: Ubuntu mantic live session (desktop)_& `apt install` ends with "Error: Timeout was reached"

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
https://iso.qa.ubuntu.com/qatracker/reports/bugs/2033262

** Tags added: iso-testing

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

Title:
  Ubuntu mantic live session (desktop)_& `apt install` ends with "Error:
  Timeout was reached"

Status in apt package in Ubuntu:
  New

Bug description:
  Running a Ubuntu Desktop mantic live session on
  - dell [optiplex] 780 (c2q-q9400, 8gb, amd/ati cedar radeon hd 
5000/6000/7350/8350)

  ** steps to create

  - boot & ubuntu mantic daily; select 'TRY'
  - wait for boot to complete
  - open terminal (ctrl+alt+t)
  - sudo apt update
  - sudo apt install vlc

  ** expected results

  package & requirements install

  ** actual result

  Setting up libheif-plugin-aomenc:amd64 (1.16.2-2ubuntu1) ...
  Processing triggers for libc-bin (2.38-1ubuntu3) ...
  Processing triggers for man-db (2.11.2-3) ...
  Error: Timeout was reached

  ** comments

  this was repeated twice, same result.

  PROBLEM MAYBE ONLY FINAL ERROR MESSAGE SHOWN on terminal, ie. ending
  with "Error: Timeout was reached" as I can use the packages that I
  installed.. though my running `apt install -f` was because of the
  final error message

  also occurred with `sudo apt install gstreamer1.0-plugins-bad`

  ** actual paste of terminal  (top redacted)

  rocessing triggers for libc-bin (2.38-1ubuntu3) ...
  Processing triggers for man-db (2.11.2-3) ...
  Error: Timeout was reached
  ubuntu@ubuntu:~$   sudo apt -f install
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  0 upgraded, 0 newly installed, 0 to remove and 195 not upgraded.
  ubuntu@ubuntu:~$ sudo apt install vlc
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  The following additional packages will be installed:
    fonts-freefont-ttf liba52-0.7.4 libaacs0 libaribb24-0 libavformat60 
libbdplus0 libbluray2 libcddb2 libcjson1
    libdouble-conversion3 libdvbpsi10 libebml5 libgnutls30 libixml11 
liblirc-client0 liblua5.2-0 libmad0 libmatroska7
    libmbedcrypto7 libmd4c0 libmpeg2-4 libmysofa1 libnorm1 libopenmpt-modplug1 
libp11-kit0 libpcre2-16-0 libpcre2-32-0
    libpcre2-8-0 libpgm-5.3-0 libpostproc57 libprotobuf-lite32 libproxy-tools 
libqt5core5a libqt5dbus5 libqt5gui5
    libqt5network5 libqt5qml5 libqt5qmlmodels5 libqt5quick5 libqt5svg5 
libqt5waylandclient5 libqt5waylandcompositor5
    libqt5widgets5 libqt5x11extras5 librabbitmq4 libresid-builder0c2a librist4 
libsidplay2 libspatialaudio0
    libspeexdsp1 libssh-gcrypt-4 libssh2-1 libswscale7 libudfread0 libupnp17 
libva-wayland2 libvlc-bin libvlc5
    libvlccore9 libvncclient1 libxcb-composite0 libxcb-xinerama0 libxcb-xinput0 
libzmq5 p11-kit p11-kit-modules
    qt5-gtk-platformtheme qttranslations5-l10n qtwayland5 vlc-bin vlc-data 
vlc-l10n vlc-plugin-access-extra
    vlc-plugin-base vlc-plugin-notify vlc-plugin-qt vlc-plugin-samba 
vlc-plugin-skins2 vlc-plugin-video-output
    vlc-plugin-video-splitter vlc-plugin-visualization
  Suggested packages:
    libbluray-bdj gnutls-bin lirc qgnomeplatform-qt5 qt5-image-formats-plugins 
qt5-qmltooling-plugins
    vlc-plugin-fluidsynth vlc-plugin-jack vlc-plugin-pipewire vlc-plugin-svg 
libdvdcss2
  The following NEW packages will be installed:
    fonts-freefont-ttf liba52-0.7.4 libaacs0 libaribb24-0 libavformat60 
libbdplus0 libbluray2 libcddb2 libcjson1
    libdouble-conversion3 libdvbpsi10 libebml5 libixml11 liblirc-client0 
liblua5.2-0 libmad0 libmatroska7
    libmbedcrypto7 libmd4c0 libmpeg2-4 libmysofa1 libnorm1 libopenmpt-modplug1 
libpcre2-16-0 libpgm-5.3-0 libpostproc57
    libprotobuf-lite32 libproxy-tools libqt5core5a libqt5dbus5 libqt5gui5 
libqt5network5 libqt5qml5 libqt5qmlmodels5
    libqt5quick5 libqt5svg5 libqt5waylandclient5 libqt5waylandcompositor5 
libqt5widgets5 libqt5x11extras5 librabbitmq4
    libresid-builder0c2a librist4 libsidplay2 libspatialaudio0 libspeexdsp1 
libssh-gcrypt-4 libssh2-1 libswscale7
    libudfread0 libupnp17 libva-wayland2 libvlc-bin libvlc5 libvlccore9 
libvncclient1 libxcb-composite0
    libxcb-xinerama0 libxcb-xinput0 libzmq5 qt5-gtk-platformtheme 
qttranslations5-l10n qtwayland5 vlc vlc-bin vlc-data
    vlc-l10n vlc-plugin-access-extra vlc-plugin-base vlc-plugin-notify 
vlc-plugin-qt vlc-plugin-samba vlc-plugin-skins2
    vlc-plugin-video-output vlc-plugin-video-splitter vlc-plugin-visualization
  The following packages will be upgraded:
    libgnutls30 libp11-kit0 libpcre2-32-0 libpcre2-8-0 p11-kit p11-kit-modules
  6 upgraded, 76 newly installed, 0 to remove and 189 not upgraded.
  Need to get 0 B/41.9 MB of archives.
  After this operation, 158 MB of additional disk space will be used.
  Do you want to continue? [Y/n] y
  Extracting 

[Touch-packages] [Bug 2022927] Re: Busybox mount fails to mount Snaps

[Isaac True]

@paelzer unfortunately I've had no response yet from the mailing list
regarding this...

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

Title:
  Busybox mount fails to mount Snaps

Status in busybox package in Ubuntu:
  New

Bug description:
  Snapd tries to mount squashfs Snaps with non-standard mount flags like
  "x-gdu.hide" and "x-gvfs-hide", both of which are used to indicate to
  userspace programs that a given mount should not be shown in a list of
  mounted partitions/filesystems. Busybox does not support these flags,
  and so fails with "Invalid argument".

  $ sudo busybox mount -t tmpfs -o x-gdu-hide test /tmp/test
  mount: mounting test on /tmp/test failed: Invalid argument

  These flags can likely be be safely ignored, as they don't actually
  affect the functionality of the mount. This goes for all mount options
  starting with "x-", as these generally denote non-standard mount
  option "extensions".

  I've created a patch against Busybox which adds an optional
  configuration item to ignore all mount options beginning with "x-". An
  additional verbose option has also been added to enable the ability to
  report that the mount flags have been ignored, rather than silently
  ignoring them.

  This is a requirement for a customer project, where we are limited to
  using Busybox (due to coreutils' GPL-3.0 licence) but would also
  require using Snaps like checkbox for testing and verification. This
  was posted on the Busybox mailing list a few months ago
  (http://lists.busybox.net/pipermail/busybox/2023-March/090202.html)
  but patch acceptance there seems to take quite a long time, and we
  need this for the customer.

  A PPA containing the patched Busybox version is available on the
  project's Launchpad team: https://launchpad.net/~nemos-
  team/+archive/ubuntu/ppa

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/2022927/+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 1881554] Re: PCI/internal sound card not detected

[Daniel van Vugt]

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

Thank you for reporting this bug to Ubuntu.

Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested
in discussing it anymore. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in.

** Changed in: alsa-driver (Ubuntu)
   Status: New => Incomplete

** Summary changed:

- PCI/internal sound card not detected
+ [Dell Inspiron 5567] PCI/internal sound card not detected

** Package changed: alsa-driver (Ubuntu) => linux (Ubuntu)

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

Title:
  [Dell Inspiron 5567] PCI/internal sound card not detected

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  No sound

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-179.209-generic 4.4.219
  Uname: Linux 4.4.0-179-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.23
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  Date: Mon Jun  1 15:11:24 2020
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  InstallationDate: Installed on 2020-05-31 (1 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/14/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.5
  dmi.board.name: 0DG5G3
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A03
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.5:bd05/14/2018:svnDellInc.:pnInspiron5567:pvr:rvnDellInc.:rn0DG5G3:rvrA03:cvnDellInc.:ct10:cvr:
  dmi.product.name: Inspiron 5567
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-06-01T14:54:04.434257

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881554/+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 1682322] Re: PCI/internal sound card not detected dummy drive only on Dell Inspiron 5567

[Daniel van Vugt]

Thank you for reporting this bug to Ubuntu.

Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested
in discussing it anymore. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in.

** Package changed: alsa-driver (Ubuntu) => linux (Ubuntu)

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

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

Title:
  PCI/internal sound card not detected dummy drive only on Dell Inspiron
  5567

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  only the dummy drive is showing in my sound preferences

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  Uname: Linux 4.8.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp3', '/dev/dsp2', 
'/dev/dsp1', '/dev/dsp', '/dev/snd/seq', '/dev/snd/timer', '/dev/sequencer'] 
failed with exit code 1:
  CurrentDesktop: Unity
  Date: Thu Apr 13 12:53:46 2017
  InstallationDate: Installed on 2017-04-05 (7 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/30/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.9
  dmi.board.name: 01W6F7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.9:bd11/30/2016:svnDellInc.:pnInspiron5567:pvr:rvnDellInc.:rn01W6F7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.name: Inspiron 5567
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1682322/+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 2033262] Re: Ubuntu mantic live session (desktop)_& `apt install` ends with "Error: Timeout was reached"

[Chris Guiver]

** Description changed:

  Running a Ubuntu Desktop mantic live session on
  - dell optiplex 780
  
- ** apt install vlc
- 
+ ** steps to create
+ 
+ - boot & ubuntu mantic daily; select 'TRY'
+ - wait for boot to complete
  - open terminal (ctrl+alt+t)
  - sudo apt update
  - sudo apt install vlc
  
  ** expected results
  
  package & requirements install
  
  ** actual result
  
- Setting up libmagickwand-6.q16-6:amd64 (8:6.9.11.60+dfsg-1.6ubuntu1) ...
- Setting up libheif-plugin-dav1d:amd64 (1.16.2-2ubuntu1) ...
- Setting up libheif-plugin-libde265:amd64 (1.16.2-2ubuntu1) ...
- Setting up libmagickcore-6.q16-6-extra:amd64 (8:6.9.11.60+dfsg-1.6ubuntu1) ...
- Setting up libheif-plugin-x265:amd64 (1.16.2-2ubuntu1) ...
  Setting up libheif-plugin-aomenc:amd64 (1.16.2-2ubuntu1) ...
  Processing triggers for libc-bin (2.38-1ubuntu3) ...
  Processing triggers for man-db (2.11.2-3) ...
  Error: Timeout was reached
  
- **
- 
- this was repeated twice, same result
+ ** comments
+ 
+ this was repeated twice, same result.
+ 
+ PROBLEM MAYBE ONLY FINAL ERROR MESSAGE SHOWN on terminal, ie. ending
+ with "Error: Timeout was reached" as I can use the packages that I
+ installed.. though my running `apt install -f` was because of the final
+ error message
  
  also occurred with `sudo apt install gstreamer1.0-plugins-bad`
  
  ** actual paste of terminal  (top redacted)
  
  rocessing triggers for libc-bin (2.38-1ubuntu3) ...
  Processing triggers for man-db (2.11.2-3) ...
  Error: Timeout was reached
  ubuntu@ubuntu:~$   sudo apt -f install
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  0 upgraded, 0 newly installed, 0 to remove and 195 not upgraded.
  ubuntu@ubuntu:~$ sudo apt install vlc
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  The following additional packages will be installed:
-   fonts-freefont-ttf liba52-0.7.4 libaacs0 libaribb24-0 libavformat60 
libbdplus0 libbluray2 libcddb2 libcjson1
-   libdouble-conversion3 libdvbpsi10 libebml5 libgnutls30 libixml11 
liblirc-client0 liblua5.2-0 libmad0 libmatroska7
-   libmbedcrypto7 libmd4c0 libmpeg2-4 libmysofa1 libnorm1 libopenmpt-modplug1 
libp11-kit0 libpcre2-16-0 libpcre2-32-0
-   libpcre2-8-0 libpgm-5.3-0 libpostproc57 libprotobuf-lite32 libproxy-tools 
libqt5core5a libqt5dbus5 libqt5gui5
-   libqt5network5 libqt5qml5 libqt5qmlmodels5 libqt5quick5 libqt5svg5 
libqt5waylandclient5 libqt5waylandcompositor5
-   libqt5widgets5 libqt5x11extras5 librabbitmq4 libresid-builder0c2a librist4 
libsidplay2 libspatialaudio0
-   libspeexdsp1 libssh-gcrypt-4 libssh2-1 libswscale7 libudfread0 libupnp17 
libva-wayland2 libvlc-bin libvlc5
-   libvlccore9 libvncclient1 libxcb-composite0 libxcb-xinerama0 libxcb-xinput0 
libzmq5 p11-kit p11-kit-modules
-   qt5-gtk-platformtheme qttranslations5-l10n qtwayland5 vlc-bin vlc-data 
vlc-l10n vlc-plugin-access-extra
-   vlc-plugin-base vlc-plugin-notify vlc-plugin-qt vlc-plugin-samba 
vlc-plugin-skins2 vlc-plugin-video-output
-   vlc-plugin-video-splitter vlc-plugin-visualization
+   fonts-freefont-ttf liba52-0.7.4 libaacs0 libaribb24-0 libavformat60 
libbdplus0 libbluray2 libcddb2 libcjson1
+   libdouble-conversion3 libdvbpsi10 libebml5 libgnutls30 libixml11 
liblirc-client0 liblua5.2-0 libmad0 libmatroska7
+   libmbedcrypto7 libmd4c0 libmpeg2-4 libmysofa1 libnorm1 libopenmpt-modplug1 
libp11-kit0 libpcre2-16-0 libpcre2-32-0
+   libpcre2-8-0 libpgm-5.3-0 libpostproc57 libprotobuf-lite32 libproxy-tools 
libqt5core5a libqt5dbus5 libqt5gui5
+   libqt5network5 libqt5qml5 libqt5qmlmodels5 libqt5quick5 libqt5svg5 
libqt5waylandclient5 libqt5waylandcompositor5
+   libqt5widgets5 libqt5x11extras5 librabbitmq4 libresid-builder0c2a librist4 
libsidplay2 libspatialaudio0
+   libspeexdsp1 libssh-gcrypt-4 libssh2-1 libswscale7 libudfread0 libupnp17 
libva-wayland2 libvlc-bin libvlc5
+   libvlccore9 libvncclient1 libxcb-composite0 libxcb-xinerama0 libxcb-xinput0 
libzmq5 p11-kit p11-kit-modules
+   qt5-gtk-platformtheme qttranslations5-l10n qtwayland5 vlc-bin vlc-data 
vlc-l10n vlc-plugin-access-extra
+   vlc-plugin-base vlc-plugin-notify vlc-plugin-qt vlc-plugin-samba 
vlc-plugin-skins2 vlc-plugin-video-output
+   vlc-plugin-video-splitter vlc-plugin-visualization
  Suggested packages:
-   libbluray-bdj gnutls-bin lirc qgnomeplatform-qt5 qt5-image-formats-plugins 
qt5-qmltooling-plugins
-   vlc-plugin-fluidsynth vlc-plugin-jack vlc-plugin-pipewire vlc-plugin-svg 
libdvdcss2
+   libbluray-bdj gnutls-bin lirc qgnomeplatform-qt5 qt5-image-formats-plugins 
qt5-qmltooling-plugins
+   vlc-plugin-fluidsynth vlc-plugin-jack vlc-plugin-pipewire vlc-plugin-svg 
libdvdcss2
  The following NEW packages will be installed:
-   fonts-freefont-ttf liba52-0.7.4 libaacs0 libaribb24-0 libavformat60 
libbdplus0 libbluray2 libcddb2 libcjson1
-   libdouble-conversion3 libdvbpsi10 libebml5 libixml11 liblirc-client0 
liblua5.2-0 libmad0 libmatroska7
-   

[Touch-packages] [Bug 2033262] [NEW] Ubuntu mantic live session (desktop)_& `apt install` ends with "Error: Timeout was reached"

[Chris Guiver]

Public bug reported:

Running a Ubuntu Desktop mantic live session on
- dell optiplex 780

** apt install vlc

- open terminal (ctrl+alt+t)
- sudo apt update
- sudo apt install vlc

** expected results

package & requirements install

** actual result

Setting up libmagickwand-6.q16-6:amd64 (8:6.9.11.60+dfsg-1.6ubuntu1) ...
Setting up libheif-plugin-dav1d:amd64 (1.16.2-2ubuntu1) ...
Setting up libheif-plugin-libde265:amd64 (1.16.2-2ubuntu1) ...
Setting up libmagickcore-6.q16-6-extra:amd64 (8:6.9.11.60+dfsg-1.6ubuntu1) ...
Setting up libheif-plugin-x265:amd64 (1.16.2-2ubuntu1) ...
Setting up libheif-plugin-aomenc:amd64 (1.16.2-2ubuntu1) ...
Processing triggers for libc-bin (2.38-1ubuntu3) ...
Processing triggers for man-db (2.11.2-3) ...
Error: Timeout was reached

**

this was repeated twice, same result

also occurred with `sudo apt install gstreamer1.0-plugins-bad`

** actual paste of terminal  (top redacted)

rocessing triggers for libc-bin (2.38-1ubuntu3) ...
Processing triggers for man-db (2.11.2-3) ...
Error: Timeout was reached
ubuntu@ubuntu:~$   sudo apt -f install
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 195 not upgraded.
ubuntu@ubuntu:~$ sudo apt install vlc
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following additional packages will be installed:
  fonts-freefont-ttf liba52-0.7.4 libaacs0 libaribb24-0 libavformat60 
libbdplus0 libbluray2 libcddb2 libcjson1
  libdouble-conversion3 libdvbpsi10 libebml5 libgnutls30 libixml11 
liblirc-client0 liblua5.2-0 libmad0 libmatroska7
  libmbedcrypto7 libmd4c0 libmpeg2-4 libmysofa1 libnorm1 libopenmpt-modplug1 
libp11-kit0 libpcre2-16-0 libpcre2-32-0
  libpcre2-8-0 libpgm-5.3-0 libpostproc57 libprotobuf-lite32 libproxy-tools 
libqt5core5a libqt5dbus5 libqt5gui5
  libqt5network5 libqt5qml5 libqt5qmlmodels5 libqt5quick5 libqt5svg5 
libqt5waylandclient5 libqt5waylandcompositor5
  libqt5widgets5 libqt5x11extras5 librabbitmq4 libresid-builder0c2a librist4 
libsidplay2 libspatialaudio0
  libspeexdsp1 libssh-gcrypt-4 libssh2-1 libswscale7 libudfread0 libupnp17 
libva-wayland2 libvlc-bin libvlc5
  libvlccore9 libvncclient1 libxcb-composite0 libxcb-xinerama0 libxcb-xinput0 
libzmq5 p11-kit p11-kit-modules
  qt5-gtk-platformtheme qttranslations5-l10n qtwayland5 vlc-bin vlc-data 
vlc-l10n vlc-plugin-access-extra
  vlc-plugin-base vlc-plugin-notify vlc-plugin-qt vlc-plugin-samba 
vlc-plugin-skins2 vlc-plugin-video-output
  vlc-plugin-video-splitter vlc-plugin-visualization
Suggested packages:
  libbluray-bdj gnutls-bin lirc qgnomeplatform-qt5 qt5-image-formats-plugins 
qt5-qmltooling-plugins
  vlc-plugin-fluidsynth vlc-plugin-jack vlc-plugin-pipewire vlc-plugin-svg 
libdvdcss2
The following NEW packages will be installed:
  fonts-freefont-ttf liba52-0.7.4 libaacs0 libaribb24-0 libavformat60 
libbdplus0 libbluray2 libcddb2 libcjson1
  libdouble-conversion3 libdvbpsi10 libebml5 libixml11 liblirc-client0 
liblua5.2-0 libmad0 libmatroska7
  libmbedcrypto7 libmd4c0 libmpeg2-4 libmysofa1 libnorm1 libopenmpt-modplug1 
libpcre2-16-0 libpgm-5.3-0 libpostproc57
  libprotobuf-lite32 libproxy-tools libqt5core5a libqt5dbus5 libqt5gui5 
libqt5network5 libqt5qml5 libqt5qmlmodels5
  libqt5quick5 libqt5svg5 libqt5waylandclient5 libqt5waylandcompositor5 
libqt5widgets5 libqt5x11extras5 librabbitmq4
  libresid-builder0c2a librist4 libsidplay2 libspatialaudio0 libspeexdsp1 
libssh-gcrypt-4 libssh2-1 libswscale7
  libudfread0 libupnp17 libva-wayland2 libvlc-bin libvlc5 libvlccore9 
libvncclient1 libxcb-composite0
  libxcb-xinerama0 libxcb-xinput0 libzmq5 qt5-gtk-platformtheme 
qttranslations5-l10n qtwayland5 vlc vlc-bin vlc-data
  vlc-l10n vlc-plugin-access-extra vlc-plugin-base vlc-plugin-notify 
vlc-plugin-qt vlc-plugin-samba vlc-plugin-skins2
  vlc-plugin-video-output vlc-plugin-video-splitter vlc-plugin-visualization
The following packages will be upgraded:
  libgnutls30 libp11-kit0 libpcre2-32-0 libpcre2-8-0 p11-kit p11-kit-modules
6 upgraded, 76 newly installed, 0 to remove and 189 not upgraded.
Need to get 0 B/41.9 MB of archives.
After this operation, 158 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Extracting templates from packages: 100%
(Reading database ... 162285 files and directories currently installed.)
Preparing to unpack .../libpcre2-8-0_10.42-3_amd64.deb ...
Unpacking libpcre2-8-0:amd64 (10.42-3) over (10.42-2) ...
Setting up libpcre2-8-0:amd64 (10.42-3) ...
(Reading database ... 162285 files and directories currently installed.)
Preparing to unpack .../p11-kit-modules_0.25.0-4ubuntu1_amd64.deb ...
Unpacking p11-kit-modules:amd64 (0.25.0-4ubuntu1) over (0.24.1-2ubuntu1) ...
Preparing to unpack .../libp11-kit0_0.25.0-4ubuntu1_amd64.deb ...
Unpacking libp11-kit0:amd64 (0.25.0-4ubuntu1) over (0.24.1-2ubuntu1) ...
Setting up libp11-kit0:amd64 (0.25.0-4ubuntu1) ...
(Reading database ... 

[Touch-packages] [Bug 2012902] Re: netplan plugin: generated NM config when using globbing will be used for only one connection

[Lukas Märdian]

** Tags added: foundations-todo

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

Title:
  netplan plugin: generated NM config when using globbing will be used
  for only one connection

Status in netplan:
  Triaged
Status in network-manager package in Ubuntu:
  New

Bug description:
  There is a mismatch between what netplan expresses when using globbing
  in a netplan file and what NM understands when using a match setting.
  For instance:

  network:
  version: 2
  ethernets:
  all-en:
  match:
  name: "en*"
  dhcp4: true

  Generates a NM connection in /run/NetworkManager/system-connections:

  ...
  [match]
  interface-name=en*;
  ...

  But an NM connection can only match one interface, so if two
  interfaces like ens2 and ens3 exist, only one of them will be
  configured, even though the netplan configuration is expected to be
  applied to both.

  Solving this might involve generating one NM connection in the netplan
  plugin per detected interface.

To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/2012902/+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 2029438] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From boris.m...@de.ibm.com 2023-08-28 04:22 EDT---
Thanks @Canonical for catching this.
Thank you Stefan for your fix & successful verification.

The updated package has been included in Mantic, therefore we can close
this bug.

==> Changing the status to: "CLOSED"

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

Title:
  gmp z13 config fails with illegal instructions

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in gmp package in Ubuntu:
  Fix Released

Bug description:
  seen with 
  https://launchpad.net/ubuntu/+source/gmp/2:6.3.0+dfsg-2ubuntu2/+build/26470068

  Note, that MPN_PATH is now unset in 2:6.3.0+dfsg-2ubuntu3

  [...]
  ../../../test-driver: line 112: 76812 Illegal instruction (core dumped) 
"$@" >> "$log_file" 2>&1
  FAIL: t-hamdist
  PASS: t-oddeven
  ../../../test-driver: line 112: 76824 Illegal instruction (core dumped) 
"$@" >> "$log_file" 2>&1
  FAIL: t-popcount
  PASS: t-set_f
  PASS: t-io_raw
  PASS: t-import
  PASS: t-export
  PASS: t-pprime_p
  ../../../test-driver: line 112: 76856 Illegal instruction (core dumped) 
"$@" >> "$log_file" 2>&1
  FAIL: t-nextprime
  PASS: t-remove
  PASS: t-limbs
  
  Testsuite summary for GNU MP 6.3.0
  
  # TOTAL: 64
  # PASS:  57
  # SKIP:  0
  # XFAIL: 0
  # FAIL:  7
  # XPASS: 0
  # ERROR: 0
  
  See tests/mpz/test-suite.log
  Please report to gmp-b...@gmplib.org (see 
https://gmplib.org/manual/Reporting-Bugs.html)

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