date:20180619

Update:
I was under the assumption that kvm/kvm_amd module was the suspect.
But I was wrong.
Reason - I tried performing '#modprobe -r kvm_amd kvm' before issuing 
'#systemctl reboot' in the reboot script and the system still halted with 
Ubuntu 18.04 kernel.

@jsalisbury -
I will keep it today and update you by tomorrow.

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

Title:
  Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD
  servers

Status in dellserver:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  New
Status in linux source package in Bionic:
  Incomplete
Status in systemd source package in Bionic:
  New

Bug description:
  Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD
  servers when under graceful reboot stress for 12hrs.

  * This hand is observed only when Onboard SATA DVD Drive is connected.

  * Not seen with Ubuntu 16.04.4 (HWE kernel v4.13)

  * Seen with Ubuntu 18.04 (4.15.0-23-generic, 4.15.0-20-generic)

  Steps:
  Setup a DellEMC AMD server with Onboard DVD Drive, install Ubuntu 18.04 and 
start reboot stress
  After a few reboots, observe that the machine hangs at "kvm: exiting hardware 
virtualization" and does not proceed with reboot cycles.

  Only physical reset helps in continuing the reboot test.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dellserver/+bug/1777674/+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 1772542] Re: after waking from sleep i get text radeon error message then return login screen

2018-06-19 Thread Chris Guiver

