[Touch-packages] [Bug 1811706] Re: eval: en: not found

2019-01-22 Thread CodeExecution
bump

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

Title:
  eval: en: not found

Status in console-setup package in Ubuntu:
  New

Bug description:
  I tried to create a minimal Ubuntu bionic arm64 installation using
  debootstrap that I would use to create a bootable Kubuntu 18.04 image
  for the Pi 3, but debootstrap seems to fail to configure keyboard-
  configuration, and therefore fails to install the Ubuntu base. Looking
  into the debootstrap logs, I get the error "eval: en: not found". I've
  searched Google for solutions but found nothing relevant.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1811706/+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 1812955] Re: g-ir-scanner/Shell-0.1 is crashing with SIGSEGV instead of succeeding

2019-01-22 Thread Daniel van Vugt
Annoyingly, many packages changed today. I think the regression occurred
somewhere in here:

Start-Date: 2019-01-23  10:59:11
Commandline: apt full-upgrade
Requested-By: dan (1000)
Install: libsereal-encoder-perl:amd64 (4.005+ds-1build1, automatic), 
libio-async-perl:amd64 (0.72-1, automatic), libstruct-dumb-perl:amd64 (0.09-1, 
automatic), libasync-mergepoint-perl:amd64 (0.04-2, automatic), 
libfuture-perl:amd64 (0.39-1, automatic), libtest-refcount-perl:amd64 (0.08-3, 
automatic), libsereal-decoder-perl:amd64 (4.005+ds-1build1, automatic), 
libtest-fatal-perl:amd64 (0.014-1, automatic), libsereal-perl:amd64 (4.005-1, 
automatic)
Upgrade: libpolkit-gobject-1-0:amd64 (0.105-22ubuntu2, 0.105-25), 
libisccfg163:amd64 (1:9.11.5+dfsg-1ubuntu1, 1:9.11.5.P1+dfsg-1ubuntu1), 
gir1.2-gtk-3.0:amd64 (3.24.3-1ubuntu1, 3.24.4-1ubuntu1), 
libsasl2-modules-db:amd64 (2.1.27~rc8-1, 2.1.27+dfsg-1), libgcr-base-3-1:amd64 
(3.28.0-4, 3.28.1-1), libgtk-3-common:amd64 (3.24.3-1ubuntu1, 3.24.4-1ubuntu1), 
grub-common:amd64 (2.02+dfsg1-5ubuntu9, 2.02+dfsg1-5ubuntu10), libgtk-3-0:amd64 
(3.24.3-1ubuntu1, 3.24.4-1ubuntu1), python-simplejson:amd64 (3.15.0-1build2, 
3.16.0-1), ubuntu-advantage-tools:amd64 (17, 18), libirs161:amd64 
(1:9.11.5+dfsg-1ubuntu1, 1:9.11.5.P1+dfsg-1ubuntu1), bind9-host:amd64 
(1:9.11.5+dfsg-1ubuntu1, 1:9.11.5.P1+dfsg-1ubuntu1), dnsutils:amd64 
(1:9.11.5+dfsg-1ubuntu1, 1:9.11.5.P1+dfsg-1ubuntu1), gtk-3-examples:amd64 
(3.24.3-1ubuntu1, 3.24.4-1ubuntu1), dnsmasq-base:amd64 (2.80-1, 2.80-1ubuntu1), 
gcr:amd64 (3.28.0-4, 3.28.1-1), libpolkit-agent-1-0:amd64 (0.105-22ubuntu2, 
0.105-25), grub2-common:amd64 (2.02+dfsg1-5ubuntu9, 2.02+dfsg1-5ubuntu10), 
libsasl2-2:amd64 (2.1.27~rc8-1, 2.1.27+dfsg-1), libisc-export1100:amd64 
(1:9.11.5+dfsg-1ubuntu1, 1:9.11.5.P1+dfsg-1ubuntu1), grub-pc:amd64 
(2.02+dfsg1-5ubuntu9, 2.02+dfsg1-5ubuntu10), debianutils:amd64 (4.8.6, 
4.8.6.1), libgcr-ui-3-1:amd64 (3.28.0-4, 3.28.1-1), 
libpolkit-gobject-1-dev:amd64 (0.105-22ubuntu2, 0.105-25), libisc1100:amd64 
(1:9.11.5+dfsg-1ubuntu1, 1:9.11.5.P1+dfsg-1ubuntu1), 
libpolkit-agent-1-dev:amd64 (0.105-22ubuntu2, 0.105-25), 
python3-simplejson:amd64 (3.15.0-1build2, 3.16.0-1), grub-pc-bin:amd64 
(2.02+dfsg1-5ubuntu9, 2.02+dfsg1-5ubuntu10), gir1.2-gck-1:amd64 (3.28.0-4, 
3.28.1-1), grub-efi-amd64-bin:amd64 (2.02+dfsg1-5ubuntu9, 
2.02+dfsg1-5ubuntu10), libgtk-3-bin:amd64 (3.24.3-1ubuntu1, 3.24.4-1ubuntu1), 
python3-distupgrade:amd64 (1:19.04.9, 1:19.04.10), libsasl2-modules:amd64 
(2.1.27~rc8-1, 2.1.27+dfsg-1), libgck-1-dev:amd64 (3.28.0-4, 3.28.1-1), 
ubuntu-release-upgrader-core:amd64 (1:19.04.9, 1:19.04.10), libzvbi0:amd64 
(0.2.35-15, 0.2.35-16), libgtk-3-dev:amd64 (3.24.3-1ubuntu1, 3.24.4-1ubuntu1), 
libhtml-tree-perl:amd64 (5.07-1, 5.07-2), liblwres161:amd64 
(1:9.11.5+dfsg-1ubuntu1, 1:9.11.5.P1+dfsg-1ubuntu1), libgcr-3-dev:amd64 
(3.28.0-4, 3.28.1-1), lintian:amd64 (2.5.122, 2.5.123), gir1.2-gcr-3:amd64 
(3.28.0-4, 3.28.1-1), libgck-1-0:amd64 (3.28.0-4, 3.28.1-1), 
libpolkit-backend-1-0:amd64 (0.105-22ubuntu2, 0.105-25), 
libdns-export1104:amd64 (1:9.11.5+dfsg-1ubuntu1, 1:9.11.5.P1+dfsg-1ubuntu1), 
policykit-1:amd64 (0.105-22ubuntu2, 0.105-25), 
ubuntu-release-upgrader-gtk:amd64 (1:19.04.9, 1:19.04.10), findutils:amd64 
(4.6.0+git+20181018-1, 4.6.0+git+20190105-2), grub-efi-amd64-signed:amd64 
(1.111+2.02+dfsg1-5ubuntu9, 1.112+2.02+dfsg1-5ubuntu10), libisccc161:amd64 
(1:9.11.5+dfsg-1ubuntu1, 1:9.11.5.P1+dfsg-1ubuntu1), 
gtk-update-icon-cache:amd64 (3.24.3-1ubuntu1, 3.24.4-1ubuntu1), 
libbind9-161:amd64 (1:9.11.5+dfsg-1ubuntu1, 1:9.11.5.P1+dfsg-1ubuntu1), 
gir1.2-polkit-1.0:amd64 (0.105-22ubuntu2, 0.105-25), libdns1104:amd64 
(1:9.11.5+dfsg-1ubuntu1, 1:9.11.5.P1+dfsg-1ubuntu1), libzvbi-common:amd64 
(0.2.35-15, 0.2.35-16), python3-chardet:amd64 (3.0.4-2, 3.0.4-3)
End-Date: 2019-01-23  11:00:16

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

Title:
  g-ir-scanner/Shell-0.1 is crashing with SIGSEGV instead of succeeding

Status in gobject-introspection package in Ubuntu:
  New

Bug description:
  g-ir-scanner is crashing with SIGSEGV instead of succeeding. So I
  can't build gnome-shell any more.

  Actually it looks like some kind of temporary sub-command "Shell-0.1"
  of g-ir-scanner that's crashing:

  /usr/bin/g-ir-scanner -pthread -I/usr/include/gobject-introspection-1.0 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
--no-libtool --namespace=Shell --nsversion=0.1 --warn-all --output 
src/Shell-0.1.gir --quiet -I/home/dan/git/gnome-shell/src 
-I/home/dan/git/gnome-shell/build/src -I./. -I../. -I./src/st/. -I../src/st/. 
-I./src/st/.. -I../src/st/.. -I./src/tray -I../src/tray 
--filelist=/home/dan/git/gnome-shell/build/src/src@@gnome-shell@sha/Shell_0.1_gir_filelist
 --include=Clutter-4 --include=ClutterX11-4 --include=Meta-4 --include=Gcr-3 
--include=PolkitAgent-1.

[Touch-packages] [Bug 1812955] Re: g-ir-scanner is crashing with SIGSEGV instead of succeeding

2019-01-22 Thread Daniel van Vugt
Maybe related to bug 1812223.

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

Title:
  g-ir-scanner/Shell-0.1 is crashing with SIGSEGV instead of succeeding

Status in gobject-introspection package in Ubuntu:
  New

Bug description:
  g-ir-scanner is crashing with SIGSEGV instead of succeeding. So I
  can't build gnome-shell any more.

  Actually it looks like some kind of temporary sub-command "Shell-0.1"
  of g-ir-scanner that's crashing:

  /usr/bin/g-ir-scanner -pthread -I/usr/include/gobject-introspection-1.0 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
--no-libtool --namespace=Shell --nsversion=0.1 --warn-all --output 
src/Shell-0.1.gir --quiet -I/home/dan/git/gnome-shell/src 
-I/home/dan/git/gnome-shell/build/src -I./. -I../. -I./src/st/. -I../src/st/. 
-I./src/st/.. -I../src/st/.. -I./src/tray -I../src/tray 
--filelist=/home/dan/git/gnome-shell/build/src/src@@gnome-shell@sha/Shell_0.1_gir_filelist
 --include=Clutter-4 --include=ClutterX11-4 --include=Meta-4 --include=Gcr-3 
--include=PolkitAgent-1.0 --include=NM-1.0 
--include-uninstalled=subprojects/gvc/Gvc-1.0.gir 
--include-uninstalled=src/ShellMenu-0.1.gir 
--include-uninstalled=src/st/St-1.0.gir --cflags-begin -I./. -I../. 
-I./src/st/. -I../src/st/. -I./src/st/.. -I../src/st/.. -I./src/tray 
-I../src/tray -pthread -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/libxml2 
-I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 
-I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include 
-I/usr/include/cairo -I/usr/include/libdrm -I/usr/include/pango-1.0 
-I/usr/include/harfbuzz -I/usr/include/fribidi -I/usr/include/atk-1.0 
-I/usr/include/pixman-1 -I/usr/include/uuid -I/usr/include/freetype2 
-I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 -include 
/usr/include/mozjs-60/js/RequiredDefines.h 
-I/usr/include/gobject-introspection-1.0 -I/usr/include/mozjs-60 
-I/usr/include/gjs-1.0 -I/home/dan/tmp.gs/include/mutter-4/clutter 
-I/home/dan/tmp.gs/include/mutter-4/cogl -I/usr/include/json-glib-1.0 
-I/usr/include/libwacom-1.0 -I/usr/include/startup-notification-1.0 
-I/usr/include/polkit-1 -I/usr/include/gcr-3 -I/usr/include/gck-1 
-I/usr/include/p11-kit-1 -I/usr/include/libnm -I/usr/include/libsecret-1 
-I/usr/include/gstreamer-1.0 -D_REENTRANT -I/home/dan/tmp.gs/include/mutter-4 
-I/home/dan/tmp.gs/include/gsettings-desktop-schemas 
-I/usr/include/gnome-desktop-3.0 -I/usr/include/gnome-settings-daemon-3.0 
-I/usr/include/gudev-1.0 --cflags-end -L/home/dan/git/gnome-shell/build/src 
--add-include-path=/usr/share/gir-1.0 
--add-include-path=/home/dan/tmp.gs/lib/x86_64-linux-gnu/mutter-4 
--add-include-path=/home/dan/git/gnome-shell/build/subprojects/gvc 
--add-include-path=/home/dan/git/gnome-shell/build/src 
--add-include-path=/home/dan/git/gnome-shell/build/src/st 
-L/home/dan/git/gnome-shell/build/src -L/home/dan/git/gnome-shell/build/src/st 
-L/lib/x86_64-linux-gnu --library gnome-shell --extra-library=gio-2.0 
--extra-library=gobject-2.0 --extra-library=glib-2.0 --extra-library=xml2 
--extra-library=gtk-3 --extra-library=gdk-3 --extra-library=pangocairo-1.0 
--extra-library=pango-1.0 --extra-library=atk-1.0 --extra-library=cairo-gobject 
--extra-library=cairo --extra-library=gdk_pixbuf-2.0 
--extra-library=atk-bridge-2.0 --extra-library=gjs 
-L/home/dan/tmp.gs//lib/x86_64-linux-gnu/mutter-4 
--extra-library=mutter-clutter-4 --extra-library=m 
--extra-library=json-glib-1.0 --extra-library=pangoft2-1.0 
--extra-library=fontconfig --extra-library=freetype --extra-library=wayland-egl 
--extra-library=wayland-client --extra-library=Xtst --extra-library=Xi 
--extra-library=udev --extra-library=input --extra-library=xkbcommon 
--extra-library=wacom --extra-library=mutter-cogl-4 --extra-library=gmodule-2.0 
-pthread --extra-library=wayland-server --extra-library=EGL --extra-library=X11 
--extra-library=Xext --extra-library=Xdamage --extra-library=Xfixes 
--extra-library=Xcomposite --extra-library=Xrandr --extra-library=GL 
--extra-library=GLESv2 --extra-library=mutter-cogl-pango-4 
--extra-library=startup-notification-1 --extra-library=girepository-1.0 
--extra-library=polkit-agent-1 --extra-library=polkit-gobject-1 
--extra-library=gcr-base-3 --extra-library=gck-1 --extra-library=p11-kit 
--extra-library=systemd --extra-library=nm --extra-library=secret-1 
--extra-library=gstreamer-1.0 --extra-library=gstbase-1.0 
-L/home/dan/tmp.gs//lib/x86_64-linux-gnu --extra-library=mutter-4 
--extra-library=gnome-desktop-3 --extra-library=canberra 
--extra-library=gudev-1.0 --extra-library=pipewire-0.2 --extra-library=Xinerama 
--extra-library=ICE --extra-library=Xcursor --extra-library=xkbfile 
--extra-library=xkbcommon-x11 --extra-library=Xrender --extra-library=X11-xcb 
--extra-library=

[Touch-packages] [Bug 1812955] Re: g-ir-scanner is crashing with SIGSEGV instead of succeeding

2019-01-22 Thread Daniel van Vugt
I downgraded to the cosmic version of gobject-introspection but the bug
still happens.

I also tried bisecting gnome-shell git but the bug still happens in all
cases.

Seems like the regression is coming from somewhere else.

** Summary changed:

- g-ir-scanner is crashing with SIGSEGV instead of succeeding
+ g-ir-scanner/Shell-0.1 is crashing with SIGSEGV instead of succeeding

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

Title:
  g-ir-scanner/Shell-0.1 is crashing with SIGSEGV instead of succeeding

Status in gobject-introspection package in Ubuntu:
  New

Bug description:
  g-ir-scanner is crashing with SIGSEGV instead of succeeding. So I
  can't build gnome-shell any more.

  Actually it looks like some kind of temporary sub-command "Shell-0.1"
  of g-ir-scanner that's crashing:

  /usr/bin/g-ir-scanner -pthread -I/usr/include/gobject-introspection-1.0 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
--no-libtool --namespace=Shell --nsversion=0.1 --warn-all --output 
src/Shell-0.1.gir --quiet -I/home/dan/git/gnome-shell/src 
-I/home/dan/git/gnome-shell/build/src -I./. -I../. -I./src/st/. -I../src/st/. 
-I./src/st/.. -I../src/st/.. -I./src/tray -I../src/tray 
--filelist=/home/dan/git/gnome-shell/build/src/src@@gnome-shell@sha/Shell_0.1_gir_filelist
 --include=Clutter-4 --include=ClutterX11-4 --include=Meta-4 --include=Gcr-3 
--include=PolkitAgent-1.0 --include=NM-1.0 
--include-uninstalled=subprojects/gvc/Gvc-1.0.gir 
--include-uninstalled=src/ShellMenu-0.1.gir 
--include-uninstalled=src/st/St-1.0.gir --cflags-begin -I./. -I../. 
-I./src/st/. -I../src/st/. -I./src/st/.. -I../src/st/.. -I./src/tray 
-I../src/tray -pthread -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/libxml2 
-I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 
-I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include 
-I/usr/include/cairo -I/usr/include/libdrm -I/usr/include/pango-1.0 
-I/usr/include/harfbuzz -I/usr/include/fribidi -I/usr/include/atk-1.0 
-I/usr/include/pixman-1 -I/usr/include/uuid -I/usr/include/freetype2 
-I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 -include 
/usr/include/mozjs-60/js/RequiredDefines.h 
-I/usr/include/gobject-introspection-1.0 -I/usr/include/mozjs-60 
-I/usr/include/gjs-1.0 -I/home/dan/tmp.gs/include/mutter-4/clutter 
-I/home/dan/tmp.gs/include/mutter-4/cogl -I/usr/include/json-glib-1.0 
-I/usr/include/libwacom-1.0 -I/usr/include/startup-notification-1.0 
-I/usr/include/polkit-1 -I/usr/include/gcr-3 -I/usr/include/gck-1 
-I/usr/include/p11-kit-1 -I/usr/include/libnm -I/usr/include/libsecret-1 
-I/usr/include/gstreamer-1.0 -D_REENTRANT -I/home/dan/tmp.gs/include/mutter-4 
-I/home/dan/tmp.gs/include/gsettings-desktop-schemas 
-I/usr/include/gnome-desktop-3.0 -I/usr/include/gnome-settings-daemon-3.0 
-I/usr/include/gudev-1.0 --cflags-end -L/home/dan/git/gnome-shell/build/src 
--add-include-path=/usr/share/gir-1.0 
--add-include-path=/home/dan/tmp.gs/lib/x86_64-linux-gnu/mutter-4 
--add-include-path=/home/dan/git/gnome-shell/build/subprojects/gvc 
--add-include-path=/home/dan/git/gnome-shell/build/src 
--add-include-path=/home/dan/git/gnome-shell/build/src/st 
-L/home/dan/git/gnome-shell/build/src -L/home/dan/git/gnome-shell/build/src/st 
-L/lib/x86_64-linux-gnu --library gnome-shell --extra-library=gio-2.0 
--extra-library=gobject-2.0 --extra-library=glib-2.0 --extra-library=xml2 
--extra-library=gtk-3 --extra-library=gdk-3 --extra-library=pangocairo-1.0 
--extra-library=pango-1.0 --extra-library=atk-1.0 --extra-library=cairo-gobject 
--extra-library=cairo --extra-library=gdk_pixbuf-2.0 
--extra-library=atk-bridge-2.0 --extra-library=gjs 
-L/home/dan/tmp.gs//lib/x86_64-linux-gnu/mutter-4 
--extra-library=mutter-clutter-4 --extra-library=m 
--extra-library=json-glib-1.0 --extra-library=pangoft2-1.0 
--extra-library=fontconfig --extra-library=freetype --extra-library=wayland-egl 
--extra-library=wayland-client --extra-library=Xtst --extra-library=Xi 
--extra-library=udev --extra-library=input --extra-library=xkbcommon 
--extra-library=wacom --extra-library=mutter-cogl-4 --extra-library=gmodule-2.0 
-pthread --extra-library=wayland-server --extra-library=EGL --extra-library=X11 
--extra-library=Xext --extra-library=Xdamage --extra-library=Xfixes 
--extra-library=Xcomposite --extra-library=Xrandr --extra-library=GL 
--extra-library=GLESv2 --extra-library=mutter-cogl-pango-4 
--extra-library=startup-notification-1 --extra-library=girepository-1.0 
--extra-library=polkit-agent-1 --extra-library=polkit-gobject-1 
--extra-library=gcr-base-3 --extra-library=gck-1 --extra-library=p11-kit 
--extra-library=systemd --extra-library=nm --extra-library=secret-1 
--extra-library=gstreamer-1.0 --extra-library=gstbase-1.0 
-L/home/dan/tmp.gs/

[Touch-packages] [Bug 1812223] Re: gir test fail on ppc64el

2019-01-22 Thread Daniel van Vugt
Maybe related to bug 1812955?

The timing is suspicious and the errors are almost similar.

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

Title:
  gir test fail on ppc64el

Status in Meson:
  New
Status in gcc-8 package in Ubuntu:
  New
Status in gobject-introspection package in Ubuntu:
  New
Status in meson package in Ubuntu:
  New

Bug description:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-disco/disco/ppc64el/m/meson/20190116_031026_4df33@/log.gz

  ninja explain: genmarshal/genmarshalprog is dirty
  [1/75] Generating simple-resources_c with a custom command.
  [2/75] Generating simple-resources_h with a custom command.
  [3/75] Generating res3 with a meson_exe.py custom command.
  [4/75] Compiling C object 
'resources/41d311a@@simple-resources-test@exe/meson-generated_.._simple-resources.c.o'.
  [5/75] Compiling C object 
'resources/41d311a@@simple-resources-test@exe/simple-main.c.o'.
  [6/75] Generating simple-resources_gresource with a custom command.
  [7/75] Generating generated-resources_c with a custom command.
  [8/75] Generating generated-resources_h with a custom command.
  [9/75] Linking target resources/simple-resources-test.
  [10/75] Compiling C object 
'resources/41d311a@@generated-resources-test@exe/meson-generated_.._generated-resources.c.o'.
  [11/75] Generating build-resources_gresource with a custom command.
  [12/75] Compiling C object 
'resources/41d311a@@generated-resources-test@exe/generated-main.c.o'.
  [13/75] Linking target resources/generated-resources-test.
  [14/75] Compiling C object 'gir/dep1/dep2/7cbf35a@@dep2lib@sha/dep2.c.o'.
  [15/75] Linking target gir/dep1/dep2/libdep2lib.so.
  [16/75] Compiling C object 'gir/dep1/07d7481@@dep1lib@sha/dep1.c.o'.
  [17/75] Generating symbol file 
'gir/dep1/dep2/7cbf35a@@dep2lib@sha/libdep2lib.so.symbols'.
  [18/75] Linking target gir/dep1/libdep1lib.so.
  [19/75] Generating symbol file 
'gir/dep1/07d7481@@dep1lib@sha/libdep1lib.so.symbols'.
  [20/75] Compiling C object 'gir/327a146@@gir_lib2@sha/meson-sample2.c.o'.
  [21/75] Linking target gir/libgir_lib2.so.
  [22/75] Generating gsettings-compile-schemas with a custom command.
  [23/75] Compiling C object 'schemas/fd70ea1@@schemaprog@exe/schemaprog.c.o'.
  [24/75] Linking target schemas/schemaprog.
  [25/75] Generating generated-gdbus.c with a custom command.
  [26/75] Generating generated-gdbus.h with a custom command.
  [27/75] Generating generated-gdbus-docbook with a custom command.
  [28/75] Compiling C object 
