[Touch-packages] [Bug 1767784] Re: [regression] output device not recognized anymore since update 1:8.0-0ubuntu3.9

[Hui Wang]

@Daniel,

Let me revert the change of 1:8.0-0ubuntu3.9?

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

Title:
  [regression] output device not recognized anymore since update
  1:8.0-0ubuntu3.9

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Since the update 1:8.0-0ubuntu3.8 to 1:8.0-0ubuntu3.9 , pulseaudio is
  not showing anymore my soundcard.

  https://launchpad.net/ubuntu/+source/pulseaudio/1:8.0-0ubuntu3.9

  The command "pacmd list-sinks" only shows a dummy output

  When running on a fresh install of ubuntu 16.04, the sound is ok.
  When updating the install with locking the following files to version 
1:8.0-0ubuntu3 the sound keeps working:
  libpulse0:amd64
  libpulse-mainloop-glib0:amd64
  libpulse-dev:amd64
  pulseaudio-module-x11:amd64
  pulseaudio-module-bluetooth:amd64
  pulseaudio-utils:amd64

  When updating to 1:8.0-0ubuntu3.9, I just get a "dummy output".

  I tried running the following versions of Ubuntu (live usb), and get the same 
issue (no need to update to get the problem)
  17.04
  17.10
  18.04

  I attached the result of command "pactl list"
  I have also generated logs during the boot but I don't know how to attach 
multiple files

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1767784/+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 1767815] Re: Can use as a password

[Dhiraj]

Arrgh! I see however can we assign a CVE for this issue, I believe the
issue still exists in the environment, I request for a CVE or please
advise for same.

Cheers!

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

Title:
  Can use  as a password

Status in shadow package in Ubuntu:
  Won't Fix

Bug description:
  Hi Team,

  I am not sure about this, but thought of reporting tho!.

  warmachine@ftw:~$ uname -a
  Linux ftw 4.13.0-39-generic #44~16.04.1-Ubuntu SMP Thu Apr 5 16:43:10 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux

  However, while creating a user `sudo adduser test` I can keep only
   has my password for test user.

  Could someone please look into this and advise me for same. I believe
  password must be robust or only  should not be allowed.

  
  Thank you 
  DM

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1767815/+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 1751252] Re: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: ''

[Daniel van Vugt]

The BadAccess from ShmAttach is coming from the Xorg process somewhere
in here:

static int
ProcShmAttach(ClientPtr client)
{
SHMSTAT_TYPE buf;
ShmDescPtr shmdesc;

REQUEST(xShmAttachReq);

REQUEST_SIZE_MATCH(xShmAttachReq);
LEGAL_NEW_RESOURCE(stuff->shmseg, client);
if ((stuff->readOnly != xTrue) && (stuff->readOnly != xFalse)) {
client->errorValue = stuff->readOnly;
return BadValue;
}
for (shmdesc = Shmsegs; shmdesc; shmdesc = shmdesc->next) {
if (!SHMDESC_IS_FD(shmdesc) && shmdesc->shmid == stuff->shmid)
break;
}
if (shmdesc) {
if (!stuff->readOnly && !shmdesc->writable)
return BadAccess;
shmdesc->refcnt++;
}
else {
shmdesc = malloc(sizeof(ShmDescRec));
if (!shmdesc)
return BadAlloc;
#ifdef SHM_FD_PASSING
shmdesc->is_fd = FALSE;
#endif
shmdesc->addr = shmat(stuff->shmid, 0,
  stuff->readOnly ? SHM_RDONLY : 0);
if ((shmdesc->addr == ((char *) -1)) || SHMSTAT(stuff->shmid, )) {
free(shmdesc);
return BadAccess;
}

/* The attach was performed with root privs. We must
 * do manual checking of access rights for the credentials
 * of the client */

if (shm_access(client, &(SHM_PERM(buf)), stuff->readOnly) == -1) {
shmdt(shmdesc->addr);
free(shmdesc);
return BadAccess;
}

shmdesc->shmid = stuff->shmid;
shmdesc->refcnt = 1;
shmdesc->writable = !stuff->readOnly;
shmdesc->size = SHM_SEGSZ(buf);
shmdesc->next = Shmsegs;
Shmsegs = shmdesc;
}
if (!AddResource(stuff->shmseg, ShmSegType, (void *) shmdesc))
return BadAlloc;
return Success;
}

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

Title:
  [regression] ubiquity crashed in debconf.py:104 with ValueError:
  invalid literal for int() with base 10: ''

Status in OEM Priority Project:
  Triaged
Status in glib2.0 package in Ubuntu:
  Incomplete
Status in ubiquity package in Ubuntu:
  Triaged
Status in glib2.0 source package in Bionic:
  Incomplete
Status in ubiquity source package in Bionic:
  Triaged

Bug description:
  The Ubuntu installer crashes on hiDPI machines (QHD/UHD etc). Although
  it was working some weeks/months ago, so this is a recent regression.

  ---

  https://errors.ubuntu.com/problem/82f7f7e7923663c7b2123c7f1f49af29f6ff4d77
  https://errors.ubuntu.com/problem/735a2b847e0eeab6c8a7b954de5110e43889be15
  https://errors.ubuntu.com/problem/dcd4c9da5ee0cc6d36324446e0e49d39705c90b7
  https://errors.ubuntu.com/problem/cb82f70f9ede07369e8104da9ddf87e28b42257d
  https://errors.ubuntu.com/problem/84a5563af3d2b85f098da832ece4cb8450bfd524

  ---

  WORKAROUND:

  1. Boot into the live session.
  2. Settings > Devices > Displays > Scale = 100%
  3. Click Apply.
  4. Proceed with installation: Click "Install Ubuntu 18.04 LTS".

  ---

  Crashed in a VM in the middle of installation. The host is Bionic up
  to date.

  From the journal
  Feb 23 12:52:27 ubuntu kernel: traps: ubiquity[2646] trap int3 
ip:7f5a76936961 sp:7ffde5090c50 error:0 in 
libglib-2.0.so.0.5400.1[7f5a768e6000+111000]
  Feb 23 12:52:41 ubuntu /install.py[6858]: Exception during installation:
  Feb 23 12:52:41 ubuntu /install.py[6858]: Traceback (most recent call last):
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 757, in 
  Feb 23 12:52:41 ubuntu /install.py[6858]: install.run()
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 135, in run
  Feb 23 12:52:41 ubuntu /install.py[6858]: self.copy_all()
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 505, in copy_all
  Feb 23 12:52:41 ubuntu /install.py[6858]: self.db.progress('SET', 10 + 
copy_progress)
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/lib/python3/dist-packages/debconf.py", line 83, in 
  Feb 23 12:52:41 ubuntu /install.py[6858]: lambda *args, **kw: 
self.command(command, *args, **kw))
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/lib/python3/dist-packages/debconf.py", line 104, in command
  Feb 23 12:52:41 ubuntu /install.py[6858]: status = int(status)
  Feb 23 12:52:41 ubuntu /install.py[6858]: ValueError: invalid literal for 
int() with base 10: ''

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: ubiquity 18.04.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CasperVersion: 1.388
  Date: Fri Feb 23 12:52:28 2018
  ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper 
initrd=/casper/initrd.lz 

[Touch-packages] [Bug 1767784] Re: [regression] output device not recognized anymore since update 1:8.0-0ubuntu3.9

[Launchpad Bug Tracker]

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

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

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

Title:
  [regression] output device not recognized anymore since update
  1:8.0-0ubuntu3.9

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Since the update 1:8.0-0ubuntu3.8 to 1:8.0-0ubuntu3.9 , pulseaudio is
  not showing anymore my soundcard.

  https://launchpad.net/ubuntu/+source/pulseaudio/1:8.0-0ubuntu3.9

  The command "pacmd list-sinks" only shows a dummy output

  When running on a fresh install of ubuntu 16.04, the sound is ok.
  When updating the install with locking the following files to version 
1:8.0-0ubuntu3 the sound keeps working:
  libpulse0:amd64
  libpulse-mainloop-glib0:amd64
  libpulse-dev:amd64
  pulseaudio-module-x11:amd64
  pulseaudio-module-bluetooth:amd64
  pulseaudio-utils:amd64

  When updating to 1:8.0-0ubuntu3.9, I just get a "dummy output".

  I tried running the following versions of Ubuntu (live usb), and get the same 
issue (no need to update to get the problem)
  17.04
  17.10
  18.04

  I attached the result of command "pactl list"
  I have also generated logs during the boot but I don't know how to attach 
multiple files

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1767784/+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 1767784] Re: [regression] output device not recognized anymore since update 1:8.0-0ubuntu3.9

[Daniel van Vugt]

Another instance of this issue has been reported in bug 1768411.

** Description changed:

  Since the update 1:8.0-0ubuntu3.8 to 1:8.0-0ubuntu3.9 , pulseaudio is
  not showing anymore my soundcard.
+ 
+ https://launchpad.net/ubuntu/+source/pulseaudio/1:8.0-0ubuntu3.9
  
  The command "pacmd list-sinks" only shows a dummy output
  
  When running on a fresh install of ubuntu 16.04, the sound is ok.
  When updating the install with locking the following files to version 
1:8.0-0ubuntu3 the sound keeps working:
  libpulse0:amd64
  libpulse-mainloop-glib0:amd64
  libpulse-dev:amd64
  pulseaudio-module-x11:amd64
  pulseaudio-module-bluetooth:amd64
  pulseaudio-utils:amd64
  
  When updating to 1:8.0-0ubuntu3.9, I just get a "dummy output".
  
  I tried running the following versions of Ubuntu (live usb), and get the same 
issue (no need to update to get the problem)
  17.04
  17.10
  18.04
  
  I attached the result of command "pactl list"
  I have also generated logs during the boot but I don't know how to attach 
multiple files

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

Title:
  [regression] output device not recognized anymore since update
  1:8.0-0ubuntu3.9

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Since the update 1:8.0-0ubuntu3.8 to 1:8.0-0ubuntu3.9 , pulseaudio is
  not showing anymore my soundcard.

  https://launchpad.net/ubuntu/+source/pulseaudio/1:8.0-0ubuntu3.9

  The command "pacmd list-sinks" only shows a dummy output

  When running on a fresh install of ubuntu 16.04, the sound is ok.
  When updating the install with locking the following files to version 
1:8.0-0ubuntu3 the sound keeps working:
  libpulse0:amd64
  libpulse-mainloop-glib0:amd64
  libpulse-dev:amd64
  pulseaudio-module-x11:amd64
  pulseaudio-module-bluetooth:amd64
  pulseaudio-utils:amd64

  When updating to 1:8.0-0ubuntu3.9, I just get a "dummy output".

  I tried running the following versions of Ubuntu (live usb), and get the same 
issue (no need to update to get the problem)
  17.04
  17.10
  18.04

  I attached the result of command "pactl list"
  I have also generated logs during the boot but I don't know how to attach 
multiple files

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1767784/+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 1768411] Re: pulseaudio 8.0-0ubuntu3.9 update broke sound on certain hardware, the dummy output profile is selected by default

[Daniel van Vugt]

*** This bug is a duplicate of bug 1767784 ***
https://bugs.launchpad.net/bugs/1767784

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1767784, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** This bug has been marked a duplicate of bug 1767784
   [regression] output device not recognized anymore since update 
1:8.0-0ubuntu3.9

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

Title:
  pulseaudio 8.0-0ubuntu3.9 update broke sound on certain hardware,  the
  dummy output profile is selected by default

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I help manage a few hundred computers and since the last pulseaudio
  update a few weeks ago ( xenial-updates )  from
  pulseaudio_1%3a8.0-0ubuntu3.8_amd64.deb to
  pulseaudio_1%3a8.0-0ubuntu3.9_amd64.deb ( and libpulse0 )  certain
  hardware including dell models 755, 390, and 3050 lost sound.  They
  were working fine for years but now the dummy output profile is
  selected by default. What happened?

  
  This can be worked around by explicitly setting:
  set-card-profile 0 output:analog-stereo
  set-sink-port 1  analog-output-headphones

  
  or by reverting back to pulseaudio_1%3a8.0-0ubuntu3.8_amd64.deb ( along with 
libpulse0 ) .

  
  When I try to use apport it gets to the end and says "apport cannot connect 
to crash database" but I have included example system details in the attachment 
after the output of pacmd list sinks and default.pa.   ( You can only attach 
one file ?!?)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1768411/+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 1768416] [NEW] ath9k_htc Reason: 3=DEAUTH_LEAVING

[sles]

Public bug reported:

After upgrade from 16.04 to 18.04 I can't use wifi.
It is ath9k_htc usb.

I got error Reason: 3=DEAUTH_LEAVING

I used workaround from

https://unix.stackexchange.com/questions/386925/aborting-authentication-
by-local-choice-reason-3-deauth-leaving-when-trying

ln -s /dev/null /etc/systemd/network/99-default.link

And got it working, but, I think , this should be fixed.

Thank you!

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

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

Title:
  ath9k_htc Reason: 3=DEAUTH_LEAVING

Status in network-manager package in Ubuntu:
  New

Bug description:
  After upgrade from 16.04 to 18.04 I can't use wifi.
  It is ath9k_htc usb.

  I got error Reason: 3=DEAUTH_LEAVING

  I used workaround from

  https://unix.stackexchange.com/questions/386925/aborting-
  authentication-by-local-choice-reason-3-deauth-leaving-when-trying

  ln -s /dev/null /etc/systemd/network/99-default.link

  And got it working, but, I think , this should be fixed.

  Thank you!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1768416/+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 1768411] Re: pulseaudio 8.0-0ubuntu3.9 update broke sound on certain hardware, the dummy output profile is selected by default

[Michael Pardee]

here is the text from running:
apport-cli -f -p pulseaudio --save bug.apport


** Attachment added: "bug.apport"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1768411/+attachment/5131795/+files/bug.apport

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

Title:
  pulseaudio 8.0-0ubuntu3.9 update broke sound on certain hardware,  the
  dummy output profile is selected by default

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I help manage a few hundred computers and since the last pulseaudio
  update a few weeks ago ( xenial-updates )  from
  pulseaudio_1%3a8.0-0ubuntu3.8_amd64.deb to
  pulseaudio_1%3a8.0-0ubuntu3.9_amd64.deb ( and libpulse0 )  certain
  hardware including dell models 755, 390, and 3050 lost sound.  They
  were working fine for years but now the dummy output profile is
  selected by default. What happened?

  
  This can be worked around by explicitly setting:
  set-card-profile 0 output:analog-stereo
  set-sink-port 1  analog-output-headphones

  
  or by reverting back to pulseaudio_1%3a8.0-0ubuntu3.8_amd64.deb ( along with 
libpulse0 ) .

  
  When I try to use apport it gets to the end and says "apport cannot connect 
to crash database" but I have included example system details in the attachment 
after the output of pacmd list sinks and default.pa.   ( You can only attach 
one file ?!?)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1768411/+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 1768411] Re: pulseaudio 8.0-0ubuntu3.9 update broke sound on certain hardware, the dummy output profile is selected by default

[Michael Pardee]

here is the default.pa

** Attachment added: "default.pa"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1768411/+attachment/5131794/+files/default.pa

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

Title:
  pulseaudio 8.0-0ubuntu3.9 update broke sound on certain hardware,  the
  dummy output profile is selected by default

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I help manage a few hundred computers and since the last pulseaudio
  update a few weeks ago ( xenial-updates )  from
  pulseaudio_1%3a8.0-0ubuntu3.8_amd64.deb to
  pulseaudio_1%3a8.0-0ubuntu3.9_amd64.deb ( and libpulse0 )  certain
  hardware including dell models 755, 390, and 3050 lost sound.  They
  were working fine for years but now the dummy output profile is
  selected by default. What happened?

  
  This can be worked around by explicitly setting:
  set-card-profile 0 output:analog-stereo
  set-sink-port 1  analog-output-headphones

  
  or by reverting back to pulseaudio_1%3a8.0-0ubuntu3.8_amd64.deb ( along with 
libpulse0 ) .

  
  When I try to use apport it gets to the end and says "apport cannot connect 
to crash database" but I have included example system details in the attachment 
after the output of pacmd list sinks and default.pa.   ( You can only attach 
one file ?!?)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1768411/+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 1768411] Re: pulseaudio 8.0-0ubuntu3.9 update broke sound on certain hardware, the dummy output profile is selected by default

[Michael Pardee]

I see now there is an option for additional attachments (one per
comment) so I'm going to attache the files separately, here is the
output of pacmd list sinks

** Attachment added: "pacmd-list.log"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1768411/+attachment/5131793/+files/pacmd-list.log

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

Title:
  pulseaudio 8.0-0ubuntu3.9 update broke sound on certain hardware,  the
  dummy output profile is selected by default

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I help manage a few hundred computers and since the last pulseaudio
  update a few weeks ago ( xenial-updates )  from
  pulseaudio_1%3a8.0-0ubuntu3.8_amd64.deb to
  pulseaudio_1%3a8.0-0ubuntu3.9_amd64.deb ( and libpulse0 )  certain
  hardware including dell models 755, 390, and 3050 lost sound.  They
  were working fine for years but now the dummy output profile is
  selected by default. What happened?

  
  This can be worked around by explicitly setting:
  set-card-profile 0 output:analog-stereo
  set-sink-port 1  analog-output-headphones

  
  or by reverting back to pulseaudio_1%3a8.0-0ubuntu3.8_amd64.deb ( along with 
libpulse0 ) .

  
  When I try to use apport it gets to the end and says "apport cannot connect 
to crash database" but I have included example system details in the attachment 
after the output of pacmd list sinks and default.pa.   ( You can only attach 
one file ?!?)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1768411/+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 1768411] [NEW] pulseaudio 8.0-0ubuntu3.9 update broke sound on certain hardware, the dummy output profile is selected by default

[Michael Pardee]

Public bug reported:

I help manage a few hundred computers and since the last pulseaudio
update a few weeks ago ( xenial-updates )  from
pulseaudio_1%3a8.0-0ubuntu3.8_amd64.deb to
pulseaudio_1%3a8.0-0ubuntu3.9_amd64.deb ( and libpulse0 )  certain
hardware including dell models 755, 390, and 3050 lost sound.  They were
working fine for years but now the dummy output profile is selected by
default. What happened?


This can be worked around by explicitly setting:
set-card-profile 0 output:analog-stereo
set-sink-port 1  analog-output-headphones


or by reverting back to pulseaudio_1%3a8.0-0ubuntu3.8_amd64.deb ( along with 
libpulse0 ) .


When I try to use apport it gets to the end and says "apport cannot connect to 
crash database" but I have included example system details in the attachment 
after the output of pacmd list sinks and default.pa.   ( You can only attach 
one file ?!?)

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

** Attachment added: "pacmd list sinks and default.pa and  apport bug text 
contents"
   
https://bugs.launchpad.net/bugs/1768411/+attachment/5131792/+files/pacmd-list-and-default-pa-and-apport-bug.txt

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

Title:
  pulseaudio 8.0-0ubuntu3.9 update broke sound on certain hardware,  the
  dummy output profile is selected by default

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I help manage a few hundred computers and since the last pulseaudio
  update a few weeks ago ( xenial-updates )  from
  pulseaudio_1%3a8.0-0ubuntu3.8_amd64.deb to
  pulseaudio_1%3a8.0-0ubuntu3.9_amd64.deb ( and libpulse0 )  certain
  hardware including dell models 755, 390, and 3050 lost sound.  They
  were working fine for years but now the dummy output profile is
  selected by default. What happened?

  
  This can be worked around by explicitly setting:
  set-card-profile 0 output:analog-stereo
  set-sink-port 1  analog-output-headphones

  
  or by reverting back to pulseaudio_1%3a8.0-0ubuntu3.8_amd64.deb ( along with 
libpulse0 ) .

  
  When I try to use apport it gets to the end and says "apport cannot connect 
to crash database" but I have included example system details in the attachment 
after the output of pacmd list sinks and default.pa.   ( You can only attach 
one file ?!?)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1768411/+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 1672120] Re: package click-apparmor 0.3.17 failed to install/upgrade: サブプロセス インストール済みの pre-removal スクリプト はエラー終了ステータス 1 を返しました

[Launchpad Bug Tracker]

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