It's now quite a few sleep sessions since I `sudo apt remove light-
locker caffeine`

Start-Date: 2018-06-06  14:55:33
Commandline: apt remove caffeine light-locker
Requested-By: guiverc (1000)
Remove: light-locker-settings:amd64 (1.5.0-0ubuntu2), light-locker:amd64 
(1.8.0-1ubuntu1), caffeine:amd64 (2.9.4-1)
End-Date: 2018-06-06  14:55:43

in that time i've had no re-occurrences of this bug.

// once powered up; I don't think it ever occurred first few sleeps; my
normal routine is use machine during day & sleep [box] at night & bug
started appearing a number of days after cold-boot.   I've been forced
to reboot since I removed caffeine+light-locker [xfs err; so rebooted to
xfs_check etc) but so far all good :)

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

Title:
  after waking from sleep i get text radeon error message then return
  login screen

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  my box is 18.04 (was 17.10 installed; standard Ubuntu with MATE & XFCE
  desktops added)

  I sleep my XFCE (xubuntu) machine rather than turning it off at night.

  Today as with yesterday morning, instead of getting the locker-screen
  after hitting the power-button to wake my machine, i get a blank
  screen with a RADEON two-line text message top left on screen which
  appear only momentarily as screen is erased and I get the
  login/greeter screen.

  (it's happened 4-5 times, but does NOT happen every time)

  I can login fine, but my xfce session is new.

  I have grep'd for the message I see (yesterday & today), but can't
  find it as i usually recall little but the radeon word...

  sudo lshw -C video
    *-display
     description: VGA compatible controller
     product: Cedar [Radeon HD 5000/6000/7350/8350 Series]
     vendor: Advanced Micro Devices, Inc. [AMD/ATI]
     physical id: 0
     bus info: pci@:01:00.0
     version: 00
     width: 64 bits
     clock: 33MHz
     capabilities: pm pciexpress msi vga_controller bus_master cap_list rom
     configuration: driver=radeon latency=0
     resources: irq:30 memory:e000-efff memory:f7de-f7df 
ioport:dc00(size=256) memory:c-d

  guiverc@d960-ubu2:/var/crash$   pwd
  /var/crash
  guiverc@d960-ubu2:/var/crash$   ls -la
  total 35332
  drwxrwsrwt  2 rootwhoopsie 4096 May 22 09:41 .
  drwxr-xr-x 15 rootroot 4096 Nov 16  2017 ..
  -rw-r-  1 guiverc whoopsie50003 May 21 10:32 
_usr_bin_caffeine.1000.crash
  -rw-r-  1 guiverc whoopsie   880121 May 21 10:33 
_usr_bin_light-locker.1000.crash
  -rw-rw-r--  1 guiverc whoopsie0 May 21 10:33 
_usr_bin_light-locker.1000.upload
  -rw-r-  1 guiverc whoopsie 35234566 May 21 10:32 
_usr_lib_xorg_Xorg.1000.crash
  (these files are dated yesteday - i didn't find anything for today)

  extract of /var/log/auth.log  (copied from `view` hence line numbers)
  // last-night
   48 May 21 19:35:10 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate 
service 'org.bluez': timed out (service_start_timeout=25000ms)
   49 May 21 19:55:52 d960-ubu2 gnome-keyring-daemon[16355]: asked to register 
item /org/freedesktop/secrets/collection/login/1, but it's already registered
   50 May 21 19:55:52 d960-ubu2 gnome-keyring-daemon[16355]: asked to register 
item /org/freedesktop/secrets/collection/login/1, but it's already registered
   51 May 21 19:56:16 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate 
service 'org.bluez': timed out (service_start_timeout=25000ms)
  // overnight
   52 May 21 20:17:01 d960-ubu2 CRON[31879]: pam_unix(cron:session): session 
opened for user root by (uid=0)
   53 May 21 20:17:01 d960-ubu2 CRON[31879]: pam_unix(cron:session): session 
closed for user root
   54 May 21 20:34:20 d960-ubu2 gnome-keyring-daemon[16355]: asked to register 
item /org/freedesktop/secrets/collection/login/1, but it's already registered
   55 May 21 20:34:20 d960-ubu2 gnome-keyring-daemon[16355]: asked to register 
item /org/freedesktop/secrets/collection/login/1, but it's already registered
   56 May 21 20:34:45 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate 
service 'org.bluez': timed out (service_start_timeout=25000ms)
   57 May 22 09:36:23 d960-ubu2 systemd-logind[1108]: Operation 'sleep' 
finished.
   58 May 22 09:36:24 d960-ubu2 gdm-password]: pam_unix(gdm-password:session): 
session closed for user guiverc
   59 May 22 09:36:24 d960-ubu2 sudo: pam_unix(sudo:session): session closed 
for user root
   60 May 22 09:36:26 d960-ubu2 sshd[1276]: Received SIGHUP; restarting.
   61 May 22 09:36:26 d960-ubu2 sshd[1276]: Server listening on 0.0.0.0 port 22.
   62 May 22 09:36:26 d960-ubu2 sshd[1276]: Server listening on :: port 22.
   63 May 22 09:36:26 d960-ubu2 dbus-daemon[1112]: [system] Rejected send 
message, 2 matched rules; type="method_call",

[Touch-packages] [Bug 1768610] Re: leftover conffile forces GNOME is software rendering

2018-06-19 Thread Treviño

> What's the reason for doing this in preinst rather than postinst
configure?

Well, I just wanted to make sure this happened as early as possible,
since this is not related to what the package installs, I thought it was
better to handle this in preinst, so that this can be also just removed
at later times.

> What about adding a "Breaks"...

Done. Agree.

--

New debdiff. Updated MPs too.

** Patch added: "xorg.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/nux/+bug/1768610/+attachment/5154434/+files/xorg.debdiff

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

Title:
  leftover conffile forces GNOME is software rendering

Status in nux package in Ubuntu:
  Fix Released
Status in xorg package in Ubuntu:
  In Progress
Status in nux source package in Xenial:
  Fix Committed
Status in xorg source package in Xenial:
  Confirmed
Status in nux source package in Artful:
  Fix Committed
Status in xorg source package in Artful:
  Confirmed
Status in nux source package in Bionic:
  Fix Committed
Status in xorg source package in Bionic:
  In Progress

Bug description:
  [ Impact ]

  GNOME shell and other 3D programs run using software rendering after
  unity removal.

  This SRU covers only the upgrade case or if nux-tools removal happens
  after this update, for people who already upgraded and in broken state
  another SRU will follow.

  [ Test case ]

  · Install xenial
  · Upgrade to bionic or artful
    (assuming you're using a GNOME session)
  · sudo apt remove nux-tools
  · log into your session
  . From terminal:
    - printenv LIBGL_ALWAYS_SOFTWARE
    Should print nothing (and return an error)

  Same should happen if you don't remove nux-tools but you change
  `/usr/lib/nux/unity_support_test` not to run properly (replace with a script 
exiting 1), but you're running a GNOME session.

  · If running Unity session instead, ensure that
printenv LIBGL_ALWAYS_SOFTWARE equals 1 in case that you're running
in an environment with no 3d support (VMs are easy tests)

  [ Regression Potential ]

  Unity desktops with no 3d support could not start anymore.

  ===

  After an upgrade from 17.10 to 18.04, I noticed that all gnome windows
  animations were gone.  After some digging, it seems that gnome-session
  incorrectly assumes that my graphics has no acceleration, when in fact
  it does: it's a i5-2520M CPU @ 2.50GHz with Intel integrated graphics
  (i915 driver).

  I've tried this with and without the xserver-xorg-video-intel package
  (a.k.a. Intel driver) with the same behavior.

  The output of gnome-session-check-accelerated is: llvmpipe (LLVM 6.0,
  256 bits)  however the system should have DRM 2.0 capability.

  GL checks (e.g. glxinfo, glxgears produce the expected output from a
  working DRM system).

  mesa-utils and mesa-utils-extra are both installed.

  I can't find a work around.  Perhaps there is something wrong with my
  install/upgrade?

  Everything else works fine, although the graphical transitions are no
  longer smooth.  But it would be nice to restore the expected behavior.

  I have attached the log of 'journalctl -b0'

  ProblemType: BugDistroRelease: Ubuntu 18.04
  Package: gnome-session 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May  2 13:06:00 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-22 (739 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bashSourcePackage: gnome-session
  UpgradeStatus: Upgraded to bionic on 2018-04-27 (5 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nux/+bug/1768610/+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 1777730] Re: package pulseaudio-module-bluetooth 1:8.0-0ubuntu3.8 failed to install/upgrade: subprocess dpkg-split returned error exit status 2

It appears you have encountered some kind of disk error during
installation:

  dpkg-split: error: error reading 
/var/cache/apt/archives/pulseaudio-module-bluetooth_1%3a8.0-0ubuntu3.10_amd64.deb:
 Input/output error
dpkg: error processing archive 
/var/cache/apt/archives/pulseaudio-module-bluetooth_1%3a8.0-0ubuntu3.10_amd64.deb
 (--unpack):
 subprocess dpkg-split returned error exit status 2

And the kernel log confirms it. Your hard disk appears to be failing:

[ 1029.625301] ata1.00: exception Emask 0x0 SAct 0x180 SErr 0x0 action 0x0
[ 1029.625313] ata1.00: irq_stat 0x4001
[ 1029.625322] ata1.00: failed command: READ FPDMA QUEUED
[ 1029.625339] ata1.00: cmd 60/20:38:90:5c:13/00:00:0c:00:00/40 tag 7 ncq dma 
16384 in
res 41/40:20:91:5c:13/00:00:0c:00:00/00 Emask 0x409 
(media error) 
[ 1029.625347] ata1.00: status: { DRDY ERR }
[ 1029.625353] ata1.00: error: { UNC }
[ 1029.625360] ata1.00: failed command: WRITE FPDMA QUEUED
[ 1029.625376] ata1.00: cmd 61/70:40:a8:12:d4/01:00:1c:00:00/40 tag 8 ncq dma 
188416 out
res 41/04:00:91:5c:13/00:00:0c:00:00/00 Emask 0x1 
(device error)
[ 1029.625383] ata1.00: status: { DRDY ERR }
[ 1029.625389] ata1.00: error: { ABRT }
[ 1029.675831] ata1.00: configured for UDMA/100
[ 1029.675870] sd 0:0:0:0: [sda] tag#7 FAILED Result: hostbyte=DID_OK 
driverbyte=DRIVER_SENSE
[ 1029.675878] sd 0:0:0:0: [sda] tag#7 Sense Key : Medium Error [current] 
[ 1029.675884] sd 0:0:0:0: [sda] tag#7 Add. Sense: Unrecovered read error - 
auto reallocate failed
[ 1029.675892] sd 0:0:0:0: [sda] tag#7 CDB: Read(10) 28 00 0c 13 5c 90 00 00 20 
00
[ 1029.675897] print_req_error: I/O error, dev sda, sector 202595473
[ 1029.675970] ata1: EH complete
[ 1032.312563] ata1.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
[ 1032.312575] ata1.00: irq_stat 0x4008
[ 1032.312584] ata1.00: failed command: READ FPDMA QUEUED
[ 1032.312602] ata1.00: cmd 60/08:80:90:5c:13/00:00:0c:00:00/40 tag 16 ncq dma 
4096 in
res 41/40:08:91:5c:13/00:00:0c:00:00/00 Emask 0x409 
(media error) 
[ 1032.312610] ata1.00: status: { DRDY ERR }
[ 1032.312616] ata1.00: error: { UNC }
[ 1032.316408] ata1.00: configured for UDMA/100
[ 1032.316448] sd 0:0:0:0: [sda] tag#16 FAILED Result: hostbyte=DID_OK 
driverbyte=DRIVER_SENSE
[ 1032.316466] sd 0:0:0:0: [sda] tag#16 Sense Key : Medium Error [current] 
[ 1032.316480] sd 0:0:0:0: [sda] tag#16 Add. Sense: Unrecovered read error - 
auto reallocate failed
[ 1032.316490] sd 0:0:0:0: [sda] tag#16 CDB: Read(10) 28 00 0c 13 5c 90 00 00 
08 00
[ 1032.316496] print_req_error: I/O error, dev sda, sector 202595473
[ 1032.316574] ata1: EH complete
[ 1039.300513] ata1.00: exception Emask 0x0 SAct 0x800 SErr 0x0 action 0x0
[ 1039.300525] ata1.00: irq_stat 0x4008
[ 1039.300533] ata1.00: failed command: READ FPDMA QUEUED
[ 1039.300551] ata1.00: cmd 60/08:58:90:5c:13/00:00:0c:00:00/40 tag 11 ncq dma 
4096 in
res 41/40:08:91:5c:13/00:00:0c:00:00/00 Emask 0x409 
(media error) 
[ 1039.300560] ata1.00: status: { DRDY ERR }
[ 1039.300565] ata1.00: error: { UNC }
[ 1039.304569] ata1.00: configured for UDMA/100
[ 1039.304605] sd 0:0:0:0: [sda] tag#11 FAILED Result: hostbyte=DID_OK 
driverbyte=DRIVER_SENSE
[ 1039.304613] sd 0:0:0:0: [sda] tag#11 Sense Key : Medium Error [current] 
[ 1039.304619] sd 0:0:0:0: [sda] tag#11 Add. Sense: Unrecovered read error - 
auto reallocate failed
[ 1039.304627] sd 0:0:0:0: [sda] tag#11 CDB: Read(10) 28 00 0c 13 5c 90 00 00 
08 00
[ 1039.304631] print_req_error: I/O error, dev sda, sector 202595473
[ 1039.304691] ata1: EH complete

So this is not a software problem, unless it's a kernel bug. But I think
most likely you have a hardware failure.

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

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

Title:
  package pulseaudio-module-bluetooth 1:8.0-0ubuntu3.8 failed to
  install/upgrade: subprocess dpkg-split returned error exit status 2

Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  tried to install nvidia driver. couldn't. several different errors
  come up

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio-module-bluetooth 1:8.0-0ubuntu3.8
  Uname: Linux 4.13.0-39-generic x86_64
  Architecture: amd64
  Date: Tue Jun 19 16:52:05 2018
  DpkgHistoryLog:
   Start-Date: 2018-06-19  16:51:58
   Commandline: apt-get -f install
   Requested-By: thakur (1000)
   Upgrade: ibus:amd64 (1.5.11-1ubuntu2, 1.5.11-1ubuntu2.1), 
pulseaudio-module-bluetooth:amd64 (1:8.0-0ubuntu3.8, 1:8.0-0ubuntu3.10), 
gir1.2-ibus-1.0:amd64 (1.5.11-1ubuntu2, 1.5.11-1ubuntu2.1)
  ErrorMessage: subprocess dpkg-split returned error exit status 2
  SourcePackage: pulseaudio
  Title: package pulseaudio-module-bluetooth 1:8.0-0ubuntu3.8 failed to 
install/upgrade:

[Touch-packages] [Bug 1777633] Re: Xorg Out of Range with VGA native resolution

"out of range" doesn't mean it's the wrong resolution. It means that
you've specified some frequencies/values that the monitor can't support,
or isn't meant to support in case they cause damage.

It's unclear to me if this is a bug in Xorg, a faulty monitor, or just a
misunderstanding.



** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

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

Title:
  Xorg Out of Range with VGA native resolution

Status in xorg-server package in Ubuntu:
  New

Bug description:
  This bug is related to Bug 1777621 with 17.10

  pg@pg-desktop:~$ xrandr 
  Screen 0: minimum 320 x 200, current 2304 x 1024, maximum 8192 x 8192
  VGA-1 connected primary 1024x768+1280+0 (normal left inverted right x axis y 
axis) 0mm x 0mm
 1024x768  60.00* 
 800x600   60.3256.25  
 848x480   60.00  
 640x480   59.94  
  HDMI-1 connected 1280x1024+0+0 (normal left inverted right x axis y axis) 
376mm x 301mm
 1280x1024 60.02*+  76.0075.0272.05  
 1152x864  75.00  
 1024x768  75.0370.0760.00  
 832x624   74.55  
 800x600   72.1975.0060.32  
 640x480   75.0072.8166.6759.94  
 720x400   70.08  
 640x350   70.07  
  HDMI-2 disconnected (normal left inverted right x axis y axis)
1280x1024_60.00 (0x120) 109.000MHz -HSync +VSync
  h: width  1280 start 1368 end 1496 total 1712 skew0 clock  
63.67KHz
  v: height 1024 start 1027 end 1034 total 1063   clock  59.89Hz
  pg@pg-desktop:~$ xrandr --newmode 1280x1024_40.00   69.75  1280 1336 1472 
1664  1024 1025 1028 1048  -HSync +Vsync
  pg@pg-desktop:~$ xrandr --verbose --addmode VGA-1 1280x1024_40.00
  pg@pg-desktop:~$ xrandr --verbose --output VGA-1 --mode 1280x1024_40.00
  screen 0: 2560x1024 677x271 mm  95.98dpi
  crtc 0: 1280x1024_40.00  40.00 +1280+0 "VGA-1"
  pg@pg-desktop:~$ 
  =>
  VGA-1 Out of Range!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 19 14:37:03 2018
  DistUpgraded: 2018-06-19 13:58:44,011 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0402] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: ASRock Incorporation Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [1849:0402]
  InstallationDate: Installed on 2017-09-28 (264 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=32b56d21-8cb0-4fcd-8f39-bdee0a192558 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to bionic on 2018-06-19 (0 days ago)
  dmi.bios.date: 12/06/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.10
  dmi.board.name: B85M
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.10:bd12/06/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB85M:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Sun Jun 17 11:33:00 2018
  xserver.configfile: default
  xserver.errors:

[Touch-packages] [Bug 1777634] Re: no more than 1 GATT descriptor allowed

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:

apport-collect 1777634

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.

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

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

Title:
  no more than 1 GATT descriptor allowed

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  By running the example-gatt-server and example-gatt-advertising,
  it was impossible to get more than one Descriptor per characteristic.
  if i comment one i can see the other in the test characteristic.
  but if i set both, it just act like no descriptor available.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1777634/+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 1777634] Re: no more than 1 GATT descriptor allowed

Also, please report the bug to upstream here:

https://bugzilla.kernel.org/enter_bug.cgi?product=Drivers=Bluetooth

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

Title:
  no more than 1 GATT descriptor allowed

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  By running the example-gatt-server and example-gatt-advertising,
  it was impossible to get more than one Descriptor per characteristic.
  if i comment one i can see the other in the test characteristic.
  but if i set both, it just act like no descriptor available.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1777634/+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 1306146] Re: rhythmbox crashed with SIGSEGV in inv_mdct_l()

2018-06-19 Thread Bug Watch Updater

** Changed in: gst-fluendo-mp3
   Status: New => Fix Released

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

Title:
  rhythmbox crashed with SIGSEGV in inv_mdct_l()

Status in Fluendo GStreamer MP3 Plugin:
  Fix Released
Status in Rhythmbox:
  Unknown
Status in gst-fluendo-mp3 package in Ubuntu:
  Confirmed

Bug description:
  I opened rhythmbox by clicking the "Play" button in the tray
  indicator, and it froze and crashed.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: rhythmbox 3.0.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
  Uname: Linux 3.13.0-23-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Apr 10 18:59:58 2014
  Disassembly: => 0x0:  Cannot access memory at address 0x0
  ExecutablePath: /usr/bin/rhythmbox
  InstallationDate: Installed on 2010-10-25 (1263 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  ProcCmdline: rhythmbox
  SegvAnalysis:
   Segfault happened at: 0x0:   Cannot access memory at address 0x0
   PC (0x) not located in a known VMA region (needed executable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: executing NULL VMA
  Signal: 11
  SourcePackage: rhythmbox
  StacktraceTop:
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstflump3dec.so
   ?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstflump3dec.so
   ?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstflump3dec.so
   gst_audio_decoder_push_buffers (dec=dec@entry=0x7fd63c012340, 
force=force@entry=0) at gstaudiodecoder.c:1406
  Title: rhythmbox crashed with SIGSEGV in gst_audio_decoder_push_buffers()
  UpgradeStatus: Upgraded to trusty on 2014-03-07 (34 days ago)
  UserGroups: adm admin audio cdrom dialout lp lpadmin plugdev sambashare video 
www-data

To manage notifications about this bug go to:
https://bugs.launchpad.net/gst-fluendo-mp3/+bug/1306146/+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 1777739] Re: systemd-journald crashed with SIGABRT in pthread_sigmask()

2018-06-19 Thread Apport retracing service

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

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

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/139/+attachment/5154412/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/139/+attachment/5154415/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/139/+attachment/5154422/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/139/+attachment/5154424/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/139/+attachment/5154425/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/139/+attachment/5154426/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/139/+attachment/5154429/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1761784

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  systemd-journald crashed with SIGABRT in pthread_sigmask()

Status in systemd package in Ubuntu:
  New

Bug description:
  No clue what caused this.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu10
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  Date: Tue Jun 19 07:12:55 2018
  ExecutablePath: /lib/systemd/systemd-journald
  InstallationDate: Installed on 2016-05-22 (757 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Hewlett-Packard HP EliteBook Folio 9470m
  ProcCmdline: /lib/systemd/systemd-journald
  ProcEnviron:
   LANG=en_CA.utf8
   LC_MONETARY=unm_US.utf8
   LC_NUMERIC=unm_US.utf8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-23-generic 
root=UUID=7ea7dcf2-f245-43a2-807a-8b662df596bb ro quiet splash vt.handoff=1
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   pthread_sigmask (how=2, newmask=, oldmask=0x0) at 
../sysdeps/unix/sysv/linux/pthread_sigmask.c:50
   journal_file_set_offline () from /lib/systemd/libsystemd-shared-237.so
   ?? ()
   ?? ()
   ?? () from /lib/systemd/libsystemd-shared-237.so
  Title: systemd-journald crashed with SIGABRT in pthread_sigmask()
  UpgradeStatus: Upgraded to bionic on 2018-05-19 (31 days ago)
  UserGroups: sambashare
  dmi.bios.date: 07/16/2013
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68IBD Ver. F.46
  dmi.board.name: 18DF
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 62.17
  dmi.chassis.asset.tag: CNU317CDD9
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68IBDVer.F.46:bd07/16/2013:svnHewlett-Packard:pnHPEliteBookFolio9470m:pvrA1029C1102:rvnHewlett-Packard:rn18DF:rvrKBCVersion62.17:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
  dmi.product.name: HP EliteBook Folio 9470m
  dmi.product.version: A1029C1102
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/139/+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 1631499] Re: package libglib2.0-0:i386 2.48.1-1~ubuntu16.04.1 failed to install/upgrade: dependency problems - leaving triggers unprocessed

This, libglib2.0-0:i386 2.48.1-1~ubuntu16.04.1, is not a package from
the official Ubuntu archive so there is nothing we, the developers of
Ubuntu, can do about it.

** Changed in: glib2.0 (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  package libglib2.0-0:i386 2.48.1-1~ubuntu16.04.1 failed to
  install/upgrade: dependency problems - leaving triggers unprocessed

Status in glib2.0 package in Ubuntu:
  Invalid

Bug description:
  Installing new version of config file /etc/X11/Xsession.d/75dbus_dbus-launch 
...
  Setting up gcr (3.18.0-1ubuntu1) ...
  dpkg: dependency problems prevent processing triggers for libglib2.0-0:i386:
   libglib2.0-0:i386 depends on libffi6 (>= 3.0.4); however:
Package libffi6:i386 is not configured yet.

  dpkg: error processing package libglib2.0-0:i386 (--configure):
   dependency problems - leaving triggers unprocessed
  dpkg: dependency problems prevent processing triggers for libglib2.0-0:i386:
   libglib2.0-0:i386 depends on libffi6 (>= 3.0.4); however:
Package libffi6:i386 is not configured yet.

  dpkg: error processing package libglib2.0-0:i386 (--configure):
   dependency problems - leaving triggers unprocessed
  dpkg: dependency problems prevent processing triggers for libglib2.0-0:i386:
   libglib2.0-0:i386 depends on libffi6 (>= 3.0.4); however:
Package libffi6:i386 is not configured yet.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libglib2.0-0:i386 2.48.1-1~ubuntu16.04.1
  ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19
  Uname: Linux 3.13.0-53-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  Date: Fri Oct  7 15:22:06 2016
  DuplicateSignature: 
package:libglib2.0-0:i386:2.48.1-1~ubuntu16.04.1:dependency problems - leaving 
triggers unprocessed
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2014-09-03 (765 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: i386
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: glib2.0
  Title: package libglib2.0-0:i386 2.48.1-1~ubuntu16.04.1 failed to 
install/upgrade: dependency problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to xenial on 2016-10-07 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1631499/+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 1652734] Re: installing kernel 4.9.0 and this crash happened installing package libglib2.0-0:amd64 2.48.1-1~ubuntu16.04.1 [origin: Ubuntu] failed to install/upgrade: dependency p

You'll need to bring this up with the developers of elementary OS.

** Changed in: glib2.0 (Ubuntu)
   Status: New => Invalid

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

Title:
  installing kernel 4.9.0 and this crash happened installing package
  libglib2.0-0:amd64 2.48.1-1~ubuntu16.04.1 [origin: Ubuntu] failed to
  install/upgrade: dependency problems - leaving triggers unprocessed

Status in glib2.0 package in Ubuntu:
  Invalid

Bug description:
  installing via dpkg

  ProblemType: Package
  DistroRelease: elementary 0.4
  Package: libglib2.0-0:amd64 2.48.1-1~ubuntu16.04.1 [origin: Ubuntu]
  Uname: Linux 4.6.3-040603-lowlatency x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  Date: Tue Dec 27 18:13:28 2016
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2016-03-10 (291 days ago)
  InstallationMedia: elementary OS 0.3.2 "Freya" - Stable amd64 (20151209)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15ubuntu0.2
  SourcePackage: glib2.0
  Title: package libglib2.0-0:amd64 2.48.1-1~ubuntu16.04.1 [origin: Ubuntu] 
failed to install/upgrade: dependency problems - leaving triggers unprocessed
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1652734/+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 1777730] [NEW] package pulseaudio-module-bluetooth 1:8.0-0ubuntu3.8 failed to install/upgrade: subprocess dpkg-split returned error exit status 2

2018-06-19 Thread Prithvi Thakur

Public bug reported:

tried to install nvidia driver. couldn't. several different errors come
up

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: pulseaudio-module-bluetooth 1:8.0-0ubuntu3.8
Uname: Linux 4.13.0-39-generic x86_64
Architecture: amd64
Date: Tue Jun 19 16:52:05 2018
DpkgHistoryLog:
 Start-Date: 2018-06-19  16:51:58
 Commandline: apt-get -f install
 Requested-By: thakur (1000)
 Upgrade: ibus:amd64 (1.5.11-1ubuntu2, 1.5.11-1ubuntu2.1), 
pulseaudio-module-bluetooth:amd64 (1:8.0-0ubuntu3.8, 1:8.0-0ubuntu3.10), 
gir1.2-ibus-1.0:amd64 (1.5.11-1ubuntu2, 1.5.11-1ubuntu2.1)
ErrorMessage: subprocess dpkg-split returned error exit status 2
SourcePackage: pulseaudio
Title: package pulseaudio-module-bluetooth 1:8.0-0ubuntu3.8 failed to 
install/upgrade: subprocess dpkg-split returned error exit status 2

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


** Tags: amd64 apport-package

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

Title:
  package pulseaudio-module-bluetooth 1:8.0-0ubuntu3.8 failed to
  install/upgrade: subprocess dpkg-split returned error exit status 2

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  tried to install nvidia driver. couldn't. several different errors
  come up

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio-module-bluetooth 1:8.0-0ubuntu3.8
  Uname: Linux 4.13.0-39-generic x86_64
  Architecture: amd64
  Date: Tue Jun 19 16:52:05 2018
  DpkgHistoryLog:
   Start-Date: 2018-06-19  16:51:58
   Commandline: apt-get -f install
   Requested-By: thakur (1000)
   Upgrade: ibus:amd64 (1.5.11-1ubuntu2, 1.5.11-1ubuntu2.1), 
pulseaudio-module-bluetooth:amd64 (1:8.0-0ubuntu3.8, 1:8.0-0ubuntu3.10), 
gir1.2-ibus-1.0:amd64 (1.5.11-1ubuntu2, 1.5.11-1ubuntu2.1)
  ErrorMessage: subprocess dpkg-split returned error exit status 2
  SourcePackage: pulseaudio
  Title: package pulseaudio-module-bluetooth 1:8.0-0ubuntu3.8 failed to 
install/upgrade: subprocess dpkg-split returned error exit status 2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/130/+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 1768905] Re: package menu 2.1.47ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed

This bug was fixed in the package menu - 2.1.47ubuntu1.17.10.1

---
menu (2.1.47ubuntu1.17.10.1) artful; urgency=medium

  * Switch triggers to use noawait (LP: #1768905)

 -- Julian Andres Klode   Tue, 05 Jun 2018 10:48:23
-0700

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

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

Title:
  package menu 2.1.47ubuntu2 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in apt package in Ubuntu:
  Incomplete
Status in menu package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Confirmed
Status in menu source package in Xenial:
  Fix Committed
Status in apt source package in Artful:
  Confirmed
Status in menu source package in Artful:
  Fix Released
Status in apt source package in Bionic:
  Confirmed
Status in menu source package in Bionic:
  Fix Committed
Status in menu package in Debian:
  New

Bug description:
  [Impact]
  Breaks some upgrades, depending on install order.

  [Test case]
  N/A. After consultation with the dpkg maintainer and investigating the 
situation, it's reasonably safe to assume that noawait is the right thing to do:

  * the intended use for the trigger is to run _after_ packages with .menu 
  files are configured, not before; therefore
  * the file trigger is triggered manually from the postinst again, discussion 
has been that the file trigger is not actually needed.

  [Regression potential]
  Menu might not be updated correctly

  [Original bug report]
  I get this error when I update to 18.04

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: menu 2.1.47ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Thu May  3 16:51:28 2018
  Dependencies:
   gcc-8-base 8-20180414-1ubuntu2
   libc6 2.27-3ubuntu1
   libgcc1 1:8-20180414-1ubuntu2
   libstdc++6 8-20180414-1ubuntu2
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2018-04-11 (22 days ago)
  InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 
(20180106)
  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: menu
  Title: package menu 2.1.47ubuntu2 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to bionic on 2018-05-03 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1768905/+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 1768905] Update Released

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

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

Title:
  package menu 2.1.47ubuntu2 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in apt package in Ubuntu:
  Incomplete
Status in menu package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Confirmed
Status in menu source package in Xenial:
  Fix Committed
Status in apt source package in Artful:
  Confirmed
Status in menu source package in Artful:
  Fix Released
Status in apt source package in Bionic:
  Confirmed
Status in menu source package in Bionic:
  Fix Committed
Status in menu package in Debian:
  New

Bug description:
  [Impact]
  Breaks some upgrades, depending on install order.

  [Test case]
  N/A. After consultation with the dpkg maintainer and investigating the 
situation, it's reasonably safe to assume that noawait is the right thing to do:

  * the intended use for the trigger is to run _after_ packages with .menu 
  files are configured, not before; therefore
  * the file trigger is triggered manually from the postinst again, discussion 
has been that the file trigger is not actually needed.

  [Regression potential]
  Menu might not be updated correctly

  [Original bug report]
  I get this error when I update to 18.04

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: menu 2.1.47ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Thu May  3 16:51:28 2018
  Dependencies:
   gcc-8-base 8-20180414-1ubuntu2
   libc6 2.27-3ubuntu1
   libgcc1 1:8-20180414-1ubuntu2
   libstdc++6 8-20180414-1ubuntu2
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2018-04-11 (22 days ago)
  InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 
(20180106)
  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: menu
  Title: package menu 2.1.47ubuntu2 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to bionic on 2018-05-03 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1768905/+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 1775292] Re: Unattended-upgrades stopped adjusting candidates in 1.1

This bug was fixed in the package unattended-upgrades - 1.3ubuntu3

---
unattended-upgrades (1.3ubuntu3) cosmic; urgency=medium

  * Stop rewriting test apt.conf in test_untrusted.py.
This fixes overwriting Unattended-Upgrade::OnlyOnACPower "false" 
accidentally
and breaking the build.

 -- Balint Reczey   Tue, 19 Jun 2018 21:24:40 +0200

** Changed in: unattended-upgrades (Ubuntu)
   Status: New => Fix Released

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

Title:
  Unattended-upgrades stopped adjusting candidates in 1.1

Status in unattended-upgrades package in Ubuntu:
  Fix Released

Bug description:
  [Impact]

   * Unattended-upgrades may fail to install an update when the highest
  version of a package to be updated exists in an origin u-u is not
  allowed to pull packages from.

  [Test Case]

   * Run sudo apt update && sudo unattended-upgrade --dry-run --verbose --debug
   * Observe no line with "adjusting candidate version: " with buggy u-u version
   * Install fixed u-u version
   * Run sudo unattended-upgrade --dry-run --verbose --debug
   * Observe lines "adjusting candidate version: "

  [Regression Potential]

   * Unattended-upgrade may crash when adjusting candidates preventing
  upgrades to be installed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1775292/+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 1773033] Re: unattended upgrade no longer actions on shutdown

This bug was fixed in the package unattended-upgrades - 1.3ubuntu3

---
unattended-upgrades (1.3ubuntu3) cosmic; urgency=medium

  * Stop rewriting test apt.conf in test_untrusted.py.
This fixes overwriting Unattended-Upgrade::OnlyOnACPower "false" 
accidentally
and breaking the build.

 -- Balint Reczey   Tue, 19 Jun 2018 21:24:40 +0200

** Changed in: unattended-upgrades (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  unattended upgrade no longer actions on shutdown

Status in unattended-upgrades package in Ubuntu:
  Fix Released

Bug description:
  Ubuntu 17.10 and 18.04 do not install updates with InstallOnShutdown
  flag set.

  post-install script on 14.04 and 16.04 would set options in
  /etc/apt/apt.conf.d/50unattended-upgrades and
  /etc/apt/apt.conf.d/10periodic to install updates on shutdown of
  ubuntu desktop. This worked on 17.10 also, until an update before the
  release of 18.04. After a fresh install of 18.04, ran the post install
  script. Below is the contents of the two files, updates do not run,
  even if performing an apt update and leaving the machine up for a few
  hours to download packages in the back ground. Both the unattended-
  upgrades and unattended-upgrades-shutdown log files are empty.

  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  ii  unattended-upgrades1.1ubuntu1
  all  automatic installation of security upgrades

  
  
--/etc/apt/apt.conf.d/50unattended-upgrades
  Unattended-Upgrade::Allowed-Origins {
  "${distro_id}:${distro_codename}";
  "${distro_id}:${distro_codename}-security";
  // Extended Security Maintenance; doesn't necessarily exist for
  // every release and this system may not have it installed, but if
  // available, the policy for updates is such that unattended-upgrades
  // should also install from here by default.
  "${distro_id}ESM:${distro_codename}";
  "${distro_id}:${distro_codename}-updates";
  //  "${distro_id}:${distro_codename}-proposed";
  //  "${distro_id}:${distro_codename}-backports";
  "LP-PPA-libreoffice:${distro_codename}";
  "Canonical:${distro_codename}";
  };

  Unattended-Upgrade::Package-Blacklist {
  //  "vim";
  //  "libc6";
  //  "libc6-dev";
  //  "libc6-i686";
  };

  Unattended-Upgrade::DevRelease "false";
  Unattended-Upgrade::InstallOnShutdown "true";
  Unattended-Upgrade::Remove-Unused-Dependencies "true";


  -/etc/apt/apt.conf.d/10periodic:--
  APT::Periodic::Update-Package-Lists "1";
  APT::Periodic::Download-Upgradeable-Packages "1";
  APT::Periodic::AutocleanInterval "7";
  APT::Periodic::Unattended-Upgrade "1";

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1773033/+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 1775307] Re: Unattended-upgrades crashes in adjusting candidates in 1.2ubuntu1 version

This bug was fixed in the package unattended-upgrades - 1.3ubuntu3

---
unattended-upgrades (1.3ubuntu3) cosmic; urgency=medium

  * Stop rewriting test apt.conf in test_untrusted.py.
This fixes overwriting Unattended-Upgrade::OnlyOnACPower "false" 
accidentally
and breaking the build.

 -- Balint Reczey   Tue, 19 Jun 2018 21:24:40 +0200

** Changed in: unattended-upgrades (Ubuntu)
   Status: New => Fix Released

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

Title:
  Unattended-upgrades crashes in adjusting candidates in 1.2ubuntu1
  version

Status in unattended-upgrades package in Ubuntu:
  Fix Released

Bug description:
  [Impact]

   * Unattended-upgrades fails to install updates when adjusting
  candidates is needed.

  [Test Case]

  Note that only 1.2ubuntu1 is affected. Earlier releases either did not
  crash or did not adjust candidates due to LP: #1775292. To reproduce
  the crash Cosmic's u-u 1.2ubuntu1 needs to be installed.

   * Run sudo apt update && sudo unattended-upgrade --dry-run --verbose --debug
   * Observe no line with "adjusting candidate version: " or a crash with buggy 
u-u versions
  ...
  adjusting candidate version: zfs-initramfs=0.7.5-1ubuntu15
  adjusting candidate version: zfs-test=0.7.5-1ubuntu15
  adjusting candidate version: zfs-zed=0.7.5-1ubuntu15
  adjusting candidate version: zfsutils-linux=0.7.5-1ubuntu15
  Traceback (most recent call last):
File "/usr/bin/unattended-upgrade", line 1928, in 
  sys.exit(main(options))
File "/usr/bin/unattended-upgrade", line 1554, in main
  allowed_origins=allowed_origins)
File "/usr/bin/unattended-upgrade", line 122, in __init__
  apt.Cache.__init__(self, rootdir=rootdir)
File "/usr/lib/python3/dist-packages/apt/cache.py", line 130, in __init__
  self.open(progress)
File "/usr/bin/unattended-upgrade", line 152, in open
  self.adjust_candidates()
File "/usr/bin/unattended-upgrade", line 161, in adjust_candidates
  for pkgname, candidate in self._get_candidates_to_adjust():
  ValueError: too many values to unpack (expected 2) * Install fixed u-u version

   * Run sudo unattended-upgrade --dry-run --verbose --debug
   * Observe lines "adjusting candidate version: " and no crash

  [Regression Potential]

   * Unattended-upgrade may crash when adjusting candidates preventing
  upgrades to be installed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1775307/+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 643623] Re: Should ubuntu-keyring include the debug archive key?

2018-06-19 Thread Unit 193

This bug was fixed with the following upload, and the package ubuntu-
dbgsym-keyring can now be installed.

ubuntu-keyring (2018.02.05) bionic; urgency=medium

  * Ship the current ubuntu-cloudimage-keyring in the ubuntu-keyring
package. LP: #1331057
  * Ship ubuntu-cloud-keyring for Cloud Archive signing keys, as a
separate keyring in /etc/apt/trusted.gpg.d/, and remove it from the
trusted.gpg keyring as no longer needed to be there.
  * Ship ubuntu-dgbsym key
  * Specify udeb Package-Type and bump priority to standard.
  * Bump standards version

 -- Dimitri John Ledkov   Wed, 17 Jan 2018 16:01:45
+

** Changed in: ubuntu-keyring (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Should ubuntu-keyring include the debug archive key?

Status in ubuntu-keyring package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: ubuntu-keyring

  Currently there doesn't seem to be a good way for developers who
  haven't been to many keysignings to establish trust in the Ubuntu
  Debug Symbol Archive Automatic Signing Key (428D7C01)

  SIgning this key with with Ubuntu Archive Automatic Signing Key (or
  equivalent) and/or including the Ubuntu Debug Symbol Archive Automatic
  Signing Key in ubuntu-keyring could help to solve this problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyring/+bug/643623/+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 1777674] Re: Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD servers

2018-06-19 Thread Joseph Salisbury

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.17 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.18-rc1

** Changed in: linux (Ubuntu)
   Importance: Undecided => High

** Also affects: linux (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: systemd (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Bionic)
   Importance: Undecided => High

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

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

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

Title:
  Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD
  servers

Status in dellserver:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  New
Status in linux source package in Bionic:
  Incomplete
Status in systemd source package in Bionic:
  New

Bug description:
  Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD
  servers when under graceful reboot stress for 12hrs.

  * This hand is observed only when Onboard SATA DVD Drive is connected.

  * Not seen with Ubuntu 16.04.4 (HWE kernel v4.13)

  * Seen with Ubuntu 18.04 (4.15.0-23-generic, 4.15.0-20-generic)

  Steps:
  Setup a DellEMC AMD server with Onboard DVD Drive, install Ubuntu 18.04 and 
start reboot stress
  After a few reboots, observe that the machine hangs at "kvm: exiting hardware 
virtualization" and does not proceed with reboot cycles.

  Only physical reset helps in continuing the reboot test.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dellserver/+bug/1777674/+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 1777711] Re: modemmanager 1.7.990-1ubuntu1 does not see my usb dongle

2018-06-19 Thread corrado venturini

may be a duplicate of
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/106

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

Title:
  modemmanager 1.7.990-1ubuntu1 does not see my usb dongle

Status in modemmanager package in Ubuntu:
  New

Bug description:
  modemmanager 1.7.990-1ubuntu1 on my Ubuntu Cosmic does not see my usb dongles 
while 1.6.8-2ubuntu1 on Ubunty Bionic and Artful (same PC, different partition) 
is ok. Same problem on my laptop. 
  Problem happens with different dongle of different factories.

  corrado@corrado-p7-cc-0527:~$ apt policy modemmanager
  modemmanager:
Installed: 1.7.990-1ubuntu1
Candidate: 1.7.990-1ubuntu1
Version table:
   *** 1.7.990-1ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  100 /var/lib/dpkg/status
  corrado@corrado-p7-cc-0527:~$ lsusb
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 004: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse
  Bus 001 Device 003: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader
  Bus 001 Device 002: ID 19d2:0037 ZTE WCDMA Technologies MSM 
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  corrado@corrado-p7-cc-0527:~$ mmcli -L

  No modems were found

  corrado@corrado-p7-cc-0527:~$ lsusb
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 004: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse
  Bus 001 Device 003: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader
  Bus 001 Device 006: ID 19d2:0037 ZTE WCDMA Technologies MSM 
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  corrado@corrado-p7-cc-0527:~$ mmcli -L

  No modems were found

  corrado@corrado-p7-cc-0527:~$ lsusb
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 004: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse
  Bus 001 Device 003: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader
  Bus 001 Device 008: ID 12d1:1003 Huawei Technologies Co., Ltd. E220 HSDPA 
Modem / E230/E270/E870 HSDPA/HSUPA Modem
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  corrado@corrado-p7-cc-0527:~$ mmcli -L

  No modems were found

  corrado@corrado-p7-cc-0527:~$ inxi -Fx
  System:
Host: corrado-p7-cc-0527 Kernel: 4.15.0-23-generic x86_64 bits: 64 
compiler: gcc v: 7.3.0 Desktop: Gnome 3.28.1 
Distro: Ubuntu Cosmic Cuttlefish (development branch) 
  Machine:
Type: Desktop Mobo: ASRock model: H110M-G/M.2 serial:  
UEFI: American Megatrends v: P1.10 date: 05/11/2017 
  CPU:
Topology: Dual Core model: Intel Core i3-7100 bits: 64 type: MT MCP 
arch: Skylake rev: 9 L2 cache: 3072 KiB 
flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 31296 
Speed: 800 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 801 2: 800 
3: 800 4: 801 
  Graphics:
Card-1: Intel HD Graphics 630 driver: i915 v: kernel bus ID: 00:02.0 
Display: x11 server: X.Org 1.19.6 driver: i915 resolution: 1920x1080~60Hz 
OpenGL: renderer: Mesa DRI Intel HD Graphics 630 (Kaby Lake GT2) 
v: 4.5 Mesa 18.1.1 direct render: Yes 
  Audio:
Card-1: Intel Sunrise Point-H HD Audio driver: snd_hda_intel v: kernel 
bus ID: 00:1f.3 
Sound Server: ALSA v: k4.15.0-23-generic 
  Network:
Card-1: Intel Ethernet Connection I219-V driver: e1000e v: 3.2.6-k 
port: N/A bus ID: 00:1f.6 
IF: enp0s31f6 state: up speed: 100 Mbps duplex: full 
mac: 70:85:c2:44:7b:86 
  Drives:
HDD Total Size: 931.51 GiB used: 8.48 GiB (0.9%) 
ID-1: /dev/sda vendor: Toshiba model: DT01ACA100 size: 931.51 GiB 
  Partition:
ID-1: / size: 31.25 GiB used: 8.47 GiB (27.1%) fs: ext4 dev: /dev/sda7 
ID-2: swap-1 size: 8.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda2 
  Sensors:
System Temperatures: cpu: 44.5 C mobo: N/A 
Fan Speeds (RPM): N/A 
  Info:
Processes: 236 Uptime: 26m Memory: 7.50 GiB used: 1.12 GiB (14.9%) 
Init: systemd runlevel: 5 Compilers: gcc: N/A Shell: bash v: 4.4.19 
inxi: 3.0.12 
  corrado@corrado-p7-cc-0527:~$ 

  
  corrado@corrado-p8-bionic:~$ apt policy modemmanager
  modemmanager:
Installed: 1.6.8-2ubuntu1
Candidate: 1.6.8-2ubuntu1
Version table:
   *** 1.6.8-2ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status
  corrado@corrado-p8-bionic:~$ lsusb
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 004: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse
  Bus 001 Device 003: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader
  Bus 001 Device 002: ID 12d1:1003 Huawei Technologies Co., Ltd. E220 HSDPA 
Modem / E230/E270/E870 HSDPA/HSUPA Modem
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  corrado@corrado-p8-bionic:~$ mmcli -L

  Found

[Touch-packages] [Bug 1770248] Re: console-setup fails intermittently due to a missing file in /tmp

** Also affects: console-setup (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

Title:
  console-setup fails intermittently due to a missing file in /tmp

Status in console-setup package in Ubuntu:
  Confirmed
Status in console-setup source package in Xenial:
  New

Bug description:
  In our testing of cloud images, we intermittently see an error along
  the lines of:

  May 09 17:59:27 ubuntu setupcon[476]: /bin/setupcon: 809:
  /bin/setupcon: cannot open /tmp/tmpkbd.7L3GEu: No such file

  This only happens from time-to-time which suggests that it's a race
  condition.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: console-setup 1.108ubuntu15.3
  ProcVersionSignature: User Name 4.13.0-1015.19-gcp 4.13.16
  Uname: Linux 4.13.0-1015-gcp x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  Date: Wed May  9 19:29:50 2018
  PackageArchitecture: all
  SourcePackage: console-setup
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1770248/+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 1777706] Re: modemmanager 1.7.990-1ubuntu1

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

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

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

Title:
  modemmanager 1.7.990-1ubuntu1

Status in modemmanager package in Ubuntu:
  Confirmed

Bug description:
  modemmanager 1.7.990-1ubuntu1 not working in Cosmic. Need to downgrade
  to modemmanager 1.6.8-2ubuntu1 to have mobile broadband working again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/106/+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 1777711] [NEW] modemmanager 1.7.990-1ubuntu1 does not see my usb dongle

2018-06-19 Thread corrado venturini

Public bug reported:

modemmanager 1.7.990-1ubuntu1 on my Ubuntu Cosmic does not see my usb dongles 
while 1.6.8-2ubuntu1 on Ubunty Bionic and Artful (same PC, different partition) 
is ok. Same problem on my laptop. 
Problem happens with different dongle of different factories.

corrado@corrado-p7-cc-0527:~$ apt policy modemmanager
modemmanager:
  Installed: 1.7.990-1ubuntu1
  Candidate: 1.7.990-1ubuntu1
  Version table:
 *** 1.7.990-1ubuntu1 500
500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
100 /var/lib/dpkg/status
corrado@corrado-p7-cc-0527:~$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse
Bus 001 Device 003: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader
Bus 001 Device 002: ID 19d2:0037 ZTE WCDMA Technologies MSM 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
corrado@corrado-p7-cc-0527:~$ mmcli -L

No modems were found

corrado@corrado-p7-cc-0527:~$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse
Bus 001 Device 003: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader
Bus 001 Device 006: ID 19d2:0037 ZTE WCDMA Technologies MSM 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
corrado@corrado-p7-cc-0527:~$ mmcli -L

No modems were found

corrado@corrado-p7-cc-0527:~$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse
Bus 001 Device 003: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader
Bus 001 Device 008: ID 12d1:1003 Huawei Technologies Co., Ltd. E220 HSDPA Modem 
/ E230/E270/E870 HSDPA/HSUPA Modem
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
corrado@corrado-p7-cc-0527:~$ mmcli -L

No modems were found

corrado@corrado-p7-cc-0527:~$ inxi -Fx
System:
  Host: corrado-p7-cc-0527 Kernel: 4.15.0-23-generic x86_64 bits: 64 
  compiler: gcc v: 7.3.0 Desktop: Gnome 3.28.1 
  Distro: Ubuntu Cosmic Cuttlefish (development branch) 
Machine:
  Type: Desktop Mobo: ASRock model: H110M-G/M.2 serial:  
  UEFI: American Megatrends v: P1.10 date: 05/11/2017 
CPU:
  Topology: Dual Core model: Intel Core i3-7100 bits: 64 type: MT MCP 
  arch: Skylake rev: 9 L2 cache: 3072 KiB 
  flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 31296 
  Speed: 800 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 801 2: 800 
  3: 800 4: 801 
Graphics:
  Card-1: Intel HD Graphics 630 driver: i915 v: kernel bus ID: 00:02.0 
  Display: x11 server: X.Org 1.19.6 driver: i915 resolution: 1920x1080~60Hz 
  OpenGL: renderer: Mesa DRI Intel HD Graphics 630 (Kaby Lake GT2) 
  v: 4.5 Mesa 18.1.1 direct render: Yes 
Audio:
  Card-1: Intel Sunrise Point-H HD Audio driver: snd_hda_intel v: kernel 
  bus ID: 00:1f.3 
  Sound Server: ALSA v: k4.15.0-23-generic 
Network:
  Card-1: Intel Ethernet Connection I219-V driver: e1000e v: 3.2.6-k 
  port: N/A bus ID: 00:1f.6 
  IF: enp0s31f6 state: up speed: 100 Mbps duplex: full 
  mac: 70:85:c2:44:7b:86 
Drives:
  HDD Total Size: 931.51 GiB used: 8.48 GiB (0.9%) 
  ID-1: /dev/sda vendor: Toshiba model: DT01ACA100 size: 931.51 GiB 
Partition:
  ID-1: / size: 31.25 GiB used: 8.47 GiB (27.1%) fs: ext4 dev: /dev/sda7 
  ID-2: swap-1 size: 8.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda2 
Sensors:
  System Temperatures: cpu: 44.5 C mobo: N/A 
  Fan Speeds (RPM): N/A 
Info:
  Processes: 236 Uptime: 26m Memory: 7.50 GiB used: 1.12 GiB (14.9%) 
  Init: systemd runlevel: 5 Compilers: gcc: N/A Shell: bash v: 4.4.19 
  inxi: 3.0.12 
corrado@corrado-p7-cc-0527:~$ 


corrado@corrado-p8-bionic:~$ apt policy modemmanager
modemmanager:
  Installed: 1.6.8-2ubuntu1
  Candidate: 1.6.8-2ubuntu1
  Version table:
 *** 1.6.8-2ubuntu1 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status
corrado@corrado-p8-bionic:~$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse
Bus 001 Device 003: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader
Bus 001 Device 002: ID 12d1:1003 Huawei Technologies Co., Ltd. E220 HSDPA Modem 
/ E230/E270/E870 HSDPA/HSUPA Modem
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
corrado@corrado-p8-bionic:~$ mmcli -L

Found 1 modems:
/org/freedesktop/ModemManager1/Modem/0 [huawei] E17X

corrado@corrado-p8-bionic:~$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse
Bus 001 Device 003: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader
Bus 001 Device 006: ID 19d2:0037 ZTE WCDMA Technologies MSM 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
corrado@corrado-p8-bionic:~$ mmcli -L

Found 1 modems:
/org/freedesktop/ModemManager1/Modem/1 [ONDA COMMUNICATION] MT191UP

[Touch-packages] [Bug 1777706] Re: modemmanager 1.7.990-1ubuntu1

2018-06-19 Thread Matteo Peterle

Upgrading libmm-glib0 1.6.8-2ubuntu1 to libmm-glib0 1.7.990-1ubuntu1
makes mobile broadband not working as well.

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

Title:
  modemmanager 1.7.990-1ubuntu1

Status in modemmanager package in Ubuntu:
  New

Bug description:
  modemmanager 1.7.990-1ubuntu1 not working in Cosmic. Need to downgrade
  to modemmanager 1.6.8-2ubuntu1 to have mobile broadband working again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/106/+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 1777709] [NEW] ubuntu-bug xserver-xorg-video-intel shows bogus dialog

2018-06-19 Thread Horst Schirmeier

Public bug reported:

Running "ubuntu-bug xserver-xorg-video-intel" as a normal user pops up a
bogus dialog after a few seconds:

[i] text

[Yes] [No] [Cancel]

There seems to be a descriptive message missing in place of the "text"
placeholder.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: apport 2.20.9-0ubuntu7.2
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Uname: Linux 4.15.0-23-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CurrentDesktop: KDE
Date: Tue Jun 19 20:53:42 2018
InstallationDate: Installed on 2016-11-26 (570 days ago)
InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: Upgraded to bionic on 2018-03-14 (97 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/109

Title:
  ubuntu-bug xserver-xorg-video-intel shows bogus dialog

Status in apport package in Ubuntu:
  New

Bug description:
  Running "ubuntu-bug xserver-xorg-video-intel" as a normal user pops up
  a bogus dialog after a few seconds:

  [i] text

  [Yes] [No] [Cancel]

  There seems to be a descriptive message missing in place of the "text"
  placeholder.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apport 2.20.9-0ubuntu7.2
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Tue Jun 19 20:53:42 2018
  InstallationDate: Installed on 2016-11-26 (570 days ago)
  InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to bionic on 2018-03-14 (97 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/109/+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 1747175] Re: [Inspiron 5559, Realtek ALC3234, Black Headphone Out, Front] No sound at all

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

Title:
  [Inspiron 5559, Realtek ALC3234, Black Headphone Out, Front] No sound
  at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  My internal speaker works fine
  People say it is a problem of ALSADRIVER
  Headphone jack works in windows
  Issue lies with ubuntu

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-112.135-lowlatency 4.4.98
  Uname: Linux 4.4.0-112-lowlatency x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  harish 2674 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sat Feb  3 23:42:53 2018
  InstallationDate: Installed on 2016-07-06 (577 days ago)
  InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  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:  harish 2674 F pulseaudio
  Symptom_Jack: Black Headphone Out, Front
  Symptom_Type: No sound at all
  Title: [Inspiron 5559, Realtek ALC3234, Black Headphone Out, Front] No sound 
at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/25/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 04D1V1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd08/25/2016:svnDellInc.:pnInspiron5559:pvr:rvnDellInc.:rn04D1V1:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 5559
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1747175/+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 1777706] [NEW] modemmanager 1.7.990-1ubuntu1

2018-06-19 Thread Matteo Peterle

Public bug reported:

modemmanager 1.7.990-1ubuntu1 not working in Cosmic. Need to downgrade
to modemmanager 1.6.8-2ubuntu1 to have mobile broadband working again.

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

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

Title:
  modemmanager 1.7.990-1ubuntu1

Status in modemmanager package in Ubuntu:
  New

Bug description:
  modemmanager 1.7.990-1ubuntu1 not working in Cosmic. Need to downgrade
  to modemmanager 1.6.8-2ubuntu1 to have mobile broadband working again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/106/+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 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.

Hello Marc, or anyone else affected,

Accepted initramfs-tools into bionic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/initramfs-
tools/0.130ubuntu3.2 in a few hours, and then in the -proposed
repository.

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

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

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

** Changed in: initramfs-tools (Ubuntu Bionic)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-bionic

-- 
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:
  In Progress
Status in initramfs-tools source package in Bionic:
  Fix Committed

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 1769682] Re: NFS-based remote root hangs when running 'netplan apply'

Hello Mathieu, or anyone else affected,

Accepted initramfs-tools into bionic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/initramfs-
tools/0.130ubuntu3.2 in a few hours, and then in the -proposed
repository.

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

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

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

** Changed in: initramfs-tools (Ubuntu Bionic)
   Status: Confirmed => Fix Committed

** Tags added: verification-needed verification-needed-bionic

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

Title:
  NFS-based remote root hangs when running 'netplan apply'

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in netplan.io package in Ubuntu:
  Fix Released
Status in nplan package in Ubuntu:
  Invalid
Status in initramfs-tools source package in Xenial:
  Confirmed
Status in netplan.io source package in Xenial:
  Invalid
Status in nplan source package in Xenial:
  Fix Released
Status in initramfs-tools source package in Artful:
  Confirmed
Status in netplan.io source package in Artful:
  Invalid
Status in nplan source package in Artful:
  Fix Released
Status in initramfs-tools source package in Bionic:
  Fix Committed
Status in netplan.io source package in Bionic:
  Fix Released
Status in nplan source package in Bionic:
  Invalid

Bug description:
  [Impact]
  Netboot users with a remote filesystem over NFS (possibly over other 
networked filesystems).

  [Test cases]
  1) Boot a system with its root filesystem over NFS.
  2) Run 'sudo netplan apply'
  3) Validate that the system remains responsive and keeps connectivity over 
the same IP address  as it had.

  [Regression potential]
  This SRU changes network properties, and enforces that networkd does not 
release and re-request an IP address from DHCP when it is restarted. 
Environments relying on the IP release/renew behavior may find themselves 
staying on the previous IP address, which might negatively impact connectivity. 
Changes in connectivity on a system running netplan should be investigated as a 
potential regression from this SRU. Other regression possibilities would 
include failure to get a new IP address over time (usually seen as losing 
connectivity) or possible IP conflicts on a network.

  ---

  With a system booted on the network, with its remote root fs on NFS:

  Running 'netplan apply' restarts systemd-networkd, which releases the
  IP received from DHCP. With no IP (and and IP potentially changing),
  the NFS server can't be reached so the system hangs.

  'netplan apply' or restarting systemd-networkd should not affect teh
  system, it should continue working normally despite "changing" network
  states, as long as the effective IP remains the same.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1769682/+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 1773334] Re: Ubuntu 18.04 mounted network shares not appearing under devices in file manager

2018-06-19 Thread Phillip Susi

Reported upstream: https://gitlab.gnome.org/GNOME/glib/issues/1424


** Package changed: udisks2 (Ubuntu) => glib2.0 (Ubuntu)

** Changed in: glib2.0 (Ubuntu)
   Importance: Undecided => High

** Changed in: glib2.0 (Ubuntu)
   Status: Confirmed => Triaged

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

Title:
  Ubuntu 18.04 mounted network shares not appearing under devices in
  file manager

Status in glib2.0 package in Ubuntu:
  Triaged

Bug description:
  Apologies if this is not the correct package to file this
  bug/regression against.

  On my 18.04 desktop installs (Gnome shell and Ubuntu Mate) when
  mounting network shares (SMB and NFS) they no longer appear under
  Devices in file manager (Nautilus or Caja), the mounts do succeed and
  are accessible at their mount points.

  In 16.04 and 17.10 these mounts appeared under Devices (Screenshot of
  mounted network shares on Ubuntu Mate 17.10 attached)

  I am using the following code to mount NFS shares

  `sudo mount.nfs 192.168.2.123:/mnt/freenas-data1/photobackup
  /media/philroche/photobackup`

  and for SMB shares

  `sudo mount.cifs //192.168.2.123/photobackup
  /media/philroche/photobackup`

  Is this a bug/regression, or perhaps it is an intentional change?

  I did ask this on IRC in #ubuntu and askubuntu.com but no reply.

  Expected behaviour:

  I expected the mounted network shares to appear under Devices in File
  manager

  Actual behaviour:

  Mounting network shares does succeed as expected but does not appear
  under Devices in File manager as it did in previous releases.

  Requested details:

  Description:  Ubuntu 18.04 LTS
  Release:  18.04
  udisks2:
Installed: 2.7.6-3
Candidate: 2.7.6-3
Version table:
   *** 2.7.6-3 500
  500 http://ie.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1773334/+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 1773334] [NEW] Ubuntu 18.04 mounted network shares not appearing under devices in file manager

You have been subscribed to a public bug:

Apologies if this is not the correct package to file this bug/regression
against.

On my 18.04 desktop installs (Gnome shell and Ubuntu Mate) when mounting
network shares (SMB and NFS) they no longer appear under Devices in file
manager (Nautilus or Caja), the mounts do succeed and are accessible at
their mount points.

In 16.04 and 17.10 these mounts appeared under Devices (Screenshot of
mounted network shares on Ubuntu Mate 17.10 attached)

I am using the following code to mount NFS shares

`sudo mount.nfs 192.168.2.123:/mnt/freenas-data1/photobackup
/media/philroche/photobackup`

and for SMB shares

`sudo mount.cifs //192.168.2.123/photobackup
/media/philroche/photobackup`

Is this a bug/regression, or perhaps it is an intentional change?

I did ask this on IRC in #ubuntu and askubuntu.com but no reply.

Expected behaviour:

I expected the mounted network shares to appear under Devices in File
manager

Actual behaviour:

Mounting network shares does succeed as expected but does not appear
under Devices in File manager as it did in previous releases.

Requested details:

Description:Ubuntu 18.04 LTS
Release:18.04
udisks2:
  Installed: 2.7.6-3
  Candidate: 2.7.6-3
  Version table:
 *** 2.7.6-3 500
500 http://ie.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status

** Affects: glib2.0 (Ubuntu)
 Importance: High
 Status: Triaged

-- 
Ubuntu 18.04 mounted network shares not appearing under devices in file manager
https://bugs.launchpad.net/bugs/1773334
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to glib2.0 in Ubuntu.

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

[Touch-packages] [Bug 1769682] Re: NFS-based remote root hangs when running 'netplan apply'

2018-06-19 Thread Mathieu Trudel-Lapierre

** Tags removed: verification-done-artful verification-done-bionic
verification-done-xenial

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

Title:
  NFS-based remote root hangs when running 'netplan apply'

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in netplan.io package in Ubuntu:
  Fix Released
Status in nplan package in Ubuntu:
  Invalid
Status in initramfs-tools source package in Xenial:
  Confirmed
Status in netplan.io source package in Xenial:
  Invalid
Status in nplan source package in Xenial:
  Fix Released
Status in initramfs-tools source package in Artful:
  Confirmed
Status in netplan.io source package in Artful:
  Invalid
Status in nplan source package in Artful:
  Fix Released
Status in initramfs-tools source package in Bionic:
  Confirmed
Status in netplan.io source package in Bionic:
  Fix Released
Status in nplan source package in Bionic:
  Invalid

Bug description:
  [Impact]
  Netboot users with a remote filesystem over NFS (possibly over other 
networked filesystems).

  [Test cases]
  1) Boot a system with its root filesystem over NFS.
  2) Run 'sudo netplan apply'
  3) Validate that the system remains responsive and keeps connectivity over 
the same IP address  as it had.

  [Regression potential]
  This SRU changes network properties, and enforces that networkd does not 
release and re-request an IP address from DHCP when it is restarted. 
Environments relying on the IP release/renew behavior may find themselves 
staying on the previous IP address, which might negatively impact connectivity. 
Changes in connectivity on a system running netplan should be investigated as a 
potential regression from this SRU. Other regression possibilities would 
include failure to get a new IP address over time (usually seen as losing 
connectivity) or possible IP conflicts on a network.

  ---

  With a system booted on the network, with its remote root fs on NFS:

  Running 'netplan apply' restarts systemd-networkd, which releases the
  IP received from DHCP. With no IP (and and IP potentially changing),
  the NFS server can't be reached so the system hangs.

  'netplan apply' or restarting systemd-networkd should not affect teh
  system, it should continue working normally despite "changing" network
  states, as long as the effective IP remains the same.

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

2018-06-19 Thread Ubuntu Kernel Bot

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

apport-collect 1777674

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

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

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

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

** Tags added: bionic

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

Title:
  Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD
  servers

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

Bug description:
  Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD
  servers when under graceful reboot stress for 12hrs.

  * This hand is observed only when Onboard SATA DVD Drive is connected.

  * Not seen with Ubuntu 16.04.4 (HWE kernel v4.13)

  * Seen with Ubuntu 18.04 (4.15.0-23-generic, 4.15.0-20-generic)

  Steps:
  Setup a DellEMC AMD server with Onboard DVD Drive, install Ubuntu 18.04 and 
start reboot stress
  After a few reboots, observe that the machine hangs at "kvm: exiting hardware 
virtualization" and does not proceed with reboot cycles.

  Only physical reset helps in continuing the reboot test.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dellserver/+bug/1777674/+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 1777674] Re: Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD servers

Moving the bug-report back to Confirmed since these logs like "kvm exiting 
hardware virt" and the logs post this are not stored on the physical disks 
(reason - disks are already unmounted).
Such logs are available only in the console logs which are already uploaded in 
this report.

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

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

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

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

Title:
  Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD
  servers

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

Bug description:
  Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD
  servers when under graceful reboot stress for 12hrs.

  * This hand is observed only when Onboard SATA DVD Drive is connected.

  * Not seen with Ubuntu 16.04.4 (HWE kernel v4.13)

  * Seen with Ubuntu 18.04 (4.15.0-23-generic, 4.15.0-20-generic)

  Steps:
  Setup a DellEMC AMD server with Onboard DVD Drive, install Ubuntu 18.04 and 
start reboot stress
  After a few reboots, observe that the machine hangs at "kvm: exiting hardware 
virtualization" and does not proceed with reboot cycles.

  Only physical reset helps in continuing the reboot test.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dellserver/+bug/1777674/+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 1777674] Re: Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD servers

Logs where the hang is not seen:

[   75.448494] kvm: exiting hardware virtualization
[   76.187482] reboot: Restarting system
[   76.191663] reboot: machine restart
[   76.197621] ACPI MEMORY or I/O RESET_REG.


The last 3 lines are not seen when the hang is observed.

** Attachment added: "console-logs-no-failure-case"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777674/+attachment/5154317/+files/console-logs-no-failure.txt

** Also affects: dellserver
   Importance: Undecided
   Status: New

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

Title:
  Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD
  servers

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

Bug description:
  Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD
  servers when under graceful reboot stress for 12hrs.

  * This hand is observed only when Onboard SATA DVD Drive is connected.

  * Not seen with Ubuntu 16.04.4 (HWE kernel v4.13)

  * Seen with Ubuntu 18.04 (4.15.0-23-generic, 4.15.0-20-generic)

  Steps:
  Setup a DellEMC AMD server with Onboard DVD Drive, install Ubuntu 18.04 and 
start reboot stress
  After a few reboots, observe that the machine hangs at "kvm: exiting hardware 
virtualization" and does not proceed with reboot cycles.

  Only physical reset helps in continuing the reboot test.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dellserver/+bug/1777674/+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 1777674] [NEW] Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD servers

Public bug reported:

Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD
servers when under graceful reboot stress for 12hrs.

* This hand is observed only when Onboard SATA DVD Drive is connected.

* Not seen with Ubuntu 16.04.4 (HWE kernel v4.13)

* Seen with Ubuntu 18.04 (4.15.0-23-generic, 4.15.0-20-generic)

Steps:
Setup a DellEMC AMD server with Onboard DVD Drive, install Ubuntu 18.04 and 
start reboot stress
After a few reboots, observe that the machine hangs at "kvm: exiting hardware 
virtualization" and does not proceed with reboot cycles.

Only physical reset helps in continuing the reboot test.

** Affects: dellserver
 Importance: Undecided
 Status: New

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

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

** Attachment added: "console-logs"
   
https://bugs.launchpad.net/bugs/1777674/+attachment/5154314/+files/console-logs.txt

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

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

Title:
  Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD
  servers

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

Bug description:
  Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD
  servers when under graceful reboot stress for 12hrs.

  * This hand is observed only when Onboard SATA DVD Drive is connected.

  * Not seen with Ubuntu 16.04.4 (HWE kernel v4.13)

  * Seen with Ubuntu 18.04 (4.15.0-23-generic, 4.15.0-20-generic)

  Steps:
  Setup a DellEMC AMD server with Onboard DVD Drive, install Ubuntu 18.04 and 
start reboot stress
  After a few reboots, observe that the machine hangs at "kvm: exiting hardware 
virtualization" and does not proceed with reboot cycles.

  Only physical reset helps in continuing the reboot test.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dellserver/+bug/1777674/+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 1713803] Re: replacement of resolvconf with systemd needs integration

How will the initramfs-tools change be validated? What test case will be
run to make sure it's working as intended?

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

Title:
  replacement of resolvconf with systemd needs integration

Status in android-androresolvd package in Ubuntu:
  Triaged
Status in avahi package in Ubuntu:
  Triaged
Status in bind9 package in Ubuntu:
  Triaged
Status in cloud-init package in Ubuntu:
  Incomplete
Status in cloud-initramfs-tools package in Ubuntu:
  Invalid
Status in dhcpcd5 package in Ubuntu:
  Confirmed
Status in dibbler package in Ubuntu:
  Won't Fix
Status in dnscrypt-proxy package in Ubuntu:
  Confirmed
Status in dnsmasq package in Ubuntu:
  Invalid
Status in dnssec-trigger package in Ubuntu:
  Invalid
Status in fetchmail package in Ubuntu:
  Confirmed
Status in freedombox-setup package in Ubuntu:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in ndisc6 package in Ubuntu:
  Fix Released
Status in netscript-2.4 package in Ubuntu:
  Won't Fix
Status in open-iscsi package in Ubuntu:
  Triaged
Status in openvpn package in Ubuntu:
  Confirmed
Status in postfix package in Ubuntu:
  Invalid
Status in pppconfig package in Ubuntu:
  Confirmed
Status in pump package in Ubuntu:
  Confirmed
Status in resolvconf package in Ubuntu:
  Invalid
Status in sendmail package in Ubuntu:
  Invalid
Status in squid3 package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid
Status in unbound package in Ubuntu:
  Triaged
Status in vpnc package in Ubuntu:
  Invalid
Status in vpnc-scripts package in Ubuntu:
  Invalid
Status in whereami package in Ubuntu:
  Triaged

Bug description:
  There is a plan to remove resolvconf from the Ubuntu Server image.
  resolvconf integrated with other parts of the system in 2 ways:
   * hooks invoked on change (/etc/resolvconf/update.d/)
   * resolvconf tool (invoked with -a and -d or -u)

  Packages which install files into /etc/resolvconf/update.d are:
  - dnsmasq: This may be mostly covered by systemd-resolved itself (the dns
    caching path).
  - resolvconf: This probably isn't necessary in systemd-resolved path.
  - unbound: This is another "validating, recursive, caching DNS resolver".

  The list of Depends/Suggests/Recommends on resolvconf.

  # for pkg in $(apt-cache rdepends resolvconf | grep -v openreso | grep -v 
Reverse); do out=$(apt-cache show $pkg | grep resolvconf); src=$(apt-cache show 
$pkg | awk '$1 == "Source:" { print $2 }'); [ -n "$src" ] || src=$pkg; case 
"$out" in Depends:*resolvconf) r=depends;; Suggests:*) r=suggests;; 
Recommends:*) r=recommends;; esac; echo "$r $src"; done  | sort -u
  depends android-androresolvd
  recommends avahi
  recommends dhcpcd5
  recommends dibbler
  recommends ndisc6
  recommends whereami
  suggests bind9
  suggests dnscrypt-proxy
  suggests dnsmasq
  suggests dnssec-trigger
  suggests fetchmail
  suggests freedombox-setup
  suggests isc-dhcp
  suggests netscript-2.4
  suggests openvpn
  suggests postfix
  suggests pppconfig
  suggests pump
  suggests resolvconf
  suggests sendmail
  suggests squid3
  suggests vpnc
  suggests vpnc-scripts

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu9
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: amd64
  Date: Tue Aug 29 18:53:50 2017
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-11-generic 
root=UUID=f897b32a-eacf-4191-9717-844918947069 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.vendor: Intel Corporation

  Related bugs:
   * bug 1698181: Switch to netplan renderer in Artful
   * bug 1714308: dns does not work in initramfs after configure_networking
   * bug 1717983 replacement of isc-dhcp-client with with systemd-networkd for 
dhclient needs integration

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/android-androresolvd/+bug/1713803/+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 1771962] Update Released

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

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

Title:
  hanging at boot for about 30 seconds since upgrade to bionic

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

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, even if the swap 
device is ephemeral (i.e. swap encrypted with a random key).  This adds an 
inappropriate 30-second boot delay to any system with randomly-crypted swap, 
which includes any system that was installed with encrypted home directories in 
earlier releases.

  [Test case]
  1. Install the ecryptfs-utils package.
  2. Enable encrypted swap by running 'sudo ecryptfs-setup-swap'.
  3. Run 'update-initramfs -u' to regenerate the initramfs.
  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.

  [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]
  Since upgrade to Bionic ubuntu is hanging at boot for about 30s. A `dmesg` 
shows

  ```
  [3.407230] clocksource: Switched to clocksource tsc
  [   34.632583] EXT4-fs (sda2): mounted filesystem with ordered data mode. 
