[Touch-packages] [Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.

[Brandon O'Donnell]

tl;dr: initramfs-tools 0.130ubuntu3.5 and running update-initramfs -u
seems to have fixed it.

I have been putting up with this problem for months, thinking it was due
to a kernel update (from 4.13 to 4.15). Finally, I find this thread
today. Anyhow, here's my info:

OS: Linux Mint 19 (based on Ubuntu 18.04)
Kernel: 4.18.15-041815-generic kernel
initramfs-tools version: 0.130ubuntu3.5
LVM root and swap partitions setup during install
Symptom: waiting 30 sec during boot, with message "failed to connect to 
lvmetad" ... "falling back".

After reading previous comments, I did following:
sudo vim /etc/initramfs-tools/conf.d/resume
 .. changed from RESUME=UUID=e6675202-6e2f-4c1b-b6e6-4ffe3ef7c882
 .. to RESUME=/dev/mint-vg/swap_1
sudo update-initramfs -u
  ,, (this indicated that it would only apply to latest kernel, not older ones, 
which is what I wanted in case it borked my boot)
reboot

It now boots without the 30sec delay, but does display a message about 
"[something something] disabled by BIOS" or somesuch. This seems to override 
the mint logo that would normally display during boot if one did not press del 
to see boot messages.
Note that I only guessed that RESUME=/dev/mint-vg/swap_1 would work, since I do 
want to be able to resume from sleep, but not sure if that's the correct syntax 
for the resume file, but it is a valid symlink for my swap partition, the 
alternatives being /dev/dm-1 and /dev/mapper/mint--vg-swap_1. Resume from sleep 
still works, not sure if it'd affected by this anyhow.

Finally, I apologise if reporting on mint 19 is not welcome/appropriate
here, but it is based on ubuntu 18.04 and I did have relevant info to
contribute.

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

Title:
  Long time booting : Failed to connect to lvmetad. Falling back to
  device scanning.

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Bionic:
  Confirmed

Bug description:
  [SRU Justification]
  A regression in initramfs-tools causes it to autogenerate config in the 
initramfs saying to resume from any available swap devices, but references the 
swap device by UUID, which is not a canonical form for referring to LVM volumes 
(because of snapshotting, they are not unique).  Ubiquity also generates a file 
in /etc at install time which references the swap partition in the same way.  
Since the lvm2 initramfs hooks also only activate precisely those LVs that are 
detected as needed at boot, this adds an inappropriate 30-second boot delay to 
any system with swap on LVM, which includes any desktop system that was 
configured with LVM (but not full-disk encryption) at install time.

  [Test case]
  1. Install using the "Use LVM" option in the desktop installer.
  4. Reboot.
  5. Verify that dmesg shows a 30-second delay before mounting the root 
filesystem.
  6. Install initramfs-tools from bionic-proposed.
  7. Reboot.
  8. Verify that dmesg no longer shows a 30-second delay before mounting the 
root filesystem.
  9. Install using the bionic daily image that contains the ubiquity from 
bionic-proposed.
  10. Reboot.
  11. Verify that /etc/initramfs-tools/conf.d/resume is not present and that 
there is no delay before mounting the root filesystem.

  [Regression potential]
  This makes changes to shell scripts, and shell is a perilous language. An 
unnoticed bug could cause all initramfs generation, and thus all kernel 
installation, to fail for some users. A regression could also cause a user to 
lose hiberation support that they currently have.

  [Original description]
  After choosing "Erase disk and install ubuntu" + "Use LVM with the new Ubuntu 
installation", the
  system is very slow to reboot.

  It shows the message : "WARNING:Failed to connect to lvmetad. Falling back to 
device scanning.",
  then waits 32 seconds, then continues as it should.

  I think this is a ubiquity bug, since the d-i based installer is not affected.
   - ubuntu-18.04-desktop-amd64.iso 
(a55353d837cbf7bc006cf49eeff05ae5044e757498e30643a9199b9a25bc9a34) : affected
   - xubuntu-18.04-desktop-amd64.iso 
(7c24318d3b1de1efd584b5aea034ce1aafd2d0f06c59812d989a5fc95bf947e3) : affected
   - ubuntu-18.04-server-amd64.iso 
(a7f5c7b0cdd0e9560d78f1e47660e066353bb8a79eb78d1fc3f4ea62a07e6cbc) : not 
affected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+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 1680421] Re: Computer suspends/sleeps before login

[Jonatã Bolzan Loss]

This bug is still present on Ubuntu 18.10.

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

Title:
  Computer suspends/sleeps before login

Status in systemd:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  I am not able to login into the system because it sleeps in the boot
  process. To fix this, I need to edit (in recovery mode) the
  /etc/systemd/logind.conf to replace the following options:

  HandleLidSwitch=ignore
  HandleLidSwitchDocked=ignore

  This behaviour started in Ubuntu 14.10.

  Some other users have this issue too:
  
http://askubuntu.com/questions/829998/ubuntu-16-04-usually-suspends-before-login-and-while-logout

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: systemd 232-19
  ProcVersionSignature: Ubuntu 4.10.0-15.17-generic 4.10.5
  Uname: Linux 4.10.0-15-generic i686
  ApportVersion: 2.20.4-0ubuntu3
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Thu Apr  6 08:25:20 2017
  InstallationDate: Installed on 2017-04-06 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta i386 (20170405)
  MachineType: Positivo Positivo Mobile
  PccardctlIdent:
   Socket 0:
     no product info available
  PccardctlStatus:
   Socket 0:
     no card
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-15-generic 
root=UUID=f7649356-2952-4c27-9279-c3ab658730ad ro locale=pt_BR quiet splash 
vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/08/2006
  dmi.bios.vendor: Phoenix
  dmi.bios.version: 4.06CJ15
  dmi.board.name: M5X0V
  dmi.board.vendor: CLEVO Co.
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenix:bvr4.06CJ15:bd06/08/2006:svnPositivo:pnPositivoMobile:pvrVT6198:rvnCLEVOCo.:rnM5X0V:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: Positivo Mobile
  dmi.product.version: VT6198
  dmi.sys.vendor: Positivo
  mtime.conffile..etc.systemd.logind.conf: 2017-04-06T08:15:16.198796

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1680421/+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 1749247] Re: Spurious SEGV running inside kvm

[Launchpad Bug Tracker]

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

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

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

Title:
  Spurious SEGV running inside kvm

Status in openldap package in Ubuntu:
  Expired
Status in qemu package in Ubuntu:
  Invalid

