[Touch-packages] [Bug 1912498] Re: Preinstall some new essential raspi packages in the official raspi images

2021-02-02 Thread Martin Wimpress
** Changed in: livecd-rootfs (Ubuntu Focal)
 Assignee: (unassigned) => Łukasz Zemczak (sil2100)

** Changed in: ubuntu-meta (Ubuntu)
 Assignee: (unassigned) => Łukasz Zemczak (sil2100)

** Changed in: ubuntu-meta (Ubuntu Focal)
 Assignee: (unassigned) => Łukasz Zemczak (sil2100)

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

Title:
  Preinstall some new essential raspi packages in the official raspi
  images

Status in livecd-rootfs package in Ubuntu:
  Opinion
Status in ubuntu-meta package in Ubuntu:
  Opinion
Status in livecd-rootfs source package in Focal:
  In Progress
Status in ubuntu-meta source package in Focal:
  In Progress

Bug description:
  [Impact]

  For 20.04.2, also as part of support for some new Pi variants (CM4,
  Pi400), we want to preinstall some new essential packages in our raspi
  images such as rpi-eeprom, raspberrypi-userland etc.

  This can be done in two possible ways. One is the 'old way', with a
  single change to livecd-rootfs adding the new packages. But what we'd
  like to propose this time is actually a more proper way, i.e.
  introducing device-specific raspi seeds and a raspi meta-package that
  would pull in all the needed dependencies. This way is better for the
  future, as if we decide we want to add new packages to existing raspi
  installations, we can do it easily by modifying the seeds and
  rebuilding meta. Currently we have no way like this.

  So the current approach includes changes in the following components:
   * The ubuntu and platform seeds (git branches)
   * ubuntu-meta package (adding ubuntu-server-raspi)
   * livecd-rootfs package (installing the raspi-server task)

  [Test Case]

  After accepting all the package into -proposed (and making sure the git seed 
changes are merged), run a raspi arm64 and armhf build. Check if the image 
boots. Confirm that the new images have the following seeded: rpi-eeprom, 
libraspberrypi-bin, flash-kernel, pi-bluetooth.
  Compare manifests between a normal, previous raspi image build and the one 
using seeds - check if nothing has been 'dropped'.

  Also, check if no other image builds have been affected and still
  build correctly, compare image manifests.

  [Where problems could occur]

  In its current form, as the update touches some livecd-rootfs
  auto/config paths, it's possible that a malformed cut-paste broke some
  edge case scenario, so it's good if other non-raspi builds are also
  checked for correctness. Seed changes are less likely to break
  anything, but manifests should be checked in case something got
  dropped by accident.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1912498/+subscriptions

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


[Touch-packages] [Bug 1782984] Re: Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple applications

2021-02-02 Thread Martin Wimpress
** Changed in: libx11 (Ubuntu Bionic)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

** Changed in: libx11 (Ubuntu Groovy)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

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

Title:
  Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple
  applications

Status in libx11 package in Ubuntu:
  Fix Released
Status in libx11 source package in Bionic:
  New
Status in libx11 source package in Focal:
  New
Status in libx11 source package in Groovy:
  New

Bug description:
  STEPS TO REPRODUCE
  ==
  The bug seems to occur when clicking on a file or folder. It is random and 
difficult to provide clear steps to reproduce. It is, however, a common 
situation.

  EXPECTED RESULTS
  
  pcmanfm works without problem.

  ACTUAL RESULTS
  ==
  All pcmanfm windows become unresponsive, though background processes (e.g. 
copying) may continue without problem. with the same error message in 
~/.cache/lxsession/LXDE/run.log:

  [xcb] Unknown sequence number while processing queue
  [xcb] Most likely this is a multi-threaded client and XInitThreads has not 
been called
  [xcb] Aborting, sorry about that.
  pcmanfm: xcb_io.c:259: poll_for_event: Assertion 
`!xcb_xlib_threads_sequence_lost' failed.
  ** Message: 19:58:49.267: app.vala:130: pcmanfm exit with this type of exit: 6
  ** Message: 19:58:49.268: app.vala:148: Exit not normal, try to reload

  (note the timestamp on the message will vary)

  AFFECTED VERSIONS
  =
  1.2.5-3ubuntu1
  NOT 1.2.4-1ubuntu0.1

  UPSTREAM BUG
  
  https://sourceforge.net/p/pcmanfm/bugs/1089/

  ADDITIONAL NOTES
  
  Other GTK2 file managers (e.g. Thunar) and applications (e.g. GIMP, Leafpad) 
seem to have the same problems. This is probably at least rooted in a GTK2 bug:
  https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1808710

  To further assert this, note that there is a SpaceFM file manager that
  is available in GTK2 and GTK3. The GTK2 version displays the behavior.
  The GTK3 version does not. Same with LibreOffice.

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

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


[Touch-packages] [Bug 1908502] Re: [MIR] libdeflate

2021-01-26 Thread Martin Wimpress
** Changed in: libdeflate (Ubuntu Hirsute)
 Assignee: (unassigned) => Sebastien Bacher (seb128)

** Changed in: tiff (Ubuntu Hirsute)
 Assignee: (unassigned) => Sebastien Bacher (seb128)

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

Title:
  [MIR] libdeflate

Status in libdeflate package in Ubuntu:
  New
Status in tiff package in Ubuntu:
  Triaged
Status in libdeflate source package in Hirsute:
  New
Status in tiff source package in Hirsute:
  Triaged

Bug description:
  * Availability

  In sync with Debian, built on all architectures
  https://launchpad.net/ubuntu/+source/libdeflate/1.7-1

  * Rationale

  It's a new depends of libtiff

  * Security

  There is no known security issues

  https://security-tracker.debian.org/tracker/source-package/libdeflate
  https://people.canonical.com/~ubuntu-security/cve/pkg/libdeflate.html
  https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=libdeflate

  * Quality assurance

  The desktop team is going to subscribe to the package

  https://launchpad.net/ubuntu/+source/libdeflate/+bugs
  https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=libdeflate

  No open reports

  The package enables upstream tests during the build and ships basic
  autopkgtests

  * Dependencies

  No universe binary dependencies

  * Standards compliance

  current 4.5.1 standards-version, debhelper compat 13, dh style simple
  rules

  * Maintenance

  Upstream is active, the package is maintained in Debian and in sync
  for Ubuntu

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

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


[Touch-packages] [Bug 1912609] Re: mac80211_hwsim: hostapd fails to start with S1G band

2021-01-26 Thread Martin Wimpress
** Changed in: wpa (Ubuntu Hirsute)
 Assignee: (unassigned) => Sebastien Bacher (seb128)

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

Title:
  mac80211_hwsim: hostapd fails to start with S1G band

Status in wpa package in Ubuntu:
  New
Status in wpa source package in Hirsute:
  New

Bug description:
  Hostapd fails to start on a recent 5.10+ kernel:

  $ cat repro.sh 
  #!/bin/sh

  sudo modprobe mac80211_hwsim
  sudo  ip a flush dev wlan0
  sudo  ip a add 192.168.5.1/24 dev wlan0

  cat << EOF > hostapd.conf
  interface=wlan0
  driver=nl80211
  hw_mode=b
  channel=1
  ssid=fake net
  EOF

  sudo  hostapd hostapd.conf

  ubuntu@hirsute-amd64:~$ ./repro.sh 
  Configuration file: hostapd.conf
  nl80211: kernel reports: expected nested data
  Using interface wlan0 with hwaddr 02:00:00:00:00:00 and ssid "fake net"
  wlan0: interface state UNINITIALIZED->ENABLED
  wlan0: AP-ENABLED 
  ^C
  wlan0: interface state ENABLED->DISABLED
  wlan0: AP-DISABLED  
  wlan0: CTRL-EVENT-TERMINATING 
  nl80211: deinit ifname=wlan0 disabled_11b_rates=0

  this due to the mismanagement of the newly added S1G band, the
  attached patch fixes it.

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

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


[Touch-packages] [Bug 1782984] Re: Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple applications

2021-01-26 Thread Martin Wimpress
** Changed in: libx11 (Ubuntu)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

** Changed in: libx11 (Ubuntu Focal)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

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

Title:
  Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple
  applications

Status in libx11 package in Ubuntu:
  Fix Released
Status in libx11 source package in Bionic:
  New
Status in libx11 source package in Focal:
  New
Status in libx11 source package in Groovy:
  New

Bug description:
  STEPS TO REPRODUCE
  ==
  The bug seems to occur when clicking on a file or folder. It is random and 
difficult to provide clear steps to reproduce. It is, however, a common 
situation.

  EXPECTED RESULTS
  
  pcmanfm works without problem.

  ACTUAL RESULTS
  ==
  All pcmanfm windows become unresponsive, though background processes (e.g. 
copying) may continue without problem. with the same error message in 
~/.cache/lxsession/LXDE/run.log:

  [xcb] Unknown sequence number while processing queue
  [xcb] Most likely this is a multi-threaded client and XInitThreads has not 
been called
  [xcb] Aborting, sorry about that.
  pcmanfm: xcb_io.c:259: poll_for_event: Assertion 
`!xcb_xlib_threads_sequence_lost' failed.
  ** Message: 19:58:49.267: app.vala:130: pcmanfm exit with this type of exit: 6
  ** Message: 19:58:49.268: app.vala:148: Exit not normal, try to reload

  (note the timestamp on the message will vary)

  AFFECTED VERSIONS
  =
  1.2.5-3ubuntu1
  NOT 1.2.4-1ubuntu0.1

  UPSTREAM BUG
  
  https://sourceforge.net/p/pcmanfm/bugs/1089/

  ADDITIONAL NOTES
  
  Other GTK2 file managers (e.g. Thunar) and applications (e.g. GIMP, Leafpad) 
seem to have the same problems. This is probably at least rooted in a GTK2 bug:
  https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1808710

  To further assert this, note that there is a SpaceFM file manager that
  is available in GTK2 and GTK3. The GTK2 version displays the behavior.
  The GTK3 version does not. Same with LibreOffice.

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

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


[Touch-packages] [Bug 1908502] Re: [MIR] libtiff5 dependency on libdeflate0

2021-01-05 Thread Martin Wimpress
** Changed in: tiff (Ubuntu)
 Assignee: (unassigned) => Olivier Tilloy (osomon)

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

Title:
  [MIR] libtiff5 dependency on libdeflate0

Status in libdeflate package in Ubuntu:
  Incomplete
Status in tiff package in Ubuntu:
  Confirmed

Bug description:
  tiff 4.1.0+git201212-1 enabled deflate support, adding libdeflate0 as
  a dependency to libtiff5, making the package uninstallable.

  Therefor I uploaded 4.1.0+git201212-1ubuntu1 disabling the deflate
  support to make libtiff5 installable again.

  Either this package stays this way, or it needs a MIR for libdeflate.

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

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


[Touch-packages] [Bug 1870508] Re: ubiquity crashed with SIGSEGV in g_type_check_instance_is_a()

2020-12-08 Thread Martin Wimpress
** Changed in: gtk+3.0 (Ubuntu)
   Status: New => Invalid

** No longer affects: gtk+3.0 (Ubuntu)

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

Title:
  ubiquity crashed with SIGSEGV in g_type_check_instance_is_a()

Status in ATK:
  Unknown
Status in atk1.0 package in Ubuntu:
  Fix Released

Bug description:
  == Test Case ==
  1. Boot to ubiquity-dm
  2. Enable the screenreader (Alt+Super+S)
  3. Select "Install Ubuntu"
  4. Proceed with all the steps of the installer

  = Actual Result = 
  During installation, when the slideshow is running, this crash occurs.

  
  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: ubiquity 20.04.9
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CasperVersion: 1.442
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  3 10:55:58 2020
  ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
  ExecutableTimestamp: 1585729537
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed initrd=/casper/initrd quiet 
splash --- maybe-ubiquity
  InterpreterPath: /usr/bin/python3.8
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcCmdline: /usr/bin/python3 /usr/lib/ubiquity/bin/ubiquity --greeter --only
  ProcCwd: /
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu1
  PythonDetails: N/A
  SegvAnalysis:
   Segfault happened at: 0x7fbd15f8f16a :   
mov%rax,-0x20(%rsp)
   PC (0x7fbd15f8f16a) ok
   source "%rax" ok
   destination "-0x20(%rsp)" (0x7ffe329d3ff0) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: ubiquity
  StacktraceTop:
   g_type_check_instance_is_a () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   atk_component_get_extents () from /lib/x86_64-linux-gnu/libatk-1.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0
   atk_component_get_extents () from /lib/x86_64-linux-gnu/libatk-1.0.so.0
   atk_component_get_extents () from /lib/x86_64-linux-gnu/libatk-1.0.so.0
  Title: ubiquity crashed with SIGSEGV in g_type_check_instance_is_a()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  separator:

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

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


[Touch-packages] [Bug 1901272] Re: Can't connect Bluetooth devices after reboot - Ubuntu 20.10 on Raspberry Pi 4

2020-10-27 Thread Martin Wimpress
** Changed in: pi-bluetooth (Ubuntu)
 Assignee: (unassigned) => Dave Jones (waveform)

** Changed in: pi-bluetooth (Ubuntu Groovy)
 Assignee: (unassigned) => Dave Jones (waveform)

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

Title:
  Can't connect Bluetooth devices after reboot - Ubuntu 20.10 on
  Raspberry Pi 4

Status in bluez package in Ubuntu:
  Confirmed
Status in linux-raspi package in Ubuntu:
  Confirmed
Status in pi-bluetooth package in Ubuntu:
  Confirmed
Status in bluez source package in Groovy:
  New
Status in linux-raspi source package in Groovy:
  New
Status in pi-bluetooth source package in Groovy:
  New

Bug description:
  Raspberry pi 4 4Gb ram
  Ubuntu desktop 20.10 64 bit
  After reboot no Bluetooth devices connect, scanning Bluetooth devices works, 
results with same device name (duplicated and with not set up status).
  Sometimes after several reboots it works.
  If I use power off and cycle power then it works fine each time.

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

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


[Touch-packages] [Bug 1896073] Re: SRU the current 2.3.6 stable update

2020-10-27 Thread Martin Wimpress
** Changed in: tracker (Ubuntu Focal)
 Assignee: (unassigned) => Sebastien Bacher (seb128)

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

Title:
  SRU the current 2.3.6 stable update

Status in tracker package in Ubuntu:
  Fix Released
Status in tracker source package in Focal:
  Fix Committed

Bug description:
  * Impact
  That's the current GNOME stable update, including some fixes and translation 
updates
  https://gitlab.gnome.org/GNOME/tracker/-/blob/tracker-2.3/NEWS

  The update add a 'tracker export' command, that's new and not used
  into any integration so has no real regression potential. It's an
  optional new option that can be used to export the data to migrate
  them to the incoming tracker3.

  * Test case

  The update is part of GNOME stable updates
  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  Check that file search works correctly from the command line, shell
  and nautilus

  * Regression potential

  There is no specific change or feature to test in that update

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

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


[Touch-packages] [Bug 1894606] Re: [SRU] Add profile-set for HP Thunderbolt Dock

2020-09-08 Thread Martin Wimpress
** Changed in: pulseaudio (Ubuntu Groovy)
 Assignee: (unassigned) => Sebastien Bacher (seb128)

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

Title:
  [SRU] Add profile-set for HP Thunderbolt Dock

Status in HWE Next:
  New
Status in pulseaudio package in Ubuntu:
  In Progress
Status in pulseaudio source package in Focal:
  In Progress
Status in pulseaudio source package in Groovy:
  In Progress

Bug description:
  [Impact]
  HP Thunderbolt Dock has a USB audio device provides headset connector 
functionality. The Dock can also attach an optional USB audio module. Since 
they are both USB audio device, the input/output names are the same and it 
confuses user.

  [Fix]
  Add PulseAudio profile-sets for each USB device with different monikers.

  The merge request is already approved by maintainer, will be merged after 
14.0 release:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/353

  [Test]
  With profile-set applied, two different USB audio device on HP TBT Dock have 
distinctive names.

  [Regression Potential]
  Currently I can't think of any regression risk, as this SRU only adds new 
profile-sets and description translation.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1894606/+subscriptions

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


[Touch-packages] [Bug 1894606] Re: [SRU] Add profile-set for HP Thunderbolt Dock

2020-09-08 Thread Martin Wimpress
** Changed in: pulseaudio (Ubuntu Focal)
 Assignee: (unassigned) => Sebastien Bacher (seb128)

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

Title:
  [SRU] Add profile-set for HP Thunderbolt Dock

Status in HWE Next:
  New
Status in pulseaudio package in Ubuntu:
  In Progress
Status in pulseaudio source package in Focal:
  In Progress
Status in pulseaudio source package in Groovy:
  In Progress

Bug description:
  [Impact]
  HP Thunderbolt Dock has a USB audio device provides headset connector 
functionality. The Dock can also attach an optional USB audio module. Since 
they are both USB audio device, the input/output names are the same and it 
confuses user.

  [Fix]
  Add PulseAudio profile-sets for each USB device with different monikers.

  The merge request is already approved by maintainer, will be merged after 
14.0 release:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/353

  [Test]
  With profile-set applied, two different USB audio device on HP TBT Dock have 
distinctive names.

  [Regression Potential]
  Currently I can't think of any regression risk, as this SRU only adds new 
profile-sets and description translation.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1894606/+subscriptions

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


[Touch-packages] [Bug 1841356] Re: username crashed with SIGSEGV in meta_display_list_windows()

2020-08-17 Thread Martin Wimpress
*** This bug is a duplicate of bug 1871716 ***
https://bugs.launchpad.net/bugs/1871716

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

** This bug has been marked a duplicate of bug 1871716
   marco crashed with SIGSEGV in meta_frame_calc_borders()

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

Title:
  username crashed with SIGSEGV in meta_display_list_windows()

Status in glib2.0 package in Ubuntu:
  Invalid
Status in marco package in Ubuntu:
  Confirmed

