[Touch-packages] [Bug 1523100] Re: Alsa not detecting internal microphone [ALC255] (Realtek)

2019-08-10 Thread Kreaninw
@Hui Wang

Are you sure that it wasn't installed? As you can see in my attached
screenshot, I'm using your oem-audio-hda-daily-dkms.

And I can't install an unsigned kernel too, as I'm using UEFI laptop, it
won't let me install the unsigned kernel.

** Attachment added: "Screenshot from 2019-08-11 11-13-39.png"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1523100/+attachment/5281953/+files/Screenshot%20from%202019-08-11%2011-13-39.png

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

Title:
  Alsa not detecting internal microphone [ALC255] (Realtek)

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I've just installed Ubuntu 16.04 alongside Windows 10 on a 64bit Acer
  Aspire VN7-792G and noticed, that the internal microphone doesn't
  work. The computer has been released a couple of months ago and it's
  Intel Skylake -based with a Sunrise Point -based motherboard.

  INFO: The problem exists in Ubuntu 15.10 too, only microphone jack
  detected. Currently using Ubuntu 16.04 for proper hardware support.

  Alsa reports the audio device to be:

  Card: HDA Intel PCH
  Chip: Intel Skylake HDMI

  The speakers are working fine, but both alsamixer and pavucontrol
  (Pulseaudio Volume Control) raport the unplugged external microphone
  connector as the only sound input.

  I have tried many of the alsa model configurations (options snd-hda-
  intel model=something) without success, alsa finds only the microphone
  jack, which works fine when I plug an external microphone in it.

  Here's some info:

  lspci | grep -I audio:

  00:1f.3 Multimedia audio controller: Intel Corporation Sunrise Point-H
  HD Audio (rev 31)

  cat /proc/asound/cards:

  0 [PCH]: HDA-Intel - HDA Intel PCH
  HDA Intel PCH at 0x8432 irq 128

  And a clip from dmesg | grep snd:

  [3.019164] snd_hda_intel :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [3.047505] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC255: 
line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
  [3.047508] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
  [3.047510] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
  [3.047511] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
  [3.047512] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x1e/0x0
  [3.047512] snd_hda_codec_realtek hdaudioC0D0:inputs:
  [3.047514] snd_hda_codec_realtek hdaudioC0D0:  Mic=0x1a

  One problem is that I can't find any model options (options snd-hda-
  intel model=something) or other parameters for the card's model
  (ALC255), I suppose this issue is relatively new.

  /Dennis
  --- 
  ApportVersion: 2.19.2-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dennis 1180 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2015-11-11 (23 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20151110)
  Package: alsa-driver (not installed)
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Tags:  xenial
  Uname: Linux 4.2.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/25/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.02
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire VN7-792G
  dmi.board.vendor: Acer
  dmi.board.version: V1.02
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.02
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.02:bd09/25/2015:svnAcer:pnAspireVN7-792G:pvrV1.02:rvnAcer:rnAspireVN7-792G:rvrV1.02:cvnAcer:ct10:cvrV1.02:
  dmi.product.name: Aspire VN7-792G
  dmi.product.version: V1.02
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1523100/+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 1615389] Re: Searching for files and folders in AO takes much longer than previously

2019-08-10 Thread Launchpad Bug Tracker
[Expired for gnome-shell (Ubuntu) because there has been no activity for
60 days.]

** Changed in: gnome-shell (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Searching for files and folders in AO takes much longer than
  previously

Status in Ubuntu GNOME:
  Expired
Status in gnome-shell package in Ubuntu:
  Expired
Status in tracker package in Ubuntu:
  Expired

Bug description:
  I have noticed that after upgrading from Ubuntu GNOME 15.10 to 16.04
  with GNOME 3.20 that searching for files and folders in the Activities
  Overview takes much much longer when previously (before upgrading) it
  would find them almost instantly as it currently does with
  applications.

  In the preferences for Tracker I have it set up so that it is meant to
  index content. What is interesting though is that for instance it
  might take 5 minutes to find my Artwork folder in my Documents
  directory through the AO. But if I run 'locate Artwork' in Terminal it
  finds it almost instantly.

  So that makes me think that perhaps it is an issue with it not
  properly indexing the content or not being able to retrieve the
  information or something and being forced to do a real-time search.

  But it is becoming rather annoying so I thought I would report it so
  that we can try to figure out what the issue is and hopefully find a
  solution.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1615389/+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 1615389] Re: Searching for files and folders in AO takes much longer than previously

