[Touch-packages] [Bug 2060898] Re: Trying to install gimp-help-en threatens to install wslu

[Martin Wimpress ]

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

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

** Changed in: ubuntu-mate-meta (Ubuntu Noble)
   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/2060898

Title:
  Trying to install gimp-help-en threatens to install wslu

Status in edubuntu-meta package in Ubuntu:
  Fix Released
Status in kubuntu-meta package in Ubuntu:
  Fix Released
Status in lubuntu-meta 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:
  Invalid
Status in ubuntustudio-meta package in Ubuntu:
  Fix Released
Status in wslu package in Ubuntu:
  Invalid
Status in edubuntu-meta source package in Noble:
  Fix Released
Status in kubuntu-meta source package in Noble:
  Fix Released
Status in lubuntu-meta source package in Noble:
  Fix Released
Status in ubuntu-budgie-meta source package in Noble:
  Fix Released
Status in ubuntu-mate-meta source package in Noble:
  Fix Committed
Status in ubuntu-meta source package in Noble:
  Invalid
Status in ubuntustudio-meta source package in Noble:
  Fix Released
Status in wslu source package in Noble:
  Invalid

Bug description:
  Filing this against ubuntu-meta since I believe this is a seed problem
  that potentially affects all variants of Ubuntu (flavors or
  otherwise).

  wslu is "a collection of utilities for the Windows 10 Linux Subsystem,
  such as for converting Linux paths to a Windows paths or creating
  Linux application shortcuts on the Windows 10 Desktop." Obviously this
  package should *never* be installed on a desktop or even on most VMs,
  but only within WSL instances. However...

  wslu provides the virtual package www-browser, as one of its features
  is to open links in Windows 10 using the default browser set there.
  This means that if a package depends or recommends www-browser, it may
  attempt to pull in one of several packages, wslu included. In the
  past, this hasn't been a problem because Firefox was present on all
  flavor images, and Firefox provides www-browser as well. However, now
  that Firefox is a Snap, it is possible for Firefox to be installed
  without the firefox transitional apt package being installed. (This is
  the case in a default installation of Kubuntu Noble Beta.) As it turns
  out, Kubuntu Noble Beta ships with *no* packages that provide www-
  browser, meaning that any package that depends on it will have to
  install a new browser.

  Due to some stroke of misfortune, apt is picking wslu out of all
  packages as the package for this use case. Installing gimp-help-en
  will also install www-browser, which results in wslu becoming
  installed.

  wslu causes quite a few problems when installed on a desktop system -
  among them, the syslog is spammed with errors due to the system not in
  fact being a WSL VM, audio breaks in weird ways, and application
  launchers sometimes fail. Why this happens is unclear, but the issues
  appear to resolve once wslu is removed from the system. It is
  therefore probably a good idea to avoid wslu becoming installed on
  accident in this way.

  Probably the best way to resolve this is to ensure that some package
  that provides www-browser is available on every Ubuntu image. This
  could be done via seeding or by adding a package to ubuntu-minimal.
  Alternatively, wslu could be set to no longer provide www-browser,
  though it's unclear if that would break its functionality.

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


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

[Touch-packages] [Bug 2017786] Re: update script in ubuntu-meta not handling germinate or specified versions

[Martin Wimpress ]

** Changed in: ubuntu-mate-meta (Ubuntu)
   Status: New => Won't Fix

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

Title:
  update script in ubuntu-meta not handling germinate or specified
  versions

Status in edubuntu-meta package in Ubuntu:
  Won't Fix
Status in kubuntu-meta package in Ubuntu:
  Fix Released
Status in lubuntu-meta package in Ubuntu:
  New
Status in ubuntu-budgie-meta package in Ubuntu:
  New
Status in ubuntu-mate-meta package in Ubuntu:
  Won't Fix
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-unity-meta package in Ubuntu:
  New
Status in ubuntucinnamon-meta package in Ubuntu:
  New
Status in ubuntukylin-meta package in Ubuntu:
  New
Status in ubuntustudio-meta package in Ubuntu:
  Won't Fix
Status in xubuntu-meta package in Ubuntu:
  Won't Fix

Bug description:
  update script handled debootstrap and devscripts, does not handle
  germinate. also doesn't handle potential specified versions in the
  package directory.

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


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

[Touch-packages] [Bug 1948339] Re: Logon screen can be bypassed using various shortcuts

[Martin Wimpress ]

@bkanbach I can version marco Recommends ensuring both packages update
in lockstep. I have spoken to the Ubuntu Security team and they will
handle the CVE assignment.

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

Title:
  Logon screen can be bypassed using various shortcuts

Status in arctica-greeter package in Ubuntu:
  Fix Committed
Status in lightdm package in Ubuntu:
  Invalid
Status in marco package in Ubuntu:
  Fix Committed
Status in mate-settings-daemon package in Ubuntu:
  Invalid

Bug description:
  Hi,

  my little daughter discovered a logon screen bypass in Ubuntu Mate
  21.10 after hitting the keyboard for a while.

  It turns out that several keyboard shortcuts are allowed while Ubuntu
  Mate is locked (arctica-greeter):

  - Mod4 + S (mate-search-tool)
  - Mod4 + E (Open Caja / File Explorer)
  - CTRL + Shift + Esc (mate-system-monitor)
  - PRNT (Screenshot)

  All of the mentioned shortcuts could be used to spawn a file explorer
  (Caja) or various other binaries as user "lightdm", who owns the logon
  screen.

  Although an interactive terminal like mate-terminal, xterm, lxterm
  etc. could not be opened directly, there are various options to run
  commands as the lightdm user, for example by creating a shell script
  using "caja", and execute it directly using the GUI.

  I've attached Proof-of-Concept GIFs for all shortcuts mentioned above.
  There might be additional shortcuts that could be used to achieve the
  same, however I'm not aware about every shortcut that is configured,
  but I suppose that the root cause is located somewhere in arctica-
  greeter, rather than within every single binary launched by shortcuts.

  The bug was reproduced on a fresh installation of Ubuntu Mate 21.10. I
  haven't tested other versions of Ubuntu Mate yet.

  Please find additional version details below:

  $ apt-cache policy lightdm

  lightdm:
    Installed: 1.30.0-0ubuntu4
    Candidate: 1.30.0-0ubuntu4
    Version table:
   *** 1.30.0-0ubuntu4 500
  500 http://de.archive.ubuntu.com/ubuntu impish/universe amd64 Packages
  100 /var/lib/dpkg/status

  $ apt-cache policy arctica-greeter

  arctica-greeter:
    Installed: 0.99.1.5-2nmu1
    Candidate: 0.99.1.5-2nmu1
    Version table:
   *** 0.99.1.5-2nmu1 500
  500 http://de.archive.ubuntu.com/ubuntu impish/universe amd64 Packages
  100 /var/lib/dpkg/status

  Thanks,
  Basti

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


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

[Touch-packages] [Bug 1948339] Re: Logon screen can be bypassed using various shortcuts

[Martin Wimpress ]

