[Touch-packages] [Bug 1981190] Re: Fibcom FM350-GL not able connect to network with 5G mode

[Dirk Su]

5G function enabled with ModemManager 1.20.0-1

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

** Changed in: libqmi (Ubuntu)
   Status: Confirmed => Fix Released

** Changed in: libmbim (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Fibcom FM350-GL not able connect to network with 5G mode

Status in libmbim package in Ubuntu:
  Fix Released
Status in libqmi package in Ubuntu:
  Fix Released
Status in modemmanager package in Ubuntu:
  Fix Released

Bug description:
  Fibcom FM350-GL can support 5G network
  (https://www.fibocom.com/en/products/5G-FM350-GL.html). But in Ubuntu
  22.04, system can only connect to mobile network with 4G mode.


General  | path: /org/freedesktop/ModemManager1/Modem/0
 |device id: e045a43cd7977e24e1a11af409a780c054e26b0e

Hardware | manufacturer: generic
 |model: MBIM [14C3:4D75]
 |firmware revision: 81600..00.29.18.01_GC
 |   C01
 | h/w revision: V1.0.6
 |supported: gsm-umts, lte
 |  current: gsm-umts, lte
 | equipment id: 352750140002001

System   |   device: 
/sys/devices/pci:00/:00:1c.0/:73:00.0
 |  drivers: mtk_t7xx
 |   plugin: generic
 | primary port: wwan0mbim0
 |ports: wwan0 (net), wwan0at0 (at), wwan0mbim0 
(mbim)

Status   |   unlock retries: sim-pin (3), sim-pin2 (3)
 |state: connected
 |  power state: on
 |  access tech: lte
 |   signal quality: 74% (recent)

Modes|supported: allowed: 3g, 4g; preferred: none
 |  current: allowed: 3g, 4g; preferred: none

IP   |supported: ipv4, ipv6, ipv4v6

3GPP | imei: 352750140002001
 |enabled locks: sim, fixed-dialing
 |  operator id: 46692
 |operator name: Chunghwa Telecom
 | registration: home

3GPP EPS | ue mode of operation: csps-2
 |  initial bearer path: /org/freedesktop/ModemManager1/Bearer/0

SIM  | primary sim path: /org/freedesktop/ModemManager1/SIM/0

Bearer   |paths: /org/freedesktop/ModemManager1/Bearer/1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-06-15 (26 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: modemmanager 1.18.6-1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.17.0-9012.13+exp.27-oem 5.17.9
  Tags:  jammy
  Uname: Linux 5.17.0-9012-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/1981190/+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 1300620] Re: [Lenovo ThinkPad S1 Yoga] Middle button does not work for scrolling

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

Title:
  [Lenovo ThinkPad S1 Yoga] Middle button does not work for scrolling

Status in xorg package in Ubuntu:
  Expired

Bug description:
  On my clickpad (Touchpad with no button) the middle mouse button
  doesn't work for scrolling with trackpoint. I've configured a soft
  middlemouse button area via the following script:

  
  #!/bin/bash
  TOUCHPAD="SynPS/2 Synaptics TouchPad"
  TRACKPOINT="TPPS/2 IBM TrackPoint"
  killall -9 syndaemon
  echo "touchpad on"
  xinput set-prop "${TOUCHPAD}" "Synaptics Off" 0

  echo "setting soft button areas"
  #Order: RightButtonAreaLeft, RightButtonAreaRight, RightButtonAreaTop, 
RightButtonAreaBottom, MiddleButtonAreaLeft, MiddleButtonAreaRight, 
MitddleButtonAreaTop, MiddleButtonAreaBottom"
  xinput set-prop "${TOUCHPAD}" "Synaptics Soft Button Areas" 4000, 0, 4063, 0, 
3000, 4000, 4063, 1500
  #xinput set-prop "${TOUCHPAD}" "Synaptics Soft Button Areas" 4000, 0, 0, 
4466, 3000, 3999, 0, 1500

  echo "enable twofingerscrolling in both directions"
  xinput set-prop "${TOUCHPAD}" "Synaptics Two-Finger Scrolling" 1, 1

  echo "shortening upper and lower edge to reserve space for 'just button' 
actions. Order: left, right, top, bottom"
  xinput set-prop "${TOUCHPAD}" "Synaptics Area" 0, 0, 1500, 4000
  #workaround for just scrolling
  #xinput set-prop "${TOUCHPAD}" "Synaptics Area" 0, 4000, 1500, 0

  echo "enabling palm detection"
  xinput set-prop "${TOUCHPAD}" "Synaptics Palm Detection" 1

  #echo "Middle mouse button emulation for scrolling on trackpoint"
  #xinput set-prop "${TRACKPOINT}" "Evdev Wheel Emulation" 1
  #xinput set-prop "${TRACKPOINT}" "Evdev Wheel Emulation Button" 2
  #xinput set-prop "${TRACKPOINT}" "Evdev Wheel Emulation Timeout" 200
  #xinput set-prop "${TRACKPOINT}" "Evdev Wheel Emulation Axes" 6 7 4 5 # 
horizontal und vertikal

  echo "enable tap events"
  # RTCornerButton, RBCornerButton, LTCornerButton, LBCornerButton, TapButton1, 
TapButton2, TapButton3
  xinput set-prop "${TOUCHPAD}" "Synaptics Tap Action" 2, 3, 1, 1, 1, 3, 0

  echo "list actual properties"
  xinput list-props "${TOUCHPAD}"

  echo "no touch while typing"
  syndaemon -i 0.5 -d

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7
  Uname: Linux 3.13.0-20-generic x86_64
  ApportVersion: 2.14-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: kwin
  CurrentDesktop: KDE
  Date: Tue Apr  1 09:02:37 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: kubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
     Subsystem: Lenovo Device [17aa:2217]
  InstallationDate: Installed on 2014-03-25 (6 days ago)
  InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140324)
  LightdmGreeterLog:
   QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: Datei 
oder Verzeichnis nicht gefunden
   QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus
   Bus::open: Can not get ibus-daemon's address.
   IBusInputContext::createInputContext: no connection to ibus-daemon
   file:///usr/share/kde4/apps/lightdm-kde-greeter/themes/userbar/main.qml:135: 
Unable to assign [undefined] to QString usersession
  LightdmGreeterLogOld:
   QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: Datei 
oder Verzeichnis nicht gefunden
   QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus
   Bus::open: Can not get ibus-daemon's address.
   IBusInputContext::createInputContext: no connection to ibus-daemon
   file:///usr/share/kde4/apps/lightdm-kde-greeter/themes/userbar/main.qml:135: 
Unable to assign [undefined] to QString usersession
  MachineType: LENOVO 20C0S0AX00
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-20-generic.efi.signed 
root=UUID=389305e0-f86b-4068-a352-fe5597926b87 ro rootflags=subvol=@ 
kopt=root=/dev/mapper/ray-root quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/26/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GQET34WW (1.14 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20C0S0AX00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 Pro
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGQET34WW(1.14):bd02/26/2014:svnLENOVO:pn20C

[Touch-packages] [Bug 1432413] Re: Synaptic Touchpad xevents are hijacked under X

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

Title:
  Synaptic Touchpad xevents are hijacked under X

Status in xorg package in Ubuntu:
  Expired

Bug description:
  Synaptic Touchpad xevents are hijacked under X11.

  I have a problem with the synaptic touch-pad on my Acer Aspire that started 
around a week ago.
  The problem can be described as that there is a massive amount of xevents 
being generated and appearing to originate from the touch-pad even though the 
touch-pad is not used.
  I have tested the HW which seems to work fine.
  The test performed is to start a terminal session (Ctrl + Alt + 2) before the 
fault occurs and check the xevents by running
   ~$ sudo evtest /dev/input/eventX
  where the X to use is found in /proc/bus/input/devices and found by running
   ~$ cat /proc/bus/input/devices |grep mouse
  No matter how much the touch-pad is used will the console show the 
corresponding events which indicates that HW and driver works OK as long it is 
not under X

  When the problem has occurred (in Desktop mode) is it easy (but inconvenient) 
to get back to normal by key combo Fn+F7 twice, turn off touch-pad and then 
turn on again.
  And more, one can get unlucky in the sense that the generated events could 
click somewhere one do not want to click.
  During the problem is it impossible to use the mouse since it flies around 
(mostly going in a bottom to top of screen direction) but one can check the 
generated events using evtest again.

  How can I help troubleshooting the problem?

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.16.0-31.43~14.04.1-generic 3.16.7-ckt5
  Uname: Linux 3.16.0-31-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.7
  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 15 19:51:13 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation ValleyView Gen7 [8086:0f31] (rev 0e) (prog-if 00 [VGA 
controller])
 Subsystem: Acer Incorporated [ALI] Device [1025:0933]
  InstallationDate: Installed on 2015-02-21 (22 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: Acer Aspire E3-112
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-31-generic 
root=UUID=a97d0b51-4244-48ca-ba87-bc3a38a8b62d ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/20/2014
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.08
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: R2
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - A01 Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.08:bd08/20/2014:svnAcer:pnAspireE3-112:pvrV1.08:rvnAcer:rnR2:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: Aspire E3-112
  dmi.product.version: V1.08
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.11.3+14.04.20150122-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1~ubuntu2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 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: Sun Mar 15 18:59:07 2015
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1576 
   vendor BOE
  xserver.version: 2:1.16.0-1ubuntu1.2~trusty2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1432413/+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 1589056] Re: HDMI does not 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/1589056

Title:
  HDMI does not work

Status in xorg package in Ubuntu:
  Expired

Bug description:
  xrandr displays "HDMI-1 disconnected (normal left inverted right x
  axis y axis)" even if it is connected using a HDMI cable to a Samsung
  monitor (model S27B350H) that has both HDMI and VGA connectors.

  WORKAROUND: Use the Nvidia proprietary driver.

  Graphics by lspci -vvv:
  01:00.0 VGA compatible controller: NVIDIA Corporation G84GLM [Quadro FX 570M] 
(rev a1) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Device 30c5
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR-  [disabled]
   Capabilities: 
   Kernel driver in use: nouveau

  ---
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  BootLog:
   root: clean, 247512/1281120 files, 1867600/512 blocks
   [FAILED] Failed to start Automatically refresh installed snaps.
   See 'systemctl status snapd.refresh.service' for details.
   [  OK  ] Started Authenticate and Authorize Users to Run 
Privileged Tasks.
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  DistUpgraded: 2016-06-24 18:11:48,939 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation G84GLM [Quadro FX 570M] [10de:040c] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: Hewlett-Packard Company G84GLM [Quadro FX 570M] [103c:30c5]
  InstallationDate: Installed on 2015-11-21 (228 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic 
root=UUID=bdc3be24-dee9-4ead-bca0-c9b1e45a87e5 ro persistent quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Tags:  xenial ubuntu
  Uname: Linux 4.4.0-28-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-06-24 (12 days ago)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 12/01/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68MVD Ver. F.20
  dmi.board.name: 30C5
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 71.36
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68MVDVer.F.20:bd12/01/2011:svnHewlett-Packard:pn:pvrF.20:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.36:cvnHewlett-Packard:ct10:cvr:
  dmi.product.version: F.20
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1589056/+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 1615864] Re: Screen resolution not saved after reboot or logout and back in

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

Title:
  Screen resolution not saved after reboot or logout and back in

Status in xorg package in Ubuntu:
  Expired

Bug description:
  The issue is that Ubuntu 16.04 does not save or read the saved screen
  resolution settings of 1920x1080 from my Vizio 42 inch TV HDMI
  connected to my computer. When booting into the desktop the mouse
  pointer is small as if in 1920x1080 but then changes to a larger
  pointer then the resolution is then 1280x720 which seems to what 16.04
  falls back to.

  The TV reports the proper information under xrandr.
  gee@HTPC:~$ xrandr
  Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 4096 x 4096
  VGA-0 disconnected (normal left inverted right x axis y axis)
  TV-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) 980mm x 580mm
 1280x720  60.00 +  59.94
 1920x1080 59.9459.94*   60.0560.0050.04
 720x576   50.0050.08
 720x480   59.94
 640x480   59.93

  WORKAROUND: Type at the terminal:
  xrandr -s 1920x1080

  ---
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
u'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  304.131  Sun Nov  8 21:43:33 
PST 2015
   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: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME-Flashback:Unity
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia-304, 304.131, 4.4.0-34-generic, x86_64: installed
   nvidia-304, 304.131, 4.4.0-36-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation C68 [GeForce 7050 PV / nForce 630a] [10de:053a] (rev a2) 