'gdbus/8d60afc@@gdbus-test@exe/meson-generated_.._generated-gdbus.c.o'.
  [29/75] Compiling C object 'gdbus/8d60afc@@gdbus-test@exe/gdbusprog.c.o'.
  [30/75] Generating MesonDep2-1.0.gir with a custom command.
  g-ir-scanner: link: cc -o 
/tmp/tmpbrjz1hlu/tmp-introspect81qm411v/MesonDep2-1.0 
/tmp/tmpbrjz1hlu/tmp-introspect81qm411v/MesonDep2-1.0.o -L. -Wl,-rpath,. 
-Wl,--no-as-needed -L/tmp/tmpbrjz1hlu/gir/dep1/dep2 
-Wl,-rpath,/tmp/tmpbrjz1hlu/gir/dep1/dep2 -lasan -ldep2lib -lgobject-2.0 
-lglib-2.0 -lgio-2.0 -lgobject-2.0 -Wl,--export-dynamic -lgmodule-2.0 -pthread 
-lglib-2.0
  [31/75] Linking target gdbus/gdbus-test.
  [32/75] Generating MesonDep2-1.0.typelib with a custom command.
  [33/75] Generating enums.h with a meson_exe.py custom command.
  [34/75] Generating enums.c with a meson_exe.py custom command.
  [35/75] Compiling C object 
'mkenums/75bf728@@enumprog1@exe/meson-generated_.._enums.c.o'.
  [36/75] Compiling C object 
'mkenums/75bf728@@enumprog1@exe/meson-generated_.._main1.c.o'.
  [37/75] Linking target mkenums/enumprog1.
  [38/75] Generating MesonDep1-1.0.gir with a custom command.
  FAILED: gir/dep1/MesonDep1-1.0.gir 
  /usr/bin/g-ir-scanner -pthread -I/usr/include/gobject-introspection-1.0 
-I/usr/include/glib-2.0 -I/usr/lib/powerpc64le-linux-gnu/glib-2.0/include 
--no-libtool --namespace=MesonDep1 --nsversion=1.0 --warn-all --output 
gir/dep1/MesonDep1-1.0.gir --c-include=dep1.h 
'-I/tmp/autopkgtest.GpLQfj/build.Rq6/src/test cases/frameworks/7 
gnome/gir/dep1' -I/tmp/tmpbrjz1hlu/gir/dep1 
--filelist=/tmp/tmpbrjz1hlu/gir/dep1/07d7481@@dep1lib@sha/MesonDep1_1.0_gir_filelist
 --include=GObject-2.0 --include=MesonDep2-1.0 --symbol-prefix=meson 
--identifier-prefix=Meson --cflags-begin -DMESON_TEST -fsanitize=address 
-fno-omit-frame-pointer -I/usr/include/glib-2.0 
-I/usr/lib/powerpc64le-linux-gnu/glib-2.0/include --cflags-end 
--add-include-path=/tmp/tmpbrjz1hlu/gir/dep1/dep2 -lasan 
-L/tmp/tmpbrjz1hlu/gir/dep1/dep2 --extra-library=dep2lib --library dep1lib 
-L/tmp/tmpbrjz1hlu/gir/dep1 --extra-library=gobject-2.0 --extra-library=glib-2.0
  g-ir-scanner: link: cc -o 
/tmp/tmpbrjz1hlu/tmp-introspectghii58n3/MesonDep1-1.0 
/tmp/tmpbrjz1hlu/tmp-introspectghii58n3/MesonDep1-1.0.o -L. -Wl,-rpath,. 
-Wl,--no-as-needed -L/tmp/tmpbrjz1hlu/gir/dep1/dep2 

[Touch-packages] [Bug 1812955] Re: g-ir-scanner is crashing with SIGSEGV instead of succeeding

2019-01-22 Thread Daniel van Vugt
This bug will probably prevent future rebuilds of gnome-shell on disco,
so is at least High if not Critical.

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

Title:
  g-ir-scanner is crashing with SIGSEGV instead of succeeding

Status in gobject-introspection package in Ubuntu:
  New

Bug description:
  g-ir-scanner is crashing with SIGSEGV instead of succeeding. So I
  can't build gnome-shell any more.

  Actually it looks like some kind of temporary sub-command "Shell-0.1"
  of g-ir-scanner that's crashing:

  /usr/bin/g-ir-scanner -pthread -I/usr/include/gobject-introspection-1.0 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
--no-libtool --namespace=Shell --nsversion=0.1 --warn-all --output 
src/Shell-0.1.gir --quiet -I/home/dan/git/gnome-shell/src 
-I/home/dan/git/gnome-shell/build/src -I./. -I../. -I./src/st/. -I../src/st/. 
-I./src/st/.. -I../src/st/.. -I./src/tray -I../src/tray 
--filelist=/home/dan/git/gnome-shell/build/src/src@@gnome-shell@sha/Shell_0.1_gir_filelist
 --include=Clutter-4 --include=ClutterX11-4 --include=Meta-4 --include=Gcr-3 
--include=PolkitAgent-1.0 --include=NM-1.0 
--include-uninstalled=subprojects/gvc/Gvc-1.0.gir 
--include-uninstalled=src/ShellMenu-0.1.gir 
--include-uninstalled=src/st/St-1.0.gir --cflags-begin -I./. -I../. 
-I./src/st/. -I../src/st/. -I./src/st/.. -I../src/st/.. -I./src/tray 
-I../src/tray -pthread -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/libxml2 
-I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 
-I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include 
-I/usr/include/cairo -I/usr/include/libdrm -I/usr/include/pango-1.0 
-I/usr/include/harfbuzz -I/usr/include/fribidi -I/usr/include/atk-1.0 
-I/usr/include/pixman-1 -I/usr/include/uuid -I/usr/include/freetype2 
-I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 -include 
/usr/include/mozjs-60/js/RequiredDefines.h 
-I/usr/include/gobject-introspection-1.0 -I/usr/include/mozjs-60 
-I/usr/include/gjs-1.0 -I/home/dan/tmp.gs/include/mutter-4/clutter 
-I/home/dan/tmp.gs/include/mutter-4/cogl -I/usr/include/json-glib-1.0 
-I/usr/include/libwacom-1.0 -I/usr/include/startup-notification-1.0 
-I/usr/include/polkit-1 -I/usr/include/gcr-3 -I/usr/include/gck-1 
-I/usr/include/p11-kit-1 -I/usr/include/libnm -I/usr/include/libsecret-1 
-I/usr/include/gstreamer-1.0 -D_REENTRANT -I/home/dan/tmp.gs/include/mutter-4 
-I/home/dan/tmp.gs/include/gsettings-desktop-schemas 
-I/usr/include/gnome-desktop-3.0 -I/usr/include/gnome-settings-daemon-3.0 
-I/usr/include/gudev-1.0 --cflags-end -L/home/dan/git/gnome-shell/build/src 
--add-include-path=/usr/share/gir-1.0 
--add-include-path=/home/dan/tmp.gs/lib/x86_64-linux-gnu/mutter-4 
--add-include-path=/home/dan/git/gnome-shell/build/subprojects/gvc 
--add-include-path=/home/dan/git/gnome-shell/build/src 
--add-include-path=/home/dan/git/gnome-shell/build/src/st 
-L/home/dan/git/gnome-shell/build/src -L/home/dan/git/gnome-shell/build/src/st 
-L/lib/x86_64-linux-gnu --library gnome-shell --extra-library=gio-2.0 
--extra-library=gobject-2.0 --extra-library=glib-2.0 --extra-library=xml2 
--extra-library=gtk-3 --extra-library=gdk-3 --extra-library=pangocairo-1.0 
--extra-library=pango-1.0 --extra-library=atk-1.0 --extra-library=cairo-gobject 
--extra-library=cairo --extra-library=gdk_pixbuf-2.0 
--extra-library=atk-bridge-2.0 --extra-library=gjs 
-L/home/dan/tmp.gs//lib/x86_64-linux-gnu/mutter-4 
--extra-library=mutter-clutter-4 --extra-library=m 
--extra-library=json-glib-1.0 --extra-library=pangoft2-1.0 
--extra-library=fontconfig --extra-library=freetype --extra-library=wayland-egl 
--extra-library=wayland-client --extra-library=Xtst --extra-library=Xi 
--extra-library=udev --extra-library=input --extra-library=xkbcommon 
--extra-library=wacom --extra-library=mutter-cogl-4 --extra-library=gmodule-2.0 
-pthread --extra-library=wayland-server --extra-library=EGL --extra-library=X11 
--extra-library=Xext --extra-library=Xdamage --extra-library=Xfixes 
--extra-library=Xcomposite --extra-library=Xrandr --extra-library=GL 
--extra-library=GLESv2 --extra-library=mutter-cogl-pango-4 
--extra-library=startup-notification-1 --extra-library=girepository-1.0 
--extra-library=polkit-agent-1 --extra-library=polkit-gobject-1 
--extra-library=gcr-base-3 --extra-library=gck-1 --extra-library=p11-kit 
--extra-library=systemd --extra-library=nm --extra-library=secret-1 
--extra-library=gstreamer-1.0 --extra-library=gstbase-1.0 
-L/home/dan/tmp.gs//lib/x86_64-linux-gnu --extra-library=mutter-4 
--extra-library=gnome-desktop-3 --extra-library=canberra 
--extra-library=gudev-1.0 --extra-library=pipewire-0.2 --extra-library=Xinerama 
--extra-library=ICE --extra-library=Xcursor --extra-library=xkbfile 
--extra-library=xkbcommon-

[Touch-packages] [Bug 1812955] [NEW] g-ir-scanner is crashing with SIGSEGV instead of succeeding

2019-01-22 Thread Daniel van Vugt
Public bug reported:

g-ir-scanner is crashing with SIGSEGV instead of succeeding. So I can't
build gnome-shell any more.

Actually it looks like some kind of temporary sub-command "Shell-0.1" of
g-ir-scanner that's crashing:

/usr/bin/g-ir-scanner -pthread -I/usr/include/gobject-introspection-1.0 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
--no-libtool --namespace=Shell --nsversion=0.1 --warn-all --output 
src/Shell-0.1.gir --quiet -I/home/dan/git/gnome-shell/src 
-I/home/dan/git/gnome-shell/build/src -I./. -I../. -I./src/st/. -I../src/st/. 
-I./src/st/.. -I../src/st/.. -I./src/tray -I../src/tray 
--filelist=/home/dan/git/gnome-shell/build/src/src@@gnome-shell@sha/Shell_0.1_gir_filelist
 --include=Clutter-4 --include=ClutterX11-4 --include=Meta-4 --include=Gcr-3 
--include=PolkitAgent-1.0 --include=NM-1.0 
--include-uninstalled=subprojects/gvc/Gvc-1.0.gir 
--include-uninstalled=src/ShellMenu-0.1.gir 
--include-uninstalled=src/st/St-1.0.gir --cflags-begin -I./. -I../. 
-I./src/st/. -I../src/st/. -I./src/st/.. -I../src/st/.. -I./src/tray 
-I../src/tray -pthread -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/libxml2 
-I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 
-I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include 
-I/usr/include/cairo -I/usr/include/libdrm -I/usr/include/pango-1.0 
-I/usr/include/harfbuzz -I/usr/include/fribidi -I/usr/include/atk-1.0 
-I/usr/include/pixman-1 -I/usr/include/uuid -I/usr/include/freetype2 
-I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 -include 
/usr/include/mozjs-60/js/RequiredDefines.h 
-I/usr/include/gobject-introspection-1.0 -I/usr/include/mozjs-60 
-I/usr/include/gjs-1.0 -I/home/dan/tmp.gs/include/mutter-4/clutter 
-I/home/dan/tmp.gs/include/mutter-4/cogl -I/usr/include/json-glib-1.0 
-I/usr/include/libwacom-1.0 -I/usr/include/startup-notification-1.0 
-I/usr/include/polkit-1 -I/usr/include/gcr-3 -I/usr/include/gck-1 
-I/usr/include/p11-kit-1 -I/usr/include/libnm -I/usr/include/libsecret-1 
-I/usr/include/gstreamer-1.0 -D_REENTRANT -I/home/dan/tmp.gs/include/mutter-4 
-I/home/dan/tmp.gs/include/gsettings-desktop-schemas 
-I/usr/include/gnome-desktop-3.0 -I/usr/include/gnome-settings-daemon-3.0 
-I/usr/include/gudev-1.0 --cflags-end -L/home/dan/git/gnome-shell/build/src 
--add-include-path=/usr/share/gir-1.0 
--add-include-path=/home/dan/tmp.gs/lib/x86_64-linux-gnu/mutter-4 
--add-include-path=/home/dan/git/gnome-shell/build/subprojects/gvc 
--add-include-path=/home/dan/git/gnome-shell/build/src 
--add-include-path=/home/dan/git/gnome-shell/build/src/st 
-L/home/dan/git/gnome-shell/build/src -L/home/dan/git/gnome-shell/build/src/st 
-L/lib/x86_64-linux-gnu --library gnome-shell --extra-library=gio-2.0 
--extra-library=gobject-2.0 --extra-library=glib-2.0 --extra-library=xml2 
--extra-library=gtk-3 --extra-library=gdk-3 --extra-library=pangocairo-1.0 
--extra-library=pango-1.0 --extra-library=atk-1.0 --extra-library=cairo-gobject 
--extra-library=cairo --extra-library=gdk_pixbuf-2.0 
--extra-library=atk-bridge-2.0 --extra-library=gjs 
-L/home/dan/tmp.gs//lib/x86_64-linux-gnu/mutter-4 
--extra-library=mutter-clutter-4 --extra-library=m 
--extra-library=json-glib-1.0 --extra-library=pangoft2-1.0 
--extra-library=fontconfig --extra-library=freetype --extra-library=wayland-egl 
--extra-library=wayland-client --extra-library=Xtst --extra-library=Xi 
--extra-library=udev --extra-library=input --extra-library=xkbcommon 
--extra-library=wacom --extra-library=mutter-cogl-4 --extra-library=gmodule-2.0 
-pthread --extra-library=wayland-server --extra-library=EGL --extra-library=X11 
--extra-library=Xext --extra-library=Xdamage --extra-library=Xfixes 
--extra-library=Xcomposite --extra-library=Xrandr --extra-library=GL 
--extra-library=GLESv2 --extra-library=mutter-cogl-pango-4 
--extra-library=startup-notification-1 --extra-library=girepository-1.0 
--extra-library=polkit-agent-1 --extra-library=polkit-gobject-1 
--extra-library=gcr-base-3 --extra-library=gck-1 --extra-library=p11-kit 
--extra-library=systemd --extra-library=nm --extra-library=secret-1 
--extra-library=gstreamer-1.0 --extra-library=gstbase-1.0 
-L/home/dan/tmp.gs//lib/x86_64-linux-gnu --extra-library=mutter-4 
--extra-library=gnome-desktop-3 --extra-library=canberra 
--extra-library=gudev-1.0 --extra-library=pipewire-0.2 --extra-library=Xinerama 
--extra-library=ICE --extra-library=Xcursor --extra-library=xkbfile 
--extra-library=xkbcommon-x11 --extra-library=Xrender --extra-library=X11-xcb 
--extra-library=xcb --extra-library=xcb-randr --extra-library=xcb-res 
--extra-library=SM --extra-library=drm --extra-library=gbm
Command '['/home/dan/git/gnome-shell/build/tmp-introspectu443gr_x/Shell-0.1', 
'--introspect-dump=/home/dan/git/gnome-shell/build/tmp-introspectu443gr_x/functions.txt,/home/dan/git/gnome-shell/build/tmp-introspectu443gr_x/dump.xml']'
 died with .

Proble

[Touch-packages] [Bug 1812353] Re: content injection in http method (CVE-2019-3462)

2019-01-22 Thread Launchpad Bug Tracker
This bug was fixed in the package apt - 1.8.0~alpha3.1

---
apt (1.8.0~alpha3.1) unstable; urgency=emergency

  * SECURITY UPDATE: content injection in http method (CVE-2019-3462)
(LP: #1812353)

 -- Julian Andres Klode   Tue, 22 Jan 2019 19:52:38
+0100

** Changed in: apt (Ubuntu Disco)
   Status: In Progress => 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/1812353

Title:
  content injection in http method (CVE-2019-3462)

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Precise:
  Fix Released
Status in apt source package in Trusty:
  Fix Released
Status in apt source package in Xenial:
  Fix Released
Status in apt source package in Bionic:
  Fix Released
Status in apt source package in Cosmic:
  Fix Released
Status in apt source package in Disco:
  Fix Released

Bug description:
  apt, starting with version 0.8.15, decodes target URLs of redirects,
  but does not check them for newlines, allowing MiTM attackers (or
  repository mirrors) to inject arbitrary headers into the result
  returned to the main process.

  If the URL embeds hashes of the supposed file, it can thus be used to
  disable any validation of the downloaded file, as the fake hashes will
  be prepended in front of the right hashes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1812353/+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 1812353] Re: content injection in http method (CVE-2019-3462)

2019-01-22 Thread Christoph Anton Mitterer
Is there any more detailed evaluation of this hole?

It reads absolutely catastrophic, like that secure APT is basically
broken since 2011,… and if anyone has found that issue before (which one
must assume in the worst case) any code could have been rather easily
introduced in any Debian based system, from end users to DDs.

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

Title:
  content injection in http method (CVE-2019-3462)

Status in apt package in Ubuntu:
  In Progress
Status in apt source package in Precise:
  Fix Released
Status in apt source package in Trusty:
  Fix Released
Status in apt source package in Xenial:
  Fix Released
Status in apt source package in Bionic:
  Fix Released
Status in apt source package in Cosmic:
  Fix Released
Status in apt source package in Disco:
  In Progress

Bug description:
  apt, starting with version 0.8.15, decodes target URLs of redirects,
  but does not check them for newlines, allowing MiTM attackers (or
  repository mirrors) to inject arbitrary headers into the result
  returned to the main process.

  If the URL embeds hashes of the supposed file, it can thus be used to
  disable any validation of the downloaded file, as the fake hashes will
  be prepended in front of the right hashes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1812353/+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 1758736] Re: [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only mono playback

2019-01-22 Thread Daniel van Vugt
** Tags removed: artful

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

Title:
  [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only
  mono playback

Status in pulseaudio package in Ubuntu:
  Confirmed
Status in pulseaudio source package in Bionic:
  New
Status in pulseaudio source package in Cosmic:
  New
Status in pulseaudio source package in Disco:
  Confirmed

Bug description:
  There is not stereo playback only mono playback

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3.1
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   kaj1755 F...m pulseaudio
   /dev/snd/controlC1:  kaj1755 F pulseaudio
   /dev/snd/pcmC0D0c:   kaj1755 F...m pulseaudio
   /dev/snd/controlC0:  kaj1755 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 25 21:30:50 2018
  InstallationDate: Installed on 2018-03-08 (17 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:S7 successful
  Symptom_Card: SteelSeries Arctis 7 - SteelSeries Arctis 7
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: No sound at all
  Title: [USB-Audio - SteelSeries Arctis 7, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/09/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R06ET35W (1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FMS2AV00
  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:bvrR06ET35W(1.09):bd03/09/2016:svnLENOVO:pn20FMS2AV00:pvrThinkPadT460:rvnLENOVO:rn20FMS2AV00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460
  dmi.product.name: 20FMS2AV00
  dmi.product.version: ThinkPad T460
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1758736/+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 1812948] Re: bug search

2019-01-22 Thread Daniel van Vugt
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:
1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected. 
3. The behavior you actually encountered (in as much detail as possible).
Thanks!

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

** Changed in: 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/1812948

Title:
  bug search

Status in Ubuntu:
  Incomplete

Bug description:
  just did a search and these bugs came up.I'm not sure haw they
  work

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:02:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.77  Tue Jul 10 18:28:52 
PDT 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Tue Jan 22 19:38:51 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   fwts-efi-runtime-dkms, 18.03.00, 4.15.0-43-generic, x86_64: installed
   nvidia, 390.77, 4.15.0-43-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GF108 [GeForce GT 620] [10de:0f01] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: eVga.com. Corp. GF108 [GeForce GT 620] [3842:2625]
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 413c:2005 Dell Computer Corp. RT7D50 Keyboard
   Bus 002 Device 004: ID 058f:9360 Alcor Micro Corp. 8-in-1 Media Card Reader
   Bus 002 Device 002: ID 062a: Creative Labs Optical mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic 
root=UUID=c599b74a-de09-473c-b0e9-39538d42a83d ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/31/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.40
  dmi.board.name: N68C-GS FX
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.40:bd10/31/2012:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN68C-GSFX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Tue Jan 22 17:27:30 2019
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputHID 062a:MOUSE, id 8
   inputDELL DELL USB Keyboard KEYBOARD, id 9
  xserver.errors: open /dev/fb0: No such file or directory
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.6-1ubuntu4.2

To manage notificat

[Touch-packages] [Bug 1812948] [NEW] bug search

2019-01-22 Thread Alistair
Public bug reported:

just did a search and these bugs came up.I'm not sure haw they work

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
Uname: Linux 4.15.0-43-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:02:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.77  Tue Jul 10 18:28:52 
PDT 2018
 GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04)
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Tue Jan 22 19:38:51 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 fwts-efi-runtime-dkms, 18.03.00, 4.15.0-43-generic, x86_64: installed
 nvidia, 390.77, 4.15.0-43-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation GF108 [GeForce GT 620] [10de:0f01] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: eVga.com. Corp. GF108 [GeForce GT 620] [3842:2625]
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 003: ID 413c:2005 Dell Computer Corp. RT7D50 Keyboard
 Bus 002 Device 004: ID 058f:9360 Alcor Micro Corp. 8-in-1 Media Card Reader
 Bus 002 Device 002: ID 062a: Creative Labs Optical mouse
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcEnviron:
 LANGUAGE=en_CA:en
 PATH=(custom, no user)
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic 
root=UUID=c599b74a-de09-473c-b0e9-39538d42a83d ro quiet splash
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/31/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.40
dmi.board.name: N68C-GS FX
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.40:bd10/31/2012:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN68C-GSFX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Tue Jan 22 17:27:30 2019
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputHID 062a:MOUSE, id 8
 inputDELL DELL USB Keyboard KEYBOARD, id 9
xserver.errors: open /dev/fb0: No such file or directory
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.19.6-1ubuntu4.2

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


** Tags: amd64 apport-bug bionic ubuntu

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

Title:
  bug search

Status in xorg package in Ubuntu:
  New

Bug description:
  just did a search and these bugs came up.I'm not sure haw they
  work

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:02:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.77  Tue Jul 10 18:28:52 
PDT 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: No

[Touch-packages] [Bug 1758736] Re: [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only mono playback

2019-01-22 Thread Dave Chiluk
** Changed in: pulseaudio (Ubuntu)
 Assignee: (unassigned) => Dave Chiluk (chiluk)

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

** Also affects: pulseaudio (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

** Also affects: pulseaudio (Ubuntu Disco)
   Importance: Low
 Assignee: Dave Chiluk (chiluk)
   Status: Confirmed

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

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

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

** Changed in: pulseaudio (Ubuntu Cosmic)
 Assignee: (unassigned) => Dave Chiluk (chiluk)

** Changed in: pulseaudio (Ubuntu Bionic)
 Assignee: (unassigned) => Dave Chiluk (chiluk)

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

Title:
  [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only
  mono playback

Status in pulseaudio package in Ubuntu:
  Confirmed
Status in pulseaudio source package in Bionic:
  New
Status in pulseaudio source package in Cosmic:
  New
Status in pulseaudio source package in Disco:
  Confirmed

Bug description:
  There is not stereo playback only mono playback

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3.1
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   kaj1755 F...m pulseaudio
   /dev/snd/controlC1:  kaj1755 F pulseaudio
   /dev/snd/pcmC0D0c:   kaj1755 F...m pulseaudio
   /dev/snd/controlC0:  kaj1755 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 25 21:30:50 2018
  InstallationDate: Installed on 2018-03-08 (17 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:S7 successful
  Symptom_Card: SteelSeries Arctis 7 - SteelSeries Arctis 7
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: No sound at all
  Title: [USB-Audio - SteelSeries Arctis 7, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/09/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R06ET35W (1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FMS2AV00
  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:bvrR06ET35W(1.09):bd03/09/2016:svnLENOVO:pn20FMS2AV00:pvrThinkPadT460:rvnLENOVO:rn20FMS2AV00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460
  dmi.product.name: 20FMS2AV00
  dmi.product.version: ThinkPad T460
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1758736/+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 1620636] Re: Fails to pair with Bose QC35 headphones

2019-01-22 Thread Daniel van Vugt
** Tags added: xenial

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

Title:
  Fails to pair with Bose QC35 headphones

Status in Canonical System Image:
  In Progress
Status in bluez package in Ubuntu:
  In Progress

Bug description:
  I am unable to pair the Bose QC35 BT headphones with Ubuntu, either
  Ubuntu desktop running 16.04 LTS with bluez 5.37 (also tried bluez
  5.41 from installed from yakkety archive), nor using Ubuntu Touch rc-
  proposed build for Turbo #174. I'm trying to pair through the normal
  bluetooth control panel brought up through the bluetooth indicator.

  I've attached some logs that show it failing to pair. If I can provide
  anymore useful information about the headphones, please let me know.

  Syslog with bluetoothd debugging enabled:
  http://pastebin.ubuntu.com/23141394/

  btmon output:
  http://pastebin.ubuntu.com/23141446/

  bluetoothctl output:
  http://pastebin.ubuntu.com/23141510/

  With Linux kernel 4.8.0 and bluez 4.52:
  ---

  bluetoothctl: http://pastebin.ubuntu.com/23256457/
  btmon: http://pastebin.ubuntu.com/23256471/

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1620636/+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 1812918] Re: Bluetooth Sound disjoined 18.04

2019-01-22 Thread Daniel van Vugt
Can you please explain in different words what you mean by disjoined
sound?

I am also wondering if this might be somehow related to bug 1553669 or
bug 1620636.

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

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

Title:
  Bluetooth Sound disjoined 18.04

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  Since upgrade Ubuntu 16.04 to 18.04, my bluetooth did not work fine,
  sound is disjoined

  1) Ubuntu 18.04.1 LTS

  2) apt-cache policy pkgname
  N: Impossible de trouver le paquet pkgname

  3) With Ubuntu 16.04, my headset ( Bose QC35 ) was working fine by
  bluetooth connection

  4) Sound is disjoined with Ubuntu 18.04

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 22 21:47:25 2019
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic 
root=UUID=53832273-15e8-4b92-b0a3-6b1f2cf57770 ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/08/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A78M-DS2
  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.:bvrF3:bd01/08/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A78M-DS2:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.: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: Gigabyte Technology Co., Ltd.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 00:1B:10:00:2A:EC  ACL MTU: 1017:8  SCO MTU: 64:0
UP RUNNING PSCAN INQUIRY 
RX bytes:2620674 acl:357 sco:53942 events:1739 errors:0
TX bytes:3630646 acl:4536 sco:0 commands:218 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1812918/+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 1789758] Re: bluetooth headphones a2dp profile does not function after suspend, only HSP

2019-01-22 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  bluetooth headphones a2dp profile does not function after suspend,
  only HSP

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  1) lsb_release -rd
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  2) $ apt-cache policy bluez
  bluez:
Installed: 5.48-0ubuntu3.1
Candidate: 5.48-0ubuntu3.1
Version table:
   *** 5.48-0ubuntu3.1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   5.48-0ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  3) bluetooth headphones stay working in a2dp mode even after suspend

  4) bluetooth headphones connect but no sound will come out of a2dp
  mode, only in HSP profile

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18
  Uname: Linux 4.15.0-30-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 29 18:07:26 2018
  InstallationDate: Installed on 2018-05-26 (95 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180525)
  InterestingModules: rfcomm bnep btusb bluetooth
  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.15.0-30-generic 
root=UUID=9e84ffd4-d629-4dcd-a6c4-6648d1a34665 ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/16/2015
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: RKPPT10H.86A.0041.2015.0316.1442
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: D53427RKE
  dmi.board.vendor: Intel Corporation
  dmi.board.version: G87971-406
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrRKPPT10H.86A.0041.2015.0316.1442:bd03/16/2015:svn:pn:pvr:rvnIntelCorporation:rnD53427RKE:rvrG87971-406:cvn:ct3:cvr:
  dmi.product.family: To be filled by O.E.M.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 48:51:B7:07:93:F5  ACL MTU: 1021:5  SCO MTU: 96:5
DOWN 
RX bytes:5617087 acl:790 sco:22622 events:634625 errors:0
TX bytes:540631745 acl:632348 sco:22584 commands:537 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1789758/+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 1812867] Re: sound from bluetooth device is like vintage when quiting the hibernate

2019-01-22 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1789758 ***
https://bugs.launchpad.net/bugs/1789758

Oh, actually this has already been reported in bug 1789758.

** This bug has been marked a duplicate of bug 1789758
   bluetooth headphones a2dp profile does not function after suspend, only HSP

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

Title:
  sound from bluetooth device is like vintage when quiting the hibernate

Status in Ubuntu Budgie:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Hi
  I've just noticed this today, with my laptop and my desktop, both under 
Ubuntu Budgie 18.10, all last updates installed if it can help you. Using a USB 
Bluetooth key for both

  After using my wireless speaker (JBL GO for more precision if it's
  needed) within Bluetooth, I lock my computer when I leave my office.
  then I unlock my computer when I'm back to.

  Wanna play some music on the said device. Then I start to play
  music... with somewhat vintage effect on the sound.

  I shutdown the device, start it up and same thing.

  To get a working properly BT, I have to

  - unplug and plug the USB BT key
  - middle click two time on the Bluetooth logo at the top, likely to disable / 
enable it

  and then it work like a charm.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntubudgie/+bug/1812867/+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 1812914] Re: X diagnostics

2019-01-22 Thread Daniel van Vugt
Can you please describe what problem you are experiencing?

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

** Changed in: xorg-server (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/1812914

Title:
  X diagnostics

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  This bug is from X Diagnostics

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-14.15-generic 4.18.20
  Uname: Linux 4.18.0-14-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Tue Jan 22 21:42:20 2019
  DistUpgraded: 2019-01-15 00:39:12,441 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: L’exécution du processus fils « 
./xorg_fix_proprietary.py » a échoué (Aucun fichier ou dossier de ce type) (8))
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Madison [Mobility Radeon HD 5650/5750 
/ 6530M/6550M] [1002:68c1] (prog-if 00 [VGA controller])
 Subsystem: Sony Corporation Mobility Radeon HD 5650 [104d:9071]
  InstallationDate: Installed on 2016-10-08 (836 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 064e:a213 Suyin Corp. 
   Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Sony Corporation VPCEC1S1E
  ProcEnviron:
   LANGUAGE=fr_FR
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/usr/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-14-generic 
root=UUID=7c6080a7-1a0e-4121-94f1-42cba8e7b69c ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to cosmic on 2019-01-14 (7 days ago)
  dmi.bios.date: 07/20/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R0300Y8
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR0300Y8:bd07/20/2010:svnSonyCorporation:pnVPCEC1S1E:pvrC6050X6T:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.family: VAIO
  dmi.product.name: VPCEC1S1E
  dmi.product.sku: N/A
  dmi.product.version: C6050X6T
  dmi.sys.vendor: Sony Corporation
  version.compiz: compiz 1:0.9.13.1+18.10.20180930-0ubuntu1
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.10.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.10.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3
  xserver.bootTime: Tue Jan 22 21:23:19 2019
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.20.1-3ubuntu2.1
  xserver.video_driver: radeon

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1812914/+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 1812867] Re: sound from bluetooth device is like vintage when quiting the hibernate

2019-01-22 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1789758 ***
https://bugs.launchpad.net/bugs/1789758

It sounds like your Bluetooth audio is resuming with profile HSP/HFP
(low quality audio).

Next time it happens please look at your audio settings and tell us what
the current profile is. It should be A2DP for higher quality, and not
HSP/HFP.

** Package changed: bluez (Ubuntu) => pulseaudio (Ubuntu)

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

Title:
  sound from bluetooth device is like vintage when quiting the hibernate

Status in Ubuntu Budgie:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Hi
  I've just noticed this today, with my laptop and my desktop, both under 
Ubuntu Budgie 18.10, all last updates installed if it can help you. Using a USB 
Bluetooth key for both

  After using my wireless speaker (JBL GO for more precision if it's
  needed) within Bluetooth, I lock my computer when I leave my office.
  then I unlock my computer when I'm back to.

  Wanna play some music on the said device. Then I start to play
  music... with somewhat vintage effect on the sound.

  I shutdown the device, start it up and same thing.

  To get a working properly BT, I have to

  - unplug and plug the USB BT key
  - middle click two time on the Bluetooth logo at the top, likely to disable / 
enable it

  and then it work like a charm.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntubudgie/+bug/1812867/+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 1812943] [NEW] undocumented watch reacts to sigwinch or terminal resize

2019-01-22 Thread Evan Benn
Public bug reported:

Hello, I would normally PR straight to the source, but I could not work
out where that is.

watch seems to react to terminal resizes (good). But this is not
documented in the man page. This is an issue if the user actually wants
that command to only run at the specified cadence. IE it is expensive or
dangerous. A flag to disable would be nice, but really just documenting
is enough.

Confirm with:

watch -n60  'echo $(( $(cat f) + 1 )) | sponge f; cat f'

and resize your window

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

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

Title:
  undocumented watch reacts to sigwinch or terminal resize

Status in procps package in Ubuntu:
  New

Bug description:
  Hello, I would normally PR straight to the source, but I could not
  work out where that is.

  watch seems to react to terminal resizes (good). But this is not
  documented in the man page. This is an issue if the user actually
  wants that command to only run at the specified cadence. IE it is
  expensive or dangerous. A flag to disable would be nice, but really
  just documenting is enough.

  Confirm with:

  watch -n60  'echo $(( $(cat f) + 1 )) | sponge f; cat f'

  and resize your window

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1812943/+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 1770271] Re: VegaM support

2019-01-22 Thread Chih-Hsyuan Ho
@Timo,agreed. And we are not seeing any business need to support VegaM
in Xenial in near future (if ever.)

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

Title:
  VegaM support

Status in amd:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Won't Fix
Status in mesa source package in Xenial:
  Won't Fix
Status in linux source package in Bionic:
  New
Status in mesa source package in Bionic:
  Fix Committed

Bug description:
  VegaM is a new GPU.  Please include support for VegaM in the next LTS
  (16.04.x and 18.04.x) and non-LTS releases.

  Kernel support starts here (32 patches):
  https://patchwork.freedesktop.org/patch/218839/

  Mesa support:
  
https://cgit.freedesktop.org/mesa/mesa/commit/?id=d6a66bc8dbcdeed8e87f649bc281de0d60d2f123
  
https://cgit.freedesktop.org/mesa/mesa/commit/?id=c6f1d360198c52d208645c0ccb5e988cded408e8
  
https://cgit.freedesktop.org/mesa/mesa/commit/?id=90de03708fa269ad54de881b467f4811e4eef87e

To manage notifications about this bug go to:
https://bugs.launchpad.net/amd/+bug/1770271/+subscriptions

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


[Touch-packages] [Bug 1777674] Re: Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD servers with DVD

2019-01-22 Thread Joseph Salisbury
** Changed in: linux (Ubuntu Bionic)
   Status: In Progress => Confirmed

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

** Changed in: linux (Ubuntu)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

** Changed in: linux (Ubuntu Bionic)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

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

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

Status in dellserver:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Confirmed

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

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

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

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

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

  Only physical reset helps in continuing the reboot test.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dellserver/+bug/1777674/+subscriptions

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


[Touch-packages] [Bug 1576844] Re: Touchpad/Trackpad freezes then eventually unfreezes (repeatedly)

2019-01-22 Thread Juno
I have recently acquired an used Latitude model and I'm having the same
issue on Ubuntu 18.04. This  E6420 model has a trackpoint/pointing stick
on it, which works fine, moving the cursor around, but the pad won't
work for something between 30 seconds to over a minute. Everything else
is running fine during that touchpad freeze. I still have not updated
the BIOS.

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

Title:
  Touchpad/Trackpad freezes then eventually unfreezes (repeatedly)

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  Several times yesterday and today (April 28-29, 2016) the touchpad
  (trackpad) on the Dell XPS 13 9343 has frozen.  Other functions
  (keyboard, screen, etc.) have been fine but the pointer has been
  frozen in place.  Then after 1-3 minutes functionality returns.

  Thank you very much for your assistance and I'd be happy to provide
  more information.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.38-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  BootLog:

  CompizPlugins: [core,composite,opengl,cube,rotate]
  CompositorRunning: None
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Fri Apr 29 16:09:32 2016
  DistUpgraded: 2016-04-27 15:53:13,798 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.248+bdcom, 4.2.0-36-generic, x86_64: installed
   bcmwl, 6.30.223.248+bdcom, 4.4.0-22-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
     Subsystem: Dell Broadwell-U Integrated Graphics [1028:0665]
  InstallationDate: Installed on 2015-08-06 (267 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Dell Inc. XPS 13 9343
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-04-27 (2 days ago)
  dmi.bios.date: 07/14/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0TM99H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd07/14/2015:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0TM99H:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  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
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Wed Apr 27 15:54:22 2016
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5152
   vendor SHP
  xserver.version: 2:1.18.3-1ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1576844/+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 1811812] Re: Util-linux_2.33.1-0.1ubuntu1 will not install - unmet dependendies

2019-01-22 Thread Brian Murray
Part of Steve's point is that when login becomes available in -proposed
for disco then util-linux will be migratable to the release pocket
without any changes to the package itself. Subsequently, because no
changes are required to the util-linux package there will not be a
changelog entry in the package referencing this bug report so it
wouldn't be closed automatically. Given that this situation will resolve
itself in the archive automatically it makes sense to close the bug
report rather than leave it open for somebody to clean up down the line.

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

Title:
  Util-linux_2.33.1-0.1ubuntu1 will not install - unmet dependendies

Status in util-linux package in Ubuntu:
  Invalid

Bug description:
  Package util-linux (2.33.1-0.1ubuntu1) cannot be installed due to unmet 
dependencies.
  Util-linux depends on login (>=1:4.5-1.1~) but the latest installable version 
is login (1:4.5-1ubuntu1).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1811812/+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 1808717] Re: link hardening installed twice into /etc/sysctl.d

2019-01-22 Thread Brian Murray
** Tags added: cosmic

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

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

Title:
  link hardening installed twice into /etc/sysctl.d

Status in procps package in Ubuntu:
  Confirmed

Bug description:
  The procps package installs (at least;-) two files into /etc/sysctl.d in 
disco:
  * 10-link-restrictions.conf and
  * protect-links.conf

  The non-comment contents of these two files is identical.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1808717/+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 1811812] Re: Util-linux_2.33.1-0.1ubuntu1 will not install - unmet dependendies

2019-01-22 Thread Brian Murray
Additionally, just because we didn't want to keep this bug report open
it does not follow that we do not want any bug reports to be submitted.

** Changed in: util-linux (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  Util-linux_2.33.1-0.1ubuntu1 will not install - unmet dependendies

Status in util-linux package in Ubuntu:
  Invalid

Bug description:
  Package util-linux (2.33.1-0.1ubuntu1) cannot be installed due to unmet 
dependencies.
  Util-linux depends on login (>=1:4.5-1.1~) but the latest installable version 
is login (1:4.5-1ubuntu1).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1811812/+subscriptions

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


Re: [Touch-packages] [Bug 1801910] Re: logrotate fails on LXC

2019-01-22 Thread Marco Bertorello
Il 15/01/2019 04:48, Phan Van Cuong ha scritto:
> Hi Marco,
>
> In my opinion, I think we should install rsyslog above on the container.
> You could create a new image for ubuntu 18.04 for never do it again.
>
> Like what I said, could be it happened on the image of Proxmox, so you
> should install the newest package of rsyslog on the container.
>
> By default, Ubuntu 18.04 rsyslogd version is rsyslogd 8.32.0.
>
> This is a result after upgrade:
>
> $ rsyslogd -version
> rsyslogd 8.40.0, compiled with:
>   PLATFORM:   x86_64-pc-linux-gnu
>   PLATFORM (lsb_release -d):  
>   FEATURE_REGEXP: Yes
>   GSSAPI Kerberos 5 support:  No
>   FEATURE_DEBUG (debug build, slow code): No
>   32bit Atomic operations supported:  Yes
>   64bit Atomic operations supported:  Yes
>   memory allocator:   system default
>   Runtime Instrumentation (slow code):No
>   uuid support:   Yes
>   systemd support:Yes
>   Number of Bits in RainerScript integers: 64
>
> Seehttps://www.rsyslog.com  for more information.

Hi Phan,
I confirm your solution.
thanks alot and best regards

-- 
Marco Bertorello

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

Title:
  logrotate fails on LXC

Status in logrotate package in Ubuntu:
  Confirmed

Bug description:
  daily, I receive this alert from logrotate script in cron.daily:

  /etc/cron.daily/logrotate:
  Failed to kill unit rsyslog.service: Input/output error
  error: error running non-shared postrotate script for /var/log/syslog of 
'/var/log/syslog
  '
  run-parts: /etc/cron.daily/logrotate exited with return code 1

  My ubuntu is a LXC running on top of ProxmoxVE.

  the problem occour when logrotate script call /usr/lib/rsyslog
  /rsyslog-rotate that has this call:

  systemctl kill -s HUP rsyslog.service

  I already checked my disks status (because the input/output error) but
  them are ok.

  The same issue is present also in another LXC, ubuntu also this one,
  running on another node of the same cluster

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: logrotate 3.11.0-0.1ubuntu1
  ProcVersionSignature:
   
  Uname: Linux 4.15.18-7-pve x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  Date: Tue Nov  6 10:26:37 2018
  ProcEnviron:
   LANG=C
   SHELL=/bin/bash
   TERM=xterm
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  SourcePackage: logrotate
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1801910/+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 1782511] Re: [UX370UAR, Realtek ALC295, Speaker, Internal] No sound at all

2019-01-22 Thread MAI Anh Tuan
I can change sound volume, mute/unmute. It shows as everything works fine but 
actually no sound on builtin speaker.
Jack 3.5 works fine.
Bluetooth speaker works fine.

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

Title:
  [UX370UAR, Realtek ALC295, Speaker, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  none

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   ubuntu 2209 F...m pulseaudio
   /dev/snd/pcmC0D0p:   ubuntu 2209 F...m pulseaudio
   /dev/snd/controlC0:  ubuntu 2209 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 18 22:19:23 2018
  InstallationDate: Installed on 2018-07-19 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   ubuntu 2209 F...m pulseaudio
   /dev/snd/pcmC0D0p:   ubuntu 2209 F...m pulseaudio
   /dev/snd/controlC0:  gdm 961 F pulseaudio
ubuntu 2209 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [UX370UAR, Realtek ALC295, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/16/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX370UAR.303
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX370UAR
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX370UAR.303:bd11/16/2017:svnASUSTeKCOMPUTERINC.:pnUX370UAR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX370UAR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX370UAR
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1782511/+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 1812918] [NEW] Bluetooth Sound disjoined 18.04

2019-01-22 Thread Yann Marchand
Public bug reported:

Since upgrade Ubuntu 16.04 to 18.04, my bluetooth did not work fine,
sound is disjoined

1) Ubuntu 18.04.1 LTS

2) apt-cache policy pkgname
N: Impossible de trouver le paquet pkgname

3) With Ubuntu 16.04, my headset ( Bose QC35 ) was working fine by
bluetooth connection

4) Sound is disjoined with Ubuntu 18.04

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: bluez 5.48-0ubuntu3.1
ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
Uname: Linux 4.15.0-43-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Jan 22 21:47:25 2019
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic 
root=UUID=53832273-15e8-4b92-b0a3-6b1f2cf57770 ro quiet splash vt.handoff=1
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/08/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F3
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: F2A78M-DS2
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.:bvrF3:bd01/08/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A78M-DS2:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.: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: Gigabyte Technology Co., Ltd.
hciconfig:
 hci0:  Type: Primary  Bus: USB
BD Address: 00:1B:10:00:2A:EC  ACL MTU: 1017:8  SCO MTU: 64:0
UP RUNNING PSCAN INQUIRY 
RX bytes:2620674 acl:357 sco:53942 events:1739 errors:0
TX bytes:3630646 acl:4536 sco:0 commands:218 errors:0

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

Title:
  Bluetooth Sound disjoined 18.04

Status in bluez package in Ubuntu:
  New

Bug description:
  Since upgrade Ubuntu 16.04 to 18.04, my bluetooth did not work fine,
  sound is disjoined

  1) Ubuntu 18.04.1 LTS

  2) apt-cache policy pkgname
  N: Impossible de trouver le paquet pkgname

  3) With Ubuntu 16.04, my headset ( Bose QC35 ) was working fine by
  bluetooth connection

  4) Sound is disjoined with Ubuntu 18.04

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 22 21:47:25 2019
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic 
root=UUID=53832273-15e8-4b92-b0a3-6b1f2cf57770 ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/08/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A78M-DS2
  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.:bvrF3:bd01/08/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A78M-DS2:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.: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: Gigabyte Technology Co., Ltd.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 00:1B:10:00:2A:EC  ACL MTU: 1017:8  SCO MTU: 64:0
UP RUNNING PSCAN INQUIRY 
RX bytes:2620674 acl:357 sco:53942 events:1739 errors:0
TX bytes:3630646 acl:4536 sco:0 commands:218 errors:0

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

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