** Changed in: arctica-greeter (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  Logon screen can be bypassed using various shortcuts

Status in arctica-greeter package in Ubuntu:
  Fix Committed
Status in lightdm package in Ubuntu:
  Invalid
Status in marco package in Ubuntu:
  Fix Committed
Status in mate-settings-daemon package in Ubuntu:
  Invalid

Bug description:
  Hi,

  my little daughter discovered a logon screen bypass in Ubuntu Mate
  21.10 after hitting the keyboard for a while.

  It turns out that several keyboard shortcuts are allowed while Ubuntu
  Mate is locked (arctica-greeter):

  - Mod4 + S (mate-search-tool)
  - Mod4 + E (Open Caja / File Explorer)
  - CTRL + Shift + Esc (mate-system-monitor)
  - PRNT (Screenshot)

  All of the mentioned shortcuts could be used to spawn a file explorer
  (Caja) or various other binaries as user "lightdm", who owns the logon
  screen.

  Although an interactive terminal like mate-terminal, xterm, lxterm
  etc. could not be opened directly, there are various options to run
  commands as the lightdm user, for example by creating a shell script
  using "caja", and execute it directly using the GUI.

  I've attached Proof-of-Concept GIFs for all shortcuts mentioned above.
  There might be additional shortcuts that could be used to achieve the
  same, however I'm not aware about every shortcut that is configured,
  but I suppose that the root cause is located somewhere in arctica-
  greeter, rather than within every single binary launched by shortcuts.

  The bug was reproduced on a fresh installation of Ubuntu Mate 21.10. I
  haven't tested other versions of Ubuntu Mate yet.

  Please find additional version details below:

  $ apt-cache policy lightdm

  lightdm:
    Installed: 1.30.0-0ubuntu4
    Candidate: 1.30.0-0ubuntu4
    Version table:
   *** 1.30.0-0ubuntu4 500
  500 http://de.archive.ubuntu.com/ubuntu impish/universe amd64 Packages
  100 /var/lib/dpkg/status

  $ apt-cache policy arctica-greeter

  arctica-greeter:
    Installed: 0.99.1.5-2nmu1
    Candidate: 0.99.1.5-2nmu1
    Version table:
   *** 0.99.1.5-2nmu1 500
  500 http://de.archive.ubuntu.com/ubuntu impish/universe amd64 Packages
  100 /var/lib/dpkg/status

  Thanks,
  Basti

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


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

[Touch-packages] [Bug 1948339] Re: Logon screen can be bypassed using various shortcuts

[Martin Wimpress ]

** Changed in: arctica-greeter (Ubuntu)
   Status: Triaged => In Progress

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

Title:
  Logon screen can be bypassed using various shortcuts

Status in arctica-greeter package in Ubuntu:
  In Progress
Status in lightdm package in Ubuntu:
  Invalid
Status in marco package in Ubuntu:
  In Progress
Status in mate-settings-daemon package in Ubuntu:
  Invalid

Bug description:
  Hi,

  my little daughter discovered a logon screen bypass in Ubuntu Mate
  21.10 after hitting the keyboard for a while.

  It turns out that several keyboard shortcuts are allowed while Ubuntu
  Mate is locked (arctica-greeter):

  - Mod4 + S (mate-search-tool)
  - Mod4 + E (Open Caja / File Explorer)
  - CTRL + Shift + Esc (mate-system-monitor)
  - PRNT (Screenshot)

  All of the mentioned shortcuts could be used to spawn a file explorer
  (Caja) or various other binaries as user "lightdm", who owns the logon
  screen.

  Although an interactive terminal like mate-terminal, xterm, lxterm
  etc. could not be opened directly, there are various options to run
  commands as the lightdm user, for example by creating a shell script
  using "caja", and execute it directly using the GUI.

  I've attached Proof-of-Concept GIFs for all shortcuts mentioned above.
  There might be additional shortcuts that could be used to achieve the
  same, however I'm not aware about every shortcut that is configured,
  but I suppose that the root cause is located somewhere in arctica-
  greeter, rather than within every single binary launched by shortcuts.

  The bug was reproduced on a fresh installation of Ubuntu Mate 21.10. I
  haven't tested other versions of Ubuntu Mate yet.

  Please find additional version details below:

  $ apt-cache policy lightdm

  lightdm:
    Installed: 1.30.0-0ubuntu4
    Candidate: 1.30.0-0ubuntu4
    Version table:
   *** 1.30.0-0ubuntu4 500
  500 http://de.archive.ubuntu.com/ubuntu impish/universe amd64 Packages
  100 /var/lib/dpkg/status

  $ apt-cache policy arctica-greeter

  arctica-greeter:
    Installed: 0.99.1.5-2nmu1
    Candidate: 0.99.1.5-2nmu1
    Version table:
   *** 0.99.1.5-2nmu1 500
  500 http://de.archive.ubuntu.com/ubuntu impish/universe amd64 Packages
  100 /var/lib/dpkg/status

  Thanks,
  Basti

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


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

[Touch-packages] [Bug 1948339] Re: Logon screen can be bypassed using various shortcuts

[Martin Wimpress ]

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

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

Title:
  Logon screen can be bypassed using various shortcuts

Status in arctica-greeter package in Ubuntu:
  Triaged
Status in lightdm package in Ubuntu:
  Invalid
Status in marco package in Ubuntu:
  In Progress
Status in mate-settings-daemon package in Ubuntu:
  Invalid

Bug description:
  Hi,

  my little daughter discovered a logon screen bypass in Ubuntu Mate
  21.10 after hitting the keyboard for a while.

  It turns out that several keyboard shortcuts are allowed while Ubuntu
  Mate is locked (arctica-greeter):

  - Mod4 + S (mate-search-tool)
  - Mod4 + E (Open Caja / File Explorer)
  - CTRL + Shift + Esc (mate-system-monitor)
  - PRNT (Screenshot)

  All of the mentioned shortcuts could be used to spawn a file explorer
  (Caja) or various other binaries as user "lightdm", who owns the logon
  screen.

  Although an interactive terminal like mate-terminal, xterm, lxterm
  etc. could not be opened directly, there are various options to run
  commands as the lightdm user, for example by creating a shell script
  using "caja", and execute it directly using the GUI.

  I've attached Proof-of-Concept GIFs for all shortcuts mentioned above.
  There might be additional shortcuts that could be used to achieve the
  same, however I'm not aware about every shortcut that is configured,
  but I suppose that the root cause is located somewhere in arctica-
  greeter, rather than within every single binary launched by shortcuts.

  The bug was reproduced on a fresh installation of Ubuntu Mate 21.10. I
  haven't tested other versions of Ubuntu Mate yet.

  Please find additional version details below:

  $ apt-cache policy lightdm

  lightdm:
    Installed: 1.30.0-0ubuntu4
    Candidate: 1.30.0-0ubuntu4
    Version table:
   *** 1.30.0-0ubuntu4 500
  500 http://de.archive.ubuntu.com/ubuntu impish/universe amd64 Packages
  100 /var/lib/dpkg/status

  $ apt-cache policy arctica-greeter

  arctica-greeter:
    Installed: 0.99.1.5-2nmu1
    Candidate: 0.99.1.5-2nmu1
    Version table:
   *** 0.99.1.5-2nmu1 500
  500 http://de.archive.ubuntu.com/ubuntu impish/universe amd64 Packages
  100 /var/lib/dpkg/status

  Thanks,
  Basti

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


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

[Touch-packages] [Bug 1892299] Re: [20.04] Keyboard volume rendered useless because of root's userspace?

[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/1892299

Title:
  [20.04] Keyboard volume rendered useless because of root's userspace?

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  This is super minor. Yet it's super juicy:

  Running 20.04-latest and with the following audio hardware
  configuration:

  $ arecord -L
  default
  Playback/recording through the PulseAudio sound server
  surround21
  2.1 Surround output to Front and Subwoofer speakers
  surround40
  4.0 Surround output to Front and Rear speakers
  surround41
  4.1 Surround output to Front, Rear and Subwoofer speakers
  surround50
  5.0 Surround output to Front, Center and Rear speakers
  surround51
  5.1 Surround output to Front, Center, Rear and Subwoofer speakers
  surround71
  7.1 Surround output to Front, Center, Side, Rear and Woofer speakers
  null
  Discard all samples (playback) or generate zero samples (capture)
  samplerate
  Rate Converter Plugin Using Samplerate Library
  speexrate
  Rate Converter Plugin Using Speex Resampler
  jack
  JACK Audio Connection Kit
  oss
  Open Sound System
  pulse
  PulseAudio Sound Server
  upmix
  Plugin for channel upmix (4,6,8)
  vdownmix
  Plugin for channel downmix (stereo) with a simple spacialization
  usbstream:CARD=HDMI
  HDA ATI HDMI
  USB Stream Output
  sysdefault:CARD=Generic
  HD-Audio Generic, ALC887-VD Analog
  Default Audio Device
  front:CARD=Generic,DEV=0
  HD-Audio Generic, ALC887-VD Analog
  Front speakers
  dmix:CARD=Generic,DEV=0
  HD-Audio Generic, ALC887-VD Analog
  Direct sample mixing device
  dmix:CARD=Generic,DEV=2
  HD-Audio Generic, ALC887-VD Alt Analog
  Direct sample mixing device
  dsnoop:CARD=Generic,DEV=0
  HD-Audio Generic, ALC887-VD Analog
  Direct sample snooping device
  dsnoop:CARD=Generic,DEV=2
  HD-Audio Generic, ALC887-VD Alt Analog
  Direct sample snooping device
  hw:CARD=Generic,DEV=0
  HD-Audio Generic, ALC887-VD Analog
  Direct hardware device without any conversions
  hw:CARD=Generic,DEV=2
  HD-Audio Generic, ALC887-VD Alt Analog
  Direct hardware device without any conversions
  plughw:CARD=Generic,DEV=0
  HD-Audio Generic, ALC887-VD Analog
  Hardware device with all software conversions
  plughw:CARD=Generic,DEV=2
  HD-Audio Generic, ALC887-VD Alt Analog
  Hardware device with all software conversions
  usbstream:CARD=Generic
  HD-Audio Generic
  USB Stream Output
  $

  $ aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: HDMI [HDA ATI HDMI], device 3: HDMI 0 [HDMI 0]
    Subdevices: 1/1
    Subdevice #0: subdevice #0
  card 2: Generic [HD-Audio Generic], device 0: ALC887-VD Analog [ALC887-VD 
Analog]
    Subdevices: 0/1
    Subdevice #0: subdevice #0
  card 2: Generic [HD-Audio Generic], device 1: ALC887-VD Digital [ALC887-VD 
Digital]
    Subdevices: 1/1
    Subdevice #0: subdevice #0
  $

  I am using card 2 off this last paste.

  If I open a folder in caja containing videos and I play one of them
  using regular user and celluloid, volume knob on my keyboard works
  fine.

  But if I then open any other video from an "Open as administrator"
  caja window, it will not play any sound(based on my non-expert status
  I can only assume that this happens because root space and user space
  do not share the same default audio settings??)

  First question/problem/request: just like when applying monitor
  resolution changes into Control Center and applying them system wide,
  can you also please make it the same for the audio hardware output? As
  from a user perspective, it makes no sense at all to segregate the
  hardware values for sound when jumping in root in Ubuntu.

  Now my real problem is if/when I close my caja window that is in
  priviledge mode and I then re-open a video w/ celluloid with my
  regular user, sounds of course works fine, but my keyboard volume knob
  isn't responding anymore even though I see the volume on screen going
  up and down when I scroll it, the sound waves do not actually increase
  nor decrease.

  Some full moons ago, I posted something on UM forum which related of
  something similiar and here it is as a FYI: https://ubuntu-
  mate.community/t/19-10-problem-with-my-sound/20338/3

  Furthermore, and again only as a FYI, I have blacklisted "hdi" and
  "snd_hda_codec_hdmi" in /etc/modprobe.d/snd-blacklist.conf and have
  rebooted my system to take effect. Hence maybe when you will try
  reproducing this you will also need to blacklist those 2 modules to
  get this volume control on your keyboard not listening...

  And while you have your hands into the audio code, and as of why I had
 

[Touch-packages] [Bug 1837765] Re: mono, crackly audio, device not appearing raspberry pi 2B

[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/1837765

Title:
  mono, crackly audio, device not appearing raspberry pi 2B

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I am using the 3.5 jack to speakers on a raspberry pi 2B

  As detailed here: https://ubuntu-mate.community/t/audio-output-mono-
  instead-of-stereo-ubuntu-18-04-1-rpi/18001

  Audio output is mono
  Audio output is delayed and crackly for desktop sounds, as well as sometimes 
simply silent

  I note that no sound device shows up in Sound Preferences / Hardware

  Some workarounds from that thread:

  Editing /etc/pulse/default.pa such that:

  load-module module-udev-detect tsched=0

  and commenting out:

  load-module module-suspend-on-idle

  Results in a device "Built-in Audio Analog mono output" showing up in Sound 
Preferences/Hardware,
  audio is mono, but does not crackle/miss and desktop sounds work seemingly as 
expected.

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


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

[Touch-packages] [Bug 1874689] Re: alsa force-reload needed to fix my sound after upgrade to 20.04

[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 alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1874689

Title:
  alsa force-reload needed to fix my sound after upgrade to 20.04

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  After upgrading from Ubuntu Mate 18.04 LTS to Ubuntu Mate 20.04 LTS
  "sudo alsa force-reload" is needed to fix my sound.

  I upgraded yesterday (23rd) before the official announcements of 20.04
  LTS. Using "do-release-upgrade -d".

  I'm not sure yet how often I have to run "sudo alsa force-reload".
  When I have no sound a reboot is not a guranteed fix although it
  worked once.

  Booting into a Ubuntu Desktop 20.04 LTS gets working sounds each time
  I tried.

  Audio: Device-1: Intel 6 Series/C200 Series Family High Definition Audio 
driver: snd_hda_intel 
 Sound Server: ALSA v: k5.4.0-26-generic

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


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

[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 lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1706770

Title:
  Lock screen can be bypassed when auto-login is enabled via gnome-
  system-tools

Status in arctica-greeter package in Ubuntu:
  Invalid
Status in gnome-system-tools package in Ubuntu:
  Triaged
Status in lightdm package in Ubuntu:
  Invalid
Status in mate-screensaver package in Ubuntu:
  Invalid
Status in mate-session-manager package in Ubuntu:
  Invalid
Status in ubuntu-mate-meta package in Ubuntu:
  Fix Committed

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/+source/arctica-greeter/+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 1706770] Re: Lock screen can be bypassed when auto-login is enabled.

[Martin Wimpress ]

This issue is caused by the Users and Groups utility which is part of
`gnome-system-tools`. When changing the password from "Asked on logon"
to "Not asked on logon" the user is added to the `nopasswdlogin` group
and this is what causes the switch-user screen to not ask for a
password.

If you select the option to not require a password to login during
installation, it is not possible to bypass authentication when switching
users. This is because `autologin-user` is set to your username in
`/etc/lightdm/lightdm.conf` and that works correctly.

`gnome-system-tools` was originally included in Ubuntu MATE because it
offers user and time management features. But it can now be removed from
the Ubuntu MATE default install because recent versions of MATE Control
Center provide user and time management.

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

** Summary changed:

- Lock screen can be bypassed when auto-login is enabled.
+ Lock screen can be bypassed when auto-login is enabled via gnome-system-tools

-- 
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 via gnome-
  system-tools

Status in arctica-greeter package in Ubuntu:
  Invalid
Status in gnome-system-tools package in Ubuntu:
  Triaged
Status in lightdm package in Ubuntu:
  Invalid
Status in mate-screensaver package in Ubuntu:
  Invalid
Status in mate-session-manager package in Ubuntu:
  Invalid
Status in ubuntu-mate-meta package in Ubuntu:
  In Progress

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/+source/arctica-greeter/+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 1706770] Re: Lock screen can be bypassed when auto-login is enabled.

[Martin Wimpress ]

** Also affects: gnome-system-tools (Ubuntu)
   Importance: Undecided
   Status: New

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

** Changed in: lightdm (Ubuntu)
   Status: Fix Committed => Invalid

** Changed in: arctica-greeter (Ubuntu)
   Status: New => Invalid

** Changed in: gnome-system-tools (Ubuntu)
   Status: New => Confirmed

** Changed in: gnome-system-tools (Ubuntu)
   Status: Confirmed => Triaged

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

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

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

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

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

Status in arctica-greeter package in Ubuntu:
  Invalid
Status in gnome-system-tools package in Ubuntu:
  Triaged
Status in lightdm package in Ubuntu:
  Invalid
Status in mate-screensaver package in Ubuntu:
  Invalid
Status in mate-session-manager package in Ubuntu:
  Invalid
Status in ubuntu-mate-meta package in Ubuntu:
  Triaged

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/+source/arctica-greeter/+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 1706770] Re: Lock screen can be bypassed when auto-login is enabled.

[Martin Wimpress ]

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

** Also affects: arctica-greeter (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 arctica-greeter package in Ubuntu:
  New
Status in gnome-system-tools package in Ubuntu:
  New
Status in lightdm package in Ubuntu:
  Fix Committed
Status in mate-screensaver package in Ubuntu:
  New
Status in mate-session-manager package in Ubuntu:
  Invalid

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/+source/arctica-greeter/+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 1706770] Re: Lock screen can be bypassed when auto-login is enabled.

[Martin Wimpress ]

** No longer affects: ubuntu-mate

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

-- 
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 arctica-greeter package in Ubuntu:
  New
Status in lightdm package in Ubuntu:
  Fix Committed
Status in mate-screensaver package in Ubuntu:
  New
Status in mate-session-manager package in Ubuntu:
  Invalid

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/+source/arctica-greeter/+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 1769362] Re: with multiple monitors, lightDM does not appear on the display set as primary

[Martin Wimpress ]

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

Title:
  with multiple monitors, lightDM does not appear on the display set as
  primary

Status in lightdm package in Ubuntu:
  New

Bug description:
  TV hooked up to a laptop; laptop is marked as Primary Display.  With
  the TV turned off, the laptop went idle into the screensaver.  When
  woken, lightDM is rendered on the (off) TV not the laptop display.

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


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

[Touch-packages] [Bug 1893590] Re: [20.04.1] Uncooperative network center (more irritant than joy)

[Martin Wimpress ]

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

Title:
  [20.04.1] Uncooperative network center (more irritant than joy)

Status in network-manager package in Ubuntu:
  New

Bug description:
  A network center in GUI. So many reasons to love it. Here's a
  particularly basic one which surely would make my mom want NOT to use
  Linux:

  Network connections -> Wired connection -> IPv4 settings -> Method: from 
Automatic(DHCP) to Manual + add address/netmask/gateway+dns server+SAVE = OK
  ip a = specified IP address manually

  Network connections -> Wired connection -> IPv4 settings -> Method: from 
Manual to Automatic(DHCP)+SAVE = OK
  disconnect -> reconnect
  ip a = same specified IP address manually!! But I was expecting to be leased 
a DHCP IP??

  solution: Network connections -> Wired connection -> IPv4 settings ->
  delete manually added IP address + SAVE + disconnect + reconnect = ip
  a = DHCP IP, \o/

  Food for thought: Thankfully I didn't have 6 different IP
  configurations in place...

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


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

[Touch-packages] [Bug 1904796] Re: screensaver hijacks audio preferences

[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/1904796

Title:
  screensaver hijacks audio preferences

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Using 20.04.1-latest, on a laptop that is plugged via HDMI to a tv:
  if/when the audio is set to digital and the computer falls into sleep
  mode, upon waking up, the session's audio defaults back to analog
  audio output.

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


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

[Touch-packages] [Bug 1906138] Re: Indeterminate Qt progress bars don't display properly in 20.04

[Martin Wimpress ]

** No longer affects: ubuntu-mate

** No longer affects: mate-themes (Ubuntu)

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

Title:
  Indeterminate Qt progress bars don't display properly in 20.04

Status in qtbase-opensource-src package in Ubuntu:
  New

Bug description:
  In Ubuntu MATE 20.04, a Qt program with an indeterminate progress bar
  (meaning its minimum and maximum values have both been set to zero)
  does not display properly. It is supposed to animate in a way that
  shows that something is happening with an unknown time remaining.
  Instead, it sits still with its progress bar showing approximately 25
  to 30% progress.

  To test this, make a simple Qt program with a QProgressBar in the main
  window, and add these lines to the constructor of the main window:

  ui->progressBar->setMinimum(0);
  ui->progressBar->setMaximum(0);

  This problem is not present in standard Ubuntu 20.04. Standard Ubuntu
  correctly animates the indeterminate progress bar. It's unclear to me
  which package is at fault, but it seems to be something specific to
  Ubuntu MATE because standard Ubuntu 20.04 doesn't have this problem.

  Ubuntu MATE 18.04 also has this problem with Qt 5. With Qt 4 it
  doesn't have this problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1906138/+subscriptions


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

[Touch-packages] [Bug 1906600] Re: WiFi disconnects continually (goes "down" in NetworkManager)

[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 network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1906600

Title:
  WiFi disconnects continually (goes "down" in NetworkManager)

Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Invalid

Bug description:
  Hello everybody and thank you in advance for your help.  After a
  recent update, my machine rebooted and appeared to be fine, but after
  a short time the WiFi dropped and the NetworkManager applet shows that
  the interface is down.  I am also getting prompted for a password
  (which was previously saved) and when I click on connect it will
  establish the connection for a short time, but then goes down again.
  In some cases this is immediate in others, I will be online for up to
  approximately 15 minutes before it goes down again.  I have tried
  restarting NetworkManager, but I get the same results (short time up,
  then down).  I tried to review log data, but I am not a linux expert
  and so I'm not sure that I am looking at the right log, nor do I know
  exactly what to look for.  Here are some lines from around the time of
  the disconnect and the restarting of NetworkManager:

   '
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3945] device (wlo1): Activation: successful, device activated.
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8909] device (wlo1): supplicant interface state: completed -> 
authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: 
completed -> authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9011] device (wlo1): supplicant interface state: authenticating -> 
associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: 
authenticating -> associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (wlo1): supplicant interface state: associating -> 
4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: 
associating -> 4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected 
(reason -1)
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> 
disconnected
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9318] device (wlo1): Activation: (wifi) disconnected during 
association, asking for new key
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 
'supplicant-disconnect', sys-iface-state: 'managed')
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9527] dhcp4 (wlo1): state changed bound -> done
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9544] manager: NetworkManager state is now CONNECTING
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 
4-way handshake -> disconnected
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   
[1606875349.4819] device (wlo1): supplicant interface state: disconnected -> 
scanning
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   
[1606875349.4820] device (p2p-dev-wlo1): supplicant management interface state: 
disconnected -> scanning
  Dec 01 21:15:49 bryan-HP-Notebook 

