date:20180307

[Touch-packages] [Bug 1753954] Re: Intel Whiskey Lake (WHL) graphics support

2018-03-07 Thread Timo Aaltonen

xserver patched in git

** Changed in: xorg-server (Ubuntu Bionic)
   Status: New => Fix Committed

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

Title:
  Intel Whiskey Lake (WHL) graphics support

Status in libdrm package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Fix Committed
Status in xorg-server-hwe-16.04 package in Ubuntu:
  Invalid
Status in libdrm source package in Xenial:
  New
Status in linux-oem source package in Xenial:
  New
Status in mesa source package in Xenial:
  New
Status in xorg-server source package in Xenial:
  Invalid
Status in xorg-server-hwe-16.04 source package in Xenial:
  New
Status in libdrm source package in Bionic:
  Fix Released
Status in linux-oem source package in Bionic:
  Fix Released
Status in mesa source package in Bionic:
  Fix Released
Status in xorg-server source package in Bionic:
  Fix Committed
Status in xorg-server-hwe-16.04 source package in Bionic:
  Invalid

Bug description:
  [Impact]
  WHL is basically CFL-U with new PCI-ID's that are needed in the kernel, 
libdrm, mesa and xserver.

  [Test Case]

  Test the installation on a WHL machine, the graphical session should
  have full acceleration after these updates.

  [Regression Potential]

  None, just adds PCI-ID's to existing drivers.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1753954/+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 1732865] Re: [LTCTest][OPAL][FW860.20] lscpu failed to list cpu max and min frequencies

2018-03-07 Thread Steve Langasek

** Tags added: verification-failed-xenial

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

Title:
  [LTCTest][OPAL][FW860.20] lscpu failed to list cpu max and min
  frequencies

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux source package in Xenial:
  Fix Committed
Status in util-linux source package in Artful:
  Fix Released

Bug description:
  [Impact]
  lscpu fails to list CPU max and min frequencies if some CPUs are guarded.

  [Regression potential]
  Isolated change to lscpu min/max CPU frequency output, so the worst that 
could happen is that it fails to work elsewhere.

  [Test case]
  1. Clone https://github.com/open-power/op-test-framework
  2. Run this command to GUARD the cpu.
  ./op-test --bmc-type FSP --bmc-ip $FSPIP --bmc-username dev --bmc-password 
FipSdev --host-ip $HOSTIP --host-user root --host-password passw0rd --ffdcdir 
test-reports/ --run testcases.OpTestHMIHandling.MalfunctionAlert
  3. Repeat again, so that multiple CPUs are guarded.
  4. Run lscpu
  5. Observe that no CPU frequencies are displayed:
  CPU max MHz: (null)
  CPU min MHz: (null)
  6. Install util-linux from -proposed.
  7. Run lscpu again
  8. Observe that max and min CPU frequencies are correctly displayed.

  == Comment: #0 - Pridhiviraj Paidipeddi  - 2017-01-03 
05:34:32 ==
  ---Problem Description---
  After 3 CPU's are garded, lscpu failed to list CPU max and min frequencies

  Contact Information = ppaid...@in.ibm.com

  ---uname output---
  Linux p8wookie 4.8.0-32-generic #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 
UTC 2016 ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = PowerNV 8284-22A

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
   1. Read lscpu output
  2. Inject HMI Non recoverable error three times
  3. Read lscpu output again
  compare the output cpu frequencies will list as NULL

  Stack trace output:
   no

  Oops output:
   no

  Userspace tool common name: lscpu

  Userspace rpm: util-linux

  The userspace tool has the following bit modes: 64-bit

  System Dump Info:
    The system is not configured to capture a system dump.

  Userspace tool obtained from project website:  na

  *Additional Instructions for ppaid...@in.ibm.com:
  -Post a private note with access information to the machine that the bug is 
occuring on.
  -Attach sysctl -a output output to the bug.
  -Attach ltrace and strace of userspace application.

  Before CPU's are garded:
  root@p8wookie:~# lscpu
  Architecture:  ppc64le
  Byte Order:Little Endian
  CPU(s):112
  On-line CPU(s) list:   0-71,80-103,112-127
  Thread(s) per core:8
  Core(s) per socket:3
  Socket(s): 4
  NUMA node(s):  4
  Model: 2.1 (pvr 004b 0201)
  Model name:POWER8E (raw), altivec supported
  CPU max MHz:   4322.
  CPU min MHz:   2061.
  L1d cache: 64K
  L1i cache: 32K
  L2 cache:  512K
  L3 cache:  8192K
  NUMA node0 CPU(s): 0-31
  NUMA node1 CPU(s): 32-63
  NUMA node16 CPU(s):64-71,80-95
  NUMA node17 CPU(s):96-103,112-127

  After 4 cores are garded:
  root@p8wookie:~# lscpu
  Architecture:  ppc64le
  Byte Order:Little Endian
  CPU(s):96
  On-line CPU(s) list:   8-55,64-71,80-103,112-127
  Thread(s) per core:8
  Core(s) per socket:3
  Socket(s): 4
  NUMA node(s):  4
  Model: 2.1 (pvr 004b 0201)
  Model name:POWER8E (raw), altivec supported
  CPU max MHz:   (null)
  CPU min MHz:   (null)
  L1d cache: 64K
  L1i cache: 32K
  L2 cache:  512K
  L3 cache:  8192K
  NUMA node0 CPU(s): 8-31
  NUMA node1 CPU(s): 32-55
  NUMA node16 CPU(s):64-71,80-95
  NUMA node17 CPU(s):96-103,112-127

  == Comment: #1 - Pridhiviraj Paidipeddi  - 2017-01-11 
07:06:59 ==
  root@p8wookie:~# dmesg |grep -i powernv
  [0.00] Using PowerNV machine description
  [0.331564] EEH: PowerNV platform initialized
  [0.907250] powernv-rng: Registering arch random hook.
  [1.504063] powernv-cpufreq: cpufreq pstate min -68 nominal -5 max 0
  [1.507167] powernv_idle_driver registered
  [   34.184048] powernv_rng: Registered powernv hwrng.
  [   34.185619] ipmi-powernv ibm,opal:ipmi: Unable to map irq from device tree
  [   34.210966] ipmi-powernv ibm,opal:ipmi: Found new BMC (man_id: 0x00, 
prod_id: 0x, dev_id: 0x00)
  root@p8wookie:~# cat /sys/firmware/opal/msglog | grep -i occ
  [   42.297825315,7]   OCC Common Area at 0x3b0 size 1MB
  [   42.297854780,7]   OCC Common Area at 0x200080 size 1MB
  [   42.297884305,7]

[Touch-packages] [Bug 1732865] Comment bridged from LTC Bugzilla

2018-03-07 Thread bugproxy

--- Comment From mainam...@in.ibm.com 2018-03-08 01:15 EDT---
Segmentation fault is may be due to library issue?

Pridhivi,
Can you verify once with upstream build and confirm

(gdb) run(gdb) run
Starting program: /usr/bin/lscpu
Architecture:  ppc64le
Byte Order:Little Endian
CPU(s):72
On-line CPU(s) list:   8-79
Thread(s) per core:8
Core(s) per socket:4
Socket(s): 2
NUMA node(s):  2
Model: 2.1 (pvr 004b 0201)
Model name:POWER8E (raw), altivec supported

Program received signal SIGSEGV, Segmentation fault.
__GI_strtod_l_internal (nptr=0x0, endptr=0x0, group=, 
loc=0x77f115f0 <_nl_global_locale>) at strtod_l.c:583
583 strtod_l.c: No such file or directory.
(gdb) bt
#0  __GI_strtod_l_internal (nptr=0x0, endptr=0x0, group=, 
loc=0x77f115f0 <_nl_global_locale>) at strtod_l.c:583
#1  0x77d9607c in __GI_strtod (nptr=, endptr=) at strtod.c:64
#2  0x100060c0 in ?? ()
#3  0x100030e8 in ?? ()
#4  0x77d7309c in generic_start_main (main=0x10001f10, argc=, argv=0x7b18, auxvec=0x7bd0, init=, 
rtld_fini=, stack_end=,
fini=) at ../csu/libc-start.c:291
#5  0x77d73298 in __libc_start_main (argc=, 
argv=, ev=, auxvec=, 
rtld_fini=, stinfo=,
stack_on_entry=) at 
../sysdeps/unix/sysv/linux/powerpc/libc-start.c:116
#6  0x in ?? ()
(gdb)

Starting program: /usr/bin/lscpu
Architecture:  ppc64le
Byte Order:Little Endian
CPU(s):72
On-line CPU(s) list:   8-79
Thread(s) per core:8
Core(s) per socket:4
Socket(s): 2
NUMA node(s):  2
Model: 2.1 (pvr 004b 0201)
Model name:POWER8E (raw), altivec supported

Program received signal SIGSEGV, Segmentation fault.
__GI_strtod_l_internal (nptr=0x0, endptr=0x0, group=, 
loc=0x77f115f0 <_nl_global_locale>) at strtod_l.c:583
583 strtod_l.c: No such file or directory.
(gdb) bt
#0  __GI_strtod_l_internal (nptr=0x0, endptr=0x0, group=, 
loc=0x77f115f0 <_nl_global_locale>) at strtod_l.c:583
#1  0x77d9607c in __GI_strtod (nptr=, endptr=) at strtod.c:64
#2  0x100060c0 in ?? ()
#3  0x100030e8 in ?? ()
#4  0x77d7309c in generic_start_main (main=0x10001f10, argc=, argv=0x7b18, auxvec=0x7bd0, init=, 
rtld_fini=, stack_end=,
fini=) at ../csu/libc-start.c:291
#5  0x77d73298 in __libc_start_main (argc=, 
argv=, ev=, auxvec=, 
rtld_fini=, stinfo=,
stack_on_entry=) at 
../sysdeps/unix/sysv/linux/powerpc/libc-start.c:116
#6  0x in ?? ()
(gdb)

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

Title:
  [LTCTest][OPAL][FW860.20] lscpu failed to list cpu max and min
  frequencies

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux source package in Xenial:
  Fix Committed
Status in util-linux source package in Artful:
  Fix Released

Bug description:
  [Impact]
  lscpu fails to list CPU max and min frequencies if some CPUs are guarded.

  [Regression potential]
  Isolated change to lscpu min/max CPU frequency output, so the worst that 
could happen is that it fails to work elsewhere.

  [Test case]
  1. Clone https://github.com/open-power/op-test-framework
  2. Run this command to GUARD the cpu.
  ./op-test --bmc-type FSP --bmc-ip $FSPIP --bmc-username dev --bmc-password 
FipSdev --host-ip $HOSTIP --host-user root --host-password passw0rd --ffdcdir 
test-reports/ --run testcases.OpTestHMIHandling.MalfunctionAlert
  3. Repeat again, so that multiple CPUs are guarded.
  4. Run lscpu
  5. Observe that no CPU frequencies are displayed:
  CPU max MHz: (null)
  CPU min MHz: (null)
  6. Install util-linux from -proposed.
  7. Run lscpu again
  8. Observe that max and min CPU frequencies are correctly displayed.

  == Comment: #0 - Pridhiviraj Paidipeddi  - 2017-01-03 
05:34:32 ==
  ---Problem Description---
  After 3 CPU's are garded, lscpu failed to list CPU max and min frequencies

  Contact Information = ppaid...@in.ibm.com

  ---uname output---
  Linux p8wookie 4.8.0-32-generic #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 
UTC 2016 ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = PowerNV 8284-22A

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
   1. Read lscpu output
  2. Inject HMI Non recoverable error three times
  3. Read lscpu output again
  compare the output cpu frequencies will list as NULL

  Stack trace output:
   no

  Oops output:
   no

  Userspace tool common name: lscpu

  Userspace rpm: util-linux

  The userspace tool has the following bit modes: 64-bit

  System Dump Info:
    The system is not configured to capture a system dump.

  Userspace tool obtained from

[Touch-packages] [Bug 1754244] [NEW] [bionic] evolution-source-registry always using 100% cpu

2018-03-07 Thread Trent Lloyd

Public bug reported:

evolution-source-registry is using 100% CPU after login and never stops,
it continues to do so after kill/respawn or reboot.  This started
sometime after upgrade to bionic and has been consistent for the last
couple of weeks.

Looking at the process with perf, it seems that it is looping calling
poll() via g_main_context_poll() via g_main_context_iterate in a hard
loop.  In strace you can also see poll being called about 10,000
times/second.

poll([{fd=3, events=POLLIN}, {fd=11, events=POLLIN}], 2, 0) = 0
(Timeout)

gdb backtrace for the main thread reflected in the attached out.svg -
setting a breakpoint g_main_context_iterate is being called continually
but we never exit from g_main_loop_run.