[Touch-packages] [Bug 1812914] [NEW] X diagnostics

2019-01-22 Thread Jacques Basseck
Public bug reported:

This bug is from X Diagnostics

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: xorg 1:7.7+19ubuntu8
ProcVersionSignature: Ubuntu 4.18.0-14.15-generic 4.18.20
Uname: Linux 4.18.0-14-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Tue Jan 22 21:42:20 2019
DistUpgraded: 2019-01-15 00:39:12,441 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: L’exécution du processus fils « 
./xorg_fix_proprietary.py » a échoué (Aucun fichier ou dossier de ce type) (8))
DistroCodename: cosmic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Madison [Mobility Radeon HD 5650/5750 / 
6530M/6550M] [1002:68c1] (prog-if 00 [VGA controller])
   Subsystem: Sony Corporation Mobility Radeon HD 5650 [104d:9071]
InstallationDate: Installed on 2016-10-08 (836 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
Lsusb:
 Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 003: ID 064e:a213 Suyin Corp. 
 Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Sony Corporation VPCEC1S1E
ProcEnviron:
 LANGUAGE=fr_FR
 PATH=(custom, no user)
 LANG=fr_FR.UTF-8
 SHELL=/usr/bin/zsh
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-14-generic 
root=UUID=7c6080a7-1a0e-4121-94f1-42cba8e7b69c ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: Upgraded to cosmic on 2019-01-14 (7 days ago)
dmi.bios.date: 07/20/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: R0300Y8
dmi.board.asset.tag: N/A
dmi.board.name: VAIO
dmi.board.vendor: Sony Corporation
dmi.board.version: N/A
dmi.chassis.asset.tag: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: Sony Corporation
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR0300Y8:bd07/20/2010:svnSonyCorporation:pnVPCEC1S1E:pvrC6050X6T:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
dmi.product.family: VAIO
dmi.product.name: VPCEC1S1E
dmi.product.sku: N/A
dmi.product.version: C6050X6T
dmi.sys.vendor: Sony Corporation
version.compiz: compiz 1:0.9.13.1+18.10.20180930-0ubuntu1
version.libdrm2: libdrm2 2.4.95-1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.10.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.10.1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3
xserver.bootTime: Tue Jan 22 21:23:19 2019
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.20.1-3ubuntu2.1
xserver.video_driver: radeon

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


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

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

Title:
  X diagnostics

Status in xorg package in Ubuntu:
  New

Bug description:
  This bug is from X Diagnostics

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-14.15-generic 4.18.20
  Uname: Linux 4.18.0-14-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Tue Jan 22 21:42:20 2019
  DistUpgraded: 2019-01-15 00:39:12,441 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: L’exécution du processus fils « 
./xorg_fix_proprietary.py » a échoué (Aucun fichier ou dossier de ce type) (8))
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Madison [Mobility Radeon HD 5650/5750 
/ 6530M/6550M] [1002:68c1] (prog-if 00 [VGA controller])
 Subsystem: Sony Corporation Mobility Radeon HD 5650 [104d:9071]
  InstallationDate: Installed on 2016-10-08 (836 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 064e:a213 Suyin Corp. 
   Bus 001 

[Touch-packages] [Bug 1782511] Re: [UX370UAR, Realtek ALC295, Speaker, Internal] No sound at all

2019-01-22 Thread MAI Anh Tuan
It happens on my PC too
Ubuntu 18.04
HP Pavilion Power CB015NF
ALC295

alsa-info : http://www.alsa-
project.org/db/?f=7f12cf628a3c1d6dc471983775b8dc17162b263d

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

Title:
  [UX370UAR, Realtek ALC295, Speaker, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  none

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   ubuntu 2209 F...m pulseaudio
   /dev/snd/pcmC0D0p:   ubuntu 2209 F...m pulseaudio
   /dev/snd/controlC0:  ubuntu 2209 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 18 22:19:23 2018
  InstallationDate: Installed on 2018-07-19 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   ubuntu 2209 F...m pulseaudio
   /dev/snd/pcmC0D0p:   ubuntu 2209 F...m pulseaudio
   /dev/snd/controlC0:  gdm 961 F pulseaudio
ubuntu 2209 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [UX370UAR, Realtek ALC295, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/16/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX370UAR.303
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX370UAR
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX370UAR.303:bd11/16/2017:svnASUSTeKCOMPUTERINC.:pnUX370UAR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX370UAR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX370UAR
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1782511/+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 1782511] Re: [UX370UAR, Realtek ALC295, Speaker, Internal] No sound at all

2019-01-22 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  [UX370UAR, Realtek ALC295, Speaker, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  none

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   ubuntu 2209 F...m pulseaudio
   /dev/snd/pcmC0D0p:   ubuntu 2209 F...m pulseaudio
   /dev/snd/controlC0:  ubuntu 2209 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 18 22:19:23 2018
  InstallationDate: Installed on 2018-07-19 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   ubuntu 2209 F...m pulseaudio
   /dev/snd/pcmC0D0p:   ubuntu 2209 F...m pulseaudio
   /dev/snd/controlC0:  gdm 961 F pulseaudio
ubuntu 2209 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [UX370UAR, Realtek ALC295, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/16/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX370UAR.303
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX370UAR
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX370UAR.303:bd11/16/2017:svnASUSTeKCOMPUTERINC.:pnUX370UAR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX370UAR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX370UAR
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1782511/+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 1812903] Re: Please remove libproxy1-plugin-mozjs/s390x on disco

2019-01-22 Thread Jeremy Bicha
** Package changed: ubuntu => libproxy (Ubuntu)

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

Title:
  Please remove libproxy1-plugin-mozjs/s390x on disco

Status in libproxy package in Ubuntu:
  New

Bug description:
  Please remove the NBS libproxy1-plugiin-mozjs from s390x.

  It does not show up on
  https://people.canonical.com/~ubuntu-archive/nbs.html

  But it does show at
  
https://people.canonical.com/~ubuntu-archive/proposed-migration/disco_uninst.txt

  The binary package is intentionally not built on s390x because mozjs60
  is not available on s390x currently.

  $ rmadison libproxy1-plugin-mozjs
   libproxy1-plugin-mozjs | 0.4.15-3 | disco/universe | s390x
   libproxy1-plugin-mozjs | 0.4.15-5 | disco/universe | amd64, arm64, armhf, 
i386, ppc64el

  $ rmadison libproxy
   libproxy | 0.4.15-2 | cosmic   | source
   libproxy | 0.4.15-5 | disco| source

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libproxy/+bug/1812903/+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 1812903] [NEW] Please remove libproxy1-plugin-mozjs/s390x on disco

2019-01-22 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Please remove the NBS libproxy1-plugiin-mozjs from s390x.

It does not show up on
https://people.canonical.com/~ubuntu-archive/nbs.html

But it does show at
https://people.canonical.com/~ubuntu-archive/proposed-migration/disco_uninst.txt

The binary package is intentionally not built on s390x because mozjs60
is not available on s390x currently.

$ rmadison libproxy1-plugin-mozjs
 libproxy1-plugin-mozjs | 0.4.15-3 | disco/universe | s390x
 libproxy1-plugin-mozjs | 0.4.15-5 | disco/universe | amd64, arm64, armhf, 
i386, ppc64el

$ rmadison libproxy
 libproxy | 0.4.15-2 | cosmic   | source
 libproxy | 0.4.15-5 | disco| source

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


** Tags: bot-comment
-- 
Please remove libproxy1-plugin-mozjs/s390x on disco
https://bugs.launchpad.net/bugs/1812903
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to libproxy in Ubuntu.

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


[Touch-packages] [Bug 1648183] Re: Crackling and popping sound when using headphones

2019-01-22 Thread MAI Anh Tuan
the solution of @robertjjoynt doesn't work on ubuntu 18.04
my pc is HP Pavilion Power 15CB
card 0: PCH [HDA Intel PCH], device 0: ALC295 Analog [ALC295 Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

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

Title:
  Crackling and popping sound when using headphones

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in alsa-driver package in Arch Linux:
  New

Bug description:
  Laptop is  HP Pavilion - 15-au118tx. The laptop has B and O play and
  the output from speakers are just fine, when using headphones there is
  some kind of crackling and popping sound in both ears but prominently
  in the left ear.

  The issue happens only when the sound is played, if i reduce the PCM
  way low using alsamixer, the effect is minimized but the volume is
  also reduced. Increasing the volume in the panel increases the PCM as
  well.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  antony 1719 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Dec  7 23:30:05 2016
  InstallationDate: Installed on 2016-11-20 (17 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Black Headphone Out, Left
  Symptom_Type: Digital clip or distortion, or "overdriven" sound
  Title: [HP Pavilion Notebook, Realtek ALC295, Black Headphone Out, Left] 
Sound is distorted
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/19/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.14
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8216
  dmi.board.vendor: HP
  dmi.board.version: 83.13
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.14:bd07/19/2016:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn8216:rvr83.13:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2016-12-07T23:12:52.939689

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1648183/+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 1812852] Re: package whoopsie 0.2.24.6ubuntu4 failed to install/upgrade: Unterprozess neues pre-removal-Skript gab den Fehlerwert 100 zurück

2019-01-22 Thread Sebastien Bacher
** Changed in: whoopsie (Ubuntu)
   Status: New => Invalid

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

Title:
  package whoopsie 0.2.24.6ubuntu4 failed to install/upgrade:
  Unterprozess neues pre-removal-Skript gab den Fehlerwert 100 zurück

Status in whoopsie package in Ubuntu:
  Invalid

Bug description:
  while i run do-release-upgrade from ubuntu 14.04 it happens

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: whoopsie 0.2.24.6ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: amd64
  CrashReports: 600:0:122:389841:2019-01-22 13:51:23.423334360 +0100:2019-01-22 
13:51:24.423334360 +0100:/var/crash/whoopsie.0.crash
  Date: Tue Jan 22 13:51:24 2019
  Df:
   Dateisystem1K-Blöcke Benutzt Verfügbar Verw% Eingehängt auf
   udev 8147024   0   81470240% /dev
  DpkgTerminalLog: Log started: 2019-01-22  13:15:16
  ErrorMessage: Unterprozess neues pre-removal-Skript gab den Fehlerwert 100 
zurück
  InstallationDate: Installed on 2014-09-09 (1596 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: whoopsie
  Title: package whoopsie 0.2.24.6ubuntu4 failed to install/upgrade: 
Unterprozess neues pre-removal-Skript gab den Fehlerwert 100 zurück
  UpgradeStatus: Upgraded to xenial on 2019-01-22 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1812852/+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 1809827] Re: --add-file broken in bionic

2019-01-22 Thread Brian Murray
Hello Martin, or anyone else affected,

Accepted tar into bionic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/tar/1.29b-2ubuntu0.1
in a few hours, and then in the -proposed repository.

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

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

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: tar (Ubuntu Bionic)
   Status: New => Fix Committed

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

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

Title:
  --add-file broken in bionic

Status in tar package in Ubuntu:
  Fix Released
Status in tar source package in Bionic:
  Fix Committed
Status in tar package in Fedora:
  Unknown

Bug description:
  same error like this one:
  https://bugzilla.redhat.com/show_bug.cgi?id=1436030#c0

  * Impact
  tar supplied in bionic has --add-file option broken.

  * Test case
  Steps to Reproduce:
  1. echo >a.txt
  2. echo >b.txt
  3. tar cf a.tar a.txt
  4. tar rf a.tar --add-file=b.txt

  Actual results:
  tar: unhandled positional option 0

  * Regression potential
  The changes are around an option which isn't working so no much regression 
potential there, check that other options still work though

  
  Is likely fixed by this:
  
http://git.savannah.gnu.org/cgit/tar.git/commit/?id=3a283cfe9f8f1f127e8dc5597a5ea1d249985a54

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

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


[Touch-packages] [Bug 1799014] Re: bold font rendeing in Java is broken in Cosmic with OpenJDK 11

2019-01-22 Thread Tiago Stürmer Daitx
** Also affects: freetype (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

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

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

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

** Changed in: openjdk-lts (Ubuntu)
 Assignee: (unassigned) => Tiago Stürmer Daitx (tdaitx)

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

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

Status in freetype package in Ubuntu:
  Confirmed
Status in openjdk-lts package in Ubuntu:
  Confirmed
Status in freetype source package in Bionic:
  New
Status in openjdk-lts source package in Bionic:
  New
Status in freetype source package in Cosmic:
  New
Status in openjdk-lts source package in Cosmic:
  New
Status in openjdk-11 package in Debian:
  Fix Released

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

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

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


[Touch-packages] [Bug 1812474] Re: /usr/lib/evolution/evolution-addressbook-factory regularly takes 100% CPU and 100% RAM for a while, making all the system unresponsive

2019-01-22 Thread Sebastien Bacher
Thanks!

** Changed in: evolution-data-server (Ubuntu)
   Status: New => Triaged

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

Title:
  /usr/lib/evolution/evolution-addressbook-factory regularly takes 100%
  CPU and 100% RAM for a while, making all the system unresponsive

Status in evolution-data-server package in Ubuntu:
  Triaged

Bug description:
  /usr/lib/evolution/evolution-addressbook-factory regularly takes 100% CPU and 
100% RAM for a while, making all the system unresponsive; the GUI doesn't 
respond (gnome-shell's clock is stopped, the mouse pointer is stopped) and it 
lasts for a few minutes, then goes back to normal.  
  If I wait long enough, the addressbook crashes (not enough memory ?).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: evolution-data-server 3.30.1-1build1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Jan 19 09:59:18 2019
  ExecutablePath: 
/usr/lib/evolution/evolution-data-server/evolution-alarm-notify
  InstallationDate: Installed on 2017-01-09 (740 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  ProcEnviron:
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: evolution-data-server
  UpgradeStatus: Upgraded to cosmic on 2018-10-19 (92 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1812474/+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 1812904] [NEW] [FTBFS] Doesn't compile with gtk-doc >=1.26 (Disco)

2019-01-22 Thread Khurshid Alam
Public bug reported:

Gtkdoc-mktmpl was removed from gtk-doc 1.26. Instead use 
GtkDocConfig.cmake provided by gtk-doc-tools. 

See: https://github.com/GNOME/gtk-
doc/commit/46df4354abed5724697fd5e39630c5bbc6637cc4#diff-
6023128f8e440b483f85968b0db7799e

** Affects: hud (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: disco

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

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

Title:
  [FTBFS] Doesn't compile with gtk-doc >=1.26 (Disco)

Status in hud package in Ubuntu:
  Confirmed

Bug description:
  Gtkdoc-mktmpl was removed from gtk-doc 1.26. Instead use 
  GtkDocConfig.cmake provided by gtk-doc-tools. 

  See: https://github.com/GNOME/gtk-
  doc/commit/46df4354abed5724697fd5e39630c5bbc6637cc4#diff-
  6023128f8e440b483f85968b0db7799e

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hud/+bug/1812904/+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 1771031] Re: Please remove libgnome and friends from Ubuntu

2019-01-22 Thread Jeremy Bicha
Steve said he'd prefer to handle the removals semi-automatically when
they're removed from Debian so I'm closing this bug to not clutter the
Archive Admin bug queue.

** Changed in: libgnome-keyring (Ubuntu)
   Status: New => Invalid

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

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

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

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

Title:
  Please remove libgnome and friends from Ubuntu

Status in gnome-vfs package in Ubuntu:
  Invalid
Status in libbonobo package in Ubuntu:
  Invalid
Status in libbonoboui package in Ubuntu:
  Invalid
Status in libgnome package in Ubuntu:
  Invalid
Status in libgnome-keyring package in Ubuntu:
  Invalid
Status in libgnomeui package in Ubuntu:
  Invalid
Status in linsmith package in Ubuntu:
  Invalid
Status in orbit2 package in Ubuntu:
  Invalid
Status in resapplet package in Ubuntu:
  Fix Released
Status in winefish package in Ubuntu:
  Fix Released

Bug description:
  libgnome has been removed from Debian Testing and will not be included
  in the Debian 10 "Buster" release. We should do the same. If we do it
  now, maybe some projects will do the needed porting work away from
  libgnome (porting to gtk3 is probably needed) in time for Ubuntu 20.04
  LTS or Debian 10. Users who are hurt by these removals can keep using
  Ubuntu 18.04 LTS for a few years.

  resapplet and winefish are unmaintained and aren't in Debian.

  linsmith is in Debian and will be either ported to gtk3 or removed
  eventually, but I don't think Ubuntu needs to wait for that.

  This bug depends on these other removals:
  DONE: gnome-python LP: #1739800
  DONE: gnome-sharp2 LP: #1771025
  DONE: shutter LP: #1771030

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-vfs/+bug/1771031/+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 1771031] Re: Please remove libgnome and friends from Ubuntu

2019-01-22 Thread Steve Langasek
Removing packages from disco:
resapplet 0.0.7+cvs2005.09.30-0ubuntu6 in disco
resapplet 0.0.7+cvs2005.09.30-0ubuntu6 in disco amd64
resapplet 0.0.7+cvs2005.09.30-0ubuntu6 in disco arm64
resapplet 0.0.7+cvs2005.09.30-0ubuntu6 in disco armhf
resapplet 0.0.7+cvs2005.09.30-0ubuntu6 in disco i386
resapplet 0.0.7+cvs2005.09.30-0ubuntu6 in disco ppc64el
resapplet 0.0.7+cvs2005.09.30-0ubuntu6 in disco s390x
Comment: Ubuntu-specific package, depends on obsolete libgnome; LP: #1771031
1 package successfully removed.


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

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

Title:
  Please remove libgnome and friends from Ubuntu

Status in gnome-vfs package in Ubuntu:
  Invalid
Status in libbonobo package in Ubuntu:
  Invalid
Status in libbonoboui package in Ubuntu:
  Invalid
Status in libgnome package in Ubuntu:
  Invalid
Status in libgnome-keyring package in Ubuntu:
  Invalid
Status in libgnomeui package in Ubuntu:
  Invalid
Status in linsmith package in Ubuntu:
  Invalid
Status in orbit2 package in Ubuntu:
  Invalid
Status in resapplet package in Ubuntu:
  Fix Released
Status in winefish package in Ubuntu:
  Fix Released

Bug description:
  libgnome has been removed from Debian Testing and will not be included
  in the Debian 10 "Buster" release. We should do the same. If we do it
  now, maybe some projects will do the needed porting work away from
  libgnome (porting to gtk3 is probably needed) in time for Ubuntu 20.04
  LTS or Debian 10. Users who are hurt by these removals can keep using
  Ubuntu 18.04 LTS for a few years.

  resapplet and winefish are unmaintained and aren't in Debian.

  linsmith is in Debian and will be either ported to gtk3 or removed
  eventually, but I don't think Ubuntu needs to wait for that.

  This bug depends on these other removals:
  DONE: gnome-python LP: #1739800
  DONE: gnome-sharp2 LP: #1771025
  DONE: shutter LP: #1771030

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-vfs/+bug/1771031/+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 1771031] Re: Please remove libgnome and friends from Ubuntu

2019-01-22 Thread Steve Langasek
Removing packages from disco:
winefish 1.3.3-0dl1ubuntu2 in disco
winefish 1.3.3-0dl1ubuntu2 in disco amd64
winefish 1.3.3-0dl1ubuntu2 in disco arm64
winefish 1.3.3-0dl1ubuntu2 in disco armhf
winefish 1.3.3-0dl1ubuntu2 in disco i386
winefish 1.3.3-0dl1ubuntu2 in disco ppc64el
winefish 1.3.3-0dl1ubuntu2 in disco s390x
Comment: Ubuntu-specific package, depends on obsolete libgnome; LP: #1771031
1 package successfully removed.


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

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

Title:
  Please remove libgnome and friends from Ubuntu

Status in gnome-vfs package in Ubuntu:
  Invalid
Status in libbonobo package in Ubuntu:
  Invalid
Status in libbonoboui package in Ubuntu:
  Invalid
Status in libgnome package in Ubuntu:
  Invalid
Status in libgnome-keyring package in Ubuntu:
  Invalid
Status in libgnomeui package in Ubuntu:
  Invalid
Status in linsmith package in Ubuntu:
  Invalid
Status in orbit2 package in Ubuntu:
  Invalid
Status in resapplet package in Ubuntu:
  Fix Released
Status in winefish package in Ubuntu:
  Fix Released

Bug description:
  libgnome has been removed from Debian Testing and will not be included
  in the Debian 10 "Buster" release. We should do the same. If we do it
  now, maybe some projects will do the needed porting work away from
  libgnome (porting to gtk3 is probably needed) in time for Ubuntu 20.04
  LTS or Debian 10. Users who are hurt by these removals can keep using
  Ubuntu 18.04 LTS for a few years.

  resapplet and winefish are unmaintained and aren't in Debian.

  linsmith is in Debian and will be either ported to gtk3 or removed
  eventually, but I don't think Ubuntu needs to wait for that.

  This bug depends on these other removals:
  DONE: gnome-python LP: #1739800
  DONE: gnome-sharp2 LP: #1771025
  DONE: shutter LP: #1771030

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-vfs/+bug/1771031/+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 1804603] Re: systemd-tmpfiles-setup.service fails on btrfs

2019-01-22 Thread Jurit
@Dmitri, Thank you
Do you have any ideas how I can fix this bug without this armbian kernel:
● systemd-tmpfiles-setup-dev.service loaded failed failed Create Static Device 
Nodes in /dev
● systemd-tmpfiles-setup.service loaded failed failed Create Volatile Files and 
Directories

This started after november updates (apt-get update).

I have Ubuntu 18.04.01. LTS  bionic, 
And moreover I dont know this armbian kernel will fix it or not

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

Title:
  systemd-tmpfiles-setup.service fails on btrfs

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released
Status in systemd source package in Cosmic:
  Fix Released
Status in systemd source package in Disco:
  Fix Released

Bug description:
  [Impact]

   * Last security update introduced a regression on btrfs based systems, 
causing systemd-tmpfiles-setup.service to fail to start, resulting in degraded 
machines.
   * Cherrypick upstream fixes to resolve this.

  [Test Case]

   * Install VM using btrfs for /
   * Boot, check that systemd-tmpfiles-setup.service is started successfully 
with:
  $ systemctl status systemd-tmpfiles-setup.service

  [Regression Potential]

   * btrfs fd doesn't support the set of flags that systemd used, with
  this patch, a compat set of flags is set instead, thus resolving the
  introduced regression. The worst case scenario is that creating
  subvolumes/directories is still broken (as in, the current status
  quo).

  [Other Info]
   
   * Example bad output

  
  After update to systemd 237-3ubuntu10.9 systemd-tmpfiles-setup.service fails 
with:

  Nov 21 13:44:12 node-blc49 systemd[1]: Starting Create Volatile Files and 
Directories...
  Nov 21 13:44:12 node-blc49 systemd-tmpfiles[1226]: Failed to create directory 
or subvolume "/var": Bad file descriptor
  Nov 21 13:44:12 node-blc49 systemd-tmpfiles[1226]: Failed to create directory 
or subvolume "/home": Bad file descriptor
  Nov 21 13:44:12 node-blc49 systemd-tmpfiles[1226]: Failed to create directory 
or subvolume "/srv": Bad file descriptor
  Nov 21 13:44:12 node-blc49 systemd[1]: systemd-tmpfiles-setup.service: Main 
process exited, code=exited, status=1/FAILURE
  Nov 21 13:44:12 node-blc49 systemd[1]: systemd-tmpfiles-setup.service: Failed 
with result 'exit-code'.
  Nov 21 13:44:12 node-blc49 systemd[1]: Failed to start Create Volatile Files 
and Directories.

  This happens on btrfs root filesystems in real hardware and on our
  virtualized servers as well. 237-3ubuntu10.6 didnt show this errors
  and going back to 237-3ubuntu10 removes them as well.

  # lsb_release -rd
  Description:Ubuntu 18.04.1 LTS
  Release:18.04

  # apt-cache policy systemd
  systemd:
    Installiert:   237-3ubuntu10.9
    Installationskandidat: 237-3ubuntu10.9
    Versionstabelle:
   *** 237-3ubuntu10.9 500
  500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   237-3ubuntu10 500
  500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1804603/+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 1771031] Re: Please remove libgnome and friends from Ubuntu

2019-01-22 Thread Jeremy Bicha
** Changed in: gnome-vfs (Ubuntu)
   Status: New => Invalid

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

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

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

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

Title:
  Please remove libgnome and friends from Ubuntu

Status in gnome-vfs package in Ubuntu:
  Invalid
Status in libbonobo package in Ubuntu:
  Invalid
Status in libbonoboui package in Ubuntu:
  Invalid
Status in libgnome package in Ubuntu:
  Invalid
Status in libgnome-keyring package in Ubuntu:
  Invalid
Status in libgnomeui package in Ubuntu:
  Invalid
Status in linsmith package in Ubuntu:
  Invalid
Status in orbit2 package in Ubuntu:
  Invalid
Status in resapplet package in Ubuntu:
  Fix Released
Status in winefish package in Ubuntu:
  Fix Released

Bug description:
  libgnome has been removed from Debian Testing and will not be included
  in the Debian 10 "Buster" release. We should do the same. If we do it
  now, maybe some projects will do the needed porting work away from
  libgnome (porting to gtk3 is probably needed) in time for Ubuntu 20.04
  LTS or Debian 10. Users who are hurt by these removals can keep using
  Ubuntu 18.04 LTS for a few years.

  resapplet and winefish are unmaintained and aren't in Debian.

  linsmith is in Debian and will be either ported to gtk3 or removed
  eventually, but I don't think Ubuntu needs to wait for that.

  This bug depends on these other removals:
  DONE: gnome-python LP: #1739800
  DONE: gnome-sharp2 LP: #1771025
  DONE: shutter LP: #1771030

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-vfs/+bug/1771031/+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 952546] Re: nautilus crashed with SIGSEGV in _gdk_device_xi2_reset_scroll_valuators()

2019-01-22 Thread Bruce Pieterse
This bug report was reported against a really old version of GTK. The
source code has changed quite a bit since then.

If you still receive this bug in newer versions of Ubuntu, please
consider a filing a new bug report.

** Changed in: gtk+3.0 (Ubuntu)
   Status: Triaged => Invalid

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

Title:
  nautilus crashed with SIGSEGV in
  _gdk_device_xi2_reset_scroll_valuators()

Status in GTK+:
  Expired
Status in gtk+3.0 package in Ubuntu:
  Invalid

Bug description:
  A bug, I don't why it happens, I am not sure, but I think it occured
  after I tried to open a .doc file in LibreOffice 3.5 .

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: nautilus 1:3.3.91-0ubuntu4
  ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9
  Uname: Linux 3.2.0-18-generic x86_64
  ApportVersion: 1.94.1-0ubuntu2
  Architecture: amd64
  CheckboxSubmission: eaa7960ea592567b714ca16e1e8e0382
  CheckboxSystem: da9af3b901b5569a389df6337f3d812f
  CrashCounter: 1
  Date: Sun Mar 11 23:11:26 2012
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   org.gnome.nautilus.window-state geometry '960x1024+0+26'
   org.gnome.nautilus.window-state start-with-status-bar true
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  ProcCmdline: nautilus -n
  SegvAnalysis:
   Segfault happened at: 0x7f276388df90:mov0x70(%rdi),%rdx
   PC (0x7f276388df90) ok
   source "0x70(%rdi)" (0x0070) not located in a known VMA region (needed 
readable region)!
   destination "%rdx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
   gdk_display_get_event () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: nautilus crashed with SIGSEGV in gdk_display_get_event()
  UpgradeStatus: Upgraded to precise on 2012-03-11 (0 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/952546/+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 1812886] Re: gnome-software cannot find libreoffice-base when libreoffice-writer requests to install it

2019-01-22 Thread Olivier Tilloy
*** This bug is a duplicate of bug 1790294 ***
https://bugs.launchpad.net/bugs/1790294

** This bug has been marked a duplicate of bug 1790294
   Tools=>Bibliography launches Software Centre but fails to find 
"libreoffice-base" package

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

Title:
  gnome-software cannot find libreoffice-base when libreoffice-writer
  requests to install it

Status in gnome-software package in Ubuntu:
  New
Status in packagekit package in Ubuntu:
  New

Bug description:
  Steps:
  1. Make sure LibreOffice Base is not installed
  2. Start LibreOffice Writer
  2. Choose Tools -> Bibliography Database
  3. Writer asks to install missing software
  4. Click on the notification

  Expected results:
  gnome-software finds libreoffice-base and able to install it

  Actual result:
  gnome-software fails to find the missing software

  See the attached screencast.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-software 3.28.1-0ubuntu4.18.04.4
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 22 17:50:55 2019
  InstallationDate: Installed on 2018-11-29 (53 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.28.1-0ubuntu4.18.04.4
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1812886/+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 1812886] [NEW] gnome-software cannot find libreoffice-base when libreoffice-writer requests to install it

2019-01-22 Thread Amr Ibrahim
Public bug reported:

Steps:
1. Make sure LibreOffice Base is not installed
2. Start LibreOffice Writer
2. Choose Tools -> Bibliography Database
3. Writer asks to install missing software
4. Click on the notification

Expected results:
gnome-software finds libreoffice-base and able to install it

Actual result:
gnome-software fails to find the missing software

See the attached screencast.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-software 3.28.1-0ubuntu4.18.04.4
ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
Uname: Linux 4.15.0-43-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Jan 22 17:50:55 2019
InstallationDate: Installed on 2018-11-29 (53 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
InstalledPlugins:
 gnome-software-plugin-flatpak N/A
 gnome-software-plugin-limba   N/A
 gnome-software-plugin-snap3.28.1-0ubuntu4.18.04.4
SourcePackage: gnome-software
UpgradeStatus: No upgrade log present (probably fresh install)

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

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


** Tags: amd64 apport-bug bionic

** Attachment added: "gnome-software_fails_missing-software.webm"
   
https://bugs.launchpad.net/bugs/1812886/+attachment/5231509/+files/gnome-software_fails_missing-software.webm

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

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

Title:
  gnome-software cannot find libreoffice-base when libreoffice-writer
  requests to install it

Status in gnome-software package in Ubuntu:
  New
Status in packagekit package in Ubuntu:
  New

Bug description:
  Steps:
  1. Make sure LibreOffice Base is not installed
  2. Start LibreOffice Writer
  2. Choose Tools -> Bibliography Database
  3. Writer asks to install missing software
  4. Click on the notification

  Expected results:
  gnome-software finds libreoffice-base and able to install it

  Actual result:
  gnome-software fails to find the missing software

  See the attached screencast.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-software 3.28.1-0ubuntu4.18.04.4
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 22 17:50:55 2019
  InstallationDate: Installed on 2018-11-29 (53 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.28.1-0ubuntu4.18.04.4
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1812886/+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 1560286] Re: Evince displays pdf file fine, but prints colors inverted

2019-01-22 Thread Brian Murray
Hello Staten, or anyone else affected,

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

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

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

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: cairo (Ubuntu Bionic)
   Status: New => Fix Committed

** Tags added: verification-needed-bionic

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

Title:
  Evince displays pdf file fine, but prints colors inverted

Status in cairo package in Ubuntu:
  Fix Released
Status in cairo source package in Bionic:
  Fix Committed
Status in cairo source package in Cosmic:
  Fix Committed

Bug description:
  * Impact
  In some files images are printed with inverted colors

  * Test case
  open 
https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/1560286/+attachment/5226857/+files/978-1-57896-287-7%20LL4%20SW%20Sem%201%20Reduced%20p.17.pdf
 in evince, click on the print preview, the colors should be right

  * Regression potential
  it's a change in the code dealing with specific adobe file, test opening the 
example in different document viewer and try with some other files (the bug has 
several example), they should display the correct image/colors

  

  I have several pdf files that when opened by evince, they appear to be fine 
until I try to print them.  When I do, they print with the colors inverted (the 
printout looks like a photograph negative).  This color inversion also occurs 
when viewed in the print preview screen.  If I click on File > Properties, I 
get some information...
  Producer : Adobe Acrobat 15.10 Image Conversion Plug-in
  Creator : Adobe Acrobat 15.10
  ...
  Format : PDF-1.6
  ...

  I am running ubuntu 14.04 LTS

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: evince 3.10.3-0ubuntu10.2
  ProcVersionSignature: Ubuntu 3.13.0-83.127-generic 3.13.11-ckt35
  Uname: Linux 3.13.0-83-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar 21 21:01:45 2016
  ExecutablePath: /usr/bin/evince
  InstallationDate: Installed on 2012-07-24 (1336 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: Upgraded to trusty on 2014-09-29 (539 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/1560286/+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 1812353] Re: content injection in http method (CVE-2019-3462)

2019-01-22 Thread Ubuntu Foundations Team Bug Bot
** Tags added: patch

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

Title:
  content injection in http method (CVE-2019-3462)

Status in apt package in Ubuntu:
  In Progress
Status in apt source package in Precise:
  Fix Released
Status in apt source package in Trusty:
  Fix Released
Status in apt source package in Xenial:
  Fix Released
Status in apt source package in Bionic:
  Fix Released
Status in apt source package in Cosmic:
  Fix Released
Status in apt source package in Disco:
  In Progress

Bug description:
  apt, starting with version 0.8.15, decodes target URLs of redirects,
  but does not check them for newlines, allowing MiTM attackers (or
  repository mirrors) to inject arbitrary headers into the result
  returned to the main process.

  If the URL embeds hashes of the supposed file, it can thus be used to
  disable any validation of the downloaded file, as the fake hashes will
  be prepended in front of the right hashes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1812353/+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 1560286] Re: Evince displays pdf file fine, but prints colors inverted

2019-01-22 Thread Brian Murray
Hello Staten, or anyone else affected,

Accepted cairo into cosmic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/cairo/1.15.12-1ubuntu0.1 in a few
hours, and then in the -proposed repository.

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

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

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: cairo (Ubuntu Cosmic)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-cosmic

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

Title:
  Evince displays pdf file fine, but prints colors inverted

Status in cairo package in Ubuntu:
  Fix Released
Status in cairo source package in Bionic:
  Fix Committed
Status in cairo source package in Cosmic:
  Fix Committed

Bug description:
  * Impact
  In some files images are printed with inverted colors

  * Test case
  open 
https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/1560286/+attachment/5226857/+files/978-1-57896-287-7%20LL4%20SW%20Sem%201%20Reduced%20p.17.pdf
 in evince, click on the print preview, the colors should be right

  * Regression potential
  it's a change in the code dealing with specific adobe file, test opening the 
example in different document viewer and try with some other files (the bug has 
several example), they should display the correct image/colors

  

  I have several pdf files that when opened by evince, they appear to be fine 
until I try to print them.  When I do, they print with the colors inverted (the 
printout looks like a photograph negative).  This color inversion also occurs 
when viewed in the print preview screen.  If I click on File > Properties, I 
get some information...
  Producer : Adobe Acrobat 15.10 Image Conversion Plug-in
  Creator : Adobe Acrobat 15.10
  ...
  Format : PDF-1.6
  ...

  I am running ubuntu 14.04 LTS

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: evince 3.10.3-0ubuntu10.2
  ProcVersionSignature: Ubuntu 3.13.0-83.127-generic 3.13.11-ckt35
  Uname: Linux 3.13.0-83-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar 21 21:01:45 2016
  ExecutablePath: /usr/bin/evince
  InstallationDate: Installed on 2012-07-24 (1336 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: Upgraded to trusty on 2014-09-29 (539 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/1560286/+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 1763628] Re: autopkgtests are failing on valgrind

2019-01-22 Thread Jeremy Bicha
I asked bdmurray in #ubuntu-devel and he'd rather not have an SRU just
to fix an autopkgtest like this.

I'm closing since this issue is fixed in the current development
release.

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

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

Title:
  autopkgtests are failing on valgrind

Status in colord package in Ubuntu:
  Fix Released

Bug description:
  This happens now

  autopkgtest [07:42:07]: test make-check: ---]
  autopkgtest [07:42:08]: test make-check:  - - - - - - - - - - results - - - - 
- - - - - -
  make-check   FAIL stderr: ==9257== 8 bytes in 1 blocks are definitely 
lost in loss record 67 of 368
  autopkgtest [07:42:08]: test make-check:  - - - - - - - - - - stderr - - - - 
- - - - - -
  ==9257== 8 bytes in 1 blocks are definitely lost in loss record 67 of 368
  ==9257==at 0x4C2FB0F: malloc (in 
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
  ==9257==by 0x18EF2D: xmalloc (in /bin/bash)
  ==9257==by 0x18898A: set_default_locale (in /bin/bash)
  ==9257==by 0x137E66: main (in /bin/bash)
  ==9257== 
  ==9505== 8 bytes in 1 blocks are definitely lost in loss record 67 of 368
  ==9505==at 0x4C2FB0F: malloc (in 
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
  ==9505==by 0x18EF2D: xmalloc (in /bin/bash)
  ==9505==by 0x18898A: set_default_locale (in /bin/bash)
  ==9505==by 0x137E66: main (in /bin/bash)
  ==9505== 
  autopkgtest [07:42:08]:  summary
  make-check   FAIL stderr: ==9257== 8 bytes in 1 blocks are definitely 
lost in loss record 67 of 368

  From http://autopkgtest.ubuntu.com/packages/c/colord/bionic/amd64 it
  looks like it's cause by the new glib2.0, but I just tried on my
  machine without that package and it still happened.

  Could you have a look please? Looks like it might not actually be
  colord's fault here, but maybe we want to reconsider running under
  valgrind at least for the autopktests?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/colord/+bug/1763628/+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 1812750] Re: Python stack trace when running `ubuntu-bug nautilus` in disco

2019-01-22 Thread Sebastien Bacher
Thank you for your bug report, I can't confirm the issue here, unsure
what's different between those installations though

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

Title:
  Python stack trace when running `ubuntu-bug nautilus` in disco

Status in apport package in Ubuntu:
  New

Bug description:
  ERROR: hook /usr/share/apport/package-hooks/source_nautilus.py crashed:
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport/report.py", line 205, in 
_run_hook
  symb['add_info'](report, ui)
  TypeError: add_info() takes 1 positional argument but 2 were given

  During handling of the above exception, another exception occurred:

  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport/report.py", line 210, in 
_run_hook
  symb['add_info'](report)
File "/usr/share/apport/package-hooks/source_nautilus.py", line 23, in 
add_info
  report["usr_lib_nautilus"] = package_versions(*sorted(plugin_packages))
  TypeError: '<' not supported between instances of 'NoneType' and 'str'

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: apport 2.20.10-0ubuntu19
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu19
  Architecture: amd64
  CrashReports:
   640:0:119:606530:2019-01-21 14:49:01.440511009 -0500:2019-01-21 
14:49:01.136510154 
-0500:/var/crash/_opt_penguindome_client_client-cron.py.0.crash
   640:0:119:2444106:2019-01-21 14:54:50.761487081 -0500:2019-01-21 
14:54:48.449619152 -0500:/var/crash/_usr_lib_packagekit_packagekitd.0.crash
   640:1000:119:3237446:2019-01-21 14:54:03.516504591 -0500:2019-01-21 
14:54:00.808239070 -0500:/var/crash/_usr_lib_tracker_tracker-extract.1000.crash
   640:1000:119:4471123:2019-01-21 15:43:11.507506447 -0500:2019-01-21 
15:43:07.863473435 -0500:/var/crash/_usr_bin_nautilus.1000.crash
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 21 15:55:09 2019
  InstallationDate: Installed on 2019-01-02 (19 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to disco on 2019-01-21 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1812750/+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 1812353] Re: content injection in http method (CVE-2019-3462)

2019-01-22 Thread Marc Deslauriers
** Changed in: apt (Ubuntu Precise)
   Status: New => 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/1812353

Title:
  content injection in http method (CVE-2019-3462)

Status in apt package in Ubuntu:
  In Progress
Status in apt source package in Precise:
  Fix Released
Status in apt source package in Trusty:
  Fix Released
Status in apt source package in Xenial:
  Fix Released
Status in apt source package in Bionic:
  Fix Released
Status in apt source package in Cosmic:
  Fix Released
Status in apt source package in Disco:
  In Progress

Bug description:
  apt, starting with version 0.8.15, decodes target URLs of redirects,
  but does not check them for newlines, allowing MiTM attackers (or
  repository mirrors) to inject arbitrary headers into the result
  returned to the main process.

  If the URL embeds hashes of the supposed file, it can thus be used to
  disable any validation of the downloaded file, as the fake hashes will
  be prepended in front of the right hashes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1812353/+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 1812474] Re: /usr/lib/evolution/evolution-addressbook-factory regularly takes 100% CPU and 100% RAM for a while, making all the system unresponsive

2019-01-22 Thread Xavier Bestel
Done: https://gitlab.gnome.org/GNOME/evolution-data-server/issues/78

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

Title:
  /usr/lib/evolution/evolution-addressbook-factory regularly takes 100%
  CPU and 100% RAM for a while, making all the system unresponsive

Status in evolution-data-server package in Ubuntu:
  New

Bug description:
  /usr/lib/evolution/evolution-addressbook-factory regularly takes 100% CPU and 
100% RAM for a while, making all the system unresponsive; the GUI doesn't 
respond (gnome-shell's clock is stopped, the mouse pointer is stopped) and it 
lasts for a few minutes, then goes back to normal.  
  If I wait long enough, the addressbook crashes (not enough memory ?).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: evolution-data-server 3.30.1-1build1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Jan 19 09:59:18 2019
  ExecutablePath: 
/usr/lib/evolution/evolution-data-server/evolution-alarm-notify
  InstallationDate: Installed on 2017-01-09 (740 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  ProcEnviron:
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: evolution-data-server
  UpgradeStatus: Upgraded to cosmic on 2018-10-19 (92 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1812474/+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 1811930] Re: package unattended-upgrades 1.1ubuntu1.18.04.8 failed to install/upgrade: installed unattended-upgrades package post-installation script subprocess returned error ex

2019-01-22 Thread Balint Reczey
Thank you for the bug report. I tried to reproduce the problem but could
not and I suspect it is caused by an other issue with the system.

In .var.log.apt.history.log.txt i see dpkg starting to fail earlier:
...
Start-Date: 2019-01-15  10:10:08
Commandline: apt-get install apache2
Requested-By: lenovo (1000)
Install: apache2:amd64 (2.4.29-1ubuntu4.5)
Error: Sub-process /usr/bin/dpkg returned an error code (1)
End-Date: 2019-01-15  10:10:23
...

If you have more information on how the issue can be reproduced on a
clean system please share it in this bug report.

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

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

Title:
  package unattended-upgrades 1.1ubuntu1.18.04.8 failed to
  install/upgrade: installed unattended-upgrades package post-
  installation script subprocess returned error exit status 10

Status in unattended-upgrades package in Ubuntu:
  Incomplete

Bug description:
  this error occoured while upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: unattended-upgrades 1.1ubuntu1.18.04.8
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Wed Jan 16 11:53:24 2019
  DuplicateSignature:
   package:unattended-upgrades:1.1ubuntu1.18.04.8
   Setting up unattended-upgrades (1.1ubuntu1.18.04.8) ...
   dpkg: error processing package unattended-upgrades (--configure):
installed unattended-upgrades package post-installation script subprocess 
returned error exit status 10
  ErrorMessage: installed unattended-upgrades package post-installation script 
subprocess returned error exit status 10
  InstallationDate: Installed on 2018-12-06 (40 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.7, unpackaged
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, unpackaged
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.6
  SourcePackage: unattended-upgrades
  Title: package unattended-upgrades 1.1ubuntu1.18.04.8 failed to 
install/upgrade: installed unattended-upgrades package post-installation script 
subprocess returned error exit status 10
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1811930/+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 1812867] Re: sound from bluetooth device is like vintage when quiting the hibernate

2019-01-22 Thread fossfreedom
** Also affects: bluez (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  sound from bluetooth device is like vintage when quiting the hibernate

Status in Ubuntu Budgie:
  New
Status in bluez package in Ubuntu:
  New

Bug description:
  Hi
  I've just noticed this today, with my laptop and my desktop, both under 
Ubuntu Budgie 18.10, all last updates installed if it can help you. Using a USB 
Bluetooth key for both

  After using my wireless speaker (JBL GO for more precision if it's
  needed) within Bluetooth, I lock my computer when I leave my office.
  then I unlock my computer when I'm back to.

  Wanna play some music on the said device. Then I start to play
  music... with somewhat vintage effect on the sound.

  I shutdown the device, start it up and same thing.

  To get a working properly BT, I have to

  - unplug and plug the USB BT key
  - middle click two time on the Bluetooth logo at the top, likely to disable / 
enable it

  and then it work like a charm.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntubudgie/+bug/1812867/+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 1560286] Re: Evince displays pdf file fine, but prints colors inverted

2019-01-22 Thread Sebastien Bacher
The issue is fixed in 1.16 in disco, SRUs have been uploaded to cosmic &
bionic

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

Title:
  Evince displays pdf file fine, but prints colors inverted

Status in cairo package in Ubuntu:
  Fix Released

Bug description:
  * Impact
  In some files images are printed with inverted colors

  * Test case
  open 
https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/1560286/+attachment/5226857/+files/978-1-57896-287-7%20LL4%20SW%20Sem%201%20Reduced%20p.17.pdf
 in evince, click on the print preview, the colors should be right

  * Regression potential
  it's a change in the code dealing with specific adobe file, test opening the 
example in different document viewer and try with some other files (the bug has 
several example), they should display the correct image/colors

  

  I have several pdf files that when opened by evince, they appear to be fine 
until I try to print them.  When I do, they print with the colors inverted (the 
printout looks like a photograph negative).  This color inversion also occurs 
when viewed in the print preview screen.  If I click on File > Properties, I 
get some information...
  Producer : Adobe Acrobat 15.10 Image Conversion Plug-in
  Creator : Adobe Acrobat 15.10
  ...
  Format : PDF-1.6
  ...

  I am running ubuntu 14.04 LTS

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: evince 3.10.3-0ubuntu10.2
  ProcVersionSignature: Ubuntu 3.13.0-83.127-generic 3.13.11-ckt35
  Uname: Linux 3.13.0-83-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar 21 21:01:45 2016
  ExecutablePath: /usr/bin/evince
  InstallationDate: Installed on 2012-07-24 (1336 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: Upgraded to trusty on 2014-09-29 (539 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/1560286/+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 1762391] Re: pam_group.so is not evaluated by gnome-terminal

2019-01-22 Thread Jeremy Bicha
** No longer affects: gnome-terminal (Ubuntu Bionic)

** No longer affects: gnome-terminal (Ubuntu Cosmic)

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

Title:
  pam_group.so is not evaluated by gnome-terminal

Status in systemd:
  New
Status in gnome-terminal package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  New
Status in systemd source package in Bionic:
  New
Status in systemd source package in Cosmic:
  New

Bug description:
  We are using Ubuntu in a university network with lots of ldap users.
  To automatically map ldap users/groups to local groups we are using
  pam_group.so. This has worked for years.

  With the upgrade from Xenial to Bionic /etc/security/group.conf is not
  evaluated anymore by gnome-terminal as it runs as systemd --user.
  Xterm, ssh, su, and tty* however do work as expected. Only the default
  gnome-terminal behaves different.

  According to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851243
  and https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756458 this
  might not be a bug, but a feature.

  Nevertheless this behavior is very unexpected when upgrading from
  Xenial to Bionic and therefore should at least added to the changelog.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-terminal 3.28.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  9 13:17:52 2018
  InstallationDate: Installed on 2018-03-29 (11 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180321)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1762391/+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 1770271] Re: VegaM support

2019-01-22 Thread Timo Aaltonen
mesa 18.2.x is in bionic-proposed

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

Title:
  VegaM support

Status in amd:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Won't Fix
Status in mesa source package in Xenial:
  Won't Fix
Status in linux source package in Bionic:
  New
Status in mesa source package in Bionic:
  Fix Committed

Bug description:
  VegaM is a new GPU.  Please include support for VegaM in the next LTS
  (16.04.x and 18.04.x) and non-LTS releases.

  Kernel support starts here (32 patches):
  https://patchwork.freedesktop.org/patch/218839/

  Mesa support:
  
https://cgit.freedesktop.org/mesa/mesa/commit/?id=d6a66bc8dbcdeed8e87f649bc281de0d60d2f123
  
https://cgit.freedesktop.org/mesa/mesa/commit/?id=c6f1d360198c52d208645c0ccb5e988cded408e8
  
https://cgit.freedesktop.org/mesa/mesa/commit/?id=90de03708fa269ad54de881b467f4811e4eef87e

To manage notifications about this bug go to:
https://bugs.launchpad.net/amd/+bug/1770271/+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 1452239] Re: root escalation with fs.suid_dumpable=2

2019-01-22 Thread Carlos D. Gonzalez
In Bionic, when apport is enabled fs.suid_dumpable will be set to 2, no
matters what you try to set it up using sysctl. Is this the same issue?

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

Title:
  root escalation with fs.suid_dumpable=2

Status in Apport:
  Fix Released
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Precise:
  Fix Released
Status in apport source package in Trusty:
  Fix Released
Status in apport source package in Utopic:
  Fix Released
Status in apport source package in Vivid:
  Fix Released
Status in apport source package in Wily:
  Fix Released

Bug description:
  Sander Bos discovered that Apport enabled a user to perform a root
  escalation since it now configures fs.suid_dumpable=2.

  Here's a brief description of the issue:
  1- A regular user can trigger a coredump with /proc/$PID/stat as root:root 
simply by doing chmod u-r
  2- The root-owned coredump will then be written in the CWD, which in the PoC 
is /etc/logrotate.d
  3- logrotate will gladly skip parts of the coredump it doesn't understand and 
will successfully run the parts it does

  I've set a CRD of 2015-05-21 (original proposal: 2015-05-12) for the
  publication of this issue.

  I have assigned CVE-2015-1324 to this issue.

  We can either:

  1- Disable fs.suid_dumpable=2
  2- Stop creating core dump files when they are to be created as root
  3- Create root-owned core dump files in a well-known location

  

  Here is the original report from Sander Bos (now with the CVE number
  included):

  OVERVIEW
  

  Date: 2015-05-05
  Bug name: SCORE: Simple Coredump-Oriented Root Exploit
  CVE: CVE-2015-1324
  Author: Sander Bos
  Author's e-mail address: sbos _at_ sbosnet _dot_ nl

  SUMMARY
  ---

  I found a combination of vulnerabilities to lead to privilege escalation
  (root exploitation) by local users in Ubuntu releases 12.04 up to and
  including 15.04.  Depending on configuration, remote exploitation might
  be possible as well.  Local exploitation can even be done as the local,
  passwordless LightDM "Guest" account user on systems supporting it --
  indeed: from anonymous guest user to root.

  DESCRIPTION
  ---

  The Apport package creates user core dumps in the crashed process'
  CWD, and does so since Bazaar revision number 602 [1] / release 0.59.
  This is okay, but not always: there is a flaw in the fact that Apport
  also does this, as root, for tainted/protected binaries (setuid() and
  friends, capabilities(7) enabled binaries, non-readable binaries) when
  the sysctl(8)'s fs.suid_dumpable variable is set to 2 (see core(5)).
  This means that users can create core dumps as root, in arbitrary
  directories which are otherwise write-protected for those users.

  In short: Apport should _not_ create user core dumps in the CWD in dump
  mode 2 for such tainted binaries; it should either not make user core
  dumps at all then, or if possible use a designated and safe directory
  for that.

  All Ubuntu releases starting with 12.04 have the Apport service enabled by
  default [2] (and Ubuntu has Apport installed by default for much longer).

  All Ubuntu releases starting with 12.04 (or patched that way after
  their release) have sysctl(8)'s fs.suid_dumpable set to 2 by default,
  through the Apport package; see bug #1194541, "Create core dumps for
  setuid binaries", 2013-06-25 [3].

  Along with solving that bug (that is, adding the "missing feature" of
  setuid core dumps), the patch to that bug report actually created a root
  exploit hole in the upcoming release 13.10, as well as being backported
  into the at that time supported Ubuntu releases 12.04, 12.10 and 13.04.

  The exact Apport package versions (with their Ubuntu releases) that were
  "patched" to have fs.suid_dumpable set to "2"  are:

  2.0.1-0ubuntu17.4 (Ubuntu 12.04)
  2.6.1-0ubuntu12   (Ubuntu 12.10)
  2.9.2-0ubuntu8.3  (Ubuntu 13.04)

  The value fs.suid_dumpable=2 remained in Ubuntu ever since.  The exception
  to this is the systemd Apport script in Ubuntu 15.04: the option setting
  fs.suid_dumpable to "2" was forgotten to be enabled here, although in the
  Upstart script in Ubuntu 15.04 the option is still enabled.  I recently
  contacted the Apport package maintainer to make sure the systemd script
  will not enable the option, as that would enable the root hole in 15.04
  with systemd (which is the default init system) as well.  Please note:
  15.04 with systemd being safe regarding this vulnerabilty has nothing
  to do with systemd itself.

  Please note that even though Ubuntu has the value of fs.suid_dumpable set
  to 2 in releases 12.04 and later, Apport itself has been creating user
  coredumps (to CWD, and also with fs.suid_dumpable=2) since Ubuntu 7.04,
  which has Apport package release 0.76/0.76.1.  Any system s

[Touch-packages] [Bug 1812507] Re: Typo in description of snap

2019-01-22 Thread Alfonso Sanchez-Beato
Changed now, thanks!

** Changed in: network-manager (Ubuntu)
   Status: New => Fix Released

** Changed in: network-manager (Ubuntu)
 Assignee: (unassigned) => Alfonso Sanchez-Beato (alfonsosanchezbeato)

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

Title:
  Typo in description of snap

Status in network-manager package in Ubuntu:
  Fix Released

Bug description:
  https://snapcraft.io/network-manager lists the description for
  NetworkManager as “Network management based on NeworkManager” (sic).

  NeworkManager should be NetworkManager.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1812507/+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 1560286] Re: Evince displays pdf file fine, but prints colors inverted

2019-01-22 Thread Sebastien Bacher
** Description changed:

+ * Impact
+ In some files images are printed with inverted colors
+ 
+ * Test case
+ open 
https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/1560286/+attachment/5226857/+files/978-1-57896-287-7%20LL4%20SW%20Sem%201%20Reduced%20p.17.pdf
 in evince, click on the print preview, the colors should be right
+ 
+ * Regression potential
+ it's a change in the code dealing with specific adobe file, test opening the 
example in different document viewer and try with some other files (the bug has 
several example), they should display the correct image/colors
+ 
+ 
+ 
  I have several pdf files that when opened by evince, they appear to be fine 
until I try to print them.  When I do, they print with the colors inverted (the 
printout looks like a photograph negative).  This color inversion also occurs 
when viewed in the print preview screen.  If I click on File > Properties, I 
get some information...
  Producer : Adobe Acrobat 15.10 Image Conversion Plug-in
  Creator : Adobe Acrobat 15.10
  ...
  Format : PDF-1.6
  ...
  
  I am running ubuntu 14.04 LTS
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: evince 3.10.3-0ubuntu10.2
  ProcVersionSignature: Ubuntu 3.13.0-83.127-generic 3.13.11-ckt35
  Uname: Linux 3.13.0-83-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar 21 21:01:45 2016
  ExecutablePath: /usr/bin/evince
  InstallationDate: Installed on 2012-07-24 (1336 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  ProcEnviron:
-  LANGUAGE=en_US
-  PATH=(custom, user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  LANGUAGE=en_US
+  PATH=(custom, user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: Upgraded to trusty on 2014-09-29 (539 days ago)

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

Title:
  Evince displays pdf file fine, but prints colors inverted

Status in cairo package in Ubuntu:
  Fix Committed

Bug description:
  * Impact
  In some files images are printed with inverted colors

  * Test case
  open 
https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/1560286/+attachment/5226857/+files/978-1-57896-287-7%20LL4%20SW%20Sem%201%20Reduced%20p.17.pdf
 in evince, click on the print preview, the colors should be right

  * Regression potential
  it's a change in the code dealing with specific adobe file, test opening the 
example in different document viewer and try with some other files (the bug has 
several example), they should display the correct image/colors

  

  I have several pdf files that when opened by evince, they appear to be fine 
until I try to print them.  When I do, they print with the colors inverted (the 
printout looks like a photograph negative).  This color inversion also occurs 
when viewed in the print preview screen.  If I click on File > Properties, I 
get some information...
  Producer : Adobe Acrobat 15.10 Image Conversion Plug-in
  Creator : Adobe Acrobat 15.10
  ...
  Format : PDF-1.6
  ...

  I am running ubuntu 14.04 LTS

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: evince 3.10.3-0ubuntu10.2
  ProcVersionSignature: Ubuntu 3.13.0-83.127-generic 3.13.11-ckt35
  Uname: Linux 3.13.0-83-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar 21 21:01:45 2016
  ExecutablePath: /usr/bin/evince
  InstallationDate: Installed on 2012-07-24 (1336 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: Upgraded to trusty on 2014-09-29 (539 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/1560286/+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 384411] Re: using openGL cairo is very unstable in Karmic

2019-01-22 Thread Sebastien Bacher
there has been no activity/report in years, closing

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

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

Title:
  using openGL cairo is very unstable in Karmic

Status in cairo package in Ubuntu:
  Invalid

Bug description:
  I'm testing Karmic 2.6.30-8 on Asus A8Le with Intel Corporation Mobile 
GM965/GL960 Integrated Graphics Controller.
  I enabled UXA. After starting cairo in openGL mode, it works faster but often 
crashes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/384411/+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 971900] Re: indicator-applet-complete crashed with SIGABRT in __assert_fail_base()

2019-01-22 Thread Sebastien Bacher
there has been no activity/reports in years, closing

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

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

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

Title:
  indicator-applet-complete crashed with SIGABRT in __assert_fail_base()

Status in cairo package in Ubuntu:
  Invalid
Status in libx11 package in Ubuntu:
  Invalid

Bug description:
  indicator-applet-complete crashed with SIGABRT in raise()

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: indicator-applet-complete 0.4.92-0ubuntu3
  ProcVersionSignature: Ubuntu 3.2.0-20.33-generic-pae 3.2.12
  Uname: Linux 3.2.0-20-generic-pae i686
  ApportVersion: 2.0-0ubuntu2
  Architecture: i386
  CrashCounter: 1
  Date: Mon Apr  2 23:01:01 2012
  ExecutablePath: /usr/lib/indicator-applet/indicator-applet-complete
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20120318)
  ProcCmdline: /usr/lib/indicator-applet/indicator-applet-complete
  ProcEnviron:
   SHELL=/bin/bash
   LANG=es_ES.UTF-8
  Signal: 6
  SourcePackage: indicator-applet
  Title: indicator-applet-complete crashed with SIGABRT in raise()
  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/cairo/+bug/971900/+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 1026338] Re: PDF font substitution error, libcairo 1.12

2019-01-22 Thread Sebastien Bacher
Upstream closed it as not being a bug, see their comments for the
details

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

** Also affects: cairo via
   https://bugs.freedesktop.org/show_bug.cgi?id=52280
   Importance: Unknown
   Status: Unknown

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

Title:
  PDF font substitution error, libcairo 1.12

Status in cairo:
  Unknown
Status in cairo package in Ubuntu:
  Invalid

Bug description:
  When using pdftocairo 0.20.x from http://packages.ubuntu.com/quantal
  /poppler-utils , embedded custom encoded Helvetica fonts are not
  carried over from original to new PDFs: it gets substituted as
  NimbusSanL . Using pdftocairo 0.18.4 with libcairo 1.12, the error
  remains; restoring libcairo 1.10 reverts the error.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cairo/+bug/1026338/+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 1806532] Re: The line-out on the Dell Dock station can't work

2019-01-22 Thread Sebastien Bacher
** Changed in: alsa-lib (Ubuntu Bionic)
   Status: Incomplete => Fix Committed

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

Title:
  The line-out on the Dell Dock station can't work

Status in HWE Next:
  New
Status in alsa-lib package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem package in Ubuntu:
  Fix Released
Status in alsa-lib source package in Bionic:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in linux-oem source package in Bionic:
  New
Status in alsa-lib source package in Cosmic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Committed
Status in linux-oem source package in Cosmic:
  New

Bug description:
  [Impact]
  On the Dell thunderbolt docs stations (WD15 and WD19), there are two playback
  devices, one is headphone, the other is line-out, but there is no UCM for
  these docks yet, so the pluseaudio only can handle the 1st playback device,
  need us to add the UCM for them, before adding UCM, we need to set the
  longname of the sound card in the linux kernel.

  [Fix]
  For Linux kernel: Cherry-picked 3 upstream patches, these patches add the 
longname of the sound card for the dock station.

  For alsa-lib: Cherry-picked 3 upstream patches from alsa-lib, these will
  add ucm configuration files for Dell WD15&19, and change the SPDIF conf
  in the USB-AUDIO.conf.

  [Test Case]
  Open the gnome-sound-setting, we can choose headphone-usb and lineout-usb from
  UI, and play sound via these devices

  [Regression Potential]
  Very low, these patches come from upstream, and the change is only specific
  to WD15 and WD19 dock station.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1806532/+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 1812353] Re: content injection in http method (CVE-2019-3462)

2019-01-22 Thread Erlenmayr
There would be a much lower risk if HTTP (without TLS) were not still
the default for repositories.

This can actually also be abused by a MitM, he can always make your APT
think that there are no new updates (a simple 304 Not Modified works),
and then exploit recent vulnerabilities of which you have not received
the fix.

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

Title:
  content injection in http method (CVE-2019-3462)

Status in apt package in Ubuntu:
  In Progress
Status in apt source package in Precise:
  New
Status in apt source package in Trusty:
  Fix Released
Status in apt source package in Xenial:
  Fix Released
Status in apt source package in Bionic:
  Fix Released
Status in apt source package in Cosmic:
  Fix Released
Status in apt source package in Disco:
  In Progress

Bug description:
  apt, starting with version 0.8.15, decodes target URLs of redirects,
  but does not check them for newlines, allowing MiTM attackers (or
  repository mirrors) to inject arbitrary headers into the result
  returned to the main process.

  If the URL embeds hashes of the supposed file, it can thus be used to
  disable any validation of the downloaded file, as the fake hashes will
  be prepended in front of the right hashes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1812353/+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 1011717] Re: package libcairo-gobject2 1.10.2-6.1ubuntu2 failed to install/upgrade: libcairo-gobject2:amd64 1.10.2-6.1ubuntu2 cannot be configured because libcairo-gobject2

2019-01-22 Thread Sebastien Bacher
** Changed in: cairo (Ubuntu)
   Status: New => Invalid

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

Title:
  package libcairo-gobject2 1.10.2-6.1ubuntu2 failed to install/upgrade:
  libcairo-gobject2:amd64 1.10.2-6.1ubuntu2 cannot be configured because
  libcairo-gobject2

Status in cairo package in Ubuntu:
  Invalid

Bug description:
  i'm dumb and i restarted during a update - it was an accident and
  happened quickly - thank you for all you do

  ProblemType: Package
  DistroRelease: Ubuntu 12.04
  Package: libcairo-gobject2 1.10.2-6.1ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16
  Uname: Linux 3.2.0-24-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.0.1-0ubuntu8
  AptOrdering:
   libcairo-gobject2: Install
   libcairo-gobject2: Configure
   libcairo-gobject2: Configure
  Architecture: amd64
  Date: Mon Jun 11 10:00:16 2012
  DuplicateSignature:
   Unpacking replacement libcairo-gobject2:i386 ...
   dpkg: error processing libcairo-gobject2 (--configure):
libcairo-gobject2:amd64 1.10.2-6.1ubuntu2 cannot be configured because 
libcairo-gobject2:i386 is in a different version (1.10.2-6.1ubuntu3)
  ErrorMessage: libcairo-gobject2:amd64 1.10.2-6.1ubuntu2 cannot be configured 
because libcairo-gobject2
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  SourcePackage: cairo
  Title: package libcairo-gobject2 1.10.2-6.1ubuntu2 failed to install/upgrade: 
libcairo-gobject2:amd64 1.10.2-6.1ubuntu2 cannot be configured because 
libcairo-gobject2
  UpgradeStatus: Upgraded to precise on 2012-04-30 (41 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/1011717/+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 647472] Re: uptime counts time spend in suspend

2019-01-22 Thread Stephan
This is no specific issue of procps, it just returns the value from the
kernel. The kernel documents (in the source) that the value includes the
time spent in suspend.

/proc/uptime gets the value from here:

https://elixir.bootlin.com/linux/v4.20.3/source/include/linux/timekeeping.h#L93

/**
 * ktime_get_boottime - Returns monotonic time since boot in ktime_t format
 *
 * This is similar to CLOCK_MONTONIC/ktime_get, but also includes the
 * time spent in suspend.
 */
static inline ktime_t ktime_get_boottime(void)
{
return ktime_get_with_offset(TK_OFFS_BOOT);
}

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

Title:
  uptime counts time spend in suspend

Status in procps package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: procps

  According to man, amongst other things uptime shows "how long the
  system has been running". This is not true in the case of suspending
  the computer, as uptime counts the time spend in suspend as uptime
  time. In this way one can turn on a computer, put it to sleep for a
  week and then go back from suspend and uptime will show them the whole
  7 days of uptime.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: procps 1:3.2.8-1ubuntu4
  ProcVersionSignature: Ubuntu 2.6.32-24.43-generic 2.6.32.15+drm33.5
  Uname: Linux 2.6.32-24-generic x86_64
  NonfreeKernelModules: wl
  Architecture: amd64
  Date: Sat Sep 25 14:20:54 2010
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
  SourcePackage: procps

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/647472/+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 1309804] Re: When gvim window is moved: (gvim:9767): GLib-CRITICAL **: Source ID 51 was not found when attempting to remove it