[Touch-packages] [Bug 1942694] Re: [21.04] Uncooperative WiFi manager on TTY7 for proper end user integration

[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 network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1942694

Title:
  [21.04] Uncooperative WiFi manager on TTY7 for proper end user
  integration

Status in network-manager package in Ubuntu:
  New

Bug description:
  Desc.:
  Using 21.04-latest on a Dell XPS 13" laptop and working on TTY7, the wifi 
manager becomes uncooperative after, it seems, it gets tied up to 2 wifi 
profiles.

  Recreation steps:
  1. Install 21.04-latest + full patch it using your home LAN WiFi AP;
  2. Login newly installed system + test Internet = it works fine;
  3. Take same laptop and go to a hotel(for example): manually create a new 
profile for the new WiFi network from TTY7, login "hotel" wifi network profile 
+ test Internet = it works fine;
  4. Physically move back to where your "home" LAN WiFi profile is and boot 
system:

  Problem now happens::
  1. Internet doesn't work off WiFi;
  2. Click on the "Wi-Fi Network" icon at the top hand right side of the screen 
-> "no network devices available";
  3. Select "Edit connections" -> there will be your 2 profiles there: "home" 
and "hotel", delete "hotel" -> OK;
  4. "no network devices available" still shows under "Wi-Fi Network" at the 
top.
  MY USER EXPECTATIONS: Get a new list of close by AP and/or automatically 
reconnect to "profile 1: home".
  NOTA: Both profiles are set to priority 0 and also all set to "all uses may 
connect to this network". Could this be the problem?

  Solution:
  Reboot system.
  After reboot. TTY7 will have defaulted back to the "home" WiFi profile and 
Internet will work at the first user attempt.

  xo

  PS: I have been having this problem from way before hirsute.

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


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

[Touch-packages] [Bug 1920813] Re: /etc/pam.d/lightdm and /etc/pam.d/lightdm-autologin should have uncommented "session required pam_loginuid.so" for compatibility with user applications

[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 lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1920813

Title:
  /etc/pam.d/lightdm and /etc/pam.d/lightdm-autologin should have
  uncommented "session requiredpam_loginuid.so" for
  compatibility with user applications

Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Install Ubuntu MATE 21.04
  2. Launch MATE Terminal
  3. Execute `cat /proc/self/loginuid`

  Expected results:
  * above command returned 1000

  Actual results:
  * above command returned 4294967295

  
  Remediation:
  * edit /etc/pam.d/lightdm and /etc/pam.d/lightdm-autologin to uncomment

  session requiredpam_loginuid.so

  for compatibility with user applications.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: lightdm 1.30.0-0ubuntu3.1
  ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0
  Uname: Linux 5.11.0-11-generic x86_64
  ApportVersion: 2.20.11-0ubuntu60
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Mon Mar 22 22:41:05 2021
  InstallationDate: Installed on 2021-03-21 (1 days ago)
  InstallationMedia: Ubuntu-MATE 21.04 "Hirsute Hippo" - Alpha amd64 (20210321)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1921655] Re: lightdm-guest-session ICEauthority error

[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 lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1921655

Title:
  lightdm-guest-session ICEauthority error

Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Focal:
  Fix Released
Status in lightdm source package in Groovy:
  Fix Released
Status in lightdm source package in Hirsute:
  Fix Released

Bug description:
  [Impact]

  If you enable the guest session feature on e.g. Ubuntu MATE, you are
  met by an error message when trying to enter a guest session:

  "Could not update file ICEauthority file /run/user/XXX/ICEauthority"

  Even if it's not always a fatal error (the login may succeed after a
  few minutes), the user experience is really bad, and you are inclined
  to conclude that you are completely blocked from using the feature.

  The proposed fix adds a rule to the lightdm-guest-session AppArmor
  profile and prevents the error from happening.

  [Test Plan]

  On an updated Ubuntu MATE installation:

  * Enable guest session

sudo sh -c 'printf "[Seat:*]\nallow-guest=true\n"
  >/etc/lightdm/lightdm.conf.d/50-enable-guest.conf'

  * Install lightdm from {focal,groovy}-proposed

  * Reboot

  You should now be able to enter a guest session without being stopped
  by the ICEauthority error.

  [Where problems could occur]

  This one-liner is a harmless change.

  The guest session is run in an unconfined mode since Ubuntu 16.10.
  That's why the feature is disabled by default.

  So if the additional rule would be wrong somehow (which I have no
  reason to believe), it wouldn't break the AppArmor security layer for
  the simple reason that it's already broken to begin with.

  [Original description]

  Hello I ran into trouble to start the lightdm-guest-session in linux
  mint (cinnamon).

  ## How to reproduce:
   - boot linux mint (20.02) or ubuntu mate (20.04) I haven't tested other 
distros but I think others are also affected.
   - enable guest user session
   - try to login as guest user
  ## Error logs:
  ### Error Message:
  ` Could not update file ICEauthority file /run/user/XXX/ICEauthority`
  ### aa-notify:
  ```
  Profile: /usr/lib/lightdm/lightdm-guest-session
  Operation: open
  Name: /proc/8125/uid_map
  Denied: w
  Logfile: /var/log/kern.log

  Profile: /usr/lib/lightdm/lightdm-guest-session
  Operation: open
  Name: /proc/8125/setgroups
  Denied: w
  Logfile: /var/log/kern.log

  Profile: /usr/lib/lightdm/lightdm-guest-session
  Operation: open
  Name: /proc/8125/gid_map
  Denied: w
  Logfile: /var/log/kern.log

  Profile: /usr/lib/lightdm/lightdm-guest-session
  Operation: open
  Name: /proc/8624/fd/
  Denied: r
  Logfile: /var/log/kern.log
  ```
  ### dmesg:
  ```
  [  218.831289] audit: type=1400 audit(1616864450.287:76): apparmor="DENIED" 
operation="sendmsg" profile="/usr/lib/lightdm/lightdm-guest-session" 
name="/run/systemd/journal/dev-log" pid=3916 comm="cinnamon-sessio" 
requested_mask="w" denied_mask="w" fsuid=999 ouid=0
  [ 1157.263045] audit: type=1400 audit(1616865388.720:1084): apparmor="DENIED" 
operation="open" profile="/usr/lib/lightdm/lightdm-guest-session" 
name="/proc/9899/fd/" pid=9899 comm="gpg-agent" requested_mask="r" 
denied_mask="r" fsuid=999  #ouid=0
  [ 1157.899223] audit: type=1400 audit(1616865389.356:1085): apparmor="DENIED" 
operation="open" profile="/usr/lib/lightdm/lightdm-guest-session" 
name="/proc/1/cgroup" pid=9840 comm="cinnamon-sessio" requested_mask="r" 
denied_mask="r" fsuid=999 ouid=0
  [ 1157.899445] audit: type=1400 audit(1616865389.360:1086): apparmor="DENIED" 
operation="sendmsg" profile="/usr/lib/lightdm/lightdm-guest-session" 
name="/run/systemd/journal/dev-log" pid=9840 comm="cinnamon-sessio" 
requested_mask="w" denied_mask="w" fsuid=999 ouid=0
  [ 1157.903410] audit: type=1400 audit(1616865389.364:1087): apparmor="DENIED" 
operation="link" profile="/usr/lib/lightdm/lightdm-guest-session" 
name="/run/user/999/ICEauthority-l" pid=9840 comm="cinnamon-sessio" 
requested_mask="l" denied_mask="l" fsuid=999 ouid=999 
target="/run/user/999/ICEauthority-c"
  ```
  ## Solutions:
  ### bad but common work around
  Solutions I found in different forums were to move lightdm-guest-session into 
complain mode like this:
  `aa-complain /usr/lib/lightdm/lightdm-guest-session`
  ### maybe better sollution:
  My fix would be to add this to `/etc/apparmor.d/lightdm-guest-session`:
  ```
  ...
  /usr/lib/lightdm/lightdm-guest-session {
  ...
    owner /run/user/[0-9]*/ICEauthority-? l,`
  ...
  }
  ```
  I honestly have no clue about apparmor and I'm unsure where to post this but 
I hope this maybe helps some other people in the future.

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


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

[Touch-packages] [Bug 1894356] Re: could not acquire name on session bus by simultaneous login by XDMCP and keyboard

[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 lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1894356

Title:
  could not acquire name on session bus by simultaneous login by XDMCP
  and keyboard

Status in Light Display Manager:
  New
Status in lightdm package in Ubuntu:
  New
Status in lightdm package in Debian:
  Confirmed

Bug description:
  This symptom is observed with Ubuntu Mate 20.04.

  1. Create /etc/lightdm/lightdm.conf.d/10-xdmcp.conf as

  [XDMCPServer]
  enabled=true

  and restart lightdm.

  2. Login as a normal user from keyboard.

  3. Login as the same user as 2 from XDMCP gives
  "Could not acquire name on session bus"
  and I cannot login from XDMCP.
  Without Step 2, XDMCP login succeeds.

  The same symptom is reported at
  https://github.com/neutrinolabs/xrdp/issues/1559#issuecomment-623977001
  which recommends removal of "dbus-user-session" Ubuntu package.

  I worked around the above issue by putting
  "unset DBUS_SESSION_BUS_ADDRESS"
  in /etc/X11/Xsession.d/

  The same issue is also reported at
  https://bugs.launchpad.net/ubuntu-mate/+bug/1769353

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


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

[Touch-packages] [Bug 1898771] Re: suspend does not lock screen Fresh Ubuntu Mate 20.04.1

[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 lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1898771

Title:
  suspend does not lock screen Fresh Ubuntu Mate 20.04.1

Status in lightdm package in Ubuntu:
  New

Bug description:
  When suspending my freshly installed 20.04.1 system I noticed that on waking 
a password is not required. lightdm does not have locking enabled on suspend. A 
workaround I found from pszafer
   on archlinux blog. 

  Quoted below:

  
  create lockscreen.sh file somewhere in your home directory with:

  #!/bin/sh
  XDG_SEAT_PATH="/org/freedesktop/DisplayManager/Seat0" dm-tool lock
  - I've prefer just for sure creating dmlock.service file in home dir and 
create symlink to /etc/systemd/system.
  File has to be in /etc/systemd/system/dmlock.service

  [Unit]
  Description=DM Lock before sleep
  Before=sleep.target

  [Service]
  ExecStart=/home/user/dir/lockscreen.sh

  [Install]
  WantedBy=sleep.target
  For your needs, you probably need hibernate.target.

  Next run following commands:

  systemctl daemon-reload
  systemctl enable dmlock.service
  Just for sure it is working you could run:

  systemctl list-unit-files
  systemctl start dmlock.service
  Hope it helps you a little

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


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

[Touch-packages] [Bug 1888125] Re: refreshing cache stuck in ubuntu mate 20.04

[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 software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1888125

Title:
  refreshing cache stuck in ubuntu mate 20.04

Status in software-properties package in Ubuntu:
  Expired

Bug description:
  i have a very annoying bug which is refreshing cache is just not
  closing only if i rebooted the system!

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


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

[Touch-packages] [Bug 1844426] Re: Impossible to set up Livepatch on Ubuntu MATE

[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 software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1844426

Title:
  Impossible to set up Livepatch on Ubuntu MATE

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  In Ubuntu MATEE 18.04, in the Software Properties window (available
  from Software Boutique > Preferences > Show Software Sources > Manage
  Repositories, among other places), there is a Livepatch tab. This tab
  says "To use Livepatch, you need to sign in" and provides a "Sign
  In..." button.

  This button launches an empty version of gnome-control-center with no
  icons in it.

  If one is technically adept, it is possible to do what (I think) that
  button is trying to do by launching g-c-c directly in a terminal and
  overriding the desktop, thus:

  env XDG_CURRENT_DESKTOP=GNOME gnome-control-center online-accounts

  This online accounts window permits attempting to add an Ubuntu One
  account. However, when one tries, a window pops up with a place to add
  one's Ubuntu One username and password, but the window has no Submit
  button; there is no way to actually initiate sign in.

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


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

[Touch-packages] [Bug 1660121] Re: LightDM can't use the user background on Mate

[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 lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1660121

Title:
  LightDM can't use the user background on Mate

Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  Using Ubuntu Mate 16.10 (the issue appears too on 16.04 and 17.04
  alpha 2).

  On Mate, the LightDM Gtk Greeter can't use the user background. It
  works fine on other DEs like Xfce.

  From what I understand, LightDM and/or the Gkt greeter (not sure which
  one handles the background) gets the background path from Gsettings,
  so I assume it can't find the one from Mate, which stores it in
  "org.mate.background picture-filename".

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


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

[Touch-packages] [Bug 1932980] Re: window title in mate terminal not change after I logout from ssh

[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 openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1932980

Title:
  window title in mate terminal not change after I logout from ssh

Status in mate-terminal package in Ubuntu:
  New
Status in openssh package in Ubuntu:
  Invalid

Bug description:
  I use Ubuntu Mate 20.04. I always update my system. When, I open mate
  terminal and login into my server via ssh, the window title is change
  to my server @. But, its not change after I
  logout. In this report I attach a proof. Thanks.

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


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

[Touch-packages] [Bug 1937083] Re: [21.04] Funky new printer (Netowkr printer autofind)

[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 cups in Ubuntu.
https://bugs.launchpad.net/bugs/1937083

Title:
  [21.04] Funky new printer (Netowkr printer autofind)

Status in cups package in Ubuntu:
  New

Bug description:
  Using 21.04-latest on my main desktop, I am using a Xerox Versalink
  C405 via IPv4 and it always worked pretty good.

  Boring pre-ambule:
  I have been running this system for at least 90+ days and yesterday I had the 
black cartridge being switched for a new one and ever since it doesn't work. 
(But it still works from a windoze machine).

  Situation:
  After being unable to print from Linux my first reaction was to reinstall the 
printer. I have therefore went under MATE menu -> printers -> add -> Network 
Printer -> Find Network printer -> 

  Question #1: is it me or in previous UM versions after clicking on
  "finder network printer" after a couple of seconds it automatically
  found and configured it? Actually, when installing 21.04 it had
  automatically found and configured my Xerox printer..

  Question #2: Since nothing is auto-discovered after 2+ minutes of
  waiting in the New printer wizard (Find network printer), I have
  manually forced the printer's IP into the Host text field and then
  pressed on FIND.

  And this is the reason why I am opening this ticket. See the bottom
  picture because I do not think this is normal

  PS: The finality is that I am UNABLE to readd this printer. (But again
  it was automatically installed+configured at OS installation)

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


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

[Touch-packages] [Bug 1942797] Re: 21.04 - Printer uncooperative (And incohesive) behavior after PWR ON+OFF+ON

[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 cups in Ubuntu.
https://bugs.launchpad.net/bugs/1942797

Title:
  21.04 - Printer uncooperative (And incohesive) behavior after PWR
  ON+OFF+ON

Status in cups package in Ubuntu:
  New

Bug description:
  On a clone desktop running 21.04-latest which has the following LAN
  printer connected to it:

  $ lpstat -p130 ↵
  printer _xeroxofficetq1_ is idle.  enabled since Mon 06 Sep 2021 01:33:46 PM
  printer C405 is idle.  enabled since Mon 06 Sep 2021 01:33:46 PM
  printer Xerox-CommonXCPT is idle.  enabled since Wed 21 Jul 2021 09:58:10 AM
  $

  If/when my system is up and I power off the printer, leave it off for
  a few hours, replug the printer back, wait for it to boot and then
  print using that same system's firefox, it will not work.

  But if I open Libre Office Writer and print: then it shall print.

  Immediately after, going back to the firefox window and re-printing
  what has originally failed now prints too!

  Here is what /var/log/cups/ had to say (This happened around 5 minutes
  ago):

  $ cat access_log
  localhost - - [06/Sep/2021:00:00:01 -0400] "POST / HTTP/1.1" 200 349 
Create-Printer-Subscriptions successful-ok
  localhost - - [06/Sep/2021:00:00:01 -0400] "POST / HTTP/1.1" 200 176 
Create-Printer-Subscriptions successful-ok
  localhost - - [06/Sep/2021:10:22:53 -0400] "POST / HTTP/1.1" 401 186 
Renew-Subscription successful-ok
  localhost - dd [06/Sep/2021:10:22:53 -0400] "POST / HTTP/1.1" 200 186 
Renew-Subscription successful-ok
  localhost - - [06/Sep/2021:13:29:16 -0400] "POST /printers/C405 HTTP/1.1" 200 
405871 Print-Job successful-ok
  localhost - - [06/Sep/2021:13:29:19 -0400] "POST /printers/_xeroxofficetq1_ 
HTTP/1.1" 200 442 Create-Job successful-ok
  localhost - - [06/Sep/2021:13:29:19 -0400] "POST /printers/_xeroxofficetq1_ 
HTTP/1.1" 200 466895 Send-Document successful-ok
  localhost - - [06/Sep/2021:13:31:37 -0400] "POST /printers/C405 HTTP/1.1" 200 
405871 Print-Job successful-ok
  localhost - - [06/Sep/2021:13:31:40 -0400] "POST /printers/_xeroxofficetq1_ 
HTTP/1.1" 200 442 Create-Job successful-ok
  localhost - - [06/Sep/2021:13:31:40 -0400] "POST /printers/_xeroxofficetq1_ 
HTTP/1.1" 200 466823 Send-Document successful-ok
  localhost - - [06/Sep/2021:13:33:19 -0400] "POST /printers/C405 HTTP/1.1" 200 
190 Create-Job successful-ok
  localhost - - [06/Sep/2021:13:33:19 -0400] "POST /printers/C405 HTTP/1.1" 200 
1480 Send-Document successful-ok
  localhost - - [06/Sep/2021:13:33:22 -0400] "POST /printers/_xeroxofficetq1_ 
HTTP/1.1" 200 396 Create-Job successful-ok
  localhost - - [06/Sep/2021:13:33:22 -0400] "POST /printers/_xeroxofficetq1_ 
HTTP/1.1" 200 17334 Send-Document successful-ok
  localhost - - [06/Sep/2021:13:33:43 -0400] "POST /printers/C405 HTTP/1.1" 200 
479195 Print-Job successful-ok
  localhost - - [06/Sep/2021:13:33:46 -0400] "POST /printers/_xeroxofficetq1_ 
HTTP/1.1" 200 442 Create-Job successful-ok
  localhost - - [06/Sep/2021:13:33:46 -0400] "POST /printers/_xeroxofficetq1_ 
HTTP/1.1" 200 468503 Send-Document successful-ok
  $ cat page_log
  C405 dd 1115 [06/Sep/2021:13:29:19 -0400] total 0 - localhost Centre de 
retours en ligne na_letter_8.5x11in_borderless -
  _xeroxofficetq1_ lp 1116 [06/Sep/2021:13:29:38 -0400] total 0 - localhost 
PrtDrv-Rl0gMg - -
  C405 dd 1117 [06/Sep/2021:13:31:40 -0400] total 0 - localhost Centre de 
retours en ligne na_letter_8.5x11in_borderless -
  _xeroxofficetq1_ lp 1118 [06/Sep/2021:13:31:43 -0400] total 0 - localhost 
PrtDrv-Jtjdjo - -
  C405 dd 1119 [06/Sep/2021:13:33:22 -0400] total 0 - localhost Untitled 1 - -
  _xeroxofficetq1_ lp 1120 [06/Sep/2021:13:33:22 -0400] total 0 - localhost 
PrtDrv-RwY6Hm - -
  C405 dd 1121 [06/Sep/2021:13:33:46 -0400] total 0 - localhost Centre de 
retours en ligne na_letter_8.5x11in_borderless -
  _xeroxofficetq1_ lp 1122 [06/Sep/2021:13:33:46 -0400] total 0 - localhost 
PrtDrv-sH8aT0 - -
  $ date
  Mon 06 Sep 2021 01:38:54 PM EDT
  $

  Rewinding back to the previous LOG, THIS is the entry that never went through 
and gave my printer an error:
  _xeroxofficetq1_ lp 1116 [06/Sep/2021:13:29:38 -0400] total 0 - localhost 
PrtDrv-Rl0gMg - -
  C405 dd 1117 [06/Sep/2021:13:31:40 -0400] total 0 - localhost Centre de 
retours en ligne na_letter_8.5x11in_borderless -

  While this is the blank print test I did off Writer which worked:
  _xeroxofficetq1_ lp 1118 [06/Sep/2021:13:31:43 -0400] total 0 - localhost 
PrtDrv-Jtjdjo - -
  C405 dd 1119 [06/Sep/2021:13:33:22 -0400] total 0 - localhost Untitled 1 - -

  While finally having retried printing the original document and... it worked!
  _xeroxofficetq1_ lp 1120 [06/Sep/2021:13:33:22 -0400] total 0 - localhost 
PrtDrv-RwY6Hm - -
  C405 dd 1121 [06/Sep/2021:13:33:46 -0400] total 0 - localhost Centre de 
retours en ligne 

[Touch-packages] [Bug 1943813] Re: Problem with bluetooth keyboard: not usable in MATE

[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 bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1943813

Title:
  Problem with bluetooth keyboard: not usable in MATE

Status in blueman package in Ubuntu:
  New
Status in bluez package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  I have a bluetooth keyboard that I use regularly with other devices. The 
keyboard is Jelly Comb Case with Italian Keyboard for Samsung Galaxy Tab S6 
Lite 10.4 ", Removable Backlit Keyboard in 7 Colors, Italian QWERTY for Sam If 
I try to use it with Ubuntu it only works with the LIVE version. When I install 
Ubuntu it stops working, after updates.
  I have tried with various Ubuntu Mate and also the impish version of Ubuntu 
Mate but, using the same notebook, the computer cannot use it (LIVE yes, 
installed no).

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


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

[Touch-packages] [Bug 1618044] Re: no additional driver icon in most themes

[Martin Wimpress ]

** Changed in: mate-icon-theme (Ubuntu)
   Status: New => Won't Fix

** Changed in: mate-icon-theme (Ubuntu)
   Importance: Undecided => Low

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

Title:
  no additional driver icon in most themes

Status in gnome-icon-theme package in Ubuntu:
  New
Status in mate-icon-theme package in Ubuntu:
  Won't Fix
Status in numix-icon-theme package in Ubuntu:
  Fix Released

Bug description:
  Ubuntu Mate 16.10 beta 1

  In all themes except ambiant-mate and radiant-mate, the 'additional
  driver' icon is missing in the menu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-icon-theme/+bug/1618044/+subscriptions


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

[Touch-packages] [Bug 1908168] Re: Multimedia keys rendered useless if changing sound hardware while playing video

[Martin Wimpress ]

** No longer affects: ubuntu-mate

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

** Changed in: mate-settings-daemon (Ubuntu)
   Status: New => Invalid

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

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

Title:
  Multimedia keys rendered useless if changing sound hardware while
  playing video

Status in mate-media package in Ubuntu:
  Invalid
Status in mate-settings-daemon package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  While on a system that has (amonsgt several other) an analog and hdmi
  hardware sound output option available, if I play/pause(*) a video in
  Firefox and then I change the sound hardware output, the volume
  control buttons on my keyboard stop responding.

  Using 20.04.1-latest.

  (*)=case #2: change the sound hardware profile while the video is
  playing, don't pause it.

  <3

  PS: Those multiple audio hardware profiles are overall VERY
  annoying/intrusive from a user perspective...

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


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

[Martin Wimpress ]

Fixed via mate-session-manager 1.22

** No longer affects: ubuntu-mate

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

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

Title:
  User processes/sessions lingering after logoff

Status in mate-session-manager package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Invalid

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/+source/mate-session-manager/+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 1914311] Re: Random sound and volume outputs when multiple audio hardware is enabled

[Martin Wimpress ]

** No longer affects: ubuntu-mate

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

** Changed in: mate-control-center (Ubuntu)
   Status: New => Invalid

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

Title:
  Random sound and volume outputs when multiple audio hardware is
  enabled

Status in mate-control-center package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  This is an intermittant problem that I have been having:

  When using a laptop with an analog soundcard that is not plugged but
  has a hdmi cable plugged into that same laptop's hdmi port, it
  sometimes(once every 5 times maybe?) happen that MATE remembers to
  default to hdmi output audio hardware as it was lastly used at last
  session shutdown. The rest of the time, MATE defaults back to using
  the analog audio output as default hardware.

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


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

[Touch-packages] [Bug 1885474] Re: 1366x768 screen resolution broken, all other resolutions OK

[Martin Wimpress ]

** No longer affects: ubuntu-mate

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

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

Title:
  1366x768 screen resolution broken, all other resolutions OK

Status in libdrm package in Ubuntu:
  Confirmed
Status in mate-control-center package in Ubuntu:
  Invalid
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  After upgrade from Ubuntu Mate 19.10 to Ubuntu Mate 20.04 i cannot use
  a resolution of 1366x768. Screenshot attached. I am using an Asus
  vivoBook laptop with Amd Ryzen 3 and a Radeon Vega Graphics AMD.

  I found someone in reddit reporting the same problem:
  
https://www.reddit.com/r/UbuntuMATE/comments/ggq8g5/problem_with_resolution_1366x768_with_ubuntu_mate/

  All other screen resolutions OK.

  
  Many thanks

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


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

[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 openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1815318

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

Status in MATE Desktop:
  New
Status in caja package in Ubuntu:
  Confirmed
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/mate-desktop/+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 269441] Re: Trash always full

[Martin Wimpress ]

Caja did not exist in 2008.

** No longer affects: ubuntu-mate

** Changed in: caja (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  Trash always full

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

Bug description:
  I've seen other users having problems with that the trash appears
  empty even though it isn't. I have the opposite problem: my trash icon
  on the desktop always appears full, even if empty.

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


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

[Touch-packages] [Bug 1873750] Re: Custom Application Launcher with Application in Terminal enabled should use user-specified terminal emulator

[Martin Wimpress ]

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

** Changed in: ubuntu-mate-settings (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 glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1873750

Title:
  Custom Application Launcher with Application in Terminal enabled
  should use user-specified terminal emulator

Status in brisk-menu package in Ubuntu:
  Invalid
Status in classicmenu-indicator package in Ubuntu:
  Invalid
Status in glib2.0 package in Ubuntu:
  Confirmed
Status in mate-desktop-environment package in Ubuntu:
  Fix Committed
Status in mate-menu package in Ubuntu:
  Invalid
Status in mate-menus package in Ubuntu:
  Invalid
Status in mate-panel package in Ubuntu:
  Invalid
Status in mate-settings-daemon package in Ubuntu:
  Invalid
Status in ubuntu-mate-settings package in Ubuntu:
  Fix Committed
Status in vala-panel-appmenu package in Ubuntu:
  Invalid

Bug description:
  Steps to reproduce:
  1. Install Ubuntu MATE 20.04 LTS
  2. Install non-default terminal - Tilix, by `sudo apt-get install tilix`
  3. Install terminal-based application - Midnight Commander, by `sudo apt-get 