** Changed in: click-apparmor (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  package click-apparmor 0.3.17 failed to install/upgrade: サブプロセス
  インストール済みの pre-removal スクリプト はエラー終了ステータス 1 を返しました

Status in click-apparmor package in Ubuntu:
  Expired

Bug description:
  I login my account

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: click-apparmor 0.3.17
  ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17
  Uname: Linux 4.8.0-41-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  Date: Sun Mar 12 14:02:19 2017
  ErrorMessage: サブプロセス インストール済みの pre-removal スクリプト はエラー終了ステータス 1 を返しました
  InstallationDate: Installed on 2016-07-17 (237 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64(20160426.1)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.4
  SourcePackage: click-apparmor
  Title: package click-apparmor 0.3.17 failed to install/upgrade: サブプロセス 
インストール済みの pre-removal スクリプト はエラー終了ステータス 1 を返しました
  UpgradeStatus: Upgraded to yakkety on 2016-10-14 (148 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/click-apparmor/+bug/1672120/+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 1682695] Re: System stops recognizing correct screen resolution

[Launchpad Bug Tracker]

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

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

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

Title:
  System stops recognizing correct screen resolution

Status in xorg package in Ubuntu:
  Expired

Bug description:
  Up to last night, I was using my system just fine, with my 1280x1024
  monitor.  Today, the system boots up with all the text and icons much
  larger, and Settings -> Displays now informs me that my monitor is
  only 1024x768 and won't permit me to change it back to the correct
  setting.  I haven't changed anything, hardware or software.  How do I
  make it work correctly again?

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-46.49-generic 4.8.17
  Uname: Linux 4.8.0-46-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Apr 13 19:07:58 2017
  DistUpgraded: Fresh install
  DistroCodename: yakkety
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation G98 [GeForce 8400 GS Rev. 2] [10de:06e4] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. G98 [GeForce 8400 GS Rev. 2] [1043:8321]
  InstallationDate: Installed on 2017-03-26 (18 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: MSI MS-7865
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-46-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/21/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V10.0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: AM1I (MS-7865)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV10.0:bd02/21/2014:svnMSI:pnMS-7865:pvr2.0:rvnMSI:rnAM1I(MS-7865):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.name: MS-7865
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI
  version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.10.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.10.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2
  xserver.bootTime: Thu Apr 13 19:04:54 2017
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputHID 04f3:0103KEYBOARD, id 8
   inputHID 04f3:0103KEYBOARD, id 9
   inputUSB Optical MouseMOUSE, id 10
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs: Output DVI-I-1   
VGA-1
  xserver.version: 2:1.18.4-1ubuntu6
  xserver.video_driver: nouveau

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1682695/+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 1768408] [NEW] Desktop content

[Davi Mizael]

Public bug reported:

By dragging a desktop content into a folder on the system, the desktop
gets stuck and only comes back with the system reboot

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed May  2 01:10:35 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DpkgLog:
 
ExtraDebuggingInterest: I just need to know a workaround
GraphicsCard:
 Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
   Subsystem: Hewlett-Packard Company HD Graphics 5500 [103c:225a]
InstallationDate: Installed on 2018-04-27 (4 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: Hewlett-Packard HP EliteBook 820 G2
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=1d729abd-93bc-472e-89ed-243524756bc7 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/13/2017
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: M71 Ver. 01.21
dmi.board.name: 225A
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 96.5B
dmi.chassis.asset.tag: 5CG6257W70
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrM71Ver.01.21:bd07/13/2017:svnHewlett-Packard:pnHPEliteBook820G2:pvrA3009D510303:rvnHewlett-Packard:rn225A:rvrKBCVersion96.5B:cvnHewlett-Packard:ct10:cvr:
dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
dmi.product.name: HP EliteBook 820 G2
dmi.product.version: A3009D510303
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic 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/1768408

Title:
  Desktop content

Status in xorg package in Ubuntu:
  New

Bug description:
  By dragging a desktop content into a folder on the system, the desktop
  gets stuck and only comes back with the system reboot

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May  2 01:10:35 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DpkgLog:
   
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company HD Graphics 5500 [103c:225a]
  InstallationDate: Installed on 2018-04-27 (4 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Hewlett-Packard HP EliteBook 820 G2
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=1d729abd-93bc-472e-89ed-243524756bc7 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/13/2017
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: M71 Ver. 01.21
  dmi.board.name: 225A
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 96.5B
  dmi.chassis.asset.tag: 5CG6257W70
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrM71Ver.01.21:bd07/13/2017:svnHewlett-Packard:pnHPEliteBook820G2:pvrA3009D510303:rvnHewlett-Packard:rn225A:rvrKBCVersion96.5B:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
  dmi.product.name: HP EliteBook 820 G2
  dmi.product.version: A3009D510303
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  

[Touch-packages] [Bug 1751252] Re: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: ''

[Daniel van Vugt]

Thanks @pjsingh5000. Your attachment shows the python stack ends at:

# There's still work to do (postinstall).  Let's keep the user
# entertained.
self.start_slideshow()
Gtk.main()

Which agrees with what I see on screen when the bug occurs. It's the
slideshow that never starts (or does, as a blank black/white image).

After that there is no debug info from comment #22. Although my
attachment from comment #15 probably fills in the blanks:
https://launchpadlibrarian.net/368099559/dbg.txt

So it looks like the bug here is entirely in the C code.

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

Title:
  [regression] ubiquity crashed in debconf.py:104 with ValueError:
  invalid literal for int() with base 10: ''

Status in OEM Priority Project:
  Triaged
Status in glib2.0 package in Ubuntu:
  Incomplete
Status in ubiquity package in Ubuntu:
  Triaged
Status in glib2.0 source package in Bionic:
  Incomplete
Status in ubiquity source package in Bionic:
  Triaged

Bug description:
  The Ubuntu installer crashes on hiDPI machines (QHD/UHD etc). Although
  it was working some weeks/months ago, so this is a recent regression.

  ---

  https://errors.ubuntu.com/problem/82f7f7e7923663c7b2123c7f1f49af29f6ff4d77
  https://errors.ubuntu.com/problem/735a2b847e0eeab6c8a7b954de5110e43889be15
  https://errors.ubuntu.com/problem/dcd4c9da5ee0cc6d36324446e0e49d39705c90b7
  https://errors.ubuntu.com/problem/cb82f70f9ede07369e8104da9ddf87e28b42257d
  https://errors.ubuntu.com/problem/84a5563af3d2b85f098da832ece4cb8450bfd524

  ---

  WORKAROUND:

  1. Boot into the live session.
  2. Settings > Devices > Displays > Scale = 100%
  3. Click Apply.
  4. Proceed with installation: Click "Install Ubuntu 18.04 LTS".

  ---

  Crashed in a VM in the middle of installation. The host is Bionic up
  to date.

  From the journal
  Feb 23 12:52:27 ubuntu kernel: traps: ubiquity[2646] trap int3 
ip:7f5a76936961 sp:7ffde5090c50 error:0 in 
libglib-2.0.so.0.5400.1[7f5a768e6000+111000]
  Feb 23 12:52:41 ubuntu /install.py[6858]: Exception during installation:
  Feb 23 12:52:41 ubuntu /install.py[6858]: Traceback (most recent call last):
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 757, in 
  Feb 23 12:52:41 ubuntu /install.py[6858]: install.run()
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 135, in run
  Feb 23 12:52:41 ubuntu /install.py[6858]: self.copy_all()
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 505, in copy_all
  Feb 23 12:52:41 ubuntu /install.py[6858]: self.db.progress('SET', 10 + 
copy_progress)
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/lib/python3/dist-packages/debconf.py", line 83, in 
  Feb 23 12:52:41 ubuntu /install.py[6858]: lambda *args, **kw: 
self.command(command, *args, **kw))
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/lib/python3/dist-packages/debconf.py", line 104, in command
  Feb 23 12:52:41 ubuntu /install.py[6858]: status = int(status)
  Feb 23 12:52:41 ubuntu /install.py[6858]: ValueError: invalid literal for 
int() with base 10: ''

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: ubiquity 18.04.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CasperVersion: 1.388
  Date: Fri Feb 23 12:52:28 2018
  ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- keyboard-configuration/layoutcode=fr 
keyboard-configuration/variantcode=oss
  InterpreterPath: /usr/bin/python3.6
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222)
  ProcCmdline: /usr/bin/python3 /usr/lib/ubiquity/bin/ubiquity -d
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  Signal: 5
  SourcePackage: ubiquity
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: ubiquity crashed with signal 5 in _XEventsQueued()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1751252/+subscriptions

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

[Touch-packages] [Bug 1751252] Re: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: ''

[Daniel van Vugt]

This one also started in version 18.04.11:
https://errors.ubuntu.com/problem/735a2b847e0eeab6c8a7b954de5110e43889be15

But this one started in 18.04.3:
https://errors.ubuntu.com/problem/82f7f7e7923663c7b2123c7f1f49af29f6ff4d77

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

Title:
  [regression] ubiquity crashed in debconf.py:104 with ValueError:
  invalid literal for int() with base 10: ''

Status in OEM Priority Project:
  Triaged
Status in glib2.0 package in Ubuntu:
  Incomplete
Status in ubiquity package in Ubuntu:
  Triaged
Status in glib2.0 source package in Bionic:
  Incomplete
Status in ubiquity source package in Bionic:
  Triaged

Bug description:
  The Ubuntu installer crashes on hiDPI machines (QHD/UHD etc). Although
  it was working some weeks/months ago, so this is a recent regression.

  ---

  https://errors.ubuntu.com/problem/82f7f7e7923663c7b2123c7f1f49af29f6ff4d77
  https://errors.ubuntu.com/problem/735a2b847e0eeab6c8a7b954de5110e43889be15
  https://errors.ubuntu.com/problem/dcd4c9da5ee0cc6d36324446e0e49d39705c90b7
  https://errors.ubuntu.com/problem/cb82f70f9ede07369e8104da9ddf87e28b42257d
  https://errors.ubuntu.com/problem/84a5563af3d2b85f098da832ece4cb8450bfd524

  ---

  WORKAROUND:

  1. Boot into the live session.
  2. Settings > Devices > Displays > Scale = 100%
  3. Click Apply.
  4. Proceed with installation: Click "Install Ubuntu 18.04 LTS".

  ---

  Crashed in a VM in the middle of installation. The host is Bionic up
  to date.

  From the journal
  Feb 23 12:52:27 ubuntu kernel: traps: ubiquity[2646] trap int3 
ip:7f5a76936961 sp:7ffde5090c50 error:0 in 
libglib-2.0.so.0.5400.1[7f5a768e6000+111000]
  Feb 23 12:52:41 ubuntu /install.py[6858]: Exception during installation:
  Feb 23 12:52:41 ubuntu /install.py[6858]: Traceback (most recent call last):
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 757, in 
  Feb 23 12:52:41 ubuntu /install.py[6858]: install.run()
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 135, in run
  Feb 23 12:52:41 ubuntu /install.py[6858]: self.copy_all()
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 505, in copy_all
  Feb 23 12:52:41 ubuntu /install.py[6858]: self.db.progress('SET', 10 + 
copy_progress)
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/lib/python3/dist-packages/debconf.py", line 83, in 
  Feb 23 12:52:41 ubuntu /install.py[6858]: lambda *args, **kw: 
self.command(command, *args, **kw))
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/lib/python3/dist-packages/debconf.py", line 104, in command
  Feb 23 12:52:41 ubuntu /install.py[6858]: status = int(status)
  Feb 23 12:52:41 ubuntu /install.py[6858]: ValueError: invalid literal for 
int() with base 10: ''

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: ubiquity 18.04.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CasperVersion: 1.388
  Date: Fri Feb 23 12:52:28 2018
  ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- keyboard-configuration/layoutcode=fr 
keyboard-configuration/variantcode=oss
  InterpreterPath: /usr/bin/python3.6
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222)
  ProcCmdline: /usr/bin/python3 /usr/lib/ubiquity/bin/ubiquity -d
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  Signal: 5
  SourcePackage: ubiquity
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: ubiquity crashed with signal 5 in _XEventsQueued()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1751252/+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 1751252] Re: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: ''

[Daniel van Vugt]

According to this page, the problem possibly started in ubiquity version 
18.04.11:
https://errors.ubuntu.com/problem/84a5563af3d2b85f098da832ece4cb8450bfd524

** Description changed:

  The Ubuntu installer crashes on hiDPI machines (QHD/UHD etc). Although
  it was working some weeks/months ago, so this is a recent regression.
  
  ---
  
  https://errors.ubuntu.com/problem/82f7f7e7923663c7b2123c7f1f49af29f6ff4d77
  https://errors.ubuntu.com/problem/735a2b847e0eeab6c8a7b954de5110e43889be15
+ https://errors.ubuntu.com/problem/dcd4c9da5ee0cc6d36324446e0e49d39705c90b7
  
  ---
  
  WORKAROUND:
  
  1. Boot into the live session.
  2. Settings > Devices > Displays > Scale = 100%
  3. Click Apply.
  4. Proceed with installation: Click "Install Ubuntu 18.04 LTS".
  
  ---
  
  Crashed in a VM in the middle of installation. The host is Bionic up to
  date.
  
  From the journal
  Feb 23 12:52:27 ubuntu kernel: traps: ubiquity[2646] trap int3 
ip:7f5a76936961 sp:7ffde5090c50 error:0 in 
libglib-2.0.so.0.5400.1[7f5a768e6000+111000]
  Feb 23 12:52:41 ubuntu /install.py[6858]: Exception during installation:
  Feb 23 12:52:41 ubuntu /install.py[6858]: Traceback (most recent call last):
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 757, in 
  Feb 23 12:52:41 ubuntu /install.py[6858]: install.run()
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 135, in run
  Feb 23 12:52:41 ubuntu /install.py[6858]: self.copy_all()
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 505, in copy_all
  Feb 23 12:52:41 ubuntu /install.py[6858]: self.db.progress('SET', 10 + 
copy_progress)
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/lib/python3/dist-packages/debconf.py", line 83, in 
  Feb 23 12:52:41 ubuntu /install.py[6858]: lambda *args, **kw: 
self.command(command, *args, **kw))
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/lib/python3/dist-packages/debconf.py", line 104, in command
  Feb 23 12:52:41 ubuntu /install.py[6858]: status = int(status)
  Feb 23 12:52:41 ubuntu /install.py[6858]: ValueError: invalid literal for 
int() with base 10: ''
  
  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: ubiquity 18.04.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CasperVersion: 1.388
  Date: Fri Feb 23 12:52:28 2018
  ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- keyboard-configuration/layoutcode=fr 
keyboard-configuration/variantcode=oss
  InterpreterPath: /usr/bin/python3.6
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222)
  ProcCmdline: /usr/bin/python3 /usr/lib/ubiquity/bin/ubiquity -d
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  Signal: 5
  SourcePackage: ubiquity
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: ubiquity crashed with signal 5 in _XEventsQueued()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

** Description changed:

  The Ubuntu installer crashes on hiDPI machines (QHD/UHD etc). Although
  it was working some weeks/months ago, so this is a recent regression.
  
  ---
  
  https://errors.ubuntu.com/problem/82f7f7e7923663c7b2123c7f1f49af29f6ff4d77
  https://errors.ubuntu.com/problem/735a2b847e0eeab6c8a7b954de5110e43889be15
  https://errors.ubuntu.com/problem/dcd4c9da5ee0cc6d36324446e0e49d39705c90b7
+ https://errors.ubuntu.com/problem/cb82f70f9ede07369e8104da9ddf87e28b42257d
  
  ---
  
  WORKAROUND:
  
  1. Boot into the live session.
  2. Settings > Devices > Displays > Scale = 100%
  3. Click Apply.
  4. Proceed with installation: Click "Install Ubuntu 18.04 LTS".
  
  ---
  
  Crashed in a VM in the middle of installation. The host is Bionic up to
  date.
  
  From the journal
  Feb 23 12:52:27 ubuntu kernel: traps: ubiquity[2646] trap int3 
ip:7f5a76936961 sp:7ffde5090c50 error:0 in 
libglib-2.0.so.0.5400.1[7f5a768e6000+111000]
  Feb 23 12:52:41 ubuntu /install.py[6858]: Exception during installation:
  Feb 23 12:52:41 ubuntu /install.py[6858]: Traceback (most recent call last):
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 757, in 
  Feb 23 12:52:41 ubuntu /install.py[6858]: install.run()
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 

[Touch-packages] [Bug 1751252] Re: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: ''

[Yuan-Chen Cheng]

** Also affects: oem-priority
   Importance: Undecided
   Status: New

** Changed in: oem-priority
   Status: New => Triaged

** Changed in: oem-priority
   Importance: Undecided => Critical

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

Title:
  [regression] ubiquity crashed in debconf.py:104 with ValueError:
  invalid literal for int() with base 10: ''

Status in OEM Priority Project:
  Triaged
Status in glib2.0 package in Ubuntu:
  Incomplete
Status in ubiquity package in Ubuntu:
  Triaged
Status in glib2.0 source package in Bionic:
  Incomplete
Status in ubiquity source package in Bionic:
  Triaged

Bug description:
  The Ubuntu installer crashes on hiDPI machines (QHD/UHD etc). Although
  it was working some weeks/months ago, so this is a recent regression.

  ---

  https://errors.ubuntu.com/problem/82f7f7e7923663c7b2123c7f1f49af29f6ff4d77
  https://errors.ubuntu.com/problem/735a2b847e0eeab6c8a7b954de5110e43889be15

  ---

  WORKAROUND:

  1. Boot into the live session.
  2. Settings > Devices > Displays > Scale = 100%
  3. Click Apply.
  4. Proceed with installation: Click "Install Ubuntu 18.04 LTS".

  ---

  Crashed in a VM in the middle of installation. The host is Bionic up
  to date.

  From the journal
  Feb 23 12:52:27 ubuntu kernel: traps: ubiquity[2646] trap int3 
ip:7f5a76936961 sp:7ffde5090c50 error:0 in 
libglib-2.0.so.0.5400.1[7f5a768e6000+111000]
  Feb 23 12:52:41 ubuntu /install.py[6858]: Exception during installation:
  Feb 23 12:52:41 ubuntu /install.py[6858]: Traceback (most recent call last):
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 757, in 
  Feb 23 12:52:41 ubuntu /install.py[6858]: install.run()
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 135, in run
  Feb 23 12:52:41 ubuntu /install.py[6858]: self.copy_all()
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 505, in copy_all
  Feb 23 12:52:41 ubuntu /install.py[6858]: self.db.progress('SET', 10 + 
copy_progress)
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/lib/python3/dist-packages/debconf.py", line 83, in 
  Feb 23 12:52:41 ubuntu /install.py[6858]: lambda *args, **kw: 
self.command(command, *args, **kw))
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/lib/python3/dist-packages/debconf.py", line 104, in command
  Feb 23 12:52:41 ubuntu /install.py[6858]: status = int(status)
  Feb 23 12:52:41 ubuntu /install.py[6858]: ValueError: invalid literal for 
int() with base 10: ''

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: ubiquity 18.04.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CasperVersion: 1.388
  Date: Fri Feb 23 12:52:28 2018
  ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- keyboard-configuration/layoutcode=fr 
keyboard-configuration/variantcode=oss
  InterpreterPath: /usr/bin/python3.6
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222)
  ProcCmdline: /usr/bin/python3 /usr/lib/ubiquity/bin/ubiquity -d
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  Signal: 5
  SourcePackage: ubiquity
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: ubiquity crashed with signal 5 in _XEventsQueued()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1751252/+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 1768364] Re: Combo boxes close immediately after opening

[Slavic Dragovtev]

Here's an example of it happening randomly in gnome-control-center.

** Attachment added: "combo box in gnome-control-center"
   
https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1768364/+attachment/5131731/+files/Screencast%20from%2005-01-2018%2007%3A07%3A24%20PM.webm

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

Title:
  Combo boxes close immediately after opening

Status in gtk+3.0 package in Ubuntu:
  New
Status in rhythmbox package in Ubuntu:
  New

Bug description:
  Sometimes when a select box is clicked, it opens and then closes
  almost immediately.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May  1 14:39:28 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-04-27 (4 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1768364/+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 1759300] Re: Gnome Shell: Touchpad right click (bottom right) area does not work

[Daniel van Vugt]

I think we should improve this in 18.10 by moving the setting from
gnome-tweaks into gnome-control-center. That way most users will
actually find it, and be able to resolve the issue themselves.

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

Title:
  Gnome Shell: Touchpad right click (bottom right) area does not work

Status in gsettings-desktop-schemas package in Ubuntu:
  Invalid

Bug description:
  The right (second) touchpad click does not work.
  It ceased to work about three months ago.
  ubuntu 18,04 aser ex2519

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gsettings-desktop-schemas/+bug/1759300/+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 1710637] Re: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland

[Daniel van Vugt]

Bug 1767918 indicates this bug is not fixed, and still occurring in
18.04.


** Tags added: fall-through

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

Title:
  Input falls through to gdm3 and terminates the session on Ctrl+C after
  udevadm trigger is executed under wayland

Status in Snappy:
  Won't Fix
Status in console-setup package in Ubuntu:
  Fix Released
Status in gdm3 package in Ubuntu:
  Invalid
Status in gnome-shell package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid
Status in console-setup source package in Trusty:
  New
Status in gdm3 source package in Trusty:
  New
Status in gnome-shell source package in Trusty:
  New
Status in mutter source package in Trusty:
  New
Status in systemd source package in Trusty:
  New
Status in console-setup source package in Xenial:
  New
Status in gdm3 source package in Xenial:
  New
Status in gnome-shell source package in Xenial:
  New
Status in mutter source package in Xenial:
  New
Status in systemd source package in Xenial:
  New

Bug description:
  = Test Cases =

  Test Case 1:
  - Login under Wayland (session Ubuntu)
  - Open a terminal
  - snap install gimp
  - Wait until installation finishes successfully
  - In the terminal window press CTRL+C

  Result:
  - Expected: ^C is displayed in the terminal and the prompt is at the start of 
a new line
  - Actual: The session is terminated and the login screen is displayed

  Test Case 2:
  - Login under Wayland (session Ubuntu)
  - Open a terminal and type the following command:
    $ sudo udevadm trigger
  - In the terminal window press CTRL+C

  Result
  - Expected: ^C is displayed in the terminal and the prompt is at the start of 
a new line
  - Actual: The session is terminated and the login screen is displayed

  = Original Description =

  Multiple times a day I find myself without a session after hitting
  Ctrl+C in a terminal, it seems the input falls through the
  Ubuntu/GNOME session and to gdm, which itself decides to terminate.

  Even worse, when this happens, you can briefly see your login password
  in plaintext in the virtual terminal. You can see the password however
  long you want if you stop the gdm service when this happens.

  I don't have a good way to reproduce, but it seems locking the session
  with a keyboard shortcut, subsequently unlocking it, maybe suspending,
  at some point brings this behaviour into the picture, until the
  session dies with a Ctrl+C.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gdm3 3.24.2-1ubuntu9
  ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12
  Uname: Linux 4.11.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.6-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Aug 14 15:54:34 2017
  InstallationDate: Installed on 2016-05-06 (464 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to artful on 2017-07-19 (25 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/snappy/+bug/1710637/+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 1768343] Re: Not detect secondary button of notebook touchpad

[Daniel van Vugt]

*** This bug is a duplicate of bug 1759300 ***
https://bugs.launchpad.net/bugs/1759300

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1759300, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** Package changed: libinput (Ubuntu) => gsettings-desktop-schemas
(Ubuntu)

** This bug has been marked a duplicate of bug 1759300
   Gnome Shell: Touchpad right click (bottom right) area does not work

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

Title:
  Not detect secondary button of notebook touchpad

Status in gsettings-desktop-schemas package in Ubuntu:
  New

Bug description:
  When I press the secondary touchpad button, Ubuntu takes it as the primary 
one. This error does not happen with a usb mouse.
  Acer Aspire 3 7100U

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-settings-daemon 3.28.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May  1 17:02:59 2018
  ExecutablePath: /usr/lib/gnome-settings-daemon/gsd-mouse
  InstallationDate: Installed on 2018-05-01 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=es_AR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gsettings-desktop-schemas/+bug/1768343/+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 1768364] Re: Combo boxes close immediately after opening

[Slavic Dragovtev]

@Daniel, this is not just Rhythmbox. It's across many interfaces. It
just happened to be on Rhythmbox now when it occurred multiple times.

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

Title:
  Combo boxes close immediately after opening

Status in gtk+3.0 package in Ubuntu:
  New
Status in rhythmbox package in Ubuntu:
  New

Bug description:
  Sometimes when a select box is clicked, it opens and then closes
  almost immediately.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May  1 14:39:28 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-04-27 (4 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1768364/+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 1710637] Re: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland

[Daniel van Vugt]

** Information type changed from Public to Public Security

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

Title:
  Input falls through to gdm3 and terminates the session on Ctrl+C after
  udevadm trigger is executed under wayland

Status in Snappy:
  Won't Fix
Status in console-setup package in Ubuntu:
  Fix Released
Status in gdm3 package in Ubuntu:
  Invalid
Status in gnome-shell package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid
Status in console-setup source package in Trusty:
  New
Status in gdm3 source package in Trusty:
  New
Status in gnome-shell source package in Trusty:
  New
Status in mutter source package in Trusty:
  New
Status in systemd source package in Trusty:
  New
Status in console-setup source package in Xenial:
  New
Status in gdm3 source package in Xenial:
  New
Status in gnome-shell source package in Xenial:
  New
Status in mutter source package in Xenial:
  New
Status in systemd source package in Xenial:
  New

Bug description:
  = Test Cases =

  Test Case 1:
  - Login under Wayland (session Ubuntu)
  - Open a terminal
  - snap install gimp
  - Wait until installation finishes successfully
  - In the terminal window press CTRL+C

  Result:
  - Expected: ^C is displayed in the terminal and the prompt is at the start of 
a new line
  - Actual: The session is terminated and the login screen is displayed

  Test Case 2:
  - Login under Wayland (session Ubuntu)
  - Open a terminal and type the following command:
    $ sudo udevadm trigger
  - In the terminal window press CTRL+C

  Result
  - Expected: ^C is displayed in the terminal and the prompt is at the start of 