2019-01-22 Thread Paul White
Fixed in Ubuntu version 7.4.253-1

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

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

Title:
  When gvim window is moved: (gvim:9767): GLib-CRITICAL **: Source ID 51
  was not found when attempting to remove it

Status in vim package in Ubuntu:
  Fix Released
Status in vim package in Debian:
  Fix Released

Bug description:
  As soon as gvim (/usr/bin/vim.gtk from package vim-gtk) window gets
  focus the following message is printed in the window where I started
  gvim from:

  (gvim:9767): GLib-CRITICAL **: Source ID 51 was not found when
  attempting to remove it

  It does not seem to have any other effects, it's just disruptive
  message. It only appears once right after mouse pointer first hovers
  over the window (I have focus follows mouse).

  This was not happening before upgrading to Ubuntu 14.04

  Ubuntu release: Ubuntu 14.04 LTS

  Package:

  $ apt-cache policy vim-gtk
  vim-gtk:
    Installed: 2:7.4.052-1ubuntu3
    Candidate: 2:7.4.052-1ubuntu3
    Version table:
   *** 2:7.4.052-1ubuntu3 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/universe amd64 
Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1309804/+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 1414255] Re: package libcairo-gobject2:amd64 1.13.0~20140204-0ubuntu1.1 failed to install/upgrade: package libcairo-gobject2:amd64 is already installed and configured