install mc`
  3. Set Tilix as default terminal in `mate-default-applications-properties` or 
programmatically:

    gsettings set org.mate.applications-terminal exec "'tilix'"

  4. Set Tilix as alternative for x-terminal-emulator by update-
  alternatives:

    update-alternatives --set x-terminal-emulator /usr/bin/tilix.wrapper
    sudo update-alternatives --set x-terminal-emulator 
/usr/bin/tilix.wrapper

  5. Reboot
  6. Add Custom Application Launcher to the MATE Panel:

    Type: Application in Terminal
    Name: mc
    Command: mc

  7. Click the icon of just created Custom Application Launcher

  Expected results:

  * Midnight Commander is opened in the user-defined terminal - in Tilix

  Actual results:

  * Midnight Commander is default terminal - in MATE Terminal

  Notes:
  * This also happens with desktop-files installed by Midnight Commander, it 
opens in MATE Terminal when called from Brisk menu, Classic menu, Compact Menu, 
Dock, + menu, Advanced Mate Menu (`mate-menu` package)
  * What is interesting, the + respects user preferences and uses Tilix
  * Also ++ opens Tilix as expected.

  ---

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: mate-panel 1.24.0-2
  ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30
  Uname: Linux 5.4.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Mon Apr 20 10:48:51 2020
  InstallationDate: Installed on 2020-04-19 (0 days ago)
  InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Beta amd64 (20200419)
  SourcePackage: mate-panel
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1873750] Re: Custom Application Launcher with Application in Terminal enabled should use user-specified terminal emulator

[Martin Wimpress ]

** Changed in: ubuntu-mate-settings (Ubuntu)
   Status: Triaged => In Progress

** Changed in: mate-desktop-environment (Ubuntu)
   Status: Triaged => In Progress

** Changed in: mate-desktop-environment (Ubuntu)
   Importance: Undecided => Medium

** Changed in: mate-desktop-environment (Ubuntu)
 Assignee: (unassigned) => Martin Wimpress  (flexiondotorg)

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

** Changed in: ubuntu-mate-settings (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 glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1873750

Title:
  Custom Application Launcher with Application in Terminal enabled
  should use user-specified terminal emulator

Status in brisk-menu package in Ubuntu:
  Invalid
Status in classicmenu-indicator package in Ubuntu:
  Invalid
Status in glib2.0 package in Ubuntu:
  Confirmed
Status in mate-desktop-environment package in Ubuntu:
  In Progress
Status in mate-menu package in Ubuntu:
  Invalid
Status in mate-menus package in Ubuntu:
  Invalid
Status in mate-panel package in Ubuntu:
  Invalid
Status in mate-settings-daemon package in Ubuntu:
  Invalid
Status in ubuntu-mate-settings package in Ubuntu:
  In Progress
Status in vala-panel-appmenu package in Ubuntu:
  Invalid

Bug description:
  Steps to reproduce:
  1. Install Ubuntu MATE 20.04 LTS
  2. Install non-default terminal - Tilix, by `sudo apt-get install tilix`
  3. Install terminal-based application - Midnight Commander, by `sudo apt-get 
