[Touch-packages] [Bug 1958019] Re: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all

[Alexis CUGLIETTA]

I have the same problem with a ThinkBook 13x Gen 2 with Ubuntu 23.04.
The sound works properly when connecting external speakers or headset,
but I couldn't get the internal speakers to work :( This laptop also has
an ALC287/3306 chip with a CS35L41/CSC3551 amplifier. This seems very
similar what is mentioned here:

https://gist.github.com/lamperez/862763881c0e1c812392b5574727f6ff?permalink_comment_id=4526397

journalctl displays the following message: "Error: ACPI _DSD Properties
are missing for HID CSC3551".

I tried it with the base kernel (6.2.0) as well as the latest one
(6.3.3). The issue occurs regarless of the BIOS version (factory
version: HXCN49WW and 20230517 version: HXCN52WW).

I used the ACPICA tools to extract the ACPI tables and noticed the
entries relative to the CSC3551 did not contain the required "cirrus"
and "dev-index" parameters.

This is quite disapointing and I will juste return the laptop to Lenovo.

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

Title:
  [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No
  sound at all

Status in sound-2.6 (alsa-kernel):
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by
  internal speakers, but it work by headphones connected to standard
  jack aux.

  uname -r
  5.11.0-44-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-44-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 15 15:10:53 2022
  InstallationDate: Installed on 2021-10-11 (96 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2021
  dmi.bios.release: 1.49
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GKCN49WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion 7 16ACHg6
  dmi.ec.firmware.release: 1.49
  dmi.modalias: 
dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6:
  dmi.product.family: Legion 7 16ACHg6
  dmi.product.name: 82N6
  dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6
  dmi.product.version: Legion 7 16ACHg6
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 1983185] [NEW] Recent commit breaks /etc/X11/Xsession

[Alexis Dinno]

Public bug reported:

The following command:

$/etc/X11/Xsession true

opens a dialog with the following error message:

"Xsession: unable to launch "true" X session --- "true" not found;
falling back to default session."

There is a "Okay" button on this message, and clicking it does bad
things if one happens to be running Ubuntu 22.04 on Xorg (or running
Gnome on Xorg, which is seemingly a different option for the the low
latency installation I am running: 5.15.0-43-generic #46-Ubuntu SMP Tue
Jul 12 10:30:17 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux).

See Brendan O'Dea's related comment about this behavior on debian-bugs-
dist: https://www.mail-archive.com/debian-bugs-
d...@lists.debian.org/msg1857023.html

This has consequences in my use of xpra. For example, if I use xpra via
the run_scaled-master script to magnify a single application's interface
for a 4K display I get the error dialog mentioned above, often with
resulting system instability.

This behavior cropped up last month.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
Uname: Linux 5.15.0-43-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon 
znvpair
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  510.73.05  Sat May  7 05:30:26 
UTC 2022
 GCC version:
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: pass
CompositorRunning: None
Date: Sat Jul 30 10:14:43 2022
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
DkmsStatus:
 virtualbox/6.1.34, 5.15.0-41-lowlatency, x86_64: installed
 virtualbox/6.1.34, 5.15.0-43-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Device [8086:3e94] (prog-if 00 [VGA controller])
   Subsystem: Lenovo Device [17aa:2269]
 NVIDIA Corporation GP104GLM [Quadro P5200 Mobile] [10de:1bb5] (rev a1) 
(prog-if 00 [VGA controller])
   Subsystem: Lenovo GP104GLM [Quadro P5200 Mobile] [17aa:2269]
InstallationDate: Installed on 2022-07-13 (16 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
MachineType: LENOVO 20MBCTO1WW
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_aze0rg@/vmlinuz-5.15.0-43-generic 
root=ZFS=rpool/ROOT/ubuntu_aze0rg ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/10/2022
dmi.bios.release: 1.47
dmi.bios.vendor: LENOVO
dmi.bios.version: N2CET64W (1.47 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20MBCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.16
dmi.modalias: 
dmi:bvnLENOVO:bvrN2CET64W(1.47):bd06/10/2022:br1.47:efr1.16:svnLENOVO:pn20MBCTO1WW:pvrThinkPadP72:rvnLENOVO:rn20MBCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20MB_BU_Think_FM_ThinkPadP72:
dmi.product.family: ThinkPad P72
dmi.product.name: 20MBCTO1WW
dmi.product.sku: LENOVO_MT_20MB_BU_Think_FM_ThinkPad P72
dmi.product.version: ThinkPad P72
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.110-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2.1
version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug jammy ubuntu

** Attachment added: "Screenshot of the Xsession error dialog"
   
https://bugs.launchpad.net/bugs/1983185/+attachment/5606047/+files/Xsession%20error%20dialog.png

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

Title:
  Recent commit  breaks /etc/X11/Xsession

Status in xorg package in Ubuntu:
  New

Bug description:
  The following command:

  $/etc/X11/Xsession true

  opens a dialog with the following error message:

  "Xsession: unable 

[Touch-packages] [Bug 1897561] Re: libperl.so.5.30.0 causes nginx to segfault

[Alexis Lecocq]

Hello,

I also found my Nginx server down after several hours. Nowadays
certificates have short life time, their issuance is automated and the
reloading of the servers is mandatory to update the certificates. In
short, an automated action is making the web server crash. In my
opinion, the importance of this bug is very high. This seems to be a
patch for 5.30.2
https://github.com/Perl/perl5/issues/17154#issuecomment-638452287

Kind regards,

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

Title:
  libperl.so.5.30.0 causes nginx to segfault

Status in perl package in Ubuntu:
  Confirmed

Bug description:
  [Steps to reproduce]

  1) launch a focal container
  $ lxc launch images:ubuntu/focal focal-1897561
  2) enter the container
  $ lxc shell focal-1897561
  3) install libnginx-mod-http-perl
  # apt-get install -y nginx-core libnginx-mod-http-perl
  4) check nginx journal
  # journalctl -fu nginx &
  5) reload nginx 2-3 times
  # systemctl reload nginx

  Eventually you will see this from the journal:

  Oct 13 17:13:34 focal-1897561 systemd[1]: Reloaded A high performance web 
server and a reverse proxy server.
  Oct 13 17:13:35 focal-1897561 systemd[1]: nginx.service: Main process exited, 
code=dumped, status=11/SEGV
  Oct 13 17:13:35 focal-1897561 systemd[1]: nginx.service: Killing process 588 
(nginx) with signal SIGKILL.
  Oct 13 17:13:35 focal-1897561 systemd[1]: nginx.service: Killing process 589 
(nginx) with signal SIGKILL.
  Oct 13 17:13:35 focal-1897561 systemd[1]: nginx.service: Killing process 588 
(nginx) with signal SIGKILL.
  Oct 13 17:13:35 focal-1897561 systemd[1]: nginx.service: Killing process 589 
(nginx) with signal SIGKILL.
  Oct 13 17:13:35 focal-1897561 systemd[1]: nginx.service: Failed with result 
'core-dump'.

  [Workaround]

  If libnginx-mod-http-perl is not needed, purging it and restarting
  nginx sidesteps the problem.

  [Original bug description]

  Ubuntu 20.04 LTS

  Looks that Perl 5.30 has bug that causes nginx to die, usually occurs
  after "service nginx reload"

  This looks like nginx, but it really is perl issue:
  https://github.com/Perl/perl5/issues/17154

  Fix done in 5.32 (Perl5 commit bf0) and people are asking backport
  to 5.30 to get fix also to nginx.

  Error:
  Sep 28 07:39:43 host kernel: [1340832.811014] nginx[3253005]: segfault at 10 
ip 7fbf3220d593 sp 7ffd6bba6260 error 4 in 
libperl.so.5.30.0[7fbf321a5000+166000]

  Symptom: Nginx terminates
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  Package: perl 5.30.0-9build1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Tags:  focal uec-images
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1897561/+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 349469] Re: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable

[RICARDO ALEXIS RESTREPO RENGIFO]

Hello I am richard618921. I need to solve the error message debconf:
DbDriver "config": /var/cache/debconf/config.dat is locked by another
process: Resource temporarily unavailable. What can I do ???

** Changed in: aptdaemon
 Assignee: (unassigned) => RICARDO ALEXIS RESTREPO RENGIFO (richard618921)

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

Title:
  debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by
  another process: Resource temporarily unavailable

Status in Aptdaemon:
  Fix Released
Status in Debconf:
  New
Status in aptdaemon package in Ubuntu:
  Invalid
Status in debconf package in Ubuntu:
  Fix Released

Bug description:
  Upgrading packages that use debconf sometimes fail with the following
  error:

  debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by
  another process: Resource temporarily unavailable

To manage notifications about this bug go to:
https://bugs.launchpad.net/aptdaemon/+bug/349469/+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 1883295] [NEW] Xorg freeze

[Alexis]

Public bug reported:

freeze on show applications menu.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
Uname: Linux 5.4.0-37-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.2
Architecture: amd64
BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Jun 12 11:34:08 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Continuously
GpuHangReproducibility: Yes, I can easily reproduce it
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
 Intel Corporation UHD Graphics 605 [8086:3185] (rev 03) (prog-if 00 [VGA 
controller])
   Subsystem: Lenovo UHD Graphics 605 [17aa:39fd]
