from:"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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

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

** 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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

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

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

-- 
You received this bug notification because you are a member of Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

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

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

-- 
You received this bug notification because you are a member of Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1967507] Re: Yaru Metacity theme has incorrectly scaled windows buttons on HiDPI displays

2022-04-11 Thread Martin Wimpress 

** Changed in: yaru-theme (Ubuntu)
   Status: Invalid => Triaged

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

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

** Changed in: yaru-theme (Ubuntu)
   Importance: Low => Medium

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to yaru-theme in Ubuntu.
https://bugs.launchpad.net/bugs/1967507

Title:
  Yaru Metacity theme has incorrectly scaled windows buttons on HiDPI
  displays

Status in marco package in Ubuntu:
  Invalid
Status in ubuntu-mate-artwork package in Ubuntu:
  Invalid
Status in ubuntu-mate-settings package in Ubuntu:
  New
Status in yaru-theme package in Ubuntu:
  Triaged

Bug description:
   HiDPI scaling is broken in Mate 1.26 produced unscaled/corrputed
  Windows buttons

  Steps to reproduce:

  Mate Tweak > Windows > HiDPI change from "auto" to "HiDPI"
  Result: A lot of flickering then everything looks fine at 200%
  Reboot & login: Window title buttons are all of a sudden unscaled again while 
the rest is as expected (see image)
  Default wallpaper is grainy at 200% // No workaround

  Workaround 1: Mate Tweak > Windows > HiDPI change from "HiDPI" to "auto" and 
back to "HiDPI"
  Workaround 2:  Change theme from Yaru Light to something else and back to 
Yaru light

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


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

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

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

** No longer affects: ubuntu-mate

-- 
You received this bug notification because you are a member of Desktop
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
  to blacklis

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

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

** No longer affects: ubuntu-mate

-- 
You received this bug notification because you are a member of Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1821754] Re: huge files created when copying from a network drive.

** No longer affects: ubuntu-mate

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1821754

Title:
  huge files created when copying from a network drive.

Status in caja package in Ubuntu:
  New
Status in gvfs package in Ubuntu:
  New

Bug description:
  When copying files from a cifs share (mounted via pam_mount) to the
  same share or to a local drive, sometimes it keeps on copying data and
  creates a huge files (into the tens of gigabytes). An .goutputstream
  file is then also created of the same size.

  After checking more options. It happens with any filemanager and cp
  (copying from samba-share to samba-share)

  Tested this on ubuntu mate bionic (18.04.2) on amd64

  Has corrupted quite some files here now.

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


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

[Desktop-packages] [Bug 1860975] Re: Cannot set image as desktop background from Shotwell

** No longer affects: ubuntu-mate

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to shotwell in Ubuntu.
https://bugs.launchpad.net/bugs/1860975

Title:
  Cannot set image as desktop background from Shotwell

Status in shotwell package in Ubuntu:
  Confirmed

Bug description:
  This problem affects Ubuntu Mate 19.10 and 20.04.

  A common action to use in the Shotwell photo organiser is to set a
  photo as the desktop wallpaper. However this function does not work on
  Ubuntu Mate due, I assume, to Shotwell configuring settings for the
  Gnome desktop rather than for Mate.

  Steps to reproduce:

  Launch Shotwell
  Import a photo
  Select the photo, then select the following menu option: File -> Set as 
Desktop Background
  From the pop-up dialogue, select 'Use for Desktop' and click 'OK'.

  Result:
  No change to the Mate desktop wallpaper.

  Desired result:
  The Mate desktop wallpaper should change to the selected image.

  Thanks
  Nick

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


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

[Desktop-packages] [Bug 1866452] Re: Intel NUC5CPYH - Mouse pointer display on HDMI out does not cover all screen

** No longer affects: ubuntu-mate

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1866452

Title:
  Intel NUC5CPYH - Mouse pointer display on HDMI out does not cover all
  screen

Status in xf86-video-intel:
  New
Status in Ubuntu:
  New
Status in xserver-xorg-video-intel package in Ubuntu:
  New

Bug description:
  Issue Description
  -
  Intel NUC5CPYH has two video outputs:
  - VGA
  - HDMI

  On HDMI Output
  - the visible pointer can't reach the left screen border by couple of pixels 
(it get stuck in a limit position)
  - the invisible pointer in the background handle normally.

  On VGA Out
  - the pointer both visible and invisible behave normally

  On Both Monitors connected on boot (Mate 20.04 beta)
  - the pointer both visible and invisible behave normally on both outputs
  - removing VGA monitor already logged in on desktop, mouse will behave also 
normally both visible and invisible on HDMI Output.

  Connect VGA monitor after boot (Mate 20.04 beta)
  - same issue as booting with HDMI out only
  - this does not matter if I use both screens after or just one, issue is 
related to boot initialization.

  It affects probably all Ubuntu distribution.
  Tested only on Ubuntu and Ubuntu Mate, both 19.10 and also 20.04 daily builds.

  Issue first noticed
  --
  Issue first appear on Ubuntu Mate 16.04 after performing LTS hardware 
enabling Stack when first available, and find that is related to xserver-xorg 
HWE, by reverting it back, wile keeping HWE Kernel.

  Note
  
  This system also has another mouse pointer bug
  https://bugs.launchpad.net/ubuntu-mate/+bug/1866454

To manage notifications about this bug go to:
https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1866452/+subscriptions


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

[Desktop-packages] [Bug 1866454] Re: Intel NUC5CPYH - dual mouse pointer display when booting with two screens

** No longer affects: ubuntu-mate

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1866454

Title:
  Intel NUC5CPYH - dual mouse pointer display when booting with two
  screens

Status in xf86-video-intel:
  New
Status in Ubuntu:
  New
Status in xserver-xorg-video-intel package in Ubuntu:
  New

Bug description:
  
  Issue Description
  -
  - two mouse pointers on screen on booting with on dual monitor setup, One 
behave normally second is stuck just animate synchronously with first one.
  - The presence of second mouse pointer results in mouse pointer trailing 
artifacts and screen artifacts under mouse pointer, rendering desktop unusable.
  - On Ubuntu Mate the second mouse pointer appear on a screen edge, and on 
Regular Ubuntu it appear somewhere on one of the two screens.

  Affected Systems
  
  - Tested on Both Ubuntu Mate and regular Ubuntu, both version 19.10 and 20.04

  Issue reproduction
  --
  - booting with two monitors connected on affected system, 
  (connecting second monitor after login screen -lightdm greeter ... - will 
prevent issue appear)

  Workarounds
  ---
  - booting with only one monitor connected, and connect the second one later 
after log-in screen appear.
  - on booting with two monitors on Ubuntu Mate: Disabling Marco - Adaptive 
compositor to "No Compositor" will solve pointer trailing and screen artifacts, 
(but the second mouse pointer remain outside screen.

  
  Note
  
  This system also has another mouse pointer bug
  https://bugs.launchpad.net/ubuntu-mate/+bug/1866452

To manage notifications about this bug go to:
https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1866454/+subscriptions


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

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

** No longer affects: ubuntu-mate

-- 
You received this bug notification because you are a member of Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1706770] Re: Lock screen can be bypassed when auto-login is enabled via gnome-system-tools

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

-- 
You received this bug notification because you are a member of Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1860976] Re: Shotwell's 'Send To...' feature does not work in MATE without creating 'nautilus-sendto' link

** No longer affects: ubuntu-mate

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to shotwell in Ubuntu.
https://bugs.launchpad.net/bugs/1860976

Title:
  Shotwell's 'Send To...' feature does not work in MATE without creating
  'nautilus-sendto' link

Status in caja-extensions package in Ubuntu:
  New
Status in shotwell package in Ubuntu:
  New

Bug description:
  Hi

  This problem affects both 19.10 and 20.04.

  In Shotwell there is an option to email a selected photo via the
  default mail client, in my case Evolution. However, in Ubuntu Mate
  this option is greyed out. You can see this via:

  1. Select a photo, and right-click on it. The 'Send To...' option is greyed 
out.
  2. Select a photo, and then click on the 'File' menu. The 'Send To...' option 