install mc`
  3. Set Tilix as default terminal in `mate-default-applications-properties` or 
programmatically:

    gsettings set org.mate.applications-terminal exec "'tilix'"

  4. Set Tilix as alternative for x-terminal-emulator by update-
  alternatives:

    update-alternatives --set x-terminal-emulator /usr/bin/tilix.wrapper
    sudo update-alternatives --set x-terminal-emulator 
/usr/bin/tilix.wrapper

  5. Reboot
  6. Add Custom Application Launcher to the MATE Panel:

    Type: Application in Terminal
    Name: mc
    Command: mc

  7. Click the icon of just created Custom Application Launcher

  Expected results:

  * Midnight Commander is opened in the user-defined terminal - in Tilix

  Actual results:

  * Midnight Commander is default terminal - in MATE Terminal

  Notes:
  * This also happens with desktop-files installed by Midnight Commander, it 
opens in MATE Terminal when called from Brisk menu, Classic menu, Compact Menu, 
Dock, + menu, Advanced Mate Menu (`mate-menu` package)
  * What is interesting, the + respects user preferences and uses Tilix
  * Also ++ opens Tilix as expected.

  ---

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: mate-panel 1.24.0-2
  ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30
  Uname: Linux 5.4.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Mon Apr 20 10:48:51 2020
  InstallationDate: Installed on 2020-04-19 (0 days ago)
  InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Beta amd64 (20200419)
  SourcePackage: mate-panel
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1873750] Re: Custom Application Launcher with Application in Terminal enabled should use user-specified terminal emulator

[Martin Wimpress ]

glib doesn't support `x-terminal-emulator` so the first found supported
terminal emulator (which will be mate-terminal in Ubuntu MATE) will be
used, regardless of what preferred applications or alternatives have
been configured.

This is why panels/launchers will favour mate-terminal in Ubuntu MATE.

** Changed in: mate-desktop-environment (Ubuntu)
   Status: Confirmed => Triaged

** Changed in: ubuntu-mate-settings (Ubuntu)
   Status: Confirmed => Triaged

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

Title:
  Custom Application Launcher with Application in Terminal enabled
  should use user-specified terminal emulator

Status in brisk-menu package in Ubuntu:
  Invalid
Status in classicmenu-indicator package in Ubuntu:
  Invalid
Status in glib2.0 package in Ubuntu:
  Confirmed
Status in mate-desktop-environment package in Ubuntu:
  Triaged
Status in mate-menu package in Ubuntu:
  Invalid
Status in mate-menus package in Ubuntu:
  Invalid
Status in mate-panel package in Ubuntu:
  Invalid
Status in mate-settings-daemon package in Ubuntu:
  Invalid
Status in ubuntu-mate-settings package in Ubuntu:
  Triaged
Status in vala-panel-appmenu package in Ubuntu:
  Invalid

Bug description:
  Steps to reproduce:
  1. Install Ubuntu MATE 20.04 LTS
  2. Install non-default terminal - Tilix, by `sudo apt-get install tilix`
  3. Install terminal-based application - Midnight Commander, by `sudo apt-get 
install mc`
  3. Set Tilix as default terminal in `mate-default-applications-properties` or 
programmatically:

    gsettings set org.mate.applications-terminal exec "'tilix'"

  4. Set Tilix as alternative for x-terminal-emulator by update-
  alternatives:

    update-alternatives --set x-terminal-emulator /usr/bin/tilix.wrapper
    sudo update-alternatives --set x-terminal-emulator 
/usr/bin/tilix.wrapper

  5. Reboot
  6. Add Custom Application Launcher to the MATE Panel:

    Type: Application in Terminal
    Name: mc
    Command: mc

  7. Click the icon of just created Custom Application Launcher

  Expected results:

  * Midnight Commander is opened in the user-defined terminal - in Tilix

  Actual results:

  * Midnight Commander is default terminal - in MATE Terminal

  Notes:
  * This also happens with desktop-files installed by Midnight Commander, it 
opens in MATE Terminal when called from Brisk menu, Classic menu, Compact Menu, 
Dock, + menu, Advanced Mate Menu (`mate-menu` package)
  * What is interesting, the + respects user preferences and uses Tilix
  * Also ++ opens Tilix as expected.

  ---

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: mate-panel 1.24.0-2
  ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30
  Uname: Linux 5.4.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Mon Apr 20 10:48:51 2020
  InstallationDate: Installed on 2020-04-19 (0 days ago)
  InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Beta amd64 (20200419)
  SourcePackage: mate-panel
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1873750] Re: Custom Application Launcher with Application in Terminal enabled should use user-specified terminal emulator

[Martin Wimpress ]

** Also affects: glib2.0 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Custom Application Launcher with Application in Terminal enabled
  should use user-specified terminal emulator

Status in brisk-menu package in Ubuntu:
  Invalid
Status in classicmenu-indicator package in Ubuntu:
  Invalid
Status in glib2.0 package in Ubuntu:
  Confirmed
Status in mate-desktop-environment package in Ubuntu:
  Triaged
Status in mate-menu package in Ubuntu:
  Invalid
Status in mate-menus package in Ubuntu:
  Invalid
Status in mate-panel package in Ubuntu:
  Invalid
Status in mate-settings-daemon package in Ubuntu:
  Invalid
Status in ubuntu-mate-settings package in Ubuntu:
  Triaged
Status in vala-panel-appmenu package in Ubuntu:
  Invalid

Bug description:
  Steps to reproduce:
  1. Install Ubuntu MATE 20.04 LTS
  2. Install non-default terminal - Tilix, by `sudo apt-get install tilix`
  3. Install terminal-based application - Midnight Commander, by `sudo apt-get 