(prog-if 00 [VGA controller])
     Subsystem: Micro-Star International Co., Ltd. [MSI] C68 [GeForce 7050 PV / 
nForce 630a] [1462:349f]
  InstallationDate: Installed on 2016-08-20 (12 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 002: ID 099a:7202 Zippy Technology Corp.
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: MSI MS-7349
  NonfreeKernelModules: nvidia
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic 
root=UUID=377930d2-4053-4a10-96ef-8cac652e4c24 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Tags:  xenial ubuntu
  Uname: Linux 4.4.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev pulse pulse-access sambashare 
sudo video
  _MarkForUpload: True
  dmi.bios.date: 03/19/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: CaptiveWorks CW-3000HD V2.37
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: MS-7349
  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: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrCaptiveWorksCW-3000HDV2.37:bd03/19/2008:svnMSI:pnMS-7349:pvr1.0:rvnMSI:rnMS-7349:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: MS-7349
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz 1:0.9.12.2+16.04.20160801.3-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.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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  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-

[Touch-packages] [Bug 1664501] Re: Unable to wake up monitor after it goes to sleep (after locking x session, for example)

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

Title:
  Unable to wake up monitor after it goes to sleep (after locking x
  session, for example)

Status in xorg package in Ubuntu:
  Expired

Bug description:
  Additional info:

  lsb_release:
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  
  I'm using an external monitor attached via VGA (seen as DP2 in xrandr output) 
in an extended desktop configuration (not cloned). Whenever the X session 
starts some kind of screen saving (for example, after locking the screen), the 
external monitor and the laptop screen both go to a saving power state.

  After that, If I try to wake them up (moving cursor, touch keys,
  etc.), only the laptop's panel goes back. The external monitor stays
  in a suspended state. If I force it to wake up and scan inputs, it
  doesn't find any, and it doesn't appear as conencted in xrandr otput.

  The only way I've found to wake it up is by performing the following
  sequence of operations:

  ALT+F1 [switch to first tty/console] --> this does wake up and activate the 
monitor, mirroring
  login as my user
  $ xrandr -d :0 #DP2 still doesn't appear
  logout
  ALT+F7 [go back to X]

  At this point, the external monitor is working and X detects it and
  re-enables the extended desktop

  Doing just ALT+F1/ALT+F7, doesn't work (I need to execute xrandr in
  order to make the whole thing work)

  Doing xrandr from the graphical environment (directly in a xterminal
  in the Xsession) doesn't wake up the monitor

  Looks like there's no need to add any addictional operation/parameter
  to xrandr in order to make this process work, no need to set output
  settings, etc. Just issue "xrandr -d :0" and things magically work

  Thanks in advance

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  .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: Tue Feb 14 10:54:19 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Hewlett-Packard Company Skylake Integrated Graphics [103c:8079]
  MachineType: HP HP EliteBook 840 G3
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-62-generic 
root=ZFS=rpool/ROOT/ubuntu ro boot=zfs quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/22/2016
  dmi.bios.vendor: HP
  dmi.bios.version: N75 Ver. 01.05
  dmi.board.name: 8079
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 85.61
  dmi.chassis.asset.tag: 5CG6247TWJ
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrN75Ver.01.05:bd03/22/2016:svnHP:pnHPEliteBook840G3:pvr:rvnHP:rn8079:rvrKBCVersion85.61:cvnHP:ct10:cvr:
  dmi.product.name: HP EliteBook 840 G3
  dmi.sys.vendor: HP
  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
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue Feb 14 10:49:09 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5312 
   vendor CMN
  xserver.version: 2:1.18.4-0ubuntu0.2

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


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

[Touch-packages] [Bug 1664596] Re: xset led on, enables mouse-keys

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

Title:
  xset led on, enables mouse-keys

Status in xorg package in Ubuntu:
  Expired

Bug description:
  I have a backlit keyboard on a stationary PC.
  The back-light goes off at random intervals.
  I'm a heavy user of numeric keypad. That turns into mouse-keys at intervals 
as well.

  Both issues results in a rather annoying user experience. 
  I have not been able to determine the reason or what lead up to this. But it 
often happen whenever I take a short break. (after a few minutes of inactivity)

  Therefore I periodically run a script to turn the back-light back on
  and disable mouse-keys.

  It turns out that setting the back-light on, enables the mouse-keys
  again!

  Something is wired with this. But this last part is easy to reproduce
  with this script:

  #!/bin/sh
  /usr/bin/gsettings set org.gnome.desktop.a11y.keyboard mousekeys-enable false 
# disables mouse-keys
  /usr/bin/gsettings get org.gnome.desktop.a11y.keyboard mousekeys-enable  # 
reports false and mouse-keys are actually disabled

  xset led on

  /usr/bin/gsettings get org.gnome.desktop.a11y.keyboard mousekeys-enable # 
reports false, but mouse-keys are actually enabled!
  /usr/bin/gsettings set org.gnome.desktop.a11y.keyboard mousekeys-enable false 