Bug description:
  Running a continuous stream of operations against OpenLDAP slapd
  eventually causes a SEGV in liblber, in a segment of code that cannot
  fail:

   gdb /opt/symas/lib64/slapd CoreDump 
  GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.5) 7.11.1
  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 "x86_64-linux-gnu".
  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 /opt/symas/lib64/slapd...done.
  [New LWP 5472]
  [New LWP 5468]
  [New LWP 5524]
  [New LWP 5471]
  [New LWP 5469]
  [New LWP 5507]
  [New LWP 5510]
  [New LWP 5470]
  [New LWP 5506]
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  Core was generated by `/opt/symas/lib64/slapd -u root -g root -h ldap:///'.
  Program terminated with signal SIGSEGV, Segmentation fault.
  #0  0x7f4e2c9f0160 in ber_dupbv_x (dst=0x196b268, src=0x7f25f8001070, 
ctx=0x0) at /home/build/git/sold-master/openldap/libraries/liblber/memory.c:513
  513 new->bv_val[src->bv_len] = '\0';
  [Current thread is 1 (Thread 0x7f260e242700 (LWP 5472))]
  (gdb) l 500
  495 if(( new = ber_memalloc_x( sizeof(struct berval), ctx 
)) == NULL ) {
  496 return NULL;
  497 }
  498 }
  499
  500 if ( src->bv_val == NULL ) {
  501 new->bv_val = NULL;
  502 new->bv_len = 0;
  503 return new;
  504 }
  (gdb) 
  505
  506 if(( new->bv_val = ber_memalloc_x( src->bv_len + 1, ctx )) == 
NULL ) {
  507 if ( !dst )
  508 ber_memfree_x( new, ctx );
  509 return NULL;
  510 }
  511
  512 AC_MEMCPY( new->bv_val, src->bv_val, src->bv_len );
  513 new->bv_val[src->bv_len] = '\0';
  514 new->bv_len = src->bv_len;
  (gdb) p *new
  $1 = {bv_len = 0, bv_val = 0x0}
  (gdb) p *src
  $2 = {bv_len = 36, bv_val = 0x7f268ccc7bee }
  (gdb) 

  
  At line 506 we allocate some memory and check for a failure (returning NULL) 
and leave the function at line 509 if there was a failure. The allocation is 
for 37 bytes of memory and a memcpy into that memory succeeds on line 512. The 
SEGV occurs at line 513 and the pointer that was just returned from the 
allocator is NULL at this point. There are no other active threads that could 
be stomping on memory, there's no stack overrun or any other misbehavior that 
can account for it. Also, the identical test sequence completes without 
incident when running on the host OS instead of under kvm.
  (The src->bv_val pointer points to valid data at the time of the crash; it's 
just residing in a mmap'd file and that mapping isn't preserved in the 
coredump. So ignore gdb's error there.)

  Something in kvm is writing zeroes over a field of memory after we
  already checked that it was non-zero.

  This is on 
  Linux anvil1 4.4.0-112-generic #135-Ubuntu SMP Fri Jan 19 11:48:36 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  Both the host and the guest VM are on identical OS revision.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1749247/+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 1799014] Re: bold font rendeing in Java is broken in Cosmic with OpenJDK 11

[Václav Haisman]

** Attachment added: "java-bold-font-rendering2.scaled400.png"
   
https://bugs.launchpad.net/ubuntu/+source/freetype/+bug/1799014/+attachment/5203460/+files/java-bold-font-rendering2.scaled400.png

** Also affects: openjdk-lts (Ubuntu)
   Importance: Undecided
   Status: New

** Package changed: openjdk-lts (Ubuntu) => openjdk

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

Title:
  bold font rendeing in Java is broken in Cosmic with OpenJDK 11

Status in OpenJDK:
  New
Status in freetype package in Ubuntu:
  New

Bug description:
  Since update to Cosmic, I see that bold fonts in Java have broken
  rendering. See attached 400% scaled PNG for illustration. The 'r' in
  bold rendering of "Hello World" shows basically a vertical line from
  the end of the hook end. I am not entirely sure this is freetype issue
  but some sources (https://github.com/adobe/brackets/issues/14290)
  suggest there is a bug in the 2.8.1 version that Cosmic seems to
  install (libfreetype6/cosmic,now 2.8.1-2ubuntu2 amd64 [installed]).

To manage notifications about this bug go to:
https://bugs.launchpad.net/openjdk/+bug/1799014/+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 1799014] [NEW] bold font rendeing in Java is broken in Cosmic with OpenJDK 11

[Václav Haisman]

Public bug reported:

Since update to Cosmic, I see that bold fonts in Java have broken
rendering. See attached 400% scaled PNG for illustration. The 'r' in
bold rendering of "Hello World" shows basically a vertical line from the
end of the hook end. I am not entirely sure this is freetype issue but
some sources (https://github.com/adobe/brackets/issues/14290) suggest
there is a bug in the 2.8.1 version that Cosmic seems to install
(libfreetype6/cosmic,now 2.8.1-2ubuntu2 amd64 [installed]).

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


** Tags: cosmic

** Attachment added: "java-bold-font-rendering.scaled400.png"
   
https://bugs.launchpad.net/bugs/1799014/+attachment/5203459/+files/java-bold-font-rendering.scaled400.png

** Tags added: cosmic

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

Title:
  bold font rendeing in Java is broken in Cosmic with OpenJDK 11

Status in freetype package in Ubuntu:
  New

Bug description:
  Since update to Cosmic, I see that bold fonts in Java have broken
  rendering. See attached 400% scaled PNG for illustration. The 'r' in
  bold rendering of "Hello World" shows basically a vertical line from
  the end of the hook end. I am not entirely sure this is freetype issue
  but some sources (https://github.com/adobe/brackets/issues/14290)
  suggest there is a bug in the 2.8.1 version that Cosmic seems to
  install (libfreetype6/cosmic,now 2.8.1-2ubuntu2 amd64 [installed]).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/freetype/+bug/1799014/+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 1773697] Re: [USB-Audio - PX USB, playback] snd-usb-audio: probe of 2-3:1.0 failed with error -22 after kernel upgrade

[DSHR]

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

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

Title:
  [USB-Audio - PX USB, playback] snd-usb-audio: probe of 2-3:1.0 failed
  with error -22 after kernel upgrade

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Bug report has been generated on a partially working configuration.
  That allows ubuntu-bug to do more work.

  USB-Audio Connection on Bowers & Wilkens PX Bluetooth Headphones
  started working when upgrading kernel from 4.13 to 4.15 series. Then
  it suddenly stopped working again on newer kernels. The bug report has
  been generated on the latest working mainline kernel 4.15.7. All newer
  kernels have some usb quirks in place, which should fix the playback
  sample rates to 48 kHz. The quirk seems not to be working correctly
  and hinder the audio system to recognize the USB-device as a sound
  device.

  The Headphones work on kernels before 4,15.7 when manually configuring
  pulseaudio to a default samplerate of 48 kHz.

  PX Headphones are on the newest firmware level.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 4.15.7-041507-lowlatency x86_64
  AlsaInfo: Error: command ['/usr/share/alsa-base/alsa-info.sh', '--stdout', 
'--no-upload'] failed with exit code 1: mktemp: failed to create directory via 
template '/tmp/zsh-1000/alsa-info.XX': No such file or directory
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  dshr   2729 F pulseaudio
   /dev/snd/controlC1:  dshr   2729 F pulseaudio
   /dev/snd/controlC0:  dshr   2729 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sun May 27 22:21:53 2018
  InstallationDate: Installed on 2016-02-05 (841 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/zsh
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:USB successful
  Symptom_Card: PX USB - PX USB
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  dshr   2729 F pulseaudio
   /dev/snd/controlC1:  dshr   2729 F pulseaudio
   /dev/snd/controlC0:  dshr   2729 F pulseaudio
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [USB-Audio - PX USB, playback] No sound at all
  UpgradeStatus: Upgraded to bionic on 2018-05-27 (0 days ago)
  dmi.bios.date: 06/23/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N11ET33W (1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CJS00Q00
  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:bvrN11ET33W(1.09):bd06/23/2015:svnLENOVO:pn20CJS00Q00:pvrThinkPadT550:rvnLENOVO:rn20CJS00Q00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T550
  dmi.product.name: 20CJS00Q00
  dmi.product.version: ThinkPad T550
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dshr   3423 F pulseaudio
   /dev/snd/pcmC0D0c:   dshr   3423 F...m pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-02-07 (248 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180128)
  MachineType: LENOVO 4291QQ1
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/zsh
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=5501522a-496f-40cb-9b68-8ef9726b16c9 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  Tags:  cosmic
  Uname: Linux 4.18.0-10-generic x86_64
  UpgradeStatus: Upgraded to cosmic on 2018-09-30 (13 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/02/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET51WW (1.21 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4291QQ1
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset 

[Touch-packages] [Bug 1799007] Re: no sound after 18.10 upgrade

[Tessa]

other report in the wild: https://askubuntu.com/questions/1085176/sound-
device-lost-after-update-to-18-10

note that their debugging steps don't even work for me, running pacmd
just gets a complaint that the pulse daemon isn't running, even though
it looks like systemd intentionally started it in non-daemon mode:

```
$ pacmd list-cards
No PulseAudio daemon running, or not running as session daemon.
$ pstree
[...]
|-systemd-+-(sd-pam)
| |-at-spi-bus-laun-+-dbus-daemon
| | `-3*[{at-spi-bus-laun}]
| |-dbus-daemon
| |-dconf-service---2*[{dconf-service}]
| |-evolution-addre---5*[{evolution-addre}]
| |-evolution-calen---9*[{evolution-calen}]
| |-evolution-sourc---3*[{evolution-sourc}]
| |-gnome-screensav---3*[{gnome-screensav}]
| |-gnome-shell-cal---5*[{gnome-shell-cal}]
| |-goa-daemon---3*[{goa-daemon}]
| |-goa-identity-se---3*[{goa-identity-se}]
| |-gvfs-afc-volume---3*[{gvfs-afc-volume}]
| |-gvfs-goa-volume---2*[{gvfs-goa-volume}]
| |-gvfs-gphoto2-vo---2*[{gvfs-gphoto2-vo}]
| |-gvfs-mtp-volume---2*[{gvfs-mtp-volume}]
| |-gvfs-udisks2-vo---2*[{gvfs-udisks2-vo}]
| |-gvfsd-+-gvfsd-trash---2*[{gvfsd-trash}]
| |   `-2*[{gvfsd}]
| |-gvfsd-fuse---5*[{gvfsd-fuse}]
| |-gvfsd-metadata---2*[{gvfsd-metadata}]
| |-pulseaudio---{pulseaudio}
[...]
```

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

Title:
  no sound after 18.10 upgrade

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  After upgrading to 18.10, the sound in my System76 Oryx Pro no longer
  works, it no longer shows any of the audio output devices, not even
  the builtin HDMI which usually always shows.

  Not sure what happened, but this is a major regression and needs to be
  fixed. Note that this isn't the same as the bug with Timidity taking
  exclusive soundcard access
  (https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1797714) as
  I don't have any timidity packages installed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1799007/+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 1754872] Re: apt install xubuntu-desktop does not resolve dependencies properly

[Theo Linkspfeifer]

Debian's xfce4-session package only recommends light-locker, so my
suggestion in comment #26 would be an acceptable solution.

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

Title:
  apt install xubuntu-desktop does not resolve dependencies properly

Status in apt package in Ubuntu:
  Invalid
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in indicator-datetime package in Ubuntu:
  Invalid
Status in xfce4-session package in Ubuntu:
  New
Status in xubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Install `xubuntu-desktop` meta package on 18.04 LTS
  2. Login to session
  3a. Click on clock indicator on panel, select "Time & Date Settings"
  3b. Click on Gear, select "About this Computer" or "System Settings"
  3c. Click on keyboard layout indicator, select "Text Entry Settings"

  Expected results:
  xfce-oriented control center is opened

  Actual results:
  gnome-control-center is opened, but with empty window.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xubuntu-desktop 2.223
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Mar 10 21:10:11 2018
  SourcePackage: xubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1754872/+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 1799007] [NEW] no sound after 18.10 upgrade

[Tessa]

Public bug reported:

After upgrading to 18.10, the sound in my System76 Oryx Pro no longer
works, it no longer shows any of the audio output devices, not even the
builtin HDMI which usually always shows.

Not sure what happened, but this is a major regression and needs to be
fixed. Note that this isn't the same as the bug with Timidity taking
exclusive soundcard access
(https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1797714) as I
don't have any timidity packages installed.

** Affects: pulseaudio (Ubuntu)
 Importance: Undecided
 Status: 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/1799007

Title:
  no sound after 18.10 upgrade

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  After upgrading to 18.10, the sound in my System76 Oryx Pro no longer
  works, it no longer shows any of the audio output devices, not even
  the builtin HDMI which usually always shows.

  Not sure what happened, but this is a major regression and needs to be
  fixed. Note that this isn't the same as the bug with Timidity taking
  exclusive soundcard access
  (https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1797714) as
  I don't have any timidity packages installed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1799007/+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 1492430] Re: [Alienware Area-51 R2, Creative CA0132, Green Line Out, Rear] No sound at all

[Sean Clarke]

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

** This bug has been marked a duplicate of bug 1723150
   [Alienware Area-51 R2, Creative CA0132, Green Headphone Out, Front] Very low 
front headphones volume

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

Title:
  [Alienware Area-51 R2, Creative CA0132, Green Line Out, Rear] No sound
  at all

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  Description:  Ubuntu 15.04
  Release:  15.04

  
  This is a 5.1 surround sound set up. No output from any speaker. Sound 
settings configuration doesn't show proper options for this card - no channel 
info except for analog stereo and S/PDIF outputs where I would expect to see 
information on Front/Rear/Center speaker outputs.

  Output from aplay -l:

   List of PLAYBACK Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: CA0132 Analog [CA0132 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 1: CA0132 Digital [CA0132 Digital]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 1: NVidia [HDA NVidia], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 1: NVidia [HDA NVidia], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 1: NVidia [HDA NVidia], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 1: NVidia [HDA NVidia], device 9: HDMI 3 [HDMI 3]
Subdevices: 1/1
Subdevice #0: subdevice #0

  
  lspci output:

  00:1b.0 Audio device: Intel Corporation C610/X99 series chipset HD Audio 
Controller (rev 05)
Subsystem: Dell Device 064c
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: snd_hda_intel

  --
  03:00.1 Audio device: NVIDIA Corporation GM204 High Definition Audio 
Controller (rev a1)
Subsystem: NVIDIA Corporation Device 1131
Physical Slot: 6
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: snd_hda_intel

  
  Output from alsa-info.sh can be found at 
http://www.alsa-project.org/db/?f=b64f2a2d9279d19e6a0967202595956db577

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-26.28-lowlatency 3.19.8-ckt4
  Uname: Linux 3.19.0-26-lowlatency x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  keith  1905 F pulseaudio
   /dev/snd/controlC1:  keith  1905 F pulseaudio
  CurrentDesktop: XFCE
  Date: Fri Sep  4 14:24:12 2015
  InstallationDate: Installed on 2015-09-01 (3 days ago)
  InstallationMedia: Ubuntu-Studio 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  keith  1905 F pulseaudio
   /dev/snd/controlC1:  keith  1905 F pulseaudio
  Symptom_Jack: Green Line Out, Rear
  Symptom_Type: No sound at all
  Title: [Alienware Area-51 R2, Creative CA0132, Green Line Out, Rear] No sound 
at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/13/2015
  dmi.bios.vendor: Alienware
  dmi.bios.version: A03
  dmi.board.name: 0XJKKD
  dmi.board.vendor: Alienware
  dmi.board.version: A01
  dmi.chassis.type: 3
  dmi.chassis.vendor: Alienware
  dmi.modalias: 
dmi:bvnAlienware:bvrA03:bd07/13/2015:svnAlienware:pnAlienwareArea-51R2:pvr:rvnAlienware:rn0XJKKD:rvrA01:cvnAlienware:ct3:cvr:
  dmi.product.name: Alienware Area-51 R2
  dmi.sys.vendor: Alienware

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1492430/+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 1754872] Re: apt install xubuntu-desktop does not resolve dependencies properly

[Theo Linkspfeifer]

** Also affects: xfce4-session (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  apt install xubuntu-desktop does not resolve dependencies properly

Status in apt package in Ubuntu:
  Invalid
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in indicator-datetime package in Ubuntu:
  Invalid
Status in xfce4-session package in Ubuntu:
  New
Status in xubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Install `xubuntu-desktop` meta package on 18.04 LTS
  2. Login to session
  3a. Click on clock indicator on panel, select "Time & Date Settings"
  3b. Click on Gear, select "About this Computer" or "System Settings"
  3c. Click on keyboard layout indicator, select "Text Entry Settings"

  Expected results:
  xfce-oriented control center is opened

  Actual results:
  gnome-control-center is opened, but with empty window.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xubuntu-desktop 2.223
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Mar 10 21:10:11 2018
  SourcePackage: xubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1754872/+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 1723150] Re: [Alienware Area-51 R2, Creative CA0132, Green Headphone Out, Front] Very low front headphones volume

[Sean Clarke]

Also affects upstream Debian 10/Buster (4.18.0-2-amd64)

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

Title:
  [Alienware Area-51 R2, Creative CA0132, Green Headphone Out, Front]
  Very low front headphones volume

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  The sound is barely heard in Ubuntu 16.0 from the green front
  headphone jack. In a dual boot setup with Windows, on Windows, the
  sound is perfect. Standard solutions found across forums on the
  Internet do not seem to help.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-37-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aserov 1843 F pulseaudio
   /dev/snd/controlC1:  aserov 1843 F pulseaudio
  CurrentDesktop: GNOME
  Date: Thu Oct 12 17:04:24 2017
  InstallationDate: Installed on 2017-09-29 (12 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Green Headphone Out, Front
  Symptom_Type: High background noise, or volume is too low
  Title: [Alienware Area-51 R2, Creative CA0132, Green Headphone Out, Front] 
Background noise or low volume
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/11/2016
  dmi.bios.vendor: Alienware
  dmi.bios.version: A10
  dmi.board.name: 09G12C
  dmi.board.vendor: Alienware
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Alienware
  dmi.modalias: 
dmi:bvnAlienware:bvrA10:bd10/11/2016:svnAlienware:pnAlienwareArea-51R2:pvr:rvnAlienware:rn09G12C:rvrA00:cvnAlienware:ct3:cvr:
  dmi.product.name: Alienware Area-51 R2
  dmi.sys.vendor: Alienware

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1723150/+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 1723150] Re: [Alienware Area-51 R2, Creative CA0132, Green Headphone Out, Front] Very low front headphones volume

[Launchpad Bug Tracker]

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

** Changed in: alsa-driver (Ubuntu)
   Status: New => Confirmed

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

Title:
  [Alienware Area-51 R2, Creative CA0132, Green Headphone Out, Front]
  Very low front headphones volume

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  The sound is barely heard in Ubuntu 16.0 from the green front
  headphone jack. In a dual boot setup with Windows, on Windows, the
  sound is perfect. Standard solutions found across forums on the
  Internet do not seem to help.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-37-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aserov 1843 F pulseaudio
   /dev/snd/controlC1:  aserov 1843 F pulseaudio
  CurrentDesktop: GNOME
  Date: Thu Oct 12 17:04:24 2017
  InstallationDate: Installed on 2017-09-29 (12 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Green Headphone Out, Front
  Symptom_Type: High background noise, or volume is too low
  Title: [Alienware Area-51 R2, Creative CA0132, Green Headphone Out, Front] 
Background noise or low volume
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/11/2016
  dmi.bios.vendor: Alienware
  dmi.bios.version: A10
  dmi.board.name: 09G12C
  dmi.board.vendor: Alienware
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Alienware
  dmi.modalias: 
dmi:bvnAlienware:bvrA10:bd10/11/2016:svnAlienware:pnAlienwareArea-51R2:pvr:rvnAlienware:rn09G12C:rvrA00:cvnAlienware:ct3:cvr:
  dmi.product.name: Alienware Area-51 R2
  dmi.sys.vendor: Alienware

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1723150/+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 1797714] Re: [Dell Studio 1557] No sound after upgrade to Kubuntu 18.10 beta

[Tessa]

note: I'm seeing this issue even though I don't have any timidity packages 
installed. so I've opened another report to track that base issue:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1797714

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

Title:
  [Dell Studio 1557] No sound after upgrade to Kubuntu 18.10 beta

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I upgraded from Kubuntu 18.04 to 18.10 beta today, and I noticed I don't have 
sounds. The UI only shows a 'Dummy Device'. After doing a 'sudo alsa 
force-reload', KDE shows the audio device.
  When I execute alsamixer in a shell before executing the force-reload, the 
audio card is shown.

  My hardware: (from lspci)
  00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High 
Definition Audio (rev 05)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: pulseaudio 1:12.2-0ubuntu4
  Uname: Linux 4.19.0-041900rc6-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  juergen8924 F pulseaudio
   /dev/snd/controlC1:  juergen8924 F pulseaudio
  CurrentDesktop: KDE
  Date: Sat Oct 13 21:07:53 2018
  InstallationDate: Installed on 2015-02-16 (1334 days ago)
  InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 
(20121017.1)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to cosmic on 2018-10-13 (0 days ago)
  dmi.bios.date: 10/06/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A02
  dmi.board.name: 0KM426
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A02
  dmi.modalias: 
dmi:bvnDellInc.:bvrA02:bd10/06/2009:svnDellInc.:pnStudio1557:pvrA02:rvnDellInc.:rn0KM426:rvrA02:cvnDellInc.:ct8:cvrA02:
  dmi.product.name: Studio 1557
  dmi.product.version: A02
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1797714/+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 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

[sojusnik]

Still no sound, even on Ubuntu 18.10.

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

Title:
  [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Internal speaker - not sound at all
  Cable Headphonse - realy quiet disorted sound
  Bluetooth headphones - sound works fine

  On Windows 10 everything works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pmichalski   7964 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 30 22:32:10 2018
  InstallationDate: Installed on 2018-07-17 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Wbudowany dźwięk - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm2988 F pulseaudio
pmichalski   7964 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX391UA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX391UA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook S
  dmi.product.name: ZenBook S UX391UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485/+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 1770609] Re: package lvm2 2.02.176-4.1ubuntu3 failed to install/upgrade: Unterprozess installed lvm2 package post-installation script gab den Fehler-Ausgangsstatus 1 zurück

[Launchpad Bug Tracker]

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

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

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

Title:
  package lvm2 2.02.176-4.1ubuntu3 failed to install/upgrade:
  Unterprozess installed lvm2 package post-installation script gab den
  Fehler-Ausgangsstatus 1 zurück

Status in lvm2 package in Ubuntu:
  Confirmed

Bug description:
  package lvm2 2.02.176-4.1ubuntu3 failed to install/upgrade:
  Unterprozess installed lvm2 package post-installation script gab den
  Fehler-Ausgangsstatus 1 zurück

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: lvm2 2.02.176-4.1ubuntu3
  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
  Date: Fri May 11 11:40:04 2018
  ErrorMessage: Unterprozess installed lvm2 package post-installation script 
gab den Fehler-Ausgangsstatus 1 zurück
  InstallationDate: Installed on 2018-05-10 (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: lvm2
  Title: package lvm2 2.02.176-4.1ubuntu3 failed to install/upgrade: 
Unterprozess installed lvm2 package post-installation script gab den 
Fehler-Ausgangsstatus 1 zurück
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1770609/+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 1798990] [NEW] apport-gtk segfaults when pointed to invalid X window

[Tom Reynolds]

Public bug reported:

Pointing ubuntu-bug to a non-existing X window makes apport-gtk
segfault:

myrestricteduser@ubuntu1804amd64~$ DISPLAY=:1 ubuntu-bug ubiquity
Unable to init server: Could not connect: Connection refused
Unable to init server: Could not connect: Connection refused
Segmentation fault (core dumped)
myrestricteduser@ubuntu1804amd64~$

This affects at least bionic and cosmic (crash reports were uploaded).

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: apport 2.20.9-0ubuntu7.4
ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
Uname: Linux 4.15.0-36-generic x86_64
ApportLog:
 ERROR: apport (pid 7619) Sat Oct 20 20:09:19 2018: called for pid 7617, signal 
11, core limit 0, dump mode 1
 ERROR: apport (pid 7619) Sat Oct 20 20:09:19 2018: script: 
/usr/share/apport/apport-gtk, interpreted by /usr/bin/python3.6 (command line 
"/usr/bin/python3 /usr/share/apport/apport-gtk ubiquity")
 ERROR: apport (pid 7619) Sat Oct 20 20:09:19 2018: debug: session gdbus call: 
(true,)
 
 ERROR: apport (pid 7619) Sat Oct 20 20:09:23 2018: wrote report 
/var/crash/_usr_share_apport_apport-gtk.1000.crash
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
CrashReports:
 640:1000:120:7268297:2018-10-20 20:11:08.434944152 +0200:2018-10-20 
20:11:09.434944152 +0200:/var/crash/_usr_share_apport_apport-gtk.1000.crash
 664:1000:120:0:2018-10-20 20:11:18.930962176 +0200:2018-10-20 
20:11:18.930962176 +0200:/var/crash/_usr_share_apport_apport-gtk.1000.upload
CurrentDesktop: ubuntu:GNOME
Date: Sat Oct 20 20:12:03 2018
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: Upgraded to bionic on 2018-08-15 (66 days ago)

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


** Tags: amd64 apport-bug bionic

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

Title:
  apport-gtk segfaults when pointed to invalid X window

Status in apport package in Ubuntu:
  New

Bug description:
  Pointing ubuntu-bug to a non-existing X window makes apport-gtk
  segfault:

  myrestricteduser@ubuntu1804amd64~$ DISPLAY=:1 ubuntu-bug ubiquity
  Unable to init server: Could not connect: Connection refused
  Unable to init server: Could not connect: Connection refused
  Segmentation fault (core dumped)
  myrestricteduser@ubuntu1804amd64~$

  This affects at least bionic and cosmic (crash reports were uploaded).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apport 2.20.9-0ubuntu7.4
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportLog:
   ERROR: apport (pid 7619) Sat Oct 20 20:09:19 2018: called for pid 7617, 
signal 11, core limit 0, dump mode 1
   ERROR: apport (pid 7619) Sat Oct 20 20:09:19 2018: script: 
/usr/share/apport/apport-gtk, interpreted by /usr/bin/python3.6 (command line 
"/usr/bin/python3 /usr/share/apport/apport-gtk ubiquity")
   ERROR: apport (pid 7619) Sat Oct 20 20:09:19 2018: debug: session gdbus 
call: (true,)
   
   ERROR: apport (pid 7619) Sat Oct 20 20:09:23 2018: wrote report 
/var/crash/_usr_share_apport_apport-gtk.1000.crash
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CrashReports:
   640:1000:120:7268297:2018-10-20 20:11:08.434944152 +0200:2018-10-20 
20:11:09.434944152 +0200:/var/crash/_usr_share_apport_apport-gtk.1000.crash
   664:1000:120:0:2018-10-20 20:11:18.930962176 +0200:2018-10-20 
20:11:18.930962176 +0200:/var/crash/_usr_share_apport_apport-gtk.1000.upload
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 20 20:12:03 2018
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to bionic on 2018-08-15 (66 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1798990/+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 1798986] Re: package mount 2.31.1-0.4ubuntu3.2 failed to install/upgrade: pre-dependency problem - not installing mount

[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 util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1798986

Title:
  package mount 2.31.1-0.4ubuntu3.2 failed to install/upgrade: pre-
  dependency problem - not installing mount

Status in util-linux package in Ubuntu:
  New

Bug description:
  Following a successful upgrade from 17.10 to 18.04 this error was
  received.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: mount 2.31.1-0.4ubuntu3.2
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  Date: Sat Oct 20 11:09:26 2018
  ErrorMessage: pre-dependency problem - not installing mount
  InstallationDate: Installed on 2017-11-23 (331 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  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.3ubuntu0.1
  SourcePackage: util-linux
  Title: package mount 2.31.1-0.4ubuntu3.2 failed to install/upgrade: 
pre-dependency problem - not installing mount
  UpgradeStatus: Upgraded to bionic on 2018-10-20 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1798986/+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 1798986] [NEW] package mount 2.31.1-0.4ubuntu3.2 failed to install/upgrade: pre-dependency problem - not installing mount

[ereli]

Public bug reported:

Following a successful upgrade from 17.10 to 18.04 this error was
received.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: mount 2.31.1-0.4ubuntu3.2
ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
Uname: Linux 4.15.0-36-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
Date: Sat Oct 20 11:09:26 2018
ErrorMessage: pre-dependency problem - not installing mount
InstallationDate: Installed on 2017-11-23 (331 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
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.3ubuntu0.1
SourcePackage: util-linux
Title: package mount 2.31.1-0.4ubuntu3.2 failed to install/upgrade: 
pre-dependency problem - not installing mount
UpgradeStatus: Upgraded to bionic on 2018-10-20 (0 days ago)

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

Title:
  package mount 2.31.1-0.4ubuntu3.2 failed to install/upgrade: pre-
  dependency problem - not installing mount

Status in util-linux package in Ubuntu:
  New

Bug description:
  Following a successful upgrade from 17.10 to 18.04 this error was
  received.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: mount 2.31.1-0.4ubuntu3.2
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  Date: Sat Oct 20 11:09:26 2018
  ErrorMessage: pre-dependency problem - not installing mount
  InstallationDate: Installed on 2017-11-23 (331 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  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.3ubuntu0.1
  SourcePackage: util-linux
  Title: package mount 2.31.1-0.4ubuntu3.2 failed to install/upgrade: 
pre-dependency problem - not installing mount
  UpgradeStatus: Upgraded to bionic on 2018-10-20 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1798986/+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 1798562] Re: After a side by side installation, resized filesystem is corrupted

[Ubuntu Foundations Team Bug Bot]

The attachment "resize2fs: update checksums in the extent tree's
relocated block" seems to be a patch.  If it isn't, please remove the
"patch" flag from the attachment, remove the "patch" tag, and if you are
a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  After a side by side installation, resized filesystem is corrupted

Status in e2fsprogs package in Ubuntu:
  Confirmed

Bug description:
  Test Case 1:
  With e2fsprogs 1.44.4-2:

  Download this file system image:
  
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1798562/+attachment/5203159/+files/vda1b.qcow2.bz

  Run the following commands:

  bunzip2 vda1b.qcow2.bz
  qemu-img convert vda1b.qcow2 vda1b.raw
  e2fsck -f vda1b.raw
  resize2fs vda1b.raw 6200M
  e2fsck -f vda1b.raw

  e2fsck 1.44.4 (18-Aug-2018)
  Pass 1: Checking inodes, blocks, and sizes
  Inode 45746 extent block passes checks, but checksum does not match extent
  (logical block 1272, physical block 466167, len 776)
  Fix?

  
  Test Case 2 (Use case of the installer):
  1. Perform a first installation of Ubuntu
  2. Reboot into the freshly installed system and verify everything works as 
expected
  3. Do a second installation and select "Install alonogside". Keep the size 
proposed by the installer and proceed to the end of installation
  4. Reboot
  5. On boot, in the list of installed systems, select the first system 
installed on the machine
  6. Verify that it boots, you can login and it works as expected

  Actual Result
  The FS is corrupted and depending on the corruption it goes to initramfs, 
boots but cannot login, ...

  Attached is the journal of the system installed on the corrupted
  partition.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 18 10:53:57 2018
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
boot=casper only-ubiquity quiet splash ---
  InstallationDate: Installed on 2018-10-18 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1798562/+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 1246981] Re: Bluetooth mouse fails to re-connect after sleep.

[Svetlozar Argirov]

I have Bluettooth Logitec M535 mouse and have the same problem.
It will pair and I can use the mouse. But as soon as I suspend the laptop, or 
power it off it won't work anymore.
I need to go delete the mouse from the list of paired devices, turn off 
bluetooth, turn it on again and pair again so or it won't connect at all.

What solved the problem was this suggestions
https://ubuntuforums.org/showthread.php?t=2390542 from ivavis. Following
the instructions to add the mouse from the bluez console solved the
problem.

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

Title:
  Bluetooth mouse fails to re-connect after sleep.

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  This exact harware was working faultlessly in 13.04. Since re-
  installing at 13.10 the mouse consistently failes to reconnect after
  the device either hybernates or ever goes to screen saver sleep.

  I have to remove the dive and re-add it each time (which works well).

  There are other issues with the bluetooth stack as well in that I have
  not found any way to use bluetooth tethering to my mobile which again
  worked well and was easy to configure in 13.04

  Peter.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: bluetooth 4.101-0ubuntu8b1
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Fri Nov  1 16:44:37 2013
  InstallationDate: Installed on 2013-10-19 (13 days ago)
  InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  InterestingModules: bnep rfcomm btusb bluetooth
  MachineType: Dell Inc. Latitude E6530
  MarkForUpload: True
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic 
root=UUID=8283de78-9264-42bf-a8b4-25643fa1475f ro quiet splash
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/13/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 07Y85M
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd12/13/2012:svnDellInc.:pnLatitudeE6530:pvr01:rvnDellInc.:rn07Y85M:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6530
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: 20:16:D8:9C:38:E5  ACL MTU: 1021:8  SCO MTU: 64:1
UP RUNNING PSCAN ISCAN 
RX bytes:1817731 acl:117432 sco:0 events:5271 errors:0
TX bytes:37955 acl:131 sco:0 commands:5096 errors:0
  syslog:
   Nov  1 14:50:19 pnunn-Latitude-E6530 bluetoothd[1015]: Discovery session 
0x7f6489f7b450 with :1.582 activated
   Nov  1 14:50:25 pnunn-Latitude-E6530 bluetoothd[1015]: Unknown command 
complete for opcode 37
   Nov  1 14:50:28 pnunn-Latitude-E6530 bluetoothd[1015]: Stopping discovery
   Nov  1 14:50:36 pnunn-Latitude-E6530 kernel: [60934.211132] input: Microsoft 
Bluetooth Notebook Mouse 5000 as 
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/bluetooth/hci0/hci0:11/input29
   Nov  1 14:50:36 pnunn-Latitude-E6530 kernel: [60934.211646] hid-generic 
0005:045E:0700.000C: input,hidraw3: BLUETOOTH HID v1.00 Mouse [Microsoft 
Bluetooth Notebook Mouse 5000] on 20:16:d8:9c:38:e5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1246981/+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 1725840] Re: resolvconf not correctly configured after update from 17.04 to 17.10

[Cubic PPA]

** Changed in: cubic
   Status: New => Won't Fix

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

Title:
  resolvconf not correctly configured after update from 17.04 to 17.10

Status in Cubic:
  Won't Fix
Status in resolvconf package in Ubuntu:
  Confirmed

Bug description:
  After having updated my laptop from Ubuntu 17.04 to 17.10, the DNS
  lookup on my wireless network connection did not work any more.

  As it seems, the file /etc/resolv.conf was static and contained wrong
  data assigned by the NetworkManager. When I changed the file content
  manually to

nameserver 127.0.0.53

  DNS lookup worked fine. After reboot, however, I had to repeat this
  operation since NetworkManager seems to have replaced the file
  content.

  Finally, I found a solution. Running

  sudo dpkg-reconfigure resolvconf

  the file /etc/resolv.conf was replaced by the link

  /etc/resolv.conf -> ../run/resolvconf/resolv.conf

  Now, the wireless network seems to work properly.

  Hence, there must be some kind of bug during the update process from
  Ubuntu 17.04 to 17.10 that impedes resolvconf to be configured
  properly.

  Best regards,

  Artur

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: resolvconf 1.79ubuntu8
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 21 23:17:38 2017
  InstallationDate: Installed on 2013-10-18 (1463 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  PackageArchitecture: all
  SourcePackage: resolvconf
  UpgradeStatus: Upgraded to artful on 2017-10-19 (1 days ago)

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

[Pinni]

Same problem here.

-- 
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 1783757] Re: shrinking previous file systems makes them corrupted

[Theodore Ts'o]

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

** This bug has been marked a duplicate of bug 1798562
   After a side by side installation, resized filesystem is corrupted

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

Title:
  shrinking previous file systems makes them corrupted

Status in e2fsprogs package in Ubuntu:
  New

Bug description:
  Booted in UEFI mode, running test example 'Install (auto-resize) in
  Kubuntu Desktop amd64 in Bionic Daily' the previous file system was
  shrunk in order to create space for the current one. But it was
  corrupted and must be fixed.

  Workaround: sudo e2fsck -f /dev/sda2

  The same thing happened when booted  in UEFI mode, running test
  example 'Install (manual partitioning) in Kubuntu Desktop amd64 in
  Bionic Daily'

  Workaround: sudo e2fsck -f /dev/sda3

  (This current operating system's file system was fixed and made
  bootable again.)

  ---
  tester@tester-SATELLITE-PRO-C850-19W:~$ sudo parted -ls
  [sudo] password for tester: 
  Model: ATA KINGSTON SUV400S (scsi)
  Disk /dev/sda: 120GB
  Sector size (logical/physical): 512B/4096B
  Partition Table: gpt
  Disk Flags: 

  Number  Start   End SizeFile system  Name  Flags
   1  2098kB  317MB   315MB   fat32  boot, esp
   2  317MB   20,3GB  20,0GB  ext4
   3  20,3GB  45,9GB  25,6GB  ext4
   4  45,9GB  107GB   61,4GB  ext4

  
  tester@tester-SATELLITE-PRO-C850-19W:~$ sudo lsblk -fm
  NAME   FSTYPE LABEL UUID MOUNTPOINT   SIZE 
OWNER GROUP MODE
  sda 111,8G 
root  disk  brw-rw
  ├─sda1 vfat 6106-B035/boot/efi300M 
root  disk  brw-rw
  ├─sda2 ext4 d6df56de-4490-4508-beb4-8259dda193c4 18,6G 
root  disk  brw-rw
  ├─sda3 ext4 e375e0d6-e162-4136-af21-377a635761a8 /   23,9G 
root  disk  brw-rw
  └─sda4 ext4 646734a2-45bf-4000-815e-31bbafcdfd29 57,2G 
root  disk  brw-rw
  sr0  1024M 
root  cdrom brw-rw
  tester@tester-SATELLITE-PRO-C850-19W:~$ ubuntu-bug ubiquity
  ---

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Jul 26 14:01:38 2018
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed 
boot=casper maybe-ubiquity quiet splash ---
  InstallationDate: Installed on 2018-07-26 (0 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1783757/+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 1778140] Re: resize2fs hoses a filesystem on lvm after resizing

[Theodore Ts'o]

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

** This bug has been marked a duplicate of bug 1798562
   After a side by side installation, resized filesystem is corrupted

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

Title:
  resize2fs hoses a filesystem on lvm after resizing

Status in e2fsprogs package in Ubuntu:
  Confirmed

Bug description:
  Resized an ext4 filesystem on LVM. Before resizing, I confirmed
  filesystem was clean with e2fsck. After resizing, three errors were
  found.

  root@ubuntu:~# e2fsck -f /dev/ubuntu-vg/root
  e2fsck 1.44.1 (24-Mar-2018)
  Pass 1: Checking inodes, blocks, and sizes
  Inode 21110 extent block passes checks, but checksum does not match extent
(logical block 18432, physical block 503808, len 3813)
  Fix? no
  Inode 26807 extent block passes checks, but checksum does not match extent
(logical block 34816, physical block 768000, len 896)
  Fix? no
  Inode 28306 extent block passes checks, but checksum does not match extent
(logical block 30720, physical block 430080, len 5130)
  Fix? no
  Pass 2: Checking directory structure
  Pass 3: Checking directory connectivity
  Pass 4: Checking reference counts
  Pass 5: Checking group summary information

  
  This setup is currently in a virtual machine with a snapshot, so I can revert 
back and retest. The resize2fs is coming from the 18.04 Ubuntu CD.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: e2fsprogs 1.44.1-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
  CasperVersion: 1.394
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jun 21 21:03:56 2018
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: e2fsprogs
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1778140/+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 1798562] Re: After a side by side installation, resized filesystem is corrupted

[Theodore Ts'o]

Thanks for the very nice repro!I've created a fix which will be
going into the maint branch of the e2fsprogs tree.   The commit
description:

resize2fs: update checksums in the extent tree's relocated block

When shrinking an file system, and we need to relocate an inode, the
checksums in its extent tree must get updated to reflect its new inode
number.  When doing this, we need to do this *after* we update the
extent tree to reflect any blocks which need to be relocated due to
the file system shrink operation.

Otherwise, in the case where only an interior node of the extent tree
needs to get relocated, and none of the entries in that node need to
be adjusted, the checksum for that interior node is updated in the old
copy of that block, and then after the extent tree is updated to use
the new copy of that interior node, the extent tree is left with an
invalid checksum.

This is a relatively rare case, since it requires the following
conditions to be true:

*)  The metadata checksum feature must be enabled.
*)  An inode needs to be relocated.
*)  The inode needs to have an interior node.
*)  The block for that interior node needs to be relocated.
*)  None of blocks addressed by entries in that interior node needs
to be relocated.

When all of these conditions are true, though, the file system is left
with corrupted with bad checksum for the extent tree block.

Addresses-Launchpad-Bug: 1798562

Signed-off-by: Theodore Ts'o 
Reported-by: Jean-Baptiste Lallement 

I've tested e2fsprogs with this change and it fixes your repro.   I also
have a regression test in the subsequent commit which reproduces the
problem with a smaller test file system.

** Patch added: "resize2fs: update checksums in the extent tree's relocated 
block"
   
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1798562/+attachment/5203340/+files/0001-resize2fs-update-checksums-in-the-extent-tree-s-relo.patch

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

Title:
  After a side by side installation, resized filesystem is corrupted

Status in e2fsprogs package in Ubuntu:
  Confirmed

Bug description:
  Test Case 1:
  With e2fsprogs 1.44.4-2:

  Download this file system image:
  
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1798562/+attachment/5203159/+files/vda1b.qcow2.bz

  Run the following commands:

  bunzip2 vda1b.qcow2.bz
  qemu-img convert vda1b.qcow2 vda1b.raw
  e2fsck -f vda1b.raw
  resize2fs vda1b.raw 6200M
  e2fsck -f vda1b.raw

  e2fsck 1.44.4 (18-Aug-2018)
  Pass 1: Checking inodes, blocks, and sizes
  Inode 45746 extent block passes checks, but checksum does not match extent
  (logical block 1272, physical block 466167, len 776)
  Fix?

  
  Test Case 2 (Use case of the installer):
  1. Perform a first installation of Ubuntu
  2. Reboot into the freshly installed system and verify everything works as 
expected
  3. Do a second installation and select "Install alonogside". Keep the size 
proposed by the installer and proceed to the end of installation
  4. Reboot
  5. On boot, in the list of installed systems, select the first system 
installed on the machine
  6. Verify that it boots, you can login and it works as expected

  Actual Result
  The FS is corrupted and depending on the corruption it goes to initramfs, 
boots but cannot login, ...

  Attached is the journal of the system installed on the corrupted
  partition.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 18 10:53:57 2018
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
boot=casper only-ubiquity quiet splash ---
  InstallationDate: Installed on 2018-10-18 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1798562/+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 1797714] Re: [Dell Studio 1557] No sound after upgrade to Kubuntu 18.10 beta

[Dennis L.]

Update: Probably related to this report:
https://bugs.launchpad.net/ubuntu/+source/timidity/+bug/1798466

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

Title:
  [Dell Studio 1557] No sound after upgrade to Kubuntu 18.10 beta

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I upgraded from Kubuntu 18.04 to 18.10 beta today, and I noticed I don't have 
sounds. The UI only shows a 'Dummy Device'. After doing a 'sudo alsa 
force-reload', KDE shows the audio device.
  When I execute alsamixer in a shell before executing the force-reload, the 
audio card is shown.

  My hardware: (from lspci)
  00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High 
Definition Audio (rev 05)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: pulseaudio 1:12.2-0ubuntu4
  Uname: Linux 4.19.0-041900rc6-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  juergen8924 F pulseaudio
   /dev/snd/controlC1:  juergen8924 F pulseaudio
  CurrentDesktop: KDE
  Date: Sat Oct 13 21:07:53 2018
  InstallationDate: Installed on 2015-02-16 (1334 days ago)
  InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 
(20121017.1)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to cosmic on 2018-10-13 (0 days ago)
  dmi.bios.date: 10/06/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A02
  dmi.board.name: 0KM426
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A02
  dmi.modalias: 
dmi:bvnDellInc.:bvrA02:bd10/06/2009:svnDellInc.:pnStudio1557:pvrA02:rvnDellInc.:rn0KM426:rvrA02:cvnDellInc.:ct8:cvrA02:
  dmi.product.name: Studio 1557
  dmi.product.version: A02
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1797714/+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 1797714] Re: [Dell Studio 1557] No sound after upgrade to Kubuntu 18.10 beta

[Dennis L.]

Removing the timidity package resolved this for me.

But the symptoms are strange: 
Symptoms after upgrading from 18.04 to 18:10:
- aplay -l shows all audio devices as expected, including internal on-board 
sound device
- pavucontrol only shows hdmi3 output, analog sound is missing from options

Removing timidity (just out of frustration because I couldn't find any
other suggestions on this) and rebooting once brought back the analog
sound devices

Thanks to JR for mentioning this.

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

Title:
  [Dell Studio 1557] No sound after upgrade to Kubuntu 18.10 beta

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I upgraded from Kubuntu 18.04 to 18.10 beta today, and I noticed I don't have 
sounds. The UI only shows a 'Dummy Device'. After doing a 'sudo alsa 
force-reload', KDE shows the audio device.
  When I execute alsamixer in a shell before executing the force-reload, the 
audio card is shown.

  My hardware: (from lspci)
  00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High 
Definition Audio (rev 05)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: pulseaudio 1:12.2-0ubuntu4
  Uname: Linux 4.19.0-041900rc6-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  juergen8924 F pulseaudio
   /dev/snd/controlC1:  juergen8924 F pulseaudio
  CurrentDesktop: KDE
  Date: Sat Oct 13 21:07:53 2018
  InstallationDate: Installed on 2015-02-16 (1334 days ago)
  InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 
(20121017.1)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to cosmic on 2018-10-13 (0 days ago)
  dmi.bios.date: 10/06/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A02
  dmi.board.name: 0KM426
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A02
  dmi.modalias: 
dmi:bvnDellInc.:bvrA02:bd10/06/2009:svnDellInc.:pnStudio1557:pvrA02:rvnDellInc.:rn0KM426:rvrA02:cvnDellInc.:ct8:cvrA02:
  dmi.product.name: Studio 1557
  dmi.product.version: A02
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1797714/+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 1789258] Re: drm:drm_atomic_helper_wait_for_dependencies flip_done timed out

[Darko Veberic]

the solution proposed in
https://bugzilla.redhat.com/show_bug.cgi?id=1534300 and
https://bugs.freedesktop.org/show_bug.cgi?id=93782 solved the problem.
one should add

video=SVIDEO-1:d

to the kernel parameters, best in /etc/defaults/grub

** Bug watch added: Red Hat Bugzilla #1534300
   https://bugzilla.redhat.com/show_bug.cgi?id=1534300

** Bug watch added: freedesktop.org Bugzilla #93782
   https://bugs.freedesktop.org/show_bug.cgi?id=93782

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

Title:
  drm:drm_atomic_helper_wait_for_dependencies flip_done timed out

Status in libdrm package in Ubuntu:
  New

Bug description:
  every now an then the system freezes but eventually comes back to
  life. the boot process is especially slow, login greeter takes ages to
  come up and then, while there, needs some extra time to unfreeze and
  actually allow typing in the password.

  the freeze can be easily reproduced each time when switching from
  graphics to console (with ctrl-alt-fN) and back. each time the dmesg
  gets also gets appended with the error messages that can be found in
  the attached text file.

  is the workaround really to uninstall intel's xorg drivers?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libdrm-intel1 2.4.91-2
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Mon Aug 27 20:03:14 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller 
(primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Mobile GM965/GL960 Integrated Graphics Controller 
(primary) [17aa:383e]
 Subsystem: Lenovo Mobile GM965/GL960 Integrated Graphics Controller 
(secondary) [17aa:383e]
  InstallationDate: Installed on 2018-08-24 (3 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 0769BJG
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=5c1b96ff-002e-4358-bf56-8dd74e76584d ro dis_ucode_ldr
  SourcePackage: libdrm
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/11/2008
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 68ET37WW
  dmi.board.name: IEL10
  dmi.board.vendor: LENOVO
  dmi.board.version: REFERENCE
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnLENOVO:bvr68ET37WW:bd06/11/2008:svnLENOVO:pn0769BJG:pvr3000N200:rvnLENOVO:rnIEL10:rvrREFERENCE:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.family: Lenovo
  dmi.product.name: 0769BJG
  dmi.product.version: 3000 N200
  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.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  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/libdrm/+bug/1789258/+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 1789258] Re: drm:drm_atomic_helper_wait_for_dependencies flip_done timed out

[Darko Veberic]

the situation is the same after an upgrade to 18.10. the graphics
freezes for about 25 seconds each time one switches from tty to
graphical console or when lightdm/gdm starts. i am attaching the dmesg
output where several such freezes can be seen. it's all related to a
timeout in blanking the screen.

** Attachment added: "dmesg output containing several drm freezes, see 
"timeout""
   
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1789258/+attachment/5203280/+files/dmesg.txt

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

Title:
  drm:drm_atomic_helper_wait_for_dependencies flip_done timed out

Status in libdrm package in Ubuntu:
  New

Bug description:
  every now an then the system freezes but eventually comes back to
  life. the boot process is especially slow, login greeter takes ages to
  come up and then, while there, needs some extra time to unfreeze and
  actually allow typing in the password.

  the freeze can be easily reproduced each time when switching from
  graphics to console (with ctrl-alt-fN) and back. each time the dmesg
  gets also gets appended with the error messages that can be found in
  the attached text file.

  is the workaround really to uninstall intel's xorg drivers?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libdrm-intel1 2.4.91-2
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Mon Aug 27 20:03:14 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller 
(primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Mobile GM965/GL960 Integrated Graphics Controller 
(primary) [17aa:383e]
 Subsystem: Lenovo Mobile GM965/GL960 Integrated Graphics Controller 
(secondary) [17aa:383e]
  InstallationDate: Installed on 2018-08-24 (3 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 0769BJG
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=5c1b96ff-002e-4358-bf56-8dd74e76584d ro dis_ucode_ldr
  SourcePackage: libdrm
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/11/2008
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 68ET37WW
  dmi.board.name: IEL10
  dmi.board.vendor: LENOVO
  dmi.board.version: REFERENCE
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnLENOVO:bvr68ET37WW:bd06/11/2008:svnLENOVO:pn0769BJG:pvr3000N200:rvnLENOVO:rnIEL10:rvrREFERENCE:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.family: Lenovo
  dmi.product.name: 0769BJG
  dmi.product.version: 3000 N200
  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.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  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/libdrm/+bug/1789258/+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 1798954] [NEW] Some go warnings are showing up

[Vitaliy Kanev]

Public bug reported:

Steps to reproduce
--

1. Type `sudo LANG="ru_RU.UTF-8" apt install `.
2. Observe output

Expected behaviour
--

No errors

Actual behaviour


Errors are showing up. Please locate "apt regression bug.txt" attachment

System information
--

vitalkanev@fisher:~$ lsb_release -a && echo && uname -a && echo && LANG=C apt 
policy apt
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.10
Release:18.10
Codename:   cosmic

Linux fisher 4.18.0-10-generic #11-Ubuntu SMP Thu Oct 11 15:13:55 UTC
2018 x86_64 x86_64 x86_64 GNU/Linux

apt:
  Installed: 1.7.0
  Candidate: 1.7.0
  Version table:
 *** 1.7.0 500
500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: apt 1.7.0
ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
Uname: Linux 4.18.0-10-generic x86_64
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
CurrentDesktop: KDE
Date: Sat Oct 20 14:29:39 2018
InstallationDate: Installed on 2018-10-19 (0 days ago)
InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
SourcePackage: apt
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug cosmic

** Attachment added: "apt regression bug.txt"
   
https://bugs.launchpad.net/bugs/1798954/+attachment/5203276/+files/apt%20regression%20bug.txt

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

Title:
  Some go warnings are showing up

Status in apt package in Ubuntu:
  New

Bug description:
  Steps to reproduce
  --

  1. Type `sudo LANG="ru_RU.UTF-8" apt install `.
  2. Observe output

  Expected behaviour
  --

  No errors

  Actual behaviour
  

  Errors are showing up. Please locate "apt regression bug.txt"
  attachment

  System information
  --

  vitalkanev@fisher:~$ lsb_release -a && echo && uname -a && echo && LANG=C apt 
policy apt
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 18.10
  Release:18.10
  Codename:   cosmic

  Linux fisher 4.18.0-10-generic #11-Ubuntu SMP Thu Oct 11 15:13:55 UTC
  2018 x86_64 x86_64 x86_64 GNU/Linux

  apt:
Installed: 1.7.0
Candidate: 1.7.0
Version table:
   *** 1.7.0 500
  500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: apt 1.7.0
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat Oct 20 14:29:39 2018
  InstallationDate: Installed on 2018-10-19 (0 days ago)
  InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1798954/+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 124440] Re: [enhancement] Ubuntu needs a way to set mouse wheel scrolling speed

[clel]

Can someone responsible for this (is there anyone?) please update this
to reflect the current state?

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

Title:
  [enhancement] Ubuntu needs a way to set mouse wheel scrolling speed

Status in gnome-control-center:
  Unknown
Status in GTK+:
  Unknown
Status in Mir:
  Fix Released
Status in Unity:
  Invalid
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in gtk+3.0 package in Ubuntu:
  Triaged
Status in mir package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings package in Ubuntu:
  Triaged

Bug description:
  This has been driving me nuts for a while now. The scroll wheel on my
  desktop mouse (it's an MS wireless optical mouse model 1008) scrolls
  rather fast. Instead of moving a few lines, it scrolls half a page or
  more with a very gentle scroll. The bluetooth mouse I use with my
  laptop does not do this so it's probably somewhat hardware specific.
  However, I'm wondering if there is a way to modify the speed or
  sensitivity. I found an answer here from about a year ago
  (https://answers.launchpad.net/ubuntu/+question/1339) that suggests
  there isn't a way but I'm wondering if anything has changed since
  then. I've also skimmed through synaptic but didn't see anything
  promising (like gsynaptic for touchpads).

  Thanks.

  See https://answers.launchpad.net/ubuntu/+question/9200 for more
  information.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/124440/+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 1798712] Re: No sound (18.10 Cosmic)

[Dylan M Corrales]

It looks like it successfully starts after a long delay (more than 1
hour, no clue how long).

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

Title:
  No sound (18.10 Cosmic)

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Installed: 1:12.2-0ubuntu4

  I'm getting no sound on boot after upgrade.

  I tried killing the currently running pulseaudio daemon, then starting it 
with `-`, here's what happens:
  `~$ pulseaudio -
  I: [pulseaudio] main.c: setrlimit(RLIMIT_NICE, (31, 31)) failed: Operation 