install mc`
  3. Set Tilix as default terminal in `mate-default-applications-properties` or 
programmatically:

    gsettings set org.mate.applications-terminal exec "'tilix'"

  4. Set Tilix as alternative for x-terminal-emulator by update-
  alternatives:

    update-alternatives --set x-terminal-emulator /usr/bin/tilix.wrapper
    sudo update-alternatives --set x-terminal-emulator 
/usr/bin/tilix.wrapper

  5. Reboot
  6. Add Custom Application Launcher to the MATE Panel:

    Type: Application in Terminal
    Name: mc
    Command: mc

  7. Click the icon of just created Custom Application Launcher

  Expected results:

  * Midnight Commander is opened in the user-defined terminal - in Tilix

  Actual results:

  * Midnight Commander is default terminal - in MATE Terminal

  Notes:
  * This also happens with desktop-files installed by Midnight Commander, it 
opens in MATE Terminal when called from Brisk menu, Classic menu, Compact Menu, 
Dock, + menu, Advanced Mate Menu (`mate-menu` package)
  * What is interesting, the + respects user preferences and uses Tilix
  * Also ++ opens Tilix as expected.

  ---

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: mate-panel 1.24.0-2
  ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30
  Uname: Linux 5.4.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Mon Apr 20 10:48:51 2020
  InstallationDate: Installed on 2020-04-19 (0 days ago)
  InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Beta amd64 (20200419)
  SourcePackage: mate-panel
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1882525] Re: [amdgpu] MATE desktop is corrupted upon login on Ryzen APU

[Martin Wimpress ]

** Changed in: marco (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  [amdgpu] MATE desktop is corrupted upon login on Ryzen APU

Status in marco package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Confirmed

Bug description:
  Today I upgraded from Ubuntu MATE 19.10 to 20.04. After doing so, Ubuntu 
boots normally to the display manager (login screen) as expected. But once I 
log in, everything on the screen is cut up into horizontal slices, with each 
slice offset farther right than the slice above, and squares of random colors 
running diagonally across the screen. I've attached a picture of my monitor 
showing the issue for reference.
  My hardware is a home-built PC with an ASUS Prime B450M motherboard, a Ryzen 
3 2200G APU, and using that APU's integrated graphics.
  In terms of software I'm running Ubuntu 20.04, which I just upgraded to and 
did a software update on. I have Linux 5.4.0-33-generic, X.Org 1.20.8, and Mesa 
20.0.4. Before I upgraded Ubuntu, I was affected by Bug #1880041 but it seems 
fixed in the new kernel. I don't believe they're related but I figure it's 
worth mentioning.
  I tried adding the nomodeset kernel option at boot, and it's an effective 
workaround. Also, I tried booting from an Ubuntu Mate 20.04 live USB to see if 
this was caused by some quirk of my particular software setup, and successfully 
reproduced the bug, proving it wasn't.
  If you'd like me to, I can provide log files, system information, etc. or 
help narrow it down by testing workarounds.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg-core 2:1.20.8-2ubuntu2.1
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompositorRunning: None
  Date: Mon Jun  8 06:41:47 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/xorg/Xorg
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Raven Ridge [Radeon Vega Series / Radeon 
Vega Mobile Series] [1043:876b]
  InstallationDate: Installed on 2019-10-20 (231 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: System manufacturer System Product Name
  ProcEnviron: PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic 
root=UUID=43189257-cc94-4e98-ac1d-e16336dd152e ro quiet splash vt.handoff=7
  SourcePackage: xorg-server
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/13/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2006
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B450M-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2006:bd11/13/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB450M-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


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

[Touch-packages] [Bug 1828725] Re: indicator-datetime does not have color squares for different calendars and dates from contacts (birthdays & anniversaries)

[Martin Wimpress ]

Fixed since ayatana-indicator-datetime 2.1.1-2 in Ubuntu MATE 21.10

** No longer affects: ubuntu-mate

** Changed in: ayatana-indicator-datetime (Ubuntu)
   Status: New => Fix Released

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

Title:
  indicator-datetime does not have color squares for different calendars
  and dates from contacts (birthdays & anniversaries)

Status in Indicator Date and Time:
  New
Status in ayatana-indicator-datetime package in Ubuntu:
  Fix Released
Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Install Ubuntu with `indicator-datetime` and `evolution`
  2. Add event to *Personal* calendar (default color)
  3. Add new calendar and name it for example *Work* (red color)
  4. Create contact with two dates - birthday and anniversary (it is pink color)

  Expected results:
  * `indicator-datetime` show four coloured events as it was in Ubuntu 12.04 
LTS (see screenshot - ubuntu-12-04.png)

  Actual results:
  * `indicator-datetime` show for event without color squares in the left of 
them (see screenshot - ubuntu-19-10.png)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: indicator-datetime 15.10+19.10.20190507-0ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-14.15-generic 5.0.6
  Uname: Linux 5.0.0-14-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sun May 12 14:54:43 2019
  InstallationDate: Installed on 2019-04-28 (13 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan EANIMAL" - Alpha amd64 (20190426)
  SourcePackage: indicator-datetime
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Martin Wimpress ]

Fixed via ayatana-indicator-power 2.1.1-2.

** No longer affects: ubuntu-mate

** Changed in: indicator-power (Ubuntu)
   Status: Confirmed => Invalid

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

** Changed in: ayatana-indicator-power (Ubuntu)
   Status: Confirmed => Fix Released

-- 
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 ayatana-indicator-power package in Ubuntu:
  Fix Released
Status in indicator-power package in Ubuntu:
  Invalid
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/+source/ayatana-indicator-power/+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 1948339] Re: Logon screen can be bypassed using various shortcuts

[Martin Wimpress ]

Sorry for the late reply on this issue. I only saw it a few days ago.
I've spoken with the Arctica greeter developer and we've been working on
a fix.

The issue is this, Arctica Greeter requires a window manager and it
invokes Marco, the window manager from MATE Desktop. Marco handles
keybindings and by default has a number predefined. Ubuntu MATE adds a
few more. This is why you are able to invoke applications bound to
keybindings in Marco from Arctica Greeter.

The proposed solution is to add a patch to Marco so that it can be
invoked with keybindings disabled and then patch Arctica Greeter to
invoke Marco with the argument to disable its keybindings.

I will start preparing patched versions of Marco and Artica Greeter in a
PPA for testing/validation.

** Changed in: arctica-greeter (Ubuntu)
   Status: New => Triaged

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

** Changed in: mate-settings-daemon (Ubuntu)
   Status: New => Invalid

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

** Changed in: marco (Ubuntu)
   Status: New => Triaged

** Changed in: arctica-greeter (Ubuntu)
   Importance: Undecided => Critical

** Changed in: arctica-greeter (Ubuntu)
 Assignee: (unassigned) => Martin Wimpress  (flexiondotorg)

** Changed in: marco (Ubuntu)
   Importance: Undecided => Critical

** Changed in: marco (Ubuntu)
 Assignee: (unassigned) => Martin Wimpress  (flexiondotorg)

** No longer affects: ubuntu-mate

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

Title:
  Logon screen can be bypassed using various shortcuts

Status in arctica-greeter package in Ubuntu:
  Triaged
Status in lightdm package in Ubuntu:
  Invalid
Status in marco package in Ubuntu:
  Triaged
Status in mate-settings-daemon package in Ubuntu:
  Invalid

Bug description:
  Hi,

  my little daughter discovered a logon screen bypass in Ubuntu Mate
  21.10 after hitting the keyboard for a while.

  It turns out that several keyboard shortcuts are allowed while Ubuntu
  Mate is locked (arctica-greeter):

  - Mod4 + S (mate-search-tool)
  - Mod4 + E (Open Caja / File Explorer)
  - CTRL + Shift + Esc (mate-system-monitor)
  - PRNT (Screenshot)

  All of the mentioned shortcuts could be used to spawn a file explorer
  (Caja) or various other binaries as user "lightdm", who owns the logon
  screen.

  Although an interactive terminal like mate-terminal, xterm, lxterm
  etc. could not be opened directly, there are various options to run
  commands as the lightdm user, for example by creating a shell script
  using "caja", and execute it directly using the GUI.

  I've attached Proof-of-Concept GIFs for all shortcuts mentioned above.
  There might be additional shortcuts that could be used to achieve the
  same, however I'm not aware about every shortcut that is configured,
  but I suppose that the root cause is located somewhere in arctica-
  greeter, rather than within every single binary launched by shortcuts.

  The bug was reproduced on a fresh installation of Ubuntu Mate 21.10. I
  haven't tested other versions of Ubuntu Mate yet.

  Please find additional version details below:

  $ apt-cache policy lightdm

  lightdm:
    Installed: 1.30.0-0ubuntu4
    Candidate: 1.30.0-0ubuntu4
    Version table:
   *** 1.30.0-0ubuntu4 500
  500 http://de.archive.ubuntu.com/ubuntu impish/universe amd64 Packages
  100 /var/lib/dpkg/status

  $ apt-cache policy arctica-greeter

  arctica-greeter:
    Installed: 0.99.1.5-2nmu1
    Candidate: 0.99.1.5-2nmu1
    Version table:
   *** 0.99.1.5-2nmu1 500
  500 http://de.archive.ubuntu.com/ubuntu impish/universe amd64 Packages
  100 /var/lib/dpkg/status

  Thanks,
  Basti

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


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

[Touch-packages] [Bug 1884303] Re: LAN printing hell on 20.04 (UPnP VS mDNS? Or maybe IPv4 vs IPv6??)

[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 cups in Ubuntu.
https://bugs.launchpad.net/bugs/1884303

Title:
  LAN printing hell on 20.04 (UPnP VS mDNS? Or maybe IPv4 vs IPv6??)

Status in cups package in Ubuntu:
  New

Bug description:
  Hello,

  I have been experiencing this problem for at least 2 LTS versions I
  believe and it concerns and issue with a LAN printer. I am still not
  quite too sure if it involves a happy mix-up of TCPvsmDNSvsuPnP and|or
  if it's a lpstat VS GUI binary setting and|or ??

  Anyways, when using 20.04 fully patched(and also possibly not) while
  using a LAN printer there seems to be a "duplicated-corrupted entry"
  that ends up somewhat generated in the system.

  For example:
  $ lpstat -p
  printer Samsung_C460_Series_SEC30CDA7A49F15_ now printing 
Samsung_C460_Series_SEC30CDA7A49F15_-12.  enabled since Fri 19 Jun 2020 
01:09:47 PM
  $

  And MATE agrees with that (See attachment "1.jpg")

  But when using Atril (See "2.jpg") or LOWriter (See "3.jpg") (or any
  other binary such as firefox) the story isn't so clear.

  That brought me back to this:
  $ lpstat -p
  lpstat: No destinations added.
  $

  And MATE still agrees with that (See "4.jpg")

  Yet LOWriter (and co) seemed a bit still challenged (See "5.jpg")

  Anyways, time to delete everything and readd. But why are there 2x
  choices? (See "6.jpg")

  Looking carefully at both entries, I believe that one is the TCP
  socket (See "7.jpg") while the 2nd one is via SSDP/UPnP (See "8.jpg").

  But anyways, I always go for the TCP entry and that's done (See
  "9.jpg").

  $ lpstat -p  1 ↵
  printer Samsung-C460 is idle.  enabled since Fri 19 Jun 2020 02:36:42 PM
  $

  And MATE again agrees (See "10.jpg")

  Yaaay! Time to print out that SOB, so let's go back into Atril and print it 
(See "11.jpg")
  Nothing surprising there: the old ghosted/MAC addressed profile still shows.

  But did printing on the newly added via TCP one actually worked? YES!
  This time it did. Why this time? Because in other times it will just
  die in the spoiler and have me started back at the very beginning of
  this ticket.

  Also, a major point of interest is: after having readded the printer,
  notice how lpstat named it, it was "Samsung-C460". Well, if/when I'll
  reboot the system, that simple name will be gone and will have been
  changed to "Samsung-C460-Series-SEC30CDA7A49F15" while still showing
  this "Samsung_C460_Series_SEC30CDA7A49F15_" ghost.

  From the printer's perspective, here is what's opened on it:
  PORT  STATE SERVICE VERSION
  80/tcpopen  httpSamsung SyncThru Web Service
  |_http-favicon: Unknown favicon MD5: 10E320BB701D0D099E175B6C339958F9
  | http-methods: 
  |_  Supported Methods: GET POST
  | http-robots.txt: 1 disallowed entry 
  |_*
  |_http-title: Site doesn't have a title (text/html; charset=utf-8).
  427/tcp   open  svrloc?
  515/tcp   open  printer?
  | fingerprint-strings: 
  |   TerminalServerCookie: 
  |_PortThru lpd: No Jobs on this queue
  631/tcp   open  httpSamsung SyncThru Web Service
  |_http-favicon: Unknown favicon MD5: 10E320BB701D0D099E175B6C339958F9
  | http-methods: 
  |_  Supported Methods: GET POST
  |_http-title: Site doesn't have a title (text/html; charset=utf-8).
  5200/tcp  open  targus-getdata?
  | fingerprint-strings: 
  |   DNSStatusRequestTCP, DNSVersionBindReqTCP, FourOhFourRequest, 
GenericLines, GetRequest, HTTPOptions, Help, Kerberos, LDAPSearchReq, 
LPDString, RPCCheck, RTSPRequest, SMBProgNeg, SSLSessionReq, TLSSessionReq, 
TerminalServerCookie, X11Probe: 
  | HTTP/1.1 405 Method Not Allowed
  | Connection: close
  |_Server: ESWeb/0.5
  9100/tcp  open  jetdirect?
  10001/tcp open  scp-config?

  Here's what /var/log/cups/error_log as to say about all of this:
  E [19/Jun/2020:00:00:00 -0400] Unable to open listen socket for address 
[v1.::1]:631 - Cannot assign requested address.
  E [19/Jun/2020:13:02:02 -0400] [Job 10] File \'\' not found
  E [19/Jun/2020:13:05:58 -0400] Unable to open listen socket for address 
[v1.::1]:631 - Cannot assign requested address.
  E [19/Jun/2020:13:08:09 -0400] [Job 11] No destination host name supplied by 
cups-browsed for printer \"Samsung_C460_Series_SEC30CDA7A49F15_\", is 
cups-browsed running?
  E [19/Jun/2020:13:08:39 -0400] [Job 12] No destination host name supplied by 
cups-browsed for printer \"Samsung_C460_Series_SEC30CDA7A49F15_\", is 
cups-browsed running?
  E [19/Jun/2020:13:09:58 -0400] [Client 2371] Returning IPP 
client-error-not-possible for Cancel-Job (ipp://localhost/jobs/11) from 
localhost.
  E [19/Jun/2020:13:09:58 -0400] [Client 2493] Returning IPP 
client-error-not-possible for Cancel-Job (ipp://localhost/jobs/11) from 
localhost.
  E [19/Jun/2020:13:10:07 -0400] [Job 12] No destination host 

[Touch-packages] [Bug 1884307] Re: no Montréal listed in city?

[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 tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/1884307

Title:
  no Montréal listed in city?

Status in tzdata package in Ubuntu:
  Incomplete

Bug description:
  It was olek @ UMC (https://ubuntu-mate.community/t/20-04-some-very-
  minor-annoyances-for-when-working-in-tty7/22142) whom suggested me to
  bug report this so why not ;)

  Why are the only 2 selectable cities from GMT-5 (Eastern) are: Toronto
  and NYC? There's also this other city called Montréal who hosts a
  whole bunch of different of people in between the two.

  Oh, and did you know that there was also a province and infrastructure
  surrounding this whole city? We better be start using it in 2020!

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


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

[Touch-packages] [Bug 1895369] Re: Network printer goes missing after 1x print when IPv6 is disabled

[Martin Wimpress ]

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

Title:
  Network printer goes missing after 1x print when IPv6 is disabled

Status in cups package in Ubuntu:
  New

Bug description:
  Using 20.04.1-latest and having disabled IPv6 @ /etc/sysctl.conf via
  the following settings:

  net.ipv6.conf.all.disable_ipv6 = 1
  net.ipv6.conf.default.disable_ipv6 = 1
  net.ipv6.conf.lo.disable_ipv6 = 1

  When I open a .TXT using Libre Office Writer and print it, the first
  time it prints well.

  If I then close LOW immediately after, open another .txt and print it
  I get "Could not start printer. Please check your printer
  configuration".

  $ cat /var/log/cups/error_log 
   130 ↵
  E [12/Sep/2020:00:00:01 -0400] Unable to open listen socket for address 
[v1.::1]:631 - Cannot assign requested address.
  E [12/Sep/2020:00:44:29 -0400] [Job 7] File \'\' not found
  E [12/Sep/2020:00:46:05 -0400] Unable to open listen socket for address 
[v1.::1]:631 - Cannot assign requested address.
  E [12/Sep/2020:00:46:05 -0400] [Job 7] File \'\' not found
  W [12/Sep/2020:00:46:05 -0400] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'Samsung_C460_Series_SEC30CDA7A49F15_-Gray..\' already exists
  W [12/Sep/2020:00:46:05 -0400] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'Samsung_C460_Series_SEC30CDA7A49F15_-DeviceN..\' already exists
  E [12/Sep/2020:00:47:25 -0400] Unable to open listen socket for address 
[v1.::1]:631 - Cannot assign requested address.
  E [12/Sep/2020:00:47:25 -0400] [Job 7] File \'\' not found
  W [12/Sep/2020:00:47:28 -0400] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'Samsung_C460_Series_SEC30CDA7A49F15_-Gray..\' already exists
  W [12/Sep/2020:00:47:28 -0400] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'Samsung_C460_Series_SEC30CDA7A49F15_-DeviceN..\' already exists
  $

  Also, the first document that I requested to be printed 1x copy will
  print a 2nd time without being asked.

  The solution is to wait.

  If I then close LOW and wait around 2-3 minutes then reopen that 2nd
  document and print it: it will print immediately and per requested.

  Another thing to mention is everytime I am in LOW and CTRL+P I always
  see the print window pop-up alongside my Samsung printer in it. The
  error/duplicate/refusal to print will happen after having clicked on
  "OK".

  PS1: This of course occurs when using a LAN printer.
  PS2: I did not installed any proprietary samsung binaries. Am instead using 
the default/vanilla network printer install that was done by UMC.
  PS3: This problem has been around since at least 18.04 if not prior.

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


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

[Touch-packages] [Bug 1915776] Re: crash report crashes in 21.04+Mate

[Martin Wimpress ]

** No longer affects: ubuntu-mate

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

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

Title:
  crash report crashes in 21.04+Mate

Status in apport package in Ubuntu:
  New
Status in marco package in Ubuntu:
  Incomplete

Bug description:
  I downloaded an ISO for 21.04 + Mate, (daily build) installed in a 
VirtualBox. Quite happy with it, works well, but every boot it pops up a box of 
'crash report' and 'can I report?' Watching the network traffic, nothing is 
getting reported and the crashes still happen.
  I am looking for somebody I can email the last dozen lines or so of the 
boot-log to.

  My personal email is kneedragon1...@gmail.com. 
  I would be very happy to help.

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


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

[Touch-packages] [Bug 1950410] Re: PS4 DualShock wireless controller connected/disconnected/unusable

[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 bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1950410

Title:
  PS4 DualShock wireless controller connected/disconnected/unusable

Status in blueman package in Ubuntu:
  New
Status in bluez package in Ubuntu:
  New

Bug description:
  Using a laptop running 21.10-latest, using a Sony Wireless Controller
  Model CUH-ZCT2U (The PS4 model), it seems impossible to connect via
  bluetooth to my laptop.

  Even though both hcitool & bluetooth manager are able to see the
  device, bonus mission bluetooth devices can also connect to it, but
  this is fairly short as it automatically disconnects.

  Here is what dmesg had to say about this.

  ```
  [ 2479.109487] sony 0005:054C:09CC.0002: unknown main item tag 0x0
  [ 2479.123654] input: Wireless Controller Touchpad as 
/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:5/0005:054C:09CC.0002/input/input28
  [ 2479.124094] input: Wireless Controller Motion Sensors as 
/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:5/0005:054C:09CC.0002/input/input29
  [ 2479.124676] input: Wireless Controller as 
/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:5/0005:054C:09CC.0002/input/input27
  [ 2479.125046] sony 0005:054C:09CC.0002: input,hidraw1: BLUETOOTH HID v81.00 
Gamepad [Wireless Controller] on 9c:b6:d0:8f:c1:70
  [ 2490.957043] sony 0005:054C:09CC.0003: unknown main item tag 0x0
  [ 2490.971080] input: Wireless Controller Touchpad as 
/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:4/0005:054C:09CC.0003/input/input31
  [ 2490.971525] input: Wireless Controller Motion Sensors as 
/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:4/0005:054C:09CC.0003/input/input32
  [ 2490.972397] input: Wireless Controller as 
/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:4/0005:054C:09CC.0003/input/input30
  [ 2490.973740] sony 0005:054C:09CC.0003: input,hidraw1: BLUETOOTH HID v81.00 
Gamepad [Wireless Controller] on 9c:b6:d0:8f:c1:70
  [ 2498.688287] sony 0005:054C:09CC.0004: unknown main item tag 0x0
  [ 2498.699789] input: Wireless Controller Touchpad as 
/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:5/0005:054C:09CC.0004/input/input34
  [ 2498.700142] input: Wireless Controller Motion Sensors as 
/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:5/0005:054C:09CC.0004/input/input35
  [ 2498.700962] input: Wireless Controller as 
/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:5/0005:054C:09CC.0004/input/input33
  [ 2498.701415] sony 0005:054C:09CC.0004: input,hidraw1: BLUETOOTH HID v81.00 
Gamepad [Wireless Controller] on 9c:b6:d0:8f:c1:70
  [ 2511.533433] sony 0005:054C:09CC.0005: unknown main item tag 0x0
  [ 2511.543132] input: Wireless Controller Touchpad as 
/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:6/0005:054C:09CC.0005/input/input37
  [ 2511.543793] input: Wireless Controller Motion Sensors as 
/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:6/0005:054C:09CC.0005/input/input38
  [ 2511.544577] input: Wireless Controller as 
/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:6/0005:054C:09CC.0005/input/input36
  [ 2511.545359] sony 0005:054C:09CC.0005: input,hidraw1: BLUETOOTH HID v81.00 
Gamepad [Wireless Controller] on 9c:b6:d0:8f:c1:70
  [ 2517.758693] sony 0005:054C:09CC.0006: unknown main item tag 0x0
  [ 2517.766837] input: Wireless Controller Touchpad as 
/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:7/0005:054C:09CC.0006/input/input40
  [ 2517.767834] input: Wireless Controller Motion Sensors as 
/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:7/0005:054C:09CC.0006/input/input41
  [ 2517.768642] input: Wireless Controller as 
/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:7/0005:054C:09CC.0006/input/input39
  [ 2517.769168] sony 0005:054C:09CC.0006: input,hidraw1: BLUETOOTH HID v81.00 
Gamepad [Wireless Controller] on 9c:b6:d0:8f:c1:70
  [ 2522.932282] sony 0005:054C:09CC.0007: unknown main item tag 0x0
  [ 2522.947350] input: Wireless Controller Touchpad as 
/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:8/0005:054C:09CC.0007/input/input43
  [ 2522.947965] input: Wireless Controller Motion Sensors as 
/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:8/0005:054C:09CC.0007/input/input44
  [ 2522.948593] input: Wireless Controller as 
/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:8/0005:054C:09CC.0007/input/input42
  [ 2522.951519] sony 0005:054C:09CC.0007: input,hidraw1: BLUETOOTH HID v81.00 