(gdb) bt
#0  0x7f6e1ce30150 in g_main_context_iterate (context=0x55ca494d18c0, 
block=block@entry=1, dispatch=dispatch@entry=1, self=)
at ../../../../glib/gmain.c:3840
#1  0x7f6e1ce30662 in g_main_loop_run (loop=0x55ca4949f580) at 
../../../../glib/gmain.c:4099
#2  0x7f6e1df22710 in dbus_server_run_server (server=0x55ca494df1a0 
[ESourceRegistryServer]) at ./src/libebackend/e-dbus-server.c:247
#3  0x7f6e19502dae in ffi_call_unix64 () at 
/usr/lib/x86_64-linux-gnu/libffi.so.6
#4  0x7f6e1950271f in ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6
#5  0x7f6e1d10ab4d in g_cclosure_marshal_generic_va 
(closure=0x55ca494d8ab0, return_value=0x7ffd34330e10, instance=, 
args_list=, marshal_data=, n_params=0, 
param_types=0x0) at ../../../../gobject/gclosure.c:1604
#6  0x7f6e1d10a1a6 in _g_closure_invoke_va (closure=0x55ca494d8ab0, 
return_value=0x7ffd34330e10, instance=0x55ca494df1a0, args=0x7ffd34330ec0, 
n_params=0, param_types=0x0) at ../../../../gobject/gclosure.c:867
#7  0x7f6e1d1256df in g_signal_emit_valist (instance=0x55ca494df1a0, 
signal_id=, detail=, 
var_args=var_args@entry=0x7ffd34330ec0)
at ../../../../gobject/gsignal.c:3300
#8  0x7f6e1d125e0f in g_signal_emit 
(instance=instance@entry=0x55ca494df1a0, signal_id=, 
detail=detail@entry=0) at ../../../../gobject/gsignal.c:3447
#9  0x7f6e1df22a1d in e_dbus_server_run (server=0x55ca494df1a0 
[ESourceRegistryServer], wait_for_client=0) at 
./src/libebackend/e-dbus-server.c:441
#10 0x55ca473cec0c in main (argc=, argv=) at 
./src/services/evolution-source-registry/evolution-source-registry.c:233


ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: evolution-data-server 3.27.90-1ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-11.12-generic 4.15.5
Uname: Linux 4.15.0-11-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon 
znvpair
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: GNOME
Date: Thu Mar  8 13:28:39 2018
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/evolution/evolution-source-registry
ProcEnviron:
 LANG=en_AU.UTF-8
 LANGUAGE=en_AU:en
 PATH=(custom, user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
SourcePackage: evolution-data-server
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: evolution-data-server (Ubuntu)
 Importance: Undecided
 Status: New


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

** Description changed:

  evolution-source-registry is using 100% CPU after login and never stops,
  it continues to do so after kill/respawn or reboot.  This started
  sometime after upgrade to bionic and has been consistent for the last
  couple of weeks.
  
  Looking at the process with perf, it seems that it is looping calling
  poll() via g_main_context_poll() via g_main_context_iterate in a hard
  loop.  In strace you can also see poll being called about 10,000
  times/second.
  
  poll([{fd=3, events=POLLIN}, {fd=11, events=POLLIN}], 2, 0) = 0
  (Timeout)
  
  gdb backtrace for the main thread reflected in the attached out.svg -
  setting a breakpoint g_main_context_iterate is being called continually
  but we never exit from g_main_loop_run.
  
+ (gdb) bt
+ #0  0x7f6e1ce30150 in g_main_context_iterate (context=0x55ca494d18c0, 
block=block@entry=1, dispatch=dispatch@entry=1, self=)
+ at ../../../../glib/gmain.c:3840
+ #1  0x7f6e1ce30662 in g_main_loop_run (loop=0x55ca4949f580) at 
../../../../glib/gmain.c:4099
+ #2  0x7f6e1df22710 in dbus_server_run_server (server=0x55ca494df1a0 
[ESourceRegistryServer]) at ./src/libebackend/e-dbus-server.c:247
+ #3  0x7f6e19502dae in ffi_call_unix64 () at 
/usr/lib/x86_64-linux-gnu/libffi.so.6
+ #4  0x7f6e1950271f in ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6
+ #5  0x7f6e1d10ab4d in g_cclosure_marshal_generic_va 
(closure=0x55ca494d8ab0, return_value=0x7ffd34330e10, instance=, 
args_list=, marshal_data=, n_params=0, 
param_types=0x0) at ../../../../gobject/gclosure.c:1604
+ #6  0x7f6e1d10a1a6 in _g_closure_invoke_va (closure=0x55ca494d8ab0, 
return_value=0x7ffd34330e10, instance=0x55ca494df1a0, args=0x7ffd34330ec0, 
n_params=0, param_types=0x0) at ../../../../gobject/gclosure.c:867
+ #7  0x7f6e1d1256df in

[Touch-packages] [Bug 1750947] Re: pulseaudio print lots of error when selecting unavailable profile

2018-03-07 Thread Hui Wang

** Description changed:

+ SRU Document:
+
+ [Impact]
+
+ A HDMI audio device usually has several output ports, each port
+ represents a profile in pulseaudio, without this patch, the puseaudio
+ always choose the first profile no matter it is active or not.
+
+ [Test Case]
+
+ connect each port of HDMI device, and check if the profile of that port
+ is active or not.
+
+ [Regression Potential]
+ no regression possibility, since this commit is already in artful and bionic.
+
+ [Other Info]
+
Only pulseaudio-xenial has this problem.

we need to backport this commit to pulseaudio-xenial.

https://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/?id=a222a07920731f3c4967faccab7469af50b428a4

After printing out the error logs, the kernel crashes and system hangs.

** Description changed:

SRU Document:

[Impact]

A HDMI audio device usually has several output ports, each port
represents a profile in pulseaudio, without this patch, the puseaudio
always choose the first profile no matter it is active or not.

[Test Case]

connect each port of HDMI device, and check if the profile of that port
is active or not.

[Regression Potential]
- no regression possibility, since this commit is already in artful and bionic.
+
+ no regression possibility, since this commit is already in artful and
+ bionic.

[Other Info]

Only pulseaudio-xenial has this problem.

we need to backport this commit to pulseaudio-xenial.

https://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/?id=a222a07920731f3c4967faccab7469af50b428a4

After printing out the error logs, the kernel crashes and system hangs.

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

Title:
pulseaudio print lots of error when selecting unavailable profile

Status in HWE Next:
New
Status in pulseaudio package in Ubuntu:
Fix Released
Status in pulseaudio source package in Xenial:
New

Bug description:
SRU Document:

[Impact]

A HDMI audio device usually has several output ports, each port
represents a profile in pulseaudio, without this patch, the puseaudio
always choose the first profile no matter it is active or not.

[Test Case]

connect each port of HDMI device, and check if the profile of that
port is active or not.

[Regression Potential]

no regression possibility, since this commit is already in artful and
bionic.

[Other Info]

Only pulseaudio-xenial has this problem.

we need to backport this commit to pulseaudio-xenial.

https://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/?id=a222a07920731f3c4967faccab7469af50b428a4

After printing out the error logs, the kernel crashes and system
hangs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1750947/+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 1750947] Re: pulseaudio print lots of error when selecting unavailable profile

2018-03-07 Thread Timo Aaltonen

added a pointer to this bug and uploaded

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

Title:
  pulseaudio print lots of error when selecting unavailable profile

Status in HWE Next:
  New
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  New

Bug description:
  Only pulseaudio-xenial has this problem.

  we need to backport this commit to pulseaudio-xenial.

  
https://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/?id=a222a07920731f3c4967faccab7469af50b428a4

  After printing out the error logs, the kernel crashes and system
  hangs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1750947/+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 1750947] Re: pulseaudio print lots of error when selecting unavailable profile

2018-03-07 Thread Timo Aaltonen

update the description to add the usual impact/test case/regression
potential etc

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

Title:
  pulseaudio print lots of error when selecting unavailable profile

Status in HWE Next:
  New
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  New

Bug description:
  Only pulseaudio-xenial has this problem.

  we need to backport this commit to pulseaudio-xenial.

  
https://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/?id=a222a07920731f3c4967faccab7469af50b428a4

  After printing out the error logs, the kernel crashes and system
  hangs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1750947/+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 1750947] Re: pulseaudio print lots of error when selecting unavailable profile

2018-03-07 Thread Timo Aaltonen

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

Title:
  pulseaudio print lots of error when selecting unavailable profile

Status in HWE Next:
  New
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  New

Bug description:
  Only pulseaudio-xenial has this problem.

  we need to backport this commit to pulseaudio-xenial.

  
https://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/?id=a222a07920731f3c4967faccab7469af50b428a4

  After printing out the error logs, the kernel crashes and system
  hangs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1750947/+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 1686189] Re: External monitor connecting problem on Intel graphics card

2018-03-07 Thread Kai-Heng Feng

Do you have package "xserver-xorg-video-intel"?

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

Title:
  External monitor connecting problem on Intel graphics card

Status in linux package in Ubuntu:
  Fix Released
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I am facing a problem with Intel Graphics driver. I have external
  monitor and in display settings the second monitor is detecting but
  it's not working, so could you email me a solution.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  Uname: Linux 4.4.25-040425-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Apr 25 21:45:16 2017
  DistUpgraded: 2017-04-25 21:07:40,819 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: i915-4.6.3-4.4.0, 1, 4.4.0-75-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05e9]
  InstallationDate: Installed on 2017-04-25 (0 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  MachineType: Dell Inc. Inspiron 3537
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.25-040425-generic 
root=UUID=3914e6d5-5c87-4816-8043-776ef4184d29 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2017-04-25 (0 days ago)
  dmi.bios.date: 04/30/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 03JPPR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A08
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd04/30/2014:svnDellInc.:pnInspiron3537:pvrA08:rvnDellInc.:rn03JPPR:rvrA00:cvnDellInc.:ct8:cvrA08:
  dmi.product.name: Inspiron 3537
  dmi.product.version: A08
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue Apr 25 21:37:24 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   17900 
   vendor AUO
  xserver.version: 2:1.18.4-0ubuntu0.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686189/+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 1718824] Re: The analogue audio does not work on the Dell USB Dock

2018-03-07 Thread Hui Wang

** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  The analogue audio does not work on the Dell USB Dock

Status in HWE Next:
  In Progress
Status in OEM Priority Project:
  Triaged
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  Fix Released
Status in pulseaudio source package in Artful:
  Fix Released

Bug description:
  SRU Document:

  [Impact]

  If users use the latest Dell USB Dock, e.g. TB16, they will found the
  analog audio (lineout jack) can't work under ubuntu linux

  [Test Case]

  After applying the fix, users can play sound via analog speaker or
  lineout freely. Without the fix, users can't play sound from lineout
  jack.

  [Regression Potential]

  No any possibility to introduce regression since this fix just adding
  a new dock's support, it does not change any existing code.

  [Other Info]

  No more info here

  Steps:
  1. Cold boot system with BME/IE connected
  2. Plug in a speaker to Line-out jack
  3. Set Analog Stereo Output from Sound settings

  Expected results: Line-out port can work

  Actual results: Line-out port not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1718824/+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 1750947] Re: pulseaudio print lots of error when selecting unavailable profile

2018-03-07 Thread Hui Wang

Already pushed the fix to ubuntu-xenial branch, and this is the debdiff
against 3.8. If everything is ok, please trigger the SRU build.

thx.


** Patch added: "pulseaudio_8.0-0ubuntu3.9.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1750947/+attachment/5072607/+files/pulseaudio_8.0-0ubuntu3.9.debdiff

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

Title:
  pulseaudio print lots of error when selecting unavailable profile

Status in HWE Next:
  New
Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  Only pulseaudio-xenial has this problem.

  we need to backport this commit to pulseaudio-xenial.

  
https://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/?id=a222a07920731f3c4967faccab7469af50b428a4

  After printing out the error logs, the kernel crashes and system
  hangs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1750947/+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 1742894] Re: Scilab does not start after some upgrades on Ubuntu Xenial

2018-03-07 Thread fabcap77

I observed the same problem also with Scilab under Ubuntu 14.04, with
the following version of libjogl2-java:

libjogl2-java/trusty,now 2.1.5-1ubuntu3 all [installed,automatic]
libjogl2-jni/trusty,now 2.1.5-1ubuntu3 amd64 [installed]

Is there a fix available for Ubuntu Trusty?

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

Title:
  Scilab does not start after some upgrades on Ubuntu Xenial

Status in Mesa:
  Confirmed
Status in libjogl2-java package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Invalid
Status in scilab package in Ubuntu:
  Invalid
Status in libjogl2-java source package in Xenial:
  Fix Released
Status in mesa source package in Xenial:
  Invalid
Status in scilab source package in Xenial:
  Invalid
Status in libjogl2-java source package in Artful:
  Fix Released
Status in mesa source package in Artful:
  Invalid
Status in scilab source package in Artful:
  Invalid
Status in scilab package in Debian:
  Fix Released

Bug description:
  [Impact]

  Software that use libjogl2-java (Scilab, Matlab,...) fail to run,
  because Mesa dropped 'Gallium' from the renderer string.

  [Test case]
  Steps to reproduce:
  1. have installed Scilab on Ubuntu Xenial system
  2. install system updates
  3. try to launch Scilab from GUI - it does not start
  4. try to launch Scilab from terminal - it does not start with the following 
output in the terminal:

  $ scilab
  Could not create a Scilab main class. Error:
  Exception in thread "main" java.lang.InternalError: XXX0 profile[1]: GL3bc -> 
profileImpl GL4bc !!! not mapped
   at com.jogamp.opengl.GLProfile.computeProfileMap(GLProfile.java:2071)
   at 
com.jogamp.opengl.GLProfile.initProfilesForDeviceCritical(GLProfile.java:1954)
   at com.jogamp.opengl.GLProfile.initProfilesForDevice(GLProfile.java:1875)
   at 
com.jogamp.opengl.GLProfile.initProfilesForDefaultDevices(GLProfile.java:1842)
   at com.jogamp.opengl.GLProfile.access$000(GLProfile.java:80)
   at com.jogamp.opengl.GLProfile$1.run(GLProfile.java:230)
   at java.security.AccessController.doPrivileged(Native Method)
   at com.jogamp.opengl.GLProfile.initSingleton(GLProfile.java:216)
   at com.jogamp.opengl.GLProfile.getProfileMap(GLProfile.java:2297)
   at com.jogamp.opengl.GLProfile.get(GLProfile.java:988)
   at com.jogamp.opengl.GLProfile.getDefault(GLProfile.java:722)
   at com.jogamp.opengl.GLProfile.getDefault(GLProfile.java:733)
   at org.scilab.modules.gui.SwingView.(Unknown Source)
   at org.scilab.modules.gui.SwingView.registerSwingView(Unknown Source)
   at org.scilab.modules.core.Scilab.(Unknown Source)

  Scilab cannot create Scilab Java Main-Class (we have not been able to
  find the main Scilab class. Check if the Scilab and thirdparty
  packages are available).

  Expected results:
  Scilab works normally on Ubuntu 16.04 LTS system.

  Actual results:
  see error above.

  [Regression potential]
  The fix is a simple oneliner that allows libjogl2-java to detect Mesa with 
both new and original version of Mesa.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1742894/+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 1753954] Re: Intel Whiskey Lake (WHL) graphics support

2018-03-07 Thread alex zhang

Whiskey Lake (WHL)
Package/pin compatible Quad core WHL (U42) or Dual core CNL (U22) design in 
common board with stuffing option Two versions of CPU Si will be compatible 
with this platform:
•   WHL U4+2 derived based on Coffelake-U with CNL-LP PCH
Use CFL-S/H code already in upstream(4.13-4.15)
PCI ID Changes: Graphics Related(v4.16)
•   Cannonlake Prime –U 2+2 w/ CNL-H PCH and CNL-LP PCH
Use CNL-Y features (4.13-4.16)