Opts: (null)
  ```

  This is 100% reproducable and is always 30s minimum. I do not know in
  which package to report this properly – please excuse me.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader-core 1:18.04.17
  ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17
  Uname: Linux 4.15.0-20-lowlatency x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: i3
  Date: Fri May 18 09:40:59 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-06-03 (1444 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: Upgraded to bionic on 2018-05-13 (5 days ago)
  VarLogDistupgradeAptclonesystemstate.tar.gz:
   Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
127: polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized

   This incident has been reported.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1771962/+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 1771962] Re: hanging at boot for about 30 seconds since upgrade to bionic

This bug was fixed in the package initramfs-tools - 0.130ubuntu3.1

---
initramfs-tools (0.130ubuntu3.1) bionic; urgency=medium

  * hooks/resume: don't generate RESUME config pointing to randomly-crypted
swap devices.  LP: #1771962.

 -- Steve Langasek   Fri, 08 Jun 2018
21:29:19 -0700

** Changed in: initramfs-tools (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  hanging at boot for about 30 seconds since upgrade to bionic

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

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, even if the swap 
device is ephemeral (i.e. swap encrypted with a random key).  This adds an 
inappropriate 30-second boot delay to any system with randomly-crypted swap, 
which includes any system that was installed with encrypted home directories in 
earlier releases.

  [Test case]
  1. Install the ecryptfs-utils package.
  2. Enable encrypted swap by running 'sudo ecryptfs-setup-swap'.
  3. Run 'update-initramfs -u' to regenerate the initramfs.
  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.

  [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]
  Since upgrade to Bionic ubuntu is hanging at boot for about 30s. A `dmesg` 
shows

  ```
  [3.407230] clocksource: Switched to clocksource tsc
  [   34.632583] EXT4-fs (sda2): mounted filesystem with ordered data mode. 