InstallationDate: Installed on 2020-06-12 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 5986:112b Acer, Inc EasyCamera
 Bus 001 Device 002: ID 8087:0a2a Intel Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 81J2
ProcEnviron:
 LANGUAGE=es_MX:es
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=es_MX.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=8dc8d3e5-254c-4aea-8f07-294a527b810c ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/09/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: 9HCN26WW
dmi.board.asset.tag: No Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0R32823WIN
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo ideapad S130-14IGM
dmi.modalias: 
dmi:bvnLENOVO:bvr9HCN26WW:bd07/09/2019:svnLENOVO:pn81J2:pvrLenovoideapadS130-14IGM:rvnLENOVO:rnLNVNB161216:rvrSDK0R32823WIN:cvnLENOVO:ct10:cvrLenovoideapadS130-14IGM:
dmi.product.family: ideapad S130-14IGM
dmi.product.name: 81J2
dmi.product.sku: LENOVO_MT_81J2_BU_idea_FM_ideapad S130-14IGM
dmi.product.version: Lenovo ideapad S130-14IGM
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal freeze ubuntu

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  freeze on show applications menu.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun 12 11:34:08 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation UHD Graphics 605 [8086:3185] (rev 03) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo UHD Graphics 605 [17aa:39fd]
  InstallationDate: Installed on 2020-06-12 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 5986:112b Acer, Inc EasyCamera
   Bus 001 Device 002: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81J2
  ProcEnviron:
   LANGUAGE=es_MX:es
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_MX.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=8dc8d3e5-254c-4aea-8f07-294a527b810c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/09/2019
  

[Touch-packages] [Bug 1814261] Re: gpm prevents loging to the console: spurious “Enter” events seems inserted

[Alexis Wilke]

I rebooted on Ubuntu 16.04 (4.4.0-142-generic) and it worked as expected
once gpm was turned off.

I used the following command to prevent gpm from starting on a reboot
and messing up the login screen:

sudo systemctl mask gpm

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

Title:
  gpm prevents loging to the console: spurious “Enter” events seems
  inserted

Status in gpm package in Ubuntu:
  New

Bug description:
  Hello,

  When our servers boot, We can't login because of spurious “enter”.

  We have this problem on virtual and physical machines since:

  * kernel linux-image-4.15.0-44-generic on bionic
  * kernel linux-image-4.4.0-142-generic on xenial

  To reproduce:

  1. start an ubuntu server with the specific kernel
  2. install GPM
  3. on a console
 1. type the user name “root”
 2. hit “enter”
 3. wait few seconds => spurious “Enter” are send to the console
  4. Stop gpm.service
  5. retry to login on a console => no problem

  
  lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04
  Codename: bionic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gpm/+bug/1814261/+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 1814261] Re: gpm prevents loging to the console: spurious “Enter” events seems inserted

[Alexis Wilke]

I have the exact same problem on Ubuntu 16.04
(vmlinuz-4.4.0-142-generic).

I will try to turn off GPM and see how my console functions without it.

What a surprise though! Not being able to log in the simplest console.
Not something I've seen in ages...

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

Title:
  gpm prevents loging to the console: spurious “Enter” events seems
  inserted

Status in gpm package in Ubuntu:
  New

Bug description:
  Hello,

  When our servers boot, We can't login because of spurious “enter”.

  We have this problem on virtual and physical machines since:

  * kernel linux-image-4.15.0-44-generic on bionic
  * kernel linux-image-4.4.0-142-generic on xenial

  To reproduce:

  1. start an ubuntu server with the specific kernel
  2. install GPM
  3. on a console
 1. type the user name “root”
 2. hit “enter”
 3. wait few seconds => spurious “Enter” are send to the console
  4. Stop gpm.service
  5. retry to login on a console => no problem

  
  lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04
  Codename: bionic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gpm/+bug/1814261/+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 1771185] Re: Secondary monitor not connecting in 18.04 LTS

[Alexis Lecocq]

Same problem with ASUS S406 (no graphic card, CPU i5-8250U)

The most awkward thing is sometimes it is working, sometimes it's not. I
can't figure out why. When not working, even a restart does not re-
enable it but xrandr can enable mirroring laptop display.

Any advice?

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

Title:
  Secondary monitor not connecting in 18.04 LTS

Status in libxrandr package in Ubuntu:
  Confirmed

Bug description:
  I have an Acer Aspire V Nitro VN7-592G-709V with Nvidia Geforce 960M
  (nvidia driver v390) and a Benq W1070 projector.

  I have upgraded from Ubuntu 16.04 to 18.04 and my projector connects
  for a split second and then gets disconnected. In Ubuntu 16.04
  projector was working fine as a mirror display and extended desktop.
  Here's what I already tried:

  - enable the nouveau driver instead of the nvidia driver -> no result
  - enable the on-board intel board with sudo prime-select intel -> no result
  - apt purge nvidia* & reinstall nvidia driver 390 (stable) or 396 (beta) -> 
no result
  - disable nouveau driver, disable nvidia driver from the repository and 
install nvidia driver from nvidia website (both 390 and 396) -> no result
  - installed CCSM (CompizConfig Settings Manager) and disabled display 
auto-detection -> no result
  - played around with the refresh rate (some forums say that the two outputs 
have to be in sync -> no result
  - deleted the whole Ubuntu 18.04 upgrade and installed a fresh 18.04 -> still 
the same issue
  - tried to manually enable the output with xrandr --output HDMI-1-2 --mode 
1920x1920 -> nothing
  - under settings -> devices -> displays I don't see a secondary display (just 
the main one)

  I have the latest libxrandr2, 2:1.5.1-1 under Ubuntu 18.04 (updated to
  day)

  Here is the output of xrandr the very second when I connect the
  projector (then HDMI-1-2 goes disconnected and no modes are
  displayed):

  ~$ xrandr
  Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 16384 x 16384
  eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x 
axis y axis) 345mm x 194mm
     1920x1080 60.02*+  60.0159.9759.9659.93
     1680x1050 59.9559.88
     1600x1024 60.17
     1400x1050 59.98
     1600x900  59.9959.9459.9559.82
     1280x1024 60.02
     1440x900  59.89
     1400x900  59.9659.88
     1280x960  60.00
     1440x810  60.0059.97
     1368x768  59.8859.85
     1360x768  59.8059.96
     1280x800  59.9959.9759.8159.91
     1152x864  60.00
     1280x720  60.0059.9959.8659.74
     1024x768  60.0460.00
     960x720   60.00
     928x696   60.05
     896x672   60.01
     1024x576  59.9559.9659.9059.82
     960x600   59.9360.00
     960x540   59.9659.9959.6359.82
     800x600   60.0060.3256.25
     840x525   60.0159.88
     864x486   59.9259.57
     800x512   60.17
     700x525   59.98
     800x450   59.9559.82
     640x512   60.02
     720x450   59.89
     700x450   59.9659.88
     640x480   60.0059.94
     720x405   59.5158.99
     684x384   59.8859.85
     680x384   59.8059.96
     640x400   59.8859.98
     576x432   60.06
     640x360   59.8659.8359.8459.32
     512x384   60.00
     512x288   60.0059.92
     480x270   59.6359.82
     400x300   60.3256.34
     432x243   59.9259.57
     320x240   60.05
     360x202   59.5159.13
     320x180   59.8459.32
  DP-1-1 disconnected (normal left inverted right x axis y axis)
  HDMI-1-1 disconnected (normal left inverted right x axis y axis)
  DP-1-2 disconnected (normal left inverted right x axis y axis)
  HDMI-1-2 disconnected (normal left inverted right x axis y axis)
    1920x1080 (0x258) 148.500MHz +HSync +VSync
  h: width  1920 start 2008 end 2052 total 2200 skew0 clock  
67.50KHz
  v: height 1080 start 1084 end 1089 total 1125   clock  
60.00Hz
    1920x1080 (0x259) 148.500MHz +HSync +VSync
  h: width  1920 start 2448 end 2492 total 2640 skew0 clock  
56.25KHz
  v: height 1080 start 1084 end 1089 total 1125   clock  
50.00Hz
    1920x1080 (0x25a) 148.352MHz +HSync +VSync
  h: width  1920 start 2008 end 2052 total 2200 skew0 clock  
67.43KHz
  v: height 1080 start 1084 end 1089 total 1125   clock  
59.94Hz
    1920x1080i (0x25b) 74.250MHz +HSync 

[Touch-packages] [Bug 1762314] Re: Sound output too low

[Pierre-Alexis Ciavaldini]

Same issue here on T570 running Manjaro, this is the only bug report talking 
about the problem which seems not related to Ubuntu but to alsa. All sliders 
are up in alsamixer, sound is around half-volume compared to the Windows 
install. ALSA Driver Version: k4.14.67-1-MANJARO.
these did not help: 
https://wiki.archlinux.org/index.php/Advanced_Linux_Sound_Architecture/Troubleshooting#Volume_is_too_low

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

Title:
  Sound output too low

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Sound output on lenovo p51s is too low. No option to go above 100% in volume 
settings. Download pulse audio volume control to raise application and output 
volume to 153%, which helps to some extent, but then leads to distortion. 
  Was running windows 10 on same system and audio was loud enough!
  Also after this morning
  s update, the volume keys no longer work, even after re-mapping them in 