is not greyed out this time, but cannot be selected (so, same result).

  A quick online search has found a solution to this, which is:

  cd /usr/bin
  sudo ln -s caja-sendto nautilus-sendto

  Restart Shotwell and the 'Send To...' option now  as expected.

  Can this solution be validated and if deemed fit for purpose included
  in the 20.04 LTS?

  Thanks
  Nick

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


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

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

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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

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

** 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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

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

** 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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

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

** 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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1769362] Re: with multiple monitors, lightDM does not appear on the display set as primary

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

** No longer affects: ubuntu-mate

-- 
You received this bug notification because you are a member of Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1873236] Re: 20.04 - 2 network icons displayed

** No longer affects: ubuntu-mate

--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-applet in Ubuntu.
https://bugs.launchpad.net/bugs/1873236

Title:
20.04 - 2 network icons displayed

Status in network-manager-applet package in Ubuntu:
Confirmed

Bug description:
Ubuntu MATE daily since start of Alpha. No changes to system or
network since installation, only testing apps and compiz.

This morning, after several suspend/resume I have 2 network indicators
displaying, which has not previously occurred. (At same time power
management indicator - it is a laptop - disappeared. See separate
report #1871854)

Using default theme with icons just changed in colour to orange with
the new applet back at start of beta test when it became available.

1 network icon is the correct one of 2 small arrows (1 up, 1 down) and
left click displays network info, and right click displays About, help
etc. As expected. About info displays Indicator Applet Complete
1.24.0.

2nd, new, icon is same but larger, and both left and right click
display the same network info, so no way to access the About info.

I do have MATE Netspeed indicator active, but it has been throughout
my testing.

Returns to 1 network indicator (the smaller correct one) after
logout/login.

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

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

[Desktop-packages] [Bug 1768920] Re: 2 WiFi Icons in the Panel after installation of 18.04

** No longer affects: ubuntu-mate

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-applet in Ubuntu.
https://bugs.launchpad.net/bugs/1768920

Title:
  2 WiFi Icons in the Panel after installation of 18.04

Status in network-manager-applet package in Ubuntu:
  Invalid
Status in ubuntu-mate-settings package in Ubuntu:
  Fix Released

Bug description:
  After installing Ubuntu Mate 18.04, on the First login it shows 2 WiFi icons 
in the top panel.
  It goes away after the reboot though.

  My Laptop: Dell XPS 13 9370 Developer Edition, 16 GB RAM and 1 TB SSD

  Regards,
  Saurabh

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


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

[Desktop-packages] [Bug 1877762] Re: 1360x768 Vega graphics display staggered

** No longer affects: ubuntu-mate

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu.
https://bugs.launchpad.net/bugs/1877762

Title:
  1360x768 Vega graphics display staggered

Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Confirmed

Bug description:
  This was the go-to resolution pre-update. All of the other modes seem
  to work.

  Release 20.04 LTS (Focal Fossa) 64-bit
  Kernel Linux 5.4.0-29-generic x86_64
  MATE 1.24.0
  Processor: AMD Ryzen 3 2200G with Radeon Vega Graphics × 4 
  Graphics: AMD RAVEN (DRM 3.35.0, 5.4.0-29-generic, LLVM 9.0.1)
  lspci output: 38:00.0 VGA compatible controller: Advanced Micro Devices, Inc. 
[AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] (rev c8)

  As you can see from the attached image, the display shifts to the
  right every few lines.

  Still working on installing the full amdgpu package (libffs 6
  required, 7 installed so I'm working on the bits).

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


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

[Desktop-packages] [Bug 1888392] Re: The libreoffice interface does not appear in Ubuntu MATE

** No longer affects: ubuntu-mate

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1888392

Title:
  The libreoffice interface does not appear in Ubuntu MATE

Status in libreoffice package in Ubuntu:
  New

Bug description:
  When I try to open a document in libreoffice, the application does not
  open completely. Only the window bar appears.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libreoffice-core 1:6.4.4-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Tue Jul 21 09:26:19 2020
  ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
  InstallationDate: Installed on 2020-04-27 (84 days ago)
  InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 
(20200423)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

** 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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1904460] Re: Gnome disks icon is missing when upgraded from 18.04 to 20.04

** No longer affects: ubuntu-mate

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-disk-utility in Ubuntu.
https://bugs.launchpad.net/bugs/1904460

Title:
  Gnome disks icon is missing when upgraded from 18.04 to 20.04

Status in gnome-disk-utility package in Ubuntu:
  Incomplete

Bug description:
  Upgraded 18.04 to 20.04 using 'do-release-upgrade'. I now have a
  missing icon for gnome disks. I have reinstalled adwaita icons and
  brisk menu, to no avail.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1904460/+subscriptions


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

[Desktop-packages] [Bug 1904462] Re: Dejadup fails after upgrading from 18.04 to 20.04

** No longer affects: ubuntu-mate

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to deja-dup in Ubuntu.
https://bugs.launchpad.net/bugs/1904462

Title:
  Dejadup fails after upgrading from 18.04 to 20.04

Status in deja-dup package in Ubuntu:
  Incomplete

Bug description:
  Upgraded from 18.04 to 20.04 using do-release-upgrade. Dejadup now
  fails to make backups. Log attached, i think the last line is the
  error.

  "PermissionError: [Errno 13] Permission denied:
  b'/home/morpheus/.config/gnome-mpv/.deja-dup-ignore'

  I have checked inside that folder, and there is no hidden file '.deja-
  dup-ignore'

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


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

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

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

** No longer affects: ubuntu-mate

-- 
You received this bug notification because you are a member of Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

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

** No longer affects: ubuntu-mate

-- 
You received this bug notification because you are a member of Desktop
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 NetworkManager[22616]:   
[16

[Desktop-packages] [Bug 1922137] Re: [20.04.2-latest] Default print spoiler(TTY7) is useless when XeroxOffice is installed

** No longer affects: ubuntu-mate

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to system-config-printer in Ubuntu.
https://bugs.launchpad.net/bugs/1922137

Title:
  [20.04.2-latest] Default print spoiler(TTY7) is useless when
  XeroxOffice is installed

Status in system-config-printer package in Ubuntu:
  New

Bug description:
  On a regular desktop running focal 20.04.2 fully patched and using a
  LAN Xerox laser printer, the printer spoiler (when you press ctrl+p)
  is totally useless and it's options are disregarded.

  
  Reproduction steps:

  1. Install /opt/XeroxOffice/ @ 
https://www.support.xerox.com/en-us/product/versalink-c405/downloads
  2. Open .odt -> ctrl+p -> copies=50 -> print -> xerox print wizard opens -> 
copies=1 -> print = 1 paper copy only

  (ofc, the same result when using FireFox!)

  <3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1922137/+subscriptions


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

[Desktop-packages] [Bug 1937350] Re: USB HDD not properly spin down after safely remove

** No longer affects: ubuntu-mate

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to udisks2 in Ubuntu.
https://bugs.launchpad.net/bugs/1937350

Title:
  USB HDD not properly spin down after safely remove

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  New
Status in udisks2 package in Ubuntu:
  New

Bug description:
  I do not know which package I should file the bug for.

  I am using Ubuntu MATE 20.04 LTS and Microsoft Windows 10.

  On Microsoft Windows 10, no issue with safely remove any USB external
  HDD. When using Microsoft Windows 10, after safely remove my external
  HDD, the HDD will spin down.

  But, on Ubuntu MATE 20.04 LTS, some issues occur after I try to safely
  remove my external HDD.

  Tried different hard drive, different enclosures, and also some
  external hard drive that came bundled with enclosure. All having same
  or different issues after safely remove them in Ubuntu MATE.

  Problems will also occur on those branded external HDD that came
  bundled with enclosure, for example, those Seagate Backup Plus drives
  ( https://www.seagate.com/as/en/consumer/backup/backup-plus/ ).

  Here are the common problems after safely remove (in Ubuntu MATE):
  1. The external HDD will spin down and then spin up again, and then being 
automatically remounted again. The "dmesg" command shows errors.

  2. The external HDD will spin down and then spin up again, no remount.
  The LED on the enclosure keep flashing. The "dmesg" command shows
  errors. After you unplug the HDD, you can connect another HDD.

  3. The external HDD will spin down and then spin up again, no remount.
  The LED on the enclosure keep flashing. The "dmesg" command shows
  errors. BUT, after you unplug the HDD, when you connect another HDD,
  the computer will not detect it and will not mount it until you reboot
  the computer. But, before reboot connecting another device (e.g.
  keyboard, mouse, etc) to the same USB port, the device works
  perfectly.

  4. The external HDD will spin down and then spin up again, no remount.
  But, after a few seconds, it spin down again. But, still, the "dmesg"
  command shows errors.

  Different HDD, different enclosure, show different symptoms or
  problems. Some HDD enclosures, number 1 above will occur. Some HDD
  enclosures, either number 2 or 3 above will occur. Sometimes, problem
  number 2 above will occur. Sometimes, problem number 3 will occur.
  Some enclosure, problem number 4 will occur.

  Here, I will use the following enclosure as example in this bug
  report:

  Product link: https://www.ugreen.com/products/usb-c-2-5-sata-iii-hard-
  drive-enclosure

  Purchase link in my country: https://shopee.com.my/UGREEN-USB-3.1-To-
  SATA-III-External-Hard-Drive-
  Enclosure-(2.5-)-i.64923440.1583255569?position=1

  Here are the steps to reproduce (for the enclosure above):

  1. Connect the external HDD to any available USB 3.0 port. The HDD will be 
mounted. Caja (Ubuntu MATE default file manager) will launch.
  2. Close the Caja window. Do not do anything on the HDD.
  3. Use left or right hand, touch the HDD enclosure to feel the spinning. Do 
not let your hand leave the enclosure, so that you can continue feel the 
spinning.
  4. Use your another hand to operate your computer.
  5. Go to desktop.
  6. Right click on the external HDD icon.
  7. Click "Safely Remove Drive".

  The HDD unmounted. Assume that one of your hands still touching the
  enclosure of the HDD, you will feel that the HDD will spin down and
  then spin up again. No remount. The LED indicator on the enclosure
  will keep flashing. These are described in problem number 2 and 3
  above. Sometimes, after you unplug the drive and try to connect
  another drive, it will not be detected until you reboot your computer.

  Almost all external HDDs I tested will cause "dmesg" command to shows
  "Buffer I/O error" and "Synchronize Cache() failed" error
  after "Safely Remove Drive".

  In Microsoft Windows 10, all above mentioned problems WILL NOT occur.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  cshong 1059 F pulseaudio
   /dev/snd/controlC0:  cshong 1059 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-11-23 (242 days ago)
  InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  IwConfig:
   lono wireless extensions.
   
   enp3s0no wireless extensions.
  MachineType: ASUS All Series
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-63-generic 
root=UUID=cad772fa-c02b-4268-bc15-e366825ac807 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18
  RelatedPackageVersions:
   linux-restr

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

** No longer affects: ubuntu-mate

-- 
You received this bug notification because you are a member of Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1914891] Re: Wi-Fi "connect to new network" goes AWOL when changing geolocalisation

** No longer affects: ubuntu-mate

--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-applet in Ubuntu.
https://bugs.launchpad.net/bugs/1914891

Title:
Wi-Fi "connect to new network" goes AWOL when changing geolocalisation

Status in network-manager-applet package in Ubuntu:
New

Bug description:
If/when you install 20.04.1 and during setup you choose a BSSID +
finish installation + fully patched system and everything ok, then if
you take your laptop over to a different geolocalisation that has
different wifi equipment, it becomes fairly hard/impossible for a
simple end user to then connect to a new equipment in this new
location because there exists no list of found access points.

To state this differently:
1. I installed 20.04.1 ISO on my laptop;
2. During installation there was a "wizard" that found a bunch of APs and I
connected to one, did the installation, everything went well;
3. Everytime I am physically located where this AP I connected to during
installation is: my Internet works no problem.
4. Everytime I take this system and go elsewhere that has different APs, all
that MATE gives me at TTY7 launch is that yellow pop-up at the right-hand upper
portion of the screen saying that there are other APs nearby.
-> The problem with that is: I need to manually go under Control Center ->
Advanced Network Configuration -> click on green "+" -> select Wi-Fi -> Fill in
all of those informations.

This is no problem when you actually know where to connect to. But
that is not always the case.

My expectations: Instead of MATE telling me it found APs around me
(Point #4) is that I would like for that same auto-discovery of APs
that was launched during installation to also be available somewhere
in MATE so I actually see a list of which APs are around me. That is
not currently the case, we need to guess, and this is frustrating.

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

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

** No longer affects: ubuntu-mate

-- 
You received this bug notification because you are a member of Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

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

** No longer affects: ubuntu-mate

-- 
You received this bug notification because you are a member of Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad

[Desktop-packages] [Bug 1884379] Re: Mass Storage is not unmounted after logoff

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

** No longer affects: ubuntu-mate

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1884379

Title:
  Mass Storage is not unmounted after logoff

Status in gvfs package in Ubuntu:
  New

Bug description:
  Mass Storage is not unmounted after logoff
  I could not access an usb-drive, after some investigation
  you can reproduce this by:

  Login user1 plugin USB-Mass Storage device
  Logoff user1
  Login with user2, USB-Mass Storage device is mounted as user1
  (or use a tty to check: mounts)

  https://ubuntu-mate.community/t/mass-storage-is-not-unmounted-after-
  logoff/22172

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


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

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

** No longer affects: ubuntu-mate

-- 
You received this bug notification because you are a member of Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

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

** No longer affects: ubuntu-mate

-- 
You received this bug notification because you are a member of Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

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

** No longer affects: ubuntu-mate

-- 
You received this bug notification because you are a member of Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1889057] Re: shares-admin can't install services - failed to install package: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.PackageKit was not

** No longer affects: ubuntu-mate

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1889057

Title:
  shares-admin can't install services - failed to install package:
  GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
  org.freedesktop.PackageKit was not provided by any .service files

Status in gnome-software package in Ubuntu:
  Incomplete
Status in sessioninstaller package in Ubuntu:
  Won't Fix

Bug description:
  Steps to reproduce:
  1. Have Ubuntu MATE 20.04 LTS installed
  2. Launch `shares-admin`
  3. Confirm installation of sharing services by clicking "Install services" in 
the opened window

  Expected results:
  * services are installed

  Actual results:
  * services are not installed, terminal shows the error:

  ```
  ** (shares-admin:9029): WARNING **: 12:11:42.050: failed to install package: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.freedesktop.PackageKit was not provided by any .service files
  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-system-tools 3.0.0-9ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Mon Jul 27 12:06:27 2020
  InstallationDate: Installed on 2020-07-08 (18 days ago)
  InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 
(20200423)
  SourcePackage: gnome-system-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

** No longer affects: ubuntu-mate

-- 
You received this bug notification because you are a member of Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

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

** No longer affects: ubuntu-mate

-- 
You received this bug notification because you are a member of Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1955505] Re: Wrong context menu font is used

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to vte2.91 in Ubuntu.
https://bugs.launchpad.net/bugs/1955505

Title:
  Wrong context menu font is used

Status in MATE Desktop:
  Unknown
Status in mate-terminal package in Ubuntu:
  Fix Committed
Status in vte2.91 package in Ubuntu:
  Invalid

Bug description:
  Expected behaviour: Font should display as expected.

  Actual behaviour: A monospace font is displayed instead.

  Steps to reproduce the behaviour:

  1. Install Ubuntu MATE 22.04 LTS
  2. Launch mate-terminal
  3. Do right mouse click to get context menu

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: mate-terminal 1.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu74
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE
  Date: Tue Dec 21 23:49:21 2021
  InstallationDate: Installed on 2021-12-21 (0 days ago)
  InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Alpha amd64 
(20211221)
  SourcePackage: mate-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1955505] Re: Wrong context menu font is displayed when using vte 0.66.2-1

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

** Summary changed:

- Wrong context menu font is displayed when using vte 0.66.2-1
+ Wrong context menu font is used

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to vte2.91 in Ubuntu.
https://bugs.launchpad.net/bugs/1955505

Title:
  Wrong context menu font is used

Status in MATE Desktop:
  Unknown
Status in mate-terminal package in Ubuntu:
  In Progress
Status in vte2.91 package in Ubuntu:
  Invalid

Bug description:
  Expected behaviour: Font should display as expected.

  Actual behaviour: A monospace font is displayed instead.

  Steps to reproduce the behaviour:

  1. Install Ubuntu MATE 22.04 LTS
  2. Launch mate-terminal
  3. Do right mouse click to get context menu

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: mate-terminal 1.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu74
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE
  Date: Tue Dec 21 23:49:21 2021
  InstallationDate: Installed on 2021-12-21 (0 days ago)
  InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Alpha amd64 
(20211221)
  SourcePackage: mate-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

** No longer affects: ubuntu-mate

-- 
You received this bug notification because you are a member of Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1932005] Re: nm-applet not showing in system tray

** No longer affects: ubuntu-mate

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-applet in Ubuntu.
https://bugs.launchpad.net/bugs/1932005

Title:
  nm-applet not showing in system tray

Status in network-manager-applet package in Ubuntu:
  New

Bug description:
  Hello all,

  I noticed this morning that the network options (i am not sure if it
  suppose to be nm-applet) is no longer showing in system tray and for a
  while now that KDE Connect indicator is not showing in the system
  tray.

  
  I am currently Ubuntu Mate 20.04 on a raspberry PI400  uname -a
  Linux pi400 5.4.0-1036-raspi #39-Ubuntu SMP PREEMPT Wed May 12 17:37:51 UTC 
2021 aarch64 aarch64 aarch64 GNU/Linux

  
  cat /etc/os-release 
  NAME="Ubuntu"
  VERSION="20.04.2 LTS (Focal Fossa)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 20.04.2 LTS"
  VERSION_ID="20.04"
  HOME_URL="https://www.ubuntu.com/";
  SUPPORT_URL="https://help.ubuntu.com/";
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/";
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy";
  VERSION_CODENAME=focal
  UBUNTU_CODENAME=focal

  apt policy network-manager
  network-manager:
Installed: 1.22.10-1ubuntu2.2
Candidate: 1.22.10-1ubuntu2.2
Version table:
   *** 1.22.10-1ubuntu2.2 500
  500 http://ports.ubuntu.com/ubuntu-ports focal-updates/main arm64 
Packages
  100 /var/lib/dpkg/status
   1.22.10-1ubuntu1 500
  500 http://ports.ubuntu.com/ubuntu-ports focal/main arm64 Packages

  Does anyone else have a similar issue?

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


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

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

** No longer affects: ubuntu-mate

-- 
You received this bug notification because you are a member of Desktop
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 na_letter_8.5x11in_bo

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

** No longer affects: ubuntu-mate

-- 
You received this bug notification because you are a member of Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1950094] Re: libreoffice base zone liste choix impossible

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

** No longer affects: ubuntu-mate

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1950094

Title:
  libreoffice base zone liste choix impossible

Status in libreoffice package in Ubuntu:
  New

Bug description:

  Bonjour,

  Ce phénomène existait déjà sous UbuntuMate 20.04. J'ai donc chargé
  UbuntuMate 21.10 afin de voir si une modification avait été apporté à
  un éventuel bogue que je vous soumets.

  Le souci est avec la zone de liste dans LibreOffice Base avec la macro
  ci-dessous sur Événement "A réception du focus".

  Sub ActualiserListe(oEv as Object)
  oEv.Source.Model.Refresh
  End Sub

  pour mettre à jour la zone de liste après modification d'un élément.

  La mise à jour fonctionne bien mais je ne peux pas choisir une
  nouvelle entrée dans la liste. Alors que si je choisis un autre
  événement, comme "souris déplacée alors qu'une touche est pressée"
  beaucoup moins pratique, je ne rencontre pas ce problème.

  Après plusieurs recherches sur le forum OpenOffice il s'avère que la
  fonction marche bien mais que le problème pourrait venir de
  l'environnement Ubuntu.

  Sauriez-vous m'aider pour débloquer ma situation ?

  Dommage que je ne puisse pas joindre mon fichier pour des essais sur
  vos propres machines ce serait plus "parlant".

  Merci.
  Éric

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


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

[Desktop-packages] [Bug 1955827] Re: Firefox without 'TitleBar' alters the look of MATE buttons

** No longer affects: ubuntu-mate

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1955827

Title:
  Firefox without 'TitleBar' alters the look of MATE buttons

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  I was testing Ubuntu MATE 20.04, and when I was configuring Firefox [95.0.1] 
I noticed that when I customized the toolbar and left it without 'Title Bar' 
the window buttons were cut off.
  I thought it might be a Firefox theme issue but when I changed the theme the 
problem persisted.

  https://subirimagenes.s3.eu-
  central-1.wasabisys.com/subirimagenes/2kYiAJh1dw.png

  
https://subirimagenes.s3.eu-central-1.wasabisys.com/subirimagenes/uJZed9mBAC.png
  --- 
  ProblemType: Bug
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu-mate   2046 F pulseaudio
  BuildID: 20210804193234
  CasperMD5CheckMismatches: 
./pool/restricted/n/nvidia-graphics-drivers-470-server/libnvidia-gl-470-server_470.57.02-0ubuntu0.20.04.3_amd64.deb
  CasperMD5CheckResult: skip
  CasperVersion: 1.445.1
  Channel: Unavailable
  CurrentDesktop: MATE
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:352
  DefaultProfilePrefSources: /usr/lib/firefox/defaults/pref/all-ubuntumate.js
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  DistroRelease: Ubuntu 20.04
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   # Include files from /etc/network/interfaces.d:
   source-directory /etc/network/interfaces.d
  IpRoute:
   default via 192.168.1.1 dev wlp7s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp7s0 scope link metric 1000 
   192.168.1.0/24 dev wlp7s0 proto kernel scope link src 192.168.1.3 metric 600
  LiveMediaBuild: Ubuntu-MATE 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: firefox 91.0+build2-0ubuntu0.20.04.1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22
  Profile0Extensions: extensions.sqlite corrupt or missing
  Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile0Locales: extensions.sqlite corrupt or missing
  Profile0PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:352
  Profile0PrefSources:
   /usr/lib/firefox/defaults/pref/all-ubuntumate.js
   prefs.js
  Profile0Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile1 (Default) - LastVersion=None/None (Out of date)
   Profile0 - LastVersion=91.0/20210804193234 (In use)
  RunningIncompatibleAddons: False
  Tags:  focal
  Uname: Linux 5.11.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/04/2013
  dmi.bios.release: 1.1
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0VRTT1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A11
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.ec.firmware.release: 1.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd11/04/2013:br1.1:efr1.1:svnDellInc.:pnInspiron3420:pvrNotSpecified:rvnDellInc.:rn0VRTT1:rvrA11:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 3420
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.
  --- 
  ProblemType: Bug
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu-mate   2046 F pulseaudio
  BuildID: 20210804193234
  CasperMD5CheckMismatches: 
./pool/restricted/n/nvidia-graphics-drivers-470-server/libnvidia-gl-470-server_470.57.02-0ubuntu0.20.04.3_amd64.deb
  CasperMD5CheckResult: skip
  CasperVersion: 1.445.1
  Channel: Unavailable
  CurrentDesktop: MATE
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:3

[Desktop-packages] [Bug 1920985] Re: Orca no longer able to review MATE-Terminal output

** No longer affects: ubuntu-mate

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

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

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to orca in Ubuntu.
https://bugs.launchpad.net/bugs/1920985

Title:
  Orca no longer able to review MATE-Terminal output

Status in mate-terminal package in Ubuntu:
  Invalid
Status in orca package in Ubuntu:
  Fix Released

Bug description:
  To reproduce, launch Ubuntu 21.04 Daily, launch the screen reader,
  open a Terminal, and press CAPSLOCK+I to read the current line.

  Expected behavior: Orca would read the line with the prompt where the
  cursor is.

  Actual: Orca reads the menu bar. Using CAPSLOCK+O to move down a line,
  Orca says "Tab list", but further presses of the same key do not yield
  any more speech.

  In 20.10, this works as expected, and I can review the full window
  contents from down at the prompt up to the menu bar, line by line.

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


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

[Desktop-packages] [Bug 1955505] Re: Wrong context menu font is displayed when using vte 0.66.2-1

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

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

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

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to vte2.91 in Ubuntu.
https://bugs.launchpad.net/bugs/1955505

Title:
  Wrong context menu font is displayed when using vte 0.66.2-1

Status in MATE Desktop:
  Unknown
Status in mate-terminal package in Ubuntu:
  Triaged
Status in vte2.91 package in Ubuntu:
  Invalid

Bug description:
  Expected behaviour: Font should display as expected.

  Actual behaviour: A monospace font is displayed instead.

  Steps to reproduce the behaviour:

  1. Install Ubuntu MATE 22.04 LTS
  2. Launch mate-terminal
  3. Do right mouse click to get context menu

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: mate-terminal 1.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu74
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE
  Date: Tue Dec 21 23:49:21 2021
  InstallationDate: Installed on 2021-12-21 (0 days ago)
  InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Alpha amd64 
(20211221)
  SourcePackage: mate-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1406538] Re: Screenshot contains selected area highlight

** Changed in: mate-utils (Ubuntu)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-screenshot in Ubuntu.
https://bugs.launchpad.net/bugs/1406538

Title:
  Screenshot contains selected area highlight

Status in gnome-screenshot package in Ubuntu:
  Fix Released
Status in mate-utils package in Ubuntu:
  Fix Released

Bug description:
  mate-utils_1.8.1-0+rebecca_amd64
  If i choose "select area to grab" i almost constantly get an annoying green 
overlay which is what i just used to highlight the area that i wanted to grab.
  See attached example.
  I'm using Mint MATE x64 17.1, software compositing window manager enabled, 
compiz disabled, VGA AMD radeon 6370M, drivers "xserver-xorg-video-ati" 
7.3.0-1-ubuntu3.1, kernel 3.13.0-37-generic x86_64. 
  I remember this happening since mint 13 or so.

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


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

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

** 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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1855770] Re: Unable to disable ssh component of gnome-keyring

** No longer affects: ubuntu-mate

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1855770

Title:
  Unable to disable ssh component of gnome-keyring

Status in gnome-keyring package in Ubuntu:
  New
Status in mate-session-manager package in Ubuntu:
  New

Bug description:
  Under previous versions of Ubuntu MATE (18.04 in particular), it was
  possible to disable the ssh component of gnome-keyring-daemon either
  by a) unchecking a box in Startup Applications, or b) editing
  ~/.config/autostart/gnome-keyring-ssh.desktop to include "X-MATE-
  Autostart-enabled=false". However, in 19.10 (and possibly before),
  disabling this component seems to be a no-op. This means that I can't
  easily use a gpg smartcard for ssh keys.

  To replicate:
* Disable gnome-keyring-ssh, either by unchecking the box in Startup 
Applications or by editing the .desktop file directly.
* Log out and in again.
* At a command prompt, run "echo $SSH_AUTH_SOCK".

  Expected behavior: get ssh-agent or gnupg-agent socket info.

  Actual behavior: get "/run/user/1000/keyring/ssh"

  I can see from `ps aux` that gnome-keyring-daemon is not having its
  components started separately, but rather just launched with
  `/usr/bin/gnome-keyring-daemon --daemonize --login`.

  I see on the release notes "Fixed a gnome-keyring timeout in mate-
  session-manager" -- is it possible that now gnome-keyring-daemon is
  being started incorrectly?

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


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

[Desktop-packages] [Bug 1914311] Re: Random sound and volume outputs when multiple audio hardware is enabled

** 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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

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

** 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 Desktop
Packages, which is subscribed to xserver-xorg-video-amdgpu 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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1930312] Re: USB disks and SD cards mount for wrong user

** No longer affects: ubuntu-mate

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1930312

Title:
  USB disks and SD cards mount for wrong user

Status in caja package in Ubuntu:
  Invalid
Status in gvfs package in Ubuntu:
  Confirmed
Status in udisks2 package in Ubuntu:
  Confirmed

Bug description:
  I have MATE 20.04 LTS installed on a laptop with 4 users. Plugging in SD 
cards and USB sticks works perfectly, unless there is someone else logged in on 
the machine.
  eg:
  1- user A logs in, then walks away and screen locks
  2- user B switches to the login screen and logs in as user B
  3- user B plugs in a USB stick, but it doesn't mount for user B
  4- (hidden from sight) user A gets an "authentication is required to mount... 
/dev/sdb1" error and the window is asking for admin password
  - details of this are:
  polkit.subject-pid: 102318
  polkit.caller-pid: 806
  Action: org.freedesktop.udisks2.filesystem-mount-other-seat
  Vendor: The Udisks Project

  user B has no indication on why it didn't mount. If they click on the
  USB stick in the Caja side bar, they get an "Unable to mount USB Disk
  - an operation is already pending"

  So it seems that automount is trying to show the USB stick to the
  inactive user A, totally blocking user B. (user B doesn't even get the
  chance to enter an admin password to override)

  the only solution is basically to "switch account", log in as user A and log 
them out.
  (this clearly doesn't work if user B doesn't know their password!)

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


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

[Desktop-packages] [Bug 269441] Re: Trash always full

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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

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

** 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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

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

** 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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

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

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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

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

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

-- 
You received this bug notification because you are a member of Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1803586] Re: SeaHorse hangs Panel when trying to decrypt file

Can you reproduce this issue in Ubuntu MATE 22.04?

** Changed in: mate-panel (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to seahorse in Ubuntu.
https://bugs.launchpad.net/bugs/1803586

Title:
  SeaHorse hangs Panel when trying to decrypt file

Status in mate-panel package in Ubuntu:
  Incomplete
Status in seahorse package in Ubuntu:
  New

Bug description:
  Hello ,

  Let's say that we have a file that we need to encrypt , so you go
  ahead and click Encrypt and then SeaHorse will ask you to choose which
  PGP to use , if you don't have one then you will be prompted to make
  one , let's say that we have made the PGP key and we encrypted the key
  but we didn't save the passphrase in the password manager so you will
  be prompted to put the password so you can decrypt the file and see
  the content

  But when you get prompted to put the passphrase to decrypt, then you
  decide not to put the passphrase but to cancel the process, you will
  be prompted second time to put the password automatically , I cancel
  it again and then the PC works just fine , but the whole menu is stuck
  , I can't click on Applications/Places/System , but I am able to click
  on the icons in the panel

  But it's frozen , I need to logout and login again to be able to use
  the panel again

  UPDATE : Even if not cancelling , putting the passphrase and unlocking
  the encryption will result in having the unencrypted file but still
  the panel freezes, And a logout/restart is needed to get it back
  working.

  If I'm missing any information please tell me I would update

  Thanks.

  Ubuntu Mate 18.04.1 LTS
  4.15.0-39-generic
  Traditional Panel
  Marco as Window Manager

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


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

[Desktop-packages] [Bug 1875202] Re: When Firefox titlebar is turned off windows controls are impacted.

The configuration option described no longer seems to be available. That
said, since Ubuntu MATE 22.04 the Ambiant/Radiant themes are no longer
supported and not installed by default.

** No longer affects: ubuntu-mate

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

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

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1875202

Title:
  When Firefox titlebar is turned off windows controls are impacted.

Status in firefox package in Ubuntu:
  Incomplete
Status in marco package in Ubuntu:
  Invalid
Status in ubuntu-mate-artwork package in Ubuntu:
  Incomplete

Bug description:
  When you go to Firefox --> Customize --> Uncheck Titlebar, the window
  controls in the upper left are cutoff and impacted by this change. In
  addition to the windows control any video played in the browser
  present some tearing due to the change in the pixel height.

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


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

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

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server 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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1967507] Re: Yaru Metacity theme has incorrectly scaled windows buttons on HiDPI displays

I am seeing this happen about 1 in 5 times the desktop session is
initialised. I don't think this is an issue with the Metacity theme
since it does work, most of the time.

Looks like it might be related to the Marco issue:

 - https://bugs.launchpad.net/ubuntu/+source/marco/+bug/1943289

** Changed in: yaru-theme (Ubuntu)
   Status: Triaged => Invalid

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to yaru-theme in Ubuntu.
https://bugs.launchpad.net/bugs/1967507

Title:
  Yaru Metacity theme has incorrectly scaled windows buttons on HiDPI
  displays

Status in marco package in Ubuntu:
  Confirmed
Status in ubuntu-mate-artwork package in Ubuntu:
  Invalid
Status in yaru-theme package in Ubuntu:
  Invalid

Bug description:
   HiDPI scaling is broken in Mate 1.26 produced unscaled/corrputed
  Windows buttons

  Steps to reproduce:

  Mate Tweak > Windows > HiDPI change from "auto" to "HiDPI"
  Result: A lot of flickering then everything looks fine at 200%
  Reboot & login: Window title buttons are all of a sudden unscaled again while 
the rest is as expected (see image)
  Default wallpaper is grainy at 200% // No workaround

  Workaround 1: Mate Tweak > Windows > HiDPI change from "HiDPI" to "auto" and 
back to "HiDPI"
  Workaround 2:  Change theme from Yaru Light to something else and back to 
Yaru light

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


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

[Desktop-packages] [Bug 1897988] Re: GitKraken Flatpak doesn't display Icon in task switcher

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to flatpak in Ubuntu.
https://bugs.launchpad.net/bugs/1897988

Title:
  GitKraken Flatpak doesn't display Icon in task switcher

Status in Ubuntu MATE:
  Invalid
Status in flatpak package in Ubuntu:
  Confirmed
Status in marco package in Ubuntu:
  Fix Released
Status in mate-panel package in Ubuntu:
  Invalid

Bug description:
  The GitKraken or any other flatpak doesn't display the icon on top of
  the window in the task switcher like other applications. I have
  attached a screenshot. It's the same for the bottom task bar too.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-48-generic 5.4.0-48.52
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  phillipsj   1317 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Wed Sep 30 20:33:37 2020
  InstallationDate: Installed on 2020-09-30 (0 days ago)
  InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 005: ID 138a:0017 Validity Sensors, Inc. VFS 5011 fingerprint 
sensor
   Bus 001 Device 004: ID 04f2:b52c Chicony Electronics Co., Ltd Integrated 
Camera
   Bus 001 Device 002: ID 1199:9079 Sierra Wireless, Inc. Sierra Wireless 
EM7455 Qualcomm Snapdragon X7 LTE-A
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20F6006FUS
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic 
root=UUID=5a1e3d3b-2e79-426e-9641-1447dcd64341 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-48-generic N/A
   linux-backports-modules-5.4.0-48-generic  N/A
   linux-firmware1.187.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/08/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R02ET71W (1.44 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20F6006FUS
  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:bvrR02ET71W(1.44):bd05/08/2019:svnLENOVO:pn20F6006FUS:pvrThinkPadX260:rvnLENOVO:rn20F6006FUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X260
  dmi.product.name: 20F6006FUS
  dmi.product.sku: LENOVO_MT_20F6_BU_Think_FM_ThinkPad X260
  dmi.product.version: ThinkPad X260
  dmi.sys.vendor: LENOVO

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


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

[Desktop-packages] [Bug 1967507] Re: Yaru Metacity theme has incorrectly scaled windows buttons on HiDPI displays

Typical! I've just seen this issue on an installed system using Intel
integrated graphics.

This might be a race condition with Marco, the window manager, and the
settings daemon because it didn't happen on a session restart.

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to yaru-theme in Ubuntu.
https://bugs.launchpad.net/bugs/1967507

Title:
  Yaru Metacity theme has incorrectly scaled windows buttons on HiDPI
  displays

Status in marco package in Ubuntu:
  Confirmed
Status in ubuntu-mate-artwork package in Ubuntu:
  Invalid
Status in yaru-theme package in Ubuntu:
  Triaged

Bug description:
   HiDPI scaling is broken in Mate 1.26 produced unscaled/corrputed
  Windows buttons

  Steps to reproduce:

  Mate Tweak > Windows > HiDPI change from "auto" to "HiDPI"
  Result: A lot of flickering then everything looks fine at 200%
  Reboot & login: Window title buttons are all of a sudden unscaled again while 
the rest is as expected (see image)
  Default wallpaper is grainy at 200% // No workaround

  Workaround 1: Mate Tweak > Windows > HiDPI change from "HiDPI" to "auto" and 
back to "HiDPI"
  Workaround 2:  Change theme from Yaru Light to something else and back to 
Yaru light

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


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

[Desktop-packages] [Bug 1967507] Re: Yaru Metacity theme has incorrectly scaled windows buttons on HiDPI displays

Ubuntu MATE 22.04 onwards use the Metacity theme from upstream Yaru,
which I maintain.

I have tried reproducing this issue and can only do so in one scenario:

 - In the Live Session while using the nouveau driver for NVIDIA GPUs.

@Simon Morgan: Please provide more details about your iGPU/dGPU and
drivers.

## Work around

 - Press Alt+F2
 - Run: marco --replace

Or, use MATE Tweak to set the DPI to HiDPI.

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

** Changed in: yaru-theme (Ubuntu)
   Status: New => Triaged

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to yaru-theme in Ubuntu.
https://bugs.launchpad.net/bugs/1967507

Title:
  Yaru Metacity theme has incorrectly scaled windows buttons on HiDPI
  displays

Status in marco package in Ubuntu:
  New
Status in ubuntu-mate-artwork package in Ubuntu:
  Invalid
Status in yaru-theme package in Ubuntu:
  Triaged

Bug description:
   HiDPI scaling is broken in Mate 1.26 produced unscaled/corrputed
  Windows buttons

  Steps to reproduce:

  Mate Tweak > Windows > HiDPI change from "auto" to "HiDPI"
  Result: A lot of flickering then everything looks fine at 200%
  Reboot & login: Window title buttons are all of a sudden unscaled again while 
the rest is as expected (see image)
  Default wallpaper is grainy at 200% // No workaround

  Workaround 1: Mate Tweak > Windows > HiDPI change from "HiDPI" to "auto" and 
back to "HiDPI"
  Workaround 2:  Change theme from Yaru Light to something else and back to 
Yaru light

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


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

[Desktop-packages] [Bug 1967507] Re: Yaru Metacity theme has incorrectly scaled windows buttons on HiDPI displays

** Summary changed:

- Yaru mate artwork broken HiDPI support
+ Yaru Metacity theme has incorrectly scaled windows buttons on HiDPI displays

** Also affects: yaru-theme (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to yaru-theme in Ubuntu.
https://bugs.launchpad.net/bugs/1967507

Title:
  Yaru Metacity theme has incorrectly scaled windows buttons on HiDPI
  displays

Status in ubuntu-mate-artwork package in Ubuntu:
  Invalid
Status in yaru-theme package in Ubuntu:
  Triaged

Bug description:
   HiDPI scaling is broken in Mate 1.26 produced unscaled/corrputed
  Windows buttons

  Steps to reproduce:

  Mate Tweak > Windows > HiDPI change from "auto" to "HiDPI"
  Result: A lot of flickering then everything looks fine at 200%
  Reboot & login: Window title buttons are all of a sudden unscaled again while 
the rest is as expected (see image)
  Default wallpaper is grainy at 200% // No workaround

  Workaround 1: Mate Tweak > Windows > HiDPI change from "HiDPI" to "auto" and 
back to "HiDPI"
  Workaround 2:  Change theme from Yaru Light to something else and back to 
Yaru light

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


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

[Desktop-packages] [Bug 1947420] Re: Buggish interface @ workstation panels previews when using dual portrait

2022-04-05 Thread Martin Wimpress 

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libwnck3 in Ubuntu.
https://bugs.launchpad.net/bugs/1947420

Title:
  Buggish interface @ workstation panels previews when using dual
  portrait

Status in MATE Desktop:
  New
Status in libwnck3 package in Ubuntu:
  Fix Released
Status in mate-panel package in Ubuntu:
  Invalid

Bug description:
  ...Freshly upgraded to 21.10 using the same OS that I used to open
  most of my previous video glitches ever...

  Using 2x monitor in portrait mode, the preview panel/widget(?) located
  at the bottom right side shows 2 things wrong:

  1. The "Workspace 1" preview is very elongated when compared to not only all 
of it's previous incarnations (from 14.04 to 21.10) but also has an 
inconsistent size when compared to it's neighbouring "Workspace 2". 
Expectation: both 1 and 2 should be sized identically.
  2. When hovering the mouse cursor on "Workspace 2" only it's left portion 
will highlight.
  Expectation: both monitors of "2" should highlight

  See enclosed picture.

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


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

[Desktop-packages] [Bug 1967854] Re: Gaming input devices are not supported

2022-04-05 Thread Martin Wimpress 

** Also affects: ayatana-indicator-power (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: ayatana-indicator-power (Ubuntu)
   Importance: Undecided => Medium

** Changed in: ayatana-indicator-power (Ubuntu)
 Assignee: (unassigned) => Martin Wimpress  (flexiondotorg)

** Changed in: ayatana-indicator-power (Ubuntu)
   Status: New => Triaged

** Description changed:

  If a battery-powered gaming input device (controller, joystick, etc) is
  connected MATE Power Manager detect the device as "Unknown" and Power
  Statistics show a missing icon image.
+ 
+ Ayatana Indicator Power is also missing support for gaming input devices
+ and displays a broken icon in the panel and lists the gaming input
+ devices as Unknown.

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

** Also affects: yaru-theme (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: yaru-theme (Ubuntu)
   Status: New => Fix Committed

** Changed in: yaru-theme (Ubuntu)
   Importance: Undecided => Medium

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

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

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

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

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to yaru-theme in Ubuntu.
https://bugs.launchpad.net/bugs/1967854

Title:
  Gaming input devices are not supported

Status in ayatana-indicator-power package in Ubuntu:
  Triaged
Status in mate-power-manager package in Ubuntu:
  Fix Committed
Status in ubuntu-mate-artwork package in Ubuntu:
  In Progress
Status in yaru-theme package in Ubuntu:
  Fix Committed

Bug description:
  If a battery-powered gaming input device (controller, joystick, etc)
  is connected MATE Power Manager detect the device as "Unknown" and
  Power Statistics show a missing icon image.

  Ayatana Indicator Power is also missing support for gaming input
  devices and displays a broken icon in the panel and lists the gaming
  input devices as Unknown.

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


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

[Desktop-packages] [Bug 1959995] Re: present: Crash in 'present_scmd_get_crtc' and 'present_flush' (NVIDIA 495.46)

Fixed in 22.04 via xorg-server 2:21.1.3-2ubuntu2

** Changed in: xorg-server (Ubuntu Jammy)
   Status: Fix Committed => Fix Released

** Changed in: xorg-server (Ubuntu Impish)
   Importance: Undecided => High

** Changed in: xorg-server (Ubuntu Focal)
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1959995

Title:
  present: Crash in 'present_scmd_get_crtc' and 'present_flush' (NVIDIA
  495.46)

Status in X.Org X server:
  Unknown
Status in marco package in Ubuntu:
  Fix Committed
Status in xorg-server package in Ubuntu:
  Fix Released
Status in marco source package in Focal:
  Confirmed
Status in xorg-server source package in Focal:
  Confirmed
Status in marco source package in Impish:
  Confirmed
Status in xorg-server source package in Impish:
  Confirmed
Status in marco source package in Jammy:
  Fix Committed
Status in xorg-server source package in Jammy:
  Fix Released

Bug description:
  This bug causes xserver to crash when using newer Nvidia drivers
  (NVIDIA 495.46+) with Optimus. It's apparently triggered when using
  the MATE desktop environment. It has been noticed on xorg-server-21.1,
  but it's likely affecting version 1.20.13 as well.

  It has been fixed already, but could you please backport the fix?

  Patch that fixes it is here:
  
https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/841/diffs?commit_id=22d5818851967408bb7c903cb345b7ca8766094c

  The bug report at freedesktop.org is here:
  https://gitlab.freedesktop.org/xorg/xserver/-/issues/1275

  Thank you!

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1959995/+subscriptions


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

[Desktop-packages] [Bug 1960621] Re: MATE Desktop session fails to start with NVIDIA 495 & 510 drivers

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

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

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

** Changed in: nvidia-graphics-drivers-510 (Ubuntu Focal)
   Status: Confirmed => Invalid

** Changed in: nvidia-graphics-drivers-510 (Ubuntu Impish)
   Status: Confirmed => Invalid

** Changed in: nvidia-graphics-drivers-510 (Ubuntu Jammy)
   Status: Confirmed => Invalid

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

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

** This bug has been marked a duplicate of bug 1959995
   present: Crash in 'present_scmd_get_crtc' and 'present_flush' (NVIDIA 495.46)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to metacity in Ubuntu.
https://bugs.launchpad.net/bugs/1960621

Title:
  MATE Desktop session fails to start with NVIDIA 495 & 510 drivers

Status in marco package in Ubuntu:
  Fix Released
Status in metacity package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  New
Status in marco source package in Focal:
  Invalid
Status in nvidia-graphics-drivers-510 source package in Focal:
  Invalid
Status in marco source package in Impish:
  Invalid
Status in nvidia-graphics-drivers-510 source package in Impish:
  Invalid
Status in marco source package in Jammy:
  Fix Released
Status in metacity source package in Jammy:
  Invalid
Status in nvidia-graphics-drivers-510 source package in Jammy:
  Invalid
Status in xorg-server source package in Jammy:
  New

Bug description:
  I have been using nvidia-graphics-drivers-470 for a while. In January,
  I tried the 495 drivers, but this resulted in failing to start the GUI
  when booting: the mouse cursor would appear, but then the screen would
  clear and the switch to graphics would be attempted again. This would
  repeat until restarted, so I used recovery mode to test that a) it
  still happened with that (yes) and b) to go back to the 470 drivers
  via the root terminal.

  For some reason, yesterday xscreensaver had a problem getting the
  right GLcontext. I noticed that the 510 drivers were available, so
  used Software & Updates's Additional Drivers to install those.

  Exactly the same issue as with the 495 drivers: the mouse cursor
  appears for a second, then disappears, and reappears, and.. until I
  reboot and go back to 470.

  I am using Ubuntu MATE 21.10 with a GeForce GTX 1050 Ti card.

  $ lsb_release -rd
  Description:  Ubuntu 21.10
  Release:  21.10

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


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

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

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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1959995] Re: present: Crash in 'present_scmd_get_crtc' and 'present_flush' (NVIDIA 495.46)

Now xorg-server 2:21.1.3-2ubuntu2 has migrated to the release pocket in
Jammy, macro can have Xpresent re-enabled.

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

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

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

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1959995

Title:
  present: Crash in 'present_scmd_get_crtc' and 'present_flush' (NVIDIA
  495.46)

Status in X.Org X server:
  Unknown
Status in marco package in Ubuntu:
  Fix Committed
Status in xorg-server package in Ubuntu:
  Fix Committed
Status in marco source package in Focal:
  Confirmed
Status in xorg-server source package in Focal:
  Confirmed
Status in marco source package in Impish:
  Confirmed
Status in xorg-server source package in Impish:
  Confirmed
Status in marco source package in Jammy:
  Fix Committed
Status in xorg-server source package in Jammy:
  Fix Committed

Bug description:
  This bug causes xserver to crash when using newer Nvidia drivers
  (NVIDIA 495.46+) with Optimus. It's apparently triggered when using
  the MATE desktop environment. It has been noticed on xorg-server-21.1,
  but it's likely affecting version 1.20.13 as well.

  It has been fixed already, but could you please backport the fix?

  Patch that fixes it is here:
  
https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/841/diffs?commit_id=22d5818851967408bb7c903cb345b7ca8766094c

  The bug report at freedesktop.org is here:
  https://gitlab.freedesktop.org/xorg/xserver/-/issues/1275

  Thank you!

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1959995/+subscriptions


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

[Desktop-packages] [Bug 1966556] Re: gjs-console crashed with SIGSEGV in g_main_dispatch()

2022-03-29 Thread Martin Wimpress 

** Information type changed from Private to Public

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gjs in Ubuntu.
https://bugs.launchpad.net/bugs/1966556

Title:
  gjs-console crashed with SIGSEGV in g_main_dispatch()

Status in gjs package in Ubuntu:
  Confirmed

Bug description:
  gjs-console crashed with SIGSEGV in g_main_context_dispatch()

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: gjs 1.72.0-1
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 26 13:33:01 2022
  Disassembly: => 0x0:  Não é possível acessar a memória no endereço 0x0
  ExecutablePath: /usr/bin/gjs-console
  InstallationDate: Installed on 2022-03-20 (6 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220319)
  ProcCmdline: /usr/bin/gjs /usr/share/gnome-maps/org.gnome.Maps 
--gapplication-service
  SegvAnalysis:
   Segfault happened at: 0x0:   Não é possível acessar a memória no endereço 0x0
   PC (0x) not located in a known VMA region (needed executable region)!
   source "0x0" (0x) not located in a known VMA region (needed readable 
region)!
  SegvReason:
   executing NULL VMA
   reading NULL VMA
  Signal: 11
  SourcePackage: gjs
  StacktraceTop:
   ?? ()
   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
   g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libedataserver-1.2.so.26
  Title: gjs-console crashed with SIGSEGV in g_main_context_dispatch()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

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


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

[Desktop-packages] [Bug 1949312] Re: Transmission icon Ubuntu MATE doesn´t fit overall icontheme

** Changed in: yaru-theme (Ubuntu)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to transmission in Ubuntu.
https://bugs.launchpad.net/bugs/1949312

Title:
  Transmission icon Ubuntu MATE doesn´t fit overall icontheme

Status in transmission package in Ubuntu:
  Invalid
Status in ubuntu-mate-artwork package in Ubuntu:
  Invalid
Status in yaru-theme package in Ubuntu:
  Fix Committed

Bug description:
  When using the Yaru icon theme in Ubuntu MATE and adding Transmission
  to the indicator applet, the Transmission icons does not fit the other
  icons in the indicator. (The Transmission icon has color, while the
  others have not)

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


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

[Desktop-packages] [Bug 964518] Re: remmina should get a monochrome indicator icon

** Changed in: yaru-theme (Ubuntu)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to remmina in Ubuntu.
https://bugs.launchpad.net/bugs/964518

Title:
  remmina should get a monochrome indicator icon

Status in remmina package in Ubuntu:
  Invalid
Status in yaru-theme package in Ubuntu:
  Fix Committed

Bug description:
  In Precise remmina will replace vinagre, and it will be installed by
  default. Thanks to this I think it would be nice if remmina got a
  nicer icon and a monochrome indicator icon. The currently used icon is
  very ugly. See the attached screenshot.

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


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

[Desktop-packages] [Bug 964518] Re: remmina should get a monochrome indicator icon

** Changed in: yaru-theme (Ubuntu)
   Status: Triaged => In Progress

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to remmina in Ubuntu.
https://bugs.launchpad.net/bugs/964518

Title:
  remmina should get a monochrome indicator icon

Status in remmina package in Ubuntu:
  Invalid
Status in yaru-theme package in Ubuntu:
  In Progress

Bug description:
  In Precise remmina will replace vinagre, and it will be installed by
  default. Thanks to this I think it would be nice if remmina got a
  nicer icon and a monochrome indicator icon. The currently used icon is
  very ugly. See the attached screenshot.

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


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

[Desktop-packages] [Bug 1949312] Re: Transmission icon Ubuntu MATE doesn´t fit overall icontheme

** Changed in: yaru-theme (Ubuntu)
   Status: Triaged => In Progress

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to transmission in Ubuntu.
https://bugs.launchpad.net/bugs/1949312

Title:
  Transmission icon Ubuntu MATE doesn´t fit overall icontheme

Status in transmission package in Ubuntu:
  Invalid
Status in ubuntu-mate-artwork package in Ubuntu:
  Invalid
Status in yaru-theme package in Ubuntu:
  In Progress

Bug description:
  When using the Yaru icon theme in Ubuntu MATE and adding Transmission
  to the indicator applet, the Transmission icons does not fit the other
  icons in the indicator. (The Transmission icon has color, while the
  others have not)

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


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

[Desktop-packages] [Bug 964518] Re: remmina should get a monochrome indicator icon

** Also affects: yaru-theme (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: yaru-theme (Ubuntu)
   Status: New => Triaged

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

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

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to remmina in Ubuntu.
https://bugs.launchpad.net/bugs/964518

Title:
  remmina should get a monochrome indicator icon

Status in remmina package in Ubuntu:
  Invalid
Status in yaru-theme package in Ubuntu:
  Triaged

Bug description:
  In Precise remmina will replace vinagre, and it will be installed by
  default. Thanks to this I think it would be nice if remmina got a
  nicer icon and a monochrome indicator icon. The currently used icon is
  very ugly. See the attached screenshot.

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


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

[Desktop-packages] [Bug 1949312] Re: Transmission icon Ubuntu MATE doesn´t fit overall icontheme

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

** Also affects: yaru-theme (Ubuntu)
   Importance: Undecided
   Status: New

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

** Changed in: yaru-theme (Ubuntu)
   Status: New => Triaged

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

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to transmission in Ubuntu.
https://bugs.launchpad.net/bugs/1949312

Title:
  Transmission icon Ubuntu MATE doesn´t fit overall icontheme

Status in transmission package in Ubuntu:
  Invalid
Status in ubuntu-mate-artwork package in Ubuntu:
  Invalid
Status in yaru-theme package in Ubuntu:
  Triaged

Bug description:
  When using the Yaru icon theme in Ubuntu MATE and adding Transmission
  to the indicator applet, the Transmission icons does not fit the other
  icons in the indicator. (The Transmission icon has color, while the
  others have not)

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


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

[Desktop-packages] [Bug 1959995] Re: present: Crash in 'present_scmd_get_crtc' and 'present_flush' (NVIDIA 495.46)

The i386 build failed a month ago and is preventing migration from
proposed:

- https://bugs.launchpad.net/ubuntu/+source/xorg-
server/2:21.1.3-2ubuntu1/+build/23194148

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1959995

Title:
  present: Crash in 'present_scmd_get_crtc' and 'present_flush' (NVIDIA
  495.46)

Status in X.Org X server:
  Unknown
Status in marco package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Fix Committed
Status in marco source package in Focal:
  Confirmed
Status in xorg-server source package in Focal:
  Confirmed
Status in marco source package in Impish:
  Confirmed
Status in xorg-server source package in Impish:
  Confirmed
Status in marco source package in Jammy:
  Confirmed
Status in xorg-server source package in Jammy:
  Fix Committed

Bug description:
  This bug causes xserver to crash when using newer Nvidia drivers
  (NVIDIA 495.46+) with Optimus. It's apparently triggered when using
  the MATE desktop environment. It has been noticed on xorg-server-21.1,
  but it's likely affecting version 1.20.13 as well.

  It has been fixed already, but could you please backport the fix?

  Patch that fixes it is here:
  
https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/841/diffs?commit_id=22d5818851967408bb7c903cb345b7ca8766094c

  The bug report at freedesktop.org is here:
  https://gitlab.freedesktop.org/xorg/xserver/-/issues/1275

  Thank you!

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1959995/+subscriptions


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

[Desktop-packages] [Bug 1959995] Re: present: Crash in 'present_scmd_get_crtc' and 'present_flush' (NVIDIA 495.46)