not permitted
  I: [pulseaudio] main.c: setrlimit(RLIMIT_RTPRIO, (9, 9)) failed: Operation 
not permitted
  D: [pulseaudio] core-rtclock.c: Timer slack is set to 50 us.`
  Although this appears in the terminal, there's still no sound in the settings 
menu, or in pavucontrol.

  alsamixer runs just fine, showing that alsa is working.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1798712/+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 1798951] [NEW] Unattended Upgrades failing with variable reference error

[Knut Ahlers]

Public bug reported:

When running unattended-upgrades with auto-remove enabled the script
complains about a variable being referenced before assignment:

```
# unattended-upgrade -d
[...]
Removing unused kernel packages: linux-image-4.15.0-32-generic 
linux-modules-4.15.0-32-generic
Keeping 2 auto-removable package(s) because it would also remove the following 
packages which should be kept in this step: [...]
Traceback (most recent call last):
  File "/usr/bin/unattended-upgrade", line 1991, in 
sys.exit(main(options))
  File "/usr/bin/unattended-upgrade", line 1791, in main
options.verbose or options.debug, options.dry_run)
  File "/usr/bin/unattended-upgrade", line 1480, in do_auto_remove
if res:
UnboundLocalError: local variable 'res' referenced before assignment
```

This causes the apt-daily-upgrade.service to "fail" which then again
causes no updates to be installed, which means the package does not
fulfil its purpose:

```
# systemctl status apt-daily-upgrade.service
● apt-daily-upgrade.service - Daily apt upgrade and clean activities
   Loaded: loaded (/lib/systemd/system/apt-daily-upgrade.service; static; 
vendor preset: enabled)
   Active: inactive (dead) since Sat 2018-10-20 06:17:09 CEST; 6h ago
 Docs: man:apt(8)
 Main PID: 32708 (code=exited, status=0/SUCCESS)