Please don't forget CNL-H based components. Above is what I got from
Intel.

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

Title:
  Intel Whiskey Lake (WHL) graphics support

Status in libdrm package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  New
Status in xorg-server-hwe-16.04 package in Ubuntu:
  Invalid
Status in libdrm source package in Xenial:
  New
Status in linux-oem source package in Xenial:
  New
Status in mesa source package in Xenial:
  New
Status in xorg-server source package in Xenial:
  Invalid
Status in xorg-server-hwe-16.04 source package in Xenial:
  New
Status in libdrm source package in Bionic:
  Fix Released
Status in linux-oem source package in Bionic:
  Fix Released
Status in mesa source package in Bionic:
  Fix Released
Status in xorg-server source package in Bionic:
  New
Status in xorg-server-hwe-16.04 source package in Bionic:
  Invalid

Bug description:
  [Impact]
  WHL is basically CFL-U with new PCI-ID's that are needed in the kernel, 
libdrm, mesa and xserver.

  [Test Case]

  Test the installation on a WHL machine, the graphical session should
  have full acceleration after these updates.

  [Regression Potential]

  None, just adds PCI-ID's to existing drivers.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1753954/+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 1754205] Re: perl crashed with SIGABRT in _dbus_abort()

2018-03-07 Thread Apport retracing service

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

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 #1743216, 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/1754205/+attachment/5072514/+files/CoreDump.gz

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

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

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

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

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

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

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

** 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 perl in Ubuntu.
https://bugs.launchpad.net/bugs/1754205

Title:
  perl crashed with SIGABRT in _dbus_abort()

Status in perl package in Ubuntu:
  New

Bug description:
  Erro ocorrido sem motivo

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: perl-base 5.26.1-5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Budgie:GNOME
  Date: Wed Mar  7 22:19:42 2018
  ExecutablePath: /usr/bin/perl
  InstallationDate: Installed on 2018-01-29 (37 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180129)
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: perl
  StacktraceTop:
   _dbus_abort () from /lib/x86_64-linux-gnu/libdbus-1.so.3
   _dbus_warn_check_failed () from /lib/x86_64-linux-gnu/libdbus-1.so.3
   dbus_message_iter_append_basic () from /lib/x86_64-linux-gnu/libdbus-1.so.3
   ?? () from /usr/lib/x86_64-linux-gnu/perl5/5.26/auto/Net/DBus/DBus.so
   Perl_pp_entersub ()
  Title: perl crashed with SIGABRT in _dbus_abort()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display

2018-03-07 Thread Chazall1

All functioning as expected with the nvidia-driver-390.

Thank you

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

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Incomplete

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

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

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

[Touch-packages] [Bug 1750884] Re: [2.4, bionic] /etc/resolv.conf not configured correctly in Bionic, leads to no DNS resolution

2018-03-07 Thread Jason Hobbs

Is there a workaround for this? I can just rm /etc/resolv.conf and
create it with the contents I want, right?

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

Title:
  [2.4, bionic] /etc/resolv.conf not configured correctly in Bionic,
  leads to no DNS resolution

Status in cloud-init:
  New
Status in MAAS:
  Triaged
Status in nplan package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  When deploying Bionic, /etc/resolv.conf is not configured correctly,
  which leads to no DNS resolution. In the output below, you will see
  that netplan config is correctly to the 10.90.90.1 nameserver, but in
  resolv.conf that's a local address.

  Resolv.conf should really be configured to use the provided DNS
  server(s). That said, despite that fact, DNS resolution doesn't work
  with the local address.

  Bionic
  --

  ubuntu@node01:~$ cat /etc/netplan/50-cloud-init.yaml
  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  network:
  version: 2
  ethernets:
  enp0s25:
  match:
  macaddress: b8:ae:ed:7d:17:d2
  mtu: 1500
  nameservers:
  addresses:
  - 10.90.90.1
  search:
  - maaslab
  - maas
  set-name: enp0s25
  bridges:
  br0:
  addresses:
  - 10.90.90.3/24
  gateway4: 10.90.90.1
  interfaces:
  - enp0s25
  parameters:
  forward-delay: 15
  stp: false
  ubuntu@node01:~$ cat /etc/resolv.conf
  # This file is managed by man:systemd-resolved(8). Do not edit.
  #
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.
  nameserver 127.0.0.53

  search maaslab maas
  ubuntu@node01:~$ ping google.com
  ping: google.com: Temporary failure in name resolution

  [...]

  ubuntu@node01:~$ sudo vim /etc/resolv.conf
  ubuntu@node01:~$ cat /etc/resolv.conf
  # This file is managed by man:systemd-resolved(8). Do not edit.
  #
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.
  nameserver 10.90.90.1

  search maaslab maas
  ubuntu@node01:~$ ping google.com
  PING google.com (172.217.0.174) 56(84) bytes of data.
  64 bytes from mia09s16-in-f14.1e100.net (172.217.0.174): icmp_seq=1 ttl=52 
time=4.46 ms
  64 bytes from mia09s16-in-f14.1e100.net (172.217.0.174): icmp_seq=2 ttl=52 
time=4.38 ms

  =
  Xenial
  ==

  ubuntu@node05:~$ cat /etc/network/interfaces.d/50-cloud-init.cfg
  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  auto lo
  iface lo inet loopback
  dns-nameservers 10.90.90.1
  dns-search maaslab maas

  auto enp0s25
  iface enp0s25 inet static
  address 10.90.90.162/24
  gateway 10.90.90.1
  mtu 1500
  ubuntu@node05:~$ cat /etc/resolv.conf
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  nameserver 10.90.90.1
  search maaslab maas

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1750884/+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 1753884] Re: session logout after suspend

2018-03-07 Thread Simon

Christopher, thanks for responding so quickly!

It took me a while to download the newest ISO.

I've been able to narrow it down a bit more as well: the log out only
happens if I have my second monitor plugged in. Sometimes (but not
always) the second monitor will flash the "logged out" screen for a
second or two before going dim. If I unplug the second monitor and close
the lid of my computer I log in and it's still the same session.

I have "Suspend even if external monitor is plugged in" toggled in Tweak
Tools.

1) No, my session is not logged out if I suspend via the GUI with the
lid open.

2) There are! Is it safe to upload that file? I can do so.

3) I'm fairly sure it's happened since I initially installed 16.04

4) With the live USB I don't think I can set up a user account that will
get logged out? When I close the lid of my laptop without the external
monitor plugged in there is no log in screen and I just see the desktop
(even when I toggle that the user is not logged in automatically). With
the external monitor plugged in the desktop just switches. I couldn't
find a toggle for the "Suspend even if external monitor is plugged in"
option. I'm happy to actually try upgrading my machine to 18.04 or
17.10, but that would lose you your test scenario if it ends up working?

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

Title:
   session logout after suspend

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  When I close the lid of my laptop, my session gets logged out, where I
  would expect the lock screen simply to come up.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Tue Mar  6 18:07:50 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
     Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c]
  InstallationDate: Installed on 2018-02-15 (19 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: LENOVO 20AQ009HUS
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic 
root=UUID=6f20d80f-81f4-40c1-aafd-95b2c5de55ed ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/29/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GJET78WW (2.28 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20AQ009HUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGJET78WW(2.28):bd07/29/2014:svnLENOVO:pn20AQ009HUS:pvrThinkPadT440s:rvnLENOVO:rn20AQ009HUS:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T440s
  dmi.product.name: 20AQ009HUS
  dmi.product.version: ThinkPad T440s
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1753884/+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 1754186] [NEW] Night Light only affects a single monitor now

2018-03-07 Thread Nathaniel W. Turner

Public bug reported:

The Display settings have a "Night Light" option which allows reducing blue 
light at night.
In Ubuntu 17.10, this worked great, and the setting took effect on all 3 of my 
monitors.
In Bionic, only the 1st monitor is affected; the other 2 remain at the default 
color temperature.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: GNOME
Date: Wed Mar  7 17:51:02 2018
DistUpgraded: 2018-03-07 12:52:16,474 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Tahiti XT [Radeon HD 7970/8970 OEM / R9 
280X] [1002:6798] (prog-if 00 [VGA controller])
   Subsystem: XFX Pine Group Inc. Double D HD 7970 Black Edition [1682:3211]
InstallationDate: Installed on 2014-08-21 (1294 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
MachineType: To be filled by O.E.M. To be filled by O.E.M.
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=98fea0b5-8fa6-4625-bae5-b85a70783a13 ro quiet splash nomdmonddf 
nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to bionic on 2018-03-07 (0 days ago)
dmi.bios.date: 04/18/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1208
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: SABERTOOTH 990FX
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
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.:bvr1208:bd04/18/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FX:rvrRev1.xx: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.90-1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-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: Sat Oct  7 12:18:20 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.3-1ubuntu1.1
xserver.video_driver: radeon

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


** Tags: amd64 apport-bug bionic regression reproducible single-occurrence 
third-party-packages ubuntu wayland-session

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

Title:
  Night Light only affects a single monitor now

Status in xorg package in Ubuntu:
  New

Bug description:
  The Display settings have a "Night Light" option which allows reducing blue 
light at night.
  In Ubuntu 17.10, this worked great, and the setting took effect on all 3 of 
my monitors.
  In Bionic, only the 1st monitor is affected; the other 2 remain at the 
default color temperature.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Wed Mar  7 17:51:02 2018
  DistUpgraded: 2018-03-07 12:52:16,474 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Tahiti XT [Radeon HD 7970/8970 OEM / 
R9 280X] [1002:6798] (prog-if 00 [VGA controller])
 Subsystem: XFX Pine Group Inc. Double D HD 7970 Black Edition [1682:3211]
  InstallationDate: Installed on 2014-08-21 (1294 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty

[Touch-packages] [Bug 50093] Re: Some sysctl's are ignored on boot

2018-03-07 Thread Dave Vree

bumping another year -- now 11 years old and still a real problem

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

Title:
  Some sysctl's are ignored on boot

Status in procps package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: procps

  /etc/init.d/procps.sh comes too early in the boot process to apply a
  lot of sysctl's. As it runs before networking modules are loaded and
  filesystems are mounted, there are quite a lot of commonly-used
  sysctl's which are simply ignored on boot and produce errors to the
  console.

  Simply renaming the symlink from S17 to > S40 probably isn't a great
  solution, as there are probably folk who want and expect some sysctl's
  to be applied before filesystems are mounted and so on. However,
  simply ugnoring something as important as sysctl settings isn't really
  on. Administrators expect the settings in /etc/sysctl.conf to take
  effect.

  One sto-gap solution would be to run sysctl -p twice; once at S17 and once at 
S41. There may still be some warnings and errors, but everything would be 
applied. A different, more complex approach might be to re-architect the sysctl 
configuration into something like;
   
  /etc/sysctl.d/$modulename

  and have the userland module-loading binaries take care of applying
  them after modules are loaded. Though this may take care of explicitly
  loaded modules only, I'm not sure.

  Incidentally, /etc/sysctl.conf still refers to
  /etc/networking/options, but hasn't that been deprecated?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/50093/+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 1754173] [NEW] Laptop has integrated Intel and discrete Nvidia graphics, the Intel graphics are not detected. Worked fine with 17.10.

2018-03-07 Thread Niels Roetert

Public bug reported:

HP ZBook 15, 2014 model.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.25  Wed Jan 24 20:02:43 
PST 2018
 GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-5ubuntu1)
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: Budgie:GNOME
Date: Wed Mar  7 22:38:17 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus: nvidia, 390.25, 4.15.0-10-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation GK208GLM [Quadro K610M] [10de:12b9] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Hewlett-Packard Company GK208GLM [Quadro K610M] [103c:197b]
InstallationDate: Installed on 2018-03-07 (0 days ago)
InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180307)
MachineType: Hewlett-Packard HP ZBook 15
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=752bcb50-d5d1-4251-a33b-18fc83b6dd9e ro quiet splash vt.handoff=1
SourcePackage: mesa
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/24/2018
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: L70 Ver. 01.39
dmi.board.name: 1909
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 94.56
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL70Ver.01.39:bd01/24/2018:svnHewlett-Packard:pnHPZBook15:pvrA3009DD10303:rvnHewlett-Packard:rn1909:rvrKBCVersion94.56:cvnHewlett-Packard:ct10:cvr:
dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
dmi.product.name: HP ZBook 15
dmi.product.version: A3009DD10303
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.90-1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


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

Title:
  Laptop has integrated Intel and discrete Nvidia graphics, the Intel
  graphics are not detected. Worked fine with 17.10.

Status in mesa package in Ubuntu:
  New

Bug description:
  HP ZBook 15, 2014 model.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.25  Wed Jan 24 20:02:43 
PST 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-5ubuntu1)
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: Budgie:GNOME
  Date: Wed Mar  7 22:38:17 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 390.25, 4.15.0-10-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GK208GLM [Quadro K610M] [10de:12b9] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Hewlett-Packard Company GK208GLM [Quadro K610M] [103c:197b]
  InstallationDate: Installed on 2018-03-07 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180307)
  MachineType: Hewlett-Packard HP ZBook 15
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=752bcb50-d5d1-4251-a33b-18fc83b6dd9e ro quiet splash vt.handoff=1
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/24/2018
  dmi.bios.vendor: Hewlett-Pa

[Touch-packages] [Bug 1752938] Re: Upgrading Ubuntu 18.04 disables GPU hardware acceleration

2018-03-07 Thread Jhonny Oliveira

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

I'm facing huge difficulties after this upgrade. All games I'm running
with wine stopped working. I did not test others. They start, but I
either get a black or purple window, no image. Can somebody point me the
right way to debug and solve this?

I have an AMD Radeon HD 7850 installed.

Making a basic test, it seems to perform better with software
rendering... ?!?

$ glxgears -info
GL_RENDERER   = AMD PITCAIRN (DRM 2.50.0 / 4.15.0-11-generic, LLVM 5.0.1)
GL_VERSION= 3.0 Mesa 18.0.0-rc4
GL_VENDOR = X.Org
(...)
VisualID 1064, 0x428
355 frames in 5.0 seconds = 70.940 FPS
300 frames in 5.0 seconds = 59.997 FPS