Gamepad [Wireless Controller] on 9c:b6:d0:8f:c1:70
  ```

  When I plug the same controller via USB it's not only automatically 

[Touch-packages] [Bug 1959473] Re: Evolution: Migrate to People API to retain programmatic access to Google Contacts.

[Martin Wimpress ]

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

** No longer affects: ubuntu-mate

** This bug has been marked a duplicate of bug 1952107
   Google Contacts API Deprecated

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

Title:
  Evolution: Migrate to People API to retain programmatic access to
  Google Contacts.

Status in Evolution:
  Unknown
Status in evolution package in Ubuntu:
  Confirmed
Status in evolution-data-server package in Ubuntu:
  Confirmed

Bug description:
  I'm running Ubuntu MATE 20.04; I stick with LTS for this system.  I
  use Evolution for email and calendar.  Tonight I got this message:

  =
  Failed to connect address book “guy.rouill...@gmail.com : Contacts”

  Invalid request URI or header, or unsupported nonstandard parameter: Contacts 
API is being deprecated. Migrate to People API to retain programmatic access to 
Google Contacts. See 
https://developers.google.com/people/contacts-api-migration.
  ==

  I went to report this on the GNOME bug tracker and found this existing
  issue:

  https://gitlab.gnome.org/GNOME/evolution/-/issues/1655

  That issue was closed with this comment:
  ==
  "Andre Klapper

  Issue found on latest Evolution in Debian 11 (3.38.3-1)

  That version is ancient and not maintained anymore by GNOME
  developers. Feel free to file a bug report in your distribution's
  issue tracker."

  The version in MATE is even older: 3.36.5-0ubuntu1

  So apparently Evolution in MATE is currently not functional.  We need to 
update to a later release.  I will update to the newer LTS of MATE when it is 
released.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2018-10-05 (1212 days ago)
  InstallationMedia: Ubuntu-MATE 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Package: evolution-data-server
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-92.103-generic 5.4.157
  Tags: third-party-packages focal
  Uname: Linux 5.4.0-92-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-17 (622 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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


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

[Touch-packages] [Bug 1926256] Re: Pasted text in the terminal is always highlighted and selected

[Martin Wimpress ]

** Changed in: vte2.91 (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: bash (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  Pasted text in the terminal is always highlighted and selected

Status in bash package in Ubuntu:
  Invalid
Status in gnome-terminal package in Ubuntu:
  Invalid
Status in mate-terminal package in Ubuntu:
  Invalid
Status in readline package in Ubuntu:
  Confirmed
Status in vte2.91 package in Ubuntu:
  Invalid

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 21.04 installed
  2. Launch terminal
  3a. Execute some command, select this command to copy it, then paste command
  3b. Paste some command from clipboard to terminal

  Expected result:
  * pasted command is not highlighted and is not selected

  Actual result:
  * pasted command is selected and highlighted

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: mate-terminal 1.24.1-1
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE
  Date: Tue Apr 27 09:43:56 2021
  InstallationDate: Installed on 2021-04-23 (3 days ago)
  InstallationMedia: Ubuntu-MATE 21.04 "Hirsute Hippo" - Release amd64 
(20210420)
  SourcePackage: mate-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1854383] Re: Extra window decorations are created on windows with client-side decorations.

[Martin Wimpress ]

This issue is caused by `mate-maximus` which is part of the `mate-
netboot` package. `mate-netboot` doesn't get much upstream development
attention so unlikely to fixed in the near future.

Ubuntu MATE provides several resolution-efficient panel layouts, so
removing `mate-netbook` from Ubuntu MATE is the best option for
addressing this issue.

mate-netbook was removed from ubuntu-mate-meta 1.281:

 - https://launchpad.net/ubuntu/+source/ubuntu-mate-meta/1.281

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

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

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

** No longer affects: ubuntu-mate

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

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

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

** Changed in: ubuntu-mate-meta (Ubuntu)
   Status: New => Fix Released

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

Title:
  Extra window decorations are created on windows with client-side
  decorations.

Status in gtk+3.0 package in Ubuntu:
  Invalid
Status in marco package in Ubuntu:
  Invalid
Status in mate-netbook package in Ubuntu:
  New
Status in ubuntu-mate-meta package in Ubuntu:
  Fix Released

Bug description:
  Steps to reproduce after a minimal/full install of Ubuntu MATE:

  1. Start up a Gtk3 application with a header bar (tested with Gnome
  Software) or a browser (such as Firefox) without using a standard
  window title bar that saves the position and size of the window before
  it was closed.

  2. Maximize the application window, then close it without changing the
  window size

  3. Relaunch the application and resize/unmaximize it

  After this, dummy window decorations will be created around the
  window. This issue has been tested on a Dell XPS 9570 and using Gnome
  Boxes 3.34.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1854383/+subscriptions


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

[Touch-packages] [Bug 1854383] Re: Extra window decorations are created on windows with client-side decorations.

[Martin Wimpress ]

The workaround for Ubuntu MATE versions prior to 22.04 is to remove the
`mate-netbook` package. It is Recommended only, so can be safely removed
like so:

killall mate-maximus
sudo apt-get remove mate-netbook

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

Title:
  Extra window decorations are created on windows with client-side
  decorations.

Status in gtk+3.0 package in Ubuntu:
  Invalid
Status in marco package in Ubuntu:
  Invalid
Status in mate-netbook package in Ubuntu:
  New
Status in ubuntu-mate-meta package in Ubuntu:
  Fix Released

Bug description:
  Steps to reproduce after a minimal/full install of Ubuntu MATE:

  1. Start up a Gtk3 application with a header bar (tested with Gnome
  Software) or a browser (such as Firefox) without using a standard
  window title bar that saves the position and size of the window before
  it was closed.

  2. Maximize the application window, then close it without changing the
  window size

  3. Relaunch the application and resize/unmaximize it

  After this, dummy window decorations will be created around the
  window. This issue has been tested on a Dell XPS 9570 and using Gnome
  Boxes 3.34.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1854383/+subscriptions


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

[Touch-packages] [Bug 1926256] Re: Pasted text in the terminal is always highlighted and selected

[Martin Wimpress ]

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

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

Title:
  Pasted text in the terminal is always highlighted and selected

Status in bash package in Ubuntu:
  Confirmed
Status in gnome-terminal package in Ubuntu:
  Invalid
Status in mate-terminal package in Ubuntu:
  Invalid
Status in readline package in Ubuntu:
  Confirmed
Status in vte2.91 package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 21.04 installed
  2. Launch terminal
  3a. Execute some command, select this command to copy it, then paste command
  3b. Paste some command from clipboard to terminal

  Expected result:
  * pasted command is not highlighted and is not selected

  Actual result:
  * pasted command is selected and highlighted

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: mate-terminal 1.24.1-1
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE
  Date: Tue Apr 27 09:43:56 2021
  InstallationDate: Installed on 2021-04-23 (3 days ago)
  InstallationMedia: Ubuntu-MATE 21.04 "Hirsute Hippo" - Release amd64 
(20210420)
  SourcePackage: mate-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1787368] Re: Caja does not show previews of text files on Bionic and newer versions

[Martin Wimpress ]

This functionality was dropped from GTK and while there was some
upstream effort to re-implement this capability no forward progress has
been made in 3 years.

Closing this.

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

** Changed in: caja (Ubuntu)
   Status: Confirmed => Won't Fix

** No longer affects: mate-desktop

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

Title:
  Caja does not show previews of text files on Bionic and newer versions

Status in caja package in Ubuntu:
  Won't Fix
Status in gtk+3.0 package in Ubuntu:
  Invalid

Bug description:
  Steps to reproduce:
  1. Install Ubuntu MATE 18.04 LTS (or upgrade from 16.04 LTS)
  2. Create text file somewhere (in home folder for example) with `echo text > 
~/file.txt`.
  3. Open Caja in home folder

  Expected results:
  * Caja shows preview (the contents) of `file.txt` in Icon view.

  Actual results:
  * Caja does not show preview of `file.txt`.

  
  Notes:
  1. all settings in Preview tab are set to *Local Only*
  2. this happens on clean user profile and/or after `dconf reset -f /` and 
`gsettings reset-recursively  org.mate.caja`
  3. Problem first seen on AskUbuntu ( https://askubuntu.com/q/1065825/66509 ).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: caja 1.20.2-4ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18
  Uname: Linux 4.15.0-30-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Thu Aug 16 12:36:57 2018
  InstallationDate: Installed on 2018-04-26 (111 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  SourcePackage: caja
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1854383] Re: Extra window decorations are created on windows with client-side decorations.

[Martin Wimpress ]

Does this happen with Yaru MATE on Jammy daily?

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

Title:
  Extra window decorations are created on windows with client-side
  decorations.

Status in Ubuntu MATE:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in marco package in Ubuntu:
  New

Bug description:
  Steps to reproduce after a minimal/full install of Ubuntu MATE:

  1. Start up a Gtk3 application with a header bar (tested with Gnome
  Software) or a browser (such as Firefox) without using a standard
  window title bar that saves the position and size of the window before
  it was closed.

  2. Maximize the application window, then close it without changing the
  window size

  3. Relaunch the application and resize/unmaximize it

  After this, dummy window decorations will be created around the
  window. This issue has been tested on a Dell XPS 9570 and using Gnome
  Boxes 3.34.

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


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

[Martin Wimpress ]

** Changed in: gdebi (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 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:
  Fix Committed
Status in vte2.91 package in Ubuntu:
  Fix Released
Status in vte2.91 source package in Bionic:
  Fix Released

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 1946499] Re: installation of deb-packages with gdebi-gtk shows "dpkg: error: unable to read filedescriptor flags for : Bad file descr

[Martin Wimpress ]

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

Title:
  installation of deb-packages with gdebi-gtk shows "dpkg: error: unable
  to read filedescriptor flags for : Bad file descriptor" in gdebi terminal, package is not
  installed

Status in Ubuntu MATE:
  Invalid
Status in gdebi package in Ubuntu:
  Fix Committed
Status in vte2.91 package in Ubuntu:
  Confirmed
Status in gdebi source package in Impish:
  Fix Committed

Bug description:
  Steps to reproduce:
  1. Install Ubuntu MATE 21.10
  2. Open Firefox, navigate to discord.com
  3. Download deb-file. At time of writing from the 
https://dl.discordapp.net/apps/linux/0.0.16/discord-0.0.16.deb link
  4. Open Caja in ~/Downloads folder and use GDebi to install the 
discord-0.0.16.deb file
  5. In the GDebi window click Install button

  Expected results:
  * Gdebi quietly install discord package, there are no error messages in its 
terminal

  Actual results:
  * Gdebi terminal shows the error in the last line

  ```
  Selecting previously unselected package gconf2-common.
  (Reading database ... 457178 files and directories currently installed.)
  Preparing to unpack .../0-gconf2-common_3.2.6-7ubuntu2_all.deb ...
  Unpacking gconf2-common (3.2.6-7ubuntu2) ...
  Selecting previously unselected package libgconf-2-4:amd64.
  Preparing to unpack .../1-libgconf-2-4_3.2.6-7ubuntu2_amd64.deb ...
  Unpacking libgconf-2-4:amd64 (3.2.6-7ubuntu2) ...
  Selecting previously unselected package gconf-service-backend.
  Preparing to unpack .../2-gconf-service-backend_3.2.6-7ubuntu2_amd64.deb ...
  Unpacking gconf-service-backend (3.2.6-7ubuntu2) ...
  Selecting previously unselected package gconf-service.
  Preparing to unpack .../3-gconf-service_3.2.6-7ubuntu2_amd64.deb ...
  Unpacking gconf-service (3.2.6-7ubuntu2) ...
  Selecting previously unselected package libappindicator1.
  Preparing to unpack 
.../4-libappindicator1_12.10.1+20.10.20200706.1-0ubuntu1_amd64.deb ...
  Unpacking libappindicator1 (12.10.1+20.10.20200706.1-0ubuntu1) ...
  Selecting previously unselected package libunwind-13:amd64.
  Preparing to unpack .../5-libunwind-13_1%3a13.0.0-2_amd64.deb ...
  Unpacking libunwind-13:amd64 (1:13.0.0-2) ...
  Selecting previously unselected package libc++abi1-13:amd64.
  Preparing to unpack .../6-libc++abi1-13_1%3a13.0.0-2_amd64.deb ...
  Unpacking libc++abi1-13:amd64 (1:13.0.0-2) ...
  Selecting previously unselected package libc++1-13:amd64.
  Preparing to unpack .../7-libc++1-13_1%3a13.0.0-2_amd64.deb ...
  Unpacking libc++1-13:amd64 (1:13.0.0-2) ...
  Selecting previously unselected package libc++1:amd64.
  Preparing to unpack .../8-libc++1_1%3a13.0-53~exp1_amd64.deb ...
  Unpacking libc++1:amd64 (1:13.0-53~exp1) ...
  Setting up libappindicator1 (12.10.1+20.10.20200706.1-0ubuntu1) ...
  Setting up gconf2-common (3.2.6-7ubuntu2) ...

  Creating config file /etc/gconf/2/path with new version
  Setting up libunwind-13:amd64 (1:13.0.0-2) ...
  Setting up libc++abi1-13:amd64 (1:13.0.0-2) ...
  Setting up libc++1-13:amd64 (1:13.0.0-2) ...
  Setting up libc++1:amd64 (1:13.0-53~exp1) ...
  Setting up gconf-service (3.2.6-7ubuntu2) ...
  Processing triggers for libc-bin (2.34-0ubuntu2) ...
  Processing triggers for sgml-base (1.30) ...
  Setting up libgconf-2-4:amd64 (3.2.6-7ubuntu2) ...
  Setting up gconf-service-backend (3.2.6-7ubuntu2) ...
  Processing triggers for libc-bin (2.34-0ubuntu2) ...
  dpkg: error: unable to read filedescriptor flags for : Bad file descriptor
  ```

  and as the result Discord package is not installed .

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gdebi 0.9.5.7+nmu5ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE
  Date: Fri Oct  8 18:17:36 2021
  InstallationDate: Installed on 2021-10-08 (0 days ago)
  InstallationMedia: Ubuntu-MATE 21.10 "Impish Indri" - Daily amd64 (20211008)
  PackageArchitecture: all
  SourcePackage: gdebi
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2021-10-08T15:41:41.001986

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


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

[Martin Wimpress ]

** Changed in: gdebi (Ubuntu)
   Importance: Medium => High

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

-- 
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:
  Fix Committed
Status in vte2.91 package in Ubuntu:
  Fix Released
Status in vte2.91 source package in Bionic:
  Fix Released

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 1946499] Re: installation of deb-packages with gdebi-gtk shows "dpkg: error: unable to read filedescriptor flags for : Bad file descr

[Martin Wimpress ]

** No longer affects: ubuntu-mate-meta (Ubuntu)

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

** Changed in: gdebi (Ubuntu)
   Status: Confirmed => Triaged

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

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

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

Title:
  installation of deb-packages with gdebi-gtk shows "dpkg: error: unable
  to read filedescriptor flags for : Bad file descriptor" in gdebi terminal, package is not
  installed

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

Bug description:
  Steps to reproduce:
  1. Install Ubuntu MATE 21.10
  2. Open Firefox, navigate to discord.com
  3. Download deb-file. At time of writing from the 
https://dl.discordapp.net/apps/linux/0.0.16/discord-0.0.16.deb link
  4. Open Caja in ~/Downloads folder and use GDebi to install the 
discord-0.0.16.deb file
  5. In the GDebi window click Install button

  Expected results:
  * Gdebi quietly install discord package, there are no error messages in its 
terminal

  Actual results:
  * Gdebi terminal shows the error in the last line

  ```
  Selecting previously unselected package gconf2-common.
  (Reading database ... 457178 files and directories currently installed.)
  Preparing to unpack .../0-gconf2-common_3.2.6-7ubuntu2_all.deb ...
  Unpacking gconf2-common (3.2.6-7ubuntu2) ...
  Selecting previously unselected package libgconf-2-4:amd64.
  Preparing to unpack .../1-libgconf-2-4_3.2.6-7ubuntu2_amd64.deb ...
  Unpacking libgconf-2-4:amd64 (3.2.6-7ubuntu2) ...
  Selecting previously unselected package gconf-service-backend.
  Preparing to unpack .../2-gconf-service-backend_3.2.6-7ubuntu2_amd64.deb ...
  Unpacking gconf-service-backend (3.2.6-7ubuntu2) ...
  Selecting previously unselected package gconf-service.
  Preparing to unpack .../3-gconf-service_3.2.6-7ubuntu2_amd64.deb ...
  Unpacking gconf-service (3.2.6-7ubuntu2) ...
  Selecting previously unselected package libappindicator1.
  Preparing to unpack 