Oct 20 06:16:00 myhost systemd[1]: Starting Daily apt upgrade and clean 
activities...
Oct 20 06:17:09 myhost apt.systemd.daily[32708]: Traceback (most recent call 
last):
Oct 20 06:17:09 myhost apt.systemd.daily[32708]:   File 
"/usr/bin/unattended-upgrade", line 1991, in 
Oct 20 06:17:09 myhost apt.systemd.daily[32708]: sys.exit(main(options))
Oct 20 06:17:09 myhost apt.systemd.daily[32708]:   File 
"/usr/bin/unattended-upgrade", line 1791, in main
Oct 20 06:17:09 myhost apt.systemd.daily[32708]: options.verbose or 
options.debug, options.dry_run)
Oct 20 06:17:09 myhost apt.systemd.daily[32708]:   File 
"/usr/bin/unattended-upgrade", line 1480, in do_auto_remove
Oct 20 06:17:09 myhost apt.systemd.daily[32708]: if res:
Oct 20 06:17:09 myhost apt.systemd.daily[32708]: UnboundLocalError: local 
variable 'res' referenced before assignment
Oct 20 06:17:09 myhost systemd[1]: Started Daily apt upgrade and clean 
activities.

# apt-get --just-print upgrade | grep ^Inst | wc -l
99
```

Mapped to the current source code of the script within the bionic branch
the error occurs in this line:

https://git.launchpad.net/ubuntu/+source/unattended-upgrades/tree
/unattended-
upgrade?h=ubuntu/bionic=165a91cd44a77a03a83c64cd3812831ba26e3a80#n1418

Used version of the package:

```
# apt-cache policy unattended-upgrades
unattended-upgrades:
  Installed: 1.1ubuntu1.18.04.5
  Candidate: 1.1ubuntu1.18.04.5
  Version table:
 *** 1.1ubuntu1.18.04.5 500