2019-01-22 Thread Sebastien Bacher
** Changed in: cairo (Ubuntu)
   Status: New => Invalid

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

Title:
  package libcairo-gobject2:amd64 1.13.0~20140204-0ubuntu1.1 failed to
  install/upgrade: package libcairo-gobject2:amd64 is already installed
  and configured

Status in cairo package in Ubuntu:
  Invalid

Bug description:
  Just started the computer and appear this problem. Don't know actually
  what does it means, i'm quite new in using ubuntu, so i let it go
  ahead and submit the bug.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libcairo-gobject2:amd64 1.13.0~20140204-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
  Uname: Linux 3.13.0-44-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  AptdaemonVersion: 1.1.1-1ubuntu5.1
  Architecture: amd64
  Date: Fri Jan 23 16:51:11 2015
  DuplicateSignature: 
package:libcairo-gobject2:amd64:1.13.0~20140204-0ubuntu1.1:package 
libcairo-gobject2:amd64 is already installed and configured
  ErrorMessage: package libcairo-gobject2:amd64 is already installed and 
configured
  InstallationDate: Installed on 2015-01-03 (20 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: cairo
  Title: package libcairo-gobject2:amd64 1.13.0~20140204-0ubuntu1.1 failed to 
install/upgrade: package libcairo-gobject2:amd64 is already installed and 
configured
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/1414255/+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 1023842] Re: Vim contains a buggy version of the netrw plugin