2019-08-10 Thread Launchpad Bug Tracker
[Expired for tracker (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Searching for files and folders in AO takes much longer than
  previously

Status in Ubuntu GNOME:
  Expired
Status in gnome-shell package in Ubuntu:
  Expired
Status in tracker package in Ubuntu:
  Expired

Bug description:
  I have noticed that after upgrading from Ubuntu GNOME 15.10 to 16.04
  with GNOME 3.20 that searching for files and folders in the Activities
  Overview takes much much longer when previously (before upgrading) it
  would find them almost instantly as it currently does with
  applications.

  In the preferences for Tracker I have it set up so that it is meant to
  index content. What is interesting though is that for instance it
  might take 5 minutes to find my Artwork folder in my Documents
  directory through the AO. But if I run 'locate Artwork' in Terminal it
  finds it almost instantly.

  So that makes me think that perhaps it is an issue with it not
  properly indexing the content or not being able to retrieve the
  information or something and being forced to do a real-time search.

  But it is becoming rather annoying so I thought I would report it so
  that we can try to figure out what the issue is and hopefully find a
  solution.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1615389/+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 1615389] Re: Searching for files and folders in AO takes much longer than previously

2019-08-10 Thread Launchpad Bug Tracker
[Expired for Ubuntu GNOME because there has been no activity for 60
days.]

** Changed in: ubuntu-gnome
   Status: Incomplete => Expired

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

Title:
  Searching for files and folders in AO takes much longer than
  previously

Status in Ubuntu GNOME:
  Expired
Status in gnome-shell package in Ubuntu:
  Expired
Status in tracker package in Ubuntu:
  Expired

Bug description:
  I have noticed that after upgrading from Ubuntu GNOME 15.10 to 16.04
  with GNOME 3.20 that searching for files and folders in the Activities
  Overview takes much much longer when previously (before upgrading) it
  would find them almost instantly as it currently does with
  applications.

  In the preferences for Tracker I have it set up so that it is meant to
  index content. What is interesting though is that for instance it
  might take 5 minutes to find my Artwork folder in my Documents
  directory through the AO. But if I run 'locate Artwork' in Terminal it
  finds it almost instantly.

  So that makes me think that perhaps it is an issue with it not
  properly indexing the content or not being able to retrieve the
  information or something and being forced to do a real-time search.

  But it is becoming rather annoying so I thought I would report it so
  that we can try to figure out what the issue is and hopefully find a
  solution.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1615389/+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 1523100] Re: Alsa not detecting internal microphone [ALC255] (Realtek)

2019-08-10 Thread Hui Wang
Please test this kernel:
https://drive.google.com/drive/folders/16OBmEmWPYncLOT-QVlo6vkyy3Ar819aX?usp=sharing

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

Title:
  Alsa not detecting internal microphone [ALC255] (Realtek)

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I've just installed Ubuntu 16.04 alongside Windows 10 on a 64bit Acer
  Aspire VN7-792G and noticed, that the internal microphone doesn't
  work. The computer has been released a couple of months ago and it's
  Intel Skylake -based with a Sunrise Point -based motherboard.

  INFO: The problem exists in Ubuntu 15.10 too, only microphone jack
  detected. Currently using Ubuntu 16.04 for proper hardware support.

  Alsa reports the audio device to be:

  Card: HDA Intel PCH
  Chip: Intel Skylake HDMI

  The speakers are working fine, but both alsamixer and pavucontrol
  (Pulseaudio Volume Control) raport the unplugged external microphone
  connector as the only sound input.

  I have tried many of the alsa model configurations (options snd-hda-
  intel model=something) without success, alsa finds only the microphone
  jack, which works fine when I plug an external microphone in it.

  Here's some info:

  lspci | grep -I audio:

  00:1f.3 Multimedia audio controller: Intel Corporation Sunrise Point-H
  HD Audio (rev 31)

  cat /proc/asound/cards:

  0 [PCH]: HDA-Intel - HDA Intel PCH
  HDA Intel PCH at 0x8432 irq 128

  And a clip from dmesg | grep snd:

  [3.019164] snd_hda_intel :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [3.047505] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC255: 