500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages
500 http://archive.ubuntu.com/ubuntu bionic-updates/main i386 Packages
500 http://mirror.hetzner.de/ubuntu/packages bionic-updates/main amd64 
Packages
500 http://mirror.hetzner.de/ubuntu/packages bionic-updates/main i386 
Packages
100 /var/lib/dpkg/status
 1.1ubuntu1 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
500 http://archive.ubuntu.com/ubuntu bionic/main i386 Packages
500 http://mirror.hetzner.de/ubuntu/packages bionic/main amd64 Packages
500 http://mirror.hetzner.de/ubuntu/packages bionic/main i386 Packages
```

** Affects: unattended-upgrades (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Unattended Upgrades failing with variable reference error

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  When running unattended-upgrades with auto-remove enabled the script
  complains about a variable being referenced before assignment:

  ```
  # unattended-upgrade -d
  [...]
  Removing unused kernel packages: linux-image-4.15.0-32-generic 
linux-modules-4.15.0-32-generic
  Keeping 2 auto-removable package(s) because it would also remove the 
following packages which should be kept in this step: [...]
  Traceback (most recent call last):
File "/usr/bin/unattended-upgrade", line 1991, in 
  sys.exit(main(options))
File "/usr/bin/unattended-upgrade", line 1791, in main
  options.verbose or options.debug, options.dry_run)