$ LIBGL_ALWAYS_SOFTWARE=1 glxgears -info
GL_RENDERER   = llvmpipe (LLVM 5.0, 128 bits)
GL_VERSION= 3.0 Mesa 18.0.0-rc4
GL_VENDOR = VMware, Inc.
(...)
VisualID 1064, 0x428
6604 frames in 5.0 seconds = 1320.753 FPS
6758 frames in 5.0 seconds = 1351.475 FPS

Further details:
$ lspci -nn | grep -E 'VGA|Display'
01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Pitcairn PRO [Radeon HD 7850 / R7 265 / R9 270 1024SP] [1002:6819]

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

Title:
  Upgrading Ubuntu 18.04 disables GPU hardware acceleration

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I don't know which package causes this problem. The thing is ugrading
  Ubuntu 18.04 disables my GPU hardware acceleration.

  glxinfo_before_upgrade 
  OpenGL vendor string: X.Org
  OpenGL renderer string: Radeon RX 560 Series (POLARIS11 / DRM 3.23.0 / 
4.15.0-10-generic, LLVM 5.0.1)
  OpenGL core profile version string: 4.5 (Core Profile) Mesa 17.3.3

  glxinfo_after_upgrade 
  OpenGL vendor string: VMware, Inc.
  OpenGL renderer string: llvmpipe (LLVM 5.0, 256 bits)
  OpenGL core profile version string: 3.3 (Core Profile) Mesa 17.3.3

  This problem is reproducible.

  Steps to reproduce:
  1. Install Ubuntu 18.04 daily live. I've tried Kubuntu 18.04 Feb 26's daily 
live(the installer in Mar 1 crashes which prevents me from installing it) and 
Xubuntu 18.04 Mar 2's daily live. Ubuntu is utilizing my GPU in live cd session 
and after the fresh install Ubuntu is also utilizing my GPU.
  2. Reboot into the newly installed system, do a dist-upgrade and reboot 
again. Opengl renderer falls back to llvmpipe.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Sat Mar  3 00:58:35 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Polaris11] [1002:67ff] (rev 
cf) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Baffin [Radeon RX 560] [1043:04be]
  InstallationDate: Installed on 2018-03-02 (0 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180302)
  MachineType: Gigabyte Technology Co., Ltd. B85M-D3V-A
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed 
root=UUID=d2dcc7eb-84ca-4102-9ae1-239de26d113c ro quiet splash vt.handoff=1
  Renderer: Software
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/12/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85M-D3V-A
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd02/12/2015:svnGigabyteTechnologyCo.,Ltd.:pnB85M-D3V-A:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB85M-D3V-A:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: B85M-D3V-A
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.3.3-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.3.3-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1

[Touch-packages] [Bug 1164016] Re: restore type-ahead find

2018-03-07 Thread Henrik Holmboe

@adpsimpson-gmail there is already #181:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/181

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

Title:
  restore type-ahead find

Status in Nautilus:
  Expired
Status in nautilus package in Ubuntu:
  Fix Released
Status in ubuntu-settings package in Ubuntu:
  Fix Released

Bug description:
  GNOME removed type-ahead find in Nautilus 3.6, not without
  controversy:

  https://mail.gnome.org/archives/nautilus-
  list/2012-August/msg2.html

  Now when you type in a Nautilus window, Nautilus immediately performs
  a search in the current directory and all its subdirectories.  I
  personally find this annoying.  If I want to search, I'll click the
  search icon.  Often I'm looking at a long directory listing and simply
  want to jump to a certain point in it, and type-ahead find works great
  for that.

  Would Ubuntu consider patching type-ahead find back in?

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/1164016/+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 1754140] [NEW] Gnome gets stuck in overview mode

2018-03-07 Thread Eric Stith

Public bug reported:

I'm running Ubuntu 17.10, and I have repeatedly had a problem with the
desktop environment getting stuck in overview mode.  When stuck, I can
close and select windows, and access the menus at on the top bar, but I
cannot exit overview mode.  The only solution I've found is to log out
and log back in.  I'm not exactly sure what combination of circumstances
causes it to happen, but it seems to happen more often if invoked via
the corner hover point.  It also happens in both Wayland and Xorg.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: ubuntu-desktop 1.404.1
Uname: Linux 4.14.15-041415-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CurrentDesktop: GNOME
Date: Wed Mar  7 11:02:02 2018
InstallationDate: Installed on 2017-05-04 (307 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntu-meta
UpgradeStatus: Upgraded to artful on 2017-10-29 (129 days ago)

** Affects: ubuntu-meta (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug artful

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

Title:
  Gnome gets stuck in overview mode

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  I'm running Ubuntu 17.10, and I have repeatedly had a problem with the
  desktop environment getting stuck in overview mode.  When stuck, I can
  close and select windows, and access the menus at on the top bar, but
  I cannot exit overview mode.  The only solution I've found is to log
  out and log back in.  I'm not exactly sure what combination of
  circumstances causes it to happen, but it seems to happen more often
  if invoked via the corner hover point.  It also happens in both
  Wayland and Xorg.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ubuntu-desktop 1.404.1
  Uname: Linux 4.14.15-041415-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Mar  7 11:02:02 2018
  InstallationDate: Installed on 2017-05-04 (307 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-meta
  UpgradeStatus: Upgraded to artful on 2017-10-29 (129 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1754140/+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 1753884] Re: session logout after suspend

2018-03-07 Thread Christopher M. Penalver

Simon, thank you for reporting this and helping make Ubuntu better.

1) To clarify, if you keep the lid open, and suspend via the GUI, is
your session logged out after resume from suspend?

2) After the session logout, are there crash files in /var/crash?

3) Is this issue something that started to happen after an update?

4) To see if this is already resolved in Ubuntu, could you please test
http://cdimage.ubuntu.com/daily-live/current/ and advise to the results?

** Description changed:

- This is a new bug report for
- https://bugs.launchpad.net/ubuntu/+source/linux/+bug/362075
- 
- I am running Ubuntu 16.04.4 LTS 64-bit + gnome, the standard
- installation as downloaded from the Ubuntu website, on a Lenovo ThinkPad
- T440s.
- 
  When I close the lid of my laptop, my session gets logged out, where I
  would expect the lock screen simply to come up.
- 
- The workaround suggested in the original bug report (which was for
- kubuntu 9.04) suggests to disable the lock screen on resume option, but
- I can't find this option on 16.04.
- 
- It's also not a super desirable work-around. I want to still have to log
- in if I close the lid of my laptop.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Tue Mar  6 18:07:50 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
-  Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
-Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c]
+  Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
+    Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c]
  InstallationDate: Installed on 2018-02-15 (19 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: LENOVO 20AQ009HUS
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic 
root=UUID=6f20d80f-81f4-40c1-aafd-95b2c5de55ed ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/29/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GJET78WW (2.28 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20AQ009HUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGJET78WW(2.28):bd07/29/2014:svnLENOVO:pn20AQ009HUS:pvrThinkPadT440s:rvnLENOVO:rn20AQ009HUS:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T440s
  dmi.product.name: 20AQ009HUS
  dmi.product.version: ThinkPad T440s
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

** Tags added: bios-outdated-2.47

** Changed in: xorg (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
   session logout after suspend

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  When I close the lid of my laptop, my session gets logged out, where I
  would expect the lock screen simply to come up.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop:

[Touch-packages] [Bug 1754107] Re: E: Sub-process /usr/bin/dpkg returned an error code (1)

2018-03-07 Thread Hans Joachim Desserud

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

** This bug has been marked a duplicate of bug 1754106
   E: Sub-process /usr/bin/dpkg returned an error code (1)

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

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

Status in procps package in Ubuntu:
  New

Bug description:
  after 
  sudo apt-get install -f

  update-rc.d: warning: start and stop actions are no longer supported; falling 
back to defaults
  insserv: warning: script 'K01vpnagentd_init' missing LSB tags and overrides
  insserv: warning: script 'vpnagentd_init' missing LSB tags and overrides
  insserv: There is a loop between service plymouth and urandom if started
  insserv:  loop involving service urandom at depth 4
  insserv:  loop involving service hwclock at depth 3
  insserv: There is a loop between service vpnagentd_init and udev if started
  insserv:  loop involving service udev at depth 1
  insserv: There is a loop at service vpnagentd_init if started
  insserv: There is a loop at service plymouth if started
  insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
  insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
  insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
  insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
  insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
  insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
  insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
  insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
  insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
  insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
  insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
  insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
  insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
  insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
  insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
  insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
  insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
  insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
  insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
  insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
  insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
  insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
  insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
  insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
  insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
  insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
  insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
  insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
  insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
  insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
  insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
  insserv: Starting vpnagentd_init depends on plymouth and therefore on

[Touch-packages] [Bug 1754106] [NEW] E: Sub-process /usr/bin/dpkg returned an error code (1)

2018-03-07 Thread Elo Bers

Public bug reported:

after 
sudo apt-get install -f

update-rc.d: warning: start and stop actions are no longer supported; falling 
back to defaults
insserv: warning: script 'K01vpnagentd_init' missing LSB tags and overrides
insserv: warning: script 'vpnagentd_init' missing LSB tags and overrides
insserv: There is a loop between service plymouth and urandom if started
insserv:  loop involving service urandom at depth 4
insserv:  loop involving service hwclock at depth 3
insserv: There is a loop between service vpnagentd_init and udev if started
insserv:  loop involving service udev at depth 1
insserv: There is a loop at service vpnagentd_init if started
insserv: There is a loop at service plymouth if started
insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting vpnagentd_init depends on plymouth and therefore

[Touch-packages] [Bug 1754107] [NEW] E: Sub-process /usr/bin/dpkg returned an error code (1)

2018-03-07 Thread Elo Bers

Public bug reported:

after 
sudo apt-get install -f

update-rc.d: warning: start and stop actions are no longer supported; falling 
back to defaults
insserv: warning: script 'K01vpnagentd_init' missing LSB tags and overrides
insserv: warning: script 'vpnagentd_init' missing LSB tags and overrides
insserv: There is a loop between service plymouth and urandom if started
insserv:  loop involving service urandom at depth 4
insserv:  loop involving service hwclock at depth 3
insserv: There is a loop between service vpnagentd_init and udev if started
insserv:  loop involving service udev at depth 1
insserv: There is a loop at service vpnagentd_init if started
insserv: There is a loop at service plymouth if started
insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting vpnagentd_init depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting vpnagentd_init depends on plymouth and therefore

[Touch-packages] [Bug 1164016] Re: restore type-ahead find

2018-03-07 Thread Andrew Simpson

> Oh I see why: most of us cannot change back the status of the bug once
it has been changed to "fix released" (which is stupid, too).

If that is genuinely the reason (and this bug has been marked as "Fix
Released" since Jan 2014, so it seems correct), then is it not time to
raise a new bug?

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

Title:
  restore type-ahead find

Status in Nautilus:
  Expired
Status in nautilus package in Ubuntu:
  Fix Released
Status in ubuntu-settings package in Ubuntu:
  Fix Released

Bug description:
  GNOME removed type-ahead find in Nautilus 3.6, not without
  controversy:

  https://mail.gnome.org/archives/nautilus-
  list/2012-August/msg2.html

  Now when you type in a Nautilus window, Nautilus immediately performs
  a search in the current directory and all its subdirectories.  I
  personally find this annoying.  If I want to search, I'll click the
  search icon.  Often I'm looking at a long directory listing and simply
  want to jump to a certain point in it, and type-ahead find works great
  for that.

  Would Ubuntu consider patching type-ahead find back in?

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/1164016/+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 1754092] [NEW] firefox esr loading bookmark limbo

2018-03-07 Thread Galen Thurber

Public bug reported:

on three computers I use Firefox ESR
which all have the odd behaviour of not loading a bookmark.
I'll select a bookmark ex: youtube.com and the tab icon will rotate but the 
page never loads & never times out. The limbo will happen with various 
bookmarks, cache has been cleared.
To fix the limbo problem I'll hit enter once in the address bar.
The limbo happens on 
Description:Ubuntu 16.04.4 LTS
Release:16.04
and
Ubuntu 14.04.5LTS
and MX Linux 17

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

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

Title:
  firefox esr loading bookmark limbo

Status in apt package in Ubuntu:
  New

Bug description:
  on three computers I use Firefox ESR
  which all have the odd behaviour of not loading a bookmark.
  I'll select a bookmark ex: youtube.com and the tab icon will rotate but the 
page never loads & never times out. The limbo will happen with various 
bookmarks, cache has been cleared.
  To fix the limbo problem I'll hit enter once in the address bar.
  The limbo happens on 
  Description:  Ubuntu 16.04.4 LTS
  Release:  16.04
  and
  Ubuntu 14.04.5LTS
  and MX Linux 17

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1754092/+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 1754052] Re: Dell Latitude 7480 press shift keys triggers random mouseclick when `Tap to click` enabled on touchpad.

2018-03-07 Thread Timo Aaltonen

** Package changed: xorg (Ubuntu) => linux (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/1754052

Title:
  Dell Latitude 7480 press shift keys triggers random mouseclick when
  `Tap to click` enabled on touchpad.

Status in linux package in Ubuntu:
  New

Bug description:
  In Ubuntu 16.04.3 and 17.10.1 holding down either shift key on a Dell
  Latitude 7480 causes random mouse clicks to occur without being
  nowhere near the touchpad with palms. No external mouse/keyboard
  connected. Disabling `Tap to click` in `Mouse & Touchpad` settings
  makes the problem go away. The problem is not present in 14.04.5,
  whether installed or live CD.

  How to reproduce:

  1. On a Dell Latitude 7480 live boot (or install) one of the following images:
  - ubuntu-16.04.3-desktop-amd64.iso
  - ubuntu-17.10.1-desktop-amd64.iso

  2. Open `Mouse & Touchpad` and make sure `Tap to click` is enabled.
  3. Click `Test Your Settings` and make sure window has focus.
  4. Hold down either shift key and after a few seconds single/double clicks 
start registering.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
  Uname: Linux 4.10.0-28-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CasperVersion: 1.376.2
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed Mar  7 13:00:21 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:07a0]
  LiveMediaBuild: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
  MachineType: Dell Inc. Latitude 7480
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/username.seed boot=casper quiet splash ---
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/30/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.2
  dmi.board.name: 00F6D3
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.2:bd01/30/2018:svnDellInc.:pnLatitude7480:pvr:rvnDellInc.:rn00F6D3:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.name: Latitude 7480
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1754052/+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 1528921] Re: rsync hangs on select(5, [], [4], [], {60, 0}

2018-03-07 Thread David Britton

Thanks for the nice update on the bug.  This is clearly something you
can reproduce and are able to trigger.  However, I agree with your
analysis that it could be a network configuration issue, but one that
requires some deep support in order to get to the bottom of.

I suggest that you carry on debugging, and even use the bug for more
debugging information.  As a suggestion, you might get more visibility
for deep support on rsync issues at:

https://askubuntu.com/

or at an rsync specific forum.  I will mark this as Incomplete for now,
if you feel there is an actionable bug to fix in rsync, you can always
re-open or ask on this bug.


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

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

Title:
  rsync hangs on select(5, [], [4], [], {60, 0}

Status in rsync package in Ubuntu:
  Incomplete

Bug description:
  In the last few months my home directory backup stopped completing.
  I've been able to reproduce the problem on a single subdirectory
  although I had to add the --debug=all flag to reproduce it on that
  smaller directory.  Specifically, this command never completes:

  rsync --debug=all -avz /tmp/html2 /tmp/rsynctest/

  The html2 directory is a copy of
  gnuradio-3.7.8.1/build/docs/doxygen/html .

  When I strace the command, I see this:
  write(1, "sender finished /tmp/html2/atsc_"..., 58sender finished 
/tmp/html2/atsc__interleaver_8h__incl.md5
  ) = 58
  write(1, "send_files(338, /tmp/html2/atsc_"..., 59send_files(338, 
/tmp/html2/atsc__interleaver_8h__incl.png)
  ) = 59
  open("html2/atsc__interleaver_8h__incl.png", O_RDONLY|O_LARGEFILE) = 3
  fstat64(3, {st_mode=S_IFREG|0664, st_size=264657, ...}) = 0
  write(1, "html2/atsc__interleaver_8h__incl"..., 
37html2/atsc__interleaver_8h__incl.png
  ) = 37
  read(3, 
"\211PNG\r\n\32\n\0\0\0\rIHDR\0\0\n\253\0\0\2\233\10\6\0\0\0h\242\""..., 
262144) = 262144
  select(6, [5], [4], [5], {60, 0})   = 2 (in [5], out [4], left {59, 
96})
  read(5, 
"\0\0\0\0\0\0\0\1\0\240\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\1\0\240\0\0\0"..., 95) 
= 95
  write(4, 
"r\311\0\7\177\377\232\237\264\272e\300\300\240\316\264&\314\301\252*\37\256y\225g\373^\315j\370\350"...,
 51574) = 51574
  select(5, [], [4], [], {60, 0}) = 1 (out [4], left {59, 97})
  write(4, 
"\7\320\0\7\177\377\234|\7X\223Y\273\255c\27\25f\306\212\202\214#E\272\212t\1\225A\fU"...,
 53259) = 53259
  select(5, [], [4], [], {60, 0}

  The select command times out over and over.  I get the same behavior
  when trying to back up my entire home directory but I don't need the
  --debug=all flag in that case.


  lsb_release -rd
  Description:Ubuntu 14.04.3 LTS
  Release:14.04

  apt-cache policy rsync
  rsync:
Installed: 3.1.0-2ubuntu0.1
Candidate: 3.1.0-2ubuntu0.1
Version table:
   *** 3.1.0-2ubuntu0.1 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main i386 
Packages
  500 http://security.ubuntu.com/ubuntu/ trusty-security/main i386 
Packages
  100 /var/lib/dpkg/status
   3.1.0-2 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/main i386 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: rsync 3.1.0-2ubuntu0.1
  ProcVersionSignature: Ubuntu 3.13.0-74.118-generic 3.13.11-ckt30
  Uname: Linux 3.13.0-74-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: i386
  CurrentDesktop: KDE
  Date: Wed Dec 23 09:44:17 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2010-09-18 (1922 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta i386 (20100901.1)
  SourcePackage: rsync
  UpgradeStatus: Upgraded to trusty on 2014-12-27 (361 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1528921/+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 1686189] Re: External monitor connecting problem on Intel graphics card

2018-03-07 Thread mauro

Hi there,

I'm facing still this problem with kernel 4.4.0-116-generic

Any documentation I can post to help?
Dmesg?

thanks

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

Title:
  External monitor connecting problem on Intel graphics card

Status in linux package in Ubuntu:
  Fix Released
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I am facing a problem with Intel Graphics driver. I have external
  monitor and in display settings the second monitor is detecting but
  it's not working, so could you email me a solution.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  Uname: Linux 4.4.25-040425-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Apr 25 21:45:16 2017
  DistUpgraded: 2017-04-25 21:07:40,819 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: i915-4.6.3-4.4.0, 1, 4.4.0-75-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05e9]
  InstallationDate: Installed on 2017-04-25 (0 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  MachineType: Dell Inc. Inspiron 3537
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.25-040425-generic 
root=UUID=3914e6d5-5c87-4816-8043-776ef4184d29 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2017-04-25 (0 days ago)
  dmi.bios.date: 04/30/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 03JPPR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A08
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd04/30/2014:svnDellInc.:pnInspiron3537:pvrA08:rvnDellInc.:rn03JPPR:rvrA00:cvnDellInc.:ct8:cvrA08:
  dmi.product.name: Inspiron 3537
  dmi.product.version: A08
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue Apr 25 21:37:24 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   17900 
   vendor AUO
  xserver.version: 2:1.18.4-0ubuntu0.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686189/+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 1164016] Re: restore type-ahead find

2018-03-07 Thread teo1978

@109 this is already known to be the wrong behavior. It was introduced long ago 
by the hopelessly stupid Nautilus people, and patched by Ubuntu to reestablish 
the old sensible behavior, but something must have gone wrong in the latest 
release and so the idiocy has resurfaced.
What I don't understand is how it can be taking so long to fix again.

Oh I see why: most of us cannot change back the status of the bug once
it has been changed to "fix released" (which is stupid, too).

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

Title:
  restore type-ahead find

Status in Nautilus:
  Expired
Status in nautilus package in Ubuntu:
  Fix Released
Status in ubuntu-settings package in Ubuntu:
  Fix Released

Bug description:
  GNOME removed type-ahead find in Nautilus 3.6, not without
  controversy:

  https://mail.gnome.org/archives/nautilus-
  list/2012-August/msg2.html

  Now when you type in a Nautilus window, Nautilus immediately performs
  a search in the current directory and all its subdirectories.  I
  personally find this annoying.  If I want to search, I'll click the
  search icon.  Often I'm looking at a long directory listing and simply
  want to jump to a certain point in it, and type-ahead find works great
  for that.

  Would Ubuntu consider patching type-ahead find back in?

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/1164016/+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 1754068] Re: vim-tiny doesn't work well with git commit editing comments

2018-03-07 Thread Cui Wei

vim-tiny should skip some syntax from /usr/share/vim/vim80/debian.vim
that is not supported.

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

Title:
  vim-tiny doesn't work well with git commit editing comments

Status in vim package in Ubuntu:
  New

Bug description:
  1) Ubuntu 18.04;
  2) remove nano, vim-runtime (full version);
  3) install vim-tiny;
  4) git a git-repo and do some changes, then press 'git commit -a';
  5) vim-tiny will always report many errors as follows:

  
  Error detected while processing /usr/share/vim/vim80/debian.vim:
  line   29:
  E319: Sorry, the command is not available in this version: function! 