Bug description:
  No more information about the crash

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: marco 1.22.2-0ubuntu2
  ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4
  Uname: Linux 5.2.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sun Aug 25 10:05:35 2019
  ExecutablePath: /usr/bin/marco
  InstallationDate: Installed on 2019-08-24 (0 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Alpha amd64 (20190824)
  ProcCmdline: username
  ProcEnviron:
   LANGUAGE=it_IT
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7fb31bfc8dc1 : mov
0x388(%rdi),%rdi
   PC (0x7fb31bfc8dc1) ok
   source "0x388(%rdi)" (0x0388) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: marco
  StacktraceTop:
   meta_display_list_windows () from /lib/x86_64-linux-gnu/libmarco-private.so.2
   meta_display_queue_retheme_all_windows () from 
/lib/x86_64-linux-gnu/libmarco-private.so.2
   ?? () from /lib/x86_64-linux-gnu/libmarco-private.so.2
   g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: username crashed with SIGSEGV in meta_display_list_windows()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1841356/+subscriptions

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


[Touch-packages] [Bug 1865226] Re: gdm-smartcard pam config needs to be updated for Ubuntu and installed

2020-07-14 Thread Martin Wimpress
** Changed in: gdm3 (Ubuntu)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

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

Title:
  gdm-smartcard pam config needs to be updated for Ubuntu and installed

Status in gdm:
  New
Status in gdm3 package in Ubuntu:
  Confirmed
Status in pam package in Ubuntu:
  Invalid

Bug description:
  the pam profile for gdm-smartcard is missing. gdm refuses to login
  with a smartcard. Looking at ubuntu/+source/gdm3, other pam files are
  pregenerated into debian/ and installed from there; gdm-smartcard is
  left out.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.3-0ubuntu18.04.4
  ProcVersionSignature: Ubuntu 5.3.0-24.26~18.04.2-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 28 14:30:30 2020
  InstallationDate: Installed on 2016-05-23 (1376 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.gdm3.Xsession: 2018-04-27T11:41:04.766901

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

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


[Touch-packages] [Bug 1886314] Re: preinstall `earlyoom` by default

2020-07-14 Thread Martin Wimpress
** Changed in: ubuntu-meta (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  preinstall `earlyoom` by default

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Fedora done this https://fedoraproject.org/wiki/Changes/EnableEarlyoom

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

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


[Touch-packages] [Bug 1876065] Re: After unplug headphones and plug them again no sound can be heard

2020-06-02 Thread Martin Wimpress
** Changed in: pulseaudio (Ubuntu Focal)
 Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng)

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

Title:
  After unplug headphones and plug them again no sound can be heard

Status in pulseaudio package in Ubuntu:
  Fix Committed
Status in pulseaudio source package in Focal:
  Fix Committed
Status in pulseaudio source package in Groovy:
  Fix Committed

Bug description:
  * Impact
  Sound isn't automatically redirected to headphones when those are connected 
to a jack interface

  * Test case
  Disconnect the headsets
  Start your webbrowser/music player/video player and play some sound
  Connect the headsets to the jack interface

  -> the sound should be directly redirected to the plugged headsets

  * Regression potential
  Check that audio routing when connecting/disconnecting devices to the hack 
entry is working correctly

  

  After startup with headset plugged in they play sound nicely - no
  issue. When they are unplugged, the sound is switched to the speaker
  (laptop) - all good. However, when I plug the headset back there is no
  sound. I see the app on pavucontrol, the volume is fine - everything
  looks fine except there is no sound. I dumped output of "pactl list"
  command on startup (headset plugged), after unplugging the headset,
  and when it is plugged back. From the comparison of these outputs, it
  looks like the source has got muted after the headset is plugged.

  Source #1
   State: RUNNING
   Name: alsa_input.pci-_00_1f.3.analog-stereo
   Description: Built-in Audio Analog Stereo
   Driver: module-alsa-card.c
   Sample Specification: s16le 2ch 44100Hz
   Channel Map: front-left,front-right
   Owner Module: 7
   Mute: yes

  Attached three outputs:
  headset-in.txt - after startup with headset plugged - all fine.
  headset-out.txt - after unplugged headset - sound through the speaker - all 
fine.
  headset-back.txt - after plugged headset back - no sound.

  Any help greatly appreciated.

  Regards,
  Roman

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

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


[Touch-packages] [Bug 1864307] Re: Many apps have no icon in Software on Focal

2020-06-02 Thread Martin Wimpress
** Changed in: gnome-software (Ubuntu)
 Assignee: (unassigned) => Ken VanDine (ken-vandine)

** Changed in: gnome-software (Ubuntu Focal)
 Assignee: (unassigned) => Ken VanDine (ken-vandine)

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

Title:
  Many apps have no icon in Software on Focal

Status in GNOME Software:
  Unknown
Status in snap-store:
  Fix Released
Status in gnome-software package in Ubuntu:
  Triaged
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in gnome-software source package in Focal:
  Triaged
Status in ubuntu-meta source package in Focal:
  Fix Released

Bug description:
  Many applications have no icon displayed in GNOME Software 3.35.91 on
  latest Ubuntu Focal. See the attached screenshot.

  
  [Impact] 

   * Some apt packages do not include an icon in snap-store

  [Test Case]

   * Open snap-store, search for GCompris and confirm there is an
  appropriate icon

  [Regression Potential]

   * Very low.  Previous Ubuntu releases including apt-config-icons
  based on the depends in gnome-software.  This just adds an apt config
  that can be used to fetch icons for apt packages via apt.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-software/+bug/1864307/+subscriptions

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


[Touch-packages] [Bug 1871329] Re: No "Select Audio Device" panel when plugging headphones, and no sound output to headphones

2020-04-07 Thread Martin Wimpress
** Changed in: pulseaudio (Ubuntu)
 Assignee: (unassigned) => Sebastien Bacher (seb128)

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

Title:
  No "Select Audio Device" panel when plugging headphones, and no sound
  output to headphones

Status in pulseaudio package in Ubuntu:
  New

Bug description:

  
  Summary
  ===

  Internal speakers work as expected, but when plugging headphones
  through the 3.5mm jack, the "Select Audio Device" panel doesn't show
  up (it normally shows up to allow user to select what kind of device
  has been plugged in, be it headphones, microphone or headset). In the
  Sound Settings, the Output Device automatically switches to
  "Headphones - sof-hda-dsp", but no sound can be heard even though the
  vumeter in the Sound Settings moves!

  Steps to reproduce
  ==

  1. Install focal beta
  2. Make sure the sound works as expected using the internal speakers and an 
audio file or Youtube
  3. Plug headphones in jack 3.5mm interface

  Expected Results
  

  - In Sound Settings, the headphones are automatically selected as output 
device
  - In Sound Settings, the vumeter under the Output Device moves according to 
the sound
  - Sound can be heard through the headphones

  
  Actual results
  ==

  - In Sound Settings, the headphones are automatically selected as output 
device (OK)
  - In Sound Settings, the vumeter under the Output Device moves according to 
the sound (OK)
  - No sound can be heard (Not OK)

  Attached are output of `pactl info` and `pactl list` before and after
  plugging headphones, while playing a tune on Bandcamp in Firefox.

  
  Additional Info
  ===

  Ubuntu: 20.04 beta image
  Certified device: 
  system-manufacturer: Dell Inc.
  system-product-name: Vostro 5590
  bios-version: 1.1.0
  CPU: Intel(R) Core(TM) i5-10210U CPU @ 1.60GHz (8x)
  GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:9b41] (rev 02)
  01:00.0 3D controller [0302]: NVIDIA Corporation Device [10de:1d13] (rev a1)
  kernel-version: 5.4.0-21-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pieq   1768 F pulseaudio
   /dev/snd/pcmC0D0p:   pieq   1768 F...m pulseaudio
   /dev/snd/pcmC0D6c:   pieq   1768 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  7 16:33:27 2020
  InstallationDate: Installed on 2020-04-07 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/18/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.0:bd07/18/2019:svnDellInc.:pnVostro5590:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 5590
  dmi.product.sku: 095A
  dmi.sys.vendor: Dell Inc.

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

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


[Touch-packages] [Bug 1843982] Re: Various programs crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from update_user()

2020-04-07 Thread Martin Wimpress
** Changed in: accountsservice (Ubuntu)
 Assignee: (unassigned) => Iain Lane (laney)

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

Title:
  Various programs crashed with SIGSEGV in g_str_hash() from
  g_hash_table_lookup() from update_user()

Status in accountsservice:
  New
Status in accountsservice package in Ubuntu:
  Triaged
Status in accountsservice package in Debian:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/3a817938d76d231fdfc8f698392fbf5e3724084f

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 14 10:29:16 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2019-05-24 (112 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190523)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=nb_NO.UTF-8
   LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.34.0-2ubuntu1
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   g_str_hash () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libaccountsservice.so.0
   g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-shell crashed with SIGSEGV in g_str_hash()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

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

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


[Touch-packages] [Bug 1870508] Re: ubiquity crashed with SIGSEGV in g_type_check_instance_is_a()

2020-04-07 Thread Martin Wimpress
** Changed in: atk1.0 (Ubuntu)
 Assignee: (unassigned) => Marcus Tomlinson (marcustomlinson)

** Changed in: ubiquity (Ubuntu)
 Assignee: (unassigned) => Marcus Tomlinson (marcustomlinson)

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

Title:
  ubiquity crashed with SIGSEGV in g_type_check_instance_is_a()

Status in atk1.0 package in Ubuntu:
  Confirmed
Status in ubiquity package in Ubuntu:
  Confirmed

Bug description:
  == Test Case ==
  1. Boot to ubiquity-dm
  2. Enable the screenreader (Alt+Super+S)
  3. Select "Install Ubuntu"
  4. Proceed with all the steps of the installer

  = Actual Result = 
  During installation, when the slideshow is running, this crash occurs.

  
  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: ubiquity 20.04.9
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CasperVersion: 1.442
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  3 10:55:58 2020
  ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
  ExecutableTimestamp: 1585729537
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed initrd=/casper/initrd quiet 
splash --- maybe-ubiquity
  InterpreterPath: /usr/bin/python3.8
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcCmdline: /usr/bin/python3 /usr/lib/ubiquity/bin/ubiquity --greeter --only
  ProcCwd: /
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu1
  PythonDetails: N/A
  SegvAnalysis:
   Segfault happened at: 0x7fbd15f8f16a :   
mov%rax,-0x20(%rsp)
   PC (0x7fbd15f8f16a) ok
   source "%rax" ok
   destination "-0x20(%rsp)" (0x7ffe329d3ff0) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: ubiquity
  StacktraceTop:
   g_type_check_instance_is_a () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   atk_component_get_extents () from /lib/x86_64-linux-gnu/libatk-1.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0
   atk_component_get_extents () from /lib/x86_64-linux-gnu/libatk-1.0.so.0
   atk_component_get_extents () from /lib/x86_64-linux-gnu/libatk-1.0.so.0
  Title: ubiquity crashed with SIGSEGV in g_type_check_instance_is_a()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/atk1.0/+bug/1870508/+subscriptions

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


[Touch-packages] [Bug 1733321] Re: network-manager ADT tests fail with on ppc64el with artful/linux 4.13.0.17.18

2020-04-07 Thread Martin Wimpress
** Changed in: network-manager (Ubuntu Eoan)
   Status: New => Won't Fix

** Tags removed: artful

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

Title:
  network-manager ADT tests fail with on ppc64el with artful/linux
  4.13.0.17.18

Status in network-manager package in Ubuntu:
  New
Status in network-manager source package in Artful:
  Won't Fix
Status in network-manager source package in Disco:
  Won't Fix
Status in network-manager source package in Eoan:
  Won't Fix
Status in network-manager source package in Focal:
  New

Bug description:
  [Impact]

  The killswitches-no-urfkill autopkgtest fails sometimes because nmcli
  reports the old state when it's called right after rfkill
  block/unblock. Adding a sleep before calling nmcli fixes the issue.

  ppc64el ADT log from failed testcase:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-artful/artful/ppc64el/n/network-
  manager/20171120_100719_28642@/log.gz

  Testcase output:
  -
  autopkgtest [10:04:48]: test killswitches-no-urfkill: [---
  make -C /lib/modules/4.13.0-17-generic/build 
KBUILD_SRC=/lib/modules/4.13.0-17-generic/build 
M=/tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests
  make[1]: Entering directory '/usr/src/linux-headers-4.13.0-17-generic'
    AR  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/built-in.o
    CC [M]  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.o
    Building modules, stage 2.
    MODPOST 1 modules
    CC  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.mod.o
    LD [M]  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.ko
  make[1]: Leaving directory '/usr/src/linux-headers-4.13.0-17-generic'
  ERROR: NM could not track device state.
  autopkgtest [10:05:20]: test killswitches-no-urfkill: ---]
  autopkgtest [10:05:20]: test killswitches-no-urfkill:  - - - - - - - - - - 
results - - - - - - - - - -
  killswitches-no-urfkill FAIL non-zero exit status 1
  -

  Package versions [artful/ppc64el]:
  network-manager 1.8.4-1ubuntu3
  linux-meta 4.13.0.17.18

  
  [Test Case]

  2.1. Download network-manager package source code
  $ apt-get source network-manager

  2.2. Run killswitches-no-urfkill testcase
  $ cd network-manager-1.8.4
  $ sudo ./debian/tests/killswitches-no-urfkill

  
  [Regression Potential]

  No regression potential. The fix touches only the testcase shipped
  with the source package and it doesn't change the binary package. The
  sleep time added is very small, so no possibility of causing testcase
  timeout.

  
  [Other Info]

  On ppc64el architecture, it was observed that a fix for systemd is
  also needed (see bug 1734908) for the testcase to be successful.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1733321/+subscriptions

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


[Touch-packages] [Bug 1715931] Re: Update to exiv2 version 0.27

2020-03-24 Thread Martin Wimpress
** Changed in: exiv2 (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

Title:
  Update to exiv2 version 0.27

Status in exiv2 package in Ubuntu:
  Fix Released
Status in exiv2 source package in Focal:
  Fix Released
Status in exiv2 package in Debian:
  Fix Released

Bug description:
  0.26 was released in April

  http://www.exiv2.org/whatsnew.html

  "This release contains a large collection of new features, new lenses
  and bugfixes across all areas of Exiv2. "

  Presumably debian stretch freeze interfered with a prompter update

  Currently in debian exp here:

  https://packages.debian.org/experimental/exiv2

  I was hoping to to get a new feature release of the very popular
  Digikam (5.7.0) into artful under a FFE, but that has bumped the
  minimum exiv2 build depend from 0.25 -> 0.26.

  If due to rdeps etc an update in artful turns out not to be possible,
  I would like to target this for early in 18.04 LTS cycle.

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

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


[Touch-packages] [Bug 1866841] Re: Add chrome-gnome-shell to ubuntu-desktop recommends

2020-03-24 Thread Martin Wimpress
We won't be adding chrome-gnome-shell to the default install since the
new Extension manager features in GNOME 3.36 to provide this
functionality.

** Changed in: chrome-gnome-shell (Ubuntu)
   Status: New => Invalid

** Changed in: hundredpapercuts
   Status: New => Opinion

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

Title:
  Add chrome-gnome-shell to ubuntu-desktop recommends

Status in One Hundred Papercuts:
  Opinion
Status in chrome-gnome-shell package in Ubuntu:
  Invalid
Status in ubuntu-meta package in Ubuntu:
  Opinion

Bug description:
  Please, consider adding the chrome-gnome-shell package as a
  recommended dependency for ubuntu-desktop package in Ubuntu 20.04. The
  chrome-gnome-shell package provides GNOME Shell integration
  (connector) for Firefox, Chrome, Chromium and other web browsers that
  is necessary for users to be able to manage GNOME Shell extensions
  using a extensions.gnome.org website. Since the Shell Extensions
  support was removed from gnome-software since 3.36 and the replacement
  Extensions application cannot be used to find and install new
  extensions, there is not any user friendly way to install new Shell
  Extensions without having the chrome-gnome-shell package installed.

  More information:
  https://wiki.gnome.org/Projects/GnomeShellIntegrationForChrome

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

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


[Touch-packages] [Bug 1715931] Re: Update to exiv2 version 0.27

2020-03-24 Thread Martin Wimpress
Closed via https://launchpad.net/ubuntu/+source/exiv2/0.27.2-8ubuntu2

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

Title:
  Update to exiv2 version 0.27

Status in exiv2 package in Ubuntu:
  Fix Committed
Status in exiv2 source package in Focal:
  Fix Committed
Status in exiv2 package in Debian:
  Fix Released

Bug description:
  0.26 was released in April

  http://www.exiv2.org/whatsnew.html

  "This release contains a large collection of new features, new lenses
  and bugfixes across all areas of Exiv2. "

  Presumably debian stretch freeze interfered with a prompter update

  Currently in debian exp here:

  https://packages.debian.org/experimental/exiv2

  I was hoping to to get a new feature release of the very popular
  Digikam (5.7.0) into artful under a FFE, but that has bumped the
  minimum exiv2 build depend from 0.25 -> 0.26.

  If due to rdeps etc an update in artful turns out not to be possible,
  I would like to target this for early in 18.04 LTS cycle.

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

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


[Touch-packages] [Bug 1866841] Re: Add chrome-gnome-shell to ubuntu-desktop recommends

2020-03-24 Thread Martin Wimpress
** Changed in: ubuntu-meta (Ubuntu)
 Assignee: (unassigned) => Martin Wimpress (flexiondotorg)

** Changed in: ubuntu-meta (Ubuntu)
   Status: New => Opinion

** Tags removed: rls-ff-incoming
** Tags added: rls-notfixing

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

Title:
  Add chrome-gnome-shell to ubuntu-desktop recommends

Status in One Hundred Papercuts:
  New
Status in chrome-gnome-shell package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  Opinion

Bug description:
  Please, consider adding the chrome-gnome-shell package as a
  recommended dependency for ubuntu-desktop package in Ubuntu 20.04. The
  chrome-gnome-shell package provides GNOME Shell integration
  (connector) for Firefox, Chrome, Chromium and other web browsers that
  is necessary for users to be able to manage GNOME Shell extensions
  using a extensions.gnome.org website. Since the Shell Extensions
  support was removed from gnome-software since 3.36 and the replacement
  Extensions application cannot be used to find and install new
  extensions, there is not any user friendly way to install new Shell
  Extensions without having the chrome-gnome-shell package installed.

  More information:
  https://wiki.gnome.org/Projects/GnomeShellIntegrationForChrome

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

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


[Touch-packages] [Bug 1478173] Re: Ambiance & Radiance themes are missing a "background-color" for tooltip elements (needed for GTK3-enabled Firefox Nightly)

2020-02-27 Thread Martin Wimpress
** Changed in: ubuntu-themes (Ubuntu)
 Assignee: Martin Wimpress (flexiondotorg) => (unassigned)

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

Title:
  Ambiance & Radiance themes are missing a "background-color" for
  tooltip elements (needed for GTK3-enabled Firefox Nightly)

Status in One Hundred Papercuts:
  Confirmed
Status in Ubuntu theme:
  In Progress
Status in ubuntu-themes package in Ubuntu:
  In Progress

Bug description:
  Firefox Nightlies recently became GTK3-enabled, and that uncovered an
  issue with Ubuntu's Ambiance & Radiance GTK3 themes.

  They're missing a "background-color" for the .tooltip {...} CSS rule
  in their config files. They have a "tooltip_bg_color" variable, which
  they use to set up a background-image (really a gradient), but there's
  no background-color.

  This causes problems for GTK3-enabled Firefox, because it reads back some 
system-colors by setting up a dummy tooltip and reading the 
(currently-not-useful) background-color and the foreground-color. Right now, 
this produces unreadable output (for the user) with 
white-text-on-a-white-background, as shown in this screenshot:
   https://bug1187203.bmoattachments.org/attachment.cgi?id=8638351

  The solution is simple -- just add this one line to the ".tooltip" CSS rule 
in gtk-widgets.css:
 background-color: @tooltip_bg_color;

  For more details, see bug
  https://bugzilla.mozilla.org/show_bug.cgi?id=1187203

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: light-themes 14.04+15.04.20150410-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-23.24-generic 3.19.8-ckt2
  Uname: Linux 3.19.0-23-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Jul 24 17:35:25 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-05-18 (67 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1641915] Re: GtkToolButtons clip and overlap

2020-02-27 Thread Martin Wimpress
** Changed in: ubuntu-themes (Ubuntu Xenial)
 Assignee: Martin Wimpress (flexiondotorg) => (unassigned)

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

Title:
  GtkToolButtons clip and overlap

Status in Ubuntu theme:
  Fix Released
Status in ubuntu-themes package in Ubuntu:
  Fix Released
Status in ubuntu-themes source package in Xenial:
  In Progress

Bug description:
  [ Impact ]

  GtkToolButton styling causes buttons to clip and overlap each other. This
  can be seen in gnome-disks and the Ubiquity disk partitioner for Ubuntu 
16.04.1. See the attached screenshot:

    * https://bugs.launchpad.net/ubuntu-
  themes/+bug/1641915/+attachment/4777652/+files/gtk-toolbutton-
  clipping.png

  [ Test Case ]

  Start a Ubuntu 16.04.1 live session and "Try Ubuntu". From the live
  Desktop click the Ubuntu logo in the launcher, search for Disks and
  start it. Select the hard disk from the side panel, then look at and
  hover over, the buttons beneath the representation of the disk
  partitions. You'll notice the buttons clip/overlap as illustrated in
  the screenshot above.

  Now double click the "Install Ubuntu 16.04.1 LTS" icon on the desktop.
  The Installer will start, click Continue, click Continue, check
  "Something else" and then the click Continue. Look at, and hover over,
  the buttons beneath the tree representing the disk partitions. You'll
  notice they clip/overlap as illustrated in the screenshot above.

  After the patched ubuntu-themes has been installed the buttons
  described in the steps above will no longer clip/overlap.

  [ Regression Potential ]

  None expected.

  [ Other Info ]

  This issue does not present in Yakkety or Zesty.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1641915/+subscriptions

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


[Touch-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support.

2020-02-18 Thread Martin Wimpress
** Tags removed: champagne
** Tags added: desktop-lts-wishlist rls-ff-notfixing

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

Title:
  Poor quality audio with modern Bluetooth headsets in HSP/HFP.  Missing
  wide band speech support.

Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Triaged
Status in Arch Linux:
  New

Bug description:
  Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all
  other major platforms (Windows, MacOS, ChromeOS, Android, iOS).

  Modern Bluetooth headsets (such as the Bose QC series headphones, many
  others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding.
  As it currently stands, Ubuntu defaults to only supporting HSP
  headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at
  this time.

  The ChromiumOS team recently tackled this issue -
  https://bugs.chromium.org/p/chromium/issues/detail?id=843048

  Their efforts may assist in bringing this to Ubuntu, however it
  appears that there are quite a lot of differences considering they
  have developed their own audio server solution etc.

  The Bluetooth Telephony Working Group published the HFP 1.6 spec in
  May 2011 -
  https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193

  Patches have been proposed in the past for this issue to the kernel
  and PulseAudio:

  PulseAudio: https://patchwork.freedesktop.org/patch/245272/
  Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html

  It appears that the Chromium OS team applied the same kernel patch:
  
https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu3
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jnappi 2777 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul 27 11:08:29 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-04 (629 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago)
  dmi.bios.date: 06/07/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R07ET67W (2.07 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FW000TUS
  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:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460p
  dmi.product.name: 20FW000TUS
  dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p
  dmi.product.version: ThinkPad T460p
  dmi.sys.vendor: LENOVO

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

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


[Touch-packages] [Bug 1861481] Re: language-options causes live CD sessions to be untranslated

2020-02-15 Thread Martin Wimpress
** Changed in: lightdm (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  language-options causes live CD sessions to be untranslated

Status in lightdm package in Ubuntu:
  Fix Released

Bug description:
  Since Ubuntu 19.10, for all Ubuntu live CDs that use LightDM (e.g.
  MATE and Xubuntu), if a user selects a language in syslinux other than
  those with an included langpack, the session is then untranslated.

  For example, if one boots Ubuntu MATE 20.04 and selects Greek in
  syslinux, he ends up with LANGUAGE=en in the session.

  The chain of events is:
  LightDM has an Ubuntu-specific patch that makes it call 
/usr/share/language-tools/language-options instead of the upstream `locale -a`.
  `locale -a` does list el_GR as a supported locale because casper correctly 
updated the locales.
  But language-options doesn't list el_GR, so it fools LightDM into thinking 
that Greek aren't supported; while they're all there, since e.g. MATE doesn't 
rely on langpacks; mate-panel.mo and mate-calc.mo etc are all there.

  I believe the correct fix would be for language-options to list el_GR
  on live CDs (to merge the output of locale -a in its output).

  Thanks!

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

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


[Touch-packages] [Bug 1856054] Re: pulseaudio now depends on libsnapd-glib1 which recommends snapd

2019-12-17 Thread Martin Wimpress
This issue is being addressed via https://pad.lv/1856196

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

Title:
  pulseaudio now depends on libsnapd-glib1 which recommends snapd

Status in pulseaudio package in Ubuntu:
  Won't Fix

Bug description:
  The latest update for pulseaudio (1:11.1-1ubuntu7.5) in bionic now has
  libsnapd-glib1 as a dependency.

  This is complete and utter nonsense. I do not want cascading
  dependencies that have no business being installed on the systems I
  manage.

  Please rectify this at once.

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

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


[Touch-packages] [Bug 1633319] Re: memory leak in indicator-datetime

2019-10-22 Thread Martin Wimpress
** Tags removed: yakkety
** Tags added: rls-ee-incoming

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

Title:
  memory leak in indicator-datetime

Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from 16.04 to 16.10 on the System76 Serval WS
  indicator-datetime-service is consuming all the system memory from
  3.7GB up to 32 GB in 30 seconds. The system kills the indicator-
  datetime-service process and indicator-datetime-service restarts and
  memory consumption repeats until killed again. All swap memory is
  consumed in this pattern.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: indicator-datetime 15.10+16.10.20160820.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Oct 14 00:12:00 2016
  EcryptfsInUse: Yes
  SourcePackage: indicator-datetime
  UpgradeStatus: Upgraded to yakkety on 2016-10-14 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1633319/+subscriptions

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


[Touch-packages] [Bug 1847739] Re: Make zfs-initramfs and zfsutils-linux install optional

2019-10-12 Thread Martin Wimpress
** Changed in: ubuntu-mate-meta (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  Make zfs-initramfs and zfsutils-linux install optional

Status in ubiquity package in Ubuntu:
  Fix Released
Status in ubuntu-budgie-meta package in Ubuntu:
  Fix Released
Status in ubuntu-mate-meta package in Ubuntu:
  Fix Committed
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntustudio-meta package in Ubuntu:
  Fix Released
Status in xubuntu-meta package in Ubuntu:
  New

Bug description:
  Move those 2 to the live seed to have them available in the installer.

  Mark them then manually installed in the installer if needed. Then,
  ubiquity will purge them if not used.

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

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


[Touch-packages] [Bug 1847739] Re: Make zfs-initramfs and zfsutils-linux install optional

2019-10-12 Thread Martin Wimpress
** Changed in: ubuntu-mate-meta (Ubuntu)
   Status: New => In Progress

** Changed in: ubuntu-mate-meta (Ubuntu)
 Assignee: (unassigned) => Martin Wimpress (flexiondotorg)

** Changed in: ubuntu-mate-meta (Ubuntu)
   Importance: Undecided => High

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

Title:
  Make zfs-initramfs and zfsutils-linux install optional

Status in ubiquity package in Ubuntu:
  Fix Released
Status in ubuntu-budgie-meta package in Ubuntu:
  Fix Released
Status in ubuntu-mate-meta package in Ubuntu:
  In Progress
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntustudio-meta package in Ubuntu:
  Fix Released
Status in xubuntu-meta package in Ubuntu:
  New

Bug description:
  Move those 2 to the live seed to have them available in the installer.

  Mark them then manually installed in the installer if needed. Then,
  ubiquity will purge them if not used.

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

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


[Touch-packages] [Bug 1847431] Re: Installing ZFS without network is failing

2019-10-09 Thread Martin Wimpress
** Changed in: ubuntu-mate-meta (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  Installing ZFS without network is failing

Status in ubiquity package in Ubuntu:
  Fix Released
Status in ubuntu-budgie-meta package in Ubuntu:
  New
Status in ubuntu-mate-meta package in Ubuntu:
  Fix Committed
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntustudio-meta package in Ubuntu:
  New

Bug description:
  We need to:
  * seed zfs-initramfs
  * remove apt install from ubiquity zfs script.

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

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


[Touch-packages] [Bug 1847431] Re: Installing ZFS without network is failing

2019-10-09 Thread Martin Wimpress
** Changed in: ubuntu-mate-meta (Ubuntu)
   Status: New => In Progress

** Changed in: ubuntu-mate-meta (Ubuntu)
   Importance: Undecided => Medium

** Changed in: ubuntu-mate-meta (Ubuntu)
 Assignee: (unassigned) => Martin Wimpress (flexiondotorg)

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

Title:
  Installing ZFS without network is failing

Status in ubiquity package in Ubuntu:
  Fix Released
Status in ubuntu-budgie-meta package in Ubuntu:
  New
Status in ubuntu-mate-meta package in Ubuntu:
  In Progress
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntustudio-meta package in Ubuntu:
  New

Bug description:
  We need to:
  * seed zfs-initramfs
  * remove apt install from ubiquity zfs script.

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

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


[Touch-packages] [Bug 1847431] Re: Installing ZFS without network is failing

2019-10-09 Thread Martin Wimpress
** Also affects: ubuntu-budgie-meta (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: ubuntustudio-meta (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Installing ZFS without network is failing

Status in ubiquity package in Ubuntu:
  New
Status in ubuntu-budgie-meta package in Ubuntu:
  New
Status in ubuntu-mate-meta package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  New
Status in ubuntustudio-meta package in Ubuntu:
  New

Bug description:
  We need to:
  * seed zfs-initramfs
  * remove apt install from ubiquity zfs script.

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

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


[Touch-packages] [Bug 1843768] Re: [FFe] Ubiquity with zfs install option

2019-10-04 Thread Martin Wimpress
** Changed in: ubuntu-mate-meta (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  [FFe] Ubiquity with zfs install option

Status in ubiquity package in Ubuntu:
  New
Status in ubuntu-mate-meta package in Ubuntu:
  Fix Committed
Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Part of the 19.10 feature announcement is zfs experimental support in
  the installer (https://ubuntu.com/blog/enhancing-our-zfs-support-on-
  ubuntu-19-10-an-introduction). We modified ubiquity to present an
  “EXPERIMENTAL” (with warning) ZSYS install option. This option is only
  visible is zfsutils-linux is installed on the system. So, it won't be
  available for derivatives that use ubiquity but do not seed zfsutils-
  linux.

  Update as of 20/09/2019: the plan is to not seed zsys (security review
  will take a while), but to only seed zfsutils-linux. People can then
  opt-in to zsys which should be available by default next cycle.

  This option takes an entire disk and have a fix set of dataset
  installed. There is no support but we need this to make an official
  install option for the next LTS.

  The patch has been created to be as minimal as possible. Partman does
  a full disk partitioning, and then the script zsys-setup the first
  non-ESP partition and replaces with zfs pools.

  4 partitions are created:
  1. if GPT partitioning: ESP partition. This one is done by partman directly.
  2. bpool (for boot), pool with older zfs compatible version to be readable by 
grub)
  3. rpool (for / and userdataset)
  4. /boot/grub (ext4) to contain a single grub (NOTE: this could be later on 
moved to the ESP)

  Additionaly if a swap file has been created by ubiquity, it is
  recreated as a ZFS volume. If the script fails to execute, the final
  installation is an ext4 installation on entire disk.

  Note that the implementation is slightly different from the
  specification due to a difficult cohabitation with partman in the
  custom partitioning page.

  Please find attached the MP on ubiquity as well as the package build
  log.

  https://launchpadlibrarian.net/442036321/buildlog_ubuntu-eoan-
  amd64.ubiquity_19.10.10~ppa1_BUILDING.txt.gz

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

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


[Touch-packages] [Bug 1843768] Re: [FFe] Ubiquity with zfs install option

2019-10-04 Thread Martin Wimpress
** Changed in: ubuntu-mate-meta (Ubuntu)
 Assignee: (unassigned) => Martin Wimpress (flexiondotorg)

** Changed in: ubuntu-mate-meta (Ubuntu)
   Importance: Undecided => Medium

** Changed in: ubuntu-mate-meta (Ubuntu)
   Status: New => In Progress

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

Title:
  [FFe] Ubiquity with zfs install option

Status in ubiquity package in Ubuntu:
  New
Status in ubuntu-mate-meta package in Ubuntu:
  In Progress
Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Part of the 19.10 feature announcement is zfs experimental support in
  the installer (https://ubuntu.com/blog/enhancing-our-zfs-support-on-
  ubuntu-19-10-an-introduction). We modified ubiquity to present an
  “EXPERIMENTAL” (with warning) ZSYS install option. This option is only
  visible is zfsutils-linux is installed on the system. So, it won't be
  available for derivatives that use ubiquity but do not seed zfsutils-
  linux.

  Update as of 20/09/2019: the plan is to not seed zsys (security review
  will take a while), but to only seed zfsutils-linux. People can then
  opt-in to zsys which should be available by default next cycle.

  This option takes an entire disk and have a fix set of dataset
  installed. There is no support but we need this to make an official
  install option for the next LTS.

  The patch has been created to be as minimal as possible. Partman does
  a full disk partitioning, and then the script zsys-setup the first
  non-ESP partition and replaces with zfs pools.

  4 partitions are created:
  1. if GPT partitioning: ESP partition. This one is done by partman directly.
  2. bpool (for boot), pool with older zfs compatible version to be readable by 
grub)
  3. rpool (for / and userdataset)
  4. /boot/grub (ext4) to contain a single grub (NOTE: this could be later on 
moved to the ESP)

  Additionaly if a swap file has been created by ubiquity, it is
  recreated as a ZFS volume. If the script fails to execute, the final
  installation is an ext4 installation on entire disk.

  Note that the implementation is slightly different from the
  specification due to a difficult cohabitation with partman in the
  custom partitioning page.

  Please find attached the MP on ubiquity as well as the package build
  log.

  https://launchpadlibrarian.net/442036321/buildlog_ubuntu-eoan-
  amd64.ubiquity_19.10.10~ppa1_BUILDING.txt.gz

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

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


[Touch-packages] [Bug 1843768] Re: [FFe] Ubiquity with zfs install option

2019-10-04 Thread Martin Wimpress
** Also affects: ubuntu-mate-meta (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  [FFe] Ubiquity with zfs install option

Status in ubiquity package in Ubuntu:
  New
Status in ubuntu-mate-meta package in Ubuntu:
  In Progress
Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Part of the 19.10 feature announcement is zfs experimental support in
  the installer (https://ubuntu.com/blog/enhancing-our-zfs-support-on-
  ubuntu-19-10-an-introduction). We modified ubiquity to present an
  “EXPERIMENTAL” (with warning) ZSYS install option. This option is only
  visible is zfsutils-linux is installed on the system. So, it won't be
  available for derivatives that use ubiquity but do not seed zfsutils-
  linux.

  Update as of 20/09/2019: the plan is to not seed zsys (security review
  will take a while), but to only seed zfsutils-linux. People can then
  opt-in to zsys which should be available by default next cycle.

  This option takes an entire disk and have a fix set of dataset
  installed. There is no support but we need this to make an official
  install option for the next LTS.

  The patch has been created to be as minimal as possible. Partman does
  a full disk partitioning, and then the script zsys-setup the first
  non-ESP partition and replaces with zfs pools.

  4 partitions are created:
  1. if GPT partitioning: ESP partition. This one is done by partman directly.
  2. bpool (for boot), pool with older zfs compatible version to be readable by 
grub)
  3. rpool (for / and userdataset)
  4. /boot/grub (ext4) to contain a single grub (NOTE: this could be later on 
moved to the ESP)

  Additionaly if a swap file has been created by ubiquity, it is
  recreated as a ZFS volume. If the script fails to execute, the final
  installation is an ext4 installation on entire disk.

  Note that the implementation is slightly different from the
  specification due to a difficult cohabitation with partman in the
  custom partitioning page.

  Please find attached the MP on ubiquity as well as the package build
  log.

  https://launchpadlibrarian.net/442036321/buildlog_ubuntu-eoan-
  amd64.ubiquity_19.10.10~ppa1_BUILDING.txt.gz

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

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


[Touch-packages] [Bug 1815318] Re: mate 18.04.1 xserver won't open caja on local machine

2019-09-06 Thread Martin Wimpress
Does using either of these help?

  * caja --browser
  * caja --no-desktop

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

** Changed in: ubuntu-mate
   Status: New => Incomplete

** Changed in: ubuntu-mate
   Status: Incomplete => Invalid

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

Title:
  mate 18.04.1 xserver won't open caja on local machine

Status in Ubuntu MATE:
  Invalid
Status in caja package in Ubuntu:
  Incomplete
Status in openssh package in Ubuntu:
  Invalid

Bug description:
  Steps to reproduce:
  1. Have installed Ubuntu MATE 18.04 LTS (you know its hostname and IP - i.e. 
192.168.1.162)
  2. Install SSH server on Ubuntu MATE 18.04 LTS
  3. Open terminal on other remote system (client) and execute command to run 
Caja over X forwarding:

 ssh -X user@192.168.1.162 caja

  Expected results:
  * Caja is shown on remote (client) screen with window title *folder (on 
hostname)*

  Actual results:
  * Caja is not shown on remote (client) screen, but launches on server locally.

  Note: this works normally if server runs Ubuntu MATE 16.04 LTS, but
  fails with 18.04 LTS.

  ---
  Original description below:

  I can open a remote terminal using ssh -X 192.168.1.162. All other
  gui's that I've tested opened locally except the file manager Caja.
  When issuing caja in the remote terminal, I get nothing locally. Caja
  does open on the remote machine however, just not locally. The ssh -X
  18.04.1 client still works connecting to a mate 16.04 server. I've
  tested this on numerous mate 18.04 clients, two 16.04 servers and two
  18.04 servers, all mate. Something is wonky with caja on an 18.04.1
  server.

  Please let me know if I can provide any more information. The only
  file manager I've tested that works is an X file manager, xfimage.
  X2go works and connects to servers, SSH Connect to Server works, why
  isn't the remote X terminal working using caja?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1815318/+subscriptions

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


[Touch-packages] [Bug 1823550] Re: GtkSourceView (gedit - Text Editor and others) wrongly has monospaced font in dropdown (context) menu

2019-05-11 Thread Martin Wimpress
For reference this is the commit for ubuntu-mate-artwork that resolves
this issue in our themes:

  * https://github.com/ubuntu-mate/ubuntu-mate-
artwork/commit/da425237ea3eba1e95d95154af25150dc94d7f50

** Changed in: ubuntu-mate-artwork (Ubuntu)
   Status: Triaged => Fix Committed

** Changed in: ubuntu-mate-artwork (Ubuntu)
 Assignee: (unassigned) => Martin Wimpress (flexiondotorg)

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

Title:
  GtkSourceView (gedit - Text Editor and others) wrongly has monospaced
  font in dropdown (context) menu

Status in GtkSourceView:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  Invalid
Status in gtksourceview3 package in Ubuntu:
  Invalid
Status in mate-themes package in Ubuntu:
  Invalid
Status in pluma package in Ubuntu:
  Invalid
Status in ubuntu-mate-artwork package in Ubuntu:
  Fix Committed
Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 17.04 or later installed
  2. Open any application with GtkSourceView component - such as Pluma, Gedit, 
Giggle, Gitg, gnome-builder and maybe others (see complete list with `apt-cache 
rdepends libgtksourceview-3.0-1`)
  3. Click right mouse button on text zone

  Expected result:
  * dropdown menu has normal font as all other interface elements

  Actual result:
  * dropdwon menu wrongly has monospaced font

  Notes:
  * first seen in 17.04, but persists in 17.10, 18.04 LTS, 18.10, 19.04 
releases.
  * seems to be caused by GTK3 library

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: pluma 1.18.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-42.46-generic 4.10.17
  Uname: Linux 4.10.0-42-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.10
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sun Apr  7 20:13:24 2019
  InstallationDate: Installed on 2018-08-07 (243 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: pluma
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1823550] Re: GtkSourceView (gedit - Text Editor and others) wrongly has monospaced font in dropdown (context) menu

2019-05-09 Thread Martin Wimpress
** Changed in: mate-themes (Ubuntu)
   Status: Confirmed => Invalid

** Also affects: ubuntu-mate-artwork (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: ubuntu-mate-artwork (Ubuntu)
   Status: New => Triaged

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

Title:
  GtkSourceView (gedit - Text Editor and others) wrongly has monospaced
  font in dropdown (context) menu

Status in GtkSourceView:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  Invalid
Status in gtksourceview3 package in Ubuntu:
  Invalid
Status in mate-themes package in Ubuntu:
  Invalid
Status in pluma package in Ubuntu:
  Invalid
Status in ubuntu-mate-artwork package in Ubuntu:
  Triaged
Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 17.04 or later installed
  2. Open any application with GtkSourceView component - such as Pluma, Gedit, 
Giggle, Gitg, gnome-builder and maybe others (see complete list with `apt-cache 
rdepends libgtksourceview-3.0-1`)
  3. Click right mouse button on text zone

  Expected result:
  * dropdown menu has normal font as all other interface elements

  Actual result:
  * dropdwon menu wrongly has monospaced font

  Notes:
  * first seen in 17.04, but persists in 17.10, 18.04 LTS, 18.10, 19.04 
releases.
  * seems to be caused by GTK3 library

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: pluma 1.18.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-42.46-generic 4.10.17
  Uname: Linux 4.10.0-42-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.10
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sun Apr  7 20:13:24 2019
  InstallationDate: Installed on 2018-08-07 (243 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: pluma
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1673258] Re: Remove aptdaemon and drop or port its reverse-dependencies

2019-04-17 Thread Martin Wimpress
** Changed in: ubuntu-mate-welcome (Ubuntu)
   Importance: Undecided => Wishlist

** Changed in: ubuntu-mate-welcome (Ubuntu)
   Status: New => Opinion

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

Title:
  Remove aptdaemon and drop or port its reverse-dependencies

Status in aptdaemon package in Ubuntu:
  New
Status in apturl package in Ubuntu:
  New
Status in dell-recovery package in Ubuntu:
  Fix Released
Status in gnome-software package in Ubuntu:
  Fix Released
Status in language-selector package in Ubuntu:
  New
Status in lubuntu-software-center package in Ubuntu:
  Fix Released
Status in mythbuntu-control-centre package in Ubuntu:
  Fix Released
Status in sessioninstaller package in Ubuntu:
  New
Status in software-properties package in Ubuntu:
  New
Status in ubiquity package in Ubuntu:
  New
Status in ubuntu-mate-meta package in Ubuntu:
  Fix Released
Status in ubuntu-mate-welcome package in Ubuntu:
  Opinion
Status in update-manager package in Ubuntu:
  New
Status in update-notifier package in Ubuntu:
  New
Status in zeroinstall-injector package in Ubuntu:
  Fix Released

Bug description:
  aptdaemon is abandoned and unmaintained.  It has already been dropped
  from Debian, but there are several reverse dependencies keeping it in
  Ubuntu.  I will add bug tasks for each of those dependencies, which
  should be ported or dropped themselves.  Then we can get rid of
  aptdaemon too.

  See this mailing list thread for more details:
  https://lists.ubuntu.com/archives/ubuntu-devel/2017-March/039722.html

  https://github.com/ubuntu-mate/ubuntu-mate-welcome/issues/48

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

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


[Touch-packages] [Bug 1726788] Re: python3.6 crashed with signal 7 in adler32_z()

2019-04-06 Thread Martin Wimpress
** Also affects: apt (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: ubuntu-mate-welcome (Ubuntu)
   Status: New => Invalid

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

Title:
  python3.6 crashed with signal 7 in adler32_z()

Status in apt package in Ubuntu:
  New
Status in ubuntu-mate-welcome package in Ubuntu:
  Invalid

Bug description:
  This crash came from multiple errors I was experiencing in my Ubuntu
  MATE installation.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: python3.6-minimal 3.6.3-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  Date: Tue Oct 24 10:26:31 2017
  ExecutablePath: /usr/bin/python3.6
  InstallationDate: Installed on 2017-10-23 (0 days ago)
  InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 
(20171018)
  ProcCmdline: ubuntu-mate-welcome
  ProcEnviron:
   
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  Signal: 7
  SourcePackage: python3.6
  StacktraceTop:
   adler32_z () from /lib/x86_64-linux-gnu/libz.so.1
   ?? () from /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0
   pkgCache::ReMap(bool const&) () from 
/usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0
   pkgCache::pkgCache(MMap*, bool) () from 
/usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0
   ?? () from /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0
  Title: python3.6 crashed with signal 7 in adler32_z()
  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/apt/+bug/1726788/+subscriptions

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


[Touch-packages] [Bug 1675079] Re: 16.04 LTS Partition /boot fills up with Kernel images, gets underwear in a twist

2018-12-14 Thread Not Martin Wimpress
I understand. Saying "the default is true" is a bit puzzling, but after
reading https://github.com/mvo5/unattended-upgrades/blob/master
/unattended-upgrade#L1957 , the conditional makes sense since the
default [object] is defined as "True". It also makes sense how this
works for proposed-16.04 since that line isn't even mentioned in the
config but "True" is pushed in the script anyway.

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

Title:
  16.04 LTS Partition /boot fills up with Kernel images, gets underwear
  in a twist

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in update-manager package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  Fix Committed
Status in update-manager source package in Xenial:
  Fix Released
Status in unattended-upgrades source package in Artful:
  Won't Fix
Status in update-manager source package in Artful:
  Fix Released

Bug description:
  [Impact]

   * Update-manager and unattended-upgrades install many kernel packages during 
the lifetime of a release but does not remove them automatically leading to 
those packages filling disk space potentially completely filling /boot and 
making the system unable to install updates or even boot.
   * Stable release users are impacted by this bug for years and their systems 
already collected many autoremovable unused kernel packages, thus they would 
benefit from backporting the fix greatly.
   * The bug is fixed by removing autoremovable (not currently booted) kernel 
packages when running unattended-upgrades or update-manager. Update manager 
offers the kernel removals when there are other updates to be installed.

  [Test Case]

   1. Install kernel packages to be removed, mark them auto-installed
  and run apt's kernel hook script to make apt consider them
  autoremovable:

    sudo apt install -y linux-image-extra-4.4.0-92-generic 
linux-image-extra-4.4.0-93-generic
    sudo apt-mark auto linux-image-extra-4.4.0-92-generic 
linux-image-extra-4.4.0-93-generic
    sudo /etc/kernel/postinst.d/apt-auto-removal

   2. Also downgrade a package to be upgraded:

     sudo apt-get install -y --allow-downgrades ca-
  certificates=20160104ubuntu1

   3. (update-manager). Run update-manager and observe that kernel
  packages are offered for removal in Details of updates.

    sudo update-manager

   4. (update-manager) Click on Install Now and observe that the kernel
  packages are removed.

   3. (unattended-upgrades) Run unattended-upgrades manually and observe
  the removal of the autoremovable kernel packages:

    sudo unattended-upgrade -v

  [Regression Potential]

   The change may cause update-manager or unattanded-upgrades to remove
  used kernel packages or fail to install other package updates.

  [Other Info]

  The unattended-upgrades fix is uploaded with many other fixes and
  those may cause regressions in other areas in unattended-upgrades.

  [Original bug text]

  On a 16.04LTS system, the /boot partition will eventually fill with
  Kernel images, until the point where "apt-get autoremove" can't
  complete.

  This issue has previously been reported as fixed, but it is not fixed:
  https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1357093

  Generally what I see is the final kernel image that fills the drive is
  incompletely installed (the header package does not make it).  "apt-
  get autoremove" tries to work, but fails.  I must manually remove
  kernel images to free enough space.

  I see this on a machine used by my elderly parents, where 'Download
  and install updates automatically' is set.  And on my home machines,
  where the setting is elsewhere.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1675079/+subscriptions

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


[Touch-packages] [Bug 1675079] Re: 16.04 LTS Partition /boot fills up with Kernel images, gets underwear in a twist

2018-12-14 Thread Not Martin Wimpress
Balint, I'm confused on your statement in the other dup bug report
(https://bugs.launchpad.net/ubuntu/+source/unattended-
upgrades/+bug/1357093/comments/129 ) that this is fixed in 18.04, but
looking at line 60 in the "50unattended-upgrades.Ubuntu" file in the
current package (1.1ubuntu1.18.04.7):

//Unattended-Upgrade::Remove-Unused-Kernel-Packages "false";

...it appears to me that 2 modifications are needed before any kernels
are auto-removed. I saw your Nov 9th commit to switch it to "true", but
doesn't the line still needs to be commented out in order to activate?

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

Title:
  16.04 LTS Partition /boot fills up with Kernel images, gets underwear
  in a twist

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in update-manager package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  Fix Committed
Status in update-manager source package in Xenial:
  Fix Released
Status in unattended-upgrades source package in Artful:
  Won't Fix
Status in update-manager source package in Artful:
  Fix Released

Bug description:
  [Impact]

   * Update-manager and unattended-upgrades install many kernel packages during 
the lifetime of a release but does not remove them automatically leading to 
those packages filling disk space potentially completely filling /boot and 
making the system unable to install updates or even boot.
   * Stable release users are impacted by this bug for years and their systems 
already collected many autoremovable unused kernel packages, thus they would 
benefit from backporting the fix greatly.
   * The bug is fixed by removing autoremovable (not currently booted) kernel 
packages when running unattended-upgrades or update-manager. Update manager 
offers the kernel removals when there are other updates to be installed.

  [Test Case]

   1. Install kernel packages to be removed, mark them auto-installed
  and run apt's kernel hook script to make apt consider them
  autoremovable:

    sudo apt install -y linux-image-extra-4.4.0-92-generic 
linux-image-extra-4.4.0-93-generic
    sudo apt-mark auto linux-image-extra-4.4.0-92-generic 
linux-image-extra-4.4.0-93-generic
    sudo /etc/kernel/postinst.d/apt-auto-removal

   2. Also downgrade a package to be upgraded:

     sudo apt-get install -y --allow-downgrades ca-
  certificates=20160104ubuntu1

   3. (update-manager). Run update-manager and observe that kernel
  packages are offered for removal in Details of updates.

    sudo update-manager

   4. (update-manager) Click on Install Now and observe that the kernel
  packages are removed.

   3. (unattended-upgrades) Run unattended-upgrades manually and observe
  the removal of the autoremovable kernel packages:

    sudo unattended-upgrade -v

  [Regression Potential]

   The change may cause update-manager or unattanded-upgrades to remove
  used kernel packages or fail to install other package updates.

  [Other Info]

  The unattended-upgrades fix is uploaded with many other fixes and
  those may cause regressions in other areas in unattended-upgrades.

  [Original bug text]

  On a 16.04LTS system, the /boot partition will eventually fill with
  Kernel images, until the point where "apt-get autoremove" can't
  complete.

  This issue has previously been reported as fixed, but it is not fixed:
  https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1357093

  Generally what I see is the final kernel image that fills the drive is
  incompletely installed (the header package does not make it).  "apt-
  get autoremove" tries to work, but fails.  I must manually remove
  kernel images to free enough space.

  I see this on a machine used by my elderly parents, where 'Download
  and install updates automatically' is set.  And on my home machines,
  where the setting is elsewhere.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1675079/+subscriptions

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


[Touch-packages] [Bug 1766108] Re: Battery indicator crashes when unchecking "Show Percentage in Menu Bar"

2018-11-13 Thread Martin Wimpress
** Changed in: mate-indicator-applet (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: mate-panel (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  Battery indicator crashes when unchecking "Show Percentage in Menu
  Bar"

Status in ubuntu-mate:
  New
Status in indicator-power package in Ubuntu:
  Confirmed
Status in mate-indicator-applet package in Ubuntu:
  Invalid
Status in mate-panel package in Ubuntu:
  Invalid

Bug description:
  Steps to reproduce:

  1. Click on the battery indicator.
  2. Click "Show Percentage on Menu Bar" to enable it.
  3. Do it again to disable it.
  4. Battery indicator disappears

  
  Output from dmesg:

  [  613.877855] mate-panel[1604]: segfault at 1c ip 7f51b23daa20 sp 
7ffe8df7f5d8 error 4 in libcairo.so.2.11510.0[7f51b236c000+118000]
  [  749.662960] mate-panel[2930]: segfault at 38 ip 7fc98aa82300 sp 
7fffa5290f68 error 4 in libgdk-3.so.0.2200.30[7fc98aa3b000+eb000]
  [  775.815530] mate-panel[3127]: segfault at 1c ip 7fc317b61a20 sp 
7ffea6e1f028 error 4 in libcairo.so.2.11510.0[7fc317af3000+118000]
  [  816.504199] mate-panel[3225]: segfault at 38 ip 7fa314f0e300 sp 
7fffa993f928 error 4 in libgdk-3.so.0.2200.30[7fa314ec7000+eb000]
  [  841.353444] mate-panel[3363]: segfault at 38 ip 7fbc86c4a300 sp 
7ffd6b3a5d58 error 4 in libgdk-3.so.0.2200.30[7fbc86c03000+eb000]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1766108/+subscriptions

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


[Touch-packages] [Bug 1801325] Re: User processes/sessions lingering after logoff

2018-11-13 Thread Martin Wimpress
** Also affects: mate-session-manager (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: mate-session-manager (Ubuntu)
   Status: New => In Progress

** Changed in: mate-session-manager (Ubuntu)
 Assignee: (unassigned) => Victor Kareh (vkareh)

** Changed in: ubuntu-mate
   Status: In Progress => Invalid

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

Title:
  User processes/sessions lingering after logoff

Status in ubuntu-mate:
  Invalid
Status in mate-session-manager package in Ubuntu:
  In Progress
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Hi!

  Logoff doesn't terminate all user processes/sessions, which means
  after mutiple logon/logoff operations lots of sessions and processes
  are leaking (you can see them with systemctl status). Verified with
  redshift(-gtk), at least. This can be worked around with
  KillUserProcesses=yes on /etc/systemd/logind.conf, but it breaks GNU
  Screen, for example. Tested on 18.04 and 18.10.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1801325/+subscriptions

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


[Touch-packages] [Bug 1775068] Re: Volume control not working Dell XPS 27 (7760)

2018-09-27 Thread Martin Wimpress
** Also affects: pulseaudio (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: ubuntu-mate

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

Title:
  Volume control not working Dell XPS 27 (7760)

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  
  Pressing vol up/vol down show OSD change up/down but volume all time is at 
100%.

  I found temporary fix:

  Add section:
  [Element Master]
  switch = mute
  volume = ignore

  To:
  /usr/share/pulseaudio/alsa-mixer/paths/analog-output.conf.common

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

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


[Touch-packages] [Bug 1789234] Re: Audio Popping when Headphones are plugged into Laptop

2018-09-27 Thread Martin Wimpress
** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

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

** No longer affects: ubuntu-mate

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

Title:
  Audio Popping when Headphones are plugged into Laptop

Status in linux package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  There seems to be a power saving issue where the sound card
  automatically turns off when not in use. When the laptop is off the
  charger, I plug in the headset into the headphone port. Then a sharp
  popping sound is sent through to my earbuds to my eardrums. You often
  have to manually disable the power saving to stop the issue, but this
  impacts the battery life of the laptop. I noticed this issue on Ubuntu
  MATE first and if has occurred on ALL versions of Ubuntu MATE I have
  used {16.04 onwards}. This issue also occurs on other Ubuntu distros.

  
  Here is the specific Audio hardware
  jgj@jgjbuntu-Inspiron-5547:~$ lspci | grep Audio
  00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller (rev 
0b)
  00:1b.0 Audio device: Intel Corporation 8 Series HD Audio Controller (rev 04)

  Hope this bug can be resolved.

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

-- 
Mailing list: https://launchpad.net/~touch-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

2018-07-05 Thread Martin Wimpress
RX VegaM works for me with Mesa 18.1.1 or newer, providing I have Linux
4.18 and the firmware blobs from AMD.

Currently using the Intel Hades Canyon NUC running Ubuntu MATE 18.04
with the above installed.

-- 
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:
  Triaged
Status in mesa package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  New
Status in mesa source package in Xenial:
  New
Status in linux source package in Bionic:
  New
Status in mesa source package in Bionic:
  New

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 1762807] Re: gnome-session-bin installed on Ubuntu MATE

2018-04-10 Thread Martin Wimpress
** Branch linked: lp:~ubuntu-mate-dev/software-properties/lp1762807

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

Title:
  gnome-session-bin installed on Ubuntu MATE

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu MATE seeds software-properties-gtk which causes gnome-session-
  bin to be pulled into the Ubuntu MATE image. This issue arises because
  debian/control doesn't Recommends: mate-session-manager for software-
  properties-gtk.

  To resolve this issue debian/control for software-properties-gtk
  should be updated to:

  Recommends: gnome-session-bin | xfce4-session | lubuntu-default-
  settings | lxqt-session | mate-session-manager, gnome-keyring

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1762807/+subscriptions

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


[Touch-packages] [Bug 1762807] [NEW] gnome-session-bin installed on Ubuntu MATE

2018-04-10 Thread Martin Wimpress
Public bug reported:

Ubuntu MATE seeds software-properties-gtk which causes gnome-session-bin
to be pulled into the Ubuntu MATE image. This issue arises because
debian/control doesn't Recommends: mate-session-manager for software-
properties-gtk.

To resolve this issue debian/control for software-properties-gtk should
be updated to:

Recommends: gnome-session-bin | xfce4-session | lubuntu-default-settings
| lxqt-session | mate-session-manager, gnome-keyring

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

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

Title:
  gnome-session-bin installed on Ubuntu MATE

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu MATE seeds software-properties-gtk which causes gnome-session-
  bin to be pulled into the Ubuntu MATE image. This issue arises because
  debian/control doesn't Recommends: mate-session-manager for software-
  properties-gtk.

  To resolve this issue debian/control for software-properties-gtk
  should be updated to:

  Recommends: gnome-session-bin | xfce4-session | lubuntu-default-
  settings | lxqt-session | mate-session-manager, gnome-keyring

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1762807/+subscriptions

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


[Touch-packages] [Bug 1502045] Re: Move from consolekit to logind

2018-04-07 Thread Martin Wimpress
mate-power-manager has been using systemd for sometime in Ubuntu.

** Changed in: mate-power-manager (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  Move from consolekit to logind

Status in lxdm package in Ubuntu:
  Fix Released
Status in lxsession package in Ubuntu:
  Fix Released
Status in mate-power-manager package in Ubuntu:
  Fix Released
Status in openssh package in Ubuntu:
  Fix Released
Status in polkit-qt-1 package in Ubuntu:
  Triaged
Status in solaar package in Ubuntu:
  Triaged
Status in sugar package in Ubuntu:
  Triaged
Status in tcosmonitor package in Ubuntu:
  Fix Released
Status in ulatencyd package in Ubuntu:
  Triaged
Status in lxdm package in Debian:
  Fix Released
Status in tcosmonitor package in Debian:
  Fix Released

Bug description:
  consolekit has been dead upstream for a long time. Ubuntu moved to
  logind in saucy (13.10), and we don't support consolekit any more.
  There are a few packages which still depend on it, most notably
  openssh, lxdm, and lxsession{,-logout}. For Ubuntu 16.04 we really
  should get rid of CK.

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

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


[Touch-packages] [Bug 1760598] Re: I/O Error after clicking "reboot now" - Ubuntu font missing from casper shutdown

2018-04-04 Thread Martin Wimpress
** Changed in: ubuntu-mate
   Status: New => Invalid

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

Title:
  I/O Error after clicking "reboot now" - Ubuntu font missing from
  casper shutdown

Status in ubuntu-mate:
  Invalid
Status in casper package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Invalid
Status in ubiquity package in Ubuntu:
  Confirmed
Status in ubuntu-mate-welcome package in Ubuntu:
  Invalid

Bug description:
  ubuntu Plymouth theme now correctly uses Ubuntu font, meaning it needs
  to be cached for display of the shutdown message.

  We really should be using shutdown initramfs on the livecd

  --

  Tested in Virtualbox VM.
  Ubuntu MATE works after force-reboot, but after I click on "restart now" 
after completing the installation, the screen shows me this:

  req_error: I/O error, dev sr0, sector 1488792

  And the above message loops a couple times, and wont turn off the
  computer to restart.

  No error happens after force reboot, and the OS boots properly, but
  I'm curious as to what's causing this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1760598/+subscriptions

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


[Touch-packages] [Bug 1756238] Re: gdebi-gtk broken in 18.04 error: unable to read filedescriptor flags

2018-03-31 Thread Martin Wimpress
Looks like 91_keep_fds.patch was something that never made it upstream
when originally added.

vte (1:0.25.91-0ubuntu4) maverick; urgency=low

  * debian/patches/91_keep_fds.patch:
- Update and return patch that hadn't been applied upstream (LP: #620297)
 -- Robert Ancell  Wed, 08 Sep 2010 17:57:18 +1000

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

Title:
  gdebi-gtk broken in 18.04 error: unable to read filedescriptor flags

Status in gdebi package in Ubuntu:
  Confirmed
Status in vte2.91 package in Ubuntu:
  Fix Committed

Bug description:
  When using gdebi-gtk to install a .deb the install fails with the
  message:-

  dpkg: error: unable to read filedescriptor flags for : Bad file descriptor

  This only occurs via the gdebi-gtk GUI front end, packages install perfectly 
if done via the CLI with:
  sudo gdebi /path/to/packagename.deb

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

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


[Touch-packages] [Bug 1753216] Re: dpkg: Fehler: Dateideskriptorflags für »« können nicht gelesen werden: Ungültiger Dateideskriptor

2018-03-18 Thread Martin Wimpress
*** This bug is a duplicate of bug 1756238 ***
https://bugs.launchpad.net/bugs/1756238

** This bug has been marked a duplicate of bug 1756238
   gdebi-gtk broken in 18.04 error: unable to read filedescriptor flags

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

Title:
  dpkg: Fehler: Dateideskriptorflags für »« können nicht gelesen werden: Ungültiger
  Dateideskriptor

Status in gdebi package in Ubuntu:
  Confirmed

Bug description:
  Fehlermeldung:
  dpkg: Fehler: Dateideskriptorflags für »« können nicht gelesen werden: Ungültiger Dateideskriptor

  beim Installieren eines deb-Paketes mit Paket-Instalaationsprogramm

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

  gdebi:
Installiert:   0.9.5.7+nmu2
Installationskandidat: 0.9.5.7+nmu2
Versionstabelle:
   *** 0.9.5.7+nmu2 500
  500 http://de.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
  500 http://de.archive.ubuntu.com/ubuntu bionic/universe i386 Packages
  100 /var/lib/dpkg/status

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

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


[Touch-packages] [Bug 1673258] Re: Remove aptdaemon and drop or port its reverse-dependencies

2018-02-27 Thread Martin Wimpress
** Changed in: ubuntu-mate-meta (Ubuntu)
   Status: New => In Progress

** Changed in: ubuntu-mate-meta (Ubuntu)
   Status: In Progress => Fix Committed

** Changed in: ubuntu-mate-meta (Ubuntu)
 Assignee: (unassigned) => Martin Wimpress (flexiondotorg)

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

Title:
  Remove aptdaemon and drop or port its reverse-dependencies

Status in aptdaemon package in Ubuntu:
  New
Status in apturl package in Ubuntu:
  New
Status in dell-recovery package in Ubuntu:
  Fix Released
Status in gnome-software package in Ubuntu:
  Fix Released
Status in language-selector package in Ubuntu:
  New
Status in lubuntu-software-center package in Ubuntu:
  Fix Released
Status in mythbuntu-control-centre package in Ubuntu:
  Fix Released
Status in sessioninstaller package in Ubuntu:
  New
Status in software-properties package in Ubuntu:
  New
Status in ubiquity package in Ubuntu:
  New
Status in ubuntu-mate-meta package in Ubuntu:
  Fix Committed
Status in ubuntu-mate-welcome package in Ubuntu:
  New
Status in update-manager package in Ubuntu:
  New
Status in update-notifier package in Ubuntu:
  New
Status in zeroinstall-injector package in Ubuntu:
  Fix Released

Bug description:
  aptdaemon is abandoned and unmaintained.  It has already been dropped
  from Debian, but there are several reverse dependencies keeping it in
  Ubuntu.  I will add bug tasks for each of those dependencies, which
  should be ported or dropped themselves.  Then we can get rid of
  aptdaemon too.

  See this mailing list thread for more details:
  https://lists.ubuntu.com/archives/ubuntu-devel/2017-March/039722.html

  https://bitbucket.org/ubuntu-mate/ubuntu-mate-welcome/issues/48/port-
  from-aptdaemon-to-packagekit

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

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


[Touch-packages] [Bug 1741468] Re: Broken GUI in Ubuntu MATE Live Session

2018-01-06 Thread Martin Wimpress
What version of Ubuntu MATE?

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

Title:
  Broken GUI in Ubuntu MATE Live Session

Status in xorg package in Ubuntu:
  New

Bug description:
  Device: MacBook Air, late 2013

  
  -The toolbar on the top and the bottom loads, but they seem to be images only.

  -I cannot click on the Applications, Places, System, Firefox, or MATE
  Welcome, nor the power button on the top bar.

  -The Bottom bar's show desktop and switch desktop does not click
  either.

  -My cursor shows and tracks, but it does not seem to register clicks.
  This is both with a mouse and a trackpad.

  -Background image is black.

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

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


[Touch-packages] [Bug 1732530] Re: Dejadup is not working b/c duplicity is not installed

2017-12-30 Thread Martin Wimpress
** Changed in: ubuntu-mate-meta (Ubuntu)
   Status: New => Fix Committed

** Changed in: ubuntu-mate-meta (Ubuntu)
 Assignee: (unassigned) => Martin Wimpress (flexiondotorg)

** Changed in: ubuntu-mate-meta (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  Dejadup is not working b/c duplicity is not installed

Status in ubuntu-mate:
  Invalid
Status in deja-dup package in Ubuntu:
  New
Status in ubuntu-mate-meta package in Ubuntu:
  Fix Committed
Status in ubuntu-meta package in Ubuntu:
  New
Status in ubuntukylin-meta package in Ubuntu:
  New

Bug description:
  Ubuntu Mate 17.10

  Dejadup is not working b/c duplicity is not installed. After a manual
  install, Deja-Dup works as expected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1732530/+subscriptions

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


[Touch-packages] [Bug 1732530] Re: Dejadup is not working b/c duplicity is not installed

2017-12-30 Thread Martin Wimpress
It appears that duplicity is now a Suggests: for deja-dup and not
installed by default. I will update the ubuntu-mate-meta package to
include duplicity.

** Also affects: deja-dup (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: ubuntu-mate-meta (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: ubuntu-mate
   Status: Confirmed => Invalid

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

** Also affects: ubuntukylin-meta (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Dejadup is not working b/c duplicity is not installed

Status in ubuntu-mate:
  Invalid
Status in deja-dup package in Ubuntu:
  New
Status in ubuntu-mate-meta package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  New
Status in ubuntukylin-meta package in Ubuntu:
  New

Bug description:
  Ubuntu Mate 17.10

  Dejadup is not working b/c duplicity is not installed. After a manual
  install, Deja-Dup works as expected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1732530/+subscriptions

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


[Touch-packages] [Bug 1722595] Re: python idle / idle3 errors on start

2017-10-11 Thread Martin Wimpress
** Also affects: python3-defaults (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: ubuntu-mate
   Status: New => Invalid

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

Title:
  python idle / idle3 errors on start

Status in ubuntu-mate:
  Invalid
Status in python3-defaults package in Ubuntu:
  New

Bug description:
  
  root@central:/home/holiday# apt list --installed | grep idle

  idle/artful,artful,now 3.6.3-0ubuntu1 all [installed]
  idle-python3.6/artful,artful,now 3.6.3-1ubuntu1 all [installed,automatic]
  idle3/artful,artful,now 3.6.3-0ubuntu1 all [installed]

  root@central:/home/holiday# idle3
  The program 'idle3' is currently not installed. You can install it by typing:
  apt install idle3
  root@central:/home/holiday# apt install idle3
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  idle3 is already the newest version (3.6.3-0ubuntu1).
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

  root@central:/home/holiday# 
  root@central:/home/holiday# idle
  Traceback (most recent call last):   
File "/usr/bin/idle", line 3, in 
  from idlelib.PyShell import main
  ModuleNotFoundError: No module named 'idlelib.PyShell'

  root@central:/home/holiday#

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1722595/+subscriptions

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


[Touch-packages] [Bug 1718394] Re: CUPS - Can't detect file type

2017-09-21 Thread Martin Wimpress
** Also affects: cups (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: ubuntu-mate-artwork (Ubuntu)
   Status: New => Invalid

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

Title:
  CUPS - Can't detect file type

Status in cups package in Ubuntu:
  New
Status in ubuntu-mate-artwork package in Ubuntu:
  Invalid

Bug description:
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10
  Kernel Linux 4.12.0-13-generic x86_64

  Can't detect file type when using CUPS with Canon MG5700-series
  drivers (driverless and cups-gutenprint) - when printing.

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

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


[Touch-packages] [Bug 1706770] Re: Lock screen can be bypassed when auto-login is enabled.

2017-08-29 Thread Martin Wimpress
** Also affects: lightdm (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Lock screen can be bypassed when auto-login is enabled.

Status in ubuntu-mate:
  New
Status in lightdm package in Ubuntu:
  New
Status in mate-session-manager package in Ubuntu:
  New

Bug description:
  16.04 LTS
  =

  Hi,

  My machine is set up with full-disk encryption, so it requires a
  password when I boot it up. Because of this I thought I would enable
  auto-login to avoid having to enter two passwords at boot.

  When I leave my computer for short periods of time, I lock it. I
  thought this was working fine for a long time, but I've discovered the
  lock screen is actually easily bypassable when auto-login is enabled.
  All one has to do is click "Switch User" on the lock screen, then
  press "Unlock" and the computer unlocks without prompting for a
  password.

  Perhaps this is just me being an idiot, but I thought this was secure
  until now. It seems like either unlocking should always require a
  password (otherwise what's the point of locking in the first place) or
  it should be made totally obvious that unlocking doesn't actually
  require a password (i.e. removing the password box from the lock
  screen when auto-login is enabled).

  Thanks,
  Chris

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1706770/+subscriptions

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


[Touch-packages] [Bug 1631208] Re: Tabs in Firefox dialogs are not rendered (for add-on options & Certificate Viewer)

2017-08-25 Thread Martin Wimpress
** Changed in: ubuntu-themes (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  Tabs in Firefox dialogs are not rendered (for add-on options &
  Certificate Viewer)

Status in ubuntu-themes package in Ubuntu:
  Fix Committed

Bug description:
  Tabs in the preference dialogues of Firefox add-on don't render
  anymore in Ubuntu 16.10. Here is the upstream bug report:

    * https://bugzilla.mozilla.org/show_bug.cgi?id=1306425

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

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


[Touch-packages] [Bug 1580394] Re: [Latitude 3340, Realtek ALC3234] MATE - Headphone Static on Battery Power

2017-08-18 Thread Martin Wimpress
** Changed in: libmatemixer (Ubuntu)
   Status: New => Invalid

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

Title:
  [Latitude 3340, Realtek ALC3234] MATE - Headphone Static on Battery
  Power

Status in alsa-driver package in Ubuntu:
  New
Status in libmatemixer package in Ubuntu:
  Invalid

Bug description:
  I have noticed that when I am on battery power on a Dell Latitude 3340
  laptop with headphones plugged in , and there is no audio playing on
  the computer, there is a consistent static sound that comes through
  the headphones at a constant volume that is not affected by changing
  the volume level. I think it may be picking up some kind of analog
  loopback signal because keyboard presses and disk activity seem to
  influence the noise. When I plug the power cable into the laptop , the
  static immediately goes away.

  I reported this earlier to the upstream Linux Kernel bug tracker, but
  it seems to be fixed in any distro running a 4.4 kernel or greater
  that I have tested , Except for Ubuntu MATE 16.04 LTS 64-bit. This
  make me think it is not a kernel level issue and is found somewhere
  either in the audio settings on Ubuntu MATE or a pulseaudio bug. I
  cannot reproduce it on any other 16.04 distro version, but it also
  affects all the 14.04.4 distros as well.

  Running amixer -c 1 set "Loopback Mixing" "Disabled" does not prevent
  the static.

  The BIOS Firmware version is up to date.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu-mate   1718 F pulseaudio
   /dev/snd/controlC0:  ubuntu-mate   1718 F pulseaudio
  CasperVersion: 1.376
  CurrentDesktop: MATE
  Date: Wed May 11 00:43:52 2016
  LiveMediaBuild: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/04/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd11/04/2015:svnDellInc.:pnLatitude3340:pvr00:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude 3340
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1580394/+subscriptions

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


[Touch-packages] [Bug 1685668] Re: Firefox switched mouse clicks in scroll bar

2017-08-15 Thread Martin Wimpress
** Also affects: firefox (Ubuntu)
   Importance: Undecided
   Status: New

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

** Changed in: ubuntu-mate
   Status: New => Invalid

** Changed in: ubuntu-mate
   Status: Invalid => Opinion

** Changed in: ubuntu-mate
   Importance: Undecided => Wishlist

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

Title:
  Firefox switched mouse clicks in scroll bar

Status in ubuntu-mate:
  Opinion
Status in firefox package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  This is a GTK3 behavior, but it's so weird:

  https://ubuntu-mate.community/t/how-to-restore-firefox-left-middle-
  clicking-on-scrollbar-behavior/12862

  I fixed it creating this file (it didn't exists in xenial):

  costales@desktop:/$ cat /usr/share/themes/Ambiant-MATE/gtk-3.0/settings.ini
  [Settings]
  gtk-primary-button-warps-slider = false
  costales@desktop:/$ 

  
  I was looking for creating a proposed branch, but I saw the last code:
  
http://bazaar.launchpad.net/~ubuntu-mate-dev/ubuntu-mate/ubuntu-mate-artwork/view/head:/usr/share/themes/Ambiant-MATE/gtk-3.0/settings.ini

  And it has:
  gtk-primary-button-warps-slider = true

  Should it be "= false"?

  Thanks in advance!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1685668/+subscriptions

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


[Touch-packages] [Bug 1695825] Re: No "Recently Used" in Caja 1.18.1

2017-08-15 Thread Martin Wimpress
This is due to a change of behaviour in GTK+3.

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

** Changed in: ubuntu-mate
   Status: New => 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/1695825

Title:
  No "Recently Used" in Caja 1.18.1

Status in ubuntu-mate:
  Invalid
Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  I updated to 17.04 about a week ago. Prior to that, when using 16.04,
  I'd been able to see, and use, the "Recently Used" function at the top
  of the "Places" Side pane in Caja. Now it seems to not be there.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1695825/+subscriptions

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


[Touch-packages] [Bug 1710507] Re: Systemd persistent logs are not enabled

2017-08-15 Thread Martin Wimpress
** Also affects: systemd (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: ubuntu-mate

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

Title:
  Systemd persistent logs are not enabled

Status in systemd package in Ubuntu:
  New

Bug description:
  Currently, the installation is not creating the '/var/log/journal'
  directory, which means journald falls back to volatile storage of logs
  and does not provide persistent logging out of the box.

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

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


[Touch-packages] [Bug 1555331] Re: mate-panel crashed with SIGSEGV in g_slist_remove_all()

2017-07-20 Thread Martin Wimpress
It really seems like some old bug in GTK+2. It crashes on this line,
always with the same stacktrace.

  * https://bugzilla.redhat.com/1293096
  * https://bugzilla.redhat.com/1343807

I'm doubt that rc_style will ever be fixed as this is replaced with
GtkStyleProvider in GTK3+. Ubuntu MATE was migrated to GTK3+ only for
Ubuntu MATE 16.10 and this issue is no longer present since that
release.

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

** Changed in: mate-panel (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 gtk+2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1555331

Title:
  mate-panel crashed with SIGSEGV in g_slist_remove_all()

Status in gtk+2.0 package in Ubuntu:
  New
Status in mate-panel package in Ubuntu:
  Won't Fix

Bug description:
  Description:  Ubuntu Xenial Xerus (development branch)
  Release:  16.04

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: mate-panel 1.12.2-1
  ProcVersionSignature: Ubuntu 4.4.0-11.26-generic 4.4.4
  Uname: Linux 4.4.0-11-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Wed Mar  9 22:49:55 2016
  ExecutablePath: /usr/bin/mate-panel
  InstallationDate: Installed on 2016-02-25 (12 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160224)
  ProcCmdline: mate-panel
  SegvAnalysis:
   Segfault happened at: 0x7f4fa6439b1c :cmp
%rbp,(%rdi)
   PC (0x7f4fa6439b1c) ok
   source "%rbp" ok
   destination "(%rdi)" (0x160016) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: mate-panel
  StacktraceTop:
   g_slist_remove_all () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
   g_hash_table_foreach () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   gtk_rc_reset_styles () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
  Title: mate-panel crashed with SIGSEGV in g_slist_remove_all()
  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/gtk+2.0/+bug/1555331/+subscriptions

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


[Touch-packages] [Bug 1641914] Re: Please backport two recent-manager patches

2017-07-17 Thread Martin Wimpress
** Changed in: gtk+3.0 (Ubuntu Yakkety)
   Status: New => Won't Fix

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

Title:
  Please backport two recent-manager patches

Status in GTK+:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Yakkety:
  Won't Fix

Bug description:
  
https://git.gnome.org/browse/gtk+/commit/?h=gtk-3-22=bf560369f2401e2cdd16f962f248e98c890835d0
  
https://git.gnome.org/browse/gtk+/commit/?h=gtk-3-22=a28022e9161415ef65ae3f21f0c4052f5db8558b

  Please apply/backport these two patches from the 3.22 branch. They fix a 
memory DOS, originally reported against mate-panel here:
  https://github.com/mate-desktop/mate-panel/issues/479

  The GTK+2 version of this bug is bug 1641912

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

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


[Touch-packages] [Bug 1641912] Re: Please backport two recent-manager patches

2017-07-11 Thread Martin Wimpress
Yakkety 16.10 goes EOL this month.

** Changed in: gtk+2.0 (Ubuntu Yakkety)
   Status: Confirmed => Won't Fix

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

Title:
  Please backport two recent-manager patches

Status in GTK+:
  Fix Released
Status in gtk+2.0 package in Ubuntu:
  Confirmed
Status in gtk+2.0 source package in Xenial:
  Confirmed
Status in gtk+2.0 source package in Yakkety:
  Won't Fix

Bug description:
  
https://git.gnome.org/browse/gtk+/commit/?h=gtk-2-24=a3b2d6a65be9f592de9570c227df00f910167e9e
  
https://git.gnome.org/browse/gtk+/commit/?h=gtk-2-24=35871edb318083b2d7e4758cbdaad6109eed60ca

  Please apply/backport these two patches from the 2.24 branch. They fix a 
memory DOS, originally reported against mate-panel here:
  https://github.com/mate-desktop/mate-panel/issues/479

  For the GTK3 version of this bug, see bug 1641914
  Note that MATE is GTK2 only for Ubuntu 16.04 LTS.

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

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


[Touch-packages] [Bug 1681912] Re: [Zesty] missing dnsmasq-base package breaks NetworkManager connection sharing feature

2017-04-12 Thread Martin Wimpress
** Summary changed:

- [Zesty] missing dnsmasq package breaks NetworkManager connection sharing 
feature
+ [Zesty] missing dnsmasq-base package breaks NetworkManager connection sharing 
feature

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

Title:
  [Zesty] missing dnsmasq-base package breaks NetworkManager connection
  sharing feature

Status in ubuntu-mate:
  New
Status in network-manager package in Ubuntu:
  New
Status in ubuntu-mate-meta package in Ubuntu:
  Invalid

Bug description:
  Network settings in Zesty allow users to define a connection as
  "Shared to other computers", this does not currently work in Ubuntu
  MATE 17.04 Beta 2 at least for wired connections.

  The reason, from the logs is that dnsmasq binary, from dnsmasq package
  is not present:

  [...]
  Apr 11 20:37:22 Edge NetworkManager[946]:   [1491935842.1052] 
Executing: /sbin/iptables --table nat --insert POSTROUTING --source 
10.42.0.0/255.255.255.0 ! --destination 10.42.0.0/255.255.255.0 --jump 
MASQUERADE
  Apr 11 20:37:22 Edge NetworkManager[946]:  [1491935842.1117] device 
(enp1s0f2): share: (enp1s0f2) failed to start dnsmasq: Could not find "dnsmasq" 
binary
  Apr 11 20:37:22 Edge NetworkManager[946]:   [1491935842.1119] 
Executing: /sbin/iptables --table nat --delete POSTROUTING --source 
10.42.0.0/255.
  [...]

  ouroumov@Edge:~$ apt-cache policy dnsmasq
  dnsmasq:
    Installed: (none)
    Candidate: 2.76-5
    Version table:
   2.76-5 500
  500 http://fr.archive.ubuntu.com/ubuntu zesty/universe amd64 Packages
  500 http://fr.archive.ubuntu.com/ubuntu zesty/universe i386 Packages

  After installing package dnsmasq, connection sharing works again as
  expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: ubuntu-mate-core 1.190
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Tue Apr 11 20:39:44 2017
  InstallationDate: Installed on 2017-04-05 (6 days ago)
  InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Beta amd64 (20170321.1)
  SourcePackage: ubuntu-mate-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1681912/+subscriptions

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


[Touch-packages] [Bug 1681912] Re: [Zesty] missing dnsmasq package breaks NetworkManager connection sharing feature

2017-04-11 Thread Martin Wimpress
** Also affects: network-manager (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: ubuntu-mate-meta (Ubuntu)
   Status: New => Invalid

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

Title:
  [Zesty] missing dnsmasq package breaks NetworkManager connection
  sharing feature

Status in ubuntu-mate:
  New
Status in network-manager package in Ubuntu:
  New
Status in ubuntu-mate-meta package in Ubuntu:
  Invalid

Bug description:
  Network settings in Zesty allow users to define a connection as
  "Shared to other computers", this does not currently work in Ubuntu
  MATE 17.04 Beta 2 at least for wired connections.

  The reason, from the logs is that dnsmasq binary, from dnsmasq package
  is not present:

  [...]
  Apr 11 20:37:22 Edge NetworkManager[946]:   [1491935842.1052] 
Executing: /sbin/iptables --table nat --insert POSTROUTING --source 
10.42.0.0/255.255.255.0 ! --destination 10.42.0.0/255.255.255.0 --jump 
MASQUERADE
  Apr 11 20:37:22 Edge NetworkManager[946]:  [1491935842.1117] device 
(enp1s0f2): share: (enp1s0f2) failed to start dnsmasq: Could not find "dnsmasq" 
binary
  Apr 11 20:37:22 Edge NetworkManager[946]:   [1491935842.1119] 
Executing: /sbin/iptables --table nat --delete POSTROUTING --source 
10.42.0.0/255.
  [...]

  ouroumov@Edge:~$ apt-cache policy dnsmasq
  dnsmasq:
    Installed: (none)
    Candidate: 2.76-5
    Version table:
   2.76-5 500
  500 http://fr.archive.ubuntu.com/ubuntu zesty/universe amd64 Packages
  500 http://fr.archive.ubuntu.com/ubuntu zesty/universe i386 Packages

  After installing package dnsmasq, connection sharing works again as
  expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: ubuntu-mate-core 1.190
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Tue Apr 11 20:39:44 2017
  InstallationDate: Installed on 2017-04-05 (6 days ago)
  InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Beta amd64 (20170321.1)
  SourcePackage: ubuntu-mate-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1681912/+subscriptions

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


[Touch-packages] [Bug 1641915] Re: GtkToolButtons clip and overlap

2017-03-27 Thread Martin Wimpress
** Changed in: ubuntu-themes (Ubuntu Xenial)
   Status: Incomplete => New

** Changed in: ubuntu-themes (Ubuntu Xenial)
 Assignee: Martin Wimpress (flexiondotorg) => (unassigned)

** Changed in: ubuntu-themes
 Assignee: Martin Wimpress (flexiondotorg) => (unassigned)

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

Title:
  GtkToolButtons clip and overlap

Status in Ubuntu theme:
  In Progress
Status in ubuntu-themes package in Ubuntu:
  Fix Released
Status in ubuntu-themes source package in Xenial:
  New

Bug description:
  [ Impact ]

  GtkToolButton styling causes buttons to clip and overlap each other. This
  can be seen in gnome-disks and the Ubiquity disk partitioner for Ubuntu 
16.04.1. See the attached screenshot:

    * https://bugs.launchpad.net/ubuntu-
  themes/+bug/1641915/+attachment/4777652/+files/gtk-toolbutton-
  clipping.png

  [ Test Case ]

  Start a Ubuntu 16.04.1 live session and "Try Ubuntu". From the live
  Desktop click the Ubuntu logo in the launcher, search for Disks and
  start it. Select the hard disk from the side panel, then look at and
  hover over, the buttons beneath the representation of the disk
  partitions. You'll notice the buttons clip/overlap as illustrated in
  the screenshot above.

  Now double click the "Install Ubuntu 16.04.1 LTS" icon on the desktop.
  The Installer will start, click Continue, click Continue, check
  "Something else" and then the click Continue. Look at, and hover over,
  the buttons beneath the tree representing the disk partitions. You'll
  notice they clip/overlap as illustrated in the screenshot above.

  After the patched ubuntu-themes has been installed the buttons
  described in the steps above will no longer clip/overlap.

  [ Regression Potential ]

  None expected.

  [ Other Info ]

  This issue does not present in Yakkety or Zesty.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1641915/+subscriptions

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


[Touch-packages] [Bug 1046129] Re: Use New Radio/Check Assets for Gtk-2.0 Theme Consistency

2017-03-26 Thread Martin Wimpress
** Also affects: ubuntu-mate-artwork (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: ubuntu-mate-artwork (Ubuntu)
   Status: New => Fix Committed

** Changed in: ubuntu-mate-artwork (Ubuntu)
   Importance: Undecided => Medium

** Changed in: ubuntu-mate-artwork (Ubuntu)
 Assignee: (unassigned) => Martin Wimpress (flexiondotorg)

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

Title:
  Use New Radio/Check Assets for Gtk-2.0 Theme Consistency

Status in Ubuntu theme:
  Fix Committed
Status in ubuntu-mate-artwork package in Ubuntu:
  Fix Committed
Status in ubuntu-themes package in Ubuntu:
  Triaged

Bug description:
  Add new radio and check assets for use with gtk-2.0 Ambiance/Radiance
  for theme consistency.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1046129/+subscriptions

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


[Touch-packages] [Bug 1624171] Re: systemd-logind error at startup if systemd-shim and upstart-sysv

2017-03-18 Thread Martin Wimpress
** No longer affects: ubuntu-mate

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

Title:
  systemd-logind error at startup if systemd-shim and upstart-sysv

Status in systemd-shim package in Ubuntu:
  New
Status in upstart package in Ubuntu:
  New

Bug description:
  If systemd-shim is installed with upstart-sysv on PPC64 system running
  ubuntu-mate 16.04.1, the system will not boot to desktop and the below
  error message is generated after logging in to TTY:

  [  646.474008] systemd-logind[2208]: Failed to start user service,
  ignoring: Unknown unit: user@1000.service

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1624171/+subscriptions

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


[Touch-packages] [Bug 1645687] Re: 50unattended-upgrades.ucf-dist

2017-03-16 Thread Martin Wimpress
** Also affects: unattended-upgrades (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: ubuntu-mate

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

Title:
  50unattended-upgrades.ucf-dist

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  During a refresh procedure of Ubuntu-Mate 16.04 (on 29th November,
  2016) the following notice appeared in the first line of the terminal.
  (Refreshing among others the linux-
  image-4.4.0-51-generic_4.4.0-51.72_i386.deb package):

  N: "50unattended-upgrades.ucf-dist" file(s) has/have been left out of
  consideration in the "/etc/apt/apt.conf.d/ map having invalid file
  extension.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1645687/+subscriptions

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


[Touch-packages] [Bug 1648237] Re: update-manager and unattended-upgrades failure

2017-03-16 Thread Martin Wimpress
** No longer affects: ubuntu-mate

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

Title:
  update-manager and unattended-upgrades failure

Status in unattended-upgrades package in Ubuntu:
  Confirmed
Status in update-manager package in Ubuntu:
  Confirmed

Bug description:
  A series of issues about update-manager and unattended-upgrade. I have set 
the system to:
  - automatically check for update daily
  - when there are security updates, download and install them automatically
  - when there are other updates, display them immediately.

  What occurs:

  (1) unattended-upgrade runs on boot but systematically its log states
  every day that: "No packages found that can be upgraded unattended and
  no pending auto-removals" even where there are security updates to
  install.

  (2) update-manager appears not to refresh the cache automatically
  after boot.

  (3) when the cache is manually refreshed so there are updates, update-
  manager runs after a subsequent boot and appears in the panel. However
  clicking on it leads it to simply disappear.

  (4) update-manager will not launch from the menu. When launched from a
  terminal it runs correctly, refreshes the cache and will install
  updates.

  No crash reports, nothing obvious in log files.

  Ubuntu-MATE 16.10 clean install, fully updated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1648237/+subscriptions

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


[Touch-packages] [Bug 1663421] Re: systemd-udevd crashed with SIGABRT in __open_nocancel()

2017-03-16 Thread Martin Wimpress
** No longer affects: ubuntu-mate

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

Title:
  systemd-udevd crashed with SIGABRT in __open_nocancel()

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Description: Ubuntu Zesty Zapus (development branch)
  Release: 17.04
  Destro: Ubuntu Mate
  Windows manager: Marco(compton GPU compositor)
  Video card: Radeon RX 460 4GB 128bit
  OpenGL vendor string: X.Org

  I get this error after usb-gtk-creator finish to upload a os on a usb
  stick.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: udev 232-8
  ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5
  Uname: Linux 4.9.0-15-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  Date: Fri Feb 10 01:30:13 2017
  ExecutablePath: /lib/systemd/systemd-udevd
  InstallationDate: Installed on 2017-02-06 (3 days ago)
  InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Alpha amd64 (20170125)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcCmdline: /lib/systemd/systemd-udevd
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.9.0-15-generic.efi.signed 
root=UUID=8b97de22-0e3b-4da0-8676-7c8865800def ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   __open_nocancel () at ../sysdeps/unix/syscall-template.S:84
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: systemd-udevd crashed with SIGABRT in __open_nocancel()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 05/05/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.40
  dmi.board.name: A88M-G/3.1
  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:bd05/05/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnA88M-G/3.1:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.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.

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

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


[Touch-packages] [Bug 1600136] Re: App indicator does not show icon for Qt apps or with custom icons

2017-02-22 Thread Martin Wimpress
** Tags added: isv

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

Title:
  App indicator does not show icon for Qt apps or with custom icons

Status in Qt:
  In Progress
Status in Snappy:
  New
Status in appmenu-qt5 package in Ubuntu:
  Fix Released
Status in libappindicator package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src package in Ubuntu:
  In Progress
Status in snapd package in Ubuntu:
  In Progress
Status in sni-qt package in Ubuntu:
  Fix Released
Status in appmenu-qt5 source package in Xenial:
  Fix Committed
Status in libappindicator source package in Xenial:
  Fix Committed
Status in qtbase-opensource-src source package in Xenial:
  New
Status in snapd source package in Xenial:
  New
Status in sni-qt source package in Xenial:
  Fix Committed

Bug description:
  Snaps that use the app indicator area via Qt can't display their icon
  there.

  Steps to reproduce and screenshot:
  https://github.com/nuttyartist/notes/pull/77

  Some research:

  - Uses http://doc.qt.io/qt-5/qsystemtrayicon.html
  - The indicator icon is created under /tmp under a randomly generated 
directory name

  didrocks mentions also:

  1. The application says "this is my menu, and here is my icon at that 
address", the address being /tmp/blablabla
  2. appindicator receives the bus messages
  3. and says "let's have a look at this icon at that address"
  4. BUT! /tmp in the snap is different form system /tmp

  


  SRU bug for libappindicator:

  [Impact]

  Indicator icons pointing to a position inside the snap aren't properly
  found by unity, that shows a "missing icon" emblem

  [Test case]

  * Download this yaml file http://pastebin.com/raw/FpEvQYGN and save it as 
snapcraft.yaml
    in any folder you want
  * Run:
    - snapcraft prime
    - sudo snap try prime
    - snap run gtk3-appindicator

  An indicator should open (with proper icon), then if you select "Set
  icon with Full Path" and/or "Enable Local Theme" from its menu, you
  should see a proper icon.

  When snaps are generated in non updated systems, the icon will be
  still missing.

  [Regression potential]

  If $SNAP is defined for an app not running in snap confinement the
  icons couldn't be properly visible

  


  SRU bug for appmenu-qt5:

  [Impact]

  Indicator icons pointing to a position inside the snap aren't properly
  found by unity, that shows a "missing icon" emblem

  [Test case]

  * Download this yaml file http://pastebin.com/raw/KeZ1udjW and save it as 
snapcraft.yaml
    in any folder you want
  * Run:
    - snapcraft prime
    - sudo snap try prime
    - snap run qt5-systray

  An indicator should open, with the proper icon showin. From the window
  you can change the icon type, and all the types should work.

  When snaps are generated in non updated systems, the icons (except the
  Themed one) will be still missing.

  [Regression potential]

  If $SNAP env variable is defined for an app not running in snap
  confinement the icons couldn't be properly visible

  


  SRU bug for sni-qt:

  [Impact]

  Indicator icons pointing to a position inside the snap aren't properly
  found by unity, that shows a "missing icon" emblem

  [Test case]

  * Download this yaml file http://pastebin.com/raw/EZjQS5CH and save it as 
snapcraft.yaml
in any folder you want
  * Run:
- snapcraft prime
- sudo snap try prime
- snap run qt4-systray

  An indicator should open, with the proper icon showin. From the window
  you can change the icon type, and all the types should work.

  When snaps are generated in non updated systems, the icons (except the
  Themed one) will be still missing.

  [Regression potential]

  If $SNAP env variable is defined for an app not running in snap
  confinement the icons couldn't be properly visible

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

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


[Touch-packages] [Bug 1624738] Re: Firefox search and location boxes have black borders when unselected

2017-02-06 Thread Martin Wimpress
** Changed in: ubuntu-themes (Ubuntu)
   Status: In Progress => Invalid

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

Title:
  Firefox search and location boxes have black borders when unselected

Status in ubuntu-mate-artwork package in Ubuntu:
  Fix Released
Status in ubuntu-themes package in Ubuntu:
  Invalid

Bug description:
  [Impact]

  As seen in the attached screen shot the borders around Firefox
  location and search entry boxes are black when unselected, but they
  should be grey.

  The black borders are inconsistent with the rest of the Ubuntu theming
  and it looks jarring.

  The issue is resolved by styling the 'frame' selector, which Firefox
  uses to style the Search and Location entry boxes. Some overrides are
  then applied to prevent frames incorrectly rendering borders in other
  applications.

  [Test Case]

  To observe the issue simply open Firefox and look at the Search or
  Location entry boxes while they are unselected, the borders will be
  black.

  After installing the patched theme doing to same will result in the
  borders being rendered using an appropriate shade of grey.

  [Regression Potential]

  It is possible that some GTK3+ applications may now render frames with
  a border where they previously did not. That said, the default
  applications in Ubuntu have been checked for this regression and the
  appropriate overrides have been added.

  The default installed applications in Ubuntu have been tested to
  ensure they do not regress in the manner described above.

  [Other Info]
   
  Should Firefox style the Search and Location entry boxes with a discrete 
selector in the future then the styling added to work around the black border 
could be removed/updated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-mate-artwork/+bug/1624738/+subscriptions

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


[Touch-packages] [Bug 1622686] Re: double header in 16.10

2017-01-27 Thread Martin Wimpress
I installed Xenial daily, completed an oem-setup, installed humanity-
icon-theme 0.6.10.1 and prepared the system. I confirm that the double
header in oem-firstboot is fixed.

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

Title:
  double header in 16.10

Status in humanity-icon-theme package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Fix Released
Status in humanity-icon-theme source package in Xenial:
  Fix Committed
Status in ubiquity source package in Xenial:
  New
Status in humanity-icon-theme source package in Yakkety:
  Fix Committed
Status in ubiquity source package in Yakkety:
  New

Bug description:
  [Impact]

  During install and oem-firstboot, the header bar at the top of the
  screen in Ubiquity is twice as tall as it should be on hidpi screens
  (looking like two normal sized header bars stacked on top of each
  other), and the blue a11y icon is double sized.

  This looks obviously incorrect and ugly and makes a bad first
  impression on users installing Ubuntu on a hidpi laptop or customers
  of Ubuntu OEMs booting new machines for the first time.  Arstechnica
  commented negatively on this in their review of Dell's XPS 13:
  http://arstechnica.com/gadgets/2017/01/dells-latest-xps-13-de-still-
  delivers-linux-now-embraces-svelte-hardware/

  Users of the Dell XPS 13 are affected as well as users of other brands
  of laptops with hidpi screens.  System76 is temporarily carrying a
  patched version of Humanity to work around this bug.

  The a11y icon is double-sized because the version of Humanity shipping
  in Ubuntu doesn't support @2 hidpi scaling, which results in the
  header bar doubling its height.  Because the header bar is drawn with
  CAIRO_PAD_REPEAT, the gradient is repeated so it looks like two bars
  stacked one on top of the other.  The fix to the Humanity icon theme
  adds @2 hidpi support, which shrinks the icon and restores the header
  bar to its normal height.

  
  [Test Case]
  ISO install:
  1. Grab an Ubuntu iso and proceed to install (not "try") Ubuntu on a computer 
with a hidpi screen.
  2. Note the double-sized header and icon during install.
  - Using an iso with a fixed version of Humanity, the header and icon 
should look normal.

  OEM-Firstboot:
  1. Grab an Ubuntu iso and do an oem-install on on a computer with a hidpi 
screen.
  2. After installing, click the launcher icon to "Prepare for shipping to the 
end user" and reboot.
  3. During oem-firstboot, note the double-sized header and icon during install.
  - To test the fix, install a fixed version of humanity before preparing 
the system for the end user.
  

  [Regression Potential]

  This patch affects the look of anything using the Humanity icon set.
  The look of Nautilus, and many other GTK apps will be affected.  This
  is not a regression but fixes another bug and resolves a discrepancy
  between rendering of icons on hidpi screens vs lowdpi screens.

  The biggest risk for regression comes from the off chance that there
  is an error or omission in the index.theme files.  Comparing icons on
  a broad range of applications and systems should catch this class of
  issues.  If any issues with icons are found, check there.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/humanity-icon-theme/+bug/1622686/+subscriptions

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


[Touch-packages] [Bug 1578810] Re: Insensitive (disabled) toolbar icons in GTK3 are not dimmed

2016-12-21 Thread Martin Wimpress
** Changed in: ubuntu-themes
   Status: In Progress => Fix Released

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

Title:
  Insensitive (disabled) toolbar icons in GTK3 are not dimmed

Status in remmina:
  Invalid
Status in Ubuntu theme:
  Fix Released
Status in Wireshark:
  Invalid
Status in ubuntu-themes package in Ubuntu:
  Fix Released
Status in ubuntu-themes source package in Xenial:
  Fix Released
Status in ubuntu-themes source package in Yakkety:
  Fix Released

Bug description:
  [ Impact ]

  Disabled (GTK 3.20) and Insensitive (GTK <= 3.18) icons are not
  dimmed, therefore there is no visual indication that an icon in the
  toolbar is inactionable.

  [ Test Case ]

  This issue can be observed in Xenial and Yakkety.

  Install `gtk-3-examples` and run `gtk3-widget-factory`, look at the
  toolbar on Page 2, the last icon (tooltip 'Insert something') is
  disabled/insensitive and should be dimmed, but is not.

  After applying the relevant merge proposal (see below), the
  disabled/insensitive icon in the toolbar on Page 2 of gtk3-widgets-
  factory will now be dimmed.

  [ Regression Potential ]

  None.

  [ Other Info ]

  This issue can also be reproduced on Xenial and Yakkety using:

* Remmina (from the archive)
* Wireshark (from the archive)
* Eclipse (downloaded)

  To reproduce with Eclipse, Eclipse has to be downloaded since the
  version in the archive uses GTK2+ for styling, and dims insensitive
  icons correctly.

* Download a recent Eclipse 
https://www.eclipse.org/downloads/download.php?file=/eclipse/downloads/drops4/R-4.5.2-201602121500/eclipse-SDK-4.5.2-linux-gtk-x86_64.tar.gz
* Extract and execute the "eclipse" executable
* In the toolbar, several icons look enabled even though they are not. For 
example the Save icon (Floppy).

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

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


[Touch-packages] [Bug 1643467] Re: Firefox 50 blocks Ubuntu 14.04 LTS's version of libavcodec

2016-11-30 Thread Not Martin Wimpress
Allowing "obsolete" codecs to run is an absolutely terrible idea. For
those of you on 14.04, I'd recommend updating libav-tools by PPA
following this answer: http://askubuntu.com/a/851192 That's your best
bet so far.

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

Title:
  Firefox 50 blocks Ubuntu 14.04 LTS's version of libavcodec

Status in firefox package in Ubuntu:
  Confirmed
Status in libav package in Ubuntu:
  Confirmed

Bug description:
  Whenever it tries to play a video, Firefox 50 displays this message at the 
top of every page:
  "libavcodec may be vulnerable or is not supported, and should be updated to 
play video"

  https://dxr.mozilla.org/mozilla-central/source/browser/locales/en-
  
US/chrome/browser/browser.properties?q=%22libavcodec+may+be+vulnerable%22_type=single#742

  Firefox refuses any libavcodec version prior to 54.35.1 (unless
  media.libavcodec.allow-obsolete==true).

  https://dxr.mozilla.org/mozilla-
  central/source/dom/media/platforms/ffmpeg/FFmpegLibWrapper.cpp#60

  Users should not be subjected to this warning, as it is vague (does not 
instruct them how to fix it).
  Ubuntu 14.04 LTS should ship with an updated version of libavcodec.

  DistroRelease: Ubuntu 14.04
  Package: firefox 50.0+build2-0ubuntu0.14.04.2

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

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


[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

2016-11-21 Thread Not Martin Wimpress
Does anyone have this problem in Linux Mint 18? "Unattended-Upgrade
::Remove-New-Unused-Dependencies" also does not exist for me but the
package was last updated a month ago, which leads me to believe the
configuration file "50unattended-upgrades" wasn't "replaced" with the
new version. Also, the package has other issues including not fetching
from the correct repos as it's a stock Ubuntu config.

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

Title:
  Kernels not autoremoving, causing out of space error on LVM or
  Encrypted installation or on any installation, when /boot partition
  gets full

Status in unattended-upgrades package in Ubuntu:
  Fix Released

Bug description:
  Currently if one chooses to use LVM or encrypted install, a /boot
  partition is created of 236Mb

  Once kernel updates start being released this partition soon fills
  until people are left unable to upgrade.

  While you and I might know that we need to watch partition space, many
  of the people we have installing think that a windows disk is a disk
  and not a partition, education is probably the key - but in the
  meantime support venues keep needing to deal with the fact the
  partition is too small and/or old kernels are not purged as new ones
  install.

  For workaround and sytem repair, see
  https://help.ubuntu.com/community/Lubuntu/Documentation/RemoveOldKernels

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1357093/+subscriptions

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


[Touch-packages] [Bug 1641915] Re: GtkToolButton styling clips and overlaps

2016-11-15 Thread Martin Wimpress
** Description changed:

- GtkToolButton styling clips and overlaps, this can be seen in gnome-
- disks and the Ubiquity disk partitioner for Ubuntu 16.04.1. See the
- attached screenshot.
+ [ Impact ]
+ 
+ GtkToolButton styling causes buttons to clip and overlap each other. This
+ can be seen in gnome-disks and the Ubiquity disk partitioner for Ubuntu 
16.04.1. See the attached screenshot:
+ 
+   * https://bugs.launchpad.net/ubuntu-
+ themes/+bug/1641915/+attachment/4777652/+files/gtk-toolbutton-
+ clipping.png
+ 
+ [ Test Case ]
+ 
+ Start a Ubuntu 16.04.1 live session and "Try Ubuntu". From the live
+ Desktop click the Ubuntu logo in the launcher, search for Disks and
+ start it. Select the hard disk from the side panel, then look at and
+ hover over, the buttons beneath the representation of the disk
+ partitions. You'll notice the buttons clip/overlap as illustrated in the
+ screenshot above.
+ 
+ Now double click the "Install Ubuntu 16.04.1 LTS" icon on the desktop.
+ The Installer will start, click Continue, click Continue, check
+ "Something else" and then the click Continue. Look at, and hover over,
+ the buttons beneath the tree representing the disk partitions. You'll
+ notice they clip/overlap as illustrated in the screenshot above.
+ 
+ After the patched ubuntu-themes has been installed the buttons described
+ in the steps above will no longer clip/overlap.
+ 
+ [ Regression Potential ]
+ 
+ None expected.

** Description changed:

  [ Impact ]
  
  GtkToolButton styling causes buttons to clip and overlap each other. This
  can be seen in gnome-disks and the Ubiquity disk partitioner for Ubuntu 
16.04.1. See the attached screenshot:
  
-   * https://bugs.launchpad.net/ubuntu-
+   * https://bugs.launchpad.net/ubuntu-
  themes/+bug/1641915/+attachment/4777652/+files/gtk-toolbutton-
  clipping.png
  
  [ Test Case ]
  
  Start a Ubuntu 16.04.1 live session and "Try Ubuntu". From the live
  Desktop click the Ubuntu logo in the launcher, search for Disks and
  start it. Select the hard disk from the side panel, then look at and
  hover over, the buttons beneath the representation of the disk
  partitions. You'll notice the buttons clip/overlap as illustrated in the
  screenshot above.
  
  Now double click the "Install Ubuntu 16.04.1 LTS" icon on the desktop.
  The Installer will start, click Continue, click Continue, check
  "Something else" and then the click Continue. Look at, and hover over,
  the buttons beneath the tree representing the disk partitions. You'll
  notice they clip/overlap as illustrated in the screenshot above.
  
  After the patched ubuntu-themes has been installed the buttons described
  in the steps above will no longer clip/overlap.
  
  [ Regression Potential ]
  
  None expected.
+ 
+ [ Other Info ]
+ 
+ This issue does not present in Yakkety or Zesty.

** Summary changed:

- GtkToolButton styling clips and overlaps
+ GtkToolButtons clip and overlap

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

Title:
  GtkToolButtons clip and overlap

Status in Ubuntu theme:
  In Progress
Status in ubuntu-themes package in Ubuntu:
  Fix Released
Status in ubuntu-themes source package in Xenial:
  In Progress

Bug description:
  [ Impact ]

  GtkToolButton styling causes buttons to clip and overlap each other. This
  can be seen in gnome-disks and the Ubiquity disk partitioner for Ubuntu 
16.04.1. See the attached screenshot:

    * https://bugs.launchpad.net/ubuntu-
  themes/+bug/1641915/+attachment/4777652/+files/gtk-toolbutton-
  clipping.png

  [ Test Case ]

  Start a Ubuntu 16.04.1 live session and "Try Ubuntu". From the live
  Desktop click the Ubuntu logo in the launcher, search for Disks and
  start it. Select the hard disk from the side panel, then look at and
  hover over, the buttons beneath the representation of the disk
  partitions. You'll notice the buttons clip/overlap as illustrated in
  the screenshot above.

  Now double click the "Install Ubuntu 16.04.1 LTS" icon on the desktop.
  The Installer will start, click Continue, click Continue, check
  "Something else" and then the click Continue. Look at, and hover over,
  the buttons beneath the tree representing the disk partitions. You'll
  notice they clip/overlap as illustrated in the screenshot above.

  After the patched ubuntu-themes has been installed the buttons
  described in the steps above will no longer clip/overlap.

  [ Regression Potential ]

  None expected.

  [ Other Info ]

  This issue does not present in Yakkety or Zesty.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1641915/+subscriptions

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


[Touch-packages] [Bug 1641915] Re: GtkToolButton styling clips and overlaps

2016-11-15 Thread Martin Wimpress
** Changed in: ubuntu-themes (Ubuntu)
 Assignee: Martin Wimpress (flexiondotorg) => (unassigned)

** Changed in: ubuntu-themes (Ubuntu)
   Status: In Progress => Fix Released

** Changed in: ubuntu-themes (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: ubuntu-themes (Ubuntu Xenial)
   Importance: Undecided => Low

** Changed in: ubuntu-themes (Ubuntu Xenial)
 Assignee: (unassigned) => Martin Wimpress (flexiondotorg)

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

Title:
  GtkToolButton styling clips and overlaps

Status in Ubuntu theme:
  In Progress
Status in ubuntu-themes package in Ubuntu:
  Fix Released
Status in ubuntu-themes source package in Xenial:
  In Progress

Bug description:
  GtkToolButton styling clips and overlaps, this can be seen in gnome-
  disks and the Ubiquity disk partitioner for Ubuntu 16.04.1. See the
  attached screenshot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1641915/+subscriptions

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


[Touch-packages] [Bug 1641915] Re: GtkToolButton styling clips and overlaps

2016-11-15 Thread Martin Wimpress
This following branch fixes this issue in Xenial:

  * lp:~flexiondotorg/ubuntu-themes/ubuntu-themes-gtktoolbutton-
lp1641915-xenial 

The attached screen shot illustrates the fix.

** Attachment added: "gtk-toolbutton-clipping-fixed.png"
   
https://bugs.launchpad.net/ubuntu-themes/+bug/1641915/+attachment/424/+files/gtk-toolbutton-clipping-fixed.png

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

Title:
  GtkToolButton styling clips and overlaps

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

Bug description:
  GtkToolButton styling clips and overlaps, this can be seen in gnome-
  disks and the Ubiquity disk partitioner for Ubuntu 16.04.1. See the
  attached screenshot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1641915/+subscriptions

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


[Touch-packages] [Bug 1641915] Re: GtkToolButton styling clips and overlaps

2016-11-15 Thread Martin Wimpress
** Changed in: ubuntu-themes
   Status: New => In Progress

** Changed in: ubuntu-themes
 Assignee: (unassigned) => Martin Wimpress (flexiondotorg)

** Also affects: ubuntu-themes (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: ubuntu-themes (Ubuntu)
 Assignee: (unassigned) => Martin Wimpress (flexiondotorg)

** Changed in: ubuntu-themes (Ubuntu)
   Status: New => In Progress

** Branch linked: lp:~flexiondotorg/ubuntu-themes/ubuntu-themes-
gtktoolbutton-lp1641915-xenial

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

Title:
  GtkToolButton styling clips and overlaps

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

Bug description:
  GtkToolButton styling clips and overlaps, this can be seen in gnome-
  disks and the Ubiquity disk partitioner for Ubuntu 16.04.1. See the
  attached screenshot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1641915/+subscriptions

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


[Touch-packages] [Bug 1442050] Re: (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown error -2

2016-11-07 Thread Not Martin Wimpress
@cpollock, I don't know your situation specifically so I would be
speculating at best. But, if I were in your position I might do the
following (but only do these steps at your own risk and have backups of
your data elsewhere):


1. delete any and all listed printers in your printer manager.
2. purge the foo2zjs drivers (I'm not familiar with the "correct" way of doing 
this so ask someone else.)
3. ensure hplip is fully-purged from your system by doing something like a 
"sudo apt purge hplip hplip-data"
4. now, install hplip and use hp's own drivers as explained in #22. Something 
curious from your log: hpmud is a component of hplip so perhaps it was 
installed at one time and wasn't properly purged before you installed the 
foo2zjs drivers and now colord is complaining that it can't see your 1020's 
color profile because foo2zjs isn't allowing it (pure speculation again.)
5. If those steps don't solve it, then perhaps purging and re-installing cups 
and then re-doing the steps over again might.


Good luck.

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

Title:
  (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown
  error -2

Status in colord package in Ubuntu:
  Confirmed

Bug description:
  Get that error logged into journalctl

  (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown
  error -2

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-6ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3
  Uname: Linux 3.19.0-12-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17-0ubuntu1
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Thu Apr  9 11:57:02 2015
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 046d:c50e Logitech, Inc. Cordless Mouse Receiver
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-12-generic 
root=UUID=7b1f4a51-558f-468f-85e0-f815d2f791e1 ro
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3002
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5W DH Deluxe
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5W DH Deluxe
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTEK COMPUTER INC

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

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


[Touch-packages] [Bug 1442050] Re: (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown error -2

2016-11-07 Thread Not Martin Wimpress
Btw, for those of you with the cups scheduler messages as well and still
want to share with samba shares, you can disable just printer sharing
and that will also effectively get rid of these messages as well. The
guide to do that is here:
https://forums.linuxmint.com/viewtopic.php?p=1231018#p1231018

Be sure to reboot.

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

Title:
  (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown
  error -2

Status in colord package in Ubuntu:
  Confirmed

Bug description:
  Get that error logged into journalctl

  (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown
  error -2

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-6ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3
  Uname: Linux 3.19.0-12-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17-0ubuntu1
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Thu Apr  9 11:57:02 2015
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 046d:c50e Logitech, Inc. Cordless Mouse Receiver
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-12-generic 
root=UUID=7b1f4a51-558f-468f-85e0-f815d2f791e1 ro
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3002
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5W DH Deluxe
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5W DH Deluxe
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTEK COMPUTER INC

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

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


[Touch-packages] [Bug 1478173] Re: Ambiance & Radiance themes are missing a "background-color" for tooltip elements (needed for GTK3-enabled Firefox Nightly)

2016-10-26 Thread Martin Wimpress
** Branch linked: lp:~flexiondotorg/ubuntu-themes/lp1478173

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

Title:
  Ambiance & Radiance themes are missing a "background-color" for
  tooltip elements (needed for GTK3-enabled Firefox Nightly)

Status in One Hundred Papercuts:
  Confirmed
Status in Ubuntu theme:
  In Progress
Status in ubuntu-themes package in Ubuntu:
  In Progress

Bug description:
  Firefox Nightlies recently became GTK3-enabled, and that uncovered an
  issue with Ubuntu's Ambiance & Radiance GTK3 themes.

  They're missing a "background-color" for the .tooltip {...} CSS rule
  in their config files. They have a "tooltip_bg_color" variable, which
  they use to set up a background-image (really a gradient), but there's
  no background-color.

  This causes problems for GTK3-enabled Firefox, because it reads back some 
system-colors by setting up a dummy tooltip and reading the 
(currently-not-useful) background-color and the foreground-color. Right now, 
this produces unreadable output (for the user) with 
white-text-on-a-white-background, as shown in this screenshot:
   https://bug1187203.bmoattachments.org/attachment.cgi?id=8638351

  The solution is simple -- just add this one line to the ".tooltip" CSS rule 
in gtk-widgets.css:
 background-color: @tooltip_bg_color;

  For more details, see bug
  https://bugzilla.mozilla.org/show_bug.cgi?id=1187203

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: light-themes 14.04+15.04.20150410-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-23.24-generic 3.19.8-ckt2
  Uname: Linux 3.19.0-23-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Jul 24 17:35:25 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-05-18 (67 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1442050] Re: (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown error -2

2016-10-19 Thread Not Martin Wimpress
Btw @cpollock, I noticed you have a 1020 printer. HP uses a convoluted
method to ensure you accept their license agreement to install their
proprietary driver for this particular printer. If you haven't already
done so by first installing the hplip gui and then manually running the
hp setup, then go ahead and do a "sudo apt-get install hplip-gui", turn
on the printer, then "delete" the printer listed in your list of
installed printers, then do a "hp-setup", accept the license agreement,
follow the instructions to complete installation, reboot, and now you're
free to uninstall "hplip-gui" if you want. (Just don't also uninstall
"hplip".)

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

Title:
  (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown
  error -2

Status in colord package in Ubuntu:
  Confirmed

Bug description:
  Get that error logged into journalctl

  (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown
  error -2

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-6ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3
  Uname: Linux 3.19.0-12-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17-0ubuntu1
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Thu Apr  9 11:57:02 2015
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 046d:c50e Logitech, Inc. Cordless Mouse Receiver
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-12-generic 
root=UUID=7b1f4a51-558f-468f-85e0-f815d2f791e1 ro
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3002
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5W DH Deluxe
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5W DH Deluxe
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTEK COMPUTER INC

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

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


[Touch-packages] [Bug 1442050] Re: (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown error -2

2016-10-19 Thread Not Martin Wimpress
I was referring to the cups scheduler. You might have issues with
applications (or system applications as in the case with samba) trying
to perpetually connect to your devices' embedded colour profiles and
fails spectacularly when said profile no longer is accessible.

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

Title:
  (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown
  error -2

Status in colord package in Ubuntu:
  Confirmed

Bug description:
  Get that error logged into journalctl

  (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown
  error -2

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-6ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3
  Uname: Linux 3.19.0-12-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17-0ubuntu1
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Thu Apr  9 11:57:02 2015
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 046d:c50e Logitech, Inc. Cordless Mouse Receiver
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-12-generic 
root=UUID=7b1f4a51-558f-468f-85e0-f815d2f791e1 ro
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3002
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5W DH Deluxe
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5W DH Deluxe
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTEK COMPUTER INC

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

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


[Touch-packages] [Bug 1442050] Re: (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown error -2

2016-10-18 Thread Not Martin Wimpress
Regarding: "Aug 8 06:38:33 tau systemd[1]: Started CUPS Scheduler.
Aug 8 06:38:33 tau colord[2924]: (colord:2924): Cd-WARNING **: failed to get 
session [pid 12325]: No such device or address"

This bug is successfully resolved by removing "samba" and "samba-common"
in synaptic. Apparently colord has severe issues with printer sharing
when the device is not longer available (possibly by default gufw
rules.)

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

Title:
  (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown
  error -2

Status in colord package in Ubuntu:
  Confirmed

Bug description:
  Get that error logged into journalctl

  (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown
  error -2

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-6ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3
  Uname: Linux 3.19.0-12-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17-0ubuntu1
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Thu Apr  9 11:57:02 2015
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 046d:c50e Logitech, Inc. Cordless Mouse Receiver
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-12-generic 
root=UUID=7b1f4a51-558f-468f-85e0-f815d2f791e1 ro
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3002
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5W DH Deluxe
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5W DH Deluxe
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTEK COMPUTER INC

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

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


[Touch-packages] [Bug 1578810] Re: Insensitive (disabled) toolbar icons in GTK3 are not dimmed

2016-10-14 Thread Martin Wimpress
** Description changed:

- Distributor ID:   Ubuntu
- Description:  Ubuntu 16.04 LTS
- Release:  16.04
- Codename: xenial
+ [ Impact ]
  
- Since Ubuntu 16.04, the disabled buttons in Eclipse toolbars look like they 
are still enabled. See attached screenshots.
- This is very easy to reproduce:
- 1. Download a recent Eclipse 
(https://www.eclipse.org/downloads/download.php?file=/eclipse/downloads/drops4/R-4.5.2-201602121500/eclipse-SDK-4.5.2-linux-gtk-x86_64.tar.gz)
- 2. Extract and execute the "eclipse" executable
- 3. In the toolbar, several icons look enabled even though they are not. For 
example the Save icon (Floppy).
+ Disabled (GTK 3.20) and Insensitive (GTK <= 3.18) icons are not dimmed,
+ therefore there is no visual indication that an icon in the toolbar is
+ inactionable.
+ 
+ [ Test Case ]
+ 
+ This issue can be observed in Xenial and Yakkety.
+ 
+ Install `gtk-3-examples` and run `gtk3-widget-factory`, look at the
+ toolbar on Page 2, the last icon (tooltip 'Insert something') is
+ disabled/insensitive and should be dimmed, but is not.
+ 
+ After applying the relevant merge proposal (see below), the
+ disabled/insensitive icon in the toolbar on Page 2 of gtk3-widgets-
+ factory will now be dimmed.
+ 
+ [ Regression Potential ]
+ 
+ None.
+ 
+ [ Other Info ]
+ 
+ This issue can also be reproduced on Xenial and Yakkety using:
+ 
+   * Remmina (from the archive)
+   * Wireshark (from the archive)
+   * Eclipse (downloaded)
+ 
+ To reproduce with Eclipse, Eclipse has to be downloaded since the
+ version in the archive uses GTK2+ for styling, and dims insensitive
+ icons correctly.
+ 
+   * Download a recent Eclipse 
https://www.eclipse.org/downloads/download.php?file=/eclipse/downloads/drops4/R-4.5.2-201602121500/eclipse-SDK-4.5.2-linux-gtk-x86_64.tar.gz
+   * Extract and execute the "eclipse" executable
+   * In the toolbar, several icons look enabled even though they are not. For 
example the Save icon (Floppy).

** Branch linked: lp:~flexiondotorg/ubuntu-themes/xenial-icon-dim-
lp1578810

** Branch linked: lp:~flexiondotorg/ubuntu-themes/yakkety-icon-dim-
lp1578810

** Changed in: remmina
   Status: New => Invalid

** Changed in: wireshark
   Status: New => Invalid

** Changed in: ubuntu-themes
   Status: New => In Progress

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

Title:
  Insensitive (disabled) toolbar icons in GTK3 are not dimmed

Status in remmina:
  Invalid
Status in Ubuntu theme:
  In Progress
Status in Wireshark:
  Invalid
Status in ubuntu-themes package in Ubuntu:
  In Progress

Bug description:
  [ Impact ]

  Disabled (GTK 3.20) and Insensitive (GTK <= 3.18) icons are not
  dimmed, therefore there is no visual indication that an icon in the
  toolbar is inactionable.

  [ Test Case ]

  This issue can be observed in Xenial and Yakkety.

  Install `gtk-3-examples` and run `gtk3-widget-factory`, look at the
  toolbar on Page 2, the last icon (tooltip 'Insert something') is
  disabled/insensitive and should be dimmed, but is not.

  After applying the relevant merge proposal (see below), the
  disabled/insensitive icon in the toolbar on Page 2 of gtk3-widgets-
  factory will now be dimmed.

  [ Regression Potential ]

  None.

  [ Other Info ]

  This issue can also be reproduced on Xenial and Yakkety using:

* Remmina (from the archive)
* Wireshark (from the archive)
* Eclipse (downloaded)

  To reproduce with Eclipse, Eclipse has to be downloaded since the
  version in the archive uses GTK2+ for styling, and dims insensitive
  icons correctly.

* Download a recent Eclipse 
https://www.eclipse.org/downloads/download.php?file=/eclipse/downloads/drops4/R-4.5.2-201602121500/eclipse-SDK-4.5.2-linux-gtk-x86_64.tar.gz
* Extract and execute the "eclipse" executable
* In the toolbar, several icons look enabled even though they are not. For 
example the Save icon (Floppy).

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

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


[Touch-packages] [Bug 1578810] Re: Insensitive (disabled) toolbar icons in GTK3 are not dimmed

2016-10-14 Thread Martin Wimpress
Here is a merge proposal for Yakkety:

  * https://code.launchpad.net/~flexiondotorg/ubuntu-themes/yakkety-
icon-dim-lp1578810/+merge/308480

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

Title:
  Insensitive (disabled) toolbar icons in GTK3 are not dimmed

Status in remmina:
  Invalid
Status in Ubuntu theme:
  In Progress
Status in Wireshark:
  Invalid
Status in ubuntu-themes package in Ubuntu:
  In Progress

Bug description:
  [ Impact ]

  Disabled (GTK 3.20) and Insensitive (GTK <= 3.18) icons are not
  dimmed, therefore there is no visual indication that an icon in the
  toolbar is inactionable.

  [ Test Case ]

  This issue can be observed in Xenial and Yakkety.

  Install `gtk-3-examples` and run `gtk3-widget-factory`, look at the
  toolbar on Page 2, the last icon (tooltip 'Insert something') is
  disabled/insensitive and should be dimmed, but is not.

  After applying the relevant merge proposal (see below), the
  disabled/insensitive icon in the toolbar on Page 2 of gtk3-widgets-
  factory will now be dimmed.

  [ Regression Potential ]

  None.

  [ Other Info ]

  This issue can also be reproduced on Xenial and Yakkety using:

* Remmina (from the archive)
* Wireshark (from the archive)
* Eclipse (downloaded)

  To reproduce with Eclipse, Eclipse has to be downloaded since the
  version in the archive uses GTK2+ for styling, and dims insensitive
  icons correctly.

* Download a recent Eclipse 
https://www.eclipse.org/downloads/download.php?file=/eclipse/downloads/drops4/R-4.5.2-201602121500/eclipse-SDK-4.5.2-linux-gtk-x86_64.tar.gz
* Extract and execute the "eclipse" executable
* In the toolbar, several icons look enabled even though they are not. For 
example the Save icon (Floppy).

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

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


[Touch-packages] [Bug 1578810] Re: Insensitive (disabled) toolbar icons in GTK3 are not dimmed

2016-10-14 Thread Martin Wimpress
Here is a merge proposal for Xenial:

  * https://code.launchpad.net/~flexiondotorg/ubuntu-themes/xenial-icon-
dim-lp1578810/+merge/308481

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

Title:
  Insensitive (disabled) toolbar icons in GTK3 are not dimmed

Status in remmina:
  Invalid
Status in Ubuntu theme:
  In Progress
Status in Wireshark:
  Invalid
Status in ubuntu-themes package in Ubuntu:
  In Progress

Bug description:
  [ Impact ]

  Disabled (GTK 3.20) and Insensitive (GTK <= 3.18) icons are not
  dimmed, therefore there is no visual indication that an icon in the
  toolbar is inactionable.

  [ Test Case ]

  This issue can be observed in Xenial and Yakkety.

  Install `gtk-3-examples` and run `gtk3-widget-factory`, look at the
  toolbar on Page 2, the last icon (tooltip 'Insert something') is
  disabled/insensitive and should be dimmed, but is not.

  After applying the relevant merge proposal (see below), the
  disabled/insensitive icon in the toolbar on Page 2 of gtk3-widgets-
  factory will now be dimmed.

  [ Regression Potential ]

  None.

  [ Other Info ]

  This issue can also be reproduced on Xenial and Yakkety using:

* Remmina (from the archive)
* Wireshark (from the archive)
* Eclipse (downloaded)

  To reproduce with Eclipse, Eclipse has to be downloaded since the
  version in the archive uses GTK2+ for styling, and dims insensitive
  icons correctly.

* Download a recent Eclipse 
https://www.eclipse.org/downloads/download.php?file=/eclipse/downloads/drops4/R-4.5.2-201602121500/eclipse-SDK-4.5.2-linux-gtk-x86_64.tar.gz
* Extract and execute the "eclipse" executable
* In the toolbar, several icons look enabled even though they are not. For 
example the Save icon (Floppy).

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

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


[Touch-packages] [Bug 1578810] Re: Insensitive (disabled) toolbar icons in GTK3 are not dimmed

2016-10-14 Thread Martin Wimpress
This issue can be observed in Xenial and Yakkety.

Install `gtk-3-examples` and run `gtk3-widget-factory`, look at the
toolbar on Page 2, the last icon (tooltip 'Insert something') is
disabled and should be dimmed, but is not.

I have also reproduced this issue on Xenial and Yakkety using:

  * Remmina (from the archive)
  * Wireshark (from the archive)
  * Eclipse (downloaded)

To reproduce with eclipse it has to be downloaded since the version in
the archive uses GTK2+ for styling, and dims insensitive icons
correctly.

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

Title:
  Insensitive (disabled) toolbar icons in GTK3 are not dimmed

Status in remmina:
  Invalid
Status in Ubuntu theme:
  In Progress
Status in Wireshark:
  Invalid
Status in ubuntu-themes package in Ubuntu:
  In Progress

Bug description:
  [ Impact ]

  Disabled (GTK 3.20) and Insensitive (GTK <= 3.18) icons are not
  dimmed, therefore there is no visual indication that an icon in the
  toolbar is inactionable.

  [ Test Case ]

  This issue can be observed in Xenial and Yakkety.

  Install `gtk-3-examples` and run `gtk3-widget-factory`, look at the
  toolbar on Page 2, the last icon (tooltip 'Insert something') is
  disabled/insensitive and should be dimmed, but is not.

  After applying the relevant merge proposal (see below), the
  disabled/insensitive icon in the toolbar on Page 2 of gtk3-widgets-
  factory will now be dimmed.

  [ Regression Potential ]

  None.

  [ Other Info ]

  This issue can also be reproduced on Xenial and Yakkety using:

* Remmina (from the archive)
* Wireshark (from the archive)
* Eclipse (downloaded)

  To reproduce with Eclipse, Eclipse has to be downloaded since the
  version in the archive uses GTK2+ for styling, and dims insensitive
  icons correctly.

* Download a recent Eclipse 
https://www.eclipse.org/downloads/download.php?file=/eclipse/downloads/drops4/R-4.5.2-201602121500/eclipse-SDK-4.5.2-linux-gtk-x86_64.tar.gz
* Extract and execute the "eclipse" executable
* In the toolbar, several icons look enabled even though they are not. For 
example the Save icon (Floppy).

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

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


[Touch-packages] [Bug 1578810] Re: Insensitive (disabled) toolbar icons in GTK3 are not dimmed

2016-10-13 Thread Martin Wimpress
** Also affects: ubuntu-themes (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: ubuntu-themes (Ubuntu)
 Assignee: (unassigned) => Martin Wimpress (flexiondotorg)

** Changed in: ubuntu-themes (Ubuntu)
   Importance: Undecided => Medium

** Changed in: ubuntu-themes (Ubuntu)
   Status: New => In Progress

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

Title:
  Insensitive (disabled) toolbar icons in GTK3 are not dimmed

Status in remmina:
  New
Status in Ubuntu theme:
  New
Status in Wireshark:
  New
Status in ubuntu-themes package in Ubuntu:
  In Progress

Bug description:
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04 LTS
  Release:  16.04
  Codename: xenial

  Since Ubuntu 16.04, the disabled buttons in Eclipse toolbars look like they 
are still enabled. See attached screenshots.
  This is very easy to reproduce:
  1. Download a recent Eclipse 
(https://www.eclipse.org/downloads/download.php?file=/eclipse/downloads/drops4/R-4.5.2-201602121500/eclipse-SDK-4.5.2-linux-gtk-x86_64.tar.gz)
  2. Extract and execute the "eclipse" executable
  3. In the toolbar, several icons look enabled even though they are not. For 
example the Save icon (Floppy).

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

-- 
Mailing list: https://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   3   >