line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
  [3.047508] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
  [3.047510] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
  [3.047511] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
  [3.047512] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x1e/0x0
  [3.047512] snd_hda_codec_realtek hdaudioC0D0:inputs:
  [3.047514] snd_hda_codec_realtek hdaudioC0D0:  Mic=0x1a

  One problem is that I can't find any model options (options snd-hda-
  intel model=something) or other parameters for the card's model
  (ALC255), I suppose this issue is relatively new.

  /Dennis
  --- 
  ApportVersion: 2.19.2-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dennis 1180 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2015-11-11 (23 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20151110)
  Package: alsa-driver (not installed)
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Tags:  xenial
  Uname: Linux 4.2.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/25/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.02
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire VN7-792G
  dmi.board.vendor: Acer
  dmi.board.version: V1.02
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.02
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.02:bd09/25/2015:svnAcer:pnAspireVN7-792G:pvrV1.02:rvnAcer:rnAspireVN7-792G:rvrV1.02:cvnAcer:ct10:cvrV1.02:
  dmi.product.name: Aspire VN7-792G
  dmi.product.version: V1.02
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1523100/+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 1523100] Re: Alsa not detecting internal microphone [ALC255] (Realtek)

2019-08-10 Thread Hui Wang
According to #27, the deb was not installed too, let me build a kernel,
then you could test the kernel instead of this deb.

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

Title:
  Alsa not detecting internal microphone [ALC255] (Realtek)

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I've just installed Ubuntu 16.04 alongside Windows 10 on a 64bit Acer
  Aspire VN7-792G and noticed, that the internal microphone doesn't
  work. The computer has been released a couple of months ago and it's
  Intel Skylake -based with a Sunrise Point -based motherboard.

  INFO: The problem exists in Ubuntu 15.10 too, only microphone jack
  detected. Currently using Ubuntu 16.04 for proper hardware support.

  Alsa reports the audio device to be:

  Card: HDA Intel PCH
  Chip: Intel Skylake HDMI

  The speakers are working fine, but both alsamixer and pavucontrol
  (Pulseaudio Volume Control) raport the unplugged external microphone
  connector as the only sound input.

  I have tried many of the alsa model configurations (options snd-hda-
  intel model=something) without success, alsa finds only the microphone
  jack, which works fine when I plug an external microphone in it.

  Here's some info:

  lspci | grep -I audio:

  00:1f.3 Multimedia audio controller: Intel Corporation Sunrise Point-H
  HD Audio (rev 31)

  cat /proc/asound/cards:

  0 [PCH]: HDA-Intel - HDA Intel PCH
  HDA Intel PCH at 0x8432 irq 128

  And a clip from dmesg | grep snd:

  [3.019164] snd_hda_intel :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [3.047505] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC255: 
line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
  [3.047508] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
  [3.047510] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
  [3.047511] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
  [3.047512] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x1e/0x0
  [3.047512] snd_hda_codec_realtek hdaudioC0D0:inputs:
  [3.047514] snd_hda_codec_realtek hdaudioC0D0:  Mic=0x1a

  One problem is that I can't find any model options (options snd-hda-
  intel model=something) or other parameters for the card's model
  (ALC255), I suppose this issue is relatively new.

  /Dennis
  --- 
  ApportVersion: 2.19.2-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dennis 1180 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2015-11-11 (23 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20151110)
  Package: alsa-driver (not installed)
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Tags:  xenial
  Uname: Linux 4.2.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/25/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.02
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire VN7-792G
  dmi.board.vendor: Acer
  dmi.board.version: V1.02
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.02
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.02:bd09/25/2015:svnAcer:pnAspireVN7-792G:pvrV1.02:rvnAcer:rnAspireVN7-792G:rvrV1.02:cvnAcer:ct10:cvrV1.02:
  dmi.product.name: Aspire VN7-792G
  dmi.product.version: V1.02
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1523100/+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 1839730] [NEW] passwd

2019-08-10 Thread anthony olszynski
Public bug reported:

i can´t use passwd

root@GAMESTATION:/home/localadmin# passwd
passwd: Modul ist nicht bekannt
passwd: Passwort nicht geändert
root@GAMESTATION:/home/localadmin# 

i have install it again but nothing change this problem.

with system-controll in Users i can it change but not with the terminal.

it produce no crash report to sending it.

my system is configured to use a samba-domain also i have installed sssd
and while it not run winbind.

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


** Tags: passwd

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

** No longer affects: samba (Ubuntu)

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

Title:
  passwd

Status in shadow package in Ubuntu:
  New

Bug description:
  i can´t use passwd

  root@GAMESTATION:/home/localadmin# passwd
  passwd: Modul ist nicht bekannt
  passwd: Passwort nicht geändert
  root@GAMESTATION:/home/localadmin# 

  i have install it again but nothing change this problem.

  with system-controll in Users i can it change but not with the
  terminal.

  it produce no crash report to sending it.

  my system is configured to use a samba-domain also i have installed
  sssd and while it not run winbind.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1839730/+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 1839714] [NEW] Segmentation fault when running apt update using libapt-pkg5.90_1.9.2