File "/usr/bin/unattended-upgrade", line 1480, in do_auto_remove
  if res:
  UnboundLocalError: local variable 'res' referenced before assignment
  ```

  This causes the apt-daily-upgrade.service to "fail" which then again
  causes no updates to be installed, which means the package does not
  fulfil its purpose:

  ```
  # systemctl status apt-daily-upgrade.service
  ● apt-daily-upgrade.service - Daily apt upgrade and clean activities
 

[Touch-packages] [Bug 1798950] [NEW] Cannot boot to a graphical desktop, black screen before login prompt.

[David Smith]

Public bug reported:

Upgraded from 18.04 to 18.10, did not boot afterwards.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: lightdm 1.28.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
Uname: Linux 4.18.0-10-generic x86_64
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
Date: Sat Oct 20 11:38:43 2018
InstallationDate: Installed on 2018-09-20 (29 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
ProcEnviron:
 LANGUAGE=en_GB:en
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: lightdm
UpgradeStatus: Upgraded to cosmic on 2018-10-19 (0 days ago)

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


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

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

Title:
  Cannot boot to a graphical desktop, black screen before login prompt.

Status in lightdm package in Ubuntu:
  New

Bug description:
  Upgraded from 18.04 to 18.10, did not boot afterwards.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: lightdm 1.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  Date: Sat Oct 20 11:38:43 2018
  InstallationDate: Installed on 2018-09-20 (29 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to cosmic on 2018-10-19 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1798950/+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 1798831] Re: 18.10 repos are missing gstreamer1.0-fluendo-mp3 package

[Brice Terzaghi]

Thanks for the clarification.

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

Title:
  18.10 repos are missing gstreamer1.0-fluendo-mp3 package

Status in gst-fluendo-mp3 package in Ubuntu:
  New
Status in ubuntu-restricted-addons package in Ubuntu:
  Confirmed

Bug description:
  The package gstreamer1.0-fluendo-mp3 isn't in the 18.10 (cosmic)
  repos, yet it still appears as a recommended package for ubuntu-
  restricted-addons (https://packages.ubuntu.com/cosmic/ubuntu-
  restricted-addons).

  I'm not sure if it's been dropped by mistake or if it's done on
  purpose (maybe because there's a better GStreamer plugin for MP3) and
  not removed from the addons recos.

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

[ccdisle]

Yes this is exactly the problem I have. Every-time I install the Nvidia-
drivers the machine won't boot up it hangs and displays

 "Failed to connect to lvmetad. Falling back to device scanning.
/dev/mapper/ubuntu--vg--root"

I even tried installing earlier drivers -340 or 361 . The problem
persists.

The only time it boots up is when I purge the Nvidia drivers.

This started soon after I upgraded to 18.10.

-- 
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 1798831] Re: 18.10 repos are missing gstreamer1.0-fluendo-mp3 package

[Hans Joachim Desserud]

Thanks for taking your time to report this issue and help making Ubuntu
better.

The gstreamer1.0-fluendo-mp3 package was indeed removed during the
Cosmic development cycle, see https://launchpad.net/ubuntu/+source/gst-
fluendo-mp3/+publishinghistory or https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=899838 for details.

So it looks like the remaining part is updating ubuntu-restricted-addons
to recommend gstreamer1.0-plugins-good instead.

** Also affects: gst-fluendo-mp3 (Ubuntu)
   Importance: Undecided
   Status: New

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

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

** Tags added: cosmic packaging

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

Title:
  18.10 repos are missing gstreamer1.0-fluendo-mp3 package

Status in gst-fluendo-mp3 package in Ubuntu:
  New
Status in ubuntu-restricted-addons package in Ubuntu:
  Confirmed

Bug description:
  The package gstreamer1.0-fluendo-mp3 isn't in the 18.10 (cosmic)
  repos, yet it still appears as a recommended package for ubuntu-
  restricted-addons (https://packages.ubuntu.com/cosmic/ubuntu-
  restricted-addons).

  I'm not sure if it's been dropped by mistake or if it's done on
  purpose (maybe because there's a better GStreamer plugin for MP3) and
  not removed from the addons recos.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-fluendo-mp3/+bug/1798831/+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 1798861] Re: Tooltips flicker constantly in GTK3 applications

[Launchpad Bug Tracker]

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

** Changed in: gtk+3.0 (Ubuntu)
   Status: New => Confirmed

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

Title:
  Tooltips flicker constantly in GTK3 applications

Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  Tooltips are flicker constantly (i.e. repeatedly shown and the hidden
  again) in GTK3 applications under XFCE.

  It is a regression in the recent GTK 3.24.

  This is the upstream report and fix:
  https://gitlab.gnome.org/GNOME/gtk/issues/1371
  
https://gitlab.gnome.org/GNOME/gtk/commit/9b7d886b723132eade2e76f3fd179cf81b7601f2

  A workaround for XFCE is as follows:

  Open Settings Editor.
  Set xsettings -> Gtk -> CursorThemeSize to 16.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libgtk-3-0 3.24.1-1ubuntu2
  Uname: Linux 4.19.0-041900rc8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  Date: Fri Oct 19 12:23:53 2018
  InstallationDate: Installed on 2017-02-01 (624 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gtk+3.0
  UpgradeStatus: Upgraded to cosmic on 2018-10-18 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1798861/+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 1450009] Re: [HP, Dell notebooks] suspends on closed lid, does not recognized external monitors/dock

[Jan Bakuwel]

This still happens on a Dell Latitude E6430 with docking station and two
external DVI monitors running Linux Mint 19 (based on Ubuntu Bionic)

ii  systemd 237-3ubuntu10.3 amd64system and service 
manager
ii  systemd-sysv 237-3ubuntu10.3 amd64system and 
service manager - SysV links

Oct 17 08:33:49 l1 systemd[1]: Started Disk Manager.
Oct 17 08:33:49 l1 systemd[1]: Reached target Graphical Interface.
Oct 17 08:33:49 l1 systemd[1]: Started Stop ureadahead data collection 45s 
after completed startup.
Oct 17 08:33:49 l1 systemd[1]: Starting Update UTMP about System Runlevel 
Changes...
Oct 17 08:33:49 l1 NetworkManager[1312]:  [1539718429.0768] manager: 
sleep: sleep requested (sleeping: no enabled: yes)
Oct 17 08:33:49 l1 NetworkManager[1312]:  [1539718429.0769] device 
(wlp3s0): state change: unavailable -> unmanaged (reason 'sleeping', 
sys-iface-state: 'managed')
Oct 17 08:33:49 l1 NetworkManager[1312]:  [1539718429.0774] manager: 
NetworkManager state is now ASLEEP
Oct 17 08:33:49 l1 systemd[1]: Reached target Sleep.
Oct 17 08:33:49 l1 systemd[1]: Starting Suspend...
Oct 17 08:33:49 l1 systemd[1]: Started Update UTMP about System Runlevel 
Changes.
Oct 17 08:33:49 l1 systemd-sleep[2197]: Suspending system...
Oct 17 08:33:49 l1 kernel: [   30.151723] PM: suspend entry (deep)

...but did NOT happen with the previous version of Linux Mint 18 (based
on Ubuntu Xenial).

ii  systemd 229-4ubuntu21.2  amd64system 
and service manager
ii  systemd-shim 9-1bzr4ubuntu1   amd64shim 
for systemd
ii  systemd-sysv 229-4ubuntu21.2  amd64
system and service manager - SysV links

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

Title:
  [HP, Dell notebooks] suspends on closed lid, does not recognized
  external monitors/dock

Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  Using systemd as init system on a HP zbook15 notebook having 2 external 
monitors connected using a docking station and starting with lid closed the 
system goes to sleep after successfully booting and starting lightdm greeter. 
Sometimes there's enough time to enter username and password but system goes to 
sleep every time after a few seconds.
  The system can be woken up and used after this happens but it will not let me 
shutdown later.

  The problem is just present in docked situation starting with closed
  lid using systemd a init system.

  If notebook is used in non-docked situation with open lid and systemd
  the problem does not occur.

  Workaround: A switch back to upstart as init system resolves the
  issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd-sysv 219-7ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  Date: Wed Apr 29 14:46:09 2015
  InstallationDate: Installed on 2015-04-27 (1 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1450009/+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 1798318] Re: After installing and deinstallig a language, it is left behind in the LANGUAGE system variable

[GunChleoc]

The following 2 files need to be fixed when a language is uninstalled:

/etc/default/locale
/home//.pam_environment

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

Title:
  After installing and deinstallig a language, it is left behind in the
  LANGUAGE system variable

Status in accountsservice package in Ubuntu:
  New

Bug description:
  After removing an installed language that was previously selected,
  it's still defined in the system. This leads to many UI elements and
  software applications picking the previously installed language if
  there is no translation available for the currently selected language.

  Steps to reproduce:

  1. Open GNOME Settings
  2. Install the Deutsch language pack
  3. Select it as your system language & locale
  4. Apply settings
  5. Pick a different language and uninstall the Deutsch language pack
  6. Reboot

  This is the result with `gd` as my usual language/locale:

  $ locale
  LANG=gd_GB.UTF-8
  LANGUAGE=gd:de_DE:en_GB:en
  LC_CTYPE="gd_GB.UTF-8"
  LC_NUMERIC=gd_GB.UTF-8
  LC_TIME=gd_GB.UTF-8
  LC_COLLATE="gd_GB.UTF-8"
  LC_MONETARY=gd_GB.UTF-8
  LC_MESSAGES="gd_GB.UTF-8"
  LC_PAPER=gd_GB.UTF-8
  LC_NAME=gd_GB.UTF-8
  LC_ADDRESS=gd_GB.UTF-8
  LC_TELEPHONE=gd_GB.UTF-8
  LC_MEASUREMENT=gd_GB.UTF-8
  LC_IDENTIFICATION=gd_GB.UTF-8
  LC_ALL=

  Notice the `LANGUAGE=gd:de_DE:en_GB:en` bit that should read
  `LANGUAGE=gd:en_GB:en` instead.

  I also noticed that after switching the language back to `gd` while
  keeping the `de` locale, part of the UI was still in `de`, including
  the "Manage Installed Languages" button, while other parts were in
  `gd`. That's probably the same bug and a symptom of the incomplete
  translation coverage for `gd`.

  I managed to manually sort of fix it by running sudo update-locale
  LANGUAGE=gd:en_GB:en as explained in
  https://askubuntu.com/questions/1083868/how-to-set-language-in-locale-
  permanently/1084062#1084062. However, it will regress every time I
  "Manage Installed Languages" -> "Apply System-wide". See attached
  screenshot for the result.

  Originally reported at https://gitlab.gnome.org/GNOME/gnome-control-
  center/issues/236

  Ubuntu version: 18.04

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

[Giovanni Panozzo]

I have the same problem on my old Dell Latitude E6400. Workaround at
post #55 fixes the problem until next reboot.

-- 
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 linux:
  Confirmed
Status in The Ubuntu Power Consumption Project:
  New
Status in bluez package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Incomplete
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/kernel/+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 798414] Re: update-initramfs should produce a more helpful error message when there isn't enough free space--or provide an automatic tool for removal of old files