2019-01-22 Thread Paul White
Fixed in Ubuntu in version 7.3.524-1

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

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

Title:
  Vim contains a buggy version of the netrw plugin

Status in vim package in Ubuntu:
  Fix Released
Status in vim package in Debian:
  Fix Released

Bug description:
  The package contains v143 version of the netrw plugin, which has a really 
annoying bug.
  When using ctrl-w-s, ctrl-w-v for window management, it messes up the windows.

  It has already been fixed in v144 version. Please upgrade package with
  the fixed version.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: vim-runtime 2:7.3.429-2ubuntu2.1
  ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19
  Uname: Linux 3.2.0-26-generic x86_64
  ApportVersion: 2.0.1-0ubuntu8
  Architecture: amd64
  Date: Thu Jul 12 12:46:58 2012
  Dependencies:
   
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  PackageArchitecture: all
  SourcePackage: vim
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1023842/+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 1790242] Re: Converting PDF to PS with pdftocairo results in wrong character spacing with some Adobe fonts

2019-01-22 Thread Sebastien Bacher
Thank you for your bug report, that's probably an upstream bug and
should be reported to them on https://gitlab.freedesktop.org/cairo/cairo

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

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

Title:
  Converting PDF to PS with pdftocairo results in wrong character
  spacing with some Adobe fonts

Status in cairo package in Ubuntu:
  New

Bug description:
  I use pdftocairo as the default renderer in CUPS to print to my HP
  LaserJet printer. It's the tool that better manages PDF documents with
  shading and transparency (common in beamer presentations and PDFs
  generated by cairo). Everything worked fine until I discovered some
  pages in documents were incorrectly printed.

  I tried to print a PDF document (produced by pdfTeX) containing the
  Helvetica-Narrow fonts, and some lines of the document exhibited wrong
  character spacing. I tried to print the same document using Chrome and
  the text was printed with correct spacing so the printer wasn't the
  responsible.

  After changing the default PDF->PS renderer I discovered the fault was
  in pdftocairo because any conversion with pdftops and pdf2gs resulted
  in correct character spacing on my screen. Changing the PS language
  level did not work. Also, this bug doesn't manifest when pdfTeX uses
  the URW base 35 fonts instead of the Adobe ones.

  I am attaching a PDF document that can be converted with pdftocairo,
  pdftops and pdf2ps with pdftocairo being the only one that looks
  different at the narrow fonts.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/1790242/+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 524674] Re: cmake.vim syntax is out of date

2019-01-22 Thread Paul White
Upstream report was closed 2010-07-21
Changes would have synced into Ubuntu long ago
So closing as fixed

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

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

Title:
  cmake.vim syntax is out of date

Status in vim package in Ubuntu:
  Fix Released
Status in vim package in Debian:
  Fix Released

Bug description:
  Binary package hint: vim

  The Vim 7.2.245 installed from Ubuntu 9.10 packages does include
  cmake.vim syntax file which is very old.

  Date:  $Date: 2006/09/23 21:09:08 $
  Version:   $Revision: 1.6 $

  However, current version available at http://www.cmake.org/CMakeDocs
  /cmake-syntax.vim is four revisions and two years ahead.

  Date:  $Date: 2008-08-25 14:31:28 $
  Version:   $Revision: 1.10 $

  I believe it's relevant to update cmake.vim in the Vim package.

  By the way, the same issue applices to $VIMFILES/indent/cmake.vim New
  version is available at http://www.cmake.org/CMakeDocs/cmake-
  indent.vim

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vim/+bug/524674/+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 1654600] Re: unattended-upgrade-shutdown hangs when /var is a separate filesystem

2019-01-22 Thread Launchpad Bug Tracker
This bug was fixed in the package unattended-upgrades - 0.90ubuntu0.10

---
unattended-upgrades (0.90ubuntu0.10) xenial-security; urgency=medium

  * No change rebuild in the -security pocket (See LP #1686470)

 -- Marc Deslauriers   Fri, 18 Jan 2019
13:34:27 -0500

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

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

Title:
  unattended-upgrade-shutdown hangs when /var is a separate filesystem

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  Fix Released
Status in unattended-upgrades source package in Yakkety:
  Fix Released
Status in unattended-upgrades source package in Zesty:
  Fix Released
Status in unattended-upgrades package in Debian:
  Fix Released

Bug description:
  [SRU justification]
  This fix is needed to make sure that the system does not hang on shutdown 
when /var is a speparate file system

  [Impact]
  System can hang up to 10 minutes if not fixed.

  [Fix]
  Change the systemd unit's ExecStart to an ExecStop so the unit is correctly 
sequenced.
  Change WantedBy to multi-user.target. This requires working around Debian Bug 
#797108 which causes the new unit not to be enabled.
  Remove the unneeded override_dh_isntallinit
  Add Default-Start levels to the SysV initscript
  Improve DEP8 testing

  [Test Case]
  In a VM with /var separated from the / file system, shutdown the VM. It will 
hang for 10 minutes

  [Regression]
  Upgrade has been tested on Xenial, Yakkety, Zesty. do-release-upgrade has 
been tested from Trusty to Xenial. All behave as expected.

  A change of behavior may occur now that the systemd unit is correctly
  enabled, which would make functionalities like InstallOnShutdown to
  work as expected whereas it could have been broken previously. This
  cannot be considered as a regression as it is expected behavior.

  Shutdown may be slowed down as it now correctly depends on /var and
  /boot to be available so the unit will run earlier than previously.

  [Original description of the problem]
  The systemd unit file unattended-upgrades.service is used to stop a running 
unattended-upgrade
  process during shutdown. This unit file is running together with all 
filesystem
  unmount services.

  The unattended-upgrades service checks if the lockfile for unattended-upgrade
  (in /var/run) exists, and if it does, there is an unattended-upgrade in 
progress
  and the service will wait until it finishes (and therefore automatically wait 
at
  shutdown).

  However, if /var is a separate filesystem, it will get unmounted even though 
/var/run
  is a tmpfs that's still mounted on top of the /var/run directory in the /var 
filesystem.
  The unattended-upgrade script will fail to find lockfile, sleeps for 5 
seconds, and
  tries to check the lockfile again. After 10 minutes (the default timeout), it 
will finally
  exit and the system will continue shutdown.

  The problem is the error handling in 
/usr/share/unattended-upgrades/unattended-upgrade-shutdown
  where it tries to lock itself:

  while True:
  res = apt_pkg.get_lock(options.lock_file)
  logging.debug("get_lock returned %i" % res)
  # exit here if there is no lock
  if res > 0:
  logging.debug("lock not taken")
  break
  lock_was_taken = True

  The function apt_pkg.get_lock() either returns a file descriptor, or -1 on an 
error.
  File descriptors are just C file descriptors, so they are always positive 
integers.
  The code should check the result to be negative, not positive. I have 
attached a patch
  to reverse the logic.

  Additional information:

  1)
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  2)
  unattended-upgrades:
    Installed: 0.90ubuntu0.3
    Candidate: 0.90ubuntu0.3
    Version table:
   *** 0.90ubuntu0.3 500
  500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   0.90 500
  500 http://nl.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  500 http://nl.archive.ubuntu.com/ubuntu xenial/main i386 Packages
  3)
  Fast reboot
  4)
  Very slow reboot (after a 10 minutes timeout)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1654600/+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 1686470] Re: Apt updates that are uniformly spread across all timezones, with predictable application windows

2019-01-22 Thread Launchpad Bug Tracker
This bug was fixed in the package unattended-upgrades - 0.90ubuntu0.10