shortcuts.3

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jatin  2098 F pulseaudio
  CurrentDesktop: Budgie:GNOME
  Date: Sun Apr  8 22:50:04 2018
  InstallationDate: Installed on 2018-03-23 (17 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180307.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: High background noise, or volume is too low
  Title: [20HCS06601, Realtek ALC298, Speaker, Internal] Background noise or 
low volume
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/03/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1VET36W (1.26 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HCS06601
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1VET36W(1.26):bd10/03/2017:svnLENOVO:pn20HCS06601:pvrThinkPadP51s:rvnLENOVO:rn20HCS06601:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P51s
  dmi.product.name: 20HCS06601
  dmi.product.version: ThinkPad P51s
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1762314/+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 1779583] Re: cron do_command.c attempts a fork() without testing for errors

[Alexis Wilke]

** Tags removed: trusty
** Tags added: xenial

** Description changed:

  The do_command.c file calls fork() twice.
  
  For the first fork(), the possibility for an error is checked properly
  and an error emitted (see
  https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1702785 for an
  example when that happens: message is "can't fork".) This first fork()
  makes use of a switch() statement as expected.
  
  The second fork(), however, is used inside an if() statement like this:
  
  if (*input_data && fork() == 0) { ... }
  
  Here we can see a couple of problems. After the if block, we have this
  statement:
  
  children++;
  
  which means that we will have to wait on TWO children. However, (1) the
  *input_data could return false and thus the second child may not be
  created at all. (2) the fork() could return -1 meaning that no other
  child is created.
  
  I suppose that the child_process() probably always or nearly always has
  some input_data. Otherwise it would block waiting for a child that was
  never started. And of course, it is relatively rare that fork() fails,
  unless you are running our of RAM (heap or stack can't be allocated) or
  process space (too many processes running concurrently.)
  
  I have a proposed patch to fix the problem. It uses a switch() which
  emits an error in case the fork() fails, but let the program go on as
  before (instead of an immediate exit as in the first fork()).
  
  The children variable gets incremented only when the fork() happens and
  succeeds (default: block in the new switch().)
  
- The do_command.c file did not change between 16.04 (trusty) and 18.04
+ The do_command.c file did not change between 16.04 (xenial) and 18.04
  (bionic beaver), so the patch will work for either version.

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

Title:
  cron do_command.c attempts a fork() without testing for errors

Status in cron package in Ubuntu:
  New

Bug description:
  The do_command.c file calls fork() twice.

  For the first fork(), the possibility for an error is checked properly
  and an error emitted (see
  https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1702785 for an
  example when that happens: message is "can't fork".) This first fork()
  makes use of a switch() statement as expected.

  The second fork(), however, is used inside an if() statement like
  this:

  if (*input_data && fork() == 0) { ... }

  Here we can see a couple of problems. After the if block, we have this
  statement:

  children++;

  which means that we will have to wait on TWO children. However, (1)
  the *input_data could return false and thus the second child may not
  be created at all. (2) the fork() could return -1 meaning that no
  other child is created.

  I suppose that the child_process() probably always or nearly always
  has some input_data. Otherwise it would block waiting for a child that
  was never started. And of course, it is relatively rare that fork()
  fails, unless you are running our of RAM (heap or stack can't be
  allocated) or process space (too many processes running concurrently.)

  I have a proposed patch to fix the problem. It uses a switch() which
  emits an error in case the fork() fails, but let the program go on as
  before (instead of an immediate exit as in the first fork()).

  The children variable gets incremented only when the fork() happens
  and succeeds (default: block in the new switch().)

  The do_command.c file did not change between 16.04 (xenial) and 18.04
  (bionic beaver), so the patch will work for either version.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1779583/+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 1779583] Re: cron do_command.c attempts a fork() without testing for errors

[Alexis Wilke]

I guess I should attempt to compile before submitting a patch. Some
brackets were required in one of the cases.

** Patch added: "Compiling fix to second fork() in child_process()"
   
https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1779583/+attachment/5158458/+files/do_command-2.patch

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

Title:
  cron do_command.c attempts a fork() without testing for errors

Status in cron package in Ubuntu:
  New

Bug description:
  The do_command.c file calls fork() twice.

  For the first fork(), the possibility for an error is checked properly
  and an error emitted (see
  https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1702785 for an
  example when that happens: message is "can't fork".) This first fork()
  makes use of a switch() statement as expected.

  The second fork(), however, is used inside an if() statement like
  this:

  if (*input_data && fork() == 0) { ... }

  Here we can see a couple of problems. After the if block, we have this
  statement:

  children++;

  which means that we will have to wait on TWO children. However, (1)
  the *input_data could return false and thus the second child may not
  be created at all. (2) the fork() could return -1 meaning that no
  other child is created.

  I suppose that the child_process() probably always or nearly always
  has some input_data. Otherwise it would block waiting for a child that
  was never started. And of course, it is relatively rare that fork()
  fails, unless you are running our of RAM (heap or stack can't be
  allocated) or process space (too many processes running concurrently.)

  I have a proposed patch to fix the problem. It uses a switch() which
  emits an error in case the fork() fails, but let the program go on as
  before (instead of an immediate exit as in the first fork()).

  The children variable gets incremented only when the fork() happens
  and succeeds (default: block in the new switch().)

  The do_command.c file did not change between 16.04 (trusty) and 18.04
  (bionic beaver), so the patch will work for either version.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1779583/+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 1779583] Re: cron do_command.c attempts a fork() without testing for errors

[Alexis Wilke]

** Description changed:

  The do_command.c file calls fork() twice.
  
- For the first for(), the possibility for an error is checked properly
+ For the first fork(), the possibility for an error is checked properly
  and an error emitted (see
  https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1702785 for an
  example when that happens: message is "can't fork".) This first fork()
  makes use of a switch() statement as expected.
  
  The second fork(), however, is used inside an if() statement like this:
  
  if (*input_data && fork() == 0) { ... }
  
  Here we can see a couple of problems. After the if block, we have this
  statement:
  
  children++;
  
  which means that we will have to wait on TWO children. However, (1) the
  *input_data could return false and thus the second child may not be
  created at all. (2) the fork() could return -1 meaning that no other
  child is created.
  
  I suppose that the child_process() probably always or nearly always has
  some input_data. Otherwise it would block waiting for a child that was
  never started. And of course, it is relatively rare that fork() fails,
  unless you are running our of RAM (heap or stack can't be allocated) or
  process space (too many processes running concurrently.)
  
  I have a proposed patch to fix the problem. It uses a switch() which
  emits an error in case the fork() fails, but let the program go on as
  before (instead of an immediate exit as in the first fork()).
  
  The children variable gets incremented only when the fork() happens and
  succeeds (default: block in the new switch().)
  
  The do_command.c file did not change between 16.04 (trusty) and 18.04
  (bionic beaver), so the patch will work for either version.

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

Title:
  cron do_command.c attempts a fork() without testing for errors

Status in cron package in Ubuntu:
  New

Bug description:
  The do_command.c file calls fork() twice.

  For the first fork(), the possibility for an error is checked properly
  and an error emitted (see
  https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1702785 for an
  example when that happens: message is "can't fork".) This first fork()
  makes use of a switch() statement as expected.

  The second fork(), however, is used inside an if() statement like
  this:

  if (*input_data && fork() == 0) { ... }

  Here we can see a couple of problems. After the if block, we have this
  statement:

  children++;

  which means that we will have to wait on TWO children. However, (1)
  the *input_data could return false and thus the second child may not
  be created at all. (2) the fork() could return -1 meaning that no
  other child is created.

  I suppose that the child_process() probably always or nearly always
  has some input_data. Otherwise it would block waiting for a child that
  was never started. And of course, it is relatively rare that fork()
  fails, unless you are running our of RAM (heap or stack can't be
  allocated) or process space (too many processes running concurrently.)

  I have a proposed patch to fix the problem. It uses a switch() which
  emits an error in case the fork() fails, but let the program go on as
  before (instead of an immediate exit as in the first fork()).

  The children variable gets incremented only when the fork() happens
  and succeeds (default: block in the new switch().)

  The do_command.c file did not change between 16.04 (trusty) and 18.04
  (bionic beaver), so the patch will work for either version.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1779583/+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 1702785] Re: High memory and "can't fork" on heavy long-lived cron daemon

[Alexis Wilke]

Actually, an immediate fix for you guys may be to make sure that there
is some *input_data. I have no clue what that means in terms of
administrative setup, though. But maybe someone else can help in that
area. The really bad statement looks like this:

if (*input_data && fork() == 0) {
... // handle input_data
exit(0);
}

children++;

The children variable counts the number of successful fork()'s. Only in
this case (1) the fork() is never checked for failure and (2) if
*input_data is false, then the fork() does not even happen. Yet, either
way, children is always increment! Ouch! As an administrator, it may not
be possible to always make sure there is something in input_data. But it
is not unlikely that this is what makes many cron fork() wait forever
and thus increase memory. I have not had that problem on my end, I was
just reading the code for fun...

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

Title:
  High memory and "can't fork" on heavy long-lived cron daemon