a new line
  - Actual: The session is terminated and the login screen is displayed

  = Original Description =

  Multiple times a day I find myself without a session after hitting
  Ctrl+C in a terminal, it seems the input falls through the
  Ubuntu/GNOME session and to gdm, which itself decides to terminate.

  Even worse, when this happens, you can briefly see your login password
  in plaintext in the virtual terminal. You can see the password however
  long you want if you stop the gdm service when this happens.

  I don't have a good way to reproduce, but it seems locking the session
  with a keyboard shortcut, subsequently unlocking it, maybe suspending,
  at some point brings this behaviour into the picture, until the
  session dies with a Ctrl+C.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gdm3 3.24.2-1ubuntu9
  ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12
  Uname: Linux 4.11.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.6-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Aug 14 15:54:34 2017
  InstallationDate: Installed on 2016-05-06 (464 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to artful on 2017-07-19 (25 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/snappy/+bug/1710637/+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 1768364] Re: Combo boxes close immediately after opening

[Daniel van Vugt]

** Summary changed:

- Select boxes close immediately after opening
+ Combo boxes close immediately after opening

** Package changed: gnome-shell (Ubuntu) => rhythmbox (Ubuntu)

** Also affects: gtk+3.0 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Combo boxes close immediately after opening

Status in gtk+3.0 package in Ubuntu:
  New
Status in rhythmbox package in Ubuntu:
  New

Bug description:
  Sometimes when a select box is clicked, it opens and then closes
  almost immediately.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May  1 14:39:28 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-04-27 (4 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1768364/+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 1768343] [NEW] Not detect secondary button of notebook touchpad

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

When I press the secondary touchpad button, Ubuntu takes it as the primary one. 
This error does not happen with a usb mouse.
Acer Aspire 3 7100U

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-settings-daemon 3.28.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue May  1 17:02:59 2018
ExecutablePath: /usr/lib/gnome-settings-daemon/gsd-mouse
InstallationDate: Installed on 2018-05-01 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcEnviron:
 PATH=(custom, user)
 XDG_RUNTIME_DIR=
 LANG=es_AR.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-settings-daemon
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gsettings-desktop-schemas (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic
-- 
Not detect secondary button of notebook touchpad
https://bugs.launchpad.net/bugs/1768343
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to gsettings-desktop-schemas in Ubuntu.

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

[Touch-packages] [Bug 1741045] Re: Change the default resample-method to speex-float-10 in daemon.conf

[Daniel van Vugt]

That seems to show speex-float-1 performing quite well:
https://imgur.com/a/jtIEj


** Summary changed:

- Change the default resample-method to speex-float-10 in daemon.conf
+ Change the default resample-method to speex-float-N (N > 1) in daemon.conf

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

Title:
  Change the default resample-method to speex-float-N (N > 1) in
  daemon.conf

Status in PulseAudio:
  Confirmed
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I suggest changing the default resample-method to speex-float-10,
  instead of speex-float-1, which is the current default now, in
  /etc/pulse/daemon.conf.

  It would look like this in daemon.conf:
  resample-method = speex-float-10

  I have always done that since at least 12.04 LTS. I was not satisfied
  with the sound quality in Ubuntu compared to Windows, so I changed the
  resample-method.

  In my day-to-day usage, it gives better sound quality without
  sacrificing CPU power.

  I have not tried other resample methods. Maybe there are better
  options I don't know about.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  amr1696 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan  3 14:37:25 2018
  InstallationDate: Installed on 2017-10-02 (92 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170930)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/08/2011
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F2
  dmi.board.name: GA-78LMT-S2P
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd04/08/2011:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-S2P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-S2P:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-78LMT-S2P
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  modified.conffile..etc.pulse.daemon.conf: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2017-10-05T12:39:48.718018

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1741045/+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 890867] Re: pulseaudio crashed with SIGABRT in pa_memimport_free()

[Daniel van Vugt]

Taras: Please report your crash in a new bug.

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

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

Title:
  pulseaudio crashed with SIGABRT in pa_memimport_free()

Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  Sound crashed after changing the volume, but seems random, hasn't done
  it again. Might be related to instalation of pulseaudio-equalizer,
  even if I do notice the sound widget/icon (gnome-shell) restarting at
  times.

  ProblemType: Crash
  DistroRelease: Ubuntu 11.10
  Package: pulseaudio 1:1.0-0ubuntu3.1
  ProcVersionSignature: Ubuntu 3.0.0-13.22-generic 3.0.6
  Uname: Linux 3.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dramalho   5025 F pulseaudio
   /dev/snd/controlC0:  dramalho   5025 F pulseaudio
   /dev/snd/pcmC0D0p:   dramalho   5025 F...m pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xd742 irq 47'
 Mixer name : 'IDT 92HD75B3X5'
 Components : 'HDA:111d7603,103c172b,00100202 
HDA:11c11040,103c3066,00100200'
 Controls  : 15
 Simple ctrls  : 10
  Card1.Amixer.info:
   Card hw:1 'NVidia'/'HDA NVidia at 0xd300 irq 16'
 Mixer name : 'Nvidia GPU 0b HDMI/DP'
 Components : 'HDA:10de000b,10de0101,00100100'
 Controls  : 16
 Simple ctrls  : 4
  Date: Tue Nov 15 18:23:52 2011
  ExecutablePath: /usr/bin/pulseaudio
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
  Signal: 6
  SourcePackage: pulseaudio
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libpulsecommon-1.0.so
   pa_memimport_free () from /usr/lib/x86_64-linux-gnu/libpulsecommon-1.0.so
   pa_pstream_unlink () from /usr/lib/x86_64-linux-gnu/libpulsecommon-1.0.so
   ?? () from /usr/lib/pulse-1.0/modules/libprotocol-native.so
   ?? () from /usr/lib/pulse-1.0/modules/libprotocol-native.so
  Title: pulseaudio crashed with SIGABRT in pa_memimport_free()
  UpgradeStatus: Upgraded to oneiric on 2011-09-01 (74 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare sudo
  XsessionErrors:
   (gnome-shell:2192): Clutter-WARNING **: Attempting to add actor of type 
'ShellGenericContainer' to a container of type 'StBoxLayout', but the actor has 
already a parent of type 'StBoxLayout'.
   (dropbox:2299): Gdk-CRITICAL **: 
IA__gdk_window_thaw_toplevel_updates_libgtk_only: assertion 
`private->update_and_descendants_freeze_count > 0' failed
   (process:4796): Gtk-WARNING **: Locale not supported by C library.
  dmi.bios.date: 03/09/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68CCU Ver. F.12
  dmi.board.name: 172B
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 30.31
  dmi.chassis.asset.tag: CZC0126G5J
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68CCUVer.F.12:bd03/09/2011:svnHewlett-Packard:pnHPEliteBook8440p:pvr:rvnHewlett-Packard:rn172B:rvrKBCVersion30.31:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 8440p
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/890867/+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 1752053] Re: nvidia-390 fails to boot graphical display

[Bernadette Addison]

I agree! This issue is definitely NOT FIXED!

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

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Invalid

Bug description:
  I'm using Bionic with the new 4.15 kernel. I've been using the
  nvidia-384 driver with no problem for a while.  Today I issued "sudo
  apt-get upgrade" and I was prompted to upgrade the nvidia driver to
  the nvidia-390.  After installing the driver and rebooting, I was only
  able to boot in to the tty terminal.  The graphical display failed to
  boot.  I have had similar problems with nvidia driver version 390 with
  Arch Linux and with Open Suse Tumbleweed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+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 1752053] Re: nvidia-390 fails to boot graphical display

[Bernadette Addison]

I agree! This issue is definitely NOT FIXED!

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

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Invalid

Bug description:
  I'm using Bionic with the new 4.15 kernel. I've been using the
  nvidia-384 driver with no problem for a while.  Today I issued "sudo
  apt-get upgrade" and I was prompted to upgrade the nvidia driver to
  the nvidia-390.  After installing the driver and rebooting, I was only
  able to boot in to the tty terminal.  The graphical display failed to
  boot.  I have had similar problems with nvidia driver version 390 with
  Arch Linux and with Open Suse Tumbleweed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+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 1751252] Re: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: ''

[PJSingh5000]

Here is the backtrace (bt f) with debug symbols.

I still have gdb open, if anyone needs me to do anything else?

** Attachment added: "gdb backtrace (bt f) with debug symbols"
   
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1751252/+attachment/5131712/+files/gdb_output_with_debug_symbols.txt

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

Title:
  [regression] ubiquity crashed in debconf.py:104 with ValueError:
  invalid literal for int() with base 10: ''

Status in glib2.0 package in Ubuntu:
  Incomplete
Status in ubiquity package in Ubuntu:
  Triaged
Status in glib2.0 source package in Bionic:
  Incomplete
Status in ubiquity source package in Bionic:
  Triaged

Bug description:
  The Ubuntu installer crashes on hiDPI machines (QHD/UHD etc). Although
  it was working some weeks/months ago, so this is a recent regression.

  ---

  https://errors.ubuntu.com/problem/82f7f7e7923663c7b2123c7f1f49af29f6ff4d77
  https://errors.ubuntu.com/problem/735a2b847e0eeab6c8a7b954de5110e43889be15

  ---

  WORKAROUND:

  1. Boot into the live session.
  2. Settings > Devices > Displays > Scale = 100%
  3. Click Apply.
  4. Proceed with installation: Click "Install Ubuntu 18.04 LTS".

  ---

  Crashed in a VM in the middle of installation. The host is Bionic up
  to date.

  From the journal
  Feb 23 12:52:27 ubuntu kernel: traps: ubiquity[2646] trap int3 
ip:7f5a76936961 sp:7ffde5090c50 error:0 in 
libglib-2.0.so.0.5400.1[7f5a768e6000+111000]
  Feb 23 12:52:41 ubuntu /install.py[6858]: Exception during installation:
  Feb 23 12:52:41 ubuntu /install.py[6858]: Traceback (most recent call last):
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 757, in 
  Feb 23 12:52:41 ubuntu /install.py[6858]: install.run()
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 135, in run
  Feb 23 12:52:41 ubuntu /install.py[6858]: self.copy_all()
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 505, in copy_all
  Feb 23 12:52:41 ubuntu /install.py[6858]: self.db.progress('SET', 10 + 
copy_progress)
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/lib/python3/dist-packages/debconf.py", line 83, in 
  Feb 23 12:52:41 ubuntu /install.py[6858]: lambda *args, **kw: 
self.command(command, *args, **kw))
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/lib/python3/dist-packages/debconf.py", line 104, in command
  Feb 23 12:52:41 ubuntu /install.py[6858]: status = int(status)
  Feb 23 12:52:41 ubuntu /install.py[6858]: ValueError: invalid literal for 
int() with base 10: ''

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: ubiquity 18.04.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CasperVersion: 1.388
  Date: Fri Feb 23 12:52:28 2018
  ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- keyboard-configuration/layoutcode=fr 
keyboard-configuration/variantcode=oss
  InterpreterPath: /usr/bin/python3.6
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222)
  ProcCmdline: /usr/bin/python3 /usr/lib/ubiquity/bin/ubiquity -d
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  Signal: 5
  SourcePackage: ubiquity
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: ubiquity crashed with signal 5 in _XEventsQueued()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1751252/+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 1768373] Re: package udev 229-4ubuntu21.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[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 systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1768373

Title:
  package udev 229-4ubuntu21.2 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in systemd package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu 16.04.4 LTS
  Release:  16.04

  After a failed update, this system error comes back every time there
  is an update

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: udev 229-4ubuntu21.2
  ProcVersionSignature: Ubuntu 4.4.0-122.146-generic 4.4.117
  Uname: Linux 4.4.0-122-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  Date: Wed May  2 09:11:12 2018
  DpkgHistoryLog:
   Start-Date: 2018-05-02  09:11:06
   Commandline: /usr/bin/unattended-upgrade
   Install: libwebpdemux1:amd64 (0.4.4-1, automatic)
   Upgrade: libgs9:amd64 (9.18~dfsg~0-0ubuntu2.7, 9.18~dfsg~0-0ubuntu2.8), 
ghostscript:amd64 (9.18~dfsg~0-0ubuntu2.7, 9.18~dfsg~0-0ubuntu2.8), 
libwebkit2gtk-4.0-37:amd64 (2.18.6-0ubuntu0.16.04.1, 2.20.1-0ubuntu0.16.04.1), 
ghostscript-x:amd64 (9.18~dfsg~0-0ubuntu2.7, 9.18~dfsg~0-0ubuntu2.8), 
libgs9-common:amd64 (9.18~dfsg~0-0ubuntu2.7, 9.18~dfsg~0-0ubuntu2.8), 
gir1.2-webkit2-4.0:amd64 (2.18.6-0ubuntu0.16.04.1, 2.20.1-0ubuntu0.16.04.1), 
libjavascriptcoregtk-4.0-18:amd64 (2.18.6-0ubuntu0.16.04.1, 
2.20.1-0ubuntu0.16.04.1), libwebkit2gtk-4.0-37-gtk2:amd64 
(2.18.6-0ubuntu0.16.04.1, 2.20.1-0ubuntu0.16.04.1), 
gir1.2-javascriptcoregtk-4.0:amd64 (2.18.6-0ubuntu0.16.04.1, 
2.20.1-0ubuntu0.16.04.1)
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-05-06 (725 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 2306CTO
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-122-generic.efi.signed 
root=UUID=28b0a55a-85a6-4f5e-8a78-262e5fdf1237 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: systemd
  Title: package udev 229-4ubuntu21.2 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/22/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ETA1WW (2.61 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2306CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Win8 STD DPK TPG
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ETA1WW(2.61):bd04/22/2014:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrWin8STDDPKTPG:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2306CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1768373/+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 1768373] [NEW] package udev 229-4ubuntu21.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Jianfeng Li]

Public bug reported:

Description:Ubuntu 16.04.4 LTS
Release:16.04

After a failed update, this system error comes back every time there is
an update

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: udev 229-4ubuntu21.2
ProcVersionSignature: Ubuntu 4.4.0-122.146-generic 4.4.117
Uname: Linux 4.4.0-122-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.16
Architecture: amd64
Date: Wed May  2 09:11:12 2018
DpkgHistoryLog:
 Start-Date: 2018-05-02  09:11:06
 Commandline: /usr/bin/unattended-upgrade
 Install: libwebpdemux1:amd64 (0.4.4-1, automatic)
 Upgrade: libgs9:amd64 (9.18~dfsg~0-0ubuntu2.7, 9.18~dfsg~0-0ubuntu2.8), 
ghostscript:amd64 (9.18~dfsg~0-0ubuntu2.7, 9.18~dfsg~0-0ubuntu2.8), 
libwebkit2gtk-4.0-37:amd64 (2.18.6-0ubuntu0.16.04.1, 2.20.1-0ubuntu0.16.04.1), 
ghostscript-x:amd64 (9.18~dfsg~0-0ubuntu2.7, 9.18~dfsg~0-0ubuntu2.8), 
libgs9-common:amd64 (9.18~dfsg~0-0ubuntu2.7, 9.18~dfsg~0-0ubuntu2.8), 
gir1.2-webkit2-4.0:amd64 (2.18.6-0ubuntu0.16.04.1, 2.20.1-0ubuntu0.16.04.1), 
libjavascriptcoregtk-4.0-18:amd64 (2.18.6-0ubuntu0.16.04.1, 
2.20.1-0ubuntu0.16.04.1), libwebkit2gtk-4.0-37-gtk2:amd64 
(2.18.6-0ubuntu0.16.04.1, 2.20.1-0ubuntu0.16.04.1), 
gir1.2-javascriptcoregtk-4.0:amd64 (2.18.6-0ubuntu0.16.04.1, 
2.20.1-0ubuntu0.16.04.1)
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2016-05-06 (725 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: LENOVO 2306CTO
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-122-generic.efi.signed 
root=UUID=28b0a55a-85a6-4f5e-8a78-262e5fdf1237 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.4
 apt  1.2.26
SourcePackage: systemd
Title: package udev 229-4ubuntu21.2 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/22/2014
dmi.bios.vendor: LENOVO
dmi.bios.version: G2ETA1WW (2.61 )
dmi.board.asset.tag: Not Available
dmi.board.name: 2306CTO
dmi.board.vendor: LENOVO
dmi.board.version: Win8 STD DPK TPG
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvrG2ETA1WW(2.61):bd04/22/2014:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrWin8STDDPKTPG:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 2306CTO
dmi.product.version: ThinkPad X230
dmi.sys.vendor: LENOVO

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

Title:
  package udev 229-4ubuntu21.2 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in systemd package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu 16.04.4 LTS
  Release:  16.04

  After a failed update, this system error comes back every time there
  is an update

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: udev 229-4ubuntu21.2
  ProcVersionSignature: Ubuntu 4.4.0-122.146-generic 4.4.117
  Uname: Linux 4.4.0-122-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  Date: Wed May  2 09:11:12 2018
  DpkgHistoryLog:
   Start-Date: 2018-05-02  09:11:06
   Commandline: /usr/bin/unattended-upgrade
   Install: libwebpdemux1:amd64 (0.4.4-1, automatic)
   Upgrade: libgs9:amd64 (9.18~dfsg~0-0ubuntu2.7, 9.18~dfsg~0-0ubuntu2.8), 
ghostscript:amd64 (9.18~dfsg~0-0ubuntu2.7, 9.18~dfsg~0-0ubuntu2.8), 
libwebkit2gtk-4.0-37:amd64 (2.18.6-0ubuntu0.16.04.1, 2.20.1-0ubuntu0.16.04.1), 
ghostscript-x:amd64 (9.18~dfsg~0-0ubuntu2.7, 9.18~dfsg~0-0ubuntu2.8), 
libgs9-common:amd64 (9.18~dfsg~0-0ubuntu2.7, 9.18~dfsg~0-0ubuntu2.8), 
gir1.2-webkit2-4.0:amd64 (2.18.6-0ubuntu0.16.04.1, 2.20.1-0ubuntu0.16.04.1), 
libjavascriptcoregtk-4.0-18:amd64 (2.18.6-0ubuntu0.16.04.1, 
2.20.1-0ubuntu0.16.04.1), libwebkit2gtk-4.0-37-gtk2:amd64 
(2.18.6-0ubuntu0.16.04.1, 2.20.1-0ubuntu0.16.04.1), 
gir1.2-javascriptcoregtk-4.0:amd64 (2.18.6-0ubuntu0.16.04.1, 
2.20.1-0ubuntu0.16.04.1)
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-05-06 (725 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 2306CTO
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-122-generic.efi.signed 
root=UUID=28b0a55a-85a6-4f5e-8a78-262e5fdf1237 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: systemd
  Title: package udev 229-4ubuntu21.2 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log 

[Touch-packages] [Bug 1764858] Re: Can't update / install / delete packages due to missing libzstd.so.1

[Joel Carlson]

Linux Mint XFCE 18.3 boots OK on my HP x360 laptop so I currently use
that to boot Xubuntu 18.04 on another partition. Will Xubuntu 18.04 be
fixed soon so people don't have this boot problem on uefi computers?
Thanks

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

Title:
  Can't update / install / delete packages due to missing libzstd.so.1

Status in apt package in Ubuntu:
  Invalid

Bug description:
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04

  After todays upgrade:

  vasily@vasily-desktop:~$ sudo apt-get update
  [sudo] пароль для vasily: 
  apt-get: error while loading shared libraries: libzstd.so.1: cannot open 
shared object file: No such file or directory

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1764858/+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 1768314] Re: Impossible to sign into launchpad

[Sebastien Bacher]

** Changed in: software-properties (Ubuntu)
   Importance: Undecided => Low

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

Title:
  Impossible to sign into launchpad

Status in software-properties package in Ubuntu:
  New

Bug description:
  I am using xubuntu and i wanted to use the live kernel update feature because 
I rarely reboot my system
  Well sadly it is not possible to sign into launchpad on xubuntu in 
software-properties-gtk
  I tried installing gnome-control-center and that did make the button work, 
but the application is empty, the window has no content

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: software-properties-gtk 0.96.24.32.1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue May  1 13:50:05 2018
  InstallationDate: Installed on 2018-04-29 (2 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1768314/+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 1767864] Re: package ca-certificates 20180409 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 1

[Steve Beattie]

Ah, after examining this more closely, Seth is correct in that Ondrej needs to 
pull in the fix to bug 1764848 in the openssl pacakge in the 
https://launchpad.net/~ondrej/+archive/ubuntu/php ppa.
I have filed https://github.com/oerdnj/deb.sury.org/issues/859 for the issue.

Thanks!

** Bug watch added: github.com/oerdnj/deb.sury.org/issues #859
   https://github.com/oerdnj/deb.sury.org/issues/859

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

Title:
  package ca-certificates 20180409 failed to install/upgrade: installed
  ca-certificates package post-installation script subprocess returned
  error exit status 1

Status in ca-certificates package in Ubuntu:
  Invalid

Bug description:
  da

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: ca-certificates 20180409
  ProcVersionSignature: Ubuntu 4.4.0-122.146-generic 4.4.117
  Uname: Linux 4.4.0-122-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Sun Apr 29 16:55:42 2018
  ErrorMessage: installed ca-certificates package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2016-11-11 (533 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: ca-certificates
  Title: package ca-certificates 20180409 failed to install/upgrade: installed 
ca-certificates package post-installation script subprocess returned error exit 
status 1
  UpgradeStatus: Upgraded to bionic on 2018-04-29 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1767864/+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 1573995] Re: I just upgraded to 16.04 and I'm getting a AppArmor Message AppArmor Message Profile:usr?sbin/dnsmasq Operation: connect Name: run/dbus/system_bus_socket Denied:wr L

[Seth Arnold]

I'm 90% sure the /var/log/kern.log comes from copy-pasting the aa-
logprof interface and isn't actually related here.

It looks vaguely like a usr.sbin.dnsmasq profile, but that part is
mangled.

It looks vaguely like it is using a systemd socket that is not actually
in its filesystem namespace, but perhaps that part is mangled too.

That's why I asked Randy for the logs -- they contain details that we
need.

Thanks

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

Title:
  I just upgraded to 16.04  and I'm getting a AppArmor Message AppArmor
  Message Profile:usr?sbin/dnsmasq Operation: connect Name:
  run/dbus/system_bus_socket Denied:wr Logfile: /var/log/kern.log
  DebuggingApparmor" for Ubuntu and when I try and enter my encription
  phrase it says something like no shell. Also, when I try and check for
  updates I am told I'm up to date ? Please let me know how I can debug
  AppArmor ? Randy Adamson adamsonran...@gmail.com Thanks

Status in apparmor package in Ubuntu:
  Expired

Bug description:
  I just upgraded to 16.04  and I'm getting a AppArmor Message AppArmor
  Message Profile:usr?sbin/dnsmasq Operation: connect Name:
  run/dbus/system_bus_socket Denied:wr Logfile: /var/log/kern.log
  DebuggingApparmor" for Ubuntu and when I try and enter my encription
  phrase it says something like no shell. Also, when I try and check for
  updates I am told I'm up to date ? Please let me know how I can debug
  AppArmor ? Randy Adamson adamsonran...@gmail.com Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1573995/+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 1767864] Re: package ca-certificates 20180409 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 1

[Steve Beattie]

** This bug is no longer a duplicate of bug 1764848
   Upgrade to ca-certificates to 20180409 causes ca-certificates.crt to be 
removed if duplicate certs found

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

Title:
  package ca-certificates 20180409 failed to install/upgrade: installed
  ca-certificates package post-installation script subprocess returned
  error exit status 1

Status in ca-certificates package in Ubuntu:
  Invalid

Bug description:
  da

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: ca-certificates 20180409
  ProcVersionSignature: Ubuntu 4.4.0-122.146-generic 4.4.117
  Uname: Linux 4.4.0-122-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Sun Apr 29 16:55:42 2018
  ErrorMessage: installed ca-certificates package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2016-11-11 (533 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: ca-certificates
  Title: package ca-certificates 20180409 failed to install/upgrade: installed 
ca-certificates package post-installation script subprocess returned error exit 
status 1
  UpgradeStatus: Upgraded to bionic on 2018-04-29 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1767864/+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 1767981] Re: Incorrect permissions on polkit-agent-helper-1

[Brian Murray]

** Summary changed:

- Incorrect permissions on upgrade found for login
+ Incorrect permissions on polkit-agent-helper-1

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

Title:
  Incorrect permissions on polkit-agent-helper-1

Status in policykit-1 package in Ubuntu:
  New

Bug description:
  I upgraded from 17.10 to 18.04, I ran 
  czajkowski@penny:~$ sudo do-release-upgrade
  czajkowski@penny:~$ sudo apt update && sudo apt dist-upgrade
  czajkowski@penny:~$ sudo apt install update-manager-core

  
  Upgrade then started and about 4 mins the Error 1 image appeared, Incorrect 
permissions on /usr/lib/policykit-1/polkit-agent-helper-1(needs to be setuid 
root)

  a few mins later the login appeared for me to enter my password,  it
  would not recognise my password Error 2.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader-core 1:18.04.17
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 30 10:21:49 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-12-20 (1226 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to bionic on 2018-04-29 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1767981/+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 1768340] [NEW] fscrypt does not work for home directory encryption

[Adar Dembo]

Public bug reported:

I am trying to use fscrypt in place of ecryptfs to encrypt my home
directory, and to automatically unlock/lock it on login and logout. I am
using a fresh installation of Ubuntu 18.04 done on 05/01/18. The
hardware is a Dell Precision 5520 laptop. The version of the fscrypt and
libpam-fscrypt packages is 0.2.2-0ubuntu2.

I began with the instructions in https://github.com/google/fscrypt
#setting-up-fscrypt-on-a-directory. I quickly ran into bug #1754270, but
after applying the workaround from that bug report I was able to
successfully encrypt a directory. With that out of the way, I set up a
new encrypted home directory, copied all of my files into it with rsync,
then moved it on top of the old home directory.

When I logged out and logged back in, I was presented with a blank
screen. The cursor was visible and responded to trackpad motion. If I
clicked the top right of the screen, I saw the usual drop-down menu
containing power settings and the like. I didn't see any other responses
to clicks or keypresses. Hitting ctrl-alt-fn-f1 brought me back to the
login screen. If I tried to login again, this time the desktop came up
normally and everything appeared to be working.

All of this suggests some sort of broken interaction here between
pam_fscrypt.so and the rest of the desktop startup process. There are
some open upstream bugs [1][2] about this, but I don't know enough about
PAM and systemd to understand what might be at fault.

This is sufficiently inconvenient that I'd consider the "encrypt home
directory via fscrypt" workflow to be broken on Ubuntu 18.04 at this
time.

1. https://github.com/google/fscrypt/issues/77
2. https://github.com/google/fscrypt/issues/95

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

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

** No longer affects: systemd (Ubuntu)

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

Title:
  fscrypt does not work for home directory encryption

Status in fscrypt package in Ubuntu:
  New

Bug description:
  I am trying to use fscrypt in place of ecryptfs to encrypt my home
  directory, and to automatically unlock/lock it on login and logout. I
  am using a fresh installation of Ubuntu 18.04 done on 05/01/18. The
  hardware is a Dell Precision 5520 laptop. The version of the fscrypt
  and libpam-fscrypt packages is 0.2.2-0ubuntu2.

  I began with the instructions in https://github.com/google/fscrypt
  #setting-up-fscrypt-on-a-directory. I quickly ran into bug #1754270,
  but after applying the workaround from that bug report I was able to
  successfully encrypt a directory. With that out of the way, I set up a
  new encrypted home directory, copied all of my files into it with
  rsync, then moved it on top of the old home directory.

  When I logged out and logged back in, I was presented with a blank
  screen. The cursor was visible and responded to trackpad motion. If I
  clicked the top right of the screen, I saw the usual drop-down menu
  containing power settings and the like. I didn't see any other
  responses to clicks or keypresses. Hitting ctrl-alt-fn-f1 brought me
  back to the login screen. If I tried to login again, this time the
  desktop came up normally and everything appeared to be working.

  All of this suggests some sort of broken interaction here between
  pam_fscrypt.so and the rest of the desktop startup process. There are
  some open upstream bugs [1][2] about this, but I don't know enough
  about PAM and systemd to understand what might be at fault.

  This is sufficiently inconvenient that I'd consider the "encrypt home
  directory via fscrypt" workflow to be broken on Ubuntu 18.04 at this
  time.

  1. https://github.com/google/fscrypt/issues/77
  2. https://github.com/google/fscrypt/issues/95

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fscrypt/+bug/1768340/+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 1767981] Re: Incorrect permissions on upgrade found for login

[Brian Murray]

I don't believe this has anything to do with the release upgrader, it
just happened to be the process which caused you to notice that the
permissions were incorrect.

** Package changed: ubuntu-release-upgrader (Ubuntu) => policykit-1
(Ubuntu)

** Changed in: policykit-1 (Ubuntu)
   Status: Incomplete => New

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

Title:
  Incorrect permissions on upgrade found for login

Status in policykit-1 package in Ubuntu:
  New

Bug description:
  I upgraded from 17.10 to 18.04, I ran 
  czajkowski@penny:~$ sudo do-release-upgrade
  czajkowski@penny:~$ sudo apt update && sudo apt dist-upgrade
  czajkowski@penny:~$ sudo apt install update-manager-core

  
  Upgrade then started and about 4 mins the Error 1 image appeared, Incorrect 
permissions on /usr/lib/policykit-1/polkit-agent-helper-1(needs to be setuid 
root)

  a few mins later the login appeared for me to enter my password,  it
  would not recognise my password Error 2.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader-core 1:18.04.17
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 30 10:21:49 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-12-20 (1226 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to bionic on 2018-04-29 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1767981/+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 1767864] Re: package ca-certificates 20180409 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 1

[Steve Beattie]

*** This bug is a duplicate of bug 1764848 ***
https://bugs.launchpad.net/bugs/1764848

Hi,

This is a duplicate of bug 1764848, which has been addressed with
openssl 1.1.0g-2ubuntu4 in Ubuntu 18.04 LTS. Looking at your dpkg
terminal log from the failed upgrade, it looks like the upgrade
installed openssl 1.0.2n-1ubuntu1, which was superceded in the ubuntu
archive on Feb 01 2018 according to the openssl publishing history:
https://launchpad.net/ubuntu/+source/openssl/+publishinghistory . This
likely means the ubuntu mirror your system is pointing at is
significantly out of date with respect to the main archive, and you may
wish to try a different mirror.

Thanks!

** This bug has been marked a duplicate of bug 1764848
   Upgrade to ca-certificates to 20180409 causes ca-certificates.crt to be 
removed if duplicate certs found

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

Title:
  package ca-certificates 20180409 failed to install/upgrade: installed
  ca-certificates package post-installation script subprocess returned
  error exit status 1

Status in ca-certificates package in Ubuntu:
  Invalid

Bug description:
  da

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: ca-certificates 20180409
  ProcVersionSignature: Ubuntu 4.4.0-122.146-generic 4.4.117
  Uname: Linux 4.4.0-122-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Sun Apr 29 16:55:42 2018
  ErrorMessage: installed ca-certificates package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2016-11-11 (533 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: ca-certificates
  Title: package ca-certificates 20180409 failed to install/upgrade: installed 
ca-certificates package post-installation script subprocess returned error exit 
status 1
  UpgradeStatus: Upgraded to bionic on 2018-04-29 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1767864/+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 1767981] [NEW] Incorrect permissions on upgrade found for login

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I upgraded from 17.10 to 18.04, I ran 
czajkowski@penny:~$ sudo do-release-upgrade
czajkowski@penny:~$ sudo apt update && sudo apt dist-upgrade
czajkowski@penny:~$ sudo apt install update-manager-core


Upgrade then started and about 4 mins the Error 1 image appeared, Incorrect 
permissions on /usr/lib/policykit-1/polkit-agent-helper-1(needs to be setuid 
root)

a few mins later the login appeared for me to enter my password,  it
would not recognise my password Error 2.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubuntu-release-upgrader-core 1:18.04.17
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr 30 10:21:49 2018
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-12-20 (1226 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntu-release-upgrader
Symptom: dist-upgrade
UpgradeStatus: Upgraded to bionic on 2018-04-29 (0 days ago)

** Affects: policykit-1 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug artful2bionic bionic dist-upgrade
-- 
Incorrect permissions on upgrade found for login
https://bugs.launchpad.net/bugs/1767981
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to policykit-1 in Ubuntu.

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

[Touch-packages] [Bug 1767201] Re: KVPM pam_unix(sudo:auth): auth could not identify password for user

[Seth Arnold]

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

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

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

Title:
  KVPM pam_unix(sudo:auth): auth could not identify password for user

Status in pam package in Ubuntu:
  New
Status in sudo package in Ubuntu:
  New

Bug description:
  Can't launch KVPM in Kubuntu 18.04 beta
  App is installed and gives password screen then fails

  Linux MadMax 4.15.0-15-generic #16-Ubuntu SMP Wed Apr 4 13:58:14 UTC
  2018 x86_64 x86_64 x86_64 GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1767201/+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 1765832] Re: Two finger scrolling not working after suspend

[Launchpad Bug Tracker]

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

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

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

Title:
  Two finger scrolling not working after suspend

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  When waking up my laptop, two finger scrolling is not working anymore.

  Running:

  $ modprobe -r psmouse
  $ modprobe psmouse

  restores the functionality.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Fri Apr 20 08:23:33 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.2.10, 4.15.0-15-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 5500 [17aa:2227]
  InstallationDate: Installed on 2018-04-10 (9 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180408)
  MachineType: LENOVO 20BTS09800
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/23/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N14ET26W (1.04 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BTS09800
  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.modalias: 
dmi:bvnLENOVO:bvrN14ET26W(1.04):bd01/23/2015:svnLENOVO:pn20BTS09800:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BTS09800:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 3rd
  dmi.product.name: 20BTS09800
  dmi.product.version: ThinkPad X1 Carbon 3rd
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1765832/+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 1767864] Re: package ca-certificates 20180409 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 1

[Seth Arnold]

I think you'll need to ask Ondrej to include fixes for
https://lists.debian.org/debian-devel/2018/04/msg00620.html

Thanks

** Information type changed from Private Security to Public Security

** Changed in: ca-certificates (Ubuntu)
   Status: New => Invalid

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

Title:
  package ca-certificates 20180409 failed to install/upgrade: installed
  ca-certificates package post-installation script subprocess returned
  error exit status 1

Status in ca-certificates package in Ubuntu:
  Invalid

Bug description:
  da

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: ca-certificates 20180409
  ProcVersionSignature: Ubuntu 4.4.0-122.146-generic 4.4.117
  Uname: Linux 4.4.0-122-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Sun Apr 29 16:55:42 2018
  ErrorMessage: installed ca-certificates package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2016-11-11 (533 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: ca-certificates
  Title: package ca-certificates 20180409 failed to install/upgrade: installed 
ca-certificates package post-installation script subprocess returned error exit 
status 1
  UpgradeStatus: Upgraded to bionic on 2018-04-29 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1767864/+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 1576432] Re: gdb crashes when trying to start a debugging session

[Chris Coulson]

This occurs when gdb sets breakpoints on various probe events in the
dynamic loader. The probe event locations are exported from ld.so as SDT
markers, but gdb needs to know whether ARM or Thumb instructions are
being exported at each marker so that it can insert the appropriate
breakpoint instruction sequence. It does this by mapping the probe
location to a function symbol (see arm_pc_is_thumb in gdb/arm-tdep.c),
and using the target address of the symbol to determine if the function
is called in Thumb or ARM more (bit 0 of the target address will be set
for Thumb mode).

The problem here is that gdb can't map any of the probes to a symbol if
the debug symbols aren't installed, and arm_pc_is_thumb returns false in
this case (indicating ARM instructions).

But the probes that gdb sets breakpoints on are in dl_main, and dl_main is 
meant to be called in Thumb mode. See the output of readelf, noting that bit 0 
of the target address is set:
$ readelf -s /usr/lib/debug/lib/arm-linux-gnueabihf/ld-2.27.so | grep dl_main
42: 172d 10516 FUNCLOCAL  DEFAULT   11 dl_main

So without the debug symbols installed, gdb inserts the ARM breakpoint
instruction sequence for the dynamic loader probes, when it should be
inserting the Thumb instruction sequence. This is why it crashes.

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

Title:
  gdb crashes when trying to start a debugging session

Status in gdb:
  New
Status in gdb package in Ubuntu:
  New

Bug description:
  This bug log applies to Ubuntu Mate for raspberry PI.

  I cannot use gdb to debug a program. See below. This happens on any
  program, even programs that come with ubuntu, for example try gdb
  /bin/less. It always crashes in  d-linux-armhf.so.3

  gdb mythfrontend
  GNU gdb (Ubuntu 7.11-0ubuntu1) 7.11
  Copyright (C) 2016 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "arm-linux-gnueabihf".
  Type "show configuration" for configuration details.
  For bug reporting instructions, please see:
  .
  Find the GDB manual and other documentation resources online at:
  .
  For help, type "help".
  Type "apropos word" to search for commands related to "word"...
  Reading symbols from mythfrontend...done.
  (gdb) start
  Temporary breakpoint 1 at 0x62c22: file main.cpp, line 1674.
  Starting program: 
/srv/storage/homexenial/peter/proj/mythtv-build/myth-p28/usr/bin/mythfrontend

  Program received signal SIGSEGV, Segmentation fault.
  0x76fd9822 in ?? () from /lib/ld-linux-armhf.so.3
  (gdb)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdb/+bug/1576432/+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 1576432] Re: gdb crashes when trying to start a debugging session

[Chris Coulson]

(Note, I looked at this because it was breaking rustc tests on armhf.
The workaround is the same - install libc6-dbg to make the crash go
away)

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

Title:
  gdb crashes when trying to start a debugging session

Status in gdb:
  New
Status in gdb package in Ubuntu:
  New

Bug description:
  This bug log applies to Ubuntu Mate for raspberry PI.

  I cannot use gdb to debug a program. See below. This happens on any
  program, even programs that come with ubuntu, for example try gdb
  /bin/less. It always crashes in  d-linux-armhf.so.3

  gdb mythfrontend
  GNU gdb (Ubuntu 7.11-0ubuntu1) 7.11
  Copyright (C) 2016 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "arm-linux-gnueabihf".
  Type "show configuration" for configuration details.
  For bug reporting instructions, please see:
  .
  Find the GDB manual and other documentation resources online at:
  .
  For help, type "help".
  Type "apropos word" to search for commands related to "word"...
  Reading symbols from mythfrontend...done.
  (gdb) start
  Temporary breakpoint 1 at 0x62c22: file main.cpp, line 1674.
  Starting program: 
/srv/storage/homexenial/peter/proj/mythtv-build/myth-p28/usr/bin/mythfrontend

  Program received signal SIGSEGV, Segmentation fault.
  0x76fd9822 in ?? () from /lib/ld-linux-armhf.so.3
  (gdb)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdb/+bug/1576432/+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 1767815] Re: Can use as a password

[Seth Arnold]

Hello Dhiraj, thanks for the report. The passwd utility assumes root
knows best and allows root to set any password to anything no matter how
poor.

You can use the pam_cracklib(8) PAM module to enforce some minimum
quality levels for your passwords when users set their own -- but of
course frustrated users may pick bad passwords this module doesn't know
how to discover.

Thanks

** Information type changed from Private Security to Public Security

** Changed in: shadow (Ubuntu)
   Status: New => Won't Fix

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

Title:
  Can use  as a password

Status in shadow package in Ubuntu:
  Won't Fix

Bug description:
  Hi Team,

  I am not sure about this, but thought of reporting tho!.

  warmachine@ftw:~$ uname -a
  Linux ftw 4.13.0-39-generic #44~16.04.1-Ubuntu SMP Thu Apr 5 16:43:10 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux

  However, while creating a user `sudo adduser test` I can keep only
   has my password for test user.

  Could someone please look into this and advise me for same. I believe
  password must be robust or only  should not be allowed.

  
  Thank you 
  DM

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1767815/+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 1767172] Re: Regression: /etc/modules checked against blacklist or it's really hard to load blacklisted watchdog modules when one really wants one

[Dimitri John Ledkov]

** Summary changed:

- Regression: /etc/modules checked against blacklist
+ Regression: /etc/modules checked against blacklist or it's really hard to 
load blacklisted watchdog modules when one really wants one

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

Title:
  Regression: /etc/modules checked against blacklist or it's really hard
  to load blacklisted watchdog modules when one really wants one

Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  New

Bug description:
  Impossible / hard to force the system to load a watchdog module
  because it is blacklisted by the kernel auto-generated list of
  "watchdog" modules.

  /etc/modules used to "just work" before.

  e.g. bcm2835_wdt module on arm64

  ===

  Before systemd-modules-load, /etc/init.d/kmod would load modules
  directly with "modprobe" (and _not_ "modprobe -b"):

  load_module() {
    local module args
    module="$1"
    args="$2"

    if [ "$VERBOSE" != no ]; then
  log_action_msg "Loading kernel module $module"
  modprobe $module $args || true
    else
  modprobe $module $args > /dev/null 2>&1 || true
    fi
  }

  However, under 18.04, systemd-modules-load will _ignore_ modules that
  are manually listed in /etc/modules and process them with the
  blacklist (the same as "modprobe -b" would). This means that it is not
  possible to manually load modules that are blacklisted (like watchdog
  modules):

  systemd-238/src/modules-load/modules-load.c:

  static int load_module(struct kmod_ctx *ctx, const char *m) {
  const int probe_flags = KMOD_PROBE_APPLY_BLACKLIST;
  ...
  default:
  err = kmod_module_probe_insert_module(mod, 
probe_flags,
    NULL, NULL, 
NULL, NULL);

  if (err == 0)
  log_info("Inserted module '%s'", 
kmod_module_get_name(mod));
  else if (err == KMOD_PROBE_APPLY_BLACKLIST)
  log_info("Module '%s' is blacklisted", 
kmod_module_get_name(mod));

  Blacklists should _not_ be applied by systemd-modules-load.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767172/+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 1767172] Re: Regression: /etc/modules checked against blacklist

[Dimitri John Ledkov]

Please note automatic blacklisting of watchdog modules was done to
prevent "accidental" watchdog misuse, resulting in "random" shutdowns of
production machines. See
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1432837 for more
details.

I'm not sure how to reconcile "blacklist as a precaution" with "I know
what I am doing, I really want watchdog".

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

Title:
  Regression: /etc/modules checked against blacklist or it's really hard
  to load blacklisted watchdog modules when one really wants one

Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  New

Bug description:
  Impossible / hard to force the system to load a watchdog module
  because it is blacklisted by the kernel auto-generated list of
  "watchdog" modules.

  /etc/modules used to "just work" before.

  e.g. bcm2835_wdt module on arm64

  ===

  Before systemd-modules-load, /etc/init.d/kmod would load modules
  directly with "modprobe" (and _not_ "modprobe -b"):

  load_module() {
    local module args
    module="$1"
    args="$2"

    if [ "$VERBOSE" != no ]; then
  log_action_msg "Loading kernel module $module"
  modprobe $module $args || true
    else
  modprobe $module $args > /dev/null 2>&1 || true
    fi
  }

  However, under 18.04, systemd-modules-load will _ignore_ modules that
  are manually listed in /etc/modules and process them with the
  blacklist (the same as "modprobe -b" would). This means that it is not
  possible to manually load modules that are blacklisted (like watchdog
  modules):

  systemd-238/src/modules-load/modules-load.c:

  static int load_module(struct kmod_ctx *ctx, const char *m) {
  const int probe_flags = KMOD_PROBE_APPLY_BLACKLIST;
  ...
  default:
  err = kmod_module_probe_insert_module(mod, 
probe_flags,
    NULL, NULL, 
NULL, NULL);

  if (err == 0)
  log_info("Inserted module '%s'", 
kmod_module_get_name(mod));
  else if (err == KMOD_PROBE_APPLY_BLACKLIST)
  log_info("Module '%s' is blacklisted", 
kmod_module_get_name(mod));

  Blacklists should _not_ be applied by systemd-modules-load.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767172/+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 1767172] Missing required logs.

[Ubuntu Kernel Bot]

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1767172

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

Title:
  Regression: /etc/modules checked against blacklist or it's really hard
  to load blacklisted watchdog modules when one really wants one

Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  New

Bug description:
  Impossible / hard to force the system to load a watchdog module
  because it is blacklisted by the kernel auto-generated list of
  "watchdog" modules.

  /etc/modules used to "just work" before.

  e.g. bcm2835_wdt module on arm64

  ===

  Before systemd-modules-load, /etc/init.d/kmod would load modules
  directly with "modprobe" (and _not_ "modprobe -b"):

  load_module() {
    local module args
    module="$1"
    args="$2"

    if [ "$VERBOSE" != no ]; then
  log_action_msg "Loading kernel module $module"
  modprobe $module $args || true
    else
  modprobe $module $args > /dev/null 2>&1 || true
    fi
  }

  However, under 18.04, systemd-modules-load will _ignore_ modules that
  are manually listed in /etc/modules and process them with the
  blacklist (the same as "modprobe -b" would). This means that it is not
  possible to manually load modules that are blacklisted (like watchdog
  modules):

  systemd-238/src/modules-load/modules-load.c:

  static int load_module(struct kmod_ctx *ctx, const char *m) {
  const int probe_flags = KMOD_PROBE_APPLY_BLACKLIST;
  ...
  default:
  err = kmod_module_probe_insert_module(mod, 
probe_flags,
    NULL, NULL, 
NULL, NULL);

  if (err == 0)
  log_info("Inserted module '%s'", 
kmod_module_get_name(mod));
  else if (err == KMOD_PROBE_APPLY_BLACKLIST)
  log_info("Module '%s' is blacklisted", 
kmod_module_get_name(mod));

  Blacklists should _not_ be applied by systemd-modules-load.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767172/+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 1767172] Re: Regression: /etc/modules checked against blacklist

[Dimitri John Ledkov]

** Description changed:

  Impossible / hard to force the system to load a watchdog module because
  it is blacklisted by the kernel auto-generated list of "watchdog"
  modules.
  
  /etc/modules used to "just work" before.
  
+ e.g. bcm2835_wdt module on arm64
+ 
  ===
  
- 
- Before systemd-modules-load, /etc/init.d/kmod would load modules directly 
with "modprobe" (and _not_ "modprobe -b"):
+ Before systemd-modules-load, /etc/init.d/kmod would load modules
+ directly with "modprobe" (and _not_ "modprobe -b"):
  
  load_module() {
    local module args
    module="$1"
    args="$2"
  
    if [ "$VERBOSE" != no ]; then
  log_action_msg "Loading kernel module $module"
  modprobe $module $args || true
    else
  modprobe $module $args > /dev/null 2>&1 || true
    fi
  }
  
  However, under 18.04, systemd-modules-load will _ignore_ modules that
  are manually listed in /etc/modules and process them with the blacklist
  (the same as "modprobe -b" would). This means that it is not possible to
  manually load modules that are blacklisted (like watchdog modules):
  
  systemd-238/src/modules-load/modules-load.c:
  
  static int load_module(struct kmod_ctx *ctx, const char *m) {
  const int probe_flags = KMOD_PROBE_APPLY_BLACKLIST;
  ...
  default:
  err = kmod_module_probe_insert_module(mod, 
probe_flags,
    NULL, NULL, 
NULL, NULL);
  
  if (err == 0)
  log_info("Inserted module '%s'", 
kmod_module_get_name(mod));
  else if (err == KMOD_PROBE_APPLY_BLACKLIST)
  log_info("Module '%s' is blacklisted", 
kmod_module_get_name(mod));
  
  Blacklists should _not_ be applied by systemd-modules-load.

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

Title:
  Regression: /etc/modules checked against blacklist or it's really hard
  to load blacklisted watchdog modules when one really wants one

Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  New

Bug description:
  Impossible / hard to force the system to load a watchdog module
  because it is blacklisted by the kernel auto-generated list of
  "watchdog" modules.

  /etc/modules used to "just work" before.

  e.g. bcm2835_wdt module on arm64

  ===

  Before systemd-modules-load, /etc/init.d/kmod would load modules
  directly with "modprobe" (and _not_ "modprobe -b"):

  load_module() {
    local module args
    module="$1"
    args="$2"

    if [ "$VERBOSE" != no ]; then
  log_action_msg "Loading kernel module $module"
  modprobe $module $args || true
    else
  modprobe $module $args > /dev/null 2>&1 || true
    fi
  }

  However, under 18.04, systemd-modules-load will _ignore_ modules that
  are manually listed in /etc/modules and process them with the
  blacklist (the same as "modprobe -b" would). This means that it is not
  possible to manually load modules that are blacklisted (like watchdog
  modules):

  systemd-238/src/modules-load/modules-load.c:

  static int load_module(struct kmod_ctx *ctx, const char *m) {
  const int probe_flags = KMOD_PROBE_APPLY_BLACKLIST;
  ...
  default:
  err = kmod_module_probe_insert_module(mod, 
probe_flags,
    NULL, NULL, 
NULL, NULL);

  if (err == 0)
  log_info("Inserted module '%s'", 
kmod_module_get_name(mod));
  else if (err == KMOD_PROBE_APPLY_BLACKLIST)
  log_info("Module '%s' is blacklisted", 
kmod_module_get_name(mod));

  Blacklists should _not_ be applied by systemd-modules-load.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767172/+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 1761834] Re: Right-click doesn't work

[FM33]

Hello,

I have this too : Physical button from the touchpad is handled as a left click.
I can use 2-fingers as a workaround, but "area" mode is not working though.

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

Title:
  Right-click doesn't work

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I decided to try out the beta for 18.04 from 17.10.  Upon upgrading, I
  discovered that right-clicking no longer works on my trackpad, and
  right-clicks are handled as left-clicks would be.  Two-finger right
  click does not work either.  If I plug in a mouse with a physical
  right button, right clicking does work.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Fri Apr  6 11:26:00 2018
  DistUpgraded: 2018-04-06 11:14:08,949 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.14.15-041415-generic, x86_64: installed
   bbswitch, 0.8, 4.15.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 530 [1028:06e4]
 Subsystem: Dell GM107M [GeForce GTX 960M] [1028:06e4]
  InstallationDate: Installed on 2017-05-04 (337 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: Dell Inc. XPS 15 9550
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic 
root=UUID=62d6bfc3-82e2-4ca2-9255-8dae5ad9b117 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-04-06 (0 days ago)
  dmi.bios.date: 08/21/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.0
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.0:bd08/21/2017:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1761834/+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 1761834] Re: Right-click doesn't work

[Launchpad Bug Tracker]

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

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

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

Title:
  Right-click doesn't work

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I decided to try out the beta for 18.04 from 17.10.  Upon upgrading, I
  discovered that right-clicking no longer works on my trackpad, and
  right-clicks are handled as left-clicks would be.  Two-finger right
  click does not work either.  If I plug in a mouse with a physical
  right button, right clicking does work.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Fri Apr  6 11:26:00 2018
  DistUpgraded: 2018-04-06 11:14:08,949 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.14.15-041415-generic, x86_64: installed
   bbswitch, 0.8, 4.15.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 530 [1028:06e4]
 Subsystem: Dell GM107M [GeForce GTX 960M] [1028:06e4]
  InstallationDate: Installed on 2017-05-04 (337 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: Dell Inc. XPS 15 9550
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic 
root=UUID=62d6bfc3-82e2-4ca2-9255-8dae5ad9b117 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-04-06 (0 days ago)
  dmi.bios.date: 08/21/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.0
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.0:bd08/21/2017:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1761834/+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 1767172] Re: Regression: /etc/modules checked against blacklist

[Dimitri John Ledkov]

Looking at where the blacklists come from, it looks like kernel
autogenerates "blacklist_linux_4.15-0-15-generic.conf" files which have
a combination of OSS and watchdog blacklists.

this indeed is not very nice/easy to override.

I wonder if the "watchdog" like modules should be shipped in separate
files elsewhere on disk, and collected into a "watchdog.conf" file which
matches blacklists for all installed kernels? That way it would be
easier for admin to override it, by dropping in an empty /etc/modules-
load.d/watchdog.conf?

Not sure how to make these modules 'available' yet not autoloaded. Split
them into a separate -watchdog-modules binary package? not installed =
not autoloaded? without any blacklists at all?

** Description changed:

- Before systemd-modules-load, /etc/init.d/kmod would load modules
- directly with "modprobe" (and _not_ "modprobe -b"):
+ Impossible / hard to force the system to load a watchdog module because
+ it is blacklisted by the kernel auto-generated list of "watchdog"
+ modules.
+ 
+ /etc/modules used to "just work" before.
+ 
+ ===
+ 
+ 
+ Before systemd-modules-load, /etc/init.d/kmod would load modules directly 
with "modprobe" (and _not_ "modprobe -b"):
  
  load_module() {
-   local module args
-   module="$1"
-   args="$2"
+   local module args
+   module="$1"
+   args="$2"
  
-   if [ "$VERBOSE" != no ]; then
- log_action_msg "Loading kernel module $module"
- modprobe $module $args || true
-   else
- modprobe $module $args > /dev/null 2>&1 || true
-   fi
+   if [ "$VERBOSE" != no ]; then
+ log_action_msg "Loading kernel module $module"
+ modprobe $module $args || true
+   else
+ modprobe $module $args > /dev/null 2>&1 || true
+   fi
  }
  
  However, under 18.04, systemd-modules-load will _ignore_ modules that
  are manually listed in /etc/modules and process them with the blacklist
  (the same as "modprobe -b" would). This means that it is not possible to
  manually load modules that are blacklisted (like watchdog modules):
  
  systemd-238/src/modules-load/modules-load.c:
  
  static int load_module(struct kmod_ctx *ctx, const char *m) {
- const int probe_flags = KMOD_PROBE_APPLY_BLACKLIST;
+ const int probe_flags = KMOD_PROBE_APPLY_BLACKLIST;
  ...
- default:
- err = kmod_module_probe_insert_module(mod, 
probe_flags,
-   NULL, NULL, 
NULL, NULL);
+ default:
+ err = kmod_module_probe_insert_module(mod, 
probe_flags,
+   NULL, NULL, 
NULL, NULL);
  
- if (err == 0)
- log_info("Inserted module '%s'", 
kmod_module_get_name(mod));
- else if (err == KMOD_PROBE_APPLY_BLACKLIST)
- log_info("Module '%s' is blacklisted", 
kmod_module_get_name(mod));
+ if (err == 0)
+ log_info("Inserted module '%s'", 
kmod_module_get_name(mod));
+ else if (err == KMOD_PROBE_APPLY_BLACKLIST)
+ log_info("Module '%s' is blacklisted", 
kmod_module_get_name(mod));
  
  Blacklists should _not_ be applied by systemd-modules-load.

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

Title:
  Regression: /etc/modules checked against blacklist

Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  New

Bug description:
  Impossible / hard to force the system to load a watchdog module
  because it is blacklisted by the kernel auto-generated list of
  "watchdog" modules.

  /etc/modules used to "just work" before.

  e.g. bcm2835_wdt module on arm64

  ===

  Before systemd-modules-load, /etc/init.d/kmod would load modules
  directly with "modprobe" (and _not_ "modprobe -b"):

  load_module() {
    local module args
    module="$1"
    args="$2"

    if [ "$VERBOSE" != no ]; then
  log_action_msg "Loading kernel module $module"
  modprobe $module $args || true
    else
  modprobe $module $args > /dev/null 2>&1 || true
    fi
  }

  However, under 18.04, systemd-modules-load will _ignore_ modules that
  are manually listed in /etc/modules and process them with the
  blacklist (the same as "modprobe -b" would). This means that it is not
  possible to manually load modules that are blacklisted (like watchdog
  modules):

  systemd-238/src/modules-load/modules-load.c:

  static int load_module(struct kmod_ctx *ctx, const char *m) {
  const int probe_flags = KMOD_PROBE_APPLY_BLACKLIST;
  ...
  default:
  err = kmod_module_probe_insert_module(mod, 
probe_flags,
    NULL, NULL, 

[Touch-packages] [Bug 1767172] Re: Regression: /etc/modules checked against blacklist

[Dimitri John Ledkov]

** Also affects: 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 systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1767172

Title:
  Regression: /etc/modules checked against blacklist

Status in linux package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  Before systemd-modules-load, /etc/init.d/kmod would load modules
  directly with "modprobe" (and _not_ "modprobe -b"):

  load_module() {
local module args
module="$1"
args="$2"

if [ "$VERBOSE" != no ]; then
  log_action_msg "Loading kernel module $module"
  modprobe $module $args || true
else
  modprobe $module $args > /dev/null 2>&1 || true
fi
  }

  However, under 18.04, systemd-modules-load will _ignore_ modules that
  are manually listed in /etc/modules and process them with the
  blacklist (the same as "modprobe -b" would). This means that it is not
  possible to manually load modules that are blacklisted (like watchdog
  modules):

  systemd-238/src/modules-load/modules-load.c:

  static int load_module(struct kmod_ctx *ctx, const char *m) {
  const int probe_flags = KMOD_PROBE_APPLY_BLACKLIST;
  ...
  default:
  err = kmod_module_probe_insert_module(mod, 
probe_flags,
NULL, NULL, 
NULL, NULL);

  if (err == 0)
  log_info("Inserted module '%s'", 
kmod_module_get_name(mod));
  else if (err == KMOD_PROBE_APPLY_BLACKLIST)
  log_info("Module '%s' is blacklisted", 
kmod_module_get_name(mod));

  Blacklists should _not_ be applied by systemd-modules-load.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767172/+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 1768314] [NEW] Impossible to sign into launchpad

[pqwoerituytrueiwoq]

Public bug reported:

I am using xubuntu and i wanted to use the live kernel update feature because I 
rarely reboot my system
Well sadly it is not possible to sign into launchpad on xubuntu in 
software-properties-gtk
I tried installing gnome-control-center and that did make the button work, but 
the application is empty, the window has no content

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: software-properties-gtk 0.96.24.32.1
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: XFCE
Date: Tue May  1 13:50:05 2018
InstallationDate: Installed on 2018-04-29 (2 days ago)
InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
PackageArchitecture: all
SourcePackage: software-properties
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: software-properties (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic

** Attachment added: "Screenshot_2018-05-01_13-54-04.png"
   
https://bugs.launchpad.net/bugs/1768314/+attachment/5131580/+files/Screenshot_2018-05-01_13-54-04.png

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

Title:
  Impossible to sign into launchpad

Status in software-properties package in Ubuntu:
  New

Bug description:
  I am using xubuntu and i wanted to use the live kernel update feature because 
I rarely reboot my system
  Well sadly it is not possible to sign into launchpad on xubuntu in 
software-properties-gtk
  I tried installing gnome-control-center and that did make the button work, 
but the application is empty, the window has no content

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: software-properties-gtk 0.96.24.32.1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue May  1 13:50:05 2018
  InstallationDate: Installed on 2018-04-29 (2 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1768314/+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 1768304] Re: package shared-mime-info 1.9-2 failed to install/upgrade: installed shared-mime-info package post-installation script subprocess was killed by signal (Terminated)

[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 shared-mime-info in
Ubuntu.
https://bugs.launchpad.net/bugs/1768304

Title:
  package shared-mime-info 1.9-2 failed to install/upgrade: installed
  shared-mime-info package post-installation script subprocess was
  killed by signal (Terminated)

Status in shared-mime-info package in Ubuntu:
  New

Bug description:
  I was trying to install projectlibre_1.7.0-1.deb when the error
  occurred.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: shared-mime-info 1.9-2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Wed May  2 00:59:17 2018
  DuplicateSignature:
   package:shared-mime-info:1.9-2
   Setting up shared-mime-info (1.9-2) ...
   dpkg: error processing package shared-mime-info (--configure):
installed shared-mime-info package post-installation script subprocess was 
killed by signal (Terminated)
  ErrorMessage: installed shared-mime-info package post-installation script 
subprocess was killed by signal (Terminated)
  InstallationDate: Installed on 2018-05-01 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: shared-mime-info
  Title: package shared-mime-info 1.9-2 failed to install/upgrade: installed 
shared-mime-info package post-installation script subprocess was killed by 
signal (Terminated)
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1768304/+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 1768304] [NEW] package shared-mime-info 1.9-2 failed to install/upgrade: installed shared-mime-info package post-installation script subprocess was killed by signal (Terminated)

[neversaynever]

Public bug reported:

I was trying to install projectlibre_1.7.0-1.deb when the error
occurred.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: shared-mime-info 1.9-2
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
Date: Wed May  2 00:59:17 2018
DuplicateSignature:
 package:shared-mime-info:1.9-2
 Setting up shared-mime-info (1.9-2) ...
 dpkg: error processing package shared-mime-info (--configure):
  installed shared-mime-info package post-installation script subprocess was 
killed by signal (Terminated)
ErrorMessage: installed shared-mime-info package post-installation script 
subprocess was killed by signal (Terminated)
InstallationDate: Installed on 2018-05-01 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.1
SourcePackage: shared-mime-info
Title: package shared-mime-info 1.9-2 failed to install/upgrade: installed 
shared-mime-info package post-installation script subprocess was killed by 
signal (Terminated)
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: shared-mime-info (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package bionic

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

Title:
  package shared-mime-info 1.9-2 failed to install/upgrade: installed
  shared-mime-info package post-installation script subprocess was
  killed by signal (Terminated)

Status in shared-mime-info package in Ubuntu:
  New

Bug description:
  I was trying to install projectlibre_1.7.0-1.deb when the error
  occurred.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: shared-mime-info 1.9-2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Wed May  2 00:59:17 2018
  DuplicateSignature:
   package:shared-mime-info:1.9-2
   Setting up shared-mime-info (1.9-2) ...
   dpkg: error processing package shared-mime-info (--configure):
installed shared-mime-info package post-installation script subprocess was 
killed by signal (Terminated)
  ErrorMessage: installed shared-mime-info package post-installation script 
subprocess was killed by signal (Terminated)
  InstallationDate: Installed on 2018-05-01 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: shared-mime-info
  Title: package shared-mime-info 1.9-2 failed to install/upgrade: installed 
shared-mime-info package post-installation script subprocess was killed by 
signal (Terminated)
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1768304/+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 1767172] Re: Regression: /etc/modules checked against blacklist

[Brian Murray]

** Tags added: rls-bb-incoming

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

Title:
  Regression: /etc/modules checked against blacklist

Status in systemd package in Ubuntu:
  New

Bug description:
  Before systemd-modules-load, /etc/init.d/kmod would load modules
  directly with "modprobe" (and _not_ "modprobe -b"):

  load_module() {
local module args
module="$1"
args="$2"

if [ "$VERBOSE" != no ]; then
  log_action_msg "Loading kernel module $module"
  modprobe $module $args || true
else
  modprobe $module $args > /dev/null 2>&1 || true
fi
  }

  However, under 18.04, systemd-modules-load will _ignore_ modules that
  are manually listed in /etc/modules and process them with the
  blacklist (the same as "modprobe -b" would). This means that it is not
  possible to manually load modules that are blacklisted (like watchdog
  modules):

  systemd-238/src/modules-load/modules-load.c:

  static int load_module(struct kmod_ctx *ctx, const char *m) {
  const int probe_flags = KMOD_PROBE_APPLY_BLACKLIST;
  ...
  default:
  err = kmod_module_probe_insert_module(mod, 
probe_flags,
NULL, NULL, 
NULL, NULL);

  if (err == 0)
  log_info("Inserted module '%s'", 
kmod_module_get_name(mod));
  else if (err == KMOD_PROBE_APPLY_BLACKLIST)
  log_info("Module '%s' is blacklisted", 
kmod_module_get_name(mod));

  Blacklists should _not_ be applied by systemd-modules-load.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1767172/+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 1767201] Re: KVPM pam_unix(sudo:auth): auth could not identify password for user

[Dan Coffey]

Hi Seth,

Kubuntu 18.04

uname -a
Linux MadMax 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux

I was starting KVPM and it would quit after the password request was 
entered.
with this error:
5/1/18 12:43 PM    sudo    pam_unix(sudo:auth): conversation failed
5/1/18 12:43 PM    sudo    pam_unix(sudo:auth): auth could not identify 
password for [dcoffey]

I've not had a issue with any other commands at this point.

After a few apt updates KVPM is starting up without error.
5/1/18 12:47 PM    sudo     dcoffey : TTY=pts/13 ; PWD=/home/dcoffey ; 
USER=root ; COMMAND=/usr/lib/x86_64-linux-gnu/libexec/kf5/kdesu_stub -
5/1/18 12:47 PM    sudo    pam_unix(sudo:session): session opened for 
user root by (uid=0)
5/1/18 12:47 PM    sudo    pam_unix(sudo:session): session closed for 
user root
5/1/18 12:47 PM    sudo     dcoffey : TTY=pts/13 ; PWD=/home/dcoffey ; 
USER=root ; COMMAND=/usr/lib/x86_64-linux-gnu/libexec/kf5/kdesu_stub -
5/1/18 12:47 PM    sudo    pam_unix(sudo:session): session opened for 
user root by (uid=0)
5/1/18 12:47 PM    kernel     sdf:
5/1/18 12:47 PM    lvmetad    WARNING: Ignoring unsupported value for cmd.


But when I quit KVPM syslog has the same error:

5/1/18 12:47 PM    sudo    pam_unix(sudo:session): session closed for 
user root
5/1/18 12:47 PM    sudo    pam_unix(sudo:auth): conversation failed
5/1/18 12:47 PM    sudo    pam_unix(sudo:auth): auth could not identify 
password for [dcoffey]

Dan

On 04/30/2018 10:04 PM, Seth Arnold wrote:
> Hi Dan, can you please describe what you're doing, what you expected to
> happen, and what happened? Messages from logfiles might also be helpful.
>
> Thanks
>
> ** Changed in: sudo (Ubuntu)
> Status: New => Incomplete
>
> ** Information type changed from Private Security to Public Security
>

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

Title:
  KVPM pam_unix(sudo:auth): auth could not identify password for user

Status in sudo package in Ubuntu:
  Incomplete

Bug description:
  Can't launch KVPM in Kubuntu 18.04 beta
  App is installed and gives password screen then fails

  Linux MadMax 4.15.0-15-generic #16-Ubuntu SMP Wed Apr 4 13:58:14 UTC
  2018 x86_64 x86_64 x86_64 GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1767201/+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 1766872] Re: 'Enable Network' in recovery mode not working in Bionic

[Eric Desrochers]

So far using the following, it seems to work for all services but
NetworkManager, which still fails.

# /lib/recovery-mode/options/network

if [ -d /run/systemd/system ]; then
for i in dbus.socket systemd-resolved.service networking.service 
systemd-networkd.service NetworkManager.service; do
- systemctl is-enabled -q $i && systemctl start $i
+   IS_ENABLED=$(systemctl is-enabled $i)
+ if [ "$IS_ENABLED" != "disabled" ];then
+systemctl start --job-mode=ignore-dependencies --no-ask-password $i
+  fi
done
/lib/systemd/systemd-networkd-wait-online && exit 0 
fi


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

Title:
  'Enable Network' in recovery mode not working in Bionic

Status in friendly-recovery package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  This bug has been noticed after the introduction of the fix of (LP:
  #1682637) in Bionic.

  I have notice a block in Bionic when choosing 'Enable Network' option
  in recovery mode on different bionic vanilla system and I can
  reproduce all the time.

  I also asked colleagues to give it a try (for a second pair of eye on
  this) and they have the same result as me.

  Basically, when choosing 'Enable Network' it get block or lock.
  If we hit 'ctrl-c', then a shell arrive and the system has network 
connectivity.

  Here's what I find while enabling "systemd.debug-shell=1" from vtty9 :

  # pstree
  systemd-+-bash---pstree
  |-recovery-menu---network---systemctl---systemd-tty-ask
  |-systemd-journal
  

  # ps
  root 486 473 0 08:29 tty1 00:00:00 /bin/systemd-tty-ask-password-agent

  root 473 486 0 08:29 tty1 00:00:00 systemctl start dbus.socket

  root 486 283 0 08:29 tty1 00:00:00 /bin/sh /lib/recovery-
  mode/options/network

  Additionally,

  systemd-analyze blame:
  "Bootup is not yet finished. Please try again later"

  "systemctl list-jobs" is showing a 100 jobs in 'waiting' state

  The only 'running' unit is friendly-recovery.service :
  52 friendly-recovery.service start running

  The rest are all "waiting". My understanding is that "waiting" units
  will be executed only after those which are "running" are completed.
  Which explain why the "ctlr-c" allow the boot to continue.

  All the systemd special unit important at boot-up are waiting.
  7 sysinit.target start waiting
  3 basic.target   start waiting
  .

  Seems like systemd is not fully initialise in 'Recovery Mode' and
  doesn't allow any 'systemctl start' operation without
  password/passphrase request, which I suspect is hidden by the
  recovery-mode menu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/1766872/+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 1752053] Re: nvidia-390 fails to boot graphical display

[Kyle Weber]

At the top of this page it says "Fix Released". Does anyone know to to
get them to change the status to an open bug and re-evaluate it? It's
clearly not fixed.

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

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Invalid

Bug description:
  I'm using Bionic with the new 4.15 kernel. I've been using the
  nvidia-384 driver with no problem for a while.  Today I issued "sudo
  apt-get upgrade" and I was prompted to upgrade the nvidia driver to
  the nvidia-390.  After installing the driver and rebooting, I was only
  able to boot in to the tty terminal.  The graphical display failed to
  boot.  I have had similar problems with nvidia driver version 390 with
  Arch Linux and with Open Suse Tumbleweed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+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 1767875] Re: /usr/bin/update-manager:ValueError:restart_icon_renderer_data_func:pkg_requires_restart:__get_candidate

[Julian Andres Klode]

This is a safety check added in python-apt to prevent old package
objects being reused in new (dep)caches. since the cache operates on
package ids, and the package ids might change, there are three things
that can happen:

(1) If # of packages in new cache < # in old cache: SEGV
(2) If id changed, functions called on the package might operate on a different 
package
(3) If you are lucky, everything works

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

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

Title:
  /usr/bin/update-
  
manager:ValueError:restart_icon_renderer_data_func:pkg_requires_restart:__get_candidate

Status in apt package in Ubuntu:
  Invalid
Status in update-manager package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
update-manager.  This problem was most recently seen with package version 
1:18.04.11, the problem page at 
https://errors.ubuntu.com/problem/a2ba8d3ab5e432b3c15f172ded6d473f4c00720a 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1767875/+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 890867] Re: pulseaudio crashed with SIGABRT in pa_memimport_free()

[Taras Prokopenko]

** Changed in: pulseaudio (Ubuntu)
   Status: Expired => New

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

Title:
  pulseaudio crashed with SIGABRT in pa_memimport_free()

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Sound crashed after changing the volume, but seems random, hasn't done
  it again. Might be related to instalation of pulseaudio-equalizer,
  even if I do notice the sound widget/icon (gnome-shell) restarting at
  times.

  ProblemType: Crash
  DistroRelease: Ubuntu 11.10
  Package: pulseaudio 1:1.0-0ubuntu3.1
  ProcVersionSignature: Ubuntu 3.0.0-13.22-generic 3.0.6
  Uname: Linux 3.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dramalho   5025 F pulseaudio
   /dev/snd/controlC0:  dramalho   5025 F pulseaudio
   /dev/snd/pcmC0D0p:   dramalho   5025 F...m pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xd742 irq 47'
 Mixer name : 'IDT 92HD75B3X5'
 Components : 'HDA:111d7603,103c172b,00100202 
HDA:11c11040,103c3066,00100200'
 Controls  : 15
 Simple ctrls  : 10
  Card1.Amixer.info:
   Card hw:1 'NVidia'/'HDA NVidia at 0xd300 irq 16'
 Mixer name : 'Nvidia GPU 0b HDMI/DP'
 Components : 'HDA:10de000b,10de0101,00100100'
 Controls  : 16
 Simple ctrls  : 4
  Date: Tue Nov 15 18:23:52 2011
  ExecutablePath: /usr/bin/pulseaudio
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
  Signal: 6
  SourcePackage: pulseaudio
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libpulsecommon-1.0.so
   pa_memimport_free () from /usr/lib/x86_64-linux-gnu/libpulsecommon-1.0.so
   pa_pstream_unlink () from /usr/lib/x86_64-linux-gnu/libpulsecommon-1.0.so
   ?? () from /usr/lib/pulse-1.0/modules/libprotocol-native.so
   ?? () from /usr/lib/pulse-1.0/modules/libprotocol-native.so
  Title: pulseaudio crashed with SIGABRT in pa_memimport_free()
  UpgradeStatus: Upgraded to oneiric on 2011-09-01 (74 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare sudo
  XsessionErrors:
   (gnome-shell:2192): Clutter-WARNING **: Attempting to add actor of type 
'ShellGenericContainer' to a container of type 'StBoxLayout', but the actor has 
already a parent of type 'StBoxLayout'.
   (dropbox:2299): Gdk-CRITICAL **: 
IA__gdk_window_thaw_toplevel_updates_libgtk_only: assertion 
`private->update_and_descendants_freeze_count > 0' failed
   (process:4796): Gtk-WARNING **: Locale not supported by C library.
  dmi.bios.date: 03/09/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68CCU Ver. F.12
  dmi.board.name: 172B
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 30.31
  dmi.chassis.asset.tag: CZC0126G5J
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68CCUVer.F.12:bd03/09/2011:svnHewlett-Packard:pnHPEliteBook8440p:pvr:rvnHewlett-Packard:rn172B:rvrKBCVersion30.31:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 8440p
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/890867/+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 1553685] Re: Lenovo Y700-17ISK subwoofer doesn't work

[Camilo]

Doesn't work on my Lenovo Y700-17ISK

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

Title:
  Lenovo Y700-17ISK subwoofer doesn't work

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Lenovo Y700-17ISK (Intel Core i7-6700HQ/RAM 16GB/SSD 512GB/Nvidia GTX960M 4GB)
  Operating system: Ubuntu 16.04 (xenial-desktop-amd64.iso 04-Mar-2016, kernel 
4.4.0-10-generic, nvidia 361.28)

  Problem: Notebook subwoofer doesn't work.

  Judging from alsa-info.sh output, there is no pin declared for the bass 
output by BIOS.
  Please find a zip file attached: 'alsa-info_hdajackretask-unconnected-pins'

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-10-generic 4.4.0-10.25
  ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3
  Uname: Linux 4.4.0-10-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aljosa 1776 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Mar  6 11:02:21 2016
  HibernationDevice: RESUME=UUID=ac022671-63df-40ae-bffe-66fff3b35125
  InstallationDate: Installed on 2016-03-05 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304)
  MachineType: LENOVO 80Q0
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-10-generic.efi.signed 
root=UUID=aa4325c4-4b4c-4372-b8ca-a66c3e5b2aa6 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-10-generic N/A
   linux-backports-modules-4.4.0-10-generic  N/A
   linux-firmware1.156
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/31/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: CDCN30WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Allsparks 7A
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad Y700-17ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrCDCN30WW:bd01/31/2016:svnLENOVO:pn80Q0:pvrLenovoideapadY700-17ISK:rvnLENOVO:rnAllsparks7A:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapadY700-17ISK:
  dmi.product.name: 80Q0
  dmi.product.version: Lenovo ideapad Y700-17ISK
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1553685/+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 1766727] Re: initramfs-tools exception during pm.DoInstall with do-release-upgrade from 16.04 to 18.04