MapExists(name, modes)
  line   30:
  E319: Sorry, the command is not available in this version:   for mode in 
split(a:modes, '\zs')
  line   34:
  E319: Sorry, the command is not available in this version:   endfor
  line   35:
  E319: Sorry, the command is not available in this version:   return 0
  line   36:
  E319: Sorry, the command is not available in this version: endfunction
  Press ENTER or type command to continue

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: vim-tiny 2:8.0.1401-1ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Wed Mar  7 23:21:55 2018
  SourcePackage: vim
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.vim.vimrc.tiny: 2018-03-07T23:21:15.792000

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1754068/+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 1754068] [NEW] vim-tiny doesn't work well with git commit editing comments

2018-03-07 Thread Cui Wei

Public bug reported:

1) Ubuntu 18.04;
2) remove nano, vim-runtime (full version);
3) install vim-tiny;
4) git a git-repo and do some changes, then press 'git commit -a';
5) vim-tiny will always report many errors as follows:


Error detected while processing /usr/share/vim/vim80/debian.vim:
line   29:
E319: Sorry, the command is not available in this version: function! 
MapExists(name, modes)
line   30:
E319: Sorry, the command is not available in this version:   for mode in 
split(a:modes, '\zs')
line   34:
E319: Sorry, the command is not available in this version:   endfor
line   35:
E319: Sorry, the command is not available in this version:   return 0
line   36:
E319: Sorry, the command is not available in this version: endfunction
Press ENTER or type command to continue

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: vim-tiny 2:8.0.1401-1ubuntu3
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: MATE
Date: Wed Mar  7 23:21:55 2018
SourcePackage: vim
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.vim.vimrc.tiny: 2018-03-07T23:21:15.792000

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

Title:
  vim-tiny doesn't work well with git commit editing comments

Status in vim package in Ubuntu:
  New

Bug description:
  1) Ubuntu 18.04;
  2) remove nano, vim-runtime (full version);
  3) install vim-tiny;
  4) git a git-repo and do some changes, then press 'git commit -a';
  5) vim-tiny will always report many errors as follows:

  
  Error detected while processing /usr/share/vim/vim80/debian.vim:
  line   29:
  E319: Sorry, the command is not available in this version: function! 
MapExists(name, modes)
  line   30:
  E319: Sorry, the command is not available in this version:   for mode in 
split(a:modes, '\zs')
  line   34:
  E319: Sorry, the command is not available in this version:   endfor
  line   35:
  E319: Sorry, the command is not available in this version:   return 0
  line   36:
  E319: Sorry, the command is not available in this version: endfunction
  Press ENTER or type command to continue

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: vim-tiny 2:8.0.1401-1ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Wed Mar  7 23:21:55 2018
  SourcePackage: vim
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.vim.vimrc.tiny: 2018-03-07T23:21:15.792000

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1754068/+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 1644323] Re: Installing unity8-session-snap adversely effects unity7

2018-03-07 Thread Will Cooke

** Changed in: canonical-devices-system-image
 Assignee: Will Cooke (willcooke) => (unassigned)

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

Title:
  Installing unity8-session-snap adversely effects unity7

Status in Canonical System Image:
  Confirmed
Status in dbus package in Ubuntu:
  Fix Released
Status in unity-gtk-module package in Ubuntu:
  Fix Released
Status in dbus source package in Xenial:
  Confirmed
Status in unity-gtk-module source package in Xenial:
  Fix Committed

Bug description:
  [ Description ]

  In Xenial, when dbus-user-session is installed, dbus' upstart job
  still starts a new bus. Things get confused about which bus to talk
  to.

  [ Fix ]

  Already fixed in Yakkety. Cherry-pick the upstart job. On top of
  Yakkety's version, call `dbus-update-activation-environment --verbose
  --systemd GTK_MODULES', because Xenial does not have the change in
  upstart to automatically publish to the systemd activation
  environment.

  /etc/X11/Xsession.d/95dbus_update-activation-env is called too early -
  before unity-gtk-module.conf is started - so dbus activated services
  miss the GTK_MODULES environment variable. Update unity-gtk-
  module.conf to set it in the dbus activation environment.

  [ QA ]

  Install dbus-user-session, press print screen. It should be delayed if
  you are experiencing this bug, and not delayed otherwise.

  Remove dbus-user-session, make sure the session still works properly -
  the global menu works, everything launches properly, etc.

  Test that gnome-terminal has global menus in both situations.

  [ Regression potential ]

  This change alters the way that the session bus is launched, even if
  you aren't using dbus-user-session. Even though this same change is
  deployed in ≥ yakkety, be aware of this. In yakkety we have installed
  dbus-user-session by default, so the case where you don't have it
  isn't as well tested. I would suggest focusing some testing on the non
  dbus-user-session case.

  [ Original report ]

  After installing the deb (and then the snap), certain things in the
  unity7 session take a very long time (30 to 60 secs), such as
  launching chromium and ctrl-alt-t for a new terminal session.

  Removing both the deb and the snap followed by a reboot does not fix
  the symptoms.

  Xenial amd64 laptop

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1644323/+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 1647148] Re: Implement CUPS server snapd interface

2018-03-07 Thread Will Cooke

** Changed in: canonical-devices-system-image
   Status: In Progress => Fix Released

** Changed in: cups (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Implement CUPS server snapd interface

Status in Canonical System Image:
  Fix Released
Status in cups package in Ubuntu:
  Fix Released

Bug description:
  The CUPS server is an helpful feature, needed if you want to get
  convergence. Thanks for all your work, see you.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1647148/+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 1754052] [NEW] Dell Latitude 7480 press shift keys triggers random mouseclick when `Tap to click` enabled on touchpad.

2018-03-07 Thread Peter Karlsson

Public bug reported:

In Ubuntu 16.04.3 and 17.10.1 holding down either shift key on a Dell
Latitude 7480 causes random mouse clicks to occur without being nowhere
near the touchpad with palms. No external mouse/keyboard connected.
Disabling `Tap to click` in `Mouse & Touchpad` settings makes the
problem go away. The problem is not present in 14.04.5, whether
installed or live CD.

How to reproduce:

1. On a Dell Latitude 7480 live boot (or install) one of the following images:
- ubuntu-16.04.3-desktop-amd64.iso
- ubuntu-17.10.1-desktop-amd64.iso

2. Open `Mouse & Touchpad` and make sure `Tap to click` is enabled.
3. Click `Test Your Settings` and make sure window has focus.
4. Hold down either shift key and after a few seconds single/double clicks 
start registering.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
Uname: Linux 4.10.0-28-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CasperVersion: 1.376.2
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Wed Mar  7 13:00:21 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:07a0]
LiveMediaBuild: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
MachineType: Dell Inc. Latitude 7480
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/username.seed boot=casper quiet splash ---
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/30/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.8.2
dmi.board.name: 00F6D3
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.2:bd01/30/2018:svnDellInc.:pnLatitude7480:pvr:rvnDellInc.:rn00F6D3:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.name: Latitude 7480
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial

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

Title:
  Dell Latitude 7480 press shift keys triggers random mouseclick when
  `Tap to click` enabled on touchpad.