# disables mouse-keys again.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-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: Tue Feb 14 15:17:53 2017
  DistUpgraded: 2016-06-03 10:07:29,690 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde XT [Radeon HD 7770/8760 / 
R7 250X] [1002:683d] (prog-if 00 [VGA controller])
 Subsystem: XFX Pine Group Inc. Cape Verde XT [Radeon HD 7770/8760 / R7 
250X] [1682:3232]
  InstallationDate: Installed on 2015-07-29 (565 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: ASUSTeK Computer INC. CM6330_CM6630_CM6730_CM6830-8
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-62-generic 
root=UUID=458544bf-05e1-4b76-93ee-1c5cfa8f7683 ro quiet splash 
usbcore.autosuspend=-1 vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-06-03 (256 days ago)
  dmi.bios.date: 08/27/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0402
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: CM6330_CM6630_CM6730_CM6830
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev x.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0402:bd08/27/2012:svnASUSTeKComputerINC.:pnCM6330_CM6630_CM6730_CM6830-8:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnCM6330_CM6630_CM6730_CM6830:rvrRevx.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: CM6330_CM6630_CM6730_CM6830-8
  dmi.product.version: System Version
  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.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: Tue Feb 14 12:39:26 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.2
  xserver.video_driver: radeon

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


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

[Touch-packages] [Bug 2009700] Re: [lunar] missing key events with ibus 1.5.28

[Launchpad Bug Tracker]

This bug was fixed in the package ibus - 1.5.28-2

---
ibus (1.5.28-2) experimental; urgency=medium

  * Team upload
  * Fix missing key events (LP: #2009700)
- d/p/client-x11-Fix-Key-typing-order.patch
- d/p/util-IMdkit-Disable-while-loop-before-call-ForwardEvent.patch

 -- Gunnar Hjalmarsson   Thu, 16 Mar 2023 13:31:39
+0100

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

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

Title:
  [lunar] missing key events with ibus 1.5.28

Status in ibus:
  Unknown
Status in ibus package in Ubuntu:
  Fix Released

Bug description:
  The new ibus 1.5.28 seem to have introduced a pretty serious bug:

  https://github.com/ValveSoftware/Proton/issues/5294

  https://github.com/ibus/ibus/issues/2485

  Very good bug report, with test case and someone proposing a patch:
  https://github.com/ibus/ibus/issues/2480

  "While playing TrackMania Nations Forever under Wine, I noticed that
  sometimes (once in a few minutes) the car continued steering after
  fully releasing the corresponding input key on my keyboard. Pressing
  and re-releasing the corresponding input fixed the problem. So, it
  appears that the game failed to register the key release event."

  This is exactly the same issue I saw when playing Wine games.
  Disabling ibus server (and switching to XIM) solved it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ibus/+bug/2009700/+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 2011751] Re: openbox crashed with SIGABRT

[Thomas Ward]

After discussion with the Security Team, we do not believe this is a
Security bug and that there currently is no need to keep it private as
there is other public discourse via other related bugs on other trackers
and here in Launchpad with other bugs (marked as dupes of this or such).

** Information type changed from Private Security to Public

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

Title:
  openbox crashed with SIGABRT

Status in glib2.0 package in Ubuntu:
  Confirmed
Status in openbox package in Ubuntu:
  Confirmed

Bug description:
  Lubuntu lunar (primary box) on
  - dell [optiplex] 7050 (i5-6500, 16gb, intel hd530/i915)

  I experienced a crash yesterday (openbox) but tend to ignore the first
  crashes... Whilst using the machine again today a crash occurred.

  This is my primary box, so my setup is pretty consistent

  - featherpad (restored session)
  - hexchat (irc)
  - qterminal (only single tab today; usually many)
  - firefox (snap, most sites excluding google related)
  - chromium (snap, used for anything google related)
  - telegram (snap)
  - element

  I was using chromium full screen (trying to read my gmail inbox) when
  borders around windows disappeared & I lost the capacity to switch
  between windows; mouse would move, but keyboard appeared mostly dead
  (it wasn't, more I think windows weren't responding, inc. clicks with
  mouse though that's likely inconsistent; I could work out how to
  describe it yesterday, but todays is almost identical).

  I switched to text terminal (ctrl+alt+f4) & explored; returned to GUI and used
  - ctrl+alt+t to open new terminal
  - openbox &

  session returned to what I expect...

  ** expected outcome

  Openbox doesn't crash

  ** actual outcome

  all windows lost borders, and i lost ability to switch between windows
  I appeared to have minimal control (not true, more a fraction of what I 
expect)

  ** How to get crash

  For me,

  - I used chromium (browser)
  - make chromium full screen (ie. F11)
  - click on something & right-click to open in new window
  OPENBOX CRASH.

  ProblemType: Crash
  DistroRelease: Ubuntu 23.04
  Package: openbox 3.6.1-10
  ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6
  Uname: Linux 6.1.0-16-generic x86_64
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashCounter: 1
  CurrentDesktop: LXQt
  Date: Thu Mar 16 09:46:22 2023
  ExecutablePath: /usr/bin/openbox
  ExecutableTimestamp: 1643543619
  InstallationDate: Installed on 2023-01-25 (49 days ago)
  InstallationMedia: Lubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230124)
  JournalErrors: -- No entries --
  ProcCmdline: /usr/bin/openbox
  ProcCwd: /home/guiverc
  RebootRequiredPkgs: Error: path contained symlinks.
  Signal: 6
  SourcePackage: openbox
  StacktraceTop:
   () at /lib/x86_64-linux-gnu/libobt.so.2
    () at /lib/x86_64-linux-gnu/libc.so.6
   client_calc_layer ()
   ()
   () at /lib/x86_64-linux-gnu/libobt.so.2
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2011751/+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 2012008] Re: package python3-problem-report 2.20.11-0ubuntu27.24 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attemptin

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package python3-problem-report 2.20.11-0ubuntu27.24 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in apport package in Ubuntu:
  New

Bug description:
  Getting an error on every boot now.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: python3-problem-report 2.20.11-0ubuntu27.24
  ProcVersionSignature: Ubuntu 5.15.0-58.64~20.04.1-generic 5.15.74
  Uname: Linux 5.15.0-58-generic x86_64
  ApportLog:
   ERROR: apport (pid 2603509) Thu Mar 16 15:38:45 2023: called for pid 3674, 
signal 11, core limit 0, dump mode 1
   ERROR: apport (pid 2603509) Thu Mar 16 15:38:45 2023: executable: 
/usr/bin/nautilus (command line "/usr/bin/nautilus --gapplication-service")
   ERROR: apport (pid 2603509) Thu Mar 16 15:38:45 2023: is_closing_session(): 
Could not determine DBUS socket.
   ERROR: apport (pid 2603509) Thu Mar 16 15:38:53 2023: wrote report 
/var/crash/_usr_bin_nautilus.1000.crash
  ApportVersion: 2.20.11-0ubuntu27.24
  AptOrdering: NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashReports:
   640:1000:125:351112706:2023-03-08 09:27:20.347548007 -0800:2023-03-08 
09:27:21.347548007 -0800:/var/crash/_usr_libexec_gvfsd-google.1000.crash
   640:1000:125:19914318:2023-03-16 15:39:57.163937568 -0700:2023-03-16 
15:39:58.163937568 -0700:/var/crash/_usr_bin_nautilus.1000.crash
   600:0:125:79228:2023-03-16 15:39:33.322134256 -0700:2023-03-16 