[Brian Murray]

Hello John, or anyone else affected,

Accepted s390-tools into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/s390-tools/1.34.0-0ubuntu8.6 in a
few hours, and then in the -proposed repository.

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

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

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

** Changed in: s390-tools (Ubuntu Xenial)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-xenial

** Changed in: ubuntu-release-upgrader (Ubuntu Xenial)
   Status: New => Invalid

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

Title:
  initramfs-tools exception during pm.DoInstall with  do-release-upgrade
  from 16.04 to 18.04

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Fix Committed
Status in s390-tools package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  Invalid
Status in initramfs-tools source package in Xenial:
  New
Status in linux source package in Xenial:
  New
Status in s390-tools source package in Xenial:
  Fix Committed
Status in ubuntu-release-upgrader source package in Xenial:
  Invalid
Status in initramfs-tools source package in Bionic:
  Invalid
Status in linux source package in Bionic:
  Fix Committed
Status in s390-tools source package in Bionic:
  Fix Released
Status in ubuntu-release-upgrader source package in Bionic:
  Invalid

Bug description:
  [Impact]
  Upgrades of linux-image-generic-hwe-16.04-edge will fail to configure because 
the post-update script for zipl will fail.

  [Test Case]
  Upgrade linux-image-generic-hwe-16.04-edge from xenial to xenial-proposed on 