Status in cron package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 14.04.5 LTS, cron 3.0pl1-124ubuntu2

  On a server with heavy cron use (a few thousand entries across cron.d
  / users, several runs per second, a few dozen forks running at any
  given time), cron will creep up in memory usage.  Last I saw was 6GB
  RSS, at which point it will start doing:

  Jul  6 07:01:27 host cron[21699]: (CRON) error (can't fork)

  Not all runs will fail, but this trend will continue until cron is
  restarted.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1702785/+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 1702785] Re: High memory and "can't fork" on heavy long-lived cron daemon

[Alexis Wilke]

I found a bug in the code as described in this issue:
https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1779583

The bug would not prevent the error you're seeing, however, there is a
second fork() which, if it fails, will block that part of cron, which
would therefore leak. So if it happens "on the wrong fork()", (1) you
won't see any logs and (2) you get a cron "process" which gets stuck
waiting for a second child that was never created.

I included a patch too.

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

Title:
  High memory and "can't fork" on heavy long-lived cron daemon

Status in cron package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 14.04.5 LTS, cron 3.0pl1-124ubuntu2

  On a server with heavy cron use (a few thousand entries across cron.d
  / users, several runs per second, a few dozen forks running at any
  given time), cron will creep up in memory usage.  Last I saw was 6GB
  RSS, at which point it will start doing:

  Jul  6 07:01:27 host cron[21699]: (CRON) error (can't fork)

  Not all runs will fail, but this trend will continue until cron is
  restarted.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1702785/+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 1779583] Re: cron do_command.c attempts a fork() without testing for errors

[Alexis Wilke]

This may be one solution to the problem reported here:

https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1702785

Because when the second fork() fails, the cron process waits for 2
children, one of which doesn't even exist and thus cron is stuck with "a
ton" of memory allocated. This would also happen if *input_data is
false. So not just because the fork() fails... but it could be because
it does not even happen.

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

Title:
  cron do_command.c attempts a fork() without testing for errors

Status in cron package in Ubuntu:
  New

Bug description:
  The do_command.c file calls fork() twice.

  For the first for(), the possibility for an error is checked properly
  and an error emitted (see
  https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1702785 for an
  example when that happens: message is "can't fork".) This first fork()
  makes use of a switch() statement as expected.

  The second fork(), however, is used inside an if() statement like
  this:

  if (*input_data && fork() == 0) { ... }

  Here we can see a couple of problems. After the if block, we have this
  statement:

  children++;

  which means that we will have to wait on TWO children. However, (1)
  the *input_data could return false and thus the second child may not
  be created at all. (2) the fork() could return -1 meaning that no
  other child is created.

  I suppose that the child_process() probably always or nearly always
  has some input_data. Otherwise it would block waiting for a child that
  was never started. And of course, it is relatively rare that fork()
  fails, unless you are running our of RAM (heap or stack can't be
  allocated) or process space (too many processes running concurrently.)

  I have a proposed patch to fix the problem. It uses a switch() which
  emits an error in case the fork() fails, but let the program go on as
  before (instead of an immediate exit as in the first fork()).

  The children variable gets incremented only when the fork() happens
  and succeeds (default: block in the new switch().)

  The do_command.c file did not change between 16.04 (trusty) and 18.04
  (bionic beaver), so the patch will work for either version.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1779583/+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 1779583] [NEW] cron do_command.c attempts a fork() without testing for errors

[Alexis Wilke]

Public bug reported:

The do_command.c file calls fork() twice.

For the first for(), the possibility for an error is checked properly
and an error emitted (see
https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1702785 for an
example when that happens: message is "can't fork".) This first fork()
makes use of a switch() statement as expected.

The second fork(), however, is used inside an if() statement like this:

if (*input_data && fork() == 0) { ... }

Here we can see a couple of problems. After the if block, we have this
statement:

children++;

which means that we will have to wait on TWO children. However, (1) the
*input_data could return false and thus the second child may not be
created at all. (2) the fork() could return -1 meaning that no other
child is created.

I suppose that the child_process() probably always or nearly always has
some input_data. Otherwise it would block waiting for a child that was
never started. And of course, it is relatively rare that fork() fails,
unless you are running our of RAM (heap or stack can't be allocated) or
process space (too many processes running concurrently.)

I have a proposed patch to fix the problem. It uses a switch() which
emits an error in case the fork() fails, but let the program go on as
before (instead of an immediate exit as in the first fork()).

The children variable gets incremented only when the fork() happens and
succeeds (default: block in the new switch().)

The do_command.c file did not change between 16.04 (trusty) and 18.04
(bionic beaver), so the patch will work for either version.

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


** Tags: bionic patch trusty

** Patch added: "Fix to second fork() in child_process()"
   
https://bugs.launchpad.net/bugs/1779583/+attachment/5158449/+files/do_command.patch

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

Title:
  cron do_command.c attempts a fork() without testing for errors

Status in cron package in Ubuntu:
  New

Bug description:
  The do_command.c file calls fork() twice.

  For the first for(), the possibility for an error is checked properly
  and an error emitted (see
  https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1702785 for an
  example when that happens: message is "can't fork".) This first fork()
  makes use of a switch() statement as expected.

  The second fork(), however, is used inside an if() statement like
  this:

  if (*input_data && fork() == 0) { ... }

  Here we can see a couple of problems. After the if block, we have this
  statement:

  children++;

  which means that we will have to wait on TWO children. However, (1)
  the *input_data could return false and thus the second child may not
  be created at all. (2) the fork() could return -1 meaning that no
  other child is created.

  I suppose that the child_process() probably always or nearly always
  has some input_data. Otherwise it would block waiting for a child that
  was never started. And of course, it is relatively rare that fork()
  fails, unless you are running our of RAM (heap or stack can't be
  allocated) or process space (too many processes running concurrently.)

  I have a proposed patch to fix the problem. It uses a switch() which
  emits an error in case the fork() fails, but let the program go on as
  before (instead of an immediate exit as in the first fork()).

  The children variable gets incremented only when the fork() happens
  and succeeds (default: block in the new switch().)

  The do_command.c file did not change between 16.04 (trusty) and 18.04
  (bionic beaver), so the patch will work for either version.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1779583/+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 1708341] [NEW] package libldap-2.4-2 2.4.42+dfsg-2ubuntu3.1 failed to install/upgrade: intentando sobreescribir el compartido `/etc/ldap/ldap.conf', que es distinto de otras inst

[Alexis Lira]

Public bug reported:

i just wanted to upgrade and appeared that error

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libldap-2.4-2 2.4.42+dfsg-2ubuntu3.1
ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
Uname: Linux 4.4.0-79-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
Date: Wed Aug  2 01:41:22 2017
ErrorMessage: intentando sobreescribir el compartido `/etc/ldap/ldap.conf', que 
es distinto de otras instancias del paquetes libldap-2.4-2:amd64
InstallationDate: Installed on 2016-08-04 (363 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.24
SourcePackage: openldap
Title: package libldap-2.4-2 2.4.42+dfsg-2ubuntu3.1 failed to install/upgrade: 
intentando sobreescribir el compartido `/etc/ldap/ldap.conf', que es distinto 
de otras instancias del paquetes libldap-2.4-2:amd64
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

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

Title:
  package libldap-2.4-2 2.4.42+dfsg-2ubuntu3.1 failed to
  install/upgrade: intentando sobreescribir el compartido
  `/etc/ldap/ldap.conf', que es distinto de otras instancias del
  paquetes libldap-2.4-2:amd64

Status in openldap package in Ubuntu:
  New

Bug description:
  i just wanted to upgrade and appeared that error

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libldap-2.4-2 2.4.42+dfsg-2ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
  Uname: Linux 4.4.0-79-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Wed Aug  2 01:41:22 2017
  ErrorMessage: intentando sobreescribir el compartido `/etc/ldap/ldap.conf', 
que es distinto de otras instancias del paquetes libldap-2.4-2:amd64
  InstallationDate: Installed on 2016-08-04 (363 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: openldap
  Title: package libldap-2.4-2 2.4.42+dfsg-2ubuntu3.1 failed to 
install/upgrade: intentando sobreescribir el compartido `/etc/ldap/ldap.conf', 
que es distinto de otras instancias del paquetes libldap-2.4-2:amd64
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1708341/+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 1707048] [NEW] bsdutils conflict

[Alexis Lira]

Public bug reported:

dpkg: error al procesar el paquete bsdutils (--configure):
 el paquete bsdutils no está listo para configurarse
 no se puede configurar (estado actual `half-installed')
Se encontraron errores al procesar:
 bsdutils
E: Sub-process /usr/bin/dpkg returned an error code (1)

** Affects: util-linux (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  bsdutils conflict

Status in util-linux package in Ubuntu:
  New

Bug description:
  dpkg: error al procesar el paquete bsdutils (--configure):
   el paquete bsdutils no está listo para configurarse
   no se puede configurar (estado actual `half-installed')
  Se encontraron errores al procesar:
   bsdutils
  E: Sub-process /usr/bin/dpkg returned an error code (1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1707048/+subscriptions

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

Re: [Touch-packages] [Bug 1703350] Re: package liburcu4:i386 0.9.1-3 failed to install/upgrade: El paquete está en un estado grave de inconsistencia - debe reinstalarlo antes de intentar su configurac

[ALEXIS]

Sorry, after Windows 7

2017-07-17 16:18 GMT-03:00 Andreas Hasenack :

> Thanks for getting back to us and letting us know your system is working
> correctly again. I will leave this bug marked as incomplete because
> there is not enough data for us to act on a fix. If you come across more
> information on this issue, or if it happens again, please post back here
> and we can take another look. Otherwise, it will expire in due course
> and automatically close.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1703350
>
> Title:
>   package liburcu4:i386 0.9.1-3 failed to install/upgrade: El paquete
>   está en un estado grave de inconsistencia - debe reinstalarlo  antes
>   de intentar su configuración.
>
> Status in liburcu package in Ubuntu:
>   Incomplete
>
> Bug description:
>   it crashes on sudo apt update
>
>   ProblemType: Package
>   DistroRelease: Ubuntu 16.04
>   Package: liburcu4:i386 0.9.1-3
>   ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
>   Uname: Linux 4.4.0-83-generic i686
>   ApportVersion: 2.20.1-0ubuntu2.9
>   Architecture: i386
>   Date: Mon Jul 10 07:44:55 2017
>   Dependencies:
>gcc-6-base 6.0.1-0ubuntu1
>libc6 2.23-0ubuntu9
>libgcc1 1:6.0.1-0ubuntu1
>   ErrorMessage: El paquete está en un estado grave de inconsistencia -
> debe reinstalarlo  antes de intentar su configuración.
>   InstallationDate: Installed on 2017-05-20 (51 days ago)
>   InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386
> (20160719)
>   RelatedPackageVersions:
>dpkg 1.18.4ubuntu1.2
>apt  1.2.20
>   SourcePackage: liburcu
>   Title: package liburcu4:i386 0.9.1-3 failed to install/upgrade: El
> paquete está en un estado grave de inconsistencia - debe reinstalarlo
> antes de intentar su configuración.
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/liburcu/+bug/
> 1703350/+subscriptions
>

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

Title:
  package liburcu4:i386 0.9.1-3 failed to install/upgrade: El paquete
  está en un estado grave de inconsistencia - debe reinstalarlo  antes
  de intentar su configuración.

Status in liburcu package in Ubuntu:
  Incomplete

Bug description:
  it crashes on sudo apt update

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: liburcu4:i386 0.9.1-3
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic i686
  ApportVersion: 2.20.1-0ubuntu2.9
  Architecture: i386
  Date: Mon Jul 10 07:44:55 2017
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu9
   libgcc1 1:6.0.1-0ubuntu1
  ErrorMessage: El paquete está en un estado grave de inconsistencia - debe 
reinstalarlo  antes de intentar su configuración.
  InstallationDate: Installed on 2017-05-20 (51 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: liburcu
  Title: package liburcu4:i386 0.9.1-3 failed to install/upgrade: El paquete 
está en un estado grave de inconsistencia - debe reinstalarlo  antes de 
intentar su configuración.
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

Re: [Touch-packages] [Bug 1703350] Re: package liburcu4:i386 0.9.1-3 failed to install/upgrade: El paquete está en un estado grave de inconsistencia - debe reinstalarlo antes de intentar su configurac

[ALEXIS]

Andreas, my english is very poor.
The problem happens before Window 7 checks the hard disck for
inconsistences and I stopped it.
Thank you for your help.

2017-07-17 16:18 GMT-03:00 Andreas Hasenack :

> Thanks for getting back to us and letting us know your system is working
> correctly again. I will leave this bug marked as incomplete because
> there is not enough data for us to act on a fix. If you come across more
> information on this issue, or if it happens again, please post back here
> and we can take another look. Otherwise, it will expire in due course
> and automatically close.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1703350
>
> Title:
>   package liburcu4:i386 0.9.1-3 failed to install/upgrade: El paquete
>   está en un estado grave de inconsistencia - debe reinstalarlo  antes
>   de intentar su configuración.
>
> Status in liburcu package in Ubuntu:
>   Incomplete
>
> Bug description:
>   it crashes on sudo apt update
>
>   ProblemType: Package
>   DistroRelease: Ubuntu 16.04
>   Package: liburcu4:i386 0.9.1-3
>   ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
>   Uname: Linux 4.4.0-83-generic i686
>   ApportVersion: 2.20.1-0ubuntu2.9
>   Architecture: i386
>   Date: Mon Jul 10 07:44:55 2017
>   Dependencies:
>gcc-6-base 6.0.1-0ubuntu1
>libc6 2.23-0ubuntu9
>libgcc1 1:6.0.1-0ubuntu1
>   ErrorMessage: El paquete está en un estado grave de inconsistencia -
> debe reinstalarlo  antes de intentar su configuración.
>   InstallationDate: Installed on 2017-05-20 (51 days ago)
>   InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386
> (20160719)
>   RelatedPackageVersions:
>dpkg 1.18.4ubuntu1.2
>apt  1.2.20
>   SourcePackage: liburcu
>   Title: package liburcu4:i386 0.9.1-3 failed to install/upgrade: El
> paquete está en un estado grave de inconsistencia - debe reinstalarlo
> antes de intentar su configuración.
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/liburcu/+bug/
> 1703350/+subscriptions
>

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

Title:
  package liburcu4:i386 0.9.1-3 failed to install/upgrade: El paquete
  está en un estado grave de inconsistencia - debe reinstalarlo  antes
  de intentar su configuración.

Status in liburcu package in Ubuntu:
  Incomplete

Bug description:
  it crashes on sudo apt update

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: liburcu4:i386 0.9.1-3
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic i686
  ApportVersion: 2.20.1-0ubuntu2.9
  Architecture: i386
  Date: Mon Jul 10 07:44:55 2017
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu9
   libgcc1 1:6.0.1-0ubuntu1
  ErrorMessage: El paquete está en un estado grave de inconsistencia - debe 
reinstalarlo  antes de intentar su configuración.
  InstallationDate: Installed on 2017-05-20 (51 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: liburcu
  Title: package liburcu4:i386 0.9.1-3 failed to install/upgrade: El paquete 
está en un estado grave de inconsistencia - debe reinstalarlo  antes de 
intentar su configuración.
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

Re: [Touch-packages] [Bug 1703350] Re: package liburcu4:i386 0.9.1-3 failed to install/upgrade: El paquete está en un estado grave de inconsistencia - debe reinstalarlo antes de intentar su configurac

[ALEXIS]

I had restarted my pc and it works well

2017-07-14 5:23 GMT-03:00 ChristianEhrhardt
<1703...@bugs.launchpad.net>:

> And - did it fix your issue around the inconsistent package?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1703350
>
> Title:
>   package liburcu4:i386 0.9.1-3 failed to install/upgrade: El paquete
>   está en un estado grave de inconsistencia - debe reinstalarlo  antes
>   de intentar su configuración.
>
> Status in liburcu package in Ubuntu:
>   Incomplete
>
> Bug description:
>   it crashes on sudo apt update
>
>   ProblemType: Package
>   DistroRelease: Ubuntu 16.04
>   Package: liburcu4:i386 0.9.1-3
>   ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
>   Uname: Linux 4.4.0-83-generic i686
>   ApportVersion: 2.20.1-0ubuntu2.9
>   Architecture: i386
>   Date: Mon Jul 10 07:44:55 2017
>   Dependencies:
>gcc-6-base 6.0.1-0ubuntu1
>libc6 2.23-0ubuntu9
>libgcc1 1:6.0.1-0ubuntu1
>   ErrorMessage: El paquete está en un estado grave de inconsistencia -
> debe reinstalarlo  antes de intentar su configuración.
>   InstallationDate: Installed on 2017-05-20 (51 days ago)
>   InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386
> (20160719)
>   RelatedPackageVersions:
>dpkg 1.18.4ubuntu1.2
>apt  1.2.20
>   SourcePackage: liburcu
>   Title: package liburcu4:i386 0.9.1-3 failed to install/upgrade: El
> paquete está en un estado grave de inconsistencia - debe reinstalarlo
> antes de intentar su configuración.
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/liburcu/+bug/
> 1703350/+subscriptions
>

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

Title:
  package liburcu4:i386 0.9.1-3 failed to install/upgrade: El paquete
  está en un estado grave de inconsistencia - debe reinstalarlo  antes
  de intentar su configuración.

Status in liburcu package in Ubuntu:
  Incomplete

Bug description:
  it crashes on sudo apt update

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: liburcu4:i386 0.9.1-3
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic i686
  ApportVersion: 2.20.1-0ubuntu2.9
  Architecture: i386
  Date: Mon Jul 10 07:44:55 2017
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu9
   libgcc1 1:6.0.1-0ubuntu1
  ErrorMessage: El paquete está en un estado grave de inconsistencia - debe 
reinstalarlo  antes de intentar su configuración.
  InstallationDate: Installed on 2017-05-20 (51 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: liburcu
  Title: package liburcu4:i386 0.9.1-3 failed to install/upgrade: El paquete 
está en un estado grave de inconsistencia - debe reinstalarlo  antes de 
intentar su configuración.
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

Re: [Touch-packages] [Bug 1703350] Re: package liburcu4:i386 0.9.1-3 failed to install/upgrade: El paquete está en un estado grave de inconsistencia - debe reinstalarlo antes de intentar su configurac

[ALEXIS]

Done

2017-07-11 16:10 GMT-03:00 Andreas Hasenack :

> Thanks for filing this bug in Ubuntu.
>
> Could you please try the following commands:
>
> sudo apt update
>
> sudo apt install --reinstall liburcu4
>
> And report back here please?
>
> Thanks
>
>
> ** Changed in: liburcu (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1703350
>
> Title:
>   package liburcu4:i386 0.9.1-3 failed to install/upgrade: El paquete
>   está en un estado grave de inconsistencia - debe reinstalarlo  antes
>   de intentar su configuración.
>
> Status in liburcu package in Ubuntu:
>   Incomplete
>
> Bug description:
>   it crashes on sudo apt update
>
>   ProblemType: Package
>   DistroRelease: Ubuntu 16.04
>   Package: liburcu4:i386 0.9.1-3
>   ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
>   Uname: Linux 4.4.0-83-generic i686
>   ApportVersion: 2.20.1-0ubuntu2.9
>   Architecture: i386
>   Date: Mon Jul 10 07:44:55 2017
>   Dependencies:
>gcc-6-base 6.0.1-0ubuntu1
>libc6 2.23-0ubuntu9
>libgcc1 1:6.0.1-0ubuntu1
>   ErrorMessage: El paquete está en un estado grave de inconsistencia -
> debe reinstalarlo  antes de intentar su configuración.
>   InstallationDate: Installed on 2017-05-20 (51 days ago)
>   InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386
> (20160719)
>   RelatedPackageVersions:
>dpkg 1.18.4ubuntu1.2
>apt  1.2.20
>   SourcePackage: liburcu
>   Title: package liburcu4:i386 0.9.1-3 failed to install/upgrade: El
> paquete está en un estado grave de inconsistencia - debe reinstalarlo
> antes de intentar su configuración.
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/liburcu/+bug/
> 1703350/+subscriptions
>

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

Title:
  package liburcu4:i386 0.9.1-3 failed to install/upgrade: El paquete
  está en un estado grave de inconsistencia - debe reinstalarlo  antes
  de intentar su configuración.

Status in liburcu package in Ubuntu:
  Incomplete

Bug description:
  it crashes on sudo apt update

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: liburcu4:i386 0.9.1-3
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic i686
  ApportVersion: 2.20.1-0ubuntu2.9
  Architecture: i386
  Date: Mon Jul 10 07:44:55 2017
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu9
   libgcc1 1:6.0.1-0ubuntu1
  ErrorMessage: El paquete está en un estado grave de inconsistencia - debe 
reinstalarlo  antes de intentar su configuración.
  InstallationDate: Installed on 2017-05-20 (51 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: liburcu
  Title: package liburcu4:i386 0.9.1-3 failed to install/upgrade: El paquete 
está en un estado grave de inconsistencia - debe reinstalarlo  antes de 
intentar su configuración.
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/liburcu/+bug/1703350/+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 1703350] [NEW] package liburcu4:i386 0.9.1-3 failed to install/upgrade: El paquete está en un estado grave de inconsistencia - debe reinstalarlo antes de intentar su configuraci

[ALEXIS]

Public bug reported:

it crashes on sudo apt update

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: liburcu4:i386 0.9.1-3
ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
Uname: Linux 4.4.0-83-generic i686
ApportVersion: 2.20.1-0ubuntu2.9
Architecture: i386
Date: Mon Jul 10 07:44:55 2017
Dependencies:
 gcc-6-base 6.0.1-0ubuntu1
 libc6 2.23-0ubuntu9
 libgcc1 1:6.0.1-0ubuntu1
ErrorMessage: El paquete está en un estado grave de inconsistencia - debe 
reinstalarlo  antes de intentar su configuración.
InstallationDate: Installed on 2017-05-20 (51 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: liburcu
Title: package liburcu4:i386 0.9.1-3 failed to install/upgrade: El paquete está 
en un estado grave de inconsistencia - debe reinstalarlo  antes de intentar su 
configuración.
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-package i386 xenial

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

Title:
  package liburcu4:i386 0.9.1-3 failed to install/upgrade: El paquete
  está en un estado grave de inconsistencia - debe reinstalarlo  antes
  de intentar su configuración.

Status in liburcu package in Ubuntu:
  New

Bug description:
  it crashes on sudo apt update

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: liburcu4:i386 0.9.1-3
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic i686
  ApportVersion: 2.20.1-0ubuntu2.9
  Architecture: i386
  Date: Mon Jul 10 07:44:55 2017
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu9
   libgcc1 1:6.0.1-0ubuntu1
  ErrorMessage: El paquete está en un estado grave de inconsistencia - debe 
reinstalarlo  antes de intentar su configuración.
  InstallationDate: Installed on 2017-05-20 (51 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: liburcu
  Title: package liburcu4:i386 0.9.1-3 failed to install/upgrade: El paquete 
está en un estado grave de inconsistencia - debe reinstalarlo  antes de 
intentar su configuración.
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/liburcu/+bug/1703350/+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 1703126] [NEW] package liblttng-ust-ctl2:i386 2.7.1-1 failed to install/upgrade: problemas de dependencias - se deja sin configurar

[ALEXIS]

Public bug reported:

crash at start

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: liblttng-ust-ctl2:i386 2.7.1-1
ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
Uname: Linux 4.4.0-83-generic i686
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: i386
Date: Sat Jul  8 12:05:54 2017
Dependencies:
 gcc-6-base 6.0.1-0ubuntu1
 libc6 2.23-0ubuntu9
 libgcc1 1:6.0.1-0ubuntu1
 liburcu4 0.9.1-3
ErrorMessage: problemas de dependencias - se deja sin configurar
InstallationDate: Installed on 2017-05-20 (49 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: ust
Title: package liblttng-ust-ctl2:i386 2.7.1-1 failed to install/upgrade: 
problemas de dependencias - se deja sin configurar
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-package i386 xenial

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

Title:
  package liblttng-ust-ctl2:i386 2.7.1-1 failed to install/upgrade:
  problemas de dependencias - se deja sin configurar

Status in ust package in Ubuntu:
  New

Bug description:
  crash at start

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: liblttng-ust-ctl2:i386 2.7.1-1
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic i686
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: i386
  Date: Sat Jul  8 12:05:54 2017
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu9
   libgcc1 1:6.0.1-0ubuntu1
   liburcu4 0.9.1-3
  ErrorMessage: problemas de dependencias - se deja sin configurar
  InstallationDate: Installed on 2017-05-20 (49 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: ust
  Title: package liblttng-ust-ctl2:i386 2.7.1-1 failed to install/upgrade: 
problemas de dependencias - se deja sin configurar
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ust/+bug/1703126/+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 1292324] Re: Support non-root X

[Yves-Alexis Perez]

Robert,

I know you weren't interested in this but would review patches if
needed. Could you point people to the right directions on where to drop
privileges before running X server and stuff like that?

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

Title:
  Support non-root X

Status in Light Display Manager:
  Triaged
Status in lightdm package in Ubuntu:
  Triaged
Status in lightdm package in Debian:
  Confirmed
Status in lightdm package in Fedora:
  Unknown

Bug description:
  Support running X as an unprivileged user.

  Currently X servers are run as root means a large complex process has
  access to services it might not need (i.e. potential security and
  stability problems). It would be nice to run each X server as either
  an unprivileged user or in the session they are being used in.

  Logind provides a system for sharing access to the display and input
  devices so this can be done - this seems like the most likely
  implementation of non-root X.

  For more information see Hans de Goede request:
  http://lists.freedesktop.org/archives/lightdm/2014-March/000539.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1292324/+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 1695564] [NEW] package linux-firmware 1.157.10 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1

[hermes alexis]

Public bug reported:

I intented upgrade my ubuntu but in the end show me the message error

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-firmware 1.157.10
ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
Uname: Linux 4.4.0-72-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
Date: Fri Jun  2 20:34:42 2017
Dependencies:
 
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-trusty-amd64-20140620-0
ErrorMessage: el subproceso instalado el script post-installation devolvió el 
código de salida de error 1
InstallationDate: Installed on 2017-03-16 (78 days ago)
InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: initramfs-tools
Title: package linux-firmware 1.157.10 failed to install/upgrade: el subproceso 
instalado el script post-installation devolvió el código de salida de error 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package need-duplicate-check xenial

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

Title:
  package linux-firmware 1.157.10 failed to install/upgrade: el
  subproceso instalado el script post-installation devolvió el código de
  salida de error 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  I intented upgrade my ubuntu but in the end show me the message error

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-firmware 1.157.10
  ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
  Uname: Linux 4.4.0-72-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Fri Jun  2 20:34:42 2017
  Dependencies:
   
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-20140620-0
  ErrorMessage: el subproceso instalado el script post-installation devolvió el 
código de salida de error 1
  InstallationDate: Installed on 2017-03-16 (78 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: initramfs-tools
  Title: package linux-firmware 1.157.10 failed to install/upgrade: el 
subproceso instalado el script post-installation devolvió el código de salida 
de error 1
  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/1695564/+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 1620636] Re: Fails to pair with Bose QC35 headphones

[Alexis Laporte]

I have a Sony MDR 1000X, which is similar to the Bose.

I have the same problem and tried the solutions people here mentionned
(I had the same choppy streaming when forcing ControllerMode = bredr).

The only difference is that my headset «pairs» but there's no sound
after it.

I can send any output log that might be needed.

Thanks.

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

Title:
  Fails to pair with Bose QC35 headphones

Status in Canonical System Image:
  In Progress
Status in bluez package in Ubuntu:
  In Progress

Bug description:
  I am unable to pair the Bose QC35 BT headphones with Ubuntu, either
  Ubuntu desktop running 16.04 LTS with bluez 5.37 (also tried bluez
  5.41 from installed from yakkety archive), nor using Ubuntu Touch rc-
  proposed build for Turbo #174. I'm trying to pair through the normal
  bluetooth control panel brought up through the bluetooth indicator.

  I've attached some logs that show it failing to pair. If I can provide
  anymore useful information about the headphones, please let me know.

  Syslog with bluetoothd debugging enabled:
  http://pastebin.ubuntu.com/23141394/

  btmon output:
  http://pastebin.ubuntu.com/23141446/

  bluetoothctl output:
  http://pastebin.ubuntu.com/23141510/

  With Linux kernel 4.8.0 and bluez 4.52:
  ---

  bluetoothctl: http://pastebin.ubuntu.com/23256457/
  btmon: http://pastebin.ubuntu.com/23256471/

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1620636/+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 1648620] [NEW] package procps 2:3.3.10-4ubuntu2.3 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1

[Alexis]

Public bug reported:

it is related with smfpd daemon; but i don't know how. 
in the console appears the message:
"
insserv: There is a loop at service plymouth if started
insserv: Starting smfpd depends on plymouth and therefore on system facility 
`$all' which can not be true!
"

i have installed the xerox phaser 3140 driver for linux two weeks ago.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: procps 2:3.3.10-4ubuntu2.3
ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
Uname: Linux 4.4.0-47-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2.2
Architecture: amd64
Date: Thu Dec  8 17:47:59 2016
ErrorMessage: el subproceso instalado el script post-installation devolvió el 
código de salida de error 1
InstallationDate: Installed on 2016-09-11 (88 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.15
SourcePackage: procps
Title: package procps 2:3.3.10-4ubuntu2.3 failed to install/upgrade: el 
subproceso instalado el script post-installation devolvió el código de salida 
de error 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

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

Title:
  package procps 2:3.3.10-4ubuntu2.3 failed to install/upgrade: el
  subproceso instalado el script post-installation devolvió el código de
  salida de error 1

Status in procps package in Ubuntu:
  New

Bug description:
  it is related with smfpd daemon; but i don't know how. 
  in the console appears the message:
  "
  insserv: There is a loop at service plymouth if started
  insserv: Starting smfpd depends on plymouth and therefore on system facility 
`$all' which can not be true!
  "

  i have installed the xerox phaser 3140 driver for linux two weeks ago.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: procps 2:3.3.10-4ubuntu2.3
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.2
  Architecture: amd64
  Date: Thu Dec  8 17:47:59 2016
  ErrorMessage: el subproceso instalado el script post-installation devolvió el 
código de salida de error 1
  InstallationDate: Installed on 2016-09-11 (88 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: procps
  Title: package procps 2:3.3.10-4ubuntu2.3 failed to install/upgrade: el 
subproceso instalado el script post-installation devolvió el código de salida 
de error 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1648620/+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 1551623] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed

[alexis]

same issue exactly from 16.04 to 16.10
here come my log files too.

** Attachment added: "log files"
   
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1551623/+attachment/4774006/+files/dist-upgrade.tar.gz

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

Title:
  package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in gconf package in Ubuntu:
  Triaged

Bug description:
  When upgrading from 15.10 to 16.04Beta (2016-03-01), this error occured, 
alongside many others related to systemd and gnome. 
  Notice that despite all warnings and errors, finally, the system remained 
functional.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: gconf2 3.2.6-3ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
  Uname: Linux 4.4.0-8-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Tue Mar  1 09:21:15 2016
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2015-10-04 (148 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.3
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to xenial on 2016-03-01 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1551623/+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 1567540] Re: ntpd crashed with SIGABRT (was: ntp crashes everytime the network goes up or down.)

[Alexis Huxley]

I am using ntp 1:4.2.8p4+dfsg-3ubuntu5 (i.e. the currently available
package) and it crashes consistently and silently at, or shortly after,
system boot up. If I restart it using systemctl then it crashes. If I
start it manually from the command line just running 'ntpd' then it
seems to keep running for longer, but even then it eventually silently
crashes.

This is on a KVM-based VM running as a mail server with stock Postfix
and Dovecot. I mention these packages because all other VMs (and PMs)
have no issues, despite identical underlying installations.

I've installed 1:4.2.8p4+dfsg-3ubuntu5.1 and this seems to have fixed
the problem.

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

Title:
  ntpd crashed with SIGABRT (was: ntp crashes everytime the network goes
  up or down.)

Status in NTP:
  Fix Released
Status in ntp package in Ubuntu:
  Fix Released
Status in ntp source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

   * In NTP 4.2.8p4 there are several races that can cause a crash on
     startup or on a bit later but still on startup by DNS querying a
     peer.

   * The crash obviously affects users, especially as it seems - due to
     its racy nature - not appear on most, but severely hamstring some
     other users.

   * The details are a bit blurred, but overall there were four fixes
     upstream that address just this "kind of issue" that seemed to
     surface post 4.2.8p4.

  [Test Case]

   * Start NTP (service)

   * Expectation: work

   * Failure: Crash

   * Constraints: this is a race, it seems to appear at <0.1% chance to
     all systems I have (or lower - as I just can say it didn't trigger in
     1000 tests). But that matches other reports. OTOH for some systems it
     seems to trigger >50% which also matches the high amount of crash
     reports (close to 20k now) as referred in comment 43

  [Regression Potential]

   * Eventually the change is rather invasive as it changes the locking
     scheme of parts of the code - so there surely is some regression
     potential.

   * Fortunately all of this change is upstream and tested there
     quite heavily. Most of it for a few months already.

   * I tested as good as I could and could neither in code nor in test
     find an obvious weakness, and looking at all the crash reports it is
     about time.

  [Other Info]

   * While all study of bugs, upstream changes and tests suggest we
     haven't broken anything, still I have to admit that "on my own" I
     can't confirm that it fixed the bug. So we are really dependent on
     the reporters here that seem to have the kind of hardware where it
     "crashes reliably".

  

  ntp crashes every time the network goes up or down while the system is 
running and also crashes after booting up without network.
  ---
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-03-12 (26 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160224)
  NtpStatus: ntpq: read: Connection refused
  Package: ntp 1:4.2.8p4+dfsg-3ubuntu4
  PackageArchitecture: amd64
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-17-generic 
root=UUID=306314bc-efcb-4c2d-b0e9-e05ec92ed0f0 ro
  ProcVersionSignature: Ubuntu 4.4.0-17.33-generic 4.4.6
  Tags:  xenial
  Uname: Linux 4.4.0-17-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  ---
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-03-12 (31 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160224)
  NtpStatus: ntpq: read: Connection refused
  Package: ntp 1:4.2.8p4+dfsg-3ubuntu5
  PackageArchitecture: amd64
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic 
root=UUID=306314bc-efcb-4c2d-b0e9-e05ec92ed0f0 ro
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Tags:  xenial
  Uname: Linux 4.4.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  ---
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-04-13 (0 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160412)
  NtpStatus: ntpq: read: Connection refused
  Package: ntp 1:4.2.8p4+dfsg-3ubuntu5
  PackageArchitecture: amd64
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic 
root=UUID=13f57794-2e19-4a56-836a-94185bba5ec5 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Tags:  xenial
  Uname: Linux 4.4.0-18-generic x86_64
  

[Touch-packages] [Bug 1292324] Re: Support non-root X

[Yves-Alexis Perez]

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

** Also affects: lightdm (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809067
   Importance: Unknown
   Status: Unknown

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

Title:
  Support non-root X

Status in Light Display Manager:
  Triaged
Status in lightdm package in Ubuntu:
  Triaged
Status in lightdm package in Debian:
  Unknown

Bug description:
  Support running X as an unprivileged user.

  Currently X servers are run as root means a large complex process has
  access to services it might not need (i.e. potential security and
  stability problems). It would be nice to run each X server as either
  an unprivileged user or in the session they are being used in.

  Logind provides a system for sharing access to the display and input
  devices so this can be done - this seems like the most likely
  implementation of non-root X.

  For more information see Hans de Goede request:
  http://lists.freedesktop.org/archives/lightdm/2014-March/000539.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1292324/+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 1516831] Re: XDMCP Request packet with no addresses crashes LightDM

[Yves-Alexis Perez]

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2015-8316

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

Title:
  XDMCP Request packet with no addresses crashes LightDM

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.14 series:
  Fix Released
Status in Light Display Manager 1.16 series:
  Fix Released
Status in lightdm package in Ubuntu:
  Fix Committed
Status in lightdm source package in Wily:
  Fix Committed

Bug description:
  [Impact]
  If LightDM receives an XDMCP Request packet with no addresses then it will 
attempt to access a negative index into an array and crash. This only occurs if 
the XDMCP server is enabled.

  [Test Case]
  1. Enable XDMCP in lightdm.conf:
  [XDMCPServer]
  enabled=true
  2. Start LightDM
  3. Send an XDMCP Request without an empty addresses field (valid XDMCP 
servers do not send this).

  Expected result:
  The request is ignored.

  Observed result:
  LightDM crashes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1516831/+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 1478552] [NEW] rsyslog-pgsql hangs after backgrounding

[Alexis Mousset]

Public bug reported:

If rsyslog is configured to forward logs into PostgreSQL with ompgsl,
when restarting rsyslog with restart rsyslog and producing logs,
rsyslog hangs until being restarted. Then it processes some logs, but
the problem quickly happens again.

This issue has been fixed in rsyslog 7.4.10. The changelog says:
* If rsyslog was set to auto-background itself (default code behaviour, but 
many distros now turn it off for good reason), ompgsql could not properly 
connect. This could even lead to a segfault. The core reason was that a PG 
session handle was kept open over a fork, something that is explicitely 
forbidden in the PG API. 
(http://www.rsyslog.com/changelog-for-7-4-10-v7-stable/)

The patch
(https://github.com/rsyslog/rsyslog/commit/ff091b7ea963b63130cfb77af57f137e632bf765)
works fine with 7.4.4.

The problem does not happen on 15.04 as backgrounding is disabled.

Information:

# lsb_release -rd
Description:Ubuntu 14.04.2 LTS
Release:14.04

# apt-cache policy rsyslog-pgsql
rsyslog-pgsql:
  Installed: 7.4.4-1ubuntu2.6

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

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

Title:
  rsyslog-pgsql hangs after backgrounding

Status in rsyslog package in Ubuntu:
  New

Bug description:
  If rsyslog is configured to forward logs into PostgreSQL with ompgsl,
  when restarting rsyslog with restart rsyslog and producing logs,
  rsyslog hangs until being restarted. Then it processes some logs, but
  the problem quickly happens again.

  This issue has been fixed in rsyslog 7.4.10. The changelog says:
  * If rsyslog was set to auto-background itself (default code behaviour, but 
many distros now turn it off for good reason), ompgsql could not properly 
connect. This could even lead to a segfault. The core reason was that a PG 
session handle was kept open over a fork, something that is explicitely 
forbidden in the PG API. 
(http://www.rsyslog.com/changelog-for-7-4-10-v7-stable/)

  The patch
  
(https://github.com/rsyslog/rsyslog/commit/ff091b7ea963b63130cfb77af57f137e632bf765)
  works fine with 7.4.4.

  The problem does not happen on 15.04 as backgrounding is disabled.

  Information:

  # lsb_release -rd
  Description:  Ubuntu 14.04.2 LTS
  Release:  14.04

  # apt-cache policy rsyslog-pgsql
  rsyslog-pgsql:
Installed: 7.4.4-1ubuntu2.6

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1478552/+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 1309535] Re: Running without pam-kwallet installed issues a warning in auth.log

[Alexis Wilke]

There is information about KWallet.

https://wiki.archlinux.org/index.php/KDE_Wallet

It is marked as optional because it is allowed to fail as it does when
you are running with Gnome (unity uses Gnome by default). So this is not
a bug. You make comment out the lines as shown in #19 but you may regret
it if you switch to KUbuntu one day...

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

Title:
  Running without pam-kwallet installed issues a warning in auth.log

Status in lightdm package in Ubuntu:
  Won't Fix
Status in pam package in Ubuntu:
  Won't Fix

Bug description:
  After upgrading to lightdm 1.10.0-0ubuntu2 I started to see this error
  in auth.log:

  Apr 10 14:34:54 simon-laptop lightdm: PAM unable to dlopen(pam_kwallet.so): 
/lib/security/pam_kwallet.so: cannot open shared object file: No such file or 
directory
  Apr 10 14:34:54 simon-laptop lightdm: PAM adding faulty module: pam_kwallet.so

  This seems like a regression because with lightdm 1.10.0-0ubuntu1 or
  before I didn't have this error showing. FYI, I don't have the pam-
  kwallet package installed.

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

  $ apt-cache policy lightdm pam-kwallet
  lightdm:
Installed: 1.10.0-0ubuntu3
Candidate: 1.10.0-0ubuntu3
Version table:
   *** 1.10.0-0ubuntu3 0
  500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lightdm 1.10.0-0ubuntu3
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Apr 18 09:12:37 2014
  InstallationDate: Installed on 2014-01-26 (81 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140124)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1309535/+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 1370852] Re: Scans all user accounts when not required

[Yves-Alexis Perez]

It seems that this change actually broke .dmrc files on Debian.

I'm currently investigating, but it seems that the files (~/.dmrc and
/var/cache/lightdm/dmrc/user.dmrc) are not updated anymore with the
selected session.

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

Title:
  Scans all user accounts when not required

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Released
Status in “lightdm” package in Ubuntu:
  Fix Released
Status in “lightdm” source package in Trusty:
  In Progress
Status in “lightdm” source package in Utopic:
  Fix Released

Bug description:
  [Impact]
  When AccountsService is not present on startup LightDM scans all the user 
accounts and attempts to access the dmrc file for each user. It does not use 
any information from the dmrc files. If you have many users and/or the dmrc 
files are on a slow filesystem this creates a big startup delay.

  [Test Case]
  1. Start LightDM on a system that doesn't have AccountsService and has many 
users
  Expected result:
  LightDM starts quickly
  Observed result:
  LightDM takes a long time to start

  [Regression potential]
  Low. We now only access the dmrc files when information from them i s 
required (lazy load). Tested with regression tests.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1370852/+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 1370852] Re: Scans all user accounts when not required

[Yves-Alexis Perez]

Actually sorry, that's wrong, it's unrelated, it's due to our own patch
setting USERS_DIR to /var/lib/lightdm (I don't really understand why,
but that's off-topic for this bug).

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

Title:
  Scans all user accounts when not required

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Released
Status in “lightdm” package in Ubuntu:
  Fix Released
Status in “lightdm” source package in Trusty:
  In Progress
Status in “lightdm” source package in Utopic:
  Fix Released

Bug description:
  [Impact]
  When AccountsService is not present on startup LightDM scans all the user 
accounts and attempts to access the dmrc file for each user. It does not use 
any information from the dmrc files. If you have many users and/or the dmrc 
files are on a slow filesystem this creates a big startup delay.

  [Test Case]
  1. Start LightDM on a system that doesn't have AccountsService and has many 
users
  Expected result:
  LightDM starts quickly
  Observed result:
  LightDM takes a long time to start

  [Regression potential]
  Low. We now only access the dmrc files when information from them i s 
required (lazy load). Tested with regression tests.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1370852/+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 1212408] Re: lightdm/gdm needs to set $XDG_CURRENT_DESKTOP

[Yves-Alexis Perez]

It seems that gdm now supports setting XDG_CURRENT_DESKTOP but uses the
DesktopNames [1] property. It might make sense to migrate LightDM to
uses that too.

[1] https://bugzilla.gnome.org/show_bug.cgi?id=727546

** Bug watch added: GNOME Bug Tracker #727546
   https://bugzilla.gnome.org/show_bug.cgi?id=727546

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

Title:
  lightdm/gdm needs to set $XDG_CURRENT_DESKTOP

Status in Light Display Manager:
  Fix Released
Status in “gdm” package in Ubuntu:
  Fix Released
Status in “gnome-session” package in Ubuntu:
  Fix Released
Status in “lightdm” package in Ubuntu:
  Fix Released

Bug description:
  Since the switch to upstart, some processes in the user environment,
  such as gnome-screensaver, now get launched without
  $XDG_CURRENT_DESKTOP being set. This is currently causing screen
  locking issues.

  This used to get set by gnome-session, but it is no longer high enough
  in the process tree to set it for the complete user session.

  Consensus in #ubuntu-desktop was that lightdm should be setting it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1212408/+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 799069] Re: xf86OpenConsole: setpgid failed

[Yves-Alexis Perez]

Seems we don't use the patch since long, and it seems to work fine even
with plymouth. Sorry for the delay.

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

Title:
  xf86OpenConsole: setpgid failed

Status in “lightdm” package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: lightdm

  Oneiric i386 on nvidia (xorg-edgers)

  got logged into xorg.log:

   xf86OpenConsole: setpgid failed: Operation not permitted
   xf86OpenConsole: setsid failed: Operation not permitted

  i've found similar issue reported but against xdm/slim/wdm: Bug #585853 
  #19 post seems to point the real problem:
  - This appears to be caused by the lightdm package not integrating with 
upstart.
  - The plymouth process which holds the console open is waiting for a signal 
that the lightdm job is starting up, so that it can let go of the console; but 
the lightdm package doesn't have an upstart job, so there's no signal sent, 
which means the plymouth and lightdm processes are fighting over the console.

  Note: need to check that the above comments are correct

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: lightdm 0.4.0-0ubuntu5
  ProcVersionSignature: Ubuntu 3.0-1.2-generic-pae 3.0.0-rc3
  Uname: Linux 3.0-1-generic-pae i686
  NonfreeKernelModules: nvidia
  Architecture: i386
  Date: Sat Jun 18 09:26:09 2011
  ProcEnviron:
   LANGUAGE=fr_FR:fr:en_GB:en
   PATH=(custom, no user)
   LANG=fr_FR.utf8
   LC_MESSAGES=fr_FR.utf8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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