15:39:34.322134256 -0700:/var/crash/python3-problem-report.0.crash
  Date: Thu Mar 16 15:39:34 2023
  Dependencies:
   
  DpkgHistoryLog:
   Start-Date: 2023-03-16  15:39:33
   Commandline: /usr/bin/apt-get -fy install
   Requested-By: druffer (1000)
  DuplicateSignature:
   package:python3-problem-report:2.20.11-0ubuntu27.24
   Setting up python3-setuptools (45.2.0-1ubuntu0.1) ...
   dpkg: error processing package python3-problem-report (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2022-10-20 (147 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  PackageArchitecture: all
  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: apport
  Title: package python3-problem-report 2.20.11-0ubuntu27.24 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2012008/+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 2012008] [NEW] package python3-problem-report 2.20.11-0ubuntu27.24 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempt

[Dennis Ruffer]

Public bug reported:

Getting an error on every boot now.

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: python3-problem-report 2.20.11-0ubuntu27.24
ProcVersionSignature: Ubuntu 5.15.0-58.64~20.04.1-generic 5.15.74
Uname: Linux 5.15.0-58-generic x86_64
ApportLog:
 ERROR: apport (pid 2603509) Thu Mar 16 15:38:45 2023: called for pid 3674, 
signal 11, core limit 0, dump mode 1
 ERROR: apport (pid 2603509) Thu Mar 16 15:38:45 2023: executable: 
/usr/bin/nautilus (command line "/usr/bin/nautilus --gapplication-service")
 ERROR: apport (pid 2603509) Thu Mar 16 15:38:45 2023: is_closing_session(): 
Could not determine DBUS socket.
 ERROR: apport (pid 2603509) Thu Mar 16 15:38:53 2023: wrote report 
/var/crash/_usr_bin_nautilus.1000.crash
ApportVersion: 2.20.11-0ubuntu27.24
AptOrdering: NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckResult: skip
CrashReports:
 640:1000:125:351112706:2023-03-08 09:27:20.347548007 -0800:2023-03-08 
09:27:21.347548007 -0800:/var/crash/_usr_libexec_gvfsd-google.1000.crash
 640:1000:125:19914318:2023-03-16 15:39:57.163937568 -0700:2023-03-16 
15:39:58.163937568 -0700:/var/crash/_usr_bin_nautilus.1000.crash
 600:0:125:79228:2023-03-16 15:39:33.322134256 -0700:2023-03-16 
15:39:34.322134256 -0700:/var/crash/python3-problem-report.0.crash
Date: Thu Mar 16 15:39:34 2023
Dependencies:
 
DpkgHistoryLog:
 Start-Date: 2023-03-16  15:39:33
 Commandline: /usr/bin/apt-get -fy install
 Requested-By: druffer (1000)
DuplicateSignature:
 package:python3-problem-report:2.20.11-0ubuntu27.24
 Setting up python3-setuptools (45.2.0-1ubuntu0.1) ...
 dpkg: error processing package python3-problem-report (--configure):
  package is in a very bad inconsistent state; you should
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2022-10-20 (147 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
PackageArchitecture: all
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: apport
Title: package python3-problem-report 2.20.11-0ubuntu27.24 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: apport (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 apport in Ubuntu.
https://bugs.launchpad.net/bugs/2012008

Title:
  package python3-problem-report 2.20.11-0ubuntu27.24 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in apport package in Ubuntu:
  New

Bug description:
  Getting an error on every boot now.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: python3-problem-report 2.20.11-0ubuntu27.24
  ProcVersionSignature: Ubuntu 5.15.0-58.64~20.04.1-generic 5.15.74
  Uname: Linux 5.15.0-58-generic x86_64
  ApportLog:
   ERROR: apport (pid 2603509) Thu Mar 16 15:38:45 2023: called for pid 3674, 
signal 11, core limit 0, dump mode 1
   ERROR: apport (pid 2603509) Thu Mar 16 15:38:45 2023: executable: 
/usr/bin/nautilus (command line "/usr/bin/nautilus --gapplication-service")
   ERROR: apport (pid 2603509) Thu Mar 16 15:38:45 2023: is_closing_session(): 
Could not determine DBUS socket.
   ERROR: apport (pid 2603509) Thu Mar 16 15:38:53 2023: wrote report 
/var/crash/_usr_bin_nautilus.1000.crash
  ApportVersion: 2.20.11-0ubuntu27.24
  AptOrdering: NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashReports:
   640:1000:125:351112706:2023-03-08 09:27:20.347548007 -0800:2023-03-08 
09:27:21.347548007 -0800:/var/crash/_usr_libexec_gvfsd-google.1000.crash
   640:1000:125:19914318:2023-03-16 15:39:57.163937568 -0700:2023-03-16 
15:39:58.163937568 -0700:/var/crash/_usr_bin_nautilus.1000.crash
   600:0:125:79228:2023-03-16 15:39:33.322134256 -0700:2023-03-16 
15:39:34.322134256 -0700:/var/crash/python3-problem-report.0.crash
  Date: Thu Mar 16 15:39:34 2023
  Dependencies:
   
  DpkgHistoryLog:
   Start-Date: 2023-03-16  15:39:33
   Commandline: /usr/bin/apt-get -fy install
   Requested-By: druffer (1000)
  DuplicateSignature:
   package:python3-problem-report:2.20.11-0ubuntu27.24
   Setting up python3-setuptools (45.2.0-1ubuntu0.1) ...
   dpkg: error processing package python3-problem-report (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2022-10-20 (147 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release a

[Touch-packages] [Bug 2011622] Re: rsync 3.1.3-8ubuntu0.5 (CVE-2022-29154 patch) breaks remote brace interpretation

[Marc Deslauriers]

I am closing this bug, since the new behaviour is expected with the
security fix. Thanks!

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

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

Title:
  rsync 3.1.3-8ubuntu0.5 (CVE-2022-29154 patch) breaks remote brace
  interpretation

Status in rsync package in Ubuntu:
  Invalid

Bug description:
  Commands like this:
  rsync -a host.example.org:\{this,that} .
  have worked for decades, in multiple Ubuntu versions, but were broken by the 
rsync 3.1.3-8ubuntu0 update (on the client, i.e. the machine on which I type 
that command).

  (To be clear, the backslash there quotes the '{' so that it is sent to
  the remote rsync rather than being interpreted by the local shell.)

  ("What happens instead?"  It now says "rsync: link_stat
  "/home/flaps/{this,that}" failed: No such file or directory (2)".)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/2011622/+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 2006954] Re: openssl: merge unstable's 3.0.8-1

[Launchpad Bug Tracker]

This bug was fixed in the package openssl - 3.0.8-1ubuntu1

---
openssl (3.0.8-1ubuntu1) lunar; urgency=medium

  * Merge 3.0.8 from Debian testing (LP: #2006954)
- Remaining changes:
  + Symlink changelog{,.Debian}.gz and copyright.gz from libssl-dev to
openssl
  + d/libssl3.postinst: Revert Debian deletion
- Skip services restart & reboot notification if needrestart is in-use.
- Bump version check to 1.1.1 (bug opened as LP: #1999139)
- Use a different priority for libssl1.1/restart-services depending
  on whether a desktop, or server dist-upgrade is being performed.
- Import libraries/restart-without-asking template as used by above.
  + Add support for building with noudeb build profile.
  + Use perl:native in the autopkgtest for installability on i386.

 -- Adrien Nader   Mon, 20 Feb 2023 16:10:19
+0100

** Changed in: openssl (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 openssl in Ubuntu.
https://bugs.launchpad.net/bugs/2006954

Title:
  openssl: merge unstable's 3.0.8-1

Status in openssl package in Ubuntu:
  Fix Released

Bug description:
  Openssl 3.0.8 has been released. Unstable now contains 3.0.8-1 which
  we can merge.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2006954/+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 2011991] [NEW] scrambled video

[Emilio Gallicchio]

Public bug reported:

The video is scrambled. It's a mpeg file with these characteristics:

$ file tp224.mpeg
tp224.mpeg: MPEG sequence, v1, progressive Y'CbCr 4:2:0 video, CCIR/ITU NTSC 
525, 25 fps

$ apt-cache policy totem
totem:
  Installed: 42.0-1ubuntu1
  Candidate: 42.0-1ubuntu1
  Version table:
 *** 42.0-1ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
100 /var/lib/dpkg/status

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

$apt list --installed gstreamer*
gir1.2-gstreamer-1.0/jammy-updates,now 1.20.3-0ubuntu1 amd64 
[installed,automatic]
gstreamer1.0-alsa/jammy,now 1.20.1-1 amd64 [installed,automatic]
gstreamer1.0-clutter-3.0/jammy-updates,now 3.0.27-2ubuntu1 amd64 
[installed,automatic]
gstreamer1.0-gl/jammy,now 1.20.1-1 amd64 [installed,automatic]
gstreamer1.0-gtk3/jammy-updates,now 1.20.3-0ubuntu1 amd64 [installed,automatic]
gstreamer1.0-libav/jammy-updates,now 1.20.3-0ubuntu1 amd64 [installed,automatic]
gstreamer1.0-packagekit/jammy,now 1.2.5-2ubuntu2 amd64 [installed,automatic]
gstreamer1.0-pipewire/jammy-updates,now 0.3.48-1ubuntu3 amd64 
[installed,automatic]
gstreamer1.0-plugins-base-apps/jammy,now 1.20.1-1 amd64 [installed,automatic]
gstreamer1.0-plugins-base/jammy,now 1.20.1-1 amd64 [installed,automatic]
gstreamer1.0-plugins-good/jammy-updates,now 1.20.3-0ubuntu1 amd64 
[installed,automatic]
gstreamer1.0-plugins-ugly/jammy,now 1.20.1-1 amd64 [installed,automatic]
gstreamer1.0-pulseaudio/jammy-updates,now 1.20.3-0ubuntu1 amd64 
[installed,automatic]
gstreamer1.0-tools/jammy-updates,now 1.20.3-0ubuntu1 amd64 [installed,automatic]
gstreamer1.0-vaapi/jammy-updates,now 1.20.1-1ubuntu1 amd64 [installed]
gstreamer1.0-x/jammy,now 1.20.1-1 amd64 [installed,automatic]
libgstreamer-gl1.0-0/jammy,now 1.20.1-1 amd64 [installed,automatic]
libgstreamer-plugins-bad1.0-0/jammy-updates,now 1.20.3-0ubuntu1 amd64 
[installed,automatic]
libgstreamer-plugins-base1.0-0/jammy,now 1.20.1-1 amd64 [installed,automatic]
libgstreamer-plugins-good1.0-0/jammy-updates,now 1.20.3-0ubuntu1 amd64 
[installed,automatic]
libgstreamer1.0-0/jammy-updates,now 1.20.3-0ubuntu1 amd64 [installed,automatic]

$ apt list --installed | grep restricted
ubuntu-restricted-addons/jammy,now 26 amd64 [installed,automatic]
ubuntu-restricted-extras/jammy,now 67 amd64 [installed]

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: libgstreamer1.0-0 1.20.3-0ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74
Uname: Linux 5.15.0-58-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Mar 16 16:40:21 2023
InstallationDate: Installed on 2023-01-27 (47 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: gstreamer1.0
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gstreamer1.0 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy

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

Title:
  scrambled video

Status in gstreamer1.0 package in Ubuntu:
  New

Bug description:
  The video is scrambled. It's a mpeg file with these characteristics:

  $ file tp224.mpeg
  tp224.mpeg: MPEG sequence, v1, progressive Y'CbCr 4:2:0 video, CCIR/ITU NTSC 
525, 25 fps

  $ apt-cache policy totem
  totem:
Installed: 42.0-1ubuntu1
Candidate: 42.0-1ubuntu1
Version table:
   *** 42.0-1ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status

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

  $apt list --installed gstreamer*
  gir1.2-gstreamer-1.0/jammy-updates,now 1.20.3-0ubuntu1 amd64 
[installed,automatic]
  gstreamer1.0-alsa/jammy,now 1.20.1-1 amd64 [installed,automatic]
  gstreamer1.0-clutter-3.0/jammy-updates,now 3.0.27-2ubuntu1 amd64 
[installed,automatic]
  gstreamer1.0-gl/jammy,now 1.20.1-1 amd64 [installed,automatic]
  gstreamer1.0-gtk3/jammy-updates,now 1.20.3-0ubuntu1 amd64 
[installed,automatic]
  gstreamer1.0-libav/jammy-updates,now 1.20.3-0ubuntu1 amd64 
[installed,automatic]
  gstreamer1.0-packagekit/jammy,now 1.2.5-2ubuntu2 amd64 [installed,automatic]
  gstreamer1.0-pipewire/jammy-updates,now 0.3.48-1ubuntu3 amd64 
[installed,automatic]
  gstreamer1.0-plugins-base-apps/jammy,now 1.20.1-1 amd64 [installed,automatic]
  gstreamer1.0-plugins-base/jammy,now 1.20.1-1 amd64 [installed,automatic]
  gstreamer1.0-plugins-good/jammy-updates,now 1.20.3-0ubuntu1 amd64 
[installed,automatic]
  gstreamer1.0-plugins-ugly/jammy,now 1.20.1

[Touch-packages] [Bug 2003797] Re: Pre-1970 timestamps are knowingly wrong

[Launchpad Bug Tracker]

This bug was fixed in the package tzdata - 2022g-7ubuntu2

---
tzdata (2022g-7ubuntu2) lunar; urgency=medium

  * Merge with Debian experimental. Remaining changes:
- Ship ICU 2022g timezone data which are utilized by PHP in tzdata-icu
- Do not rename NEWS into changelog.gz, this fixes a build failure on
  moment-timezone.js
- Point Vcs-Browser/Git to Launchpad
  * Rename new tzdata-right package to tzdata-legacy

tzdata (2022g-7exp1) experimental; urgency=medium

  * Drop /usr/share/zoneinfo/posix (identical to /usr/share/zoneinfo)
(LP: #2008076)
  * Split right/* timezones into separate tzdata-legacy package (LP: #2008076)

 -- Benjamin Drung   Mon, 13 Mar 2023 15:45:25 +0100

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

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

Title:
  Pre-1970 timestamps are knowingly wrong

Status in tzdata package in Ubuntu:
  Fix Released

Bug description:
  tzdata 2021b says in NEWS: "Merge more location-based Zones whose
  timestamps agree since 1970, as pre-1970 timestamps are out of scope.
  This is part of a process that has been ongoing since 2013.  This does
  not affect post-1970 timestamps, and timezone historians who build
  with 'make PACKRATDATA=backzone' should see no changes to pre-1970
  timestamps." tzdata 2022b finished that process: "Finish moving to
  'backzone' the location-based zones whose timestamps since 1970 are
  duplicates; adjust links accordingly. This change ordinarily affects
  only pre-1970 timestamps, and with the new PACKRATLIST option it does
  not affect any timestamps. In this round the affected zones are
  Antarctica/Vostok, Asia/Brunei, Asia/Kuala_Lumpur, Atlantic/Reykjavik,
  Europe/Amsterdam, Europe/Copenhagen, Europe/Luxembourg, Europe/Monaco,
  Europe/Oslo, Europe/Stockholm, Indian/Christmas, Indian/Cocos,
  Indian/Kerguelen, Indian/Mahe, Indian/Reunion, Pacific/Chuuk,
  Pacific/Funafuti, Pacific/Majuro, Pacific/Pohnpei, Pacific/Wake and
  Pacific/Wallis, and the affected links are Arctic/Longyearbyen,
  Atlantic/Jan_Mayen, Iceland, Pacific/Ponape, Pacific/Truk, and
  Pacific/Yap."

  The Debian/Ubuntu package builds tzdata with the default settings
  (PACKRATDATA unset) which merges zones whose timestamps agree since
  1970. This leads to timestamps before 1970 being knowingly wrong.
  Example: Europe/Oslo is a link to Europe/Berlin since they are
  identical since 1970, but they differed before 1965. Berlin observed
  no summertime between 1950 and 1980, but Oslo did in 1959 to 1965. So
  summer 1960 in Oslo should be UTC+2 compared to UTC+1 in Berlin:

  ```
  $ TZ=Europe/Oslo date -d "1960-07-01 10:00 Z"
  Fri Jul  1 12:00:00 CEST 1960
  $ TZ=Europe/Berlin date -d "1960-07-01 10:00 Z"
  Fri Jul  1 11:00:00 CET 1960
  ```

  There was a big debate upstream (see https://lwn.net/Articles/870478/
  or https://mm.icann.org/pipermail/tz/2021-May/030137.html). The
  Debian/Ubuntu package should ship timezones from backzone. Users that
  care about pre-1970 timestamps will be satisfied and users not caring
  will probably not care about the additional timezones.

  The install size will increase by around 20% and the amount of
  distinct (i.e. not symlinked) timezones will increase by 33%:

  ```
  $ grep ^Zone africa antarctica asia australasia etcetera europe factory 
northamerica southamerica | wc -l
  352
  $ grep ^Zone backzone | wc -l
  119
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2003797/+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 1683595] Re: tzdata doesn't remove /etc/timezone on purge

[Launchpad Bug Tracker]

This bug was fixed in the package tzdata - 2022g-7ubuntu2

---
tzdata (2022g-7ubuntu2) lunar; urgency=medium

  * Merge with Debian experimental. Remaining changes:
- Ship ICU 2022g timezone data which are utilized by PHP in tzdata-icu
- Do not rename NEWS into changelog.gz, this fixes a build failure on
  moment-timezone.js
- Point Vcs-Browser/Git to Launchpad
  * Rename new tzdata-right package to tzdata-legacy

tzdata (2022g-7exp1) experimental; urgency=medium

  * Drop /usr/share/zoneinfo/posix (identical to /usr/share/zoneinfo)
(LP: #2008076)
  * Split right/* timezones into separate tzdata-legacy package (LP: #2008076)

 -- Benjamin Drung   Mon, 13 Mar 2023 15:45:25 +0100

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

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

Title:
  tzdata doesn't remove /etc/timezone on purge

Status in tzdata package in Ubuntu:
  Fix Released

Bug description:
  Since version 2017a-1, tzdata will clean up /etc/localtime on purge.
  But it leaves behind /etc/timezone, despite the fact that in some
  cases it creates this file.  I think tzdata should own removing it on
  purge also.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1683595/+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 2008076] Re: Drop /usr/share/zoneinfo/posix and move /usr/share/zoneinfo/right into tzdata-legacy

[Launchpad Bug Tracker]

This bug was fixed in the package tzdata - 2022g-7ubuntu2

---
tzdata (2022g-7ubuntu2) lunar; urgency=medium

  * Merge with Debian experimental. Remaining changes:
- Ship ICU 2022g timezone data which are utilized by PHP in tzdata-icu
- Do not rename NEWS into changelog.gz, this fixes a build failure on
  moment-timezone.js
- Point Vcs-Browser/Git to Launchpad
  * Rename new tzdata-right package to tzdata-legacy

tzdata (2022g-7exp1) experimental; urgency=medium

  * Drop /usr/share/zoneinfo/posix (identical to /usr/share/zoneinfo)
(LP: #2008076)
  * Split right/* timezones into separate tzdata-legacy package (LP: #2008076)

 -- Benjamin Drung   Mon, 13 Mar 2023 15:45:25 +0100

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

Title:
  Drop /usr/share/zoneinfo/posix and move /usr/share/zoneinfo/right into
  tzdata-legacy

Status in chrony package in Ubuntu:
  Fix Released
Status in moment-timezone.js package in Ubuntu:
  Fix Committed
Status in rdate package in Ubuntu:
  Fix Committed
Status in tzdata package in Ubuntu:
  Fix Released

Bug description:
  The tzdata package ships /usr/share/zoneinfo/posix/ (for Coordinated 
Universal Time) and /usr/share/zoneinfo/right/ (for International Atomic Time). 
The files in /usr/share/zoneinfo/posix/ are identical to their counterpart in 
/usr/share/zoneinfo/. The tzdata package converts the
  configured posix/* and right/* timezones to their unprefixed variant on every 
package upgrade (e.g. it changes "posix/Europe/Berlin" to "Europe/Berlin").

  Drop /usr/share/zoneinfo/right from tzdata and move
  /usr/share/zoneinfo/right into separate tzdata-legacy package.

  ubuntu-devel discussion: https://lists.ubuntu.com/archives/ubuntu-
  devel/2023-January/042405.html

  Two packages need to be adjusted:

  * chrony: reads /usr/share/zoneinfo/right/UTC for leap seconds
  * moment-timezone.js: uses /usr/share/zoneinfo/posix/ in debian/rules
  * rdate: reads /usr/share/zoneinfo/right/UTC -> depend on tzdata-legacy

  Following packages were checked and do not need to be touched:

  Only in source code documentation and/or tests suite:

  * mariadb
  * mariadb-10.6

  Copies of tz soure code:

  * rust-chrono-tz (in tz)
  * udm (in tzdatabase)
  * r-cran-tzdb (in inst/tzdata)
  * pike8.0 (in lib/modules/Calendar.pmod/tzdata)

  Referencing only /usr/share/zoneinfo/posixrules:

  * manpages-l10n
  * libdatetime-timezone-perl
  * asterisk
  * mozjs102
  * mozjs78
  * thunderbird

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/2008076/+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 2008076] Re: Drop /usr/share/zoneinfo/posix and move /usr/share/zoneinfo/right into tzdata-legacy

[Launchpad Bug Tracker]

This bug was fixed in the package chrony - 4.3-1ubuntu4

---
chrony (4.3-1ubuntu4) lunar; urgency=medium

  * Let upstream-simulation-test-suite depend on tzdata-legacy as well
(LP: #2008076)

chrony (4.3-1ubuntu3) lunar; urgency=medium

  * Depend on tzdata-legacy for reading leapsectz from
/usr/share/zoneinfo/right/UTC (LP: #2008076)

 -- Benjamin Drung   Wed, 15 Mar 2023 15:42:10 +0100

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

** Changed in: tzdata (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 tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/2008076

Title:
  Drop /usr/share/zoneinfo/posix and move /usr/share/zoneinfo/right into
  tzdata-legacy

Status in chrony package in Ubuntu:
  Fix Released
Status in moment-timezone.js package in Ubuntu:
  Fix Committed
Status in rdate package in Ubuntu:
  Fix Committed
Status in tzdata package in Ubuntu:
  Fix Released

Bug description:
  The tzdata package ships /usr/share/zoneinfo/posix/ (for Coordinated 
Universal Time) and /usr/share/zoneinfo/right/ (for International Atomic Time). 
The files in /usr/share/zoneinfo/posix/ are identical to their counterpart in 
/usr/share/zoneinfo/. The tzdata package converts the
  configured posix/* and right/* timezones to their unprefixed variant on every 
package upgrade (e.g. it changes "posix/Europe/Berlin" to "Europe/Berlin").

  Drop /usr/share/zoneinfo/right from tzdata and move
  /usr/share/zoneinfo/right into separate tzdata-legacy package.

  ubuntu-devel discussion: https://lists.ubuntu.com/archives/ubuntu-
  devel/2023-January/042405.html

  Two packages need to be adjusted:

  * chrony: reads /usr/share/zoneinfo/right/UTC for leap seconds
  * moment-timezone.js: uses /usr/share/zoneinfo/posix/ in debian/rules
  * rdate: reads /usr/share/zoneinfo/right/UTC -> depend on tzdata-legacy

  Following packages were checked and do not need to be touched:

  Only in source code documentation and/or tests suite:

  * mariadb
  * mariadb-10.6

  Copies of tz soure code:

  * rust-chrono-tz (in tz)
  * udm (in tzdatabase)
  * r-cran-tzdb (in inst/tzdata)
  * pike8.0 (in lib/modules/Calendar.pmod/tzdata)

  Referencing only /usr/share/zoneinfo/posixrules:

  * manpages-l10n
  * libdatetime-timezone-perl
  * asterisk
  * mozjs102
  * mozjs78
  * thunderbird

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/2008076/+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 1998207] Re: netplan network-manager plugin tries to save temporary connections

[Lukas Märdian]

I think this should probably fix the duplicated temporary connections
issue. Netplan should only ever try to handle non-temporary connections,
nothing that's being written to NMS_KEYFILE_STORAGE_TYPE_RUN (like those
external OpenVPN connections). More testing is needed to investigate the
side-effects of this change.


```
diff --git a/src/core/settings/plugins/keyfile/nms-keyfile-writer.c 
b/src/core/settings/plugins/keyfile/nms-keyfile-writer.c
index b893717c20..65e4e857ec 100644
--- a/src/core/settings/plugins/keyfile/nms-keyfile-writer.c
+++ b/src/core/settings/plugins/keyfile/nms-keyfile-writer.c
@@ -418,7 +418,8 @@ _internal_write_connection(NMConnection   
*connection,
 unlink(existing_path);
 
 /* NETPLAN: write only non-temporary files to /etc/netplan/... */
-if (!is_volatile && !is_nm_generated && !is_external) {
+if (!is_volatile && !is_nm_generated && !is_external &&
+strstr(keyfile_dir, "/etc/NetworkManager/system-connections")) {
 g_autofree gchar *ssid = g_key_file_get_string(kf_file, "wifi", 
"ssid", NULL);
 g_autofree gchar *escaped_ssid = ssid ?
  g_uri_escape_string(ssid, NULL, TRUE) 
: NULL;
```

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

Title:
  netplan network-manager plugin tries to save temporary connections

Status in netplan:
  Triaged
Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  *** Note: This bug is mostly about comment #10, now ***

  When creating an OpenVPN connection, a temporal connection called tunN
  is created. For instance, after activating a connection called
  vpntest, I have:

  NAME  UUID  TYPE  DEVICE
  vpntest   458856e6-8f0f-4dc6-82f2-dd72868252a0  vpn   ens3
  tun0  1eb1dbe8-5678-4818-9adf-fb2dc01ed132  tun   tun0

  tun0 is created/removed after activating/deactivating vpntest and
  should not really be saved, but I see netplan adding it in
  /etc/netplan. And while doing so the plugin also reports some errors
  (I see these when stopping the connection):

  Nov 28 16:16:57 ubuntu NetworkManager[11752]:  [1669652217.2920] BUG: 
the profile cannot be stored in keyfile format without becoming unusable: 
cannot access file: No such file or directory
  Nov 28 16:16:57 ubuntu NetworkManager[11752]: 
((src/libnm-core-impl/nm-connection.c:342)): assertion '' failed
  Nov 28 16:16:57 ubuntu NetworkManager[11752]:   [1669652217.2920] 
keyfile: commit: failure to write 1eb1dbe8-5678-4818-9adf-fb2dc01ed132 ((null)) 
to 
"/run/NetworkManager/system-connections/tun0-1eb1dbe8-5678-4818-9adf-fb2dc01ed132.nmconnection":
 keyfile writer produces an invalid connection: cannot access file: No such 
file or directory

To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/1998207/+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 1994936] Re: initramfs need to mount efivarfs because kernel 6.0 deprecated 'efivars' sysfs interface

[Cyrus Lien]

Tried Debian mdadm (4.2+20230223-1) it doesn't fix the issue and the
only script mounting efivarfs is mdadm hook scrips.

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

Title:
  initramfs need to mount efivarfs because kernel 6.0 deprecated
  'efivars' sysfs interface

Status in OEM Priority Project:
  In Progress
Status in initramfs-tools package in Ubuntu:
  New
Status in initramfs-tools package in Debian:
  New

Bug description:
  [ Impact ]

  kernel 6.0 deprecated efivars sysfs interface [1]. For Intel VROC
  RAID, mdadm needs initramfs to mount efivarfs instead.

  [1] The commit:
  commit 0f5b2c69a4cbe4166ca24b76d5ada98ed2867741
  Author: Ard Biesheuvel 
  Date: Mon Jun 20 13:34:03 2022 +0200

  efi: vars: Remove deprecated 'efivars' sysfs interface

  [ Test Plan ]

  1. Install initramfs-tools
  2. update-initramfs -u
  3. unmkinitramfs initrd.img-`uname -r` /tmp/extract-initramfs
  4. Check if boot script 00_mount_efivarfs exists in directory 
/tmp/extract-initramfs/main/scripts/init-top/
  5. Check /tmp/extract-initramfs/main/scripts/init-top/ORDER if the boot 
script 00_mount_efivarfs will be execute before udev.

  [ Where problems could occur ]

  Not sure if there any other tools/utilities also need to mount efivarfs as 
early as mdadm but the probability of file conflict should be very low.
  Also, there are no impact mounting efivarfs multiple times.
  mount: /sys/firmware/efi/efivars: efivarfs already mounted on 
/sys/firmware/efi/efivars.

  [ Scope ]

  Jammy, Kinetic

  [ Other Info ]

  The private bug link
  https://bugs.launchpad.net/somerville/+bug/1990231

  debian MR:
  https://salsa.debian.org/kernel-team/initramfs-tools/-/merge_requests/66

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1994936/+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 2007331] Re: Fix HFP mSBC support on Realtek Bluetooth USB controller

[Launchpad Bug Tracker]

This bug was fixed in the package pulseaudio - 1:16.1+dfsg1-1ubuntu3.1

---
pulseaudio (1:16.1+dfsg1-1ubuntu3.1) kinetic; urgency=medium

  [ Kai-Heng Feng ]
  * d/p/0015-bluetooth-Amend-writeout-to-send-more-initial-frames.patch
(LP: #2007331)

 -- Kai-Heng Feng   Wed, 15 Feb 2023
20:20:36 +0800

** Changed in: pulseaudio (Ubuntu Kinetic)
   Status: Fix Committed => Fix Released

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

Title:
  Fix HFP mSBC support on Realtek Bluetooth USB controller

Status in HWE Next:
  New
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in linux-oem-6.0 source package in Jammy:
  Won't Fix
Status in linux-oem-6.1 source package in Jammy:
  Confirmed
Status in pulseaudio source package in Jammy:
  Fix Committed
Status in linux-oem-6.0 source package in Kinetic:
  Invalid
Status in linux-oem-6.1 source package in Kinetic:
  Invalid
Status in pulseaudio source package in Kinetic:
  Fix Released
Status in linux-oem-6.0 source package in Lunar:
  Invalid
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in pulseaudio source package in Lunar:
  Fix Released

Bug description:
  [Impact]
  When a BT headset is connected Realtek BT USB controller, HFP profile can't 
play or record sound when mSBC codec is used.

  [Fix]
  At Linux kernel side, add a Realtek specific quirk to support mSBC.

  At PulseAudio side, send more data frames until the connected device
  sends response.

  [Test]
  Connect different headsets to the said controller, HFP can play and record 
sounds now.
  Also verified A2DP profile is unaffected.

  [Where problems could occur]
  The kernel part is Realtek specific, so the regression risk is very limited.

  The pulseaudio side only affects HFP profile, since the codeflow only
  changes when a mic is present.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2007331/+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 2007331] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for pulseaudio has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Fix HFP mSBC support on Realtek Bluetooth USB controller

Status in HWE Next:
  New
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in linux-oem-6.0 source package in Jammy:
  Won't Fix
Status in linux-oem-6.1 source package in Jammy:
  Confirmed
Status in pulseaudio source package in Jammy:
  Fix Committed
Status in linux-oem-6.0 source package in Kinetic:
  Invalid
Status in linux-oem-6.1 source package in Kinetic:
  Invalid
Status in pulseaudio source package in Kinetic:
  Fix Released
Status in linux-oem-6.0 source package in Lunar:
  Invalid
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in pulseaudio source package in Lunar:
  Fix Released

Bug description:
  [Impact]
  When a BT headset is connected Realtek BT USB controller, HFP profile can't 
play or record sound when mSBC codec is used.

  [Fix]
  At Linux kernel side, add a Realtek specific quirk to support mSBC.

  At PulseAudio side, send more data frames until the connected device
  sends response.

  [Test]
  Connect different headsets to the said controller, HFP can play and record 
sounds now.
  Also verified A2DP profile is unaffected.

  [Where problems could occur]
  The kernel part is Realtek specific, so the regression risk is very limited.

  The pulseaudio side only affects HFP profile, since the codeflow only
  changes when a mic is present.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2007331/+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 2007625] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for openldap has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  New upstream microrelease 2.5.14

Status in openldap package in Ubuntu:
  Invalid
Status in openldap source package in Jammy:
  Fix Committed
Status in openldap source package in Kinetic:
  Fix Released

Bug description:
  [ Impact ]

   * MRE for the latest stable OpenLDAP 2.5.x release, 2.5.14.

  This update includes bugfixes only following the SRU policy exception
  defined at https://wiki.ubuntu.com/OpenLDAPUpdates.

  [ Major Changes ]

   * See the list of bugs fixed in this release here:

  https://lists.openldap.org/hyperkitty/list/openldap-
  annou...@openldap.org/thread/TZQHR4SIWUA5BZTKDAKSFDOOGDVU4TU7/

  [ Test Plan ]

   * Upstream gitlab pipeline results:
  https://git.openldap.org/openldap/openldap/-/pipelines/4816

   * Upstream "call for testing":

  
https://lists.openldap.org/hyperkitty/list/openldap-techni...@openldap.org/message/ZJTFCIIY3HHUZIHENR3TUDGGFWIVJOCF/
  
https://lists.openldap.org/hyperkitty/list/openldap-techni...@openldap.org/message/XVFN3TCIDUZCWJA7RKFTZI2762UELAGM/
  
https://lists.openldap.org/hyperkitty/list/openldap-techni...@openldap.org/message/YZIFGANGSBCV2E547KS5C6DJGJ4Z4CEX/

   * As described in the MRE wiki page for OpenLDAP, the test plan is to
  build the package in bileto and make sure that (1) all build-time
  tests pass and (2) all autopkgtest runs (from reverse dependencies)
  also pass.

   * Build log (amd64) confirming that the build-time testsuite has been 
performed and completed successfully:
    - kinetic: 
https://launchpad.net/~sergiodj/+archive/ubuntu/openldap/+build/25633699/+files/buildlog_ubuntu-kinetic-amd64.openldap_2.5.14+dfsg-0ubuntu0.22.10.1~ppa1_BUILDING.txt.gz
    - jammy: 
https://launchpad.net/~sergiodj/+archive/ubuntu/openldap/+build/25601017/+files/buildlog_ubuntu-jammy-amd64.openldap_2.5.14+dfsg-0ubuntu0.22.04.1~ppa1_BUILDING.txt.gz

   * Bileto ticket: N/A (bileto is not working at the moment)

  [ Where problems could occur ]

   * Upstream tests are always executed during build-time. There are
  many reverse dependencies whose dep8 tests depend on OpenLDAP so the
  coverage is good. Nevertheless, there is always a risk for something
  to break since we are dealing with a microrelease upgrade. Whenever a
  test failure is detected, we will be on top of it and make sure it
  doesn't affect existing users.

  [ Other Info ]

   * This is a reoccurring MRE. See below for links to previous OpenLDAP
  MREs.

   * CVEs fixed by this release:
     - None.

  Current versions in supported releases that got updates:
   openldap | 2.5.13+dfsg-0ubuntu0.22.04.1 | jammy-updates   | source

  Special cases:
  - None.

  Previous MREs for OpenLDAP:
  - https://pad.lv/1977627
  - https://pad.lv/1983618

  As usual we test and prep from the PPA and then push through
  SRU/Security as applicable.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/2007625/+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 2007625] Re: New upstream microrelease 2.5.14

[Launchpad Bug Tracker]

This bug was fixed in the package openldap -
2.5.14+dfsg-0ubuntu0.22.10.1

---
openldap (2.5.14+dfsg-0ubuntu0.22.10.1) kinetic; urgency=medium

  * New upstream version (LP: #2007625).
- Several fixes, including memory leaks that affect slapd and
  certain slapo modules.

 -- Sergio Durigan Junior   Wed, 01 Mar
2023 14:04:25 -0500

** Changed in: openldap (Ubuntu Kinetic)
   Status: Fix Committed => Fix Released

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

Title:
  New upstream microrelease 2.5.14

Status in openldap package in Ubuntu:
  Invalid
Status in openldap source package in Jammy:
  Fix Committed
Status in openldap source package in Kinetic:
  Fix Released

Bug description:
  [ Impact ]

   * MRE for the latest stable OpenLDAP 2.5.x release, 2.5.14.

  This update includes bugfixes only following the SRU policy exception
  defined at https://wiki.ubuntu.com/OpenLDAPUpdates.

  [ Major Changes ]

   * See the list of bugs fixed in this release here:

  https://lists.openldap.org/hyperkitty/list/openldap-
  annou...@openldap.org/thread/TZQHR4SIWUA5BZTKDAKSFDOOGDVU4TU7/

  [ Test Plan ]

   * Upstream gitlab pipeline results:
  https://git.openldap.org/openldap/openldap/-/pipelines/4816

   * Upstream "call for testing":

  
https://lists.openldap.org/hyperkitty/list/openldap-techni...@openldap.org/message/ZJTFCIIY3HHUZIHENR3TUDGGFWIVJOCF/
  
https://lists.openldap.org/hyperkitty/list/openldap-techni...@openldap.org/message/XVFN3TCIDUZCWJA7RKFTZI2762UELAGM/
  
https://lists.openldap.org/hyperkitty/list/openldap-techni...@openldap.org/message/YZIFGANGSBCV2E547KS5C6DJGJ4Z4CEX/

   * As described in the MRE wiki page for OpenLDAP, the test plan is to
  build the package in bileto and make sure that (1) all build-time
  tests pass and (2) all autopkgtest runs (from reverse dependencies)
  also pass.

   * Build log (amd64) confirming that the build-time testsuite has been 
performed and completed successfully:
    - kinetic: 
https://launchpad.net/~sergiodj/+archive/ubuntu/openldap/+build/25633699/+files/buildlog_ubuntu-kinetic-amd64.openldap_2.5.14+dfsg-0ubuntu0.22.10.1~ppa1_BUILDING.txt.gz
    - jammy: 
https://launchpad.net/~sergiodj/+archive/ubuntu/openldap/+build/25601017/+files/buildlog_ubuntu-jammy-amd64.openldap_2.5.14+dfsg-0ubuntu0.22.04.1~ppa1_BUILDING.txt.gz

   * Bileto ticket: N/A (bileto is not working at the moment)

  [ Where problems could occur ]

   * Upstream tests are always executed during build-time. There are
  many reverse dependencies whose dep8 tests depend on OpenLDAP so the
  coverage is good. Nevertheless, there is always a risk for something
  to break since we are dealing with a microrelease upgrade. Whenever a
  test failure is detected, we will be on top of it and make sure it
  doesn't affect existing users.

  [ Other Info ]

   * This is a reoccurring MRE. See below for links to previous OpenLDAP
  MREs.

   * CVEs fixed by this release:
     - None.

  Current versions in supported releases that got updates:
   openldap | 2.5.13+dfsg-0ubuntu0.22.04.1 | jammy-updates   | source

  Special cases:
  - None.

  Previous MREs for OpenLDAP:
  - https://pad.lv/1977627
  - https://pad.lv/1983618

  As usual we test and prep from the PPA and then push through
  SRU/Security as applicable.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/2007625/+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 2009317] Re: All Snaps Broken After Release Upgrade

[Georgia Garcia]

Hi! Could you upload some system logs of when this happens?

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

Title:
  All Snaps Broken After Release Upgrade

Status in apparmor package in Ubuntu:
  Confirmed
Status in ubuntu-release-upgrader package in Ubuntu:
  Incomplete
Status in apparmor source package in Jammy:
  Confirmed
Status in ubuntu-release-upgrader source package in Jammy:
  Incomplete
Status in apparmor source package in Kinetic:
  Confirmed
Status in ubuntu-release-upgrader source package in Kinetic:
  Incomplete

Bug description:
  isa~ lsb_release -rd
  No LSB modules are available.
  Description:  Ubuntu Lunar Lobster (development branch)
  Release:  23.04

  Expected behavior:
  ==
  Installed snaps worked before do-release-upgrade (from Kinetic to Lunar), 
they should also work after.

  Actual behavior:
  ==
  Snaps worked before do-release-upgrade, NONE work after. Printed warning is 
useless. Debugging requires secondary device. This should be a trivial fix 
(re-enable apparmor service at the end of do-release-upgrade).

  isa~ firefox
  snap-confine has elevated permissions and is not confined but should be. 
Refusing to continue to avoid permission escalation attacks
  Please make sure that the snapd.apparmor service is enabled and started.
  isa~ systemctl status snapd.apparmor
  ● snapd.apparmor.service - Load AppArmor profiles managed internally by snapd
   Loaded: loaded (/lib/systemd/system/snapd.apparmor.service; enabled; 
preset: enabled)
   Active: active (exited) since Sun 2023-03-05 18:27:10 MST; 10min ago
     Main PID: 826 (code=exited, status=0/SUCCESS)
  CPU: 43.722s

  Mar 05 18:27:10 isa systemd[1]: Finished Load AppArmor profiles managed 
internally by snapd.
  Notice: journal has been rotated since unit was started, output may be 
incomplete.

  It looks like during the release upgrade apparmor was disabled and
  needs to be re-enabled.

  isa~ systemctl status apparmor
  ○ apparmor.service - Load AppArmor profiles
   Loaded: loaded (/lib/systemd/system/apparmor.service; disabled; preset: 
enabled)
   Active: inactive (dead)
     Docs: man:apparmor(7)
   https://gitlab.com/apparmor/apparmor/wikis/home/
  isa~ systemctl start apparmor

  Notes:
  ==
  This is a reoccurring bug, I hit it when upgrading to Kinetic as well on the 
same device. This does NOT happen on all devices (my other device didn't hit 
this issue when upgrading Jammy->Kinetic->Lunar). This is a bad user experience 
- debugging requires a secondary device because Ubuntu browsers are snap-based.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2009317/+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 2009317] Re: All Snaps Broken After Release Upgrade

[Launchpad Bug Tracker]

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

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

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

Title:
  All Snaps Broken After Release Upgrade

Status in apparmor package in Ubuntu:
  Confirmed
Status in ubuntu-release-upgrader package in Ubuntu:
  Incomplete
Status in apparmor source package in Jammy:
  Confirmed
Status in ubuntu-release-upgrader source package in Jammy:
  Incomplete
Status in apparmor source package in Kinetic:
  Confirmed
Status in ubuntu-release-upgrader source package in Kinetic:
  Incomplete

Bug description:
  isa~ lsb_release -rd
  No LSB modules are available.
  Description:  Ubuntu Lunar Lobster (development branch)
  Release:  23.04

  Expected behavior:
  ==
  Installed snaps worked before do-release-upgrade (from Kinetic to Lunar), 
they should also work after.

  Actual behavior:
  ==
  Snaps worked before do-release-upgrade, NONE work after. Printed warning is 
useless. Debugging requires secondary device. This should be a trivial fix 
(re-enable apparmor service at the end of do-release-upgrade).

  isa~ firefox
  snap-confine has elevated permissions and is not confined but should be. 
Refusing to continue to avoid permission escalation attacks
  Please make sure that the snapd.apparmor service is enabled and started.
  isa~ systemctl status snapd.apparmor
  ● snapd.apparmor.service - Load AppArmor profiles managed internally by snapd
   Loaded: loaded (/lib/systemd/system/snapd.apparmor.service; enabled; 
preset: enabled)
   Active: active (exited) since Sun 2023-03-05 18:27:10 MST; 10min ago
     Main PID: 826 (code=exited, status=0/SUCCESS)
  CPU: 43.722s

  Mar 05 18:27:10 isa systemd[1]: Finished Load AppArmor profiles managed 
internally by snapd.
  Notice: journal has been rotated since unit was started, output may be 
incomplete.

  It looks like during the release upgrade apparmor was disabled and
  needs to be re-enabled.

  isa~ systemctl status apparmor
  ○ apparmor.service - Load AppArmor profiles
   Loaded: loaded (/lib/systemd/system/apparmor.service; disabled; preset: 
enabled)
   Active: inactive (dead)
     Docs: man:apparmor(7)
   https://gitlab.com/apparmor/apparmor/wikis/home/
  isa~ systemctl start apparmor

  Notes:
  ==
  This is a reoccurring bug, I hit it when upgrading to Kinetic as well on the 
same device. This does NOT happen on all devices (my other device didn't hit 
this issue when upgrading Jammy->Kinetic->Lunar). This is a bad user experience 
- debugging requires a secondary device because Ubuntu browsers are snap-based.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2009317/+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 2009317] Re: All Snaps Broken After Release Upgrade

[Launchpad Bug Tracker]

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

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

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

Title:
  All Snaps Broken After Release Upgrade

Status in apparmor package in Ubuntu:
  Confirmed
Status in ubuntu-release-upgrader package in Ubuntu:
  Incomplete
Status in apparmor source package in Jammy:
  Confirmed
Status in ubuntu-release-upgrader source package in Jammy:
  Incomplete
Status in apparmor source package in Kinetic:
  Confirmed
Status in ubuntu-release-upgrader source package in Kinetic:
  Incomplete

Bug description:
  isa~ lsb_release -rd
  No LSB modules are available.
  Description:  Ubuntu Lunar Lobster (development branch)
  Release:  23.04

  Expected behavior:
  ==
  Installed snaps worked before do-release-upgrade (from Kinetic to Lunar), 
they should also work after.

  Actual behavior:
  ==
  Snaps worked before do-release-upgrade, NONE work after. Printed warning is 
useless. Debugging requires secondary device. This should be a trivial fix 
(re-enable apparmor service at the end of do-release-upgrade).

  isa~ firefox
  snap-confine has elevated permissions and is not confined but should be. 
Refusing to continue to avoid permission escalation attacks
  Please make sure that the snapd.apparmor service is enabled and started.
  isa~ systemctl status snapd.apparmor
  ● snapd.apparmor.service - Load AppArmor profiles managed internally by snapd
   Loaded: loaded (/lib/systemd/system/snapd.apparmor.service; enabled; 
preset: enabled)
   Active: active (exited) since Sun 2023-03-05 18:27:10 MST; 10min ago
     Main PID: 826 (code=exited, status=0/SUCCESS)
  CPU: 43.722s

  Mar 05 18:27:10 isa systemd[1]: Finished Load AppArmor profiles managed 
internally by snapd.
  Notice: journal has been rotated since unit was started, output may be 
incomplete.

  It looks like during the release upgrade apparmor was disabled and
  needs to be re-enabled.

  isa~ systemctl status apparmor
  ○ apparmor.service - Load AppArmor profiles
   Loaded: loaded (/lib/systemd/system/apparmor.service; disabled; preset: 
enabled)
   Active: inactive (dead)
     Docs: man:apparmor(7)
   https://gitlab.com/apparmor/apparmor/wikis/home/
  isa~ systemctl start apparmor

  Notes:
  ==
  This is a reoccurring bug, I hit it when upgrading to Kinetic as well on the 
same device. This does NOT happen on all devices (my other device didn't hit 
this issue when upgrading Jammy->Kinetic->Lunar). This is a bad user experience 
- debugging requires a secondary device because Ubuntu browsers are snap-based.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2009317/+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 2009317] Re: All Snaps Broken After Release Upgrade

[Launchpad Bug Tracker]

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

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

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

Title:
  All Snaps Broken After Release Upgrade

Status in apparmor package in Ubuntu:
  Confirmed
Status in ubuntu-release-upgrader package in Ubuntu:
  Incomplete
Status in apparmor source package in Jammy:
  Confirmed
Status in ubuntu-release-upgrader source package in Jammy:
  Incomplete
Status in apparmor source package in Kinetic:
  Confirmed
Status in ubuntu-release-upgrader source package in Kinetic:
  Incomplete

Bug description:
  isa~ lsb_release -rd
  No LSB modules are available.
  Description:  Ubuntu Lunar Lobster (development branch)
  Release:  23.04

  Expected behavior:
  ==
  Installed snaps worked before do-release-upgrade (from Kinetic to Lunar), 
they should also work after.

  Actual behavior:
  ==
  Snaps worked before do-release-upgrade, NONE work after. Printed warning is 
useless. Debugging requires secondary device. This should be a trivial fix 
(re-enable apparmor service at the end of do-release-upgrade).

  isa~ firefox
  snap-confine has elevated permissions and is not confined but should be. 
Refusing to continue to avoid permission escalation attacks
  Please make sure that the snapd.apparmor service is enabled and started.
  isa~ systemctl status snapd.apparmor
  ● snapd.apparmor.service - Load AppArmor profiles managed internally by snapd
   Loaded: loaded (/lib/systemd/system/snapd.apparmor.service; enabled; 
preset: enabled)
   Active: active (exited) since Sun 2023-03-05 18:27:10 MST; 10min ago
     Main PID: 826 (code=exited, status=0/SUCCESS)
  CPU: 43.722s

  Mar 05 18:27:10 isa systemd[1]: Finished Load AppArmor profiles managed 
internally by snapd.
  Notice: journal has been rotated since unit was started, output may be 
incomplete.

  It looks like during the release upgrade apparmor was disabled and
  needs to be re-enabled.

  isa~ systemctl status apparmor
  ○ apparmor.service - Load AppArmor profiles
   Loaded: loaded (/lib/systemd/system/apparmor.service; disabled; preset: 
enabled)
   Active: inactive (dead)
     Docs: man:apparmor(7)
   https://gitlab.com/apparmor/apparmor/wikis/home/
  isa~ systemctl start apparmor

  Notes:
  ==
  This is a reoccurring bug, I hit it when upgrading to Kinetic as well on the 
same device. This does NOT happen on all devices (my other device didn't hit 
this issue when upgrading Jammy->Kinetic->Lunar). This is a bad user experience 
- debugging requires a secondary device because Ubuntu browsers are snap-based.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2009317/+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 2011801] Re: gdm3 crashes after installing the 'fuse' package

[Ronzo]

gdm3 crash dump

** Package changed: network-manager (Ubuntu) => gdm3 (Ubuntu)

** Attachment added: "_usr_sbin_gdm3.0.crash"
   
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2011801/+attachment/5654810/+files/_usr_sbin_gdm3.0.crash

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

Title:
  gdm3 crashes after installing the 'fuse' package

Status in gdm3 package in Ubuntu:
  New

Bug description:
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=23.04
  DISTRIB_CODENAME=lunar
  DISTRIB_DESCRIPTION="Ubuntu Lunar Lobster (development branch)"
  PRETTY_NAME="Ubuntu Lunar Lobster (development branch)"
  NAME="Ubuntu"
  VERSION_ID="23.04"
  VERSION="23.04 (Lunar Lobster)"
  VERSION_CODENAME=lunar

  After installing the 'fuse' package gdm3 crashes upon login. Happens
  in Ubuntu 23.04 and 22.10.

  apt purge fuse gdm3 && apt install gdm3 renders the system usable
  again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2011801/+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 2011801] [NEW] gdm3 crashes after installing the 'fuse' package

[Ronzo]

Public bug reported:

DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=23.04
DISTRIB_CODENAME=lunar
DISTRIB_DESCRIPTION="Ubuntu Lunar Lobster (development branch)"
PRETTY_NAME="Ubuntu Lunar Lobster (development branch)"
NAME="Ubuntu"
VERSION_ID="23.04"
VERSION="23.04 (Lunar Lobster)"
VERSION_CODENAME=lunar

After installing the 'fuse' package gdm3 crashes upon login. Happens in
Ubuntu 23.04 and 22.10.

apt purge fuse gdm3 && apt install gdm3 renders the system usable again.

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  gdm3 crashes after installing the 'fuse' package

Status in network-manager package in Ubuntu:
  New

Bug description:
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=23.04
  DISTRIB_CODENAME=lunar
  DISTRIB_DESCRIPTION="Ubuntu Lunar Lobster (development branch)"
  PRETTY_NAME="Ubuntu Lunar Lobster (development branch)"
  NAME="Ubuntu"
  VERSION_ID="23.04"
  VERSION="23.04 (Lunar Lobster)"
  VERSION_CODENAME=lunar

  After installing the 'fuse' package gdm3 crashes upon login. Happens
  in Ubuntu 23.04 and 22.10.

  apt purge fuse gdm3 && apt install gdm3 renders the system usable
  again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2011801/+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 1989410] Re: Not able to connect to hotspot because of WPA2 WPA3 security

[Launchpad Bug Tracker]

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

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

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

Title:
  Not able to connect to hotspot because of WPA2 WPA3 security

Status in wpa package in Ubuntu:
  Confirmed

Bug description:
  Both security WPA2 and WPA3 displaying on the security section due to
  this not able to connect the hotspot.

  Same device and firmware working properly in ubuntu 20.04 OS, But in
  ubuntu 22.04 we are facing this issue.

  "nmcli dev wifi" on client side:

  On Ubuntu 20.04:

  IN-USE

  SSID  ubuntu_new_golden  
  MODE  Infra
  CHAN  1
  RATE  130Mbit/s
  SECURITY WPA2 

  
  On Ubuntu 22.04:

  IN-USE

  SSID  ubuntu_new_golden  
  MODE  Infra
  CHAN  1
  RATE  130Mbit/s
  SECURITY WPA2 WPA3

  Only difference we can see is SECURITY

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libwpa-client-dev 2:2.10-6ubuntu2
  Uname: Linux 5.19.0-rpl-ww37bkc x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5json:
   {
 "result": "skip"
   }
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 15 12:23:41 2022
  Dependencies:
   
  InstallationDate: Installed on 2022-09-10 (4 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1989410/+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 2011796] [NEW] package linux-image-generic-hwe-22.04 5.19.0.35.36~22.04.10 failed to install/upgrade: Abhängigkeitsprobleme - verbleibt unkonfiguriert

[Elisabeth Maubach]

Public bug reported:

problems while updating system

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: linux-image-generic-hwe-22.04 5.19.0.35.36~22.04.10
ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74
Uname: Linux 5.15.0-58-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Thu Mar 16 06:11:44 2023
ErrorMessage: Abhängigkeitsprobleme - verbleibt unkonfiguriert
InstallationDate: Installed on 2022-04-11 (338 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.21.1ubuntu2.1
 apt  2.4.8
SourcePackage: initramfs-tools
Title: package linux-image-generic-hwe-22.04 5.19.0.35.36~22.04.10 failed to 
install/upgrade: Abhängigkeitsprobleme - verbleibt unkonfiguriert
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package jammy

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

Title:
  package linux-image-generic-hwe-22.04 5.19.0.35.36~22.04.10 failed to
  install/upgrade: Abhängigkeitsprobleme - verbleibt unkonfiguriert

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  problems while updating system

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: linux-image-generic-hwe-22.04 5.19.0.35.36~22.04.10
  ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74
  Uname: Linux 5.15.0-58-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Thu Mar 16 06:11:44 2023
  ErrorMessage: Abhängigkeitsprobleme - verbleibt unkonfiguriert
  InstallationDate: Installed on 2022-04-11 (338 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.8
  SourcePackage: initramfs-tools
  Title: package linux-image-generic-hwe-22.04 5.19.0.35.36~22.04.10 failed to 
install/upgrade: Abhängigkeitsprobleme - verbleibt unkonfiguriert
  UpgradeStatus: No upgrade log present (probably fresh install)

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