.../4-libappindicator1_12.10.1+20.10.20200706.1-0ubuntu1_amd64.deb ...
  Unpacking libappindicator1 (12.10.1+20.10.20200706.1-0ubuntu1) ...
  Selecting previously unselected package libunwind-13:amd64.
  Preparing to unpack .../5-libunwind-13_1%3a13.0.0-2_amd64.deb ...
  Unpacking libunwind-13:amd64 (1:13.0.0-2) ...
  Selecting previously unselected package libc++abi1-13:amd64.
  Preparing to unpack .../6-libc++abi1-13_1%3a13.0.0-2_amd64.deb ...
  Unpacking libc++abi1-13:amd64 (1:13.0.0-2) ...
  Selecting previously unselected package libc++1-13:amd64.
  Preparing to unpack .../7-libc++1-13_1%3a13.0.0-2_amd64.deb ...
  Unpacking libc++1-13:amd64 (1:13.0.0-2) ...
  Selecting previously unselected package libc++1:amd64.
  Preparing to unpack .../8-libc++1_1%3a13.0-53~exp1_amd64.deb ...
  Unpacking libc++1:amd64 (1:13.0-53~exp1) ...
  Setting up libappindicator1 (12.10.1+20.10.20200706.1-0ubuntu1) ...
  Setting up gconf2-common (3.2.6-7ubuntu2) ...

  Creating config file /etc/gconf/2/path with new version
  Setting up libunwind-13:amd64 (1:13.0.0-2) ...
  Setting up libc++abi1-13:amd64 (1:13.0.0-2) ...
  Setting up libc++1-13:amd64 (1:13.0.0-2) ...
  Setting up libc++1:amd64 (1:13.0-53~exp1) ...
  Setting up gconf-service (3.2.6-7ubuntu2) ...
  Processing triggers for libc-bin (2.34-0ubuntu2) ...
  Processing triggers for sgml-base (1.30) ...
  Setting up libgconf-2-4:amd64 (3.2.6-7ubuntu2) ...
  Setting up gconf-service-backend (3.2.6-7ubuntu2) ...
  Processing triggers for libc-bin (2.34-0ubuntu2) ...
  dpkg: error: unable to read filedescriptor flags for : Bad file descriptor
  ```

  and as the result Discord package is not installed .

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gdebi 0.9.5.7+nmu5ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE
  Date: Fri Oct  8 18:17:36 2021
  InstallationDate: Installed on 2021-10-08 (0 days ago)
  InstallationMedia: Ubuntu-MATE 21.10 "Impish Indri" - Daily amd64 (20211008)
  PackageArchitecture: all
  SourcePackage: gdebi
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2021-10-08T15:41:41.001986

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


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

[Touch-packages] [Bug 1946499] Re: installation of deb-packages with gdebi-gtk shows "dpkg: error: unable to read filedescriptor flags for : Bad file descr

[Martin Wimpress ]

The only difference in 91_keep_fds.patch between vte2.91
(0.62.3-1ubuntu1) and vte2.91 (0.64.2-1ubuntu1) is this:

164,165c164,165
<  auto op = new vte::base::SpawnOperation{spawn_context_from_args(pty,
<  
working_directory,
---
>  auto op = std::make_unique
>  (spawn_context_from_args(pty,

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

Title:
  installation of deb-packages with gdebi-gtk shows "dpkg: error: unable
  to read filedescriptor flags for : Bad file descriptor" in gdebi terminal, package is not
  installed

Status in Ubuntu MATE:
  Confirmed
Status in gdebi package in Ubuntu:
  Confirmed
Status in ubuntu-mate-meta package in Ubuntu:
  Confirmed
Status in vte2.91 package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Install Ubuntu MATE 21.10
  2. Open Firefox, navigate to discord.com
  3. Download deb-file. At time of writing from the 
https://dl.discordapp.net/apps/linux/0.0.16/discord-0.0.16.deb link
  4. Open Caja in ~/Downloads folder and use GDebi to install the 
discord-0.0.16.deb file
  5. In the GDebi window click Install button

  Expected results:
  * Gdebi quietly install discord package, there are no error messages in its 
terminal

  Actual results:
  * Gdebi terminal shows the error in the last line

  ```
  Selecting previously unselected package gconf2-common.
  (Reading database ... 457178 files and directories currently installed.)
  Preparing to unpack .../0-gconf2-common_3.2.6-7ubuntu2_all.deb ...
  Unpacking gconf2-common (3.2.6-7ubuntu2) ...
  Selecting previously unselected package libgconf-2-4:amd64.
  Preparing to unpack .../1-libgconf-2-4_3.2.6-7ubuntu2_amd64.deb ...
  Unpacking libgconf-2-4:amd64 (3.2.6-7ubuntu2) ...
  Selecting previously unselected package gconf-service-backend.
  Preparing to unpack .../2-gconf-service-backend_3.2.6-7ubuntu2_amd64.deb ...
  Unpacking gconf-service-backend (3.2.6-7ubuntu2) ...
  Selecting previously unselected package gconf-service.
  Preparing to unpack .../3-gconf-service_3.2.6-7ubuntu2_amd64.deb ...
  Unpacking gconf-service (3.2.6-7ubuntu2) ...
  Selecting previously unselected package libappindicator1.
  Preparing to unpack 
.../4-libappindicator1_12.10.1+20.10.20200706.1-0ubuntu1_amd64.deb ...
  Unpacking libappindicator1 (12.10.1+20.10.20200706.1-0ubuntu1) ...
  Selecting previously unselected package libunwind-13:amd64.
  Preparing to unpack .../5-libunwind-13_1%3a13.0.0-2_amd64.deb ...
  Unpacking libunwind-13:amd64 (1:13.0.0-2) ...
  Selecting previously unselected package libc++abi1-13:amd64.
  Preparing to unpack .../6-libc++abi1-13_1%3a13.0.0-2_amd64.deb ...
  Unpacking libc++abi1-13:amd64 (1:13.0.0-2) ...
  Selecting previously unselected package libc++1-13:amd64.
  Preparing to unpack .../7-libc++1-13_1%3a13.0.0-2_amd64.deb ...
  Unpacking libc++1-13:amd64 (1:13.0.0-2) ...
  Selecting previously unselected package libc++1:amd64.
  Preparing to unpack .../8-libc++1_1%3a13.0-53~exp1_amd64.deb ...
  Unpacking libc++1:amd64 (1:13.0-53~exp1) ...
  Setting up libappindicator1 (12.10.1+20.10.20200706.1-0ubuntu1) ...
  Setting up gconf2-common (3.2.6-7ubuntu2) ...

  Creating config file /etc/gconf/2/path with new version
  Setting up libunwind-13:amd64 (1:13.0.0-2) ...
  Setting up libc++abi1-13:amd64 (1:13.0.0-2) ...
  Setting up libc++1-13:amd64 (1:13.0.0-2) ...
  Setting up libc++1:amd64 (1:13.0-53~exp1) ...
  Setting up gconf-service (3.2.6-7ubuntu2) ...
  Processing triggers for libc-bin (2.34-0ubuntu2) ...
  Processing triggers for sgml-base (1.30) ...
  Setting up libgconf-2-4:amd64 (3.2.6-7ubuntu2) ...
  Setting up gconf-service-backend (3.2.6-7ubuntu2) ...
  Processing triggers for libc-bin (2.34-0ubuntu2) ...
  dpkg: error: unable to read filedescriptor flags for : Bad file descriptor
  ```

  and as the result Discord package is not installed .

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gdebi 0.9.5.7+nmu5ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE
  Date: Fri Oct  8 18:17:36 2021
  InstallationDate: Installed on 2021-10-08 (0 days ago)
  InstallationMedia: Ubuntu-MATE 21.10 "Impish Indri" - Daily amd64 (20211008)
  PackageArchitecture: all
  SourcePackage: gdebi
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2021-10-08T15:41:41.001986

To manage notifications about this bug go to:

[Touch-packages] [Bug 1946499] Re: installation of deb-packages with gdebi-gtk shows "dpkg: error: unable to read filedescriptor flags for : Bad file descr

[Martin Wimpress ]

From the recent changelog I see 91_keep_fds.patch in vte2.91 was
refreshed.

vte2.91 (0.64.2-1ubuntu1) impish; urgency=medium

  * Merge with debian experimental. Remaining changes:
- Add 91_keep_fds.patch since gdebi still requires it (LP: #1756238)
- Breaks/Replaces with libvte-2.91-0 (<= 0.60.0-2ubuntu1)
- Ubuntu gbp.conf and debian/control VCS information
  * Refresh 91_keep_fds.patch


gunnarhj can you confirm that gdebi fail to install debs?


** Changed in: vte2.91 (Ubuntu)
 Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)

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

Title:
  installation of deb-packages with gdebi-gtk shows "dpkg: error: unable
  to read filedescriptor flags for : Bad file descriptor" in gdebi terminal, package is not
  installed

Status in Ubuntu MATE:
  Confirmed
Status in gdebi package in Ubuntu:
  Confirmed
Status in ubuntu-mate-meta package in Ubuntu:
  Confirmed
Status in vte2.91 package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Install Ubuntu MATE 21.10
  2. Open Firefox, navigate to discord.com
  3. Download deb-file. At time of writing from the 
https://dl.discordapp.net/apps/linux/0.0.16/discord-0.0.16.deb link
  4. Open Caja in ~/Downloads folder and use GDebi to install the 
discord-0.0.16.deb file
  5. In the GDebi window click Install button

  Expected results:
  * Gdebi quietly install discord package, there are no error messages in its 
terminal

  Actual results:
  * Gdebi terminal shows the error in the last line

  ```
  Selecting previously unselected package gconf2-common.
  (Reading database ... 457178 files and directories currently installed.)
  Preparing to unpack .../0-gconf2-common_3.2.6-7ubuntu2_all.deb ...
  Unpacking gconf2-common (3.2.6-7ubuntu2) ...
  Selecting previously unselected package libgconf-2-4:amd64.
  Preparing to unpack .../1-libgconf-2-4_3.2.6-7ubuntu2_amd64.deb ...
  Unpacking libgconf-2-4:amd64 (3.2.6-7ubuntu2) ...
  Selecting previously unselected package gconf-service-backend.
  Preparing to unpack .../2-gconf-service-backend_3.2.6-7ubuntu2_amd64.deb ...
  Unpacking gconf-service-backend (3.2.6-7ubuntu2) ...
  Selecting previously unselected package gconf-service.
  Preparing to unpack .../3-gconf-service_3.2.6-7ubuntu2_amd64.deb ...
  Unpacking gconf-service (3.2.6-7ubuntu2) ...
  Selecting previously unselected package libappindicator1.
  Preparing to unpack 
.../4-libappindicator1_12.10.1+20.10.20200706.1-0ubuntu1_amd64.deb ...
  Unpacking libappindicator1 (12.10.1+20.10.20200706.1-0ubuntu1) ...
  Selecting previously unselected package libunwind-13:amd64.
  Preparing to unpack .../5-libunwind-13_1%3a13.0.0-2_amd64.deb ...
  Unpacking libunwind-13:amd64 (1:13.0.0-2) ...
  Selecting previously unselected package libc++abi1-13:amd64.
  Preparing to unpack .../6-libc++abi1-13_1%3a13.0.0-2_amd64.deb ...
  Unpacking libc++abi1-13:amd64 (1:13.0.0-2) ...
  Selecting previously unselected package libc++1-13:amd64.
  Preparing to unpack .../7-libc++1-13_1%3a13.0.0-2_amd64.deb ...
  Unpacking libc++1-13:amd64 (1:13.0.0-2) ...
  Selecting previously unselected package libc++1:amd64.
  Preparing to unpack .../8-libc++1_1%3a13.0-53~exp1_amd64.deb ...
  Unpacking libc++1:amd64 (1:13.0-53~exp1) ...
  Setting up libappindicator1 (12.10.1+20.10.20200706.1-0ubuntu1) ...
  Setting up gconf2-common (3.2.6-7ubuntu2) ...

  Creating config file /etc/gconf/2/path with new version
  Setting up libunwind-13:amd64 (1:13.0.0-2) ...
  Setting up libc++abi1-13:amd64 (1:13.0.0-2) ...
  Setting up libc++1-13:amd64 (1:13.0.0-2) ...
  Setting up libc++1:amd64 (1:13.0-53~exp1) ...
  Setting up gconf-service (3.2.6-7ubuntu2) ...
  Processing triggers for libc-bin (2.34-0ubuntu2) ...
  Processing triggers for sgml-base (1.30) ...
  Setting up libgconf-2-4:amd64 (3.2.6-7ubuntu2) ...
  Setting up gconf-service-backend (3.2.6-7ubuntu2) ...
  Processing triggers for libc-bin (2.34-0ubuntu2) ...
  dpkg: error: unable to read filedescriptor flags for : Bad file descriptor
  ```

  and as the result Discord package is not installed .

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gdebi 0.9.5.7+nmu5ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE
  Date: Fri Oct  8 18:17:36 2021
  InstallationDate: Installed on 2021-10-08 (0 days ago)
  InstallationMedia: Ubuntu-MATE 21.10 "Impish Indri" - Daily amd64 (20211008)
  PackageArchitecture: all
  SourcePackage: gdebi
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   

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

[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

[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

[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

[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

[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

[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()

[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

[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

[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

[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

[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()

[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

[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

[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

[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

[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

[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()

[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()

[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

[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

[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

[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

[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

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

[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

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

[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

[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

[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

[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

[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

[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

[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

[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

[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

[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