s390x.

  [Regression]
  zipl update on s390x might fail, causing the system to be unbootable.

  
  

  Upgrading from 16.04 to 18.04 using 'do-release-upgrade -d' results
  in:

  Errors were encountered while processing:
   initramfs-tools
  Exception during pm.DoInstall():  E:Sub-process /usr/bin/dpkg returned an 
error code (1)

  Could not install the upgrades

  The upgrade has aborted. Your system could be in an unusable state. A
  recovery will run now (dpkg --configure -a).

  ---

  Processing triggers for systemd (237-3ubuntu10) ...
  Processing triggers for initramfs-tools (0.130ubuntu3) ...
  update-initramfs: Generating /boot/initrd.img-4.4.0-121-generic
  Using config file '/etc/zipl.conf'
  Error: Ramdisk file '/boot/initrd.img' in section 'ubuntu': No such file or 
directory
  run-parts: /etc/initramfs/post-update.d//zz-zipl exited with return code 1
  dpkg: error processing package initramfs-tools (--configure):
   installed initramfs-tools package post-installation script subprocess 
returned error exit status 1
  Processing triggers for ca-certificates (20180409) ...
  Updating certificates in /etc/ssl/certs...
  0 added, 0 removed; done.
  Running hooks in /etc/ca-certificates/update.d...
  done.
  Processing triggers for dictionaries-common (1.27.2) ...
  Processing triggers for linux-image-4.15.0-19-generic (4.15.0-19.20) ...
  /etc/kernel/postinst.d/initramfs-tools:
  update-initramfs: Generating /boot/initrd.img-4.15.0-19-generic
  Using config file '/etc/zipl.conf'
  Building bootmap in '/boot'
  Building menu 'menu'
  Adding #1: IPL section 'ubuntu' (default)
  Adding #2: IPL section 'old'
  Preparing boot device: dasdb (0104).
  Done.
  /etc/kernel/postinst.d/zz-zipl:
  Using config file '/etc/zipl.conf'
  Building bootmap in '/boot'
  Building menu 'menu'
  Adding #1: IPL section 'ubuntu' (default)
  Adding #2: IPL section 'old'
  Preparing boot device: dasdb (0104).
  Done.
  Processing triggers for sgml-base (1.29) ...
  Processing triggers for resolvconf (1.79ubuntu10) ...
  Processing triggers for ureadahead (0.100.0-20) ...
  Errors were encountered while processing:
   initramfs-tools
  Log ended: 2018-04-24  13:12:40
  ---
  ApportVersion: 2.20.9-0ubuntu6
  Architecture: s390x
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   