2019-08-10 Thread shemgp
Public bug reported:

apt update doesn't work after upgrading apt to 1.9.2 with strace:
openat(AT_FDCWD, "/var/lib/apt/lists/lock", O_RDWR|O_CREAT|O_NOFOLLOW, 0640) = 4
fcntl(4, F_SETFD, FD_CLOEXEC)   = 0
fcntl(4, F_SETLK, {l_type=F_WRLCK, l_whence=SEEK_SET, l_start=0, l_len=0}) = 0
--- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0x5e} ---
+++ killed by SIGSEGV (core dumped) +++

downgrading libapt-pkg5.90 to 1.9.1 fixes it.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: libapt-pkg5.90 1.9.2
ProcVersionSignature: Ubuntu 5.2.0-8.9+test1-generic 5.2.0
Uname: Linux 5.2.0-8-generic x86_64
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
CurrentDesktop: GNOME
Date: Sat Aug 10 21:27:42 2019
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-09-28 (1411 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
SourcePackage: apt
UpgradeStatus: Upgraded to eoan on 2019-07-26 (14 days ago)

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


** Tags: amd64 apport-bug eoan third-party-packages

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

Title:
  Segmentation fault when running apt update using libapt-pkg5.90_1.9.2

Status in apt package in Ubuntu:
  New

Bug description:
  apt update doesn't work after upgrading apt to 1.9.2 with strace:
  openat(AT_FDCWD, "/var/lib/apt/lists/lock", O_RDWR|O_CREAT|O_NOFOLLOW, 0640) 
= 4
  fcntl(4, F_SETFD, FD_CLOEXEC)   = 0
  fcntl(4, F_SETLK, {l_type=F_WRLCK, l_whence=SEEK_SET, l_start=0, l_len=0}) = 0
  --- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0x5e} ---
  +++ killed by SIGSEGV (core dumped) +++

  downgrading libapt-pkg5.90 to 1.9.1 fixes it.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: libapt-pkg5.90 1.9.2
  ProcVersionSignature: Ubuntu 5.2.0-8.9+test1-generic 5.2.0
  Uname: Linux 5.2.0-8-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Aug 10 21:27:42 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-09-28 (1411 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: apt
  UpgradeStatus: Upgraded to eoan on 2019-07-26 (14 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1839714/+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 1839710] Re: package libibus-1.0-5:amd64 1.5.11-1ubuntu2 failed to install/upgrade: package libibus-1.0-5:amd64 is not ready for configuration cannot configure (current status 'h

2019-08-10 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

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

Status in ibus package in Ubuntu:
  New

Bug description:
  reinstall ubuntu to dell G3 15

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libibus-1.0-5:amd64 1.5.11-1ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-1028.31-oem 4.13.16
  Uname: Linux 4.13.0-1028-oem x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  AptOrdering:
   libglib2.0-0: Install
   libglib2.0-0: Configure
   libglib2.0-bin: Configure
   libibus-1.0-5: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sat Aug 10 14:23:49 2019
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-osp1-20171027-1
  DuplicateSignature:
   package:libibus-1.0-5:amd64:1.5.11-1ubuntu2
   Setting up libglib2.0-bin (2.48.2-0ubuntu4.4) ...
   dpkg: error processing package libibus-1.0-5:amd64 (--configure):
package libibus-1.0-5:amd64 is not ready for configuration
  ErrorMessage: package libibus-1.0-5:amd64 is not ready for configuration  
cannot configure (current status 'half-installed')
  InstallationDate: Installed on 2019-08-09 (0 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20171027-10:57
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.5
   apt  1.2.32
  SourcePackage: ibus
  Title: package libibus-1.0-5:amd64 1.5.11-1ubuntu2 failed to install/upgrade: 
package libibus-1.0-5:amd64 is not ready for configuration  cannot configure 
(current status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1839710/+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 1839710] [NEW] package libibus-1.0-5:amd64 1.5.11-1ubuntu2 failed to install/upgrade: package libibus-1.0-5:amd64 is not ready for configuration cannot configure (current status

2019-08-10 Thread egoistsar
Public bug reported:

reinstall ubuntu to dell G3 15

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libibus-1.0-5:amd64 1.5.11-1ubuntu2
ProcVersionSignature: Ubuntu 4.13.0-1028.31-oem 4.13.16
Uname: Linux 4.13.0-1028-oem x86_64
ApportVersion: 2.20.1-0ubuntu2.18
AptOrdering:
 libglib2.0-0: Install
 libglib2.0-0: Configure
 libglib2.0-bin: Configure
 libibus-1.0-5: Configure
 NULL: ConfigurePending
Architecture: amd64
Date: Sat Aug 10 14:23:49 2019
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-xenial-amd64-osp1-20171027-1
DuplicateSignature:
 package:libibus-1.0-5:amd64:1.5.11-1ubuntu2
 Setting up libglib2.0-bin (2.48.2-0ubuntu4.4) ...
 dpkg: error processing package libibus-1.0-5:amd64 (--configure):
  package libibus-1.0-5:amd64 is not ready for configuration
ErrorMessage: package libibus-1.0-5:amd64 is not ready for configuration  
cannot configure (current status 'half-installed')
InstallationDate: Installed on 2019-08-09 (0 days ago)
InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20171027-10:57
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.5
 apt  1.2.32
SourcePackage: ibus
Title: package libibus-1.0-5:amd64 1.5.11-1ubuntu2 failed to install/upgrade: 
package libibus-1.0-5:amd64 is not ready for configuration  cannot configure 
(current status 'half-installed')
UpgradeStatus: No upgrade log present (probably fresh install)

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

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

Status in ibus package in Ubuntu:
  New

Bug description:
  reinstall ubuntu to dell G3 15

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libibus-1.0-5:amd64 1.5.11-1ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-1028.31-oem 4.13.16
  Uname: Linux 4.13.0-1028-oem x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  AptOrdering:
   libglib2.0-0: Install
   libglib2.0-0: Configure
   libglib2.0-bin: Configure
   libibus-1.0-5: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sat Aug 10 14:23:49 2019
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-osp1-20171027-1
  DuplicateSignature:
   package:libibus-1.0-5:amd64:1.5.11-1ubuntu2
   Setting up libglib2.0-bin (2.48.2-0ubuntu4.4) ...
   dpkg: error processing package libibus-1.0-5:amd64 (--configure):
package libibus-1.0-5:amd64 is not ready for configuration
  ErrorMessage: package libibus-1.0-5:amd64 is not ready for configuration  
cannot configure (current status 'half-installed')
  InstallationDate: Installed on 2019-08-09 (0 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20171027-10:57
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.5
   apt  1.2.32
  SourcePackage: ibus
  Title: package libibus-1.0-5:amd64 1.5.11-1ubuntu2 failed to install/upgrade: 
package libibus-1.0-5:amd64 is not ready for configuration  cannot configure 
(current status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1839710/+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 1835809] Re: AMD Ryzen 3000 series fails to boot

2019-08-10 Thread TJ
Today in IRC we were asked if the ficed package is in the 19.04 ISOs. It
isn't so they will fail to boot on AMD Ryzen 3000 CPUs.

Is there a plan to re-build the 19.04 ISOs? If not there ought to at
least be a prominent addition to the 19.04 release notes.

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

Title:
  AMD Ryzen 3000 series fails to boot

Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Disco:
  Fix Released
Status in systemd source package in Eoan:
  In Progress

Bug description:
  [Impact]

   * Systems with AMD Ryzen 3000 series CPUs don't boot.

  [Test Case]

   * Boot with fixed systemd on an AMD Ryzen 3000 series system.

  [Regression Potential]

   * The fix itself is very small, it ignores known to be faulty random
  values returned by the rdrand instruction and use a different random
  source. Those values can still be returned by a properly working
  rdrand implementation in 2 in 2^32 cases on 32 bit arches and in 2 in
  2^64 cases on 64 bit arches, but the fallback to the other random
  source ensures that in those rare occasions a random number can be
  generated.

  [Original Bug Text]

  On the new AMD Ryzen 3000 series CPUs, there is an issue with systemd
  preventing the boot process from completing. This issue does not
  affect the older systemd version in 18.04, but affects the 19.04
  version.

  Here is a screenshot showing what happens:
  
https://www.phoronix.net/image.php?id=ryzen-3700x-3900x-linux&image=amd_zen2_14_show

  I am currently testing a patch to systemd, derived from this pull request:
  https://github.com/systemd/systemd/pull/12536

  This is a high severity issue, as I do not believe there is no
  potential workaround without either a firmware update or an ISO
  respin.

  I have attached a rebase of the potential patch on the current 19.04
  version of systemd for reference. I will provide more details after
  testing.

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