[tim fiedler]

** Project changed: initramfs-tools => ubuntu

** Changed in: ubuntu
 Assignee: Raul  Benalcazar (raulbenalcazar24) => tim fiedler 
(8churchill1992)

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

Title:
  update-initramfs should produce a more helpful error message when
  there isn't enough  free space--or provide an automatic tool for
  removal of old files

Status in Ubuntu Software Center:
  Invalid
Status in Ubuntu:
  Fix Released
Status in dpkg package in Ubuntu:
  Invalid
Status in initramfs-tools package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: initramfs-tools

  When installing a kernel, /boot may become full during execution of
  post-installation script typically when update-initramfs is creating
  or updating an initrd.img file. This is resulting in kernel
  installation error.  For example:

  Setting up initramfs-tools (0.98.8ubuntu3) ...
  update-initramfs: deferring update (trigger activated)
  Processing triggers for initramfs-tools ...
  update-initramfs: Generating /boot/initrd.img-2.6.38-8-generic

  gzip: stdout: No space left on device
  E: mkinitramfs failure cpio 141 gzip 1
  update-initramfs: failed for /boot/initrd.img-2.6.38-8-generic
  dpkg: error processing initramfs-tools (--configure):
   subprocess installed post-installation script returned error exit status 1

  Ideal behavior:

  Give a more helpful error message when this unfortunate situation
  occurs so that user can fix the broken system and keep it going.

  Workaround:

  As the bug reporting system forwards user to this bug report, such 