[Touch-packages] [Bug 1748839] Re: Problem to connect to WPA2/PEAP WIFI - gnome-shell

[Gabriel]

Same problem here, standard WPA2 works fine but not WPA2/PEAP.
Worked fine in 17.10.

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

Title:
  Problem to connect to WPA2/PEAP WIFI  - gnome-shell

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Connection to open or WPA secured wifi works without any issues.
  Connection to WPA2/PEAP fails. Repeatedly asks for username/password.

  Possible gnome-shell integration issue.

  The system was updated from Xenial to Bionic in mid-January. At that
  time this WPA2/PEAP setup worked without any issues. With the updates
  coming in the last week of January / First February week - the bug was
  experienced.

  1)
  ➜  syncthing git:(master) lsb_release -rd
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04

  2) - up to date packages
  [code]
  ➜  cat /etc/apt/sources.list |egrep -v '^#'
  deb http://cz.archive.ubuntu.com/ubuntu/ bionic main restricted
  deb http://cz.archive.ubuntu.com/ubuntu/ bionic-updates main restricted
  deb http://cz.archive.ubuntu.com/ubuntu/ bionic universe
  deb http://cz.archive.ubuntu.com/ubuntu/ bionic-updates universe
  deb http://cz.archive.ubuntu.com/ubuntu/ bionic multiverse
  deb http://cz.archive.ubuntu.com/ubuntu/ bionic-updates multiverse
  deb http://security.ubuntu.com/ubuntu/ bionic-security multiverse main 
universe restricted
  [/code]

  Note:
  # some pkg version related to problem might be from proposed-updates repo

  2b)
  [code]
  dpkg -l |egrep -i 'network manager|networkm|libnm'
  ii  gir1.2-networkmanager-1.0:amd641.8.4-1ubuntu4 
amd64GObject introspection data for 
the libnm-glib/libnm-util library
  ii  gir1.2-nm-1.0:amd641.8.4-1ubuntu4 
amd64GObject introspection data for 
the libnm library
  ii  gir1.2-nmgtk-1.0:amd64 1.8.10-2ubuntu1
amd64GObject introspection data for 
libnm-gtk
  ii  libnm-glib-vpn1:amd64  1.8.4-1ubuntu4 
amd64network management framework 
(GLib VPN shared library)
  ii  libnm-glib4:amd64  1.8.4-1ubuntu4 
amd64network management framework 
(GLib shared library)
  ii  libnm-gtk0:amd64   1.8.10-2ubuntu1
amd64library for wireless and 
mobile dialogs (libnm-glib version)
  ii  libnm-util2:amd64  1.8.4-1ubuntu4 
amd64network management framework 
(shared library)
  ii  libnm0:amd64   1.8.4-1ubuntu4 
amd64GObject-based client library 
for NetworkManager
  ii  libnma0:amd64  1.8.10-2ubuntu1
amd64library for wireless and 
mobile dialogs (libnm version)
  ii  libproxy1-plugin-networkmanager:amd64  0.4.15-0ubuntu1
amd64automatic proxy configuration 
management library (Network Manager plugin)
  ii  network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu4 
all  NetworkManager configuration 
to enable connectivity checking
  ii  strongswan-nm  5.6.1-2ubuntu1 
amd64strongSwan plugin to interact 
with NetworkManager

  ii  wpasupplicant  2:2.6-15ubuntu2
  amd64client support for WPA and WPA2 (IEEE 802.11i)

  [/code]

  3,4)
  Connection to open or WPA secured wifi works withou any issues. Connection to 
WPA2/PLEAP (without cert, just with username/password fails). Although wifi 
layer get's is associated the client (network-manager) possibly due to bug 
deauthenticate itself without establishing an IP connection.

  Connect to network.

  5)
  Logs (syslog/kernel)

  Core moments:

  [code]
  Feb 12 09:19:02 dontpanic NetworkManager[1125]:   [1518423542.9125] 
keyfile: update /etc/NetworkManager/system-connections/WiFi 
(82c55e94-907a-458a-ae31-8cbd75db0fa5,"WiFi")
  Feb 12 09:19:02 dontpanic gnome-shell[4284]: g_value_get_string: assertion 
'G_VALUE_HOLDS_STRING (value)' failed

  and ...

  Feb 12 09:19:02 dontpanic NetworkManager[1125]:   [1518423542.9450] 
device (wlp4s0): Activation: (wifi) connection 'WiFi' has security, and 
secrets exist.  No new secrets needed.
  Feb 12 09:19:02 dontpanic NetworkManager[1125]:   

[Touch-packages] [Bug 1766727] Re: initramfs-tools exception during pm.DoInstall with do-release-upgrade from 16.04 to 18.04

[Thadeu Lima de Souza Cascardo]

** Description changed:

+ [Impact]
+ Upgrades of linux-image-generic-hwe-16.04-edge will fail to configure because 
the post-update script for zipl will fail.
+ 
+ [Test Case]
+ Upgrade linux-image-generic-hwe-16.04-edge from xenial to xenial-proposed on 
s390x.
+ 
+ [Regression]
+ zipl update on s390x might fail, causing the system to be unbootable.
+ 
+ 
  Upgrading from 16.04 to 18.04 using 'do-release-upgrade -d' results in:
  
  Errors were encountered while processing:
   initramfs-tools
  Exception during pm.DoInstall():  E:Sub-process /usr/bin/dpkg returned an 
error code (1)
  
  Could not install the upgrades
  
  The upgrade has aborted. Your system could be in an unusable state. A
  recovery will run now (dpkg --configure -a).
  
  ---
  
  Processing triggers for systemd (237-3ubuntu10) ...
  Processing triggers for initramfs-tools (0.130ubuntu3) ...
  update-initramfs: Generating /boot/initrd.img-4.4.0-121-generic
  Using config file '/etc/zipl.conf'
  Error: Ramdisk file '/boot/initrd.img' in section 'ubuntu': No such file or 
directory
  run-parts: /etc/initramfs/post-update.d//zz-zipl exited with return code 1
  dpkg: error processing package initramfs-tools (--configure):
-  installed initramfs-tools package post-installation script subprocess 
returned error exit status 1
+  installed initramfs-tools package post-installation script subprocess 
returned error exit status 1
  Processing triggers for ca-certificates (20180409) ...
  Updating certificates in /etc/ssl/certs...
  0 added, 0 removed; done.
  Running hooks in /etc/ca-certificates/update.d...
  done.
  Processing triggers for dictionaries-common (1.27.2) ...
  Processing triggers for linux-image-4.15.0-19-generic (4.15.0-19.20) ...
  /etc/kernel/postinst.d/initramfs-tools:
  update-initramfs: Generating /boot/initrd.img-4.15.0-19-generic
  Using config file '/etc/zipl.conf'
  Building bootmap in '/boot'
  Building menu 'menu'
  Adding #1: IPL section 'ubuntu' (default)
  Adding #2: IPL section 'old'
  Preparing boot device: dasdb (0104).
  Done.
  /etc/kernel/postinst.d/zz-zipl:
  Using config file '/etc/zipl.conf'
  Building bootmap in '/boot'
  Building menu 'menu'
  Adding #1: IPL section 'ubuntu' (default)
  Adding #2: IPL section 'old'
  Preparing boot device: dasdb (0104).
  Done.
  Processing triggers for sgml-base (1.29) ...
  Processing triggers for resolvconf (1.79ubuntu10) ...
  Processing triggers for ureadahead (0.100.0-20) ...
  Errors were encountered while processing:
-  initramfs-tools
+  initramfs-tools
  Log ended: 2018-04-24  13:12:40
- --- 
+ ---
  ApportVersion: 2.20.9-0ubuntu6
  Architecture: s390x
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader
  PackageArchitecture: all
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=C
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=C
+  SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.15.0-19.20-generic 4.15.17
  Tags:  bionic
  Uname: Linux 4.15.0-19-generic s390x
  UpgradeStatus: Upgraded to bionic on 2018-04-24 (0 days ago)
  UserGroups: adm cdrom cpacfstats dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

** Description changed:

  [Impact]
  Upgrades of linux-image-generic-hwe-16.04-edge will fail to configure because 
the post-update script for zipl will fail.
  
  [Test Case]
  Upgrade linux-image-generic-hwe-16.04-edge from xenial to xenial-proposed on 
s390x.
  
  [Regression]
  zipl update on s390x might fail, causing the system to be unbootable.
  
+ 
+ 
  
  Upgrading from 16.04 to 18.04 using 'do-release-upgrade -d' results in:
  
  Errors were encountered while processing:
   initramfs-tools
  Exception during pm.DoInstall():  E:Sub-process /usr/bin/dpkg returned an 
error code (1)
  
  Could not install the upgrades
  
  The upgrade has aborted. Your system could be in an unusable state. A
  recovery will run now (dpkg --configure -a).
  
  ---
  
  Processing triggers for systemd (237-3ubuntu10) ...
  Processing triggers for initramfs-tools (0.130ubuntu3) ...
  update-initramfs: Generating /boot/initrd.img-4.4.0-121-generic
  Using config file '/etc/zipl.conf'
  Error: Ramdisk file '/boot/initrd.img' in section 'ubuntu': No such file or 
directory
  run-parts: /etc/initramfs/post-update.d//zz-zipl exited with return code 1
  dpkg: error processing package initramfs-tools (--configure):
   installed initramfs-tools package post-installation script subprocess 
returned error exit status 1
  Processing triggers for ca-certificates (20180409) ...
  Updating certificates in /etc/ssl/certs...
  0 added, 0 removed; done.
  Running hooks in /etc/ca-certificates/update.d...
  done.
  Processing triggers for dictionaries-common (1.27.2) ...
  Processing triggers for linux-image-4.15.0-19-generic (4.15.0-19.20) ...
  /etc/kernel/postinst.d/initramfs-tools:
  update-initramfs: Generating 

[Touch-packages] [Bug 1760818] Re: gedit and gnome-calculator transparency/graphics corruption issue

[Gunnar Hjalmarsson]

Second thoughts.. im-config does fall back to GTK_IM_MODULE=xim under certain 
conditions. The code is in the file
/usr/share/im-config/data/21_ibus.rc

We are considering to stop im-config from setting GTK_IM_MODULE at all
on GNOME desktops; bug #1761554 would be a reason to do so, and such a
change would apparently fix this bug as well.

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

Title:
  gedit and gnome-calculator transparency/graphics corruption issue

Status in im-config package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Invalid

Bug description:
  In a "Ubuntu" (Xorg) session on 18.04 gedit and gnome-calculator
  suffer from a graphics issue where parts of their windows hold parts
  of wallpaper or other windows' contents as background.

  See attached screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: light-themes 16.10+18.04.20180328-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  3 09:12:31 2018
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: Upgraded to bionic on 2018-02-07 (54 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1760818/+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 1767784] Re: [regression] output device not recognized anymore since update 1:8.0-0ubuntu3.9

[Flavien]

@Hui, of course, I'll keep both my distributions (16.04 and 18.04) up-
to-date. I will keep you posted about issues that might come.

In the mean time, don't hesitate asking if you need any test on my side
(like if you want test on a different configuration than yours).

Cheers

Flavien

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

Title:
  [regression] output device not recognized anymore since update
  1:8.0-0ubuntu3.9

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Since the update 1:8.0-0ubuntu3.8 to 1:8.0-0ubuntu3.9 , pulseaudio is
  not showing anymore my soundcard.

  The command "pacmd list-sinks" only shows a dummy output

  When running on a fresh install of ubuntu 16.04, the sound is ok.
  When updating the install with locking the following files to version 
1:8.0-0ubuntu3 the sound keeps working:
  libpulse0:amd64
  libpulse-mainloop-glib0:amd64
  libpulse-dev:amd64
  pulseaudio-module-x11:amd64
  pulseaudio-module-bluetooth:amd64
  pulseaudio-utils:amd64

  When updating to 1:8.0-0ubuntu3.9, I just get a "dummy output".

  I tried running the following versions of Ubuntu (live usb), and get the same 
issue (no need to update to get the problem)
  17.04
  17.10
  18.04

  I attached the result of command "pactl list"
  I have also generated logs during the boot but I don't know how to attach 
multiple files

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1767784/+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 1561643] Re: initramfs-tools ignores the FRAMEBUFFER option

[Brian Murray]

** Tags added: rls-bb-incoming

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

Title:
  initramfs-tools ignores the FRAMEBUFFER option

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  initramfs-tools ignores the FRAMEBUFFER option. This means that the
  framebuffer hook will always include the drm modules, regardless of
  whether it is dealing with an encrypted system or not.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: initramfs-tools 0.122ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Mar 24 18:06:24 2016
  InstallationDate: Installed on 2016-02-16 (37 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160209)
  PackageArchitecture: all
  SourcePackage: initramfs-tools
  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/1561643/+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 1767875] Re: /usr/bin/update-manager:ValueError:restart_icon_renderer_data_func:pkg_requires_restart:__get_candidate

[Brian Murray]

The Traceback follows:

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/UpdateManager/UpdatesAvailable.py", line 
417, in restart_icon_renderer_data_func
group_item.pkg):
  File "/usr/lib/python3/dist-packages/UpdateManager/UpdatesAvailable.py", line 
391, in pkg_requires_restart
if pkg is None or pkg.candidate is None:
  File "/usr/lib/python3/dist-packages/apt/package.py", line 1031, in 
__get_candidate
cand = self._pcache._depcache.get_candidate_ver(self._pkg)
ValueError: Object of different cache passed as argument to apt_pkg.DepCache 
method

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

Title:
  /usr/bin/update-
  
manager:ValueError:restart_icon_renderer_data_func:pkg_requires_restart:__get_candidate

Status in apt package in Ubuntu:
  New
Status in update-manager package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
update-manager.  This problem was most recently seen with package version 
1:18.04.11, the problem page at 
https://errors.ubuntu.com/problem/a2ba8d3ab5e432b3c15f172ded6d473f4c00720a 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1767875/+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 1756006] Re: FFe: Support suspend-then-hibernate