Status in xorg package in Ubuntu:
  New

Bug description:
  In Ubuntu 16.04.3 and 17.10.1 holding down either shift key on a Dell
  Latitude 7480 causes random mouse clicks to occur without being
  nowhere near the touchpad with palms. No external mouse/keyboard
  connected. Disabling `Tap to click` in `Mouse & Touchpad` settings
  makes the problem go away. The problem is not present in 14.04.5,
  whether installed or live CD.

  How to reproduce:

  1. On a Dell Latitude 7480 live boot (or install) one of the following images:
  - ubuntu-16.04.3-desktop-amd64.iso
  - ubuntu-17.10.1-desktop-amd64.iso

  2. Open `Mouse & Touchpad` and make sure `Tap to click` is enabled.
  3. Click `Test Your Settings` and make sure window has focus.
  4. Hold down either shift key and after a few seconds single/double clicks 
start registering.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
  Uname: Linux 4.10.0-28-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CasperVersion: 1.376.2
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed Mar  7 13:00:21 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too

[Touch-packages] [Bug 1638842] Re: network-manager does not manage ethernet and bluetooth interfaces when Ubuntu 16.10 is installed using chroot/netboot method

2018-03-07 Thread RamOn RabasO Meca

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

Ubuntu 17.10 here, final solution for me was #36.

Not enough with a blank file in /etc/NetworkManager/conf.d/10-globally-
managed-devices.conf and not solved modifying directly on /usr/lib/. I
had to cp the file from /usr/lib to /etc/ and modify "unmanaged-devices"
to none there, as Silje said.

Thanks!

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

Title:
  network-manager does not manage ethernet and bluetooth interfaces when
  Ubuntu 16.10 is installed using chroot/netboot method

Status in network-manager package in Ubuntu:
  Won't Fix

Bug description:
  Hello,

  I installed Ubuntu 16.10 using a chroot. I use network-manager to
  manage connections. My system is up-to-date (so I use network-manager
  1.2.4-0ubuntu1).

  Wifi works perfectly but I cannot connect to wired networks and using
  my phone's Bluetooth connection. Corresponding devices are said to be
  unmanaged by network-manager. nmcli dev outputs:

  DEVICETYPE  STATE CONNECTION 
  enp1s0ethernet  unmanaged -- 
  wlp2s0wifi  disconnected  --
  6C:9B:02:2C:EE:2C btunmanaged -- 
  hfp/org/bluez/hci0/dev_6C_9B_02_2C_EE_2C  gsm   unmanaged -- 
  loloopback  unmanaged -- 

  The following command has no effect:
  sudo nmcli dev set enp1s0 managed yes

  I can connect to a wired connection by doing:
  ifconfig enp1s0 up
  dhclient enp1s0

  There is nothing in the file /etc/network/interfaces.

  Everything works perfectly if I downgrade network-manager to this
  version: network-manager_1.2.2-0ubuntu0.16.04.3_amd64.deb
  (http://packages.ubuntu.com/xenial-updates/amd64/network-
  manager/download). I had to install libreadline6 and downgrade nplan
  to meet dependencies.

  I don't know what to join to this bug report so please ask in case
  anything is needed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1638842/+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 1754040] [NEW] Xorg freeze

2018-03-07 Thread Kirill Shustov

Public bug reported:

Freezes during work. Usually when I am starting to compile somethind
with high load.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
Uname: Linux 4.13.0-36-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Wed Mar  7 16:03:36 2018
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
DkmsStatus:
 acpi-call, 1.1.0, 4.13.0-32-generic, x86_64: installed
 acpi-call, 1.1.0, 4.13.0-36-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA 
controller])
   Subsystem: Lenovo HD Graphics 530 [17aa:5050]
   Subsystem: Lenovo GM108M [GeForce 940MX] [17aa:5050]