instructions can be given here:
  https://help.ubuntu.com/community/RemoveOldKernels

To manage notifications about this bug go to:
https://bugs.launchpad.net/software-center/+bug/798414/+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 1798562] Re: After a side by side installation, resized filesystem is corrupted

[Jean-Baptiste Lallement]

** Description changed:

- Test Case:
+ Test Case 1:
+ With e2fsprogs 1.44.4-2:
+ 
+ Download this file system image:
+ 
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1798562/+attachment/5203159/+files/vda1b.qcow2.bz
+ 
+ Run the following commands:
+ 
+ bunzip2 vda1b.qcow2.bz
+ qemu-img convert vda1b.qcow2 vda1b.raw
+ e2fsck -f vda1b.raw
+ resize2fs vda1b.raw 6200M
+ e2fsck -f vda1b.raw
+ 
+ e2fsck 1.44.4 (18-Aug-2018)
+ Pass 1: Checking inodes, blocks, and sizes
+ Inode 45746 extent block passes checks, but checksum does not match extent
+ (logical block 1272, physical block 466167, len 776)
+ Fix?
+ 
+ 
+ Test Case 2 (Use case of the installer):
  1. Perform a first installation of Ubuntu
  2. Reboot into the freshly installed system and verify everything works as 
expected
  3. Do a second installation and select "Install alonogside". Keep the size 
proposed by the installer and proceed to the end of installation
- 4. Reboot 
+ 4. Reboot
  5. On boot, in the list of installed systems, select the first system 
installed on the machine
  6. Verify that it boots, you can login and it works as expected
  
  Actual Result
  The FS is corrupted and depending on the corruption it goes to initramfs, 
boots but cannot login, ...
  
  Attached is the journal of the system installed on the corrupted
  partition.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 18 10:53:57 2018
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
boot=casper only-ubiquity quiet splash ---
  InstallationDate: Installed on 2018-10-18 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  After a side by side installation, resized filesystem is corrupted

Status in e2fsprogs package in Ubuntu:
  Confirmed

Bug description:
  Test Case 1:
  With e2fsprogs 1.44.4-2:

  Download this file system image:
  
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1798562/+attachment/5203159/+files/vda1b.qcow2.bz

  Run the following commands:

  bunzip2 vda1b.qcow2.bz
  qemu-img convert vda1b.qcow2 vda1b.raw
  e2fsck -f vda1b.raw
  resize2fs vda1b.raw 6200M
  e2fsck -f vda1b.raw

  e2fsck 1.44.4 (18-Aug-2018)
  Pass 1: Checking inodes, blocks, and sizes
  Inode 45746 extent block passes checks, but checksum does not match extent
  (logical block 1272, physical block 466167, len 776)
  Fix?

  
  Test Case 2 (Use case of the installer):
  1. Perform a first installation of Ubuntu
  2. Reboot into the freshly installed system and verify everything works as 
expected
  3. Do a second installation and select "Install alonogside". Keep the size 
proposed by the installer and proceed to the end of installation
  4. Reboot
  5. On boot, in the list of installed systems, select the first system 
installed on the machine
  6. Verify that it boots, you can login and it works as expected

  Actual Result
  The FS is corrupted and depending on the corruption it goes to initramfs, 
boots but cannot login, ...

  Attached is the journal of the system installed on the corrupted
  partition.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 18 10:53:57 2018
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
boot=casper only-ubiquity quiet splash ---
  InstallationDate: Installed on 2018-10-18 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1798562/+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 1798562] Re: After a side by side installation, resized filesystem is corrupted

[Jean-Baptiste Lallement]

** Package changed: ubiquity (Ubuntu) => e2fsprogs (Ubuntu)

** Changed in: e2fsprogs (Ubuntu)
   Importance: High => Critical

** Tags added: rls-dd-incoming

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

Title:
  After a side by side installation, resized filesystem is corrupted

Status in e2fsprogs package in Ubuntu:
  Confirmed

Bug description:
  Test Case:
  1. Perform a first installation of Ubuntu
  2. Reboot into the freshly installed system and verify everything works as 
expected
  3. Do a second installation and select "Install alonogside". Keep the size 
proposed by the installer and proceed to the end of installation
  4. Reboot 
  5. On boot, in the list of installed systems, select the first system 
installed on the machine
  6. Verify that it boots, you can login and it works as expected

  Actual Result
  The FS is corrupted and depending on the corruption it goes to initramfs, 
boots but cannot login, ...

  Attached is the journal of the system installed on the corrupted
  partition.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 18 10:53:57 2018
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
boot=casper only-ubiquity quiet splash ---
  InstallationDate: Installed on 2018-10-18 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1798562/+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 1798562] [NEW] After a side by side installation, resized filesystem is corrupted

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Test Case:
1. Perform a first installation of Ubuntu
2. Reboot into the freshly installed system and verify everything works as 
expected
3. Do a second installation and select "Install alonogside". Keep the size 
proposed by the installer and proceed to the end of installation
4. Reboot 
5. On boot, in the list of installed systems, select the first system installed 
on the machine
6. Verify that it boots, you can login and it works as expected

Actual Result
The FS is corrupted and depending on the corruption it goes to initramfs, boots 
but cannot login, ...

Attached is the journal of the system installed on the corrupted
partition.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: ubiquity (not installed)
ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
Uname: Linux 4.18.0-10-generic x86_64
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 18 10:53:57 2018
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
boot=casper only-ubiquity quiet splash ---
InstallationDate: Installed on 2018-10-18 (0 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: e2fsprogs (Ubuntu)
 Importance: High
 Status: Confirmed


** Tags: amd64 apport-bug cosmic iso-testing ubiquity-18.10.12
-- 
After a side by side installation, resized filesystem is corrupted
https://bugs.launchpad.net/bugs/1798562
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to e2fsprogs 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