[Sebastien Bacher]

The changes got commited to upstream master, we might want to
backport/SRU in bionic?

** Changed in: gnome-settings-daemon (Ubuntu)
   Importance: Undecided => Wishlist

** Changed in: gnome-settings-daemon (Ubuntu)
   Status: New => Triaged

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

Title:
  FFe: Support suspend-then-hibernate

Status in gnome-settings-daemon package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  Suspend to hibernate is a new feature that will put the system into
  hibernate after a period of time spent in the system's supported sleep
  state.  This mode will be used on some systems that take suspend to
  idle in the future with Ubuntu 18.04.

  This feature is available in upstream systemd from these two commits.
  
https://github.com/systemd/systemd/commit/c58493c00af97146d3b6c24da9c0371978124703
  
https://github.com/systemd/systemd/commit/9aa2e409bcb70f3952b38a35f16fc080c22dd5a5
  This is accepted upstream.

  The policy needs to be made available to gnome from this commit:
  https://gitlab.gnome.org/GNOME/gnome-settings-daemon/merge_requests/9
  As of 3/15/2018 this is not yet accepted or rejected.

  The new mode is not selected by default, but that can be changed from a 
separate policy package.
  The policy for the amount of time spent in S3/S2I can be configured by a 
separate package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1756006/+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 1759836] Re: systemd-udevd consumes 100% of CPU

[ephill...@gmail.com]

I use Dell Inspiron 1545 with Intel® Core™2 Duo CPU P8700 @ 2.53GHz × 2 
If I use kernel shipped with 18.04, I get 100% cpu  problem.
If I user kernel 4.14 I get Kernel Panic on system boot up.

After change Kernel to 4.13.x (shipped with ubuntu 17.10) I get my
system back.

Know all is working and CPU is normal.

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

Title:
  systemd-udevd consumes 100% of CPU

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  The systemd-udevd proccess consumes 100% of a thread everytime, but
  i'm not noticing any difference in my computer.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 29 08:52:54 2018
  InstallationDate: Installed on 2018-03-05 (23 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304)
  MachineType: Dell Inc. Inspiron N5010
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=UUID=3c29e292-f1ae-45e1-a0ed-a82524278ce1 ro quiet splash vt.handoff=1
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 08R0GW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A12
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A12
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd01/25/2011:svnDellInc.:pnInspironN5010:pvrA12:rvnDellInc.:rn08R0GW:rvrA12:cvnDellInc.:ct8:cvrA12:
  dmi.product.name: Inspiron N5010
  dmi.product.version: A12
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1759836/+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 1760818] Re: gedit and gnome-calculator transparency/graphics corruption issue

[Gunnar Hjalmarsson]

To the extent this issue is caused by im-config setting
GTK_IM_MODULE=xim, it ought to be a leftover from ~/.xinputrc files
created in 16.04. Since the fix of bug #1605408, nothing should set
GTK_IM_MODULE=xim automatically.

I don't understand how uninstalling im-config and then reinstalling it
would make a difference. Please note that a change in the im-config
configuration needs a relogin to be effective.

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

Title:
  gedit and gnome-calculator transparency/graphics corruption issue

Status in im-config package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Invalid

Bug description:
  In a "Ubuntu" (Xorg) session on 18.04 gedit and gnome-calculator
  suffer from a graphics issue where parts of their windows hold parts
  of wallpaper or other windows' contents as background.

  See attached screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: light-themes 16.10+18.04.20180328-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  3 09:12:31 2018
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: Upgraded to bionic on 2018-02-07 (54 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1760818/+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 1764106] Re: ca-certificates fails on update in Bionic

[Launchpad Bug Tracker]

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

** Changed in: ca-certificates (Ubuntu)
   Status: New => Confirmed

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

Title:
  ca-certificates fails on update in Bionic

Status in ca-certificates package in Ubuntu:
  Confirmed

Bug description:
  Processing triggers for ca-certificates (20180409) ...
  Updating certificates in /etc/ssl/certs...
  0 added, 0 removed; done.
  Running hooks in /etc/ca-certificates/update.d...

  done.
  Updating Mono key store
  /etc/ca-certificates/update.d/mono-keystore: 10: 
/etc/ca-certificates/update.d/mono-keystore: /usr/bin/cert-sync: not found

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1764106/+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 1767491] Re: package qt5-gtk-platformtheme 5.9.4+dfsg-0ubuntu4 failed to install/upgrade: dpkg-deb --control subprocess returned error exit status 127

[Brian Murray]

*** This bug is a duplicate of bug 1764858 ***
https://bugs.launchpad.net/bugs/1764858

** This bug has been marked a duplicate of bug 1764858
   Can't update / install / delete packages due to missing libzstd.so.1

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

Title:
  package qt5-gtk-platformtheme 5.9.4+dfsg-0ubuntu4 failed to
  install/upgrade: dpkg-deb --control subprocess returned error exit
  status 127

Status in qtbase-opensource-src package in Ubuntu:
  New

Bug description:
  no detail;s I know

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: qt5-gtk-platformtheme 5.9.4+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  Date: Wed Apr 25 06:19:53 2018
  DuplicateSignature:
   package:qt5-gtk-platformtheme:5.9.4+dfsg-0ubuntu4
   Removing myspell-pt-pt (20091013-12) ...
   dpkg-deb: error while loading shared libraries: libzstd.so.1: cannot open 
shared object file: No such file or directory
   dpkg: error processing archive 
/tmp/apt-dpkg-install-xqwLmR/00-libqt5dbus5_5.9.5+dfsg-0ubuntu1_amd64.deb 
(--unpack):
dpkg-deb --control subprocess returned error exit status 127
  ErrorMessage: dpkg-deb --control subprocess returned error exit status 127
  Python3Details: /usr/bin/python3.6, Python 3.6.5rc1, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6~beta1
  SourcePackage: qtbase-opensource-src
  Title: package qt5-gtk-platformtheme 5.9.4+dfsg-0ubuntu4 failed to 
install/upgrade: dpkg-deb --control subprocess returned error exit status 127
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1767491/+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 1766872] Re: 'Enable Network' in recovery mode not working in Bionic

[Eric Desrochers]

https://www.freedesktop.org/software/systemd/man/systemctl.html

If "ignore-dependencies" is specified, then all unit dependencies are
ignored for this new job and the operation is executed immediately. If
passed, no required units of the unit passed will be pulled in, and no
ordering dependencies will be honored. This is mostly a debugging and
rescue tool for the administrator and should not be used by applications

based on the above description, --job-mode may apply in friendly-
recovery as it fit in a debugging purpose IMHO.

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

Title:
  'Enable Network' in recovery mode not working in Bionic

Status in friendly-recovery package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  This bug has been noticed after the introduction of the fix of (LP:
  #1682637) in Bionic.

  I have notice a block in Bionic when choosing 'Enable Network' option
  in recovery mode on different bionic vanilla system and I can
  reproduce all the time.

  I also asked colleagues to give it a try (for a second pair of eye on
  this) and they have the same result as me.

  Basically, when choosing 'Enable Network' it get block or lock.
  If we hit 'ctrl-c', then a shell arrive and the system has network 
connectivity.

  Here's what I find while enabling "systemd.debug-shell=1" from vtty9 :

  # pstree
  systemd-+-bash---pstree
  |-recovery-menu---network---systemctl---systemd-tty-ask
  |-systemd-journal
  

  # ps
  root 486 473 0 08:29 tty1 00:00:00 /bin/systemd-tty-ask-password-agent

  root 473 486 0 08:29 tty1 00:00:00 systemctl start dbus.socket

  root 486 283 0 08:29 tty1 00:00:00 /bin/sh /lib/recovery-
  mode/options/network

  Additionally,

  systemd-analyze blame:
  "Bootup is not yet finished. Please try again later"

  "systemctl list-jobs" is showing a 100 jobs in 'waiting' state

  The only 'running' unit is friendly-recovery.service :
  52 friendly-recovery.service start running

  The rest are all "waiting". My understanding is that "waiting" units
  will be executed only after those which are "running" are completed.
  Which explain why the "ctlr-c" allow the boot to continue.

  All the systemd special unit important at boot-up are waiting.
  7 sysinit.target start waiting
  3 basic.target   start waiting
  .

  Seems like systemd is not fully initialise in 'Recovery Mode' and
  doesn't allow any 'systemctl start' operation without
  password/passphrase request, which I suspect is hidden by the
  recovery-mode menu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/1766872/+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 1720400] Re: /usr/bin/gnome-control-center:11:update_buffers:image_get_buffers:intel_update_image_buffers:intel_update_renderbuffers:intel_prepare_render

[Sebastien Bacher]

** Changed in: gnome-control-center (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  /usr/bin/gnome-control-
  
center:11:update_buffers:image_get_buffers:intel_update_image_buffers:intel_update_renderbuffers:intel_prepare_render

Status in GTK+:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Artful:
  Fix Released

Bug description:
  Impact
  ==
  On artful every time gnome-control-center (goa panel) is used to add a google 
account, gnome-control-center crashes. This is one of the most reported crashes 
after the release.

  Test Case
  =
  - Open gnome-control-center
  - Go to online-account panel
  - Add a Google online account.
  - gnome-control-center should not crash while adding a google online account.

  Regression Potential
  ===
  This is a minimal patch applied upstream:
  https://git.gnome.org/browse/gtk+/commit/?h=gtk-3-22=1c3aff510

  Check if closing a gtk window/dialog creates no artifacts both on xorg
  and on wayland.

  Original Bug Report
  ===
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-control-center.  This problem was most recently seen with package version 
1:3.26.0-0ubuntu3, the problem page at 
https://errors.ubuntu.com/problem/f738a467f5d04cbf9ac6cf7554a28bd064e4091a 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1720400/+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 1768261] [NEW] Videos are getting stuck randomly at frames

[Rishabh Lohia]

Public bug reported:

Updated Ubuntu to 18.04 (from 17.10) and this problem started. Videos,
on VLC and on Youtube, Twitch etc. on Chrome get stuck on frames. The
video seek time also gets stuck at that frame, and then suddenly the
video skips ahead. Audio has no issues. I am assuming it's a problem
with the video drivers.

I have dual graphics cards, one integrated and one dedicated(AMD Radeon
HD 8670M). I guess my problem is similar to
https://askubuntu.com/questions/1029205/video-playback-performance-
issue-ubuntu-18-04

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Tue May  1 19:40:21 2018
DistUpgraded: 2018-04-26 21:50:03,842 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05ea]
InstallationDate: Installed on 2016-01-21 (830 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
MachineType: Dell Inc. Inspiron 5537
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=d287f35b-0011-4adf-a2f4-3626718405ff ro quiet splash radeon.modeset=1 
vt.handoff=1
SourcePackage: xorg
UpgradeStatus: Upgraded to bionic on 2018-04-26 (4 days ago)
dmi.bios.date: 04/30/2014
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A08
dmi.board.name: 04NGGW
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A08
dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd04/30/2014:svnDellInc.:pnInspiron5537:pvrA08:rvnDellInc.:rn04NGGW:rvrA00:cvnDellInc.:ct8:cvrA08:
dmi.product.family: 00
dmi.product.name: Inspiron 5537
dmi.product.version: A08
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.91+git1804271336.50426f~oibaf~b
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2~git1805010730.6487e7~oibaf~b
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2~git1805010730.6487e7~oibaf~b
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic third-party-packages 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/1768261

Title:
  Videos are getting stuck randomly at frames

Status in xorg package in Ubuntu:
  New

Bug description:
  Updated Ubuntu to 18.04 (from 17.10) and this problem started. Videos,
  on VLC and on Youtube, Twitch etc. on Chrome get stuck on frames. The
  video seek time also gets stuck at that frame, and then suddenly the
  video skips ahead. Audio has no issues. I am assuming it's a problem
  with the video drivers.

  I have dual graphics cards, one integrated and one dedicated(AMD
  Radeon HD 8670M). I guess my problem is similar to
  https://askubuntu.com/questions/1029205/video-playback-performance-
  issue-ubuntu-18-04

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Tue May  1 19:40:21 2018
  DistUpgraded: 2018-04-26 21:50:03,842 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05ea]
  InstallationDate: Installed on 2016-01-21 (830 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Dell Inc. Inspiron 5537
  

[Touch-packages] [Bug 1747119] Re: package util-linux 2.27.1-6ubuntu3.2 [modified: usr/bin/mesg usr/share/man/man1/mesg.1.gz] failed to install/upgrade: trying to overwrite '/usr/share/man/man1/mesg.1

[Phillip Susi]

It sounds like this orville-write package is broken and should probably
be deleted.


** Package changed: util-linux (Ubuntu) => orville-write (Ubuntu)

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

Title:
  package util-linux 2.27.1-6ubuntu3.2 [modified: usr/bin/mesg
  usr/share/man/man1/mesg.1.gz] failed to install/upgrade: trying to
  overwrite '/usr/share/man/man1/mesg.1.gz', which is also in package
  orville-write 2.55-3

Status in orville-write package in Ubuntu:
  New

Bug description:
  I expected updrade all packages (apt-get update; apt-get upgrade)
  Instead happened E: Sub-process /usr/bin/dpkg returned an error code (1)

  when unpack util-linux_2.27.1-6ununtu3.3_i386.deb
  rewrite mesg.1.gz that already exist in orville-write 2.55-3
  dpkg-deb: error

  Summary in the end apt-get install upgrade

  E: Sub-process /usr/bin/dpkg returned an error code (1)

  Ubuntu 16.04.3 LTS
  Release 16.04

  apt-cache policy orville-write 2.55-3
  2.55-3 500
  500 http://mirror.yandex.ru/ubuntu xenial/universe i386 Packages
  100 /var/lib/dpkg/status

  
  apt-cache policy util-linux
  At the moment - 2.27.1-6ubuntu3.2
  Need - 2.27.1-6ubuntu3.3

  2.27.1-6ubuntu3.3
   500 http://mirror.yandex.ru/ubuntu xenial-updates/main i386 Packages
  2.27.1-6ubuntu3.2
   100 /var/lib/dpkg/status
  2.27.1-6ubuntu3 500
   500 http://mirror.yandex.ru/ubuntu xenial /main i386 Packages

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: util-linux 2.27.1-6ubuntu3.2 [modified: usr/bin/mesg 
usr/share/man/man1/mesg.1.gz]
  ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98
  Uname: Linux 4.4.0-109-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  Date: Sat Feb  3 10:39:39 2018
  DpkgTerminalLog:
   Preparing to unpack .../util-linux_2.27.1-6ubuntu3.3_i386.deb ...
   Unpacking util-linux (2.27.1-6ubuntu3.3) over (2.27.1-6ubuntu3.2) ...
   dpkg: error processing archive 
/var/cache/apt/archives/util-linux_2.27.1-6ubuntu3.3_i386.deb (--unpack):
trying to overwrite '/usr/share/man/man1/mesg.1.gz', which is also in 
package orville-write 2.55-3
  DuplicateSignature:
   package:util-linux:2.27.1-6ubuntu3.2 [modified: usr/bin/mesg 
usr/share/man/man1/mesg.1.gz]
   Unpacking util-linux (2.27.1-6ubuntu3.3) over (2.27.1-6ubuntu3.2) ...
   dpkg: error processing archive 
/var/cache/apt/archives/util-linux_2.27.1-6ubuntu3.3_i386.deb (--unpack):
trying to overwrite '/usr/share/man/man1/mesg.1.gz', which is also in 
package orville-write 2.55-3
  ErrorMessage: trying to overwrite '/usr/share/man/man1/mesg.1.gz', which is 
also in package orville-write 2.55-3
  InstallationDate: Installed on 2017-01-25 (373 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release i386 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.19
  SourcePackage: util-linux
  Title: package util-linux 2.27.1-6ubuntu3.2 [modified: usr/bin/mesg 
usr/share/man/man1/mesg.1.gz] failed to install/upgrade: trying to overwrite 
'/usr/share/man/man1/mesg.1.gz', which is also in package orville-write 2.55-3
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/orville-write/+bug/1747119/+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 1751252] Re: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: ''

[Mario Limonciello]

On an Dell XPS 9360 with a 3200x1800 display it also defaults to 200%
and I reliably reproduce this bug with the 18.04 final image.

I can confirm setting the scaling to 100% in the live session resolved
the crash.

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

Title:
  [regression] ubiquity crashed in debconf.py:104 with ValueError:
  invalid literal for int() with base 10: ''

Status in glib2.0 package in Ubuntu:
  Incomplete
Status in ubiquity package in Ubuntu:
  Triaged
Status in glib2.0 source package in Bionic:
  Incomplete
Status in ubiquity source package in Bionic:
  Triaged

Bug description:
  The Ubuntu installer crashes on hiDPI machines (QHD/UHD etc). Although
  it was working some weeks/months ago, so this is a recent regression.

  ---

  https://errors.ubuntu.com/problem/82f7f7e7923663c7b2123c7f1f49af29f6ff4d77
  https://errors.ubuntu.com/problem/735a2b847e0eeab6c8a7b954de5110e43889be15

  ---

  WORKAROUND:

  1. Boot into the live session.
  2. Settings > Devices > Displays > Scale = 100%
  3. Click Apply.
  4. Proceed with installation: Click "Install Ubuntu 18.04 LTS".

  ---

  Crashed in a VM in the middle of installation. The host is Bionic up
  to date.

  From the journal
  Feb 23 12:52:27 ubuntu kernel: traps: ubiquity[2646] trap int3 
ip:7f5a76936961 sp:7ffde5090c50 error:0 in 
libglib-2.0.so.0.5400.1[7f5a768e6000+111000]
  Feb 23 12:52:41 ubuntu /install.py[6858]: Exception during installation:
  Feb 23 12:52:41 ubuntu /install.py[6858]: Traceback (most recent call last):
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 757, in 
  Feb 23 12:52:41 ubuntu /install.py[6858]: install.run()
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 135, in run
  Feb 23 12:52:41 ubuntu /install.py[6858]: self.copy_all()
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 505, in copy_all
  Feb 23 12:52:41 ubuntu /install.py[6858]: self.db.progress('SET', 10 + 
copy_progress)
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/lib/python3/dist-packages/debconf.py", line 83, in 
  Feb 23 12:52:41 ubuntu /install.py[6858]: lambda *args, **kw: 
self.command(command, *args, **kw))
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/lib/python3/dist-packages/debconf.py", line 104, in command
  Feb 23 12:52:41 ubuntu /install.py[6858]: status = int(status)
  Feb 23 12:52:41 ubuntu /install.py[6858]: ValueError: invalid literal for 
int() with base 10: ''

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: ubiquity 18.04.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CasperVersion: 1.388
  Date: Fri Feb 23 12:52:28 2018
  ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- keyboard-configuration/layoutcode=fr 
keyboard-configuration/variantcode=oss
  InterpreterPath: /usr/bin/python3.6
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222)
  ProcCmdline: /usr/bin/python3 /usr/lib/ubiquity/bin/ubiquity -d
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  Signal: 5
  SourcePackage: ubiquity
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: ubiquity crashed with signal 5 in _XEventsQueued()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1751252/+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 1767784] Re: [regression] output device not recognized anymore since update 1:8.0-0ubuntu3.9

[Hui Wang]

@Flavien,

Got it, thanks. And we have another report possible regression about
1:8.0-0ubuntu3.9, if we confirm it is a regression according to that
bug, we will revert the pulseaudio to ubuntu3.8, and if you have
something new unusual, let us know.

thanks.

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

Title:
  [regression] output device not recognized anymore since update
  1:8.0-0ubuntu3.9

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Since the update 1:8.0-0ubuntu3.8 to 1:8.0-0ubuntu3.9 , pulseaudio is
  not showing anymore my soundcard.

  The command "pacmd list-sinks" only shows a dummy output

  When running on a fresh install of ubuntu 16.04, the sound is ok.
  When updating the install with locking the following files to version 
1:8.0-0ubuntu3 the sound keeps working:
  libpulse0:amd64
  libpulse-mainloop-glib0:amd64
  libpulse-dev:amd64
  pulseaudio-module-x11:amd64
  pulseaudio-module-bluetooth:amd64
  pulseaudio-utils:amd64

  When updating to 1:8.0-0ubuntu3.9, I just get a "dummy output".

  I tried running the following versions of Ubuntu (live usb), and get the same 
issue (no need to update to get the problem)
  17.04
  17.10
  18.04

  I attached the result of command "pactl list"
  I have also generated logs during the boot but I don't know how to attach 
multiple files

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1767784/+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 1752053] Re: nvidia-390 fails to boot graphical display

[Tom]

@Benadette: I've done both several times: upgrade and fresh reinstall; same 
troubles so it does not seem to matter. I also got the pci bus errors at first, 
before the nvidia driver took it's place . Do you get to the login prompt? My 
procedure above, starting at the login prompt with Ctrl-AltF2 or F3, needed to 
be repeated a few times with a system boot after nvidia-xconfig and then rm of 
the xorg.conf with another reboot... weird stuff...
I know things will fail as soon as the login asks me password twice, 
complaining first time was wrong. If it asks password once, I am confident to 
end up to my desktop...

For what it's worth, my /etc/default/grub has now, and this seems best
so far:

GRUB_CMDLINE_LINUX_DEFAULT='acpi_osi=Linux acpi_osi=! acpi_osi="Windows
2009"'

That said, my system still suffers from 1 minute+ long shutdown times,
so I am not there yet. Other than that it seems to run... I keep you
posted...

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

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Invalid

Bug description:
  I'm using Bionic with the new 4.15 kernel. I've been using the
  nvidia-384 driver with no problem for a while.  Today I issued "sudo
  apt-get upgrade" and I was prompted to upgrade the nvidia driver to
  the nvidia-390.  After installing the driver and rebooting, I was only
  able to boot in to the tty terminal.  The graphical display failed to
  boot.  I have had similar problems with nvidia driver version 390 with
  Arch Linux and with Open Suse Tumbleweed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+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 1751252] Re: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: ''

[Eric Desrochers]

It has been brought to my attention by a community user, that the
workaround (change scale from 200% to 100%) found in comment#14 works.

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

Title:
  [regression] ubiquity crashed in debconf.py:104 with ValueError:
  invalid literal for int() with base 10: ''

Status in glib2.0 package in Ubuntu:
  Incomplete
Status in ubiquity package in Ubuntu:
  Triaged
Status in glib2.0 source package in Bionic:
  Incomplete
Status in ubiquity source package in Bionic:
  Triaged

Bug description:
  The Ubuntu installer crashes on hiDPI machines (QHD/UHD etc). Although
  it was working some weeks/months ago, so this is a recent regression.

  ---

  https://errors.ubuntu.com/problem/82f7f7e7923663c7b2123c7f1f49af29f6ff4d77
  https://errors.ubuntu.com/problem/735a2b847e0eeab6c8a7b954de5110e43889be15

  ---

  WORKAROUND:

  1. Boot into the live session.
  2. Settings > Devices > Displays > Scale = 100%
  3. Click Apply.
  4. Proceed with installation: Click "Install Ubuntu 18.04 LTS".

  ---

  Crashed in a VM in the middle of installation. The host is Bionic up
  to date.

  From the journal
  Feb 23 12:52:27 ubuntu kernel: traps: ubiquity[2646] trap int3 