MachineType: LENOVO 20FW003PMS
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic 
root=UUID=66a1f8b5-dc99-4976-b72b-a89fd7190ebd ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/16/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: R07ET82W (2.22 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20FW003PMS
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrR07ET82W(2.22):bd01/16/2018:svnLENOVO:pn20FW003PMS:pvrThinkPadT460p:rvnLENOVO:rn20FW003PMS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T460p
dmi.product.name: 20FW003PMS
dmi.product.version: ThinkPad T460p
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.83-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~17.10.1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~17.10.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug artful 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/1754040

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  Freezes during work. Usually when I am starting to compile somethind
  with high load.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Wed Mar  7 16:03:36 2018
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  DkmsStatus:
   acpi-call, 1.1.0, 4.13.0-32-generic, x86_64: installed
   acpi-call, 1.1.0, 4.13.0-36-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 530 [17aa:5050]
 Subsystem: Lenovo GM108M [GeForce 940MX] [17aa:5050]
  MachineType: LENOVO 20FW003PMS
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic 
root=UUID=66a1f8b5-dc99-4976-b72b-a89fd7190ebd ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/16/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R07ET82W (2.22 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FW003PMS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR07ET82W(2.22):bd01/16/2018:svnLENOVO:pn20FW003PMS:pvrThinkPadT460p:rvnLENOVO:rn20FW003PMS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460p
  dmi.product.name: 20FW003PMS
  dmi.product.version: ThinkPad T460p
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~17.10.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~17.10.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1

[Touch-packages] [Bug 1744769] Re: package udev 229-4ubuntu21 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1

2018-03-07 Thread Launchpad Bug Tracker

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

** Changed in: systemd (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/1744769

Title:
  package udev 229-4ubuntu21 failed to install/upgrade: le sous-
  processus script post-installation installé a retourné une erreur de
  sortie d'état 1

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  L'exécution a été arrêtée car il y avait trop d'erreurs.
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: udev 229-4ubuntu21
  ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67
  Uname: Linux 4.4.0-81-generic x86_64
  NonfreeKernelModules: vboxpci vboxnetadp vboxnetflt vboxdrv
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CustomUdevRuleFiles: 10-Huawei-FlashCard.rules
  Date: Mon Jan 22 12:01:03 2018
  ErrorMessage: le sous-processus script post-installation installé a retourné 
une erreur de sortie d'état 1
  InstallationDate: Installed on 2016-08-21 (519 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 138a:003f Validity Sensors, Inc. VFS495 Fingerprint 
Reader
   Bus 001 Device 003: ID 04f2:b51c Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ProBook 450 G3
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-81-generic 
root=UUID=93c11cbd-e06f-403f-b85c-65718bf5e1fe ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: systemd
  Title: package udev 229-4ubuntu21 failed to install/upgrade: le 
sous-processus script post-installation installé a retourné une erreur de 
sortie d'état 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/18/2015
  dmi.bios.vendor: HP
  dmi.bios.version: N78 Ver. 01.06
  dmi.board.name: 8101
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 16.20
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrN78Ver.01.06:bd12/18/2015:svnHP:pnHPProBook450G3:pvr:rvnHP:rn8101:rvrKBCVersion16.20:cvnHP:ct10:cvr:
  dmi.product.name: HP ProBook 450 G3
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1744769/+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 488720] Re: Suspend/resume with nvidia driver fails

2018-03-07 Thread Mark Yisri

Hi, I know this is an old bug, but I'm experiencing this problem on the
latest 4.13 kernel. I didn't have the issue on an older 4.10 kernel.

What I have found is that if I switch with Ctrl+Alt+F1, then suspend,
then resume and switch back to X, it works. If I just suspend I'm left
with a black screen.

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

Title:
  Suspend/resume with nvidia driver fails

Status in Linux:
  Fix Released
Status in Mactel Support:
  Invalid
Status in pm-utils:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in pm-utils package in Ubuntu:
  Fix Released
Status in linux source package in Lucid:
  Invalid
Status in pm-utils source package in Lucid:
  Fix Released

Bug description:
  Linux Kernel 2.6.32-5 completely fails to resume in my Macbook 5.1
  I am reporting this bug, because with previous version of this kernel 
(2.6.32-*), resume was long and sometimes machine went back to suspend but it 
always succed in resuming.
  Now, it is impossible to resume because the screen stays black and I am 
oblige to force the shutdown with the power button
  I am on:
  Ubuntu lucid (development branch)
  10.04

  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  demoneivo   1968 F pulseaudio
  CRDA: Error: [Errno 2] Nessun file o directory
  Card0.Amixer.info:
   Card hw:0 'NVidia'/'HDA NVidia at 0xd338 irq 16'
 Mixer name : 'Realtek ALC889A'
 Components : 'HDA:10ec0885,106b3f00,00100103'
 Controls  : 36
 Simple ctrls  : 20
  Date: Thu Nov 26 12:50:26 2009
  DistroRelease: Ubuntu 10.04
  HibernationDevice: RESUME=UUID=cc355bac-f00f-457c-99b0-4ddbb235f90e
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
  MachineType: Apple Inc. MacBook5,1
  NonfreeKernelModules: wl nvidia
  Package: linux-image-2.6.32-5-generic 2.6.32-5.6
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-generic 
root=UUID=2a913905-8671-4792-b1a6-c335d9cb798d ro quiet splash
  ProcEnviron:
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.32-5.6-generic
  Regression: Yes
  RelatedPackageVersions: linux-firmware 1.25
  Reproducible: Yes
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Tags:  regression-potential
  TestedUpstream: Yes
  Uname: Linux 2.6.32-5-generic x86_64
  dmi.bios.date: 10/29/08
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MB51.88Z.0073.B06.0810291326
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-F42D89C8
  dmi.board.vendor: Apple Inc.
  dmi.board.version: Proto
  dmi.chassis.asset.tag: Asset Tag#
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F42D89C8
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMB51.88Z.0073.B06.0810291326:bd10/29/08:svnAppleInc.:pnMacBook5,1:pvr1.0:rvnAppleInc.:rnMac-F42D89C8:rvrProto:cvnAppleInc.:ct10:cvrMac-F42D89C8:
  dmi.product.name: MacBook5,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/488720/+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 1754027] Re: package python-dbus 1.2.0-3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

2018-03-07 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package python-dbus 1.2.0-3 failed to install/upgrade: package is in a
  very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in dbus-python package in Ubuntu:
  New

Bug description:
  message d'erreur à chaque mise à jour ubuntu

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: python-dbus 1.2.0-3
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Wed Mar  7 01:39:04 2018
  DuplicateSignature:
   package:python-dbus:1.2.0-3
   Setting up python (2.7.12-1~16.04) ...
   dpkg: error processing package python-dbus (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-05-19 (291 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.25
  SourcePackage: dbus-python
  Title: package python-dbus 1.2.0-3 failed to install/upgrade: package is in a 
very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus-python/+bug/1754027/+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 1754027] [NEW] package python-dbus 1.2.0-3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

2018-03-07 Thread Guillaume Vignal

Public bug reported:

message d'erreur à chaque mise à jour ubuntu

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: python-dbus 1.2.0-3
ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
Date: Wed Mar  7 01:39:04 2018
DuplicateSignature:
 package:python-dbus:1.2.0-3
 Setting up python (2.7.12-1~16.04) ...
 dpkg: error processing package python-dbus (--configure):
  package is in a very bad inconsistent state; you should
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2017-05-19 (291 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.3
 apt  1.2.25
SourcePackage: dbus-python
Title: package python-dbus 1.2.0-3 failed to install/upgrade: package is in a 
very bad inconsistent state; you should  reinstall it before attempting 
configuration
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: dbus-python (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

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

Title:
  package python-dbus 1.2.0-3 failed to install/upgrade: package is in a
  very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in dbus-python package in Ubuntu:
  New

Bug description:
  message d'erreur à chaque mise à jour ubuntu

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: python-dbus 1.2.0-3
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Wed Mar  7 01:39:04 2018
  DuplicateSignature:
   package:python-dbus:1.2.0-3
   Setting up python (2.7.12-1~16.04) ...
   dpkg: error processing package python-dbus (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-05-19 (291 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.25
  SourcePackage: dbus-python
  Title: package python-dbus 1.2.0-3 failed to install/upgrade: package is in a 
very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus-python/+bug/1754027/+subscriptions

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

[Touch-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display

2018-03-07 Thread Francois Thirioux

Quadro M1000M : works now without any tweak.

Nonetheless, if you mean "*full* support", laptop users like me will
argue the lack of a GPU switching ability and the removing of the
Wayland session.

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

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Incomplete

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

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

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

[Touch-packages] [Bug 1754009] Re: multi-arch support needed

2018-03-07 Thread Timo Aaltonen

** Description changed:

  libcapnp-0.6.1 should be marked M-A: same so that installing
- libegl1:i386/amd64 wouldn't remove packages.
+ libegl1:i386/amd64 would be possible.

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

Title:
  multi-arch support needed

Status in capnproto package in Ubuntu:
  New

Bug description:
  libcapnp-0.6.1 should be marked M-A: same so that installing
  libegl1:i386/amd64 would be possible.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/capnproto/+bug/1754009/+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 1754009] [NEW] multi-arch support needed

2018-03-07 Thread Timo Aaltonen

Public bug reported:

libcapnp-0.6.1 should be marked M-A: same so that installing
libegl1:i386/amd64 wouldn't remove packages.

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

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

Title:
  multi-arch support needed

Status in capnproto package in Ubuntu:
  New

Bug description:
  libcapnp-0.6.1 should be marked M-A: same so that installing
  libegl1:i386/amd64 wouldn't remove packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/capnproto/+bug/1754009/+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 1584321] Re: ssh: man and usage still mentioning ssh protocol 1

2018-03-07 Thread Launchpad Bug Tracker

This bug was fixed in the package openssh - 1:7.6p1-4

---
openssh (1:7.6p1-4) unstable; urgency=medium

  * Move VCS to salsa.debian.org.
  * Add a preseeding-only openssh-server/password-authentication debconf
template that can be used to disable password authentication (closes:
#878945).

 -- Colin Watson   Sat, 10 Feb 2018 02:31:46 +

** Changed in: openssh (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  ssh: man and usage still mentioning ssh protocol 1

Status in openssh package in Ubuntu:
  Fix Released

Bug description:
  openssh (1:7.1p1-1) dropped legacy SSH version 1 protocol (as pointed
  e.g: https://wiki.ubuntu.com/XenialXerus/ReleaseNotes )

  But 'usage' still mentions it:
   usage: ssh [-1246AaCfGgKkMNnqsTtVvXxYy] 

  And 'man ssh':
   -1  Forces ssh to try protocol version 1 only.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1584321/+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 1752882] Re: Systemd sysv install fails with update-rc.d: error: unable to read /etc/init.d/enable

2018-03-07 Thread Launchpad Bug Tracker

This bug was fixed in the package systemd - 237-3ubuntu4

---
systemd (237-3ubuntu4) bionic; urgency=medium

  * systemd-sysv-install: fix name initialisation.
Only initialise NAME, after --root optional argument has been parsed, 
otherwise
NAME is initialized to e.g. `enable', instead of to the `unit-name`, 
resulting
in failures. (LP: #1752882)

 -- Dimitri John Ledkov   Mon, 05 Mar 2018 09:57:58
+0100

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

Title:
  Systemd sysv install fails with update-rc.d: error: unable to read
  /etc/init.d/enable

Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  The bionic builds of cloud images for one of our partners fails when
  installing/enabling NTP in the image during livecdrootfs build:

  + chroot mountpoint_gce systemctl --root / enable ntp.service
  Synchronizing state of ntp.service with SysV service script with 
/lib/systemd/systemd-sysv-install.
  Executing: /lib/systemd/systemd-sysv-install --root=/ enable ntp
  update-rc.d: error: unable to read /etc/init.d/enable

  On Xnox's request I am filing a bug here and assigning to him.

  Please let me know if you need further information.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1752882/+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 1753731] Re: Playing media file over gvfs ceased working

2018-03-07 Thread Bug Watch Updater

** Changed in: gstreamer1.0
   Status: Unknown => Confirmed

** Changed in: gstreamer1.0
   Importance: Unknown => Critical

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

Title:
  Playing media file over gvfs ceased working

Status in Gstreamer1.0:
  Confirmed
Status in gstreamer1.0 package in Ubuntu:
  Triaged

Bug description:
  I am trying to play a media file over gvfs with totem which stopped working.
  Also showing the media information of such a remote file in nautilus doesn't 
work anymore.

  My guess was this is a regression of 1.13.1, but using gst-play-1.0
  directly surprisingly works.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gstreamer1.0/+bug/1753731/+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 1753731] Re: Playing media file over gvfs ceased working

2018-03-07 Thread Sebastien Bacher

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

** Changed in: gstreamer1.0 (Ubuntu)
   Status: New => Triaged

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

** Also affects: gstreamer1.0 via
   https://bugzilla.gnome.org/show_bug.cgi?id=794149
   Importance: Unknown
   Status: Unknown

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

Title:
  Playing media file over gvfs ceased working

Status in Gstreamer1.0:
  Unknown
Status in gstreamer1.0 package in Ubuntu:
  Triaged

Bug description:
  I am trying to play a media file over gvfs with totem which stopped working.
  Also showing the media information of such a remote file in nautilus doesn't 
work anymore.

  My guess was this is a regression of 1.13.1, but using gst-play-1.0
  directly surprisingly works.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gstreamer1.0/+bug/1753731/+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 1735929] Re: security problems with incorrect permissions for ubuntu 17.10

2018-03-07 Thread Marc Deslauriers

Any further progress on these issues?

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

Title:
  security problems with incorrect permissions for ubuntu 17.10

Status in dconf:
  Confirmed
Status in gnome-session:
  Confirmed
Status in d-conf package in Ubuntu:
  Triaged
Status in dconf package in Ubuntu:
  Triaged
Status in gnome-session package in Ubuntu:
  Triaged
Status in session-migration package in Ubuntu:
  Fix Released

Bug description:
  The release of Ubuntu you are using (lsb_release -rd):
  Description:  Ubuntu 17.10
  Release:  17.10

  This is a fresh installation of Ubuntu 17.10 from the mini.iso.
  I select only default options + [Ubuntu Desktop] installation.

  What you expected to happen:
  My home folder contains the following folders with correct and safe 
permissions after the first login:
  drwx-- 11 user user 4096 Dec  2 17:40 .config
  drwx--  3 user user 4096 Dec  2 17:39 .local

  What happened instead:
  I received these folders after the first login:
  drwxr-xr-x 11 user user 4096 Dec  2 17:40 .config
  drwxr-xr-x  3 user user 4096 Dec  2 17:39 .local
  It is not safe. Any user can access to my .config folders and read for 
example my mail databases

  I'm trying to create a new user...:
  sudo useradd -m user2
  sudo passwd user2
  ... and login then.
  It has the same problem:
  drwxr-xr-x 10 user2 user2 4096 Dec  2 19:44 .config
  drwxr-xr-x  3 user2 user2 4096 Dec  2 19:44 .local

To manage notifications about this bug go to:
https://bugs.launchpad.net/dconf/+bug/1735929/+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 1164016] Re: restore type-ahead find

2018-03-07 Thread Henrik Holmboe

The old behaviour was one of the power features of Nautilus for a person
that uses keyboard navigation. The new behaviour is dramatically
different and frankly doesn't work as well for many use cases.

Lets say I want to quickly navigate to
~/code/myproject/module/__init__.py.

1. I switch to Nautilus which shows my home folder
   A. With the old behaviour: c ENTER m ENTER m ENTER __i ENTER
   B. With the new behaviour: __init__.py, and it shows me tons of __init__.py 
located in my home folder and all subdirectories
2. Trying to use the new behaviour and still achieve my goal I try this:
   i) module/__init__.py, no hit
   ii) module __init__.py, no hit

So, currently I see no way of navigating to the intended file without
alot of hassle or reaching for the mouse. A big regression for me.

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

Title:
  restore type-ahead find

Status in Nautilus:
  Expired
Status in nautilus package in Ubuntu:
  Fix Released
Status in ubuntu-settings package in Ubuntu:
  Fix Released

Bug description:
  GNOME removed type-ahead find in Nautilus 3.6, not without
  controversy:

  https://mail.gnome.org/archives/nautilus-
  list/2012-August/msg2.html

  Now when you type in a Nautilus window, Nautilus immediately performs
  a search in the current directory and all its subdirectories.  I
  personally find this annoying.  If I want to search, I'll click the
  search icon.  Often I'm looking at a long directory listing and simply
  want to jump to a certain point in it, and type-ahead find works great
  for that.

  Would Ubuntu consider patching type-ahead find back in?

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/1164016/+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 1753954] Re: Intel Whiskey Lake (WHL) support

2018-03-07 Thread Timo Aaltonen

bionic kernel got fixed already in
https://bugs.launchpad.net/intel/+bug/1742561

** Changed in: linux-oem (Ubuntu Bionic)
   Status: New => Fix Released

** Summary changed:

- Intel Whiskey Lake (WHL) support
+ Intel Whiskey Lake (WHL) graphics support

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

Title:
  Intel Whiskey Lake (WHL) graphics support

Status in libdrm package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  New
Status in xorg-server-hwe-16.04 package in Ubuntu:
  Invalid
Status in libdrm source package in Xenial:
  New
Status in linux-oem source package in Xenial:
  New
Status in mesa source package in Xenial:
  New
Status in xorg-server source package in Xenial:
  Invalid
Status in xorg-server-hwe-16.04 source package in Xenial:
  New
Status in libdrm source package in Bionic:
  Fix Released
Status in linux-oem source package in Bionic:
  Fix Released
Status in mesa source package in Bionic:
  Fix Released
Status in xorg-server source package in Bionic:
  New
Status in xorg-server-hwe-16.04 source package in Bionic:
  Invalid

Bug description:
  [Impact]
  WHL is basically CFL-U with new PCI-ID's that are needed in the kernel, 
libdrm, mesa and xserver.

  [Test Case]

  Test the installation on a WHL machine, the graphical session should
  have full acceleration after these updates.

  [Regression Potential]

  None, just adds PCI-ID's to existing drivers.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1753954/+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 1753966] [NEW] apparmor interfers with saving of PDF from evince

2018-03-07 Thread P

Public bug reported:

While trying to save an open PDF from evince, I clicked on the "create
folder" button in the save dialog. Apparmor prevented directory creation
in the respective directory. Saving within my "home" directory works.

I consider this a bug. In my case, all user data resides in a separate
data partition. With the current apparmor profiles, saving to this
partition is hindered.

Syslog contains:

Mar  7 10:29:33 xxx kernel: [ 4569.159240] audit: type=1400
audit(1520414973.202:39): apparmor="DENIED" operation="mkdir"
profile="/usr/bin/evince" name="x" pid=5393 comm="evince"
requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000

More generally, this seems to apply to a whole set of apparmor profiles
that were updated or added recently...

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: apparmor-profiles (not installed)
ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
Uname: Linux 4.13.0-36-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CurrentDesktop: KDE
Date: Wed Mar  7 10:32:37 2018
InstallationDate: Installed on 2017-12-01 (95 days ago)
InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1)
ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic 
root=UUID=5c73304c-cd10-4645-99c9-2cf07aa48894 ro nosplash
SourcePackage: apparmor
Syslog:
 
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug artful

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

Title:
  apparmor interfers with saving of PDF from evince

Status in apparmor package in Ubuntu:
  New

Bug description:
  While trying to save an open PDF from evince, I clicked on the "create
  folder" button in the save dialog. Apparmor prevented directory
  creation in the respective directory. Saving within my "home"
  directory works.

  I consider this a bug. In my case, all user data resides in a separate
  data partition. With the current apparmor profiles, saving to this
  partition is hindered.

  Syslog contains:

  Mar  7 10:29:33 xxx kernel: [ 4569.159240] audit: type=1400
  audit(1520414973.202:39): apparmor="DENIED" operation="mkdir"
  profile="/usr/bin/evince" name="x" pid=5393 comm="evince"
  requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000

  More generally, this seems to apply to a whole set of apparmor
  profiles that were updated or added recently...

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: apparmor-profiles (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Mar  7 10:32:37 2018
  InstallationDate: Installed on 2017-12-01 (95 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic 
root=UUID=5c73304c-cd10-4645-99c9-2cf07aa48894 ro nosplash
  SourcePackage: apparmor
  Syslog:
   
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1753966/+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 1746807] Re: 18.04 daily installer fails missing kernel

2018-03-07 Thread Adam Conrad

** Also affects: apt (Ubuntu Bionic)
   Importance: Critical
 Assignee: Julian Andres Klode (juliank)
   Status: 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/1746807

Title:
  18.04 daily installer fails missing kernel

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Bionic:
  Fix Released

Bug description:
  "No installable kernel was found in the defined APT sources.

  You may try to continue without a kernel, and manually install your own 
kernel later.
  This is only recommended for experts, otherwise you will likely end up with a 
machine
  that doesn't boot.

  Continue without installing a kernel."

  Lubuntu Daily 18.04 dated 2018-February 1.

  note: yesterdays (Jan 31) install works fine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1746807/+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 1753954] Re: Intel Whiskey Lake (WHL) support

2018-03-07 Thread Timo Aaltonen

libdrm 2.4.90 in bionic has them

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

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

** Also affects: xorg-server (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

** Also affects: mesa (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: libdrm (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: xorg-server (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

** Changed in: libdrm (Ubuntu Bionic)
   Status: New => Fix Released

** Also affects: xorg-server-hwe-16.04 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: xorg-server-hwe-16.04 (Ubuntu Bionic)
   Status: New => Invalid

** Changed in: xorg-server (Ubuntu Xenial)
   Status: New => Invalid

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

Title:
  Intel Whiskey Lake (WHL) support

Status in libdrm package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  New
Status in xorg-server-hwe-16.04 package in Ubuntu:
  Invalid
Status in libdrm source package in Xenial:
  New
Status in linux-oem source package in Xenial:
  New
Status in mesa source package in Xenial:
  New
Status in xorg-server source package in Xenial:
  Invalid
Status in xorg-server-hwe-16.04 source package in Xenial:
  New
Status in libdrm source package in Bionic:
  Fix Released
Status in linux-oem source package in Bionic:
  New
Status in mesa source package in Bionic:
  Fix Released
Status in xorg-server source package in Bionic:
  New
Status in xorg-server-hwe-16.04 source package in Bionic:
  Invalid

Bug description:
  [Impact]
  WHL is basically CFL-U with new PCI-ID's that are needed in the kernel, 
libdrm, mesa and xserver.

  [Test Case]

  Test the installation on a WHL machine, the graphical session should
  have full acceleration after these updates.

  [Regression Potential]

  None, just adds PCI-ID's to existing drivers.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1753954/+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 1753954] Re: Intel Whiskey Lake (WHL) support

2018-03-07 Thread Timo Aaltonen

mesa 18.0.0-rc4 in bionic has them

** Changed in: mesa (Ubuntu Bionic)
   Status: New => Fix Released

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

Title:
  Intel Whiskey Lake (WHL) support

Status in libdrm package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  New
Status in xorg-server-hwe-16.04 package in Ubuntu:
  Invalid
Status in libdrm source package in Xenial:
  New
Status in linux-oem source package in Xenial:
  New
Status in mesa source package in Xenial:
  New
Status in xorg-server source package in Xenial:
  Invalid
Status in xorg-server-hwe-16.04 source package in Xenial:
  New
Status in libdrm source package in Bionic:
  Fix Released
Status in linux-oem source package in Bionic:
  New
Status in mesa source package in Bionic:
  Fix Released
Status in xorg-server source package in Bionic:
  New
Status in xorg-server-hwe-16.04 source package in Bionic:
  Invalid

Bug description:
  [Impact]
  WHL is basically CFL-U with new PCI-ID's that are needed in the kernel, 
libdrm, mesa and xserver.

  [Test Case]

  Test the installation on a WHL machine, the graphical session should
  have full acceleration after these updates.

  [Regression Potential]

  None, just adds PCI-ID's to existing drivers.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1753954/+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 1753954] [NEW] Intel Whiskey Lake (WHL) support

2018-03-07 Thread Timo Aaltonen

Public bug reported:

[Impact]
WHL is basically CFL-U with new PCI-ID's that are needed in the kernel, libdrm, 
mesa and xserver.

[Test Case]

Test the installation on a WHL machine, the graphical session should
have full acceleration after these updates.

[Regression Potential]

None, just adds PCI-ID's to existing drivers.

** Affects: libdrm (Ubuntu)
 Importance: Undecided
 Status: Fix Released

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

** Affects: mesa (Ubuntu)
 Importance: Undecided
 Status: Fix Released

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

** Affects: xorg-server-hwe-16.04 (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: libdrm (Ubuntu Xenial)
 Importance: Undecided
 Status: New

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

** Affects: mesa (Ubuntu Xenial)
 Importance: Undecided
 Status: New

** Affects: xorg-server (Ubuntu Xenial)
 Importance: Undecided
 Status: Invalid

** Affects: xorg-server-hwe-16.04 (Ubuntu Xenial)
 Importance: Undecided
 Status: New

** Affects: libdrm (Ubuntu Bionic)
 Importance: Undecided
 Status: Fix Released

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

** Affects: mesa (Ubuntu Bionic)
 Importance: Undecided
 Status: Fix Released

** Affects: xorg-server (Ubuntu Bionic)
 Importance: Undecided
 Status: New

** Affects: xorg-server-hwe-16.04 (Ubuntu Bionic)
 Importance: Undecided
 Status: Invalid

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

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

** Also affects: xorg-server (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Intel Whiskey Lake (WHL) support

Status in libdrm package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  New
Status in xorg-server-hwe-16.04 package in Ubuntu:
  Invalid
Status in libdrm source package in Xenial:
  New
Status in linux-oem source package in Xenial:
  New
Status in mesa source package in Xenial:
  New
Status in xorg-server source package in Xenial:
  Invalid
Status in xorg-server-hwe-16.04 source package in Xenial:
  New
Status in libdrm source package in Bionic:
  Fix Released
Status in linux-oem source package in Bionic:
  New
Status in mesa source package in Bionic:
  Fix Released
Status in xorg-server source package in Bionic:
  New
Status in xorg-server-hwe-16.04 source package in Bionic:
  Invalid

Bug description:
  [Impact]
  WHL is basically CFL-U with new PCI-ID's that are needed in the kernel, 
libdrm, mesa and xserver.

  [Test Case]

  Test the installation on a WHL machine, the graphical session should
  have full acceleration after these updates.

  [Regression Potential]

  None, just adds PCI-ID's to existing drivers.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1753954/+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 1753946] Re: verbosity for logrotate

2018-03-07 Thread Sergey Ivanov

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

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

Title:
  verbosity for logrotate

Status in logrotate package in Ubuntu:
  Invalid

Bug description:
  User has modified /etc/logrotate.conf file such that it includes another file 
/path/to/own/other_logrotate.conf:
  ...
  include /path/to/own/other_logrotate.conf
  ...

  Now run under root:

  logrotate -v /etc/logrotate.conf

  Expected result:
  verbosity related to other logrotate file should be very same as if we run 
other logrotate directly
  i.e:
  logrotate -v /etc/logrotate.conf should have same output related to 
/path/to/own/other_logrotate.conf
  as if we run directly
  logrotate -v /path/to/own/other_logrotate.conf

  Actual result:
  logrotate -v /etc/logrotate.conf has empty output regarding to 
/path/to/own/other_logrotate.conf

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: logrotate 3.8.7-2ubuntu2.16.04.2
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Mar  7 10:33:11 2018
  InstallationDate: Installed on 2018-01-23 (42 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: logrotate
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.logrotate.conf: 2018-03-07T10:33:03.883000

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1753946/+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 1753509] Re: avahi-daemon adds/installs every printer on network

2018-03-07 Thread Till Kamppeter

** Also affects: cups-filters (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: cups (Ubuntu)

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

Title:
  avahi-daemon adds/installs every printer on network

Status in cups-filters package in Ubuntu:
  New

Bug description:
  When connected to a network, avahi-daemon adds & installs all printer
  on a network without being prompted.  This is not desired behaviour.
  Discovery of the printers is good, but not automatic installation &
  addition.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: avahi-daemon 0.6.32~rc+dfsg-1ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar  5 09:29:05 2018
  InstallationDate: Installed on 2017-09-29 (157 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: avahi
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1753509/+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 1753663] Re: [Mesa 18.0 + nvidia-390] No 3D acceleration, using llvmpipe

2018-03-07 Thread shankao

I have tried every solution in this bug, but still getting LLVMpipe
renderer. Strangely, it only happens in X.org, but picks the correct
Intel in Wayland

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

Title:
  [Mesa 18.0 + nvidia-390] No 3D acceleration, using llvmpipe

Status in libglvnd package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Invalid

Bug description:
  As requested in
  https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1751414, I
  fill a new bug.

  Even after getting the fixed packages in
  https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1751414, I get
  no 3D acceleration. Seems to be some mixup with nvidia drivers.

  $glxinfo
  ...
  Extended renderer info (GLX_MESA_query_renderer):
  Vendor: VMware, Inc. (0x)
  Device: llvmpipe (LLVM 5.0, 256 bits) (0x)
  Version: 18.0.0
  Accelerated: no
  Video memory: 15963MB
  Unified memory: no
  Preferred profile: core (0x1)
  Max core profile version: 3.3
  Max compat profile version: 3.0
  Max GLES1 profile version: 1.1
  Max GLES[23] profile version: 3.0
  ...

  $ vdpauinfo
  display: :1 screen: 0
  Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object 
file: No such file or directory

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  .tmp.unity_support_test.1:

  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,imgpng,snap,mousepoll,commands,imgjpeg,workarounds,wall,imgsvg,resize,place,neg,grid,scale,regex,text,shelf,expo,move,gnomecompat,annotate,session,notification,resizeinfo,ezoom,staticswitcher,bench]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: MATE
  Date: Tue Mar  6 08:00:28 2018
  DistUpgraded: 2018-03-03 08:30:16,182 DEBUG /openCache(), new cache size 86475
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   fwts-efi-runtime-dkms, 18.02.00, 4.15.0-10-generic, x86_64: installed
   ndiswrapper, 1.60, 4.15.0-10-generic, x86_64: installed
   r8168, 8.045.08, 4.15.0-10-generic, x86_64: installed
   tp_smapi, 0.42, 4.15.0-10-generic, x86_64: installed
   virtualbox, 5.2.8, 4.15.0-10-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 08) (prog-if 00 [VGA 
controller])
     Subsystem: Intel Corporation HD Graphics 5500 [8086:1616]
  MachineType: www.51nb.com X62
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-10-generic 
root=UUID=df422beb-6d13-4575-9b30-ad00e25a7d35 ro noquiet nosplash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to bionic on 2018-03-03 (2 days ago)
  dmi.bios.date: 12/10/2016
  dmi.bios.vendor: 51NB
  dmi.bios.version: 5.011
  dmi.board.asset.tag: X62
  dmi.board.name: CRESCENTBAY
  dmi.board.vendor: INTEL Corporation
  dmi.board.version: X62.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvn51NB:bvr5.011:bd12/10/2016:svnwww.51nb.com:pnX62:pvrV10:rvnINTELCorporation:rnCRESCENTBAY:rvrX62.:cvnToBeFilledByO.E.M.:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.family: X62
  dmi.product.name: X62
  dmi.product.version: V10
  dmi.sys.vendor: www.51nb.com
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-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/libglvnd/+bug/1753663/+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 1753946] [NEW] verbosity for logrotate

2018-03-07 Thread Sergey Ivanov

Public bug reported:

User has modified /etc/logrotate.conf file such that it includes another file 
/path/to/own/other_logrotate.conf:
...
include /path/to/own/other_logrotate.conf
...

Now run under root:

logrotate -v /etc/logrotate.conf

Expected result:
verbosity related to other logrotate file should be very same as if we run 
other logrotate directly
i.e:
logrotate -v /etc/logrotate.conf should have same output related to 
/path/to/own/other_logrotate.conf
as if we run directly
logrotate -v /path/to/own/other_logrotate.conf

Actual result:
logrotate -v /etc/logrotate.conf has empty output regarding to 
/path/to/own/other_logrotate.conf

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: logrotate 3.8.7-2ubuntu2.16.04.2
ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Mar  7 10:33:11 2018
InstallationDate: Installed on 2018-01-23 (42 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
SourcePackage: logrotate
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.logrotate.conf: 2018-03-07T10:33:03.883000

** Affects: logrotate (Ubuntu)
 Importance: Undecided
 Status: Invalid


** Tags: amd64 apport-bug xenial

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

Title:
  verbosity for logrotate

Status in logrotate package in Ubuntu:
  Invalid

Bug description:
  User has modified /etc/logrotate.conf file such that it includes another file 
/path/to/own/other_logrotate.conf:
  ...
  include /path/to/own/other_logrotate.conf
  ...

  Now run under root:

  logrotate -v /etc/logrotate.conf

  Expected result:
  verbosity related to other logrotate file should be very same as if we run 
other logrotate directly
  i.e:
  logrotate -v /etc/logrotate.conf should have same output related to 
/path/to/own/other_logrotate.conf
  as if we run directly
  logrotate -v /path/to/own/other_logrotate.conf

  Actual result:
  logrotate -v /etc/logrotate.conf has empty output regarding to 
/path/to/own/other_logrotate.conf

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: logrotate 3.8.7-2ubuntu2.16.04.2
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Mar  7 10:33:11 2018
  InstallationDate: Installed on 2018-01-23 (42 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: logrotate
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.logrotate.conf: 2018-03-07T10:33:03.883000

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1753946/+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 1725921] Re: [regression] Combobox menus have gray text on gray background

2018-03-07 Thread Daniel van Vugt

Added a fix for xenial too.

** Branch linked: lp:~vanvugt/ubuntu-themes/fix-1725921-xenial

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

Title:
  [regression] Combobox menus have gray text on gray background

Status in Ubuntu theme:
  In Progress
Status in ubuntu-themes package in Ubuntu:
  In Progress
Status in ubuntu-themes source package in Bionic:
  In Progress

Bug description:
  See pictures.

  Application: pcbnew
  Version: no-vcs-found-0b1eb56~60~ubuntu17.04.1, release build
  Libraries:
  wxWidgets 3.0.3
  libcurl/7.55.1 OpenSSL/1.0.2g zlib/1.2.11 libidn2/2.0.2 libpsl/0.18.0 
(+libidn2/2.0.2) librtmp/2.3
  Platform: Linux 4.13.0-16-generic x86_64, 64 bit, Little endian, wxGTK
  Build Info:
  wxWidgets: 3.0.2 (wchar_t,wx containers,compatible with 2.8) GTK+ 2.24
  Boost: 1.62.0
  Curl: 7.52.1
  Compiler: GCC 6.3.0 with C++ ABI 1010

  Build settings:
  USE_WX_GRAPHICS_CONTEXT=OFF
  USE_WX_OVERLAY=OFF
  KICAD_SCRIPTING=ON
  KICAD_SCRIPTING_MODULES=ON
  KICAD_SCRIPTING_WXPYTHON=ON
  KICAD_SCRIPTING_ACTION_MENU=ON
  BUILD_GITHUB_PLUGIN=ON
  KICAD_USE_OCE=ON
  KICAD_SPICE=ON

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1725921/+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 1753776] Re: Graphics corruption in login animation to Xorg sessions

2018-03-07 Thread Daniel van Vugt

** Changed in: gnome-shell (Ubuntu)
   Status: Fix Released => Confirmed

** Changed in: mutter (Ubuntu)
   Status: Fix Released => Confirmed

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

** Changed in: xorg-server (Ubuntu)
   Status: Invalid => Confirmed

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

Title:
  Graphics corruption in login animation to Xorg sessions

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Immediately after login (I enter the password and hit enter) the screen 
"crumbles" for few seconds, then all becomes normal and the system works fine. 
I have done apt update+upgrade many times, also with proposed enabled, I have 
also installed a new ISO (now i'm using the Alpha dated 20180305) but the 
problem remains. The problem happens with the x11 session but not with wayland. 
  Also problem does not show with different hardware. 

  corrado@corrado-p7-bb-0305:~$ inxi -Fx
  System:Host: corrado-p7-bb-0305 Kernel: 4.15.0-10-generic x86_64 bits: 64 
gcc: 7.3.0
 Desktop: Gnome 3.27.92 (Gtk 3.22.28-1ubuntu3) Distro: Ubuntu 
Bionic Beaver (development branch)
  Machine:   Device: desktop Mobo: ASRock model: H110M-G/M.2 serial: N/A UEFI: 
American Megatrends v: P1.10 date: 05/11/2017
  CPU:   Dual core Intel Core i3-7100 (-MT-MCP-) arch: Skylake rev.9 cache: 
3072 KB
 flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 15648
 clock speeds: max: 3900 MHz 1: 1018 MHz 2: 3150 MHz 3: 3153 MHz 4: 
3081 MHz
  Graphics:  Card: Intel HD Graphics 630 bus-ID: 00:02.0
 Display Server: x11 (X.Org 1.19.6 ) driver: i915 Resolution: 
1920x1080@60.00hz
 OpenGL: renderer: Mesa DRI Intel HD Graphics 630 (Kaby Lake GT2)
 version: 4.5 Mesa 18.0.0-rc4 Direct Render: Yes
  Audio: Card Intel Sunrise Point-H HD Audio driver: snd_hda_intel bus-ID: 
00:1f.3
 Sound: Advanced Linux Sound Architecture v: k4.15.0-10-generic
  Network:   Card: Intel Ethernet Connection (2) I219-V driver: e1000e v: 
3.2.6-k 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: 1000.2GB (1.3% used)
 ID-1: /dev/sda model: TOSHIBA_DT01ACA1 size: 1000.2GB
  Partition: ID-1: / size: 32G used: 4.3G (15%) fs: ext4 dev: /dev/sda7
 ID-2: swap-1 size: 8.59GB used: 0.00GB (0%) fs: swap dev: /dev/sda2
  RAID:  No RAID devices: /proc/mdstat, md_mod kernel module present
  Sensors:   System Temperatures: cpu: 38.5C mobo: N/A
 Fan Speeds (in rpm): cpu: N/A
  Info:  Processes: 234 Uptime: 11 min Memory: 1144.7/7680.8MB Init: 
systemd runlevel: 5 Gcc sys: N/A
 Client: Shell (bash 4.4.181) inxi: 2.3.56 
  corrado@corrado-p7-bb-0305:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar  6 15:47:50 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: ASRock Incorporation HD Graphics 630 [1849:5912]
  InstallationDate: Installed on 2018-03-05 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180305)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse
   Bus 001 Device 002: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed 
root=UUID=9a36b498-59f5-4a36-81db-3046ff6bdeaa ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/11/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: H110M-G/M.2
  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:

65 matches

Mail list logo