Opts: (null)
  ```

  This is 100% reproducable and is always 30s minimum. I do not know in
  which package to report this properly – please excuse me.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader-core 1:18.04.17
  ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17
  Uname: Linux 4.15.0-20-lowlatency x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: i3
  Date: Fri May 18 09:40:59 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-06-03 (1444 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: Upgraded to bionic on 2018-05-13 (5 days ago)
  VarLogDistupgradeAptclonesystemstate.tar.gz:
   Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
127: polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized

   This incident has been reported.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1771962/+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 1773992] Re: apt-key adv should gpgconf --kill all the things after execution

2018-06-19 Thread Julian Andres Klode

** Changed in: apt (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  apt-key adv should gpgconf --kill all the things after execution

Status in apt package in Ubuntu:
  Fix Committed

Bug description:
  apt-key adv should gpgconf --kill all the things after execution

  to ensure that e.g. dirmngr processes are not left hanging around

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

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

Re: [Touch-packages] [Bug 1777094] Re: dnsmasq started too early, not getting all interfaces

2018-06-19 Thread Ryan Harper

On Tue, Jun 19, 2018 at 9:41 AM Hadmut Danisch  wrote:
>
> dnsmasq _after_ networking?
>
> Isn't it part of networking and should be running and ready for other
> services depending on networking?

Yes, but it's complicated; see below.

>
>
> (my guess is that Ubuntu has never defined the targets very precisely. it 
> should distinguish between low level /interface level configuration and 
> networking services.)
>

This is rather precisely defined; not by Ubuntu but by the init
system.  In systemd there are many targets that indicate various state
of the system during boot[1][2]
For networking, the ones that matter are:

network-pre.target (before systemd has attempted to bring the network up)
network.target (systemd has started to bring network up; for
Artful/Bionic, this means systemd-networkd.service has started)
network-online.target ("required" networking interfaces are up,
configured, routable)

Dnsmasq itself is a networking service, so arguably, it is fine to run
at After=network.target; but network.target does not guarantee that
all of networking has been configured.  Dnsmasq has two choices.  1)
it can run later, at network-online.target which means systemd is
done with creating and configuring interfaces.  2) start at
After=network.target but listen to dbus or netlink layer to react to
when a
configured interface is present and ready for it to use.

Since dnsmasq does not watch dbus or netlink for new interfaces and
when they're configured, then the only solution is to run after such
a time that the configured interfaces are ready for use by dnsmasq.

1. https://www.freedesktop.org/software/systemd/man/systemd.special.html
2. https://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/

> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1777094
>
> Title:
>   dnsmasq started too early, not getting all interfaces
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1777094/+subscriptions

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

Title:
  dnsmasq started too early, not getting all interfaces

Status in dnsmasq package in Ubuntu:
  Incomplete
Status in netplan.io package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I'm still struggling with 18.04 and the move from ifupdown to netplan.

  I am running a local virtual linux bridge as a network for several
  virtual machines and containers, which is to be serviced with dhcp and
  dns by dnsmasq.

  Conforming to latest designs from Ubuntu the bridge is now started by
  netplan and configured in /etc/netplan/60-vlan0.yaml straightforward.

  Since there is no ifupdown-scripts anymore, I've configured the
  default dnsmasq daemon in /etc/dnsmasq.d/vlan0 to offer dhcp for that
  bridge.

  This works only when started manually. 

  When booting ubuntu the normal way, the bridge is correctly generated,
  and dnsmasq is running, but it does *not* offer DNS for the bridge and
  does not occupy its port 53. But just a manual systemctl restart
  dnsmasq.service make it run as expected, then everything is fine.

  So my guess is that my configuration is correct, but dnsmasq simply
  started to early, i.e. before the bridge is created, and thus does not
  see the bridge when starting up.

  There's something wrong in the dependencies of the startup
  configuration.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: dnsmasq 2.79-1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Fri Jun 15 10:59:43 2018
  InstallationDate: Installed on 2018-04-30 (45 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  PackageArchitecture: all
  SourcePackage: dnsmasq
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1777094/+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 1777094] Re: dnsmasq started too early, not getting all interfaces

2018-06-19 Thread Hadmut Danisch

dnsmasq _after_ networking?

Isn't it part of networking and should be running and ready for other
services depending on networking?


(my guess is that Ubuntu has never defined the targets very precisely. it 
should distinguish between low level /interface level configuration and 
networking services.)

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

Title:
  dnsmasq started too early, not getting all interfaces

Status in dnsmasq package in Ubuntu:
  Incomplete
Status in netplan.io package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I'm still struggling with 18.04 and the move from ifupdown to netplan.

  I am running a local virtual linux bridge as a network for several
  virtual machines and containers, which is to be serviced with dhcp and
  dns by dnsmasq.

  Conforming to latest designs from Ubuntu the bridge is now started by
  netplan and configured in /etc/netplan/60-vlan0.yaml straightforward.

  Since there is no ifupdown-scripts anymore, I've configured the
  default dnsmasq daemon in /etc/dnsmasq.d/vlan0 to offer dhcp for that
  bridge.

  
  This works only when started manually. 

  When booting ubuntu the normal way, the bridge is correctly generated,
  and dnsmasq is running, but it does *not* offer DNS for the bridge and
  does not occupy its port 53. But just a manual systemctl restart
  dnsmasq.service make it run as expected, then everything is fine.

  So my guess is that my configuration is correct, but dnsmasq simply
  started to early, i.e. before the bridge is created, and thus does not
  see the bridge when starting up.

  There's something wrong in the dependencies of the startup
  configuration.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: dnsmasq 2.79-1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Fri Jun 15 10:59:43 2018
  InstallationDate: Installed on 2018-04-30 (45 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  PackageArchitecture: all
  SourcePackage: dnsmasq
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

Re: [Touch-packages] [Bug 1777094] Re: dnsmasq started too early, not getting all interfaces

2018-06-19 Thread Ryan Harper

I see, interesting.  The dnsmasq.service does not wait for
network-online.target;

This appears to be a duplicate of:

https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1531184

In addition to the netplan config to ensure it waits for your bridge
to come up, you need to delay dnsmasq.service until after the network
is online.  You can do that with something like this:

% mkdir -p /etc/systemd/system/dnsmasq.service.d
% echo -e "[Unit]\nAfter=network-online.target\nWants=network-online.target"
| sudo tee /etc/systemd/system/dnsmasq.service.d/network-online.conf
% reboot

After rebooting, you should see that networkd runs, brings up the
interfaces, then network-online.target is reached, and lastly dnsmasq
is then started.

% journalctl -b -o short-monotonic | egrep "(Reboot|networkd|Network
is Online|Starting dnsmasq)"
[1835835.825873] b1 systemd-networkd[173]: vlan0: IPv6 successfully enabled
[1835835.827054] b1 systemd-networkd[173]: vlan0: netdev ready
[1835835.837274] b1 systemd-networkd[173]: Enumeration completed
[1835835.864747] b1 systemd-networkd[173]: eth1: Lost carrier
[1835835.871748] b1 systemd-networkd[173]: eth0: DHCPv4 address
10.8.107.77/24 via 10.8.107.1
[1835835.879184] b1 systemd-networkd[173]: eth1: IPv6 successfully disabled
[1835835.908530] b1 systemd-networkd[173]: eth1: Gained carrier
[1835835.908903] b1 systemd-networkd[173]: eth1: Configured
[1835835.909878] b1 systemd-networkd[173]: vlan0: Gained carrier
[1835835.913807] b1 systemd-networkd-wait-online[175]: managing: eth1
[1835836.288648] b1 systemd-networkd[173]: eth0: Gained IPv6LL
[1835836.289022] b1 systemd-networkd[173]: eth0: Configured
[1835836.290405] b1 systemd-networkd-wait-online[175]: managing: eth1
[1835836.290834] b1 systemd-networkd-wait-online[175]: managing: eth0
[1835836.291077] b1 systemd-networkd-wait-online[175]: ignoring: lo
[1835837.760738] b1 systemd-networkd[173]: vlan0: Gained IPv6LL
[1835837.761713] b1 systemd-networkd[173]: vlan0: Configured
[1835837.762522] b1 systemd-networkd-wait-online[175]: managing: eth1
[1835837.763413] b1 systemd-networkd-wait-online[175]: managing: eth0
[1835837.763705] b1 systemd-networkd-wait-online[175]: ignoring: lo
[1835837.764057] b1 systemd-networkd-wait-online[175]: managing: vlan0
[1835838.445945] b1 systemd[1]: Reached target Network is Online.
[1835838.496394] b1 dbus-daemon[195]: [system] Activating via systemd:
service name='org.freedesktop.hostname1'
unit='dbus-org.freedesktop.hostname1.service' requested by ':1.0'
(uid=100 pid=173 comm="/lib/systemd/systemd-networkd "
label="unconfined")
[1835838.516683] b1 systemd[1]: Starting dnsmasq - A lightweight DHCP
and caching DNS server...
On Tue, Jun 19, 2018 at 3:51 AM Hadmut Danisch  wrote:
>
> setting optional: false   does not solve the problem, a systemctl
> restart dnsmasq is still required.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1777094
>
> Title:
>   dnsmasq started too early, not getting all interfaces
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1777094/+subscriptions

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

Title:
  dnsmasq started too early, not getting all interfaces

Status in dnsmasq package in Ubuntu:
  Incomplete
Status in netplan.io package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I'm still struggling with 18.04 and the move from ifupdown to netplan.

  I am running a local virtual linux bridge as a network for several
  virtual machines and containers, which is to be serviced with dhcp and
  dns by dnsmasq.

  Conforming to latest designs from Ubuntu the bridge is now started by
  netplan and configured in /etc/netplan/60-vlan0.yaml straightforward.

  Since there is no ifupdown-scripts anymore, I've configured the
  default dnsmasq daemon in /etc/dnsmasq.d/vlan0 to offer dhcp for that
  bridge.

  This works only when started manually. 

  When booting ubuntu the normal way, the bridge is correctly generated,
  and dnsmasq is running, but it does *not* offer DNS for the bridge and
  does not occupy its port 53. But just a manual systemctl restart
  dnsmasq.service make it run as expected, then everything is fine.

  So my guess is that my configuration is correct, but dnsmasq simply
  started to early, i.e. before the bridge is created, and thus does not
  see the bridge when starting up.

  There's something wrong in the dependencies of the startup
  configuration.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: dnsmasq 2.79-1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Fri Jun 15

[Touch-packages] [Bug 1776499] Re: Crash in libegl-mesa0 due to out of bound array access

2018-06-19 Thread Iain Lane

** Changed in: mesa (Ubuntu Bionic)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

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

Title:
  Crash in libegl-mesa0 due to out of bound array access

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Bionic:
  New

Bug description:
  Crash in libegl-mesa0 due to out of bound array access. Crash is fixed
  on Mesa master branch with change:
  
https://cgit.freedesktop.org/mesa/mesa/commit/?id=41642bdbca007035772fbfdc311f14daa5510d5d
  .This bug is to request to include this change in Mesa upgrades in
  bionic.

  Please let me know if this change needs to be back ported to other
  branch so that libegl-mesa0 upgrade in Bionic could pick this change.

  lsb_release -a
  Distributor ID: Ubuntu
  Description:Ubuntu 18.04 LTS
  Release:18.04
  Codename:   bionic

  apt-cache policy libegl-mesa0
  libegl-mesa0:
Installed: 18.0.0~rc5-1ubuntu1
Candidate: 18.0.0~rc5-1ubuntu1
Version table:
   *** 18.0.0~rc5-1ubuntu1 500
  500 http://ports.ubuntu.com/ubuntu-ports bionic/main arm64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1776499/+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 1431214] Re: Unattended-upgrades triggers kernel taint when rebuilding initrd

2018-06-19 Thread Balint Reczey

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

I'm setting this bug as a duplicate of the kernel bug as u-u can't
ensure upgrading kernel and modules in lockstep unless strict
dependencies are set between the packages.

** This bug has been marked a duplicate of bug 1253155
   Failure to validate module signature at boot time

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

Title:
  Unattended-upgrades triggers kernel taint when rebuilding initrd

Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  Kernel logs from unattended-upgrades doing mkinitrd resemble Bug
  #1253155 symptoms.

  Mar 12 06:31:51 network kernel: [213747.796032] Request for unknown module 
key 'Magrathea: Glacier signing key: c7613364bc2aa19d70bf0c6e59bf8acaff65c879' 
err -11
  Mar 12 06:31:51 network kernel: [213747.867554] xfs: module verification 
failed: signature and/or  required key missing - tainting kernel
  Mar 12 06:31:51 network kernel: [213747.958590] SGI XFS with ACLs, security 
attributes, realtime, large block/inode numbers, no debug enabled
  Mar 12 06:31:51 network kernel: [213748.044351] Request for unknown module 
key 'Magrathea: Glacier signing key: c7613364bc2aa19d70bf0c6e59bf8acaff65c879' 
err -11
  Mar 12 06:31:51 network kernel: [213748.055870] JFS: nTxBlock = 8192, nTxLock 
= 65536
  Mar 12 06:31:51 network kernel: [213748.082768] Request for unknown module 
key 'Magrathea: Glacier signing key: c7613364bc2aa19d70bf0c6e59bf8acaff65c879' 
err -11
  Mar 12 06:31:51 network kernel: [213748.085263] Request for unknown module 
key 'Magrathea: Glacier signing key: c7613364bc2aa19d70bf0c6e59bf8acaff65c879' 
err -11
  Mar 12 06:31:51 network kernel: [213748.090305] NTFS driver 2.1.30 [Flags: 
R/O MODULE].
  Mar 12 06:31:51 network kernel: [213748.092232] Request for unknown module 
key 'Magrathea: Glacier signing key: c7613364bc2aa19d70bf0c6e59bf8acaff65c879' 
err -11
  Mar 12 06:31:51 network kernel: [213748.094614] Request for unknown module 
key 'Magrathea: Glacier signing key: c7613364bc2aa19d70bf0c6e59bf8acaff65c879' 
err -11
  Mar 12 06:31:51 network kernel: [213748.096672] Request for unknown module 
key 'Magrathea: Glacier signing key: c7613364bc2aa19d70bf0c6e59bf8acaff65c879' 
err -11
  Mar 12 06:31:51 network kernel: [213748.118238] Request for unknown module 
key 'Magrathea: Glacier signing key: c7613364bc2aa19d70bf0c6e59bf8acaff65c879' 
err -11
  Mar 12 06:31:51 network kernel: [213748.119378] QNX4 filesystem 0.2.3 
registered.
  Mar 12 06:31:51 network kernel: [213748.120663] Request for unknown module 
key 'Magrathea: Glacier signing key: c7613364bc2aa19d70bf0c6e59bf8acaff65c879' 
err -11
  Mar 12 06:31:51 network kernel: [213748.123118] Request for unknown module 
key 'Magrathea: Glacier signing key: c7613364bc2aa19d70bf0c6e59bf8acaff65c879' 
err -11
  Mar 12 06:31:51 network kernel: [213748.144586] xor: automatically using best 
checksumming function:
  Mar 12 06:31:51 network kernel: [213748.184004]avx   : 35873.000 
MB/sec
  Mar 12 06:31:51 network kernel: [213748.184139] Request for unknown module 
key 'Magrathea: Glacier signing key: c7613364bc2aa19d70bf0c6e59bf8acaff65c879' 
err -11
  Mar 12 06:31:51 network kernel: [213748.252009] raid6: sse2x1   11454 MB/s
  Mar 12 06:31:51 network kernel: [213748.320008] raid6: sse2x2   14362 MB/s
  Mar 12 06:31:51 network kernel: [213748.388007] raid6: sse2x4   16577 MB/s
  Mar 12 06:31:51 network kernel: [213748.456004] raid6: avx2x1   22081 MB/s
  Mar 12 06:31:51 network kernel: [213748.524006] raid6: avx2x2   25473 MB/s
  Mar 12 06:31:51 network kernel: [213748.592005] raid6: avx2x4   29788 MB/s
  Mar 12 06:31:51 network kernel: [213748.592006] raid6: using algorithm avx2x4 
(29788 MB/s)
  Mar 12 06:31:51 network kernel: [213748.592006] raid6: using avx2x2 recovery 
algorithm
  Mar 12 06:31:51 network kernel: [213748.609455] Request for unknown module 
key 'Magrathea: Glacier signing key: c7613364bc2aa19d70bf0c6e59bf8acaff65c879' 
err -11
  Mar 12 06:31:51 network kernel: [213748.626343] bio: create slab  at 1
  Mar 12 06:31:51 network kernel: [213748.660695] Btrfs loaded

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unattended-upgrades 0.82.1ubuntu2.1
  ProcVersionSignature: Ubuntu 3.13.0-46.77-generic 3.13.11-ckt15
  Uname: Linux 3.13.0-46-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  Date: Thu Mar 12 10:32:26 2015
  InstallationDate: Installed on 2014-12-20 (81 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
  PackageArchitecture: all
  SourcePackage: unattended-upgrades
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:

[Touch-packages] [Bug 1670959] Re: systemd-resolved using 100% CPU

2018-06-19 Thread Amir H Piri

I also trying confront with this problem, but there is no solution at all. I 
tried to disable the systemd-resolved service but after that my domain resolver 
stop working and I lost access to webpages. I also have dnsmasq. I don't know 
why but I think this service is come from Ubuntu 16.04.
I upgraded my Ubuntu from 16.04 to Ubuntu 17.10 and then upgrade it to 18.04. 
Maybe this is why the problem is created.

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

Title:
  systemd-resolved using 100% CPU

Status in dnsmasq package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Sometimes systemd-resolved process is using 100% CPU.
  After a while it changes back to normal.

  It happens usually after connecting to the (wifi) network, like
  starting the OS.

  strace output:

  sendmsg(12, {msg_name(16)={sa_family=AF_INET, sin_port=htons(33589), 
sin_addr=inet_addr("127.0.0.1")}, 
msg_iov(1)=[{"6\215\201\200\0\1\0\1\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\300\f\0\34\0\1\0\0\10\235\0\20&\6(\0\0024\0Y%L\4\6#f&\214\0\0)\377\326\0\0\0\0\0\0",
 81}], msg_controllen=28, [{cmsg_len=28, cmsg_level=SOL_IP, 
cmsg_type=IP_PKTINFO, {ipi_ifindex=if_nametoindex("lo"), 
ipi_spec_dst=inet_addr("127.0.0.53"), ipi_addr=inet_addr("127.0.0.53")}}], 
msg_flags=0}, 0) = 81
  sendmsg(3, {msg_name(0)=NULL, 
msg_iov(4)=[{"PRIORITY=6\nSYSLOG_FACILITY=3\nCODE_FILE=../src/resolve/resolved-dns-stub.c\nCODE_LINE=363\nCODE_FUNCTION=dns_stub_process_query\nSYSLOG_IDENTIFIER=systemd-resolved\n",
 160}, {"MESSAGE=", 8}, {"Processing query...", 19}, {"\n", 1}], 
msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 188
  epoll_wait(4, [{EPOLLIN, {u32=3176459184, u64=94565471415216}}], 16, -1) = 1
  clock_gettime(CLOCK_BOOTTIME, {44665, 938069872}) = 0
  recvfrom(12, NULL, 0, MSG_PEEK|MSG_TRUNC, NULL, NULL) = 53
  recvmsg(12, {msg_name(16)={sa_family=AF_INET, sin_port=htons(33589), 
sin_addr=inet_addr("127.0.0.1")}, 
msg_iov(1)=[{"Z\262\1\20\0\1\0\0\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\0\0)\2\0\0\0\0\0\0\0",
 3936}], msg_controllen=56, [{cmsg_len=28, cmsg_level=SOL_IP, 
cmsg_type=IP_PKTINFO, {ipi_ifindex=if_nametoindex("lo"), 
ipi_spec_dst=inet_addr("127.0.0.53"), ipi_addr=inet_addr("127.0.0.53")}}, 
{cmsg_len=20, cmsg_level=SOL_IP, cmsg_type=IP_TTL, {ttl=64}}], msg_flags=0}, 0) 
= 53
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  getrandom("\365I", 2, GRND_NONBLOCK)= 2
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  getrandom("\203;", 2, GRND_NONBLOCK)= 2
  clock_gettime(CLOCK_BOOTTIME, {44665, 938446937}) = 0
  open("/run/systemd/netif/links/3", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such 
file or directory)
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  socket(AF_INET, SOCK_DGRAM|SOCK_CLOEXEC|SOCK_NONBLOCK, IPPROTO_IP) = 18
  connect(18, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("127.0.0.1")}, 16) = 0
  epoll_ctl(4, EPOLL_CTL_ADD, 18, {EPOLLIN, {u32=3176610576, 
u64=94565471566608}}) = 0
  write(18, 
"\203;\1\20\0\1\0\0\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\0\0)\2\0\0\0\0\0\0\0",
 53) = 53
  clock_gettime(CLOCK_BOOTTIME, {44665, 938833717}) = 0
  clock_gettime(CLOCK_BOOTTIME, {44665, 938875138}) = 0
  epoll_ctl(4, EPOLL_CTL_DEL, 18, NULL)   = 0
  close(18)   = 0

  journalctl output:

  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:41 parsec dnsmasq[1545]: Maximum number of concurrent DNS 
queries reached (max: 150)

  As you can see, I would use it together with dnsmasq.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: systemd 232-18ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-9.11-generic 4.10.0
  Uname: Linux 4.10.0-9-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  Date: Wed Mar  8 08:20:18 2017
  MachineType: Hewlett-Packard HP EliteBook Folio 1020 G1
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.10.0-9-generic 
root=UUID=a54fe703-35d4-47ac-9c6e-4034421531fb ro rootflags=subvol=@
  SourcePackage: systemd
  UpgradeStatus:

[Touch-packages] [Bug 1554365] Re: UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 2886: ordinal not in range(128)

2018-06-19 Thread Balint Reczey

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

** This bug has been marked a duplicate of bug 1737635
   Invalid UTF-8 characters in dpkg's log crash unattended-upgrade.

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

Title:
  UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position
  2886: ordinal not in range(128)

Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  I got this in the mail:

  From: Cron Daemon 
  To: root@...
  Subject: Cron  test -x /usr/sbin/anacron || ( cd / && 
run-parts --report /etc/cron.daily )
  Date: Thu, 25 Feb 2016 02:11:47 +0200 (EET)

  /etc/cron.daily/apt:
  Traceback (most recent call last):
File "/usr/bin/unattended-upgrade", line 1255, in 
  main(options)
File "/usr/bin/unattended-upgrade", line 1205, in main
  pkgs, pkg_install_success, pkgs_kept_back, mem_log, logfile_dpkg)
File "/usr/bin/unattended-upgrade", line 752, in send_summary_mail
  body += fp.read()
File "/usr/lib/python3.4/encodings/ascii.py", line 26, in decode
  return codecs.ascii_decode(input, self.errors)[0]
  UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 
2886: ordinal not in range(128)

  According to /var/log/apt/history.log.1.gz, the packages upgraded that
  day were

  Start-Date: 2016-02-25  02:06:22
  Upgrade: libgnutls-openssl27:amd64 (2.12.23-12ubuntu2.4, 
2.12.23-12ubuntu2.5), libssl1.0.0:amd64 (1.0.1f-1ubuntu2.16, 
1.0.1f-1ubuntu2.17), libvirt0:amd64 (1.2.2-0ubuntu13.1.16, 
1.2.2-0ubuntu13.1.17), libssl-dev:amd64 (1.0.1f-1ubuntu2.16, 
1.0.1f-1ubuntu2.17), ca-certificates:amd64 (20141019ubuntu0.14.04.1, 
20160104ubuntu0.14.04.1), libgnutls26:amd64 (2.12.23-12ubuntu2.4, 
2.12.23-12ubuntu2.5), libssl-doc:amd64 (1.0.1f-1ubuntu2.16, 
1.0.1f-1ubuntu2.17), openssl:amd64 (1.0.1f-1ubuntu2.16, 1.0.1f-1ubuntu2.17)
  End-Date: 2016-02-25  02:06:36

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unattended-upgrades 0.82.1ubuntu2.4
  Uname: Linux 2.6.32-042stab108.8 x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  Date: Tue Mar  8 08:26:05 2016
  PackageArchitecture: all
  ProcEnviron:
   LC_CTYPE=lt_LT.UTF-8
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=lt_LT.UTF-8
   SHELL=/bin/bash
  SourcePackage: unattended-upgrades
  UpgradeStatus: Upgraded to trusty on 2016-02-06 (30 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1554365/+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 1777648] [NEW] rastertoepson filter crashes with paper size A6

2018-06-19 Thread Frank Polte

Public bug reported:

There is/was a buffer boundary problem in the rastertoepson filter
coming with cups, which only affects A6 paper size on any Linux.

The filter crashes at the end of the first page and leaves the dot
matrix printer in an non-reseted state. This leaves to several problems
later.

Because it is a Memory Management Bug and CUPS is a security sensitive
package, this may even lead to security issues.

I already filed the bug upstream and there it was fixed within one week.

https://github.com/apple/cups/issues/5323

Please backport the fixes:
https://github.com/apple/cups/commit/0dd6c36be918fe1d3c216a1c168277f37908c465
and
https://github.com/apple/cups/commit/7e041a5e5569fdb339906eeb00e6706d562e228a

to the cups package.

Any information and files needed are in the github issue mentioned
above.

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

** Information type changed from Private Security to Public

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

Title:
  rastertoepson filter crashes with paper size A6

Status in cups package in Ubuntu:
  New

Bug description:
  There is/was a buffer boundary problem in the rastertoepson filter
  coming with cups, which only affects A6 paper size on any Linux.

  The filter crashes at the end of the first page and leaves the dot
  matrix printer in an non-reseted state. This leaves to several
  problems later.

  Because it is a Memory Management Bug and CUPS is a security sensitive
  package, this may even lead to security issues.

  I already filed the bug upstream and there it was fixed within one
  week.

  https://github.com/apple/cups/issues/5323

  Please backport the fixes:
  https://github.com/apple/cups/commit/0dd6c36be918fe1d3c216a1c168277f37908c465
  and
  https://github.com/apple/cups/commit/7e041a5e5569fdb339906eeb00e6706d562e228a

  to the cups package.

  Any information and files needed are in the github issue mentioned
  above.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1777648/+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 1777099] Re: [backport] DRM devices opened by logind stay referenced indefinitely by PID 1

2018-06-19 Thread Ubuntu Foundations Team Bug Bot

** Tags added: patch

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

Title:
  [backport] DRM devices opened by logind stay referenced indefinitely
  by PID 1

Status in OEM Priority Project:
  New
Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Bionic:
  In Progress

Bug description:
  refer to https://github.com/systemd/systemd/issues/6908

  we need that solution to make NVIDIA dGPU switching works.

  impacted issue:
  https://bugs.launchpad.net/somerville/+bug/1774326

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1777099/+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 1759628] Re: bluez regression: Bluetooth audio fails to reconnect after resume

This bug was fixed in the package bluez - 5.50-0ubuntu1

---
bluez (5.50-0ubuntu1) cosmic; urgency=medium

* New upstream release 5.50:
- Fix issue with GATT and reading long values.
- Fix issue with GATT and reading multiple includes.
- Fix issue with GATT and service changes when offline.
- Fix issue with handling secondary service discovery.
- Fix issue with handling persistency of CCC values.
- Fix issue with handling Mesh session on disconnection.
- Fix issue with handling Mesh proxy PDU SAR message length.
- Fix issue with handling Mesh default heartbeat TTL value.
- Add support for Mesh node-reset operation handling.
- Add support for GATT authorization request handling.
- Add support for GATT minimum key size requirements.
- Add support for GATT server and included services.
- Add support for handling additional advertising data.
- Add support for handling separate discoverable state.
- Add support for enabling HFP version 1.7 features.
- Add support for dedicated Bluetooth logging daemon.
* Refreshed debian/patches to work with 5.50 and apply cleanly.
* Fixed lintian errors:
- dpkg-maintscript-helper missing in postinst and postrm.
- Synchronized (some) man pages from Debian.
* New upstream release 5.49 (LP: #1759961):
- Fix issue with configuring discoverable advertising flag.
- Fix issue with bearer selection and single mode controllers.
- Fix issue with Connect and ConnectProfile returning in progress.
- Fix issue with missing Paired property change when not bonded.
- Fix issue with storage for controllers without public address.
- Fix issue with handling AVCTP disconnecting the channel queue.
- Fix issue with not clearing connectable setting on power off.
- Fix issue with creating multiple mgmt socket instances.
- Fix issue with GATT server and BR/EDR only devices.
- Fix issue with InterfaceAdded event ordering. (LP: #1759628)
- Add support for generic ConnectDevice method call.
- Add support for Mesh heartbeat client functionality.
* Drop upstreamed patch:
- fix-lp1750308-upstream-commit-1bf03369.patch

-- Daniel van Vugt Wed, 06 Jun 2018
16:26:40 +0800

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

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

Title:
bluez regression: Bluetooth audio fails to reconnect after resume

Status in bluez package in Ubuntu:
Fix Released
Status in bluez package in Fedora:
Fix Released
Status in Suse:
Fix Released

Bug description:
STEPS TO REPRODUCE:
1. Connect to Bluetooth audio device
2. Suspend & Resume
3. Reconnect to Bluetooth device.

This regression in bluez 5.48 has already been identified and fixed
upstream. Report is here and patch is here

Syslog reports messages as follows when this issue is happening (I have
replaced my device's MAC address with [MAC]):
Mar 28 12:34:29 cue pulseaudio[1859]: [pulseaudio] bluez5-util.c: Information
about device /org/bluez/hci0/dev_[MAC] is invalid
Mar 28 12:34:29 cue bluetoothd[984]: Endpoint replied with an error:
org.bluez.Error.InvalidArguments
Mar 28 12:34:33 cue pulseaudio[1859]: [pulseaudio] bluez5-util.c: Information
about device /org/bluez/hci0/dev_[MAC] is invalid
Mar 28 12:34:33 cue bluetoothd[984]: Endpoint replied with an error:
org.bluez.Error.InvalidArguments

Workaround is to run sudo systemctl restart bluetooth after resume.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: bluez 5.48-0ubuntu3
ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
Uname: Linux 4.15.0-12-generic x86_64
ApportVersion: 2.20.9-0ubuntu1
Architecture: amd64
CurrentDesktop: KDE
Date: Wed Mar 28 12:37:11 2018
InstallationDate: Installed on 2018-03-23 (5 days ago)
InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64
(20180306.1)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: Hewlett-Packard HP ProBook 640 G1
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic
root=/dev/mapper/internal-root ro quiet splash vt.handoff=1
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/25/2018
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: L78 Ver. 01.43
dmi.board.name: 2101
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 16.3C
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias:
dmi:bvnHewlett-Packard:bvrL78Ver.01.43:bd01/25/2018:svnHewlett-Packard:pnHPProBook640G1:pvrA3009DD10303:rvnHewlett-Packard:rn2101:rvrKBCVersion16.3C:cvnHewlett-Packard:ct10:cvr:

[Touch-packages] [Bug 1759961] Re: Update to bluez 5.50

This bug was fixed in the package bluez - 5.50-0ubuntu1

---
bluez (5.50-0ubuntu1) cosmic; urgency=medium

  * New upstream release 5.50:
- Fix issue with GATT and reading long values.
- Fix issue with GATT and reading multiple includes.
- Fix issue with GATT and service changes when offline.
- Fix issue with handling secondary service discovery.
- Fix issue with handling persistency of CCC values.
- Fix issue with handling Mesh session on disconnection.
- Fix issue with handling Mesh proxy PDU SAR message length.
- Fix issue with handling Mesh default heartbeat TTL value.
- Add support for Mesh node-reset operation handling.
- Add support for GATT authorization request handling.
- Add support for GATT minimum key size requirements.
- Add support for GATT server and included services.
- Add support for handling additional advertising data.
- Add support for handling separate discoverable state.
- Add support for enabling HFP version 1.7 features.
- Add support for dedicated Bluetooth logging daemon.
  * Refreshed debian/patches to work with 5.50 and apply cleanly.
  * Fixed lintian errors:
- dpkg-maintscript-helper missing in postinst and postrm.
- Synchronized (some) man pages from Debian.
  * New upstream release 5.49 (LP: #1759961):
- Fix issue with configuring discoverable advertising flag.
- Fix issue with bearer selection and single mode controllers.
- Fix issue with Connect and ConnectProfile returning in progress.
- Fix issue with missing Paired property change when not bonded.
- Fix issue with storage for controllers without public address.
- Fix issue with handling AVCTP disconnecting the channel queue.
- Fix issue with not clearing connectable setting on power off.
- Fix issue with creating multiple mgmt socket instances.
- Fix issue with GATT server and BR/EDR only devices.
- Fix issue with InterfaceAdded event ordering. (LP: #1759628)
- Add support for generic ConnectDevice method call.
- Add support for Mesh heartbeat client functionality.
  * Drop upstreamed patch:
- fix-lp1750308-upstream-commit-1bf03369.patch

 -- Daniel van Vugt   Wed, 06 Jun 2018
16:26:40 +0800

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

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

Title:
  Update to bluez 5.50

Status in bluez package in Ubuntu:
  Fix Released

Bug description:
  From upstream:
  http://www.bluez.org/release-of-bluez-5-49/

  Release of BlueZ 5.49

  This is mostly a bug fix release, with fixes to features such as
  AVCTP, OBEX, GATT and Mesh. There are however some notable new
  features also, such as improved heartbeat management support in
  meshctl as well as a new experimental ConnectDevice D-Bus method on
  the Adapter interface, which can be used for quick device object
  creation for testing purpose or when information about the device has
  been received over some Out-of-Band channel.

  Upstream changelog:
  https://git.kernel.org/pub/scm/bluetooth/bluez.git/tree/ChangeLog

  ver 5.49:
Fix issue with configuring discoverable advertising flag.
Fix issue with bearer selection and single mode controllers.
Fix issue with Connect and ConnectProfile returning in progress.
Fix issue with missing Paired property change when not bonded.
Fix issue with storage for controllers without public address.
Fix issue with handling AVCTP disconnecting the channel queue.
Fix issue with not clearing connectable setting on power off.
Fix issue with creating multiple mgmt socket instances.
Fix issue with GATT server and BR/EDR only devices.
Fix issue with InterfaceAdded event ordering.
Add support for generic ConnectDevice method call.
Add support for Mesh heartbeat client functionality.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1759961/+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 1777099] Re: [backport] DRM devices opened by logind stay referenced indefinitely by PID 1

2018-06-19 Thread Alberto Milone

Attaching the debdiff

** Patch added: "systemd_237-3ubuntu10.2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1777099/+attachment/5154277/+files/systemd_237-3ubuntu10.2.debdiff

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

Title:
  [backport] DRM devices opened by logind stay referenced indefinitely
  by PID 1

Status in OEM Priority Project:
  New
Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Bionic:
  In Progress

Bug description:
  refer to https://github.com/systemd/systemd/issues/6908

  we need that solution to make NVIDIA dGPU switching works.

  impacted issue:
  https://bugs.launchpad.net/somerville/+bug/1774326

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1777099/+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 1777634] [NEW] no more than 1 GATT descriptor allowed

2018-06-19 Thread Nicolas SAINTE-CROIX

Public bug reported:

By running the example-gatt-server and example-gatt-advertising,
it was impossible to get more than one Descriptor per characteristic.
if i comment one i can see the other in the test characteristic.
but if i set both, it just act like no descriptor available.

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


** Tags: gatt server

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

Title:
  no more than 1 GATT descriptor allowed

Status in bluez package in Ubuntu:
  New

Bug description:
  By running the example-gatt-server and example-gatt-advertising,
  it was impossible to get more than one Descriptor per characteristic.
  if i comment one i can see the other in the test characteristic.
  but if i set both, it just act like no descriptor available.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1777634/+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 1777633] [NEW] Xorg Out of Range with VGA native resolution

2018-06-19 Thread Pasi Grönqvist

Public bug reported:

This bug is related to Bug 1777621 with 17.10

pg@pg-desktop:~$ xrandr 
Screen 0: minimum 320 x 200, current 2304 x 1024, maximum 8192 x 8192
VGA-1 connected primary 1024x768+1280+0 (normal left inverted right x axis y 
axis) 0mm x 0mm
   1024x768  60.00* 
   800x600   60.3256.25  
   848x480   60.00  
   640x480   59.94  
HDMI-1 connected 1280x1024+0+0 (normal left inverted right x axis y axis) 376mm 
x 301mm
   1280x1024 60.02*+  76.0075.0272.05  
   1152x864  75.00  
   1024x768  75.0370.0760.00  
   832x624   74.55  
   800x600   72.1975.0060.32  
   640x480   75.0072.8166.6759.94  
   720x400   70.08  
   640x350   70.07  
HDMI-2 disconnected (normal left inverted right x axis y axis)
  1280x1024_60.00 (0x120) 109.000MHz -HSync +VSync
h: width  1280 start 1368 end 1496 total 1712 skew0 clock  63.67KHz
v: height 1024 start 1027 end 1034 total 1063   clock  59.89Hz
pg@pg-desktop:~$ xrandr --newmode 1280x1024_40.00   69.75  1280 1336 1472 1664  
1024 1025 1028 1048  -HSync +Vsync
pg@pg-desktop:~$ xrandr --verbose --addmode VGA-1 1280x1024_40.00
pg@pg-desktop:~$ xrandr --verbose --output VGA-1 --mode 1280x1024_40.00
screen 0: 2560x1024 677x271 mm  95.98dpi
crtc 0: 1280x1024_40.00  40.00 +1280+0 "VGA-1"
pg@pg-desktop:~$ 
=>
VGA-1 Out of Range!

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Uname: Linux 4.15.0-23-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Jun 19 14:37:03 2018
DistUpgraded: 2018-06-19 13:58:44,011 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0402] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: ASRock Incorporation Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [1849:0402]
InstallationDate: Installed on 2017-09-28 (264 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=32b56d21-8cb0-4fcd-8f39-bdee0a192558 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to bionic on 2018-06-19 (0 days ago)
dmi.bios.date: 12/06/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P2.10
dmi.board.name: B85M
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.10:bd12/06/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB85M:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Sun Jun 17 11:33:00 2018
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.5-0ubuntu2~16.04.1
xserver.video_driver: radeon

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


** Tags: amd64 apport-bug bionic false-gpu-hang freeze ubuntu

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

Title:
  Xorg Out of Range with VGA native resolution

Status in xorg package in Ubuntu:
  New

Bug description:
  This bug is related to Bug 1777621 with 17.10

  pg@pg-desktop:~$ xrandr 
  Screen 0: minimum 320 x 200, current 2304 x 1024, maximum 8192 x 8192
  VGA-1 connected primary 1024x768+1280+0 (normal left inverted right x axis y 
axis) 0mm x 0mm
 1024x768

[Touch-packages] [Bug 1751006] Re: Journalctl compiled without pattern matching support, pcre2 is not in main

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

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

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

Title:
  Journalctl compiled without pattern matching support, pcre2 is not in
  main

Status in pcre2 package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Please add pattern matching support to journalctl.  At the moment, the
  -g (--grep) option as described in the man page doesn't work:

  ╰─▶ journalctl --grep=xhci-hcd 
  Compiled without pattern matching support

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcre2/+bug/1751006/+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 1777579] Re: 18.04 Dekstop LTS DNS behavior (systemd-resolved)

2018-06-19 Thread Paul White

** Package changed: ubuntu => systemd (Ubuntu)

** Tags added: bionic

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

Title:
  18.04 Dekstop LTS DNS behavior (systemd-resolved)

Status in systemd package in Ubuntu:
  New

Bug description:
  Hi,

  I am using te latest Ubuntu Mate Desktop 18.04 LTS release and have issues 
getting local DNS to work.
  In my network I maintain a central router instance that povides DHCP and DNS 
successfully over many years. The DHCP assigns a valid address and correct DNS 
information to my above mentioned network client. However DNS resolution does 
not work for DNS records maintained in my router for my local network.
  See here: (local DNS server on .3.1)

  uho@Asus:~/Schreibtisch$ systemd-resolve --status
  Global
DNSSEC NTA: 10.in-addr.arpa
16.172.in-addr.arpa
168.192.in-addr.arpa
17.172.in-addr.arpa
18.172.in-addr.arpa
19.172.in-addr.arpa
20.172.in-addr.arpa
21.172.in-addr.arpa
22.172.in-addr.arpa
23.172.in-addr.arpa
24.172.in-addr.arpa
25.172.in-addr.arpa
26.172.in-addr.arpa
27.172.in-addr.arpa
28.172.in-addr.arpa
29.172.in-addr.arpa
30.172.in-addr.arpa
31.172.in-addr.arpa
corp
d.f.ip6.arpa
home
internal
intranet
lan
local
private
test

  Link 2 (wlp2s0)
Current Scopes: DNS
 LLMNR setting: yes
  MulticastDNS setting: no
DNSSEC setting: no
  DNSSEC supported: no
   DNS Servers: 192.168.3.1
  uho@Asus:~/Schreibtisch$ 

  uho@Asus:~/Schreibtisch$ nslookup filou
  Server:   127.0.0.53
  Address:  127.0.0.53#53

  ** server can't find filou: SERVFAIL

  uho@Asus:~/Schreibtisch$ nslookup filou 192.168.3.1
  Server:   192.168.3.1
  Address:  192.168.3.1#53

  Non-authoritative answer:
  Name: filou
  Address: 192.168.3.10

  uho@Asus:~/Schreibtisch$ nslookup 192.168.3.10
  10.3.168.192.in-addr.arpa name = filou.

  Authoritative answers can be found from:

  uho@Asus:~/Schreibtisch$

  The example above shows that DNS forward lookup for "filou" does not work, 
only reverse lookup works.
  The same behavior with explicit DNS setting in network manager.

  Any idea what's wrong? To me this looks weirdly broken.

  BTW: Old school setting in /etc/resolv.conf works like a charm.

  BR
  Uwe

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1777579/+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 1777579] [NEW] 18.04 Dekstop LTS DNS behavior (systemd-resolved)

You have been subscribed to a public bug:

Hi,

I am using te latest Ubuntu Mate Desktop 18.04 LTS release and have issues 
getting local DNS to work.
In my network I maintain a central router instance that povides DHCP and DNS 
successfully over many years. The DHCP assigns a valid address and correct DNS 
information to my above mentioned network client. However DNS resolution does 
not work for DNS records maintained in my router for my local network.
See here: (local DNS server on .3.1)

uho@Asus:~/Schreibtisch$ systemd-resolve --status
Global
  DNSSEC NTA: 10.in-addr.arpa
  16.172.in-addr.arpa
  168.192.in-addr.arpa
  17.172.in-addr.arpa
  18.172.in-addr.arpa
  19.172.in-addr.arpa
  20.172.in-addr.arpa
  21.172.in-addr.arpa
  22.172.in-addr.arpa
  23.172.in-addr.arpa
  24.172.in-addr.arpa
  25.172.in-addr.arpa
  26.172.in-addr.arpa
  27.172.in-addr.arpa
  28.172.in-addr.arpa
  29.172.in-addr.arpa
  30.172.in-addr.arpa
  31.172.in-addr.arpa
  corp
  d.f.ip6.arpa
  home
  internal
  intranet
  lan
  local
  private
  test

Link 2 (wlp2s0)
  Current Scopes: DNS
   LLMNR setting: yes
MulticastDNS setting: no
  DNSSEC setting: no
DNSSEC supported: no
 DNS Servers: 192.168.3.1
uho@Asus:~/Schreibtisch$ 

uho@Asus:~/Schreibtisch$ nslookup filou
Server: 127.0.0.53
Address:127.0.0.53#53

** server can't find filou: SERVFAIL

uho@Asus:~/Schreibtisch$ nslookup filou 192.168.3.1
Server: 192.168.3.1
Address:192.168.3.1#53

Non-authoritative answer:
Name:   filou
Address: 192.168.3.10

uho@Asus:~/Schreibtisch$ nslookup 192.168.3.10
10.3.168.192.in-addr.arpa   name = filou.

Authoritative answers can be found from:

uho@Asus:~/Schreibtisch$

The example above shows that DNS forward lookup for "filou" does not work, only 
reverse lookup works.
The same behavior with explicit DNS setting in network manager.

Any idea what's wrong? To me this looks weirdly broken.

BTW: Old school setting in /etc/resolv.conf works like a charm.

BR
Uwe

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


** Tags: bot-comment
-- 
18.04 Dekstop LTS DNS behavior (systemd-resolved)
https://bugs.launchpad.net/bugs/1777579
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to systemd in Ubuntu.

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

[Touch-packages] [Bug 1768610] Re: leftover conffile forces GNOME is software rendering

2018-06-19 Thread Iain Lane

Cheers!

My nux-tools review comments apply to x11-common too. The following are
for x11-common:

What's the reason for doing this in preinst rather than postinst
configure? It's fine in this case but usually we do things in postinst
where possible.

What about adding a "Breaks: nux-tools (<<
4.0.8+18.04.20180613.5-0ubuntu1)" to x11-common, and making the script
not do the fix up if we're upgrading from the new version ("if dpkg
--compare-versions "${2}" lt 1:7.7+19ubuntu8; then do stuff; fi")?

I think it's a good idea generally to make fix up actions in maintainer
scripts strictly limited to certain package versions and this will mean
if you still have nux-tools installed you have to upgrade it to the
fixed version, so the removal can only have happened earlier than
x11-common 1:7.7+19ubuntu8.

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

Title:
  leftover conffile forces GNOME is software rendering

Status in nux package in Ubuntu:
  Fix Released
Status in xorg package in Ubuntu:
  In Progress
Status in nux source package in Xenial:
  Fix Committed
Status in xorg source package in Xenial:
  Confirmed
Status in nux source package in Artful:
  Fix Committed
Status in xorg source package in Artful:
  Confirmed
Status in nux source package in Bionic:
  Fix Committed
Status in xorg source package in Bionic:
  In Progress

Bug description:
  [ Impact ]

  GNOME shell and other 3D programs run using software rendering after
  unity removal.

  This SRU covers only the upgrade case or if nux-tools removal happens
  after this update, for people who already upgraded and in broken state
  another SRU will follow.

  [ Test case ]

  · Install xenial
  · Upgrade to bionic or artful
    (assuming you're using a GNOME session)
  · sudo apt remove nux-tools
  · log into your session
  . From terminal:
    - printenv LIBGL_ALWAYS_SOFTWARE
    Should print nothing (and return an error)

  Same should happen if you don't remove nux-tools but you change
  `/usr/lib/nux/unity_support_test` not to run properly (replace with a script 
exiting 1), but you're running a GNOME session.

  · If running Unity session instead, ensure that
printenv LIBGL_ALWAYS_SOFTWARE equals 1 in case that you're running
in an environment with no 3d support (VMs are easy tests)

  [ Regression Potential ]

  Unity desktops with no 3d support could not start anymore.

  ===

  After an upgrade from 17.10 to 18.04, I noticed that all gnome windows
  animations were gone.  After some digging, it seems that gnome-session
  incorrectly assumes that my graphics has no acceleration, when in fact
  it does: it's a i5-2520M CPU @ 2.50GHz with Intel integrated graphics
  (i915 driver).

  I've tried this with and without the xserver-xorg-video-intel package
  (a.k.a. Intel driver) with the same behavior.

  The output of gnome-session-check-accelerated is: llvmpipe (LLVM 6.0,
  256 bits)  however the system should have DRM 2.0 capability.

  GL checks (e.g. glxinfo, glxgears produce the expected output from a
  working DRM system).

  mesa-utils and mesa-utils-extra are both installed.

  I can't find a work around.  Perhaps there is something wrong with my
  install/upgrade?

  Everything else works fine, although the graphical transitions are no
  longer smooth.  But it would be nice to restore the expected behavior.

  I have attached the log of 'journalctl -b0'

  ProblemType: BugDistroRelease: Ubuntu 18.04
  Package: gnome-session 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May  2 13:06:00 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-22 (739 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bashSourcePackage: gnome-session
  UpgradeStatus: Upgraded to bionic on 2018-04-27 (5 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nux/+bug/1768610/+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 1770166] Re: The brightness of the notebook

2018-06-19 Thread Adrian

1-in previous versions if it worked, install ubuntu 18 and it does not work.
2-I'm on it

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

Title:
  The brightness of the notebook

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  The brightness of the notebook does not lower or rise with the FN key. Acer 
Aspire 5742 i3-380m 6gb ram ssd kingston 120gb.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroRelease: Ubuntu 18.04
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Core Processor Integrated Graphics 
Controller [1025:0487]
  InstallationDate: Installed on 2018-06-14 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Acer Aspire 5742
  Package: xorg 1:7.7+19ubuntu7
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=921bc593-7a3c-4ced-8659-695cfe311ce9 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Tags:  bionic ubuntu
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/14/2011
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.18
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Aspire 5742
  dmi.board.vendor: Acer
  dmi.board.version: V1.18
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.18
  dmi.modalias: 
dmi:bvnAcer:bvrV1.18:bd03/14/2011:svnAcer:pnAspire5742:pvrV1.18:rvnAcer:rnAspire5742:rvrV1.18:cvnAcer:ct10:cvrV1.18:
  dmi.product.family: Intel_Mobile
  dmi.product.name: Aspire 5742
  dmi.product.version: V1.18
  dmi.sys.vendor: Acer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1770166/+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 1777621] Re: xrandr fails to change into the native resolution, useless setup whitout Wayland

** Description changed:

- 
- Hello 
- I have found bugs from Ubuntu 18.04  (form 16.04 by do-release-upgrade)
+ Hello
+ I have found bugs from Ubuntu 17.10  (form 16.04 by do-release-upgrade)
  a) xrandr fails to change into native resolution
  b) disabling Wayland cause “Out of Range” → can’t login at all (no login via 
HDMI or virtual TTY:s)
  c) X fails to detect old VGA monitor (ViewSonic VA902) native resolution 
(this is a persistent bug)
  
  I have used dual monitor setup over a decade, started with Etch and
  turned into Ubuntu some years ago. First monitor is connected via HDMI
  and second one by VGA. During Ubuntu installations/updates resolution
  has been problem, with xrandr etc I have managed situation until now.
  
  I have tested:
  1) 16.04 & Radeon works OK with 60 Hz VGA modeline
  2) 18.04 & Radeon: HDMI is OK but VGA  cant’t go into the native resolution
  3) 18.04 & Intel: HDMI is OK but VGA  cant’t go into the native resolution
  4) 18.04 & Radeon VGA without Wayland is Out of Range and useless
  5) 18.04 & Intel & xrandr with “easy” modeline do not work
  6) 18.04 & Radeon  & xrandr with “easy” modeline do not work
-  
  
  pg@pg-desktop:~$ xrandr --newmode 1280x1024_40.00   69.75  1280 1336 1472 
1664  1024 1025 1028 1048  -HSync +Vsync
  pg@pg-desktop:~$ xrandr --verbose --addmode XWAYLAND1 1280x1024_40.00
  pg@pg-desktop:~$ xrandr --verbose --output XWAYLAND1 --mode 1280x1024_40.00
  screen 0: 2560x1024 677x271 mm  95.98dpi
  crtc 1: 1280x1024_40.00  40.00 +1280+0 "XWAYLAND1"
  xrandr: Configure crtc 1 failed
  crtc 0: disable
  crtc 1: disable
  screen 0: revert
  crtc 0: revert
  crtc 1: revert
  
  pg@pg-desktop:~$ lspci -k | grep -iEA5 'vga|3d|display'
  00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen 
Core Processor Integrated Graphics Controller (rev 06)
-   Subsystem: ASRock Incorporation Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller
-   Kernel driver in use: i915
-   Kernel modules: i915
+  Subsystem: ASRock Incorporation Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller
+  Kernel driver in use: i915
+  Kernel modules: i915
  00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core 
Processor HD Audio Controller (rev 06)
-   Subsystem: ASRock Incorporation Xeon E3-1200 v3/4th Gen Core Processor 
HD Audio Controller
+  Subsystem: ASRock Incorporation Xeon E3-1200 v3/4th Gen Core Processor HD 
Audio Controller
  
  pg@pg-desktop:~$ more /var/log/Xorg.0.log | grep EE
-   (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
+  (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
  pg@pg-desktop:~$ more /var/log/Xorg.0.log | grep WW
-   (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
+  (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
  [ 4.672] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not 
exist.
  [ 4.672] (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist.
  [ 4.672] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist.
  [ 4.672] (WW) The directory "/usr/share/fonts/X11/100dpi" does not exist.
  [ 4.672] (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist.
  [ 4.852] (WW) Falling back to old probe method for modesetting
  [ 4.853] (WW) Falling back to old probe method for fbdev
  [ 4.853] (WW) Falling back to old probe method for vesa
  pg@pg-desktop:~$ uname -a
  Linux pg-desktop 4.13.0-45-generic #50-Ubuntu SMP Wed May 30 08:23:18 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux
  
  Also fails with separate Radeon GPU:
  [ 4.904] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
  [ 4.904] (II) FBDEV: driver for framebuffer: fbdev
  [ 4.904] (II) VESA: driver for VESA chipsets: vesa
  [ 4.931] (II) [KMS] Kernel modesetting enabled.
  [ 4.931] (WW) Falling back to old probe method for modesetting
  [ 4.931] (WW) Falling back to old probe method for fbdev
  [ 4.931] (II) Loading sub module "fbdevhw"
  [ 4.931] (II) LoadModule: "fbdevhw"
  [ 4.931] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
  [ 4.931] (II) Module fbdevhw: vendor="X.Org Foundation"
  [ 4.931]  compiled for 1.19.5, module version = 0.0.2
  [ 4.931]  ABI class: X.Org Video Driver, version 23.0
  [ 4.931] (WW) Falling back to old probe method for vesa
  [ 4.931] (II) RADEON(0): Creating default Display subsection in Screen 
section
-   "Default Screen Section" for depth/fbbpp 24/32
+  "Default Screen Section" for depth/fbbpp 24/32
  [ 4.931] (==) RADEON(0): Depth 24, (--) framebuffer bpp 32
  [ 4.931] (II) RADEON(0): Pixel depth = 24 bits stored in 4 bytes (32 bpp 
pixmaps)
  [ 4.931] (==) RADEON(0): Default visual is TrueColor
  [ 4.931] (==) RADEON(0): RGB weight 888
  [ 4.931] (II) RADEON(0): Using 8 bits per RGB (8 bit DAC)
  [ 4.931] (--) RADEON(0): Chipset: "ATI Radeon HD

[Touch-packages] [Bug 1759961] Re: Update to bluez 5.50

2018-06-19 Thread Sebastien Bacher

** Changed in: bluez (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  Update to bluez 5.50

Status in bluez package in Ubuntu:
  Fix Committed

Bug description:
  From upstream:
  http://www.bluez.org/release-of-bluez-5-49/

  Release of BlueZ 5.49

  This is mostly a bug fix release, with fixes to features such as
  AVCTP, OBEX, GATT and Mesh. There are however some notable new
  features also, such as improved heartbeat management support in
  meshctl as well as a new experimental ConnectDevice D-Bus method on
  the Adapter interface, which can be used for quick device object
  creation for testing purpose or when information about the device has
  been received over some Out-of-Band channel.

  Upstream changelog:
  https://git.kernel.org/pub/scm/bluetooth/bluez.git/tree/ChangeLog

  ver 5.49:
Fix issue with configuring discoverable advertising flag.
Fix issue with bearer selection and single mode controllers.
Fix issue with Connect and ConnectProfile returning in progress.
Fix issue with missing Paired property change when not bonded.
Fix issue with storage for controllers without public address.
Fix issue with handling AVCTP disconnecting the channel queue.
Fix issue with not clearing connectable setting on power off.
Fix issue with creating multiple mgmt socket instances.
Fix issue with GATT server and BR/EDR only devices.
Fix issue with InterfaceAdded event ordering.
Add support for generic ConnectDevice method call.
Add support for Mesh heartbeat client functionality.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1759961/+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 1777621] Re: xrandr fails to change into the native resolution, useless setup whitout Wayland

2018-06-19 Thread Pasi Grönqvist

I made mistake with update, want 18.04 but got 17.10 and don't recognize
it!

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

Title:
  xrandr fails to change into the native resolution, useless setup
  whitout Wayland

Status in xorg package in Ubuntu:
  New

Bug description:
  
  Hello 
  I have found bugs from Ubuntu 18.04  (form 16.04 by do-release-upgrade)
  a) xrandr fails to change into native resolution
  b) disabling Wayland cause “Out of Range” → can’t login at all (no login via 
HDMI or virtual TTY:s)
  c) X fails to detect old VGA monitor (ViewSonic VA902) native resolution 
(this is a persistent bug)

  I have used dual monitor setup over a decade, started with Etch and
  turned into Ubuntu some years ago. First monitor is connected via HDMI
  and second one by VGA. During Ubuntu installations/updates resolution
  has been problem, with xrandr etc I have managed situation until now.

  I have tested:
  1) 16.04 & Radeon works OK with 60 Hz VGA modeline
  2) 18.04 & Radeon: HDMI is OK but VGA  cant’t go into the native resolution
  3) 18.04 & Intel: HDMI is OK but VGA  cant’t go into the native resolution
  4) 18.04 & Radeon VGA without Wayland is Out of Range and useless
  5) 18.04 & Intel & xrandr with “easy” modeline do not work
  6) 18.04 & Radeon  & xrandr with “easy” modeline do not work
   

  pg@pg-desktop:~$ xrandr --newmode 1280x1024_40.00   69.75  1280 1336 1472 
1664  1024 1025 1028 1048  -HSync +Vsync
  pg@pg-desktop:~$ xrandr --verbose --addmode XWAYLAND1 1280x1024_40.00
  pg@pg-desktop:~$ xrandr --verbose --output XWAYLAND1 --mode 1280x1024_40.00
  screen 0: 2560x1024 677x271 mm  95.98dpi
  crtc 1: 1280x1024_40.00  40.00 +1280+0 "XWAYLAND1"
  xrandr: Configure crtc 1 failed
  crtc 0: disable
  crtc 1: disable
  screen 0: revert
  crtc 0: revert
  crtc 1: revert

  pg@pg-desktop:~$ lspci -k | grep -iEA5 'vga|3d|display'
  00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen 
Core Processor Integrated Graphics Controller (rev 06)
Subsystem: ASRock Incorporation Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller
Kernel driver in use: i915
Kernel modules: i915
  00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core 
Processor HD Audio Controller (rev 06)
Subsystem: ASRock Incorporation Xeon E3-1200 v3/4th Gen Core Processor 
HD Audio Controller

  pg@pg-desktop:~$ more /var/log/Xorg.0.log | grep EE
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
  pg@pg-desktop:~$ more /var/log/Xorg.0.log | grep WW
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
  [ 4.672] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not 
exist.
  [ 4.672] (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist.
  [ 4.672] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist.
  [ 4.672] (WW) The directory "/usr/share/fonts/X11/100dpi" does not exist.
  [ 4.672] (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist.
  [ 4.852] (WW) Falling back to old probe method for modesetting
  [ 4.853] (WW) Falling back to old probe method for fbdev
  [ 4.853] (WW) Falling back to old probe method for vesa
  pg@pg-desktop:~$ uname -a
  Linux pg-desktop 4.13.0-45-generic #50-Ubuntu SMP Wed May 30 08:23:18 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux

  Also fails with separate Radeon GPU:
  [ 4.904] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
  [ 4.904] (II) FBDEV: driver for framebuffer: fbdev
  [ 4.904] (II) VESA: driver for VESA chipsets: vesa
  [ 4.931] (II) [KMS] Kernel modesetting enabled.
  [ 4.931] (WW) Falling back to old probe method for modesetting
  [ 4.931] (WW) Falling back to old probe method for fbdev
  [ 4.931] (II) Loading sub module "fbdevhw"
  [ 4.931] (II) LoadModule: "fbdevhw"
  [ 4.931] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
  [ 4.931] (II) Module fbdevhw: vendor="X.Org Foundation"
  [ 4.931]  compiled for 1.19.5, module version = 0.0.2
  [ 4.931]  ABI class: X.Org Video Driver, version 23.0
  [ 4.931] (WW) Falling back to old probe method for vesa
  [ 4.931] (II) RADEON(0): Creating default Display subsection in Screen 
section
"Default Screen Section" for depth/fbbpp 24/32
  [ 4.931] (==) RADEON(0): Depth 24, (--) framebuffer bpp 32
  [ 4.931] (II) RADEON(0): Pixel depth = 24 bits stored in 4 bytes (32 bpp 
pixmaps)
  [ 4.931] (==) RADEON(0): Default visual is TrueColor
  [ 4.931] (==) RADEON(0): RGB weight 888
  [ 4.931] (II) RADEON(0): Using 8 bits per RGB (8 bit DAC)
  [ 4.931] (--) RADEON(0): Chipset: "ATI Radeon HD 4350" (ChipID = 0x954f)
  [ 4.931] (II) Loading sub module "fb"

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+13ubuntu3

[Touch-packages] [Bug 1777621] [NEW] xrandr fails to change into the native resolution, useless setup whitout Wayland

2018-06-19 Thread Pasi Grönqvist

Public bug reported:


Hello 
I have found bugs from Ubuntu 18.04  (form 16.04 by do-release-upgrade)
a) xrandr fails to change into native resolution
b) disabling Wayland cause “Out of Range” → can’t login at all (no login via 
HDMI or virtual TTY:s)
c) X fails to detect old VGA monitor (ViewSonic VA902) native resolution (this 
is a persistent bug)

I have used dual monitor setup over a decade, started with Etch and
turned into Ubuntu some years ago. First monitor is connected via HDMI
and second one by VGA. During Ubuntu installations/updates resolution
has been problem, with xrandr etc I have managed situation until now.

I have tested:
1) 16.04 & Radeon works OK with 60 Hz VGA modeline
2) 18.04 & Radeon: HDMI is OK but VGA  cant’t go into the native resolution
3) 18.04 & Intel: HDMI is OK but VGA  cant’t go into the native resolution
4) 18.04 & Radeon VGA without Wayland is Out of Range and useless
5) 18.04 & Intel & xrandr with “easy” modeline do not work
6) 18.04 & Radeon  & xrandr with “easy” modeline do not work
 

pg@pg-desktop:~$ xrandr --newmode 1280x1024_40.00   69.75  1280 1336 1472 1664  
1024 1025 1028 1048  -HSync +Vsync
pg@pg-desktop:~$ xrandr --verbose --addmode XWAYLAND1 1280x1024_40.00
pg@pg-desktop:~$ xrandr --verbose --output XWAYLAND1 --mode 1280x1024_40.00
screen 0: 2560x1024 677x271 mm  95.98dpi
crtc 1: 1280x1024_40.00  40.00 +1280+0 "XWAYLAND1"
xrandr: Configure crtc 1 failed
crtc 0: disable
crtc 1: disable
screen 0: revert
crtc 0: revert
crtc 1: revert

pg@pg-desktop:~$ lspci -k | grep -iEA5 'vga|3d|display'
00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen 
Core Processor Integrated Graphics Controller (rev 06)
Subsystem: ASRock Incorporation Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller
Kernel driver in use: i915
Kernel modules: i915
00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor 
HD Audio Controller (rev 06)
Subsystem: ASRock Incorporation Xeon E3-1200 v3/4th Gen Core Processor 
HD Audio Controller

pg@pg-desktop:~$ more /var/log/Xorg.0.log | grep EE
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
pg@pg-desktop:~$ more /var/log/Xorg.0.log | grep WW
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 4.672] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[ 4.672] (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist.
[ 4.672] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist.
[ 4.672] (WW) The directory "/usr/share/fonts/X11/100dpi" does not exist.
[ 4.672] (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist.
[ 4.852] (WW) Falling back to old probe method for modesetting
[ 4.853] (WW) Falling back to old probe method for fbdev
[ 4.853] (WW) Falling back to old probe method for vesa
pg@pg-desktop:~$ uname -a
Linux pg-desktop 4.13.0-45-generic #50-Ubuntu SMP Wed May 30 08:23:18 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

Also fails with separate Radeon GPU:
[ 4.904] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[ 4.904] (II) FBDEV: driver for framebuffer: fbdev
[ 4.904] (II) VESA: driver for VESA chipsets: vesa
[ 4.931] (II) [KMS] Kernel modesetting enabled.
[ 4.931] (WW) Falling back to old probe method for modesetting
[ 4.931] (WW) Falling back to old probe method for fbdev
[ 4.931] (II) Loading sub module "fbdevhw"
[ 4.931] (II) LoadModule: "fbdevhw"
[ 4.931] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[ 4.931] (II) Module fbdevhw: vendor="X.Org Foundation"
[ 4.931]compiled for 1.19.5, module version = 0.0.2
[ 4.931]ABI class: X.Org Video Driver, version 23.0
[ 4.931] (WW) Falling back to old probe method for vesa
[ 4.931] (II) RADEON(0): Creating default Display subsection in Screen 
section
"Default Screen Section" for depth/fbbpp 24/32
[ 4.931] (==) RADEON(0): Depth 24, (--) framebuffer bpp 32
[ 4.931] (II) RADEON(0): Pixel depth = 24 bits stored in 4 bytes (32 bpp 
pixmaps)
[ 4.931] (==) RADEON(0): Default visual is TrueColor
[ 4.931] (==) RADEON(0): RGB weight 888
[ 4.931] (II) RADEON(0): Using 8 bits per RGB (8 bit DAC)
[ 4.931] (--) RADEON(0): Chipset: "ATI Radeon HD 4350" (ChipID = 0x954f)
[ 4.931] (II) Loading sub module "fb"

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-45.50-generic 4.13.16
Uname: Linux 4.13.0-45-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.9
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Jun 19 12:30:55 2018
InstallationDate: Installed on 2017-09-28 (263 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)

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

[Touch-packages] [Bug 405294] Re: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"]

2018-06-19 Thread Bug Watch Updater

Launchpad has imported 38 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=58746.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.

On 2012-12-25T13:10:22+00:00 farbing wrote:

I'm using a bluetooth headset with pulseaudio. Whenever the connection
temporarily drops (e.g. by moving too far from the bt device), I get the
message in the syslog:

[bluetooth] module-bluetooth-device.c: Skipping 24275 us (= 4280 bytes)
in audio stream

and the audio lags behind after that. A workaround is to suspend and
resume the sink using "pactl suspend-sink 1 && pactl suspend-sink 0",
after which the audio is in sync again.

Using the same headset on Windows doesn't show the same behavior.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/405294/comments/109

On 2016-02-13T23:32:25+00:00 Z-mike-y wrote:

Bumping this due to the fact that this bug is still very much present in
5, 6, 7, 8 and renders the act of using a bluetooth headset on most
linux operating systems using pulseaudio utterly useless. The slightest
blip throws the whole audio out of sync with the video. I noticed this
when trying to watch a movie from a 6ft distance away (sill in range)
but occasionally the signal would blip and cause said problem. Evidence
in the logs:

Three of many lines:

Feb 13 17:25:49 saturn.net.overtmind.com pulseaudio[30599]: [bluetooth] 
module-bluez5-device.c: Skipping 5124656 us (= 903988 bytes) in audio stream
Feb 13 17:25:49 saturn.net.overtmind.com pulseaudio[30599]: [bluetooth] mod 
ule-bluez5-device.c: Skipping 220060 us (= 38816 bytes) in audio stream
Feb 13 17:25:49 saturn.net.overtmind.com pulseaudio[30599]: [bluetooth] 
module-bluez5-device.c: Skipping 346147 us (= 61060 bytes) in audio stream

Packages tested in Fedora 23:

rawhide:

bluez-5.37-2.fc24.x86_64
pulseaudio-8.0-3.fc24.x86_64

and also tried initially with:

bluez-5.36-1.fc23.x86_64
pulseaudio-7.1-1.fc23.x86_64

The rest of my findings are here, where someone else has also mentioned
seeing this on Gentoo with PA 5,6 - I have tested 7 and 8:

https://www.reddit.com/r/linuxquestions/comments/45n710/pulseaudio_bluetooth_degraded_signal_out_of_sync/

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/405294/comments/126

On 2016-02-14T09:53:05+00:00 Raymond wrote:

If you want audio sync with video after audio transmission is broken,
you need the application to skip some audio and restart audio playback

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/405294/comments/127

On 2016-02-14T10:21:54+00:00 Z-mike-y wrote:

Shouldn't the buffer reset after detecting a skip event?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/405294/comments/128

On 2016-05-04T01:37:04+00:00 Sb wrote:

(In reply to xenith from comment #3)
> Shouldn't the buffer reset after detecting a skip event?

This would seem to be the most logical thing. The way it is now, even
stopping and re-starting the audio stream doesn't fix the latency issue
if there has ever been a brief blip in the current Bluetooth connection.
Quite a showstopper for watching video with bluetooth
speakers/headphones.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/405294/comments/130

On 2016-05-08T15:46:53+00:00 Arun Raghavan wrote:

I've tried to reproduce this behaviour in the past, but it doesn't
always happen this way (but I have seen the delays turn up on drops at
times). If someone has a patch that definitely works (or a way to repro
that is 100% reliable), I can try to look at this.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/405294/comments/131

On 2016-05-10T15:58:47+00:00 Sb wrote:

(In reply to Arun Raghavan from comment #5)
> I've tried to reproduce this behaviour in the past, but it doesn't always
> happen this way (but I have seen the delays turn up on drops at times). If
> someone has a patch that definitely works (or a way to repro that is 100%
> reliable), I can try to look at this.

I have about 6 different cheap Chinese bluetooth speakers, and they all
exhibit this behavior. They all use the A2DP protocol, are you possibly
seeing different behavior with HSP/HFP?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/405294/comments/132

[Touch-packages] [Bug 1777099] Re: [backport] DRM devices opened by logind stay referenced indefinitely by PID 1

2018-06-19 Thread Alberto Milone

** Changed in: systemd (Ubuntu)
   Status: Triaged => In Progress

** Also affects: systemd (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: systemd (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: systemd (Ubuntu Bionic)
   Importance: Undecided => High

** Changed in: systemd (Ubuntu Bionic)
 Assignee: (unassigned) => Alberto Milone (albertomilone)

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

Title:
  [backport] DRM devices opened by logind stay referenced indefinitely
  by PID 1

Status in OEM Priority Project:
  New
Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Bionic:
  In Progress

Bug description:
  refer to https://github.com/systemd/systemd/issues/6908

  we need that solution to make NVIDIA dGPU switching works.

  impacted issue:
  https://bugs.launchpad.net/somerville/+bug/1774326

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1777099/+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 1760201] Re: ubuntu 18.04 GDM - missing icons and letters on login screen with nouveau + Wayland

2018-06-19 Thread Wade

I'd like to report that this issue is also being reproduced with nouveau
on NVIDIA GF108. However, my dmesg does not seem to contain nouveau
errors.

dmesg sample containing nouveau (as above):
[5.254956] nouveau :01:00.0: enabling device (0006 -> 0007)
[5.255096] nouveau :01:00.0: NVIDIA GF108 (0c1480a1)
[5.285074] nouveau :01:00.0: bios: version 70.08.a8.00.2b
[5.393498] nouveau :01:00.0: fb: 2048 MiB DDR3
[5.449440] nouveau :01:00.0: DRM: VRAM: 2048 MiB
[5.449441] nouveau :01:00.0: DRM: GART: 1048576 MiB
[5.449444] nouveau :01:00.0: DRM: TMDS table version 2.0
[5.449454] nouveau :01:00.0: DRM: DCB version 4.0
[5.449455] nouveau :01:00.0: DRM: DCB outp 00: 02010300 
[5.449457] nouveau :01:00.0: DRM: DCB conn 00: 
[5.451120] nouveau :01:00.0: DRM: MM: using COPY0 for buffer copies
[5.485363] nouveau :01:00.0: DRM: allocated 1024x768 fb: 0x6, bo 
10a8d043
[5.488176] nouveau :01:00.0: fb0: nouveaufb frame buffer device
[5.512017] [drm] Initialized nouveau 1.3.1 20120801 for :01:00.0 on 
minor 1

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

Title:
  ubuntu 18.04 GDM - missing icons and letters on login screen with
  nouveau + Wayland

Status in linux package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  WORKAROUND:

  Edit /etc/gdm3/custom.conf and uncomment:
#WaylandEnable=false

  ---

  Ubuntu 18.04(Updated 30.03.2018)
  System Language: Turkish
  Please check screenshots
  ---
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-03-24 (9 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180324)
  Package: gnome-shell
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Tags:  bionic
  Uname: Linux 4.15.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1760201/+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 1777094] Re: dnsmasq started too early, not getting all interfaces

2018-06-19 Thread Hadmut Danisch

setting optional: false   does not solve the problem, a systemctl
restart dnsmasq is still required.

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

Title:
  dnsmasq started too early, not getting all interfaces

Status in dnsmasq package in Ubuntu:
  Incomplete
Status in netplan.io package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I'm still struggling with 18.04 and the move from ifupdown to netplan.

  I am running a local virtual linux bridge as a network for several
  virtual machines and containers, which is to be serviced with dhcp and
  dns by dnsmasq.

  Conforming to latest designs from Ubuntu the bridge is now started by
  netplan and configured in /etc/netplan/60-vlan0.yaml straightforward.

  Since there is no ifupdown-scripts anymore, I've configured the
  default dnsmasq daemon in /etc/dnsmasq.d/vlan0 to offer dhcp for that
  bridge.

  
  This works only when started manually. 

  When booting ubuntu the normal way, the bridge is correctly generated,
  and dnsmasq is running, but it does *not* offer DNS for the bridge and
  does not occupy its port 53. But just a manual systemctl restart
  dnsmasq.service make it run as expected, then everything is fine.

  So my guess is that my configuration is correct, but dnsmasq simply
  started to early, i.e. before the bridge is created, and thus does not
  see the bridge when starting up.

  There's something wrong in the dependencies of the startup
  configuration.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: dnsmasq 2.79-1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Fri Jun 15 10:59:43 2018
  InstallationDate: Installed on 2018-04-30 (45 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  PackageArchitecture: all
  SourcePackage: dnsmasq
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1777094/+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 1712866] Re: icons from qt applications disappear after screen lock/sleep

2018-06-19 Thread Gyuris Gellért

This happening to me in 18.04 Bionic: the icons disappear after lock/sleep and 
do not appear on login.
Restarting with Alt+F2 + r makes them reappear.

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

Title:
  icons from qt applications disappear after screen lock/sleep

Status in gnome-shell-extension-appindicator package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-appindicator source package in Artful:
  Fix Released

Bug description:
  [Impact]

  Indicators of some Qt apps are not showing after unlocking the screen
  or shell restart.

  
  [Test case]

  - Login to 17.10
  - launch dropbox (if not already launched)
  - Launch telegram (snap version or without libappindicator support)
  - Observe icons in taskbar
  - Lock screen with Super+L
  - Unlock screen
  - Icons should still be there

  
  [Possible regressions]

  Icons that should be hidden could be visible instead

  The fix doesn't apply to snapped applications

  In the Ubuntu Xorg session, with the Ubuntu Appindicator extension
  enabled, the tray icons for QT apps (in my case, both owncloud-client
  from the Ubuntu repos and enpass, from their own repo) show up after
  first logging in. But once the screen has been left idle long enough
  to be put to sleep, and is then woken up (I don't actually have screen
  *lock* enabled, but it still goes comes back to the clock screen and a
  further gesture is needed to scroll that up to get the desktop), then
  the icons for those QT apps are gone. Non-QT apps (eg: in my case
  hexchat, from the ubuntu repos) remain.

  For a while and due to inattention it seemed more random than that,
  but I'm fairly sure now it's just the display sleep/wake thing that
  kills it.

  The applications are still running in the background (so for instance
  enpass is still available via the browser extension), and can be seen
  in the process list. It's just the icons that have disappeared. If I
  then kill those apps (from the commandline with 'kill [pid]' because
  there's no other interface to do it from) and relaunch them, they
  reappear back in the appindicator area.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell-extension-appindicator 17.10
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 24 17:12:43 2017
  Dependencies:

  InstallationDate: Installed on 2017-07-30 (24 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-appindicator
  UpgradeStatus: Upgraded to artful on 2017-08-22 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1712866/+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

2018-06-19 Thread Lensmarket

** Changed in: initramfs-tools (Ubuntu)
 Assignee: Deon Joubert (02deon-j) => (unassigned)

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

Status in initramfs-tools:
  Confirmed
Status in Ubuntu Software Center:
  Invalid
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/initramfs-tools/+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 1777514] Re: gnome-shell crashed with SIGABRT (corrupted double-linked list) in free() from ... _mesa_glsl_release_builtin_functions() from _mesa_destroy_shader_compiler_caches()

Hmm, problem:

https://errors.ubuntu.com/problem/c1f46d2d92c2be5d4c6d68c44ef0817ccea8ccab

is not being deduplicated accurately by the robots at errors.ubuntu.com.

5 hours ago the stack trace was in Mesa as mentioned above. And now it's
something different.

So we must generalize this bug to match :S

** Summary changed:

- gnome-shell crashed with SIGABRT (corrupted double-linked list) in free() 
from ... _mesa_glsl_release_builtin_functions() from 
_mesa_destroy_shader_compiler_caches() from _mesa_destroy_shader_compiler() 
from one_time_fini() from __run_exit_handlers() from exit()
+ gnome-shell crashed with SIGABRT (corrupted double-linked list) in free()

** No longer affects: mesa (Ubuntu)

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

Title:
  gnome-shell crashed with SIGABRT (corrupted double-linked list) in
  free()

Status in gnome-shell package in Ubuntu:
  Confirmed

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1777514/+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 1704297] Re: Bluetooth audio stuck in A2DP profile ([pulseaudio] module-bluez5-device.c: Refused to switch profile to headset_head_unit: Not connected)

Alexey,

Indeed it appears that PulseAudio, even upstream, is missing those
patches. However this is not the right place to request their inclusion.

Please talk to the upstream PulseAudio people instead:
https://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/User/Community/

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

Title:
  Bluetooth audio stuck in A2DP profile ([pulseaudio] module-
  bluez5-device.c: Refused to switch profile to headset_head_unit: Not
  connected)

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I've got a pair of Parot Zik bluetooth headphones, with inbuilt
  microphones and such.

  The Sound control panel offers a “Profile” dropdown, with choice of
  A2DP and HSP profiles, but selecting the HSP profile (a) doesn't add
  an input source to the “Inputs” tab, and (b) doesn't stop the
  headphones playing stereo sound, indicating that it hasn't actually
  been switched to HSP profile (which is, AFAIK, mono).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair nvidia_uvm nvidia_drm 
nvidia_modeset nvidia
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  chris  7755 F pulseaudio
   /dev/snd/controlC1:  chris  7755 F pulseaudio
   /dev/snd/pcmC0D0c:   chris  7755 F...m pulseaudio
   /dev/snd/controlC0:  chris  7755 F pulseaudio
  CurrentDesktop: GNOME
  Date: Fri Jul 14 16:27:09 2017
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/20/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.02dRSA1 02/20/2017
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Oryx Pro
  dmi.board.vendor: System76
  dmi.board.version: oryp3-ess
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.02dRSA102/20/2017:bd02/20/2017:svnSystem76:pnOryxPro:pvroryp3-ess:rvnSystem76:rnOryxPro:rvroryp3-ess:cvnSystem76:ct10:cvrN/A:
  dmi.product.name: Oryx Pro
  dmi.product.version: oryp3-ess
  dmi.sys.vendor: System76

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1704297/+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 1704297] Re: Bluetooth audio stuck in A2DP profile ([pulseaudio] module-bluez5-device.c: Refused to switch profile to headset_head_unit: Not connected)

2018-06-19 Thread Alexey Zagarin

I have a similar issue. I'm trying to get the mic working on Beats X
headset. These series of patches helped me to solve the issue:

https://patchwork.freedesktop.org/patch/178198/
https://patchwork.freedesktop.org/patch/178199/
https://patchwork.freedesktop.org/patch/178200/
https://patchwork.freedesktop.org/patch/178201/

Can we get them upstream?
I'm on Ubuntu 18.04.

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

Title:
  Bluetooth audio stuck in A2DP profile ([pulseaudio] module-
  bluez5-device.c: Refused to switch profile to headset_head_unit: Not
  connected)

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I've got a pair of Parot Zik bluetooth headphones, with inbuilt
  microphones and such.

  The Sound control panel offers a “Profile” dropdown, with choice of
  A2DP and HSP profiles, but selecting the HSP profile (a) doesn't add
  an input source to the “Inputs” tab, and (b) doesn't stop the
  headphones playing stereo sound, indicating that it hasn't actually
  been switched to HSP profile (which is, AFAIK, mono).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair nvidia_uvm nvidia_drm 
nvidia_modeset nvidia
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  chris  7755 F pulseaudio
   /dev/snd/controlC1:  chris  7755 F pulseaudio
   /dev/snd/pcmC0D0c:   chris  7755 F...m pulseaudio
   /dev/snd/controlC0:  chris  7755 F pulseaudio
  CurrentDesktop: GNOME
  Date: Fri Jul 14 16:27:09 2017
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/20/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.02dRSA1 02/20/2017
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Oryx Pro
  dmi.board.vendor: System76
  dmi.board.version: oryp3-ess
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.02dRSA102/20/2017:bd02/20/2017:svnSystem76:pnOryxPro:pvroryp3-ess:rvnSystem76:rnOryxPro:rvroryp3-ess:cvnSystem76:ct10:cvrN/A:
  dmi.product.name: Oryx Pro
  dmi.product.version: oryp3-ess
  dmi.sys.vendor: System76

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1704297/+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 1777514] Re: gnome-shell crashed with SIGABRT (corrupted double-linked list) in free() from ... _mesa_glsl_release_builtin_functions() from _mesa_destroy_shader_compiler_caches()

2018-06-19 Thread Patrik Kullman

Not sure if this was the correct "corrupted double linked list" issue
but if it is, it was happening under Wayland. Fresh install.

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

Title:
  gnome-shell crashed with SIGABRT (corrupted double-linked list) in
  free() from ... _mesa_glsl_release_builtin_functions() from
  _mesa_destroy_shader_compiler_caches() from
  _mesa_destroy_shader_compiler() from one_time_fini() from
  __run_exit_handlers() from exit()

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1777514/+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 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.

2018-06-19 Thread Marc Pignat

And this warning is not really reassuring:

sudo update-initramfs -u
update-initramfs: Generating /boot/initrd.img-4.15.0-20-generic
I: The initramfs will attempt to resume from /dev/dm-1
I: (/dev/mapper/xubuntu--vg-swap_1)
I: Set the RESUME variable to override this.

-- 
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:
  In Progress

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 1777099] Re: [backport] DRM devices opened by logind stay referenced indefinitely by PID 1

2018-06-19 Thread Alex Tu

the irc conversation about this patch:
https://pastebin.canonical.com/p/k7YkQ8rmSR/

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

Title:
  [backport] DRM devices opened by logind stay referenced indefinitely
  by PID 1

Status in OEM Priority Project:
  New
Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Triaged

Bug description:
  refer to https://github.com/systemd/systemd/issues/6908

  we need that solution to make NVIDIA dGPU switching works.

  impacted issue:
  https://bugs.launchpad.net/somerville/+bug/1774326

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1777099/+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 1773157] Re: procps outdated network options, old syncookies, new ecn update please.

This bug was fixed in the package procps - 2:3.3.15-2ubuntu1

---
procps (2:3.3.15-2ubuntu1) cosmic; urgency=medium

* Merge from Debian unstable. Remaining changes:
- debian/sysctl.d (Ubuntu-specific):
+ 10-console-messages.conf: stop low-level kernel messages on console.
+ 10-kernel-hardening.conf: add the kptr_restrict setting
+ 10-keyboard.conf.powerpc: mouse button emulation on PowerPC.
+ 10-ipv6-privacy.conf: add a file to sysctl.d to apply the defaults
for IPv6 privacy extensions for interfaces. (LP: #176125, #841353)
+ 10-link-restrictions.conf: even though the Ubuntu
kernel is built with these defaults in place, we want to make sure
that people running stock kernels don't miss out.
+ 10-magic-sysrq.conf: Disable most magic sysrq by default, allowing
critical sync, remount, reboot functions. (LP: #194676, LP: #1025467)
+ 10-network-security.conf: enable rp_filter.
+ 10-ptrace.conf: describe new PTRACE setting.
+ 10-zeropage.conf: safe mmap_min_addr value for graceful fall-back.
for armhf, and arm64.
+ 10-qemu.conf.s390x for qemu.
+ README: describe how this directory is supposed to work.
- debian/rules: Fix cross build
- ignore_eaccess.patch: If we get eaccess when opening a sysctl file for
writing, don't error out. Otherwise package upgrades can fail,
especially in containers.
- ignore_erofs.patch: Same as ignore_eaccess but for the case where
part of /proc is read/only.

procps (2:3.3.15-2) unstable; urgency=medium

* Fix link in libprocps-dev Closes: 900239
* Fix typo in license Closes: #899346

-- Balint Reczey Tue, 05 Jun 2018 11:20:00 -0700

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

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

Title:
procps outdated network options, old syncookies, new ecn update
please.

Status in procps package in Ubuntu:
Fix Released

Bug description:
The ubuntu version of procps carries it's own /etc/sysctl.d/10
-network-security.conf file explicitly that appears not to be part of
debian procps version.

Firstly, the section about "# Turn on SYN-flood protections." (came from LP
#57091 ) is now entirely outdated, upstream kernel has long since turned on
syncookies by default, so setting this flag explicitly in
10-network-security.conf is entirely redundant likely since before ubuntu-14.04
.
I would like the ubuntu-maintainer to remove that section entirely in cosmic
onwards.

[I am going to report debian the similarly outdated syncookies
comments in sysctl.conf itself].

Secondly, I propose a new 10-network-tuning.conf with:-
==
# Allow ECN for outgoing connections. Starting with 4.2, there is an adaptive
# fallback [enabled by default tcp_ecn_fallback option] preventing connection
# loss even with ecn enabled, also ecn-intolerance is increasingly very rare.
net.ipv4.tcp_ecn=1
==

I know there is a (small) chance of issues/regressions with ECN
enabled by default on outgoing but I'm quite sure the issue is very
rare, like others notice [ref: 1 and 2 below]. Apple's selective
enablements etc. show this works just as much as my own use for years
and many similar reports.

ECN actually being used for outgoing connections really helps with
latency-reduction with modern routers (both core and edge) using
queuing disciplines fq_codel or otherwise, able to mark rather than
drop packets on ECN-enabled flows [helps latency and realtime
applications]. Now we are just past LTS release is in my view the
'right time' to finally enable ECN [and obviously easy to revert!].
If this is disputed, in ANY case I strongly suggest at the very least
a commented-out ECN section should be included, but 'defaults
matter'!.

I was going to suggest a non-default section about
net.core.default_qdisc [ LP #1436945 ] but this appears to have been
fixed upstream similarly.

[1]
https://www.ietf.org/proceedings/98/slides/slides-98-maprg-tcp-ecn-experience-with-enabling-ecn-on-the-internet-padma-bhooma-00.pdf
[2] http://seclists.org/nanog/2015/Jun/675

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1773157/+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 1719159] Re: 'service procps start' does nothing; outdated README

This bug was fixed in the package procps - 2:3.3.15-2ubuntu1

---
procps (2:3.3.15-2ubuntu1) cosmic; urgency=medium

  * Merge from Debian unstable.  Remaining changes:
- debian/sysctl.d (Ubuntu-specific):
  + 10-console-messages.conf: stop low-level kernel messages on console.
  + 10-kernel-hardening.conf: add the kptr_restrict setting
  + 10-keyboard.conf.powerpc: mouse button emulation on PowerPC.
  + 10-ipv6-privacy.conf: add a file to sysctl.d to apply the defaults
for IPv6 privacy extensions for interfaces. (LP: #176125, #841353)
  + 10-link-restrictions.conf: even though the Ubuntu
kernel is built with these defaults in place, we want to make sure
that people running stock kernels don't miss out.
  + 10-magic-sysrq.conf: Disable most magic sysrq by default, allowing
critical sync, remount, reboot functions. (LP: #194676, LP: #1025467)
  + 10-network-security.conf: enable rp_filter.
  + 10-ptrace.conf: describe new PTRACE setting.
  + 10-zeropage.conf: safe mmap_min_addr value for graceful fall-back.
for armhf, and arm64.
  + 10-qemu.conf.s390x for qemu.
  + README: describe how this directory is supposed to work.
- debian/rules: Fix cross build
- ignore_eaccess.patch: If we get eaccess when opening a sysctl file for
  writing, don't error out.  Otherwise package upgrades can fail,
  especially in containers.
- ignore_erofs.patch: Same as ignore_eaccess but for the case where
  part of /proc is read/only.

procps (2:3.3.15-2) unstable; urgency=medium

  * Fix link in libprocps-dev Closes: 900239
  * Fix typo in license Closes: #899346

 -- Balint Reczey   Tue, 05 Jun 2018 11:20:00 -0700

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

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

Title:
  'service procps start' does nothing; outdated README

Status in procps package in Ubuntu:
  Fix Released

Bug description:
  /etc/sysctl.d/README says

  After making any changes, please run "service procps start" (or, from
  a Debian package maintainer script "invoke-rc.d procps start").

  however running this command does absolutely nothing on Ubuntu 17.04 (and,
  presumably, any other Ubuntu version since systemd became the main init
  system).

  To actually get your changes written into /proc/sys, you have to do

  service procps reload

  Can you please update the README?

  (This is similar to bug 1332362, but I think that one was Upstart's
  fault.)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: procps 2:3.3.12-1ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Sep 24 11:26:45 2017
  InstallationDate: Installed on 2016-09-10 (379 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  SourcePackage: procps
  UpgradeStatus: Upgraded to zesty on 2017-04-14 (163 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1719159/+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 1749562] Re: openvpn tls-crypt not working