ip:7f5a76936961 sp:7ffde5090c50 error:0 in 
libglib-2.0.so.0.5400.1[7f5a768e6000+111000]
  Feb 23 12:52:41 ubuntu /install.py[6858]: Exception during installation:
  Feb 23 12:52:41 ubuntu /install.py[6858]: Traceback (most recent call last):
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 757, in 
  Feb 23 12:52:41 ubuntu /install.py[6858]: install.run()
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 135, in run
  Feb 23 12:52:41 ubuntu /install.py[6858]: self.copy_all()
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 505, in copy_all
  Feb 23 12:52:41 ubuntu /install.py[6858]: self.db.progress('SET', 10 + 
copy_progress)
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/lib/python3/dist-packages/debconf.py", line 83, in 
  Feb 23 12:52:41 ubuntu /install.py[6858]: lambda *args, **kw: 
self.command(command, *args, **kw))
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/lib/python3/dist-packages/debconf.py", line 104, in command
  Feb 23 12:52:41 ubuntu /install.py[6858]: status = int(status)
  Feb 23 12:52:41 ubuntu /install.py[6858]: ValueError: invalid literal for 
int() with base 10: ''

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: ubiquity 18.04.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CasperVersion: 1.388
  Date: Fri Feb 23 12:52:28 2018
  ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- keyboard-configuration/layoutcode=fr 
keyboard-configuration/variantcode=oss
  InterpreterPath: /usr/bin/python3.6
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222)
  ProcCmdline: /usr/bin/python3 /usr/lib/ubiquity/bin/ubiquity -d
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  Signal: 5
  SourcePackage: ubiquity
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: ubiquity crashed with signal 5 in _XEventsQueued()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1751252/+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 1749686] Re: gnome-control-center crashed with SIGABRT in g_assertion_message()

[Sebastien Bacher]

Thank you for taking the time to report this bug and helping to make Ubuntu 
better. Please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?

This will help us to find and resolve the problem.

** Package changed: gnome-control-center (Ubuntu) => gstreamer1.0
(Ubuntu)

** Changed in: gstreamer1.0 (Ubuntu)
   Status: New => Incomplete

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

Title:
  gnome-control-center crashed with SIGABRT in g_assertion_message()

Status in gstreamer1.0 package in Ubuntu:
  Incomplete

Bug description:
  Crashed on trying to open users section.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.26.2-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 15 15:02:50 2018
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2018-02-15 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214)
  ProcCmdline: gnome-control-center --overview
  Signal: 6
  SourcePackage: gnome-control-center
  StacktraceTop:
   g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstvideo4linux2.so
   gst_device_provider_start () from 
/usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
   gst_device_monitor_start () from 
/usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
  Title: gnome-control-center crashed with SIGABRT in g_assertion_message()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1749686/+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 1741045] Re: Change the default resample-method to speex-float-10 in daemon.conf

[adasiko]

http://comments.gmane.org/gmane.comp.audio.pulseaudio.general/21051

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

Title:
  Change the default resample-method to speex-float-10 in daemon.conf

Status in PulseAudio:
  Confirmed
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I suggest changing the default resample-method to speex-float-10,
  instead of speex-float-1, which is the current default now, in
  /etc/pulse/daemon.conf.

  It would look like this in daemon.conf:
  resample-method = speex-float-10

  I have always done that since at least 12.04 LTS. I was not satisfied
  with the sound quality in Ubuntu compared to Windows, so I changed the
  resample-method.

  In my day-to-day usage, it gives better sound quality without
  sacrificing CPU power.

  I have not tried other resample methods. Maybe there are better
  options I don't know about.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  amr1696 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan  3 14:37:25 2018
  InstallationDate: Installed on 2017-10-02 (92 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170930)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/08/2011
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F2
  dmi.board.name: GA-78LMT-S2P
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd04/08/2011:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-S2P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-S2P:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-78LMT-S2P
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  modified.conffile..etc.pulse.daemon.conf: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2017-10-05T12:39:48.718018

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1741045/+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 1752053] Re: nvidia-390 fails to boot graphical display

[Bernadette Addison]

@Tom - I have the same exact machine.  I tried each of your steps in
order, and I still get only a black screen boot with a few PCIe Bus
Errors.  Did you perform a fresh install from scratch or was this coming
from an upgraded OS?  Does that even matter???

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

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Invalid

Bug description:
  I'm using Bionic with the new 4.15 kernel. I've been using the
  nvidia-384 driver with no problem for a while.  Today I issued "sudo
  apt-get upgrade" and I was prompted to upgrade the nvidia driver to
  the nvidia-390.  After installing the driver and rebooting, I was only
  able to boot in to the tty terminal.  The graphical display failed to
  boot.  I have had similar problems with nvidia driver version 390 with
  Arch Linux and with Open Suse Tumbleweed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+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 1749686] [NEW] gnome-control-center crashed with SIGABRT in g_assertion_message()

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Crashed on trying to open users section.

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: gnome-control-center 1:3.26.2-0ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Feb 15 15:02:50 2018
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2018-02-15 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214)
ProcCmdline: gnome-control-center --overview
Signal: 6
SourcePackage: gnome-control-center
StacktraceTop:
 g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstvideo4linux2.so
 gst_device_provider_start () from 
/usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
 gst_device_monitor_start () from 
/usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
Title: gnome-control-center crashed with SIGABRT in g_assertion_message()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

** Affects: gstreamer1.0 (Ubuntu)
 Importance: Medium
 Status: Incomplete


** Tags: amd64 apport-crash bionic third-party-packages
-- 
gnome-control-center crashed with SIGABRT in g_assertion_message()
https://bugs.launchpad.net/bugs/1749686
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to gstreamer1.0 in Ubuntu.

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

[Touch-packages] [Bug 1768235] [NEW] Ifenslave failing when bonding vlans

[Tom Verdaat]

Public bug reported:

There is a problem when running a bond on top of vlans. Running ifup
with verbose enabled shows run-parts being executed in (what seems like)
alphabetical order, but to enslave a vlan interface, run-part
/etc/network/if-pre-up.d/vlan should be executed before run-part
/etc/network/if-pre-up.d/ifenslave.

Our workaround has been to add "pre-up export IFACE=
IF_VLAN_RAW_DEVICE=; /etc/network/if-pre-up.d/vlan" to
all vlan slaves, but it would be better to fix this in the ifup scripts
themselves by reordering the run-parts.

Tested with version 1.9-3ubuntu10.4

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

** Description changed:

  There is a problem when running a bond on top of vlans. Running ifup
  with verbose enabled shows run-parts being executed in (what seems like)
  alphabetical order, but to enslave a vlan interface, run-part
  /etc/network/if-pre-up.d/vlan should be executed before run-part
  /etc/network/if-pre-up.d/ifenslave.
  
  Our workaround has been to add "pre-up export IFACE=
  IF_VLAN_RAW_DEVICE=; /etc/network/if-pre-up.d/vlan" to
  all vlan slaves, but it would be better to fix this in the ifup scripts
  themselves by reordering the run-parts.
+ 
+ Tested with version 1.9-3ubuntu10.4

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

Title:
  Ifenslave failing when bonding vlans

Status in ifupdown package in Ubuntu:
  New

Bug description:
  There is a problem when running a bond on top of vlans. Running ifup
  with verbose enabled shows run-parts being executed in (what seems
  like) alphabetical order, but to enslave a vlan interface, run-part
  /etc/network/if-pre-up.d/vlan should be executed before run-part
  /etc/network/if-pre-up.d/ifenslave.

  Our workaround has been to add "pre-up export IFACE=
  IF_VLAN_RAW_DEVICE=; /etc/network/if-pre-up.d/vlan"
  to all vlan slaves, but it would be better to fix this in the ifup
  scripts themselves by reordering the run-parts.

  Tested with version 1.9-3ubuntu10.4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1768235/+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 1768001] Re: En Thinkpad T430 con controlador BCM20702A0

[Seth Forshee]

I'm afraid that the firmware files just look to be pulled out of Windows
drivers downloaded from arbitrary download sites. I'd be hesitant to
stick those into our linux-firmware package in any case, and without a
license which allows us to redistribute the files we simply cannot
distribute them in Ubuntu.

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

Title:
  En Thinkpad T430 con controlador BCM20702A0

Status in bluez package in Ubuntu:
  Invalid
Status in linux-firmware package in Ubuntu:
  Triaged

Bug description:
  loa dispositivos se intentan conectar y se conectan/desconectan
  continuamente. Se hace inutilizable el bluetooth.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 30 13:26:49 2018
  InstallationDate: Installed on 2018-04-27 (2 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 2349I62
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=b9f1f5f8-77c7-404e-92e8-a58f7bd5fa9e ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/25/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G1ETB4WW (2.74 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2349I62
  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: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG1ETB4WW(2.74):bd09/25/2017:svnLENOVO:pn2349I62:pvrThinkPadT430:rvnLENOVO:rn2349I62:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T430
  dmi.product.name: 2349I62
  dmi.product.version: ThinkPad T430
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 74:E5:43:C5:85:87  ACL MTU: 1021:8  SCO MTU: 64:1
UP RUNNING PSCAN ISCAN 
RX bytes:1196 acl:0 sco:0 events:88 errors:0
TX bytes:4095 acl:0 sco:0 commands:86 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1768001/+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 1767784] Re: [regression] output device not recognized anymore since update 1:8.0-0ubuntu3.9

[Flavien]

@Hui,

I think there's a misunderstanding,
>From the moment I disconnected and reconnected the speakers everything is 
>working well on all the versions I tested it on.

So from my understanding
- the speakers were working although not detected
- due to the update, when speakers are not detected the output is shut down
- disconnecting and reconnecting made the speakers detected and the output 
enabled

I guess there's a hardware issue on my speakers (20 years old), I will have to 
solder new jacks on it.
The previous version was more tolerant to hardware faults, the new one might 
miss a feature for forcing enable a "disconnected" output.

I attached the alsa-info for 18.04.

** Attachment added: "alsa-info_18.04.txt"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1767784/+attachment/5131383/+files/alsa-info_18.04.txt

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

Title:
  [regression] output device not recognized anymore since update
  1:8.0-0ubuntu3.9

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Since the update 1:8.0-0ubuntu3.8 to 1:8.0-0ubuntu3.9 , pulseaudio is
  not showing anymore my soundcard.

  The command "pacmd list-sinks" only shows a dummy output

  When running on a fresh install of ubuntu 16.04, the sound is ok.
  When updating the install with locking the following files to version 
1:8.0-0ubuntu3 the sound keeps working:
  libpulse0:amd64
  libpulse-mainloop-glib0:amd64
  libpulse-dev:amd64
  pulseaudio-module-x11:amd64
  pulseaudio-module-bluetooth:amd64
  pulseaudio-utils:amd64

  When updating to 1:8.0-0ubuntu3.9, I just get a "dummy output".

  I tried running the following versions of Ubuntu (live usb), and get the same 
issue (no need to update to get the problem)
  17.04
  17.10
  18.04

  I attached the result of command "pactl list"
  I have also generated logs during the boot but I don't know how to attach 
multiple files

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1767784/+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 1767283] Re: nc doesn't support "-s IP" option

[Bug Watch Updater]

** Changed in: netcat-openbsd (Debian)
   Status: Fix Committed => Fix Released

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

Title:
  nc doesn't support "-s IP" option

Status in netcat-openbsd package in Ubuntu:
  Confirmed
Status in netcat-openbsd package in Debian:
  Fix Released

Bug description:
  Hey,

  netcat shows a usage error if i try to use the "-s" option:

  Example in Bionic:

  $ netcat -s 127.0.0.1 127.0.0.1 22 < /dev/null
  usage: nc [-46CDdFhklNnrStUuvZz] [-I length] [-i interval] [-M ttl]
     [-m minttl] [-O length] [-P proxy_username] [-p source_port]
     [-q seconds] [-s source] [-T keyword] [-V rtable] [-W recvlimit] [-w 
timeout]
     [-X proxy_protocol] [-x proxy_address[:port]][destination] [port]

  Example in Xenial:

  netcat -s 127.0.0.1 127.0.0.1 22 < /dev/null
  SSH-2.0-OpenSSH_7.2p2 Ubuntu-4ubuntu2.4

  Manpage shows that the option is still availible and should work. Both
  systems use openbsd netcat.

  $ type netcat
  netcat is hashed (/bin/netcat)
  $ ls -lah /bin/netcat
  lrwxrwxrwx 1 root root 24 Apr 25 21:56 /bin/netcat -> /etc/alternatives/netcat
  $ ls -lah /etc/alternatives/netcat
  lrwxrwxrwx 1 root root 15 Apr 25 21:56 /etc/alternatives/netcat -> 
/bin/nc.openbsd

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: netcat-openbsd 1.187-1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Fri Apr 27 13:41:20 2018
  Dependencies:
   gcc-8-base 8-20180414-1ubuntu2
   libbsd0 0.8.7-1
   libc6 2.27-3ubuntu1
   libgcc1 1:8-20180414-1ubuntu2
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: netcat-openbsd
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netcat-openbsd/+bug/1767283/+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 1768232] [NEW] i915 driver issue in Ubuntu 18.04

[Ubuntulearner]

Public bug reported:

lspci -nnk | grep -iA2 vga
00:02.0 VGA compatible controller [0300]: Intel Corporation 82945G/GZ 
Integrated Graphics Controller [8086:2772] (rev 02)
Subsystem: Hewlett-Packard Company 82945G/GZ Integrated Graphics Controller 
[103c:302a]
Kernel modules: i915, intelfb


and

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

Output of sudo lshw -c display

*-display UNCLAIMED   
   description: VGA compatible controller
   product: 82945G/GZ Integrated Graphics Controller
   vendor: Intel Corporation
   physical id: 2
   bus info: pci@:00:02.0
   version: 02
   width: 32 bits
   clock: 33MHz
   capabilities: msi pm vga_controller bus_master cap_list
   configuration: latency=0
   resources: memory:e200-e207 ioport:c000(size=8) 
memory:d000-dfff memory:e208-e20b memory:c-d

I've tried solution 1 and solution 2 but no success.

This issue occurred only after installing it, not when I choose 'Try
without Installing', I don't need to set nomodeset in that case.

Intel Graphics Update Tool shows:

Checking if Intel graphics card available...
  • checking for i915 module in /sys/module
  • i915 module found
Checking if Intel graphics card available... OK
Retrieving information from 01.org...
  • fetching https://download.01.org/gfx/ilg-config.cfg
  • saving to /home/garden/.ilg-config
  • fetched 1626 bytes
  • fetched 9818 bytes
  • fetched 12301 bytes
  • looking up [Ubuntu bionic] configuration
Retrieving information from 01.org... OK
Checking distribution... Failed

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue May  1 17:16:20 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: I just need to know a workaround
GraphicsCard:
 Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 
02) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company 82945G/GZ Integrated Graphics Controller 
[103c:302a]
InstallationDate: Installed on 2018-05-01 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: Hewlett-Packard HP dx2080 MT(KS826PA)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_IN
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=7ec4f610-9b62-44f3-867d-01abd93de14d ro quiet splash nomodeset 
vt.handoff=1
Renderer: Software
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
XorgConf:
 Section "Device"
Identifier "Intel Graphics"
Driver "intel"
Option "AccelMethod" "uxa"
 EndSection
dmi.bios.date: 11/28/2007
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: V1.03
dmi.board.name: 0AD8h
dmi.board.vendor: Board Manufacturer
dmi.chassis.asset.tag: INA8100LFY
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrV1.03:bd11/28/2007:svnHewlett-Packard:pnHPdx2080MT(KS826PA):pvr:rvnBoardManufacturer:rn0AD8h:rvr:cvnHewlett-Packard:ct3:cvr:
dmi.product.name: HP dx2080 MT(KS826PA)
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91+git1804271336.50426f~oibaf~b
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2~git1804301930.1c5f4f~oibaf~b
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2~git1804301930.1c5f4f~oibaf~b
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic third-party-packages 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/1768232

Title:
  i915 driver issue in Ubuntu 18.04

Status in xorg package in Ubuntu:
  New

Bug description:
  lspci -nnk | grep -iA2 vga
  00:02.0 VGA compatible controller [0300]: Intel Corporation 82945G/GZ 
Integrated Graphics Controller [8086:2772] (rev 02)
  Subsystem: Hewlett-Packard Company 82945G/GZ Integrated Graphics 
Controller [103c:302a]
  Kernel modules: i915, intelfb

  
  and

  xrandr 
  xrandr: Failed to get 

[Touch-packages] [Bug 1767784] Re: [regression] output device not recognized anymore since update 1:8.0-0ubuntu3.9

[Hui Wang]

@Flavien,

Got it, thanks. Could you please take some time to generate an alsa-
info.txt under 18.04, let us see if it is a regression for pulseaudio
1:8.0-0ubuntu3.9.

If the speaker and headphone can't work under 16.04, it is really an
issue.

thanks.

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

Title:
  [regression] output device not recognized anymore since update
  1:8.0-0ubuntu3.9

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Since the update 1:8.0-0ubuntu3.8 to 1:8.0-0ubuntu3.9 , pulseaudio is
  not showing anymore my soundcard.

  The command "pacmd list-sinks" only shows a dummy output

  When running on a fresh install of ubuntu 16.04, the sound is ok.
  When updating the install with locking the following files to version 
1:8.0-0ubuntu3 the sound keeps working:
  libpulse0:amd64
  libpulse-mainloop-glib0:amd64
  libpulse-dev:amd64
  pulseaudio-module-x11:amd64
  pulseaudio-module-bluetooth:amd64
  pulseaudio-utils:amd64

  When updating to 1:8.0-0ubuntu3.9, I just get a "dummy output".

  I tried running the following versions of Ubuntu (live usb), and get the same 
issue (no need to update to get the problem)
  17.04
  17.10
  18.04

  I attached the result of command "pactl list"
  I have also generated logs during the boot but I don't know how to attach 
multiple files

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1767784/+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 1635074] Re: Nepali Keyboard symbol should have zero width joiner and non joiner

[Bug Watch Updater]

** Changed in: xkeyboard-config
   Status: Confirmed => Fix Released

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

Title:
  Nepali Keyboard symbol should have zero width joiner and non joiner

Status in xkeyboard-config:
  Fix Released
Status in xkeyboard-config package in Ubuntu:
  New

Bug description:
  The symbols file located at '/usr/share/X11/xkb/symbols/np' doesnot
  seem to work for zero width joiner. The  'equal' key in line 22 should
  work as zero width joiner.

  'पर्=यो' is the output while it should be 'पर्‍यो' ।

  The workout seems to be replacing 'equal' in line 22 with '0x100200D'

  Also, the upper keys in numbers i.e. @,#,$,% etc are missing and
  should be available as is except for +,= where zero width joiner and
  non-joiner are used.

To manage notifications about this bug go to:
https://bugs.launchpad.net/xkeyboard-config/+bug/1635074/+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 1752053] Re: nvidia-390 fails to boot graphical display

[Tom]

Dell XPS15 9560 - System is now usable, after nightmare of trials and about 50 
reboots. 
If I recall correctly: Ctrl-Alt-F2 / F3 on login prompt; sudo update; sudo apt 
purge nvidia*; sudo apt install nvidia-390; 
I switched to Wayland and back, all broken again, so then again in tty at login 
prompt: sudo nvidia-xconfig (to create /etc/X11/xorg.conf) and then sudo rm 
/etc/X11/xorg.conf  No idea why to rm xorg directly after creating to make 
discrete graphics work and put Nvidia back in its cage, but it did. Tried sudo 
nvidia-settings but that does not work as system is convinced nvidia is not 
loaded...

Also for what it is worth, I added GRUB_CMDLINE_LINUX_DEFAULT="splash
acpi_rev_override=1 nouveau.runpm=0" as without the acpi override logout
takes ages...

I wont even dream about the good old days of 17.04/17.10 when I could
switch Nvidia / Prime on and off... Note to myself: avoid Nvidia in
laptops like the plague. Please... read this again, Tom, in 3 years when
a new laptop is due **no optimus/prime/Nvidia on laptops** ... !!

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

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Invalid

Bug description:
  I'm using Bionic with the new 4.15 kernel. I've been using the
  nvidia-384 driver with no problem for a while.  Today I issued "sudo
  apt-get upgrade" and I was prompted to upgrade the nvidia driver to
  the nvidia-390.  After installing the driver and rebooting, I was only
  able to boot in to the tty terminal.  The graphical display failed to
  boot.  I have had similar problems with nvidia driver version 390 with
  Arch Linux and with Open Suse Tumbleweed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+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 1751252] Re: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: ''

[Daniel van Vugt]

Correction:
Possibly worth noting is that size==4096 at scale 200%, and size==1024 at scale 
100%.

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

Title:
  [regression] ubiquity crashed in debconf.py:104 with ValueError:
  invalid literal for int() with base 10: ''

Status in glib2.0 package in Ubuntu:
  Incomplete
Status in ubiquity package in Ubuntu:
  Triaged
Status in glib2.0 source package in Bionic:
  Incomplete
Status in ubiquity source package in Bionic:
  Triaged

Bug description:
  The Ubuntu installer crashes on hiDPI machines (QHD/UHD etc). Although
  it was working some weeks/months ago, so this is a recent regression.

  ---

  https://errors.ubuntu.com/problem/82f7f7e7923663c7b2123c7f1f49af29f6ff4d77
  https://errors.ubuntu.com/problem/735a2b847e0eeab6c8a7b954de5110e43889be15

  ---

  WORKAROUND:

  1. Boot into the live session.
  2. Settings > Devices > Displays > Scale = 100%
  3. Click Apply.
  4. Proceed with installation: Click "Install Ubuntu 18.04 LTS".

  ---

  Crashed in a VM in the middle of installation. The host is Bionic up
  to date.

  From the journal
  Feb 23 12:52:27 ubuntu kernel: traps: ubiquity[2646] trap int3 
ip:7f5a76936961 sp:7ffde5090c50 error:0 in 
libglib-2.0.so.0.5400.1[7f5a768e6000+111000]
  Feb 23 12:52:41 ubuntu /install.py[6858]: Exception during installation:
  Feb 23 12:52:41 ubuntu /install.py[6858]: Traceback (most recent call last):
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 757, in 
  Feb 23 12:52:41 ubuntu /install.py[6858]: install.run()
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 135, in run
  Feb 23 12:52:41 ubuntu /install.py[6858]: self.copy_all()
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 505, in copy_all
  Feb 23 12:52:41 ubuntu /install.py[6858]: self.db.progress('SET', 10 + 
copy_progress)
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/lib/python3/dist-packages/debconf.py", line 83, in 
  Feb 23 12:52:41 ubuntu /install.py[6858]: lambda *args, **kw: 
self.command(command, *args, **kw))
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/lib/python3/dist-packages/debconf.py", line 104, in command
  Feb 23 12:52:41 ubuntu /install.py[6858]: status = int(status)
  Feb 23 12:52:41 ubuntu /install.py[6858]: ValueError: invalid literal for 
int() with base 10: ''

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: ubiquity 18.04.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CasperVersion: 1.388
  Date: Fri Feb 23 12:52:28 2018
  ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- keyboard-configuration/layoutcode=fr 
keyboard-configuration/variantcode=oss
  InterpreterPath: /usr/bin/python3.6
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222)
  ProcCmdline: /usr/bin/python3 /usr/lib/ubiquity/bin/ubiquity -d
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  Signal: 5
  SourcePackage: ubiquity
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: ubiquity crashed with signal 5 in _XEventsQueued()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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