---
unattended-upgrades (0.90ubuntu0.10) xenial-security; urgency=medium

  * No change rebuild in the -security pocket (See LP #1686470)

 -- Marc Deslauriers   Fri, 18 Jan 2019
13:34:27 -0500

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

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

Title:
  Apt updates that are uniformly spread across all timezones, with
  predictable application windows

Status in apt package in Ubuntu:
  Fix Released
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  Fix Released
Status in apt source package in Yakkety:
  Won't Fix
Status in unattended-upgrades source package in Yakkety:
  Won't Fix
Status in apt source package in Zesty:
  Fix Released
Status in unattended-upgrades source package in Zesty:
  Fix Released
Status in apt source package in Artful:
  Fix Released
Status in unattended-upgrades source package in Artful:
  Fix Released
Status in apt package in Debian:
  Fix Released
Status in unattended-upgrades package in Debian:
  Fix Released

Bug description:
  [ Impact ]

   * unattended-upgrades are enabled by default in Ubuntu 16.04 and
  later

   * Currently the following three things happen as a monolithic event:
     - metadata updates: apt update
     - download of updates: apt upgrade --download-only
     - application of updates: apt upgrade

   * For the long running instances, all of the above happens at random
     times throughout the day.

   * If systems were poweredoff / suspended, this happens on boot /
  resume

   * End-users would like to have predictable timing, and control over when
     the updates happen.

  Considering all of the above, the following new behavior is proposed
  which should address all concerns in question. It combines all the
  desired properties from both end-user and mirror perspectives.

  [ Proposed Default Behavior ]

   * Decouple unattended-upgrades application, from apt update

   * apt update:
     - shall be a systemd timer based unit, triggered every 12h with a
   random delay of 12h, therefore executed randomly twice a day.
     - if unattened-upgrades (default on), or download-upgreadaeble-packages
   are enabled, it should result in updates being downloaded aka
   `apt upgrade --download-only`

   * unattended-upgrades:
     - shall be a separate systemd timer based unit triggered at 6am local
   time with a random delay of 1h, therefore executed between 6am and
   7am local time.

   * On boot / resume:
     - if we have missed one, or more, apt update timers,
   apt update / download upgrades / unattended-upgrade will happen in
   sequence. This may result in mirror spikes, but we do want to secure
   cold/stale-booted systems as soon as possible.

  [Test Case]

   * Run system for more than 24h, and check that apt updates were
     automatically executed twice.

   * Check that unattended upgrades were triggered to be applied at
     6am..7am window, if any.

   * Poweroff the machine over the period when apt-get update was
     scheduled, poweron and observe that apt-get update / download /
     unattended upgrade are all performed on boot.

   * Downgrade systemd to the release version of the package (from
     -security). Remove apt periodic stamp files rm /var/lib/apt/periodic/*.
 Then run 'sudo systemctl start apt-daily.service'.
     Confirm that the systemd package is downloaded, but not upgraded.

  [Regression Potential]

   * The newly proposed behavior is a mix of Pre-xenial behavior of "do
     everything at 6am..6:30am window" and the xenial+ behavior of "do
     everything at random times throughout the day". If there are specific
     deployments that rely on the previous types of behaviour they will be
     able to adjust manually the systemd timers with the overrides to be
     executed exactly as they wish; or match the .0 release behaviour that
     they prefer.

   * If timers behavior is coded wrongly the proposed behaviour might not be
     executed as intended, thus requiring further SRUs to bring us in-line
     with the great expectations.

  [Other Info]

    * Related bug reports and history:
  - bug #1615482
  - bug #1554848

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1686470/+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 1812852] [NEW] package whoopsie 0.2.24.6ubuntu4 failed to install/upgrade: Unterprozess neues pre-removal-Skript gab den Fehlerwert 100 zurück

2019-01-22 Thread Winfried Münch
Public bug reported:

while i run do-release-upgrade from ubuntu 14.04 it happens

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: whoopsie 0.2.24.6ubuntu4
ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
Uname: Linux 4.15.0-43-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.29
Architecture: amd64
CrashReports: 600:0:122:389841:2019-01-22 13:51:23.423334360 +0100:2019-01-22 
13:51:24.423334360 +0100:/var/crash/whoopsie.0.crash
Date: Tue Jan 22 13:51:24 2019
Df:
 Dateisystem1K-Blöcke Benutzt Verfügbar Verw% Eingehängt auf
 udev 8147024   0   81470240% /dev
DpkgTerminalLog: Log started: 2019-01-22  13:15:16
ErrorMessage: Unterprozess neues pre-removal-Skript gab den Fehlerwert 100 
zurück
InstallationDate: Installed on 2014-09-09 (1596 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1
 apt  1.2.10ubuntu1
SourcePackage: whoopsie
Title: package whoopsie 0.2.24.6ubuntu4 failed to install/upgrade: Unterprozess 
neues pre-removal-Skript gab den Fehlerwert 100 zurück
UpgradeStatus: Upgraded to xenial on 2019-01-22 (0 days ago)

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


** Tags: amd64 apport-package third-party-packages xenial

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

Title:
  package whoopsie 0.2.24.6ubuntu4 failed to install/upgrade:
  Unterprozess neues pre-removal-Skript gab den Fehlerwert 100 zurück

Status in whoopsie package in Ubuntu:
  New

Bug description:
  while i run do-release-upgrade from ubuntu 14.04 it happens

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: whoopsie 0.2.24.6ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: amd64
  CrashReports: 600:0:122:389841:2019-01-22 13:51:23.423334360 +0100:2019-01-22 
13:51:24.423334360 +0100:/var/crash/whoopsie.0.crash
  Date: Tue Jan 22 13:51:24 2019
  Df:
   Dateisystem1K-Blöcke Benutzt Verfügbar Verw% Eingehängt auf
   udev 8147024   0   81470240% /dev
  DpkgTerminalLog: Log started: 2019-01-22  13:15:16
  ErrorMessage: Unterprozess neues pre-removal-Skript gab den Fehlerwert 100 
zurück
  InstallationDate: Installed on 2014-09-09 (1596 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: whoopsie
  Title: package whoopsie 0.2.24.6ubuntu4 failed to install/upgrade: 
Unterprozess neues pre-removal-Skript gab den Fehlerwert 100 zurück
  UpgradeStatus: Upgraded to xenial on 2019-01-22 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1812852/+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 1812852] Re: package whoopsie 0.2.24.6ubuntu4 failed to install/upgrade: Unterprozess neues pre-removal-Skript gab den Fehlerwert 100 zurück

2019-01-22 Thread Winfried Münch
I run the do-release-upgrade in a chroot environment on a ubuntu 18.04
system with bind from dev sys and proc to the chroot.

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

Title:
  package whoopsie 0.2.24.6ubuntu4 failed to install/upgrade:
  Unterprozess neues pre-removal-Skript gab den Fehlerwert 100 zurück

Status in whoopsie package in Ubuntu:
  New

Bug description:
  while i run do-release-upgrade from ubuntu 14.04 it happens

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: whoopsie 0.2.24.6ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: amd64
  CrashReports: 600:0:122:389841:2019-01-22 13:51:23.423334360 +0100:2019-01-22 
13:51:24.423334360 +0100:/var/crash/whoopsie.0.crash
  Date: Tue Jan 22 13:51:24 2019
  Df:
   Dateisystem1K-Blöcke Benutzt Verfügbar Verw% Eingehängt auf
   udev 8147024   0   81470240% /dev
  DpkgTerminalLog: Log started: 2019-01-22  13:15:16
  ErrorMessage: Unterprozess neues pre-removal-Skript gab den Fehlerwert 100 
zurück
  InstallationDate: Installed on 2014-09-09 (1596 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: whoopsie
  Title: package whoopsie 0.2.24.6ubuntu4 failed to install/upgrade: 
Unterprozess neues pre-removal-Skript gab den Fehlerwert 100 zurück
  UpgradeStatus: Upgraded to xenial on 2019-01-22 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1812852/+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 1760106] Re: FFe: Enable configuring resume offset via sysfs

2019-01-22 Thread Dimitri John Ledkov
@Mario

Instead of your patch, this one
https://git.kernel.org/pub/scm/libs/klibc/klibc.git/commit/?id=a2f9cd4abe2d5cb72e1e89089b132e866e3cea81
got merged into klibc upstream and is now present in disco.

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

** Changed in: klibc (Ubuntu Cosmic)
 Assignee: Dimitri John Ledkov (xnox) => (unassigned)

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

Title:
  FFe: Enable configuring resume offset via sysfs

Status in OEM Priority Project:
  Fix Released
Status in klibc package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in klibc source package in Bionic:
  New
Status in linux source package in Bionic:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released
Status in klibc source package in Cosmic:
  New
Status in linux source package in Cosmic:
  Fix Released
Status in systemd source package in Cosmic:
  Fix Released

Bug description:
  [Impact]

   * Cannot hibernate & resume from a swapfile

  [Test Case]

   * Create or enlarge swapfile to be big enough for hibernation
   * Attempt to hibernate and resume

  [Regression Potential]

   * Hibernation is not reliable technology in itself, and multiple
  things may cause failure to resume. Thus it is sufficient to validate
  this bug after swapfile is attempted for hibernation and the disk
  offset kernel parameter is modified. Irrespective if actual suspending
  or resume were successful or not.

  [Other Info]
   
   * Original bug report

  In 4.17 a new attribute is introduced to configure the hibernation
  resume offset. Since Ubuntu enables a swapfile by default this
  attribute is important to be able to make hibernation work "out of the
  box".

  The patch in the kernel is here:
  
https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git/commit/?h=linux-next&id=355064675f1c997cea017ea64c8f2c216e5425d9

  Systemd support for adopting this change is available here:
  https://github.com/systemd/systemd/pull/8406
  As of 3/30/18 it's not yet been merged however.

  Klibc support for adopting this change is available here:
  https://www.zytor.com/pipermail/klibc/2018-March/003986.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1760106/+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 1812353] Re: content injection in http method (CVE-2019-3462)

2019-01-22 Thread Launchpad Bug Tracker
This bug was fixed in the package apt - 1.6.6ubuntu0.1

---
apt (1.6.6ubuntu0.1) bionic-security; urgency=medium

  * SECURITY UPDATE: content injection in http method (CVE-2019-3462)
(LP: #1812353)

 -- Julian Andres Klode   Fri, 18 Jan 2019 11:39:50
+0100

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

Title:
  content injection in http method (CVE-2019-3462)

Status in apt package in Ubuntu:
  In Progress
Status in apt source package in Precise:
  New
Status in apt source package in Trusty:
  Fix Released
Status in apt source package in Xenial:
  Fix Released
Status in apt source package in Bionic:
  Fix Released
Status in apt source package in Cosmic:
  Fix Released
Status in apt source package in Disco:
  In Progress

Bug description:
  apt, starting with version 0.8.15, decodes target URLs of redirects,
  but does not check them for newlines, allowing MiTM attackers (or
  repository mirrors) to inject arbitrary headers into the result
  returned to the main process.

  If the URL embeds hashes of the supposed file, it can thus be used to
  disable any validation of the downloaded file, as the fake hashes will
  be prepended in front of the right hashes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1812353/+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 1811937] Re: shows network profiles on wrong device

2019-01-22 Thread Sebastien Bacher
I've reported the settings issue upstream
https://gitlab.gnome.org/GNOME/gnome-control-center/issues/353

The shell popdown menu isn't identical though, in your sreenshot there
is no entry for ens38 device which is listed in setting and active so
that might be another issue

** Summary changed:

- Networkmanager shows network profiles on wrong network
+ shows network profiles on wrong device

** Changed in: gnome-control-center (Ubuntu)
   Status: Incomplete => Triaged

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

Title:
  shows network profiles on wrong device

Status in gnome-control-center package in Ubuntu:
  Triaged
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  I have two network ports (ens 34 and ens 37) I'm able to create per
  port its own named profile where it is defined if this used profile
  should use DHCP, use manual DNS and others.

  But if I connect my android Smartphone with USB tethering all named
  Profiles are showing below the new network Port (USB Ethernet) and not
  any more below their defined port. (visual error only) That should
  only happened if a profile is not active but in this case I would
  prefer a separate profile menu where I could choose one and add to a
  specific port.

  Sometimes the network manager entry in the menu also shows confusing
  or empty entries. See print screen attached

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1811937/+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 1812353] Re: content injection in http method (CVE-2019-3462)

2019-01-22 Thread Julian Andres Klode
** Information type changed from Private Security to Public Security

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

Title:
  content injection in http method (CVE-2019-3462)

Status in apt package in Ubuntu:
  In Progress
Status in apt source package in Precise:
  New
Status in apt source package in Trusty:
  Fix Released
Status in apt source package in Xenial:
  Fix Released
Status in apt source package in Bionic:
  New
Status in apt source package in Cosmic:
  Fix Released
Status in apt source package in Disco:
  In Progress

Bug description:
  apt, starting with version 0.8.15, decodes target URLs of redirects,
  but does not check them for newlines, allowing MiTM attackers (or
  repository mirrors) to inject arbitrary headers into the result
  returned to the main process.

  If the URL embeds hashes of the supposed file, it can thus be used to
  disable any validation of the downloaded file, as the fake hashes will
  be prepended in front of the right hashes.

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

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


Re: [Touch-packages] [Bug 1811937] Re: Networkmanager shows network profiles on wrong network

2019-01-22 Thread AdlerHorst
In this case I use Ubuntu 18.04. On another device with Ubuntu 18.10 I
have the same UI problem.

Because the view in the Pop-down usually reflect the same wrong
appearance as the configuration dialogue, I thought that both may have
the same source of error. This case where the Pop-down not appear with a
network icon and text (only happened on 18.04) also only exist in the
configuration with an USB-Thetering. It's finally only a UI problem, the
Network configuration is working without Problem.


Am 22.01.19 um 10:52 schrieb Sebastien Bacher:
> Reading again it seems there is at least one settings issue. What
> version of Ubuntu are you using?
>
> ** Also affects: gnome-control-center (Ubuntu)
>Importance: Undecided
>Status: New
>
> ** Changed in: gnome-control-center (Ubuntu)
>Importance: Undecided => Low
>
> ** Changed in: gnome-control-center (Ubuntu)
>Status: New => Incomplete
>

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

Title:
  Networkmanager shows network profiles on wrong network

Status in gnome-control-center package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  I have two network ports (ens 34 and ens 37) I'm able to create per
  port its own named profile where it is defined if this used profile
  should use DHCP, use manual DNS and others.

  But if I connect my android Smartphone with USB tethering all named
  Profiles are showing below the new network Port (USB Ethernet) and not
  any more below their defined port. (visual error only) That should
  only happened if a profile is not active but in this case I would
  prefer a separate profile menu where I could choose one and add to a
  specific port.

  Sometimes the network manager entry in the menu also shows confusing
  or empty entries. See print screen attached

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1811937/+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 1812577] Re: apt-get source report dead links to git://git.debian.org

2019-01-22 Thread Rhonda D'Vine
Packages get updated and their source moved. Within Debian, the old git
hosting infrastructure got replaced by the gitlab instance on
https://salsa.debian.org/. Given that there is not really a default
schema where/how packages moved, redirects aren't an option. Older
packages in the pool don't get updated for that, and only updated
packages have current information again.  Thus this is a wontfix or
rather "will-fix-itself-over-time".

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

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

Title:
  apt-get source report dead links to git://git.debian.org

Status in apt package in Ubuntu:
  Won't Fix

Bug description:
  Steps to reproduce:
  1. Try to obtain source code of some package - for example for FreeMat with 
`apt-get source freemat`
  2. Get console output:

   Reading package lists... Done
   Building dependency tree   
   Reading state information... Done
   NOTICE: 'freemat' packaging is maintained in the 'Git' version control 
system at:
   git://git.debian.org/debian-science/packages/freemat.git
   Need to get 38,1 MB of source archives.
   Get:1 http://archive.ubuntu.com/ubuntu/ trusty/universe freemat 4.0-5build1 
(dsc) [2 139 B]
   Get:2 http://archive.ubuntu.com/ubuntu/ trusty/universe freemat 4.0-5build1 
(tar) [38,0 MB]
   Get:3 http://archive.ubuntu.com/ubuntu/ trusty/universe freemat 4.0-5build1 
(diff) [12,6 kB]
   Fetched 38,1 MB in 22s (1 727 kB/s)  
  
   gpgv: Signature made Sat. 21 Dec. 2013 06:57:14 MSK using RSA key ID EA330543
   gpgv: Can't check signature: public key not found
   dpkg-source: warning: failed to verify signature on ./freemat_4.0-5build1.dsc
   dpkg-source: info: extracting freemat in freemat-4.0
   dpkg-source: info: unpacking freemat_4.0.orig.tar.gz
   dpkg-source: info: unpacking freemat_4.0-5build1.debian.tar.gz
   dpkg-source: info: applying 01_gcc_includes.patch
   dpkg-source: info: applying 07_fix_FTBFS_with_GCC_4.4.patch
   dpkg-source: info: applying 09_warning.patch
   dpkg-source: info: applying 10_llvm.patch
   dpkg-source: info: applying gcc4.5.patch
   dpkg-source: info: applying 11_ftbfs_qt48.patch

  3. Try to get source code manually with `git` command

 $ git clone git://git.debian.org/debian-science/packages/freemat.git
 Cloning into 'freemat'...
 fatal: unable to connect to git.debian.org:
 git.debian.org[0: 194.177.211.202]: errno=Connection refused
 git.debian.org[1: 2001:648:2ffc:deb::211:202]: errno=Network is unreachable

  
  Expected results:
  * `apt-get source ...` reports correct link for the source code, user is able 
to get the source code manually.

  Actual results:
  * `apt-get source ...` reports wrong link for the source code, user is unable 
to get the source code manually.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: apt 1.0.1ubuntu2.18
  ProcVersionSignature: Ubuntu 3.13.0-153.203-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-153-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sun Jan 20 20:06:41 2019
  InstallationDate: Installed on 2018-07-22 (181 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1812577/+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 1812474] Re: /usr/lib/evolution/evolution-addressbook-factory regularly takes 100% CPU and 100% RAM for a while, making all the system unresponsive

2019-01-22 Thread Sebastien Bacher
Thank you for your bug report, could report the problem upstream as well
on https://gitlab.gnome.org/GNOME/evolution-data-server/issues ? they
probably have a better idea how to debug it

** Changed in: evolution-data-server (Ubuntu)
   Importance: Undecided => High

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

Title:
  /usr/lib/evolution/evolution-addressbook-factory regularly takes 100%
  CPU and 100% RAM for a while, making all the system unresponsive

Status in evolution-data-server package in Ubuntu:
  New

Bug description:
  /usr/lib/evolution/evolution-addressbook-factory regularly takes 100% CPU and 
100% RAM for a while, making all the system unresponsive; the GUI doesn't 
respond (gnome-shell's clock is stopped, the mouse pointer is stopped) and it 
lasts for a few minutes, then goes back to normal.  
  If I wait long enough, the addressbook crashes (not enough memory ?).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: evolution-data-server 3.30.1-1build1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Jan 19 09:59:18 2019
  ExecutablePath: 
/usr/lib/evolution/evolution-data-server/evolution-alarm-notify
  InstallationDate: Installed on 2017-01-09 (740 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  ProcEnviron:
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: evolution-data-server
  UpgradeStatus: Upgraded to cosmic on 2018-10-19 (92 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1812474/+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 1812132] Re: Does not return results with files that have hyphens in the filename

2019-01-22 Thread Sebastien Bacher
Would be probably best to report it upstream on
https://gitlab.gnome.org/GNOME/tracker/issues

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

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

Title:
  Does not return results with files that have hyphens in the filename

Status in tracker package in Ubuntu:
  New

Bug description:
  On Ubuntu 18.04 using the `vanilla-gnome-desktop` session (i.e. Gnome
  Shell), tracker does not return any files if there is a hyphen (-) in
  the search string.

  To recreate:

  - Create a file named `foo-bar`.

  - Press  to open Overview.

  - Type foo. Observe that the `foo-bar` file appears.

  - Type foo-. Observe that the overview says "No results."

  This is a regression as files with hyphens in the filename were
  included in search results in 16.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1812132/+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 1729827] Re: $ ubuntu-bug xorg

2019-01-22 Thread Daniel van Vugt
Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.

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

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

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

Title:
$ ubuntu-bug xorg

Status in Ubuntu:
  Won't Fix

Bug description:
  i don't know whot i'm doing. I hopo he will automatically report the
  bugs he found

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Fri Nov  3 11:48:15 2017
  DistroCodename: artful
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. HD Graphics 520 [1043:1070]
  InstallationDate: Installed on 2017-11-01 (1 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:3491 IMC Networks 
   Bus 001 Device 002: ID 04f2:b52b Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. P553UA
  ProcEnviron:
   LANGUAGE=it
   PATH=(custom, no user)
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=57084a81-3d5b-47bb-9418-c24272cfbe28 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to artful on 2017-11-02 (0 days ago)
  dmi.bios.date: 01/25/2017
  dmi.bios.vendor: ASUSTeK COMPUTER INC.
  dmi.bios.version: P553UA.303
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: P553UA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnASUSTeKCOMPUTERINC.:bvrP553UA.303:bd01/25/2017:svnASUSTeKCOMPUTERINC.:pnP553UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnP553UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: P
  dmi.product.name: P553UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  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+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Fri Nov  3 11:34:57 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2
  xserver.video_driver: modeset

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1729827/+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 1728444] Re: Random graphical freezes Ubuntu 17.10

2019-01-22 Thread Daniel van Vugt
Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.

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

** Changed in: gnome-shell (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  Random graphical freezes Ubuntu 17.10

Status in gnome-shell package in Ubuntu:
  Won't Fix

Bug description:
  Hello everyone!

  I'm not sure if this is the right package to report this graphics
  related bug. As this affects Wayland and Xorg sessions on my machine.

  I've noticed that mouse becomes very choppy for some time period at
  random, not sure why. Also it seems if there's high disk load (I/O
  indicator is on all the time) all graphics can freeze for very long
  time ( 30m-1h or more).

  Happy to provide extra info as needed. 
  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 29 19:57:44 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7560D] [1002:9904] 
(prog-if 00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 
7560D] [1002:9904]
  InstallationDate: Installed on 2017-09-30 (29 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=9e917423-5dbc-446b-bed6-506a46eb2382 ro quiet splash radeon.dpm=1 
vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/12/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A75M-HD2
  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:bd10/12/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A75M-HD2:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.: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: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  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+git20170309-0ubuntu1
  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/gnome-shell/+bug/1728444/+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 1728658] Re: Blank screens when connecting OneLink dock with a display connected

2019-01-22 Thread Daniel van Vugt
Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.

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

** Changed in: gnome-shell (Ubuntu)
   Status: New => Won't Fix

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

Title:
  Blank screens when connecting OneLink dock with a display connected

Status in gnome-shell package in Ubuntu:
  Won't Fix

Bug description:
  Lenovo X1 Carbon 4th gen
  OneLink dock
  2 x 2K dell displays

  Connecting the dock without displays works fine
  Connecting the dock with even one display connected results in blank screens 
on all displays

  The combination worked fine on 17.04

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Mon Oct 30 09:49:58 2017
  DistUpgraded: 2017-10-28 15:48:46,103 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: artful
  DistroVariant: ubuntu
  DkmsStatus:
   acpi-call, 1.1.0, 4.10.0-37-generic, x86_64: installedError! Could not 
locate dkms.conf file.
   File:  does not exist.
   
   acpi-call, 1.1.0, 4.13.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 520 [17aa:2238]
  InstallationDate: Installed on 2017-04-14 (199 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  MachineType: LENOVO 20FB002LUS
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=bc08c404-a63f-4e47-b021-49cc7c200f5f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to artful on 2017-10-28 (1 days ago)
  dmi.bios.date: 07/13/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1FET53W (1.27 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FB002LUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1FET53W(1.27):bd07/13/2017:svnLENOVO:pn20FB002LUS:pvrThinkPadX1Carbon4th:rvnLENOVO:rn20FB002LUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 4th
  dmi.product.name: 20FB002LUS
  dmi.product.version: ThinkPad X1 Carbon 4th
  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.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  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+git20170309-0ubuntu1
  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/gnome-shell/+bug/1728658/+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 1728741] Re: Xorg freeze

2019-01-22 Thread Daniel van Vugt
Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.

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

** Changed in: xorg-server (Ubuntu)
   Status: New => Won't Fix

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

Title:
  Xorg freeze

Status in xorg-server package in Ubuntu:
  Won't Fix

Bug description:
  Will not come back after screen lock.
  The main VAIO laptop lid monitor does not come back, stays dark, no backlight.
  I have a second HDMI monitor.
  The HDMI monitor will come back from screen lock, but scrambled.
  Mouse does not appear.
  I have also tried suckless.org slock with same result.
  Closing and opening the lid does not help.
  I also hear the laptop fan come on when trying to restore which indicates CPU 
is probably running away.
  No keyboard sequence seems to work, though I have not tested this 
exhaustively.
  All that works is a 5-second powerdown button press with restart.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 30 16:17:32 2017
  DistUpgraded: 2017-10-30 08:29:59,969 DEBUG icon theme changed, re-reading
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   NVIDIA Corporation GF108M [GeForce GT 540M] [10de:0df4] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Sony Corporation GF108M [GeForce GT 540M] [104d:9086]
  InstallationDate: Installed on 2016-10-29 (366 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  LightdmDisplayLog: (II) Server terminated successfully (0). Closing log file.
  MachineType: Sony Corporation VPCF215FX
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to artful on 2017-10-30 (0 days ago)
  dmi.bios.date: 02/10/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R0200V3
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR0200V3:bd02/10/2011:svnSonyCorporation:pnVPCF215FX:pvrC608AVBH:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.family: VAIO
  dmi.product.name: VPCF215FX
  dmi.product.version: C608AVBH
  dmi.sys.vendor: Sony Corporation
  version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1728741/+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 1730019] Re: Mouse/pointer missing after resume from sleep

2019-01-22 Thread Daniel van Vugt
Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.

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

** Changed in: gnome-shell (Ubuntu)
   Status: New => Won't Fix

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

Title:
  Mouse/pointer missing after resume from sleep

Status in gnome-shell package in Ubuntu:
  Won't Fix

Bug description:
  After waking the machine up, I am no longer able to use the mouse as
  the pointer does not respond. Only a hard reboot fixes this.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov  3 18:19:46 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.13.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation HD Graphics 5300 [8086:161e] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 5300 [17aa:3906]
  InstallationDate: Installed on 2017-11-02 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 048d:8386 Integrated Technology Express, Inc. 
   Bus 001 Device 003: ID 5986:0535 Acer, Inc 
   Bus 001 Device 002: ID 0489:e07a Foxconn / Hon Hai 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80HE
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/06/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: A6CN58WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: VIUU4
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 3 Pro-1370
  dmi.modalias: 
dmi:bvnLENOVO:bvrA6CN58WW:bd08/06/2015:svnLENOVO:pn80HE:pvrLenovoYOGA3Pro-1370:rvnLENOVO:rnVIUU4:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYOGA3Pro-1370:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80HE
  dmi.product.version: Lenovo YOGA 3 Pro-1370
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  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+git20170309-0ubuntu1
  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/gnome-shell/+bug/1730019/+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 1730094] Re: seems like things are going haywire. they repeat things being done.

2019-01-22 Thread Daniel van Vugt
Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.

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

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

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

Title:
  seems like things are going haywire. they repeat things being done.

Status in Ubuntu:
  Won't Fix

Bug description:
  the cd writer doesn't read or write. seems like things are not
  callabrationg right or something . I am not very knoweldgeable about
  this stuff.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sat Nov  4 09:43:08 2017
  DistUpgraded: 2017-10-26 12:58:05,971 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: artful
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0402] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [1043:8534]
  InstallationDate: Installed on 2017-04-14 (203 days ago)
  InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Alpha amd64 (20170219)
  MachineType: ASUSTeK COMPUTER INC. M11AD
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=654c6be4-27c5-4a07-92a8-2c3aaf6bebb7 ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: Upgraded to artful on 2017-10-26 (8 days ago)
  dmi.bios.date: 03/19/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0602
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M11AD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0602:bd03/19/2014:svnASUSTeKCOMPUTERINC.:pnM11AD:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnM11AD:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: Desktop
  dmi.product.name: M11AD
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  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+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Sat Nov  4 07:15:51 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2
  xserver.video_driver: modeset

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1730094/+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 1730251] Re: video crash

2019-01-22 Thread Daniel van Vugt
Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.

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

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

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

Title:
  video crash

Status in Ubuntu:
  Won't Fix

Bug description:
  when i play a video with vlc media player, it freeze after 20/30
  seconds but the sound still going

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov  5 23:44:35 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.13.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics 
Controller [17aa:5011]
  InstallationDate: Installed on 2017-11-04 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 37612DG
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=6dd77dcc-21a1-4be0-9bb6-dff778f4c29d ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/06/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: H9ET92WW(1.29)
  dmi.board.asset.tag: Not Available
  dmi.board.name: 37612DG
  dmi.board.vendor: LENOVO
  dmi.board.version: Win8 STD MM DPK IPG
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrH9ET92WW(1.29):bd08/06/2015:svnLENOVO:pn37612DG:pvrLenovoB590:rvnLENOVO:rn37612DG:rvrWin8STDMMDPKIPG:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: Lenovo B590
  dmi.product.name: 37612DG
  dmi.product.version: Lenovo B590
  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.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  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+git20170309-0ubuntu1
  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/+bug/1730251/+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 1730074] Re: games and menu

2019-01-22 Thread Daniel van Vugt
Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.

** Package changed: xorg (Ubuntu) => budgie-desktop (Ubuntu)

** Changed in: budgie-desktop (Ubuntu)
   Status: New => Won't Fix

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

Title:
  games and menu

Status in budgie-desktop package in Ubuntu:
  Won't Fix

Bug description:
  After adding games from Synaptic I couldn't go to Administration or
  Preferences. They were cut off. S I had to delete some games and then
  fix broken packages.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sat Nov  4 08:08:35 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA 
controller])
 Subsystem: Dell Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [1028:06ac]
  InstallationDate: Installed on 2017-11-03 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  MachineType: Dell Inc. Inspiron 15-3552
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=343298a5-bb4e-4b6b-9a51-cbcf6e910c75 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/15/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 4.1.0
  dmi.board.name: 0787MR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr4.1.0:bd06/15/2017:svnDellInc.:pnInspiron15-3552:pvr4.1.0:rvnDellInc.:rn0787MR:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 15-3552
  dmi.product.version: 4.1.0
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  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+git20170309-0ubuntu1
  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/budgie-desktop/+bug/1730074/+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 1731008] Re: Multi-monitor display arrangement doesn't work in Ubuntu 17.10

2019-01-22 Thread Daniel van Vugt
Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.

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

** Changed in: gnome-shell (Ubuntu)
   Status: New => Won't Fix

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

Title:
  Multi-monitor display arrangement doesn't work in Ubuntu 17.10

Status in gnome-shell package in Ubuntu:
  Won't Fix

Bug description:
  When using a fresh install of Ubuntu 17.10 desktop on a Lenovo T570
  laptop in a Lenovo ThinkPad Ultra Dock (40A20090XX), with the buitin
  monitor off (laptop closed) and 3 external 1920 x 1080 monitors (1 x
  Acer V246HL VGA, 2 x Dell P2417H DisplayPort) display arrangement in
  Settings | Devices | Displays does not work.  The Dell monitors show
  up as 4 and 3, the Acer as 2.  1, the builtin monitor, is not
  displayed in the arrangement area.  The monitor icons show up, left to
  right, in the order 4, 3, 2.  It is almost impossible to change that
  order.  I have managed, in 1 out of 20 attempts, to get the display
  icons into a 4, 2, 3 order, but in no case have I been able to apply
  any arrangement changes.  The Apply button is never displayed.  I want
  to get them into a 2, 4, 3 order.  This was not an issue in Ubuntu
  Gnome 17.04, in that version everything worked fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  8 10:51:08 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 620 [17aa:2247]
  InstallationDate: Installed on 2017-11-06 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 20H9000NUS
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/02/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1VET32W (1.22 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20H9000NUS
  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:bvrN1VET32W(1.22):bd06/02/2017:svnLENOVO:pn20H9000NUS:pvrThinkPadT570:rvnLENOVO:rn20H9000NUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T570
  dmi.product.name: 20H9000NUS
  dmi.product.version: ThinkPad T570
  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.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  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+git20170309-0ubuntu1
  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/gnome-shell/+bug/1731008/+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 1731068] Re: With NVIDIA proprietary drivers, initial login screan appears only on mouse movement

2019-01-22 Thread Daniel van Vugt
Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.


** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-384 (Ubuntu)

** Changed in: nvidia-graphics-drivers-384 (Ubuntu)
   Status: New => Won't Fix

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

Title:
  With NVIDIA proprietary drivers, initial login screan appears only on
  mouse movement

Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Won't Fix

Bug description:
  After installing the proprietary NVIDIA driver (384) I've been faced
  with a black screen after reboot. It turned out, that when I moved the
  mouse, the login screen appeared. The screen goes black immediately
  when I stop moving the mouse. I can normally put the password in on
  the black screen and go on with my life, but, you know, it doesn't
  look stable :)

  After I get the system up from sleeping (which didn't work earlier but
  suddenly started working) the log in screen in displayed normally.

  My system (Alienware 15 R3) has Intel's i7-7820HK and NVIDIA's GeForce
  GTX 1070 Mobile 8GB

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm 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  384.90  Tue Sep 19 19:17:35 
PDT 2017
   GCC version:  gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  BootLog: /dev/sda2: clean, 200420/61046784 files, 6117516/244157440 blocks
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Wed Nov  8 23:43:20 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: kubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.13.0-16-generic, x86_64: installed
   nvidia-384, 384.90, 4.13.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Subsystem: Dell Device [1028:0774]
   NVIDIA Corporation GP104M [GeForce GTX 1070 Mobile] [10de:1be1] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Dell GP104M [GeForce GTX 1070 Mobile] [1028:07c0]
  InstallationDate: Installed on 2017-11-04 (4 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:58c2 Realtek Semiconductor Corp. 
   Bus 001 Device 003: ID 0cf3:e300 Atheros Communications, Inc. 
   Bus 001 Device 002: ID 187c:0530 Alienware Corporation 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Alienware Alienware 15 R3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=32edfbb9-d0bb-495a-9313-48b5ee124d2b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/09/2017
  dmi.bios.vendor: Alienware
  dmi.bios.version: 1.1.8
  dmi.board.name: Alienware 15 R3
  dmi.board.vendor: Alienware
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Alienware
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnAlienware:bvr1.1.8:bd06/09/2017:svnAlienware:pnAlienware15R3:pvr1.1.8:rvnAlienware:rnAlienware15R3:rvrA00:cvnAlienware:ct10:cvrNotSpecified:
  dmi.product.family: Alienware
  dmi.product.name: Alienware 15 R3
  dmi.product.version: 1.1.8
  dmi.sys.vendor: Alienware
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  versio

[Touch-packages] [Bug 1733644] Re: Logging in while docked causes system to suspend

2019-01-22 Thread Daniel van Vugt
Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.

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

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

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

Title:
  Logging in while docked causes system to suspend

Status in Ubuntu:
  Won't Fix

Bug description:
  This issue is only present to the best of my knowledge on the Dell XPS
  9560 while connected to a docking station, in this case the Dell
  WD-15.  When logging in to the computer from a cold boot, the computer
  will go to sleep immediately after logging in.  This issue does not
  happen if the lid of the laptop is open, or if the computer is waking
  from sleep.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm 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  384.90  Tue Sep 19 19:17:35 
PDT 2017
   GCC version:  gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3)
  ApportVersion: 2.20.7-0ubuntu3.4
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 21 11:43:18 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.13.0-16-generic, x86_64: installed
   nvidia-384, 384.90, 4.13.0-16-generic, x86_64: installed
   virtualbox, 5.1.30, 4.13.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:07be]
 Subsystem: Dell GP107M [GeForce GTX 1050 Mobile] [1028:07be]
  InstallationDate: Installed on 2017-10-31 (20 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Dell Inc. XPS 15 9560
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=301dbbe4-b5ce-48cc-b1fc-f59a051d8bdb ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/30/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.name: 05FFDN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd08/30/2017:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9560
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  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+git20170309-0ubuntu1
  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/+bug/1733644/+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 1731674] Re: Can't rotate the screen

2019-01-22 Thread Daniel van Vugt
Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.

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

** Changed in: xorg-server (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  Can't rotate the screen

Status in xorg-server package in Ubuntu:
  Won't Fix

Bug description:
  I have recently installed Ubuntu 17.10. After I logged in, the screen
  rotated sideways. I tried "xrandr -o normal", but it didn't work. What
  should I do?

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Nov 11 19:44:03 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-11 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Hewlett-Packard HP Pavilion 17 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/19/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.43
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 22C7
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 90.41
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.43:bd08/19/2015:svnHewlett-Packard:pnHPPavilion17NotebookPC:pvr096E100800405F0620180:rvnHewlett-Packard:rn22C7:rvr90.41:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV
  dmi.product.name: HP Pavilion 17 Notebook PC
  dmi.product.version: 096E100800405F0620180
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  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+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1731674/+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 1732416] Re: two cursors on dual screen setup

2019-01-22 Thread Daniel van Vugt
Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.

** Package changed: xorg (Ubuntu) => mutter (Ubuntu)

** Changed in: mutter (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  two cursors on dual screen setup

Status in mutter package in Ubuntu:
  Won't Fix

Bug description:
  My secondary monitor (in portrait mode) is left of the primary
  monitor. When I move the cursor into the top left corner of my
  primary, a second cursor will show up on my secondary screen. It has
  no function, its just there. The area is about 4cm x 10cm starting at
  the top left corner. The second cursor is rotated to the left. Doesn't
  happen if I move the secondary screen to the right of my primary.
  Disappears when I move the cursor onto second screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 15 12:12:20 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:120f]
  InstallationDate: Installed on 2017-11-15 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=a2c4c090-f120-42fb-895f-11cfe3a2bfe4 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/27/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: Z270M-ITX/ac
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd10/27/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ270M-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  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+git20170309-0ubuntu1
  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/mutter/+bug/1732416/+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


  1   2   >