from:"Sean"

** Tags added: snap

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

Title:
  exo-open --launch WebBrowser does not work with firefox snap

Status in exo package in Ubuntu:
  New
Status in firefox package in Ubuntu:
  New

Bug description:
  With Firefox set as the default browser, `exo-open --launch
  WebBrowser` only outputs the current env vars (seen below).

  Passing in an additional parameter (`exo-open --launch WebBrowser
  google.com`) works as expected.

  SHELL=/bin/bash
  
SESSION_MANAGER=local/xubuntu:@/tmp/.ICE-unix/4173,unix/xubuntu:/tmp/.ICE-unix/4173
  WINDOWID=73400323
  QT_ACCESSIBILITY=1
  COLORTERM=truecolor
  XDG_CONFIG_DIRS=/etc/xdg/xdg-xubuntu:/etc/xdg:/etc/xdg
  XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session0
  XDG_MENU_PREFIX=xfce-
  CLUTTER_BACKEND=x11
  SSH_AUTH_SOCK=/run/user/999/keyring/ssh
  DESKTOP_SESSION=xubuntu
  XDG_SEAT=seat0
  PWD=/home/xubuntu
  LOGNAME=xubuntu
  XDG_SESSION_DESKTOP=xubuntu
  QT_QPA_PLATFORMTHEME=gtk2
  XDG_SESSION_TYPE=x11
  PANEL_GDK_CORE_DEVICE_EVENTS=0
  GPG_AGENT_INFO=/run/user/999/gnupg/S.gpg-agent:0:1
  XAUTHORITY=/home/xubuntu/.Xauthority
  XDG_GREETER_DATA_DIR=/var/lib/lightdm-data/xubuntu
  HOME=/home/xubuntu
  LANG=en_US.UTF-8
  
LS_COLORS=rs=0:di=01;34:ln=01;36:mh=00:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:mi=00:su=37;41:sg=30;43:ca=30;41:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arc=01;31:*.arj=01;31:*.taz=01;31:*.lha=01;31:*.lz4=01;31:*.lzh=01;31:*.lzma=01;31:*.tlz=01;31:*.txz=01;31:*.tzo=01;31:*.t7z=01;31:*.zip=01;31:*.z=01;31:*.dz=01;31:*.gz=01;31:*.lrz=01;31:*.lz=01;31:*.lzo=01;31:*.xz=01;31:*.zst=01;31:*.tzst=01;31:*.bz2=01;31:*.bz=01;31:*.tbz=01;31:*.tbz2=01;31:*.tz=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.war=01;31:*.ear=01;31:*.sar=01;31:*.rar=01;31:*.alz=01;31:*.ace=01;31:*.zoo=01;31:*.cpio=01;31:*.7z=01;31:*.rz=01;31:*.cab=01;31:*.wim=01;31:*.swm=01;31:*.dwm=01;31:*.esd=01;31:*.jpg=01;35:*.jpeg=01;35:*.mjpg=01;35:*.mjpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.svg=01;35:*.svgz=01;35:*.mng=01;35:*.pcx=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.m2v=01;35:*.mkv=01;35:*.webm=01;35:*.webp=01;35:*.ogm=01;35:*.mp4=01;35:*.m4v=01;35:*.mp4v=01;35:*.vob=01;35:*.qt=01;35:*.nuv=01;35:*.wmv=01;35:*.asf=01;35:*.rm=01;35:*.rmvb=01;35:*.flc=01;35:*.avi=01;35:*.fli=01;35:*.flv=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.yuv=01;35:*.cgm=01;35:*.emf=01;35:*.ogv=01;35:*.ogx=01;35:*.aac=00;36:*.au=00;36:*.flac=00;36:*.m4a=00;36:*.mid=00;36:*.midi=00;36:*.mka=00;36:*.mp3=00;36:*.mpc=00;36:*.ogg=00;36:*.ra=00;36:*.wav=00;36:*.oga=00;36:*.opus=00;36:*.spx=00;36:*.xspf=00;36:
  XDG_CURRENT_DESKTOP=XFCE
  VTE_VERSION=6790
  XDG_SEAT_PATH=/org/freedesktop/DisplayManager/Seat0
  LESSCLOSE=/usr/bin/lesspipe %s %s
  XDG_SESSION_CLASS=user
  TERM=xterm-256color
  GTK_OVERLAY_SCROLLING=0
  LESSOPEN=| /usr/bin/lesspipe %s
  USER=xubuntu
  DISPLAY=:0.0
  SHLVL=1
  XDG_VTNR=7
  XDG_SESSION_ID=c2
  XDG_RUNTIME_DIR=/run/user/999
  
XDG_DATA_DIRS=/usr/share/xubuntu:/usr/share/xfce4:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/usr/share
  
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
  GDMSESSION=xubuntu
  DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/999/bus
  _=/usr/bin/exo-open

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/exo/+bug/1967111/+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 1967109] Re: Xubuntu Docs installed at /usr/share/xubuntu-docs/index.html is not accessible with firefox snap

** Changed in: xubuntu-default-settings (Ubuntu)
   Importance: Undecided => High

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

Title:
  Xubuntu Docs installed at /usr/share/xubuntu-docs/index.html is not
  accessible with firefox snap

Status in firefox package in Ubuntu:
  Confirmed
Status in xubuntu-default-settings package in Ubuntu:
  New

Bug description:
  Xubuntu's documentation is stored at /usr/share/xubuntu-
  docs/index.html

  The firefox snap is not able to access this file.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1967109/+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 1845362] Re: gnome-font-viewer crashed with signal 5 in _XEventsQueued()

** Changed in: gnome-font-viewer (Ubuntu)
   Importance: High => Low

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

Title:
  gnome-font-viewer crashed with signal 5 in _XEventsQueued()

Status in gnome-font-viewer package in Ubuntu:
  Confirmed
Status in gnome-font-viewer package in Debian:
  New

Bug description:
  Reproducible crash (tested on Ubuntu and Xubuntu) or freezing of
  application during ISO testing of a live-session.

  Application will crash if there is an attempt to close it or scroll
  through fonts. On one occasion my laptop was rendered unusable when
  Firefox was launched while trying to report the crash to Launchpad.

  After the bug report has been sent gnome-font-viewer will freeze when
  automatically restarted. No fonts are displayed.

  Work around
  ---
  gnome-font-viewer appears to start correctly when started from the command 
line of my Ubuntu 20.04 installation. Then subsequent attempts to start the 
program succeed when started from the dock or the Application Overview.

  I have found that this work around wasn't necessary when using Xubuntu
  20.04.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: gnome-font-viewer 3.34.0-1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CasperVersion: 1.416
  CurrentDesktop: XFCE
  Date: Wed Sep 25 17:34:17 2019
  ExecutablePath: /usr/bin/gnome-font-viewer
  LiveMediaBuild: Xubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190925)
  ProcCmdline: gnome-font-viewer
  ProcEnviron:
   LANGUAGE=en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  Signal: 5
  SourcePackage: gnome-font-viewer
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () from /lib/x86_64-linux-gnu/libX11.so.6
   XPending () from /lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-font-viewer crashed with signal 5 in _XEventsQueued()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-font-viewer/+bug/1845362/+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 1967111] Re: exo-open --launch WebBrowser does not work with firefox snap

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

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

Title:
  exo-open --launch WebBrowser does not work with firefox snap

Status in exo package in Ubuntu:
  New
Status in firefox package in Ubuntu:
  New

Bug description:
  With Firefox set as the default browser, `exo-open --launch
  WebBrowser` only outputs the current env vars (seen below).

  Passing in an additional parameter (`exo-open --launch WebBrowser
  google.com`) works as expected.

  SHELL=/bin/bash
  
SESSION_MANAGER=local/xubuntu:@/tmp/.ICE-unix/4173,unix/xubuntu:/tmp/.ICE-unix/4173
  WINDOWID=73400323
  QT_ACCESSIBILITY=1
  COLORTERM=truecolor
  XDG_CONFIG_DIRS=/etc/xdg/xdg-xubuntu:/etc/xdg:/etc/xdg
  XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session0
  XDG_MENU_PREFIX=xfce-
  CLUTTER_BACKEND=x11
  SSH_AUTH_SOCK=/run/user/999/keyring/ssh
  DESKTOP_SESSION=xubuntu
  XDG_SEAT=seat0
  PWD=/home/xubuntu
  LOGNAME=xubuntu
  XDG_SESSION_DESKTOP=xubuntu
  QT_QPA_PLATFORMTHEME=gtk2
  XDG_SESSION_TYPE=x11
  PANEL_GDK_CORE_DEVICE_EVENTS=0
  GPG_AGENT_INFO=/run/user/999/gnupg/S.gpg-agent:0:1
  XAUTHORITY=/home/xubuntu/.Xauthority
  XDG_GREETER_DATA_DIR=/var/lib/lightdm-data/xubuntu
  HOME=/home/xubuntu
  LANG=en_US.UTF-8
  
LS_COLORS=rs=0:di=01;34:ln=01;36:mh=00:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:mi=00:su=37;41:sg=30;43:ca=30;41:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arc=01;31:*.arj=01;31:*.taz=01;31:*.lha=01;31:*.lz4=01;31:*.lzh=01;31:*.lzma=01;31:*.tlz=01;31:*.txz=01;31:*.tzo=01;31:*.t7z=01;31:*.zip=01;31:*.z=01;31:*.dz=01;31:*.gz=01;31:*.lrz=01;31:*.lz=01;31:*.lzo=01;31:*.xz=01;31:*.zst=01;31:*.tzst=01;31:*.bz2=01;31:*.bz=01;31:*.tbz=01;31:*.tbz2=01;31:*.tz=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.war=01;31:*.ear=01;31:*.sar=01;31:*.rar=01;31:*.alz=01;31:*.ace=01;31:*.zoo=01;31:*.cpio=01;31:*.7z=01;31:*.rz=01;31:*.cab=01;31:*.wim=01;31:*.swm=01;31:*.dwm=01;31:*.esd=01;31:*.jpg=01;35:*.jpeg=01;35:*.mjpg=01;35:*.mjpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.svg=01;35:*.svgz=01;35:*.mng=01;35:*.pcx=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.m2v=01;35:*.mkv=01;35:*.webm=01;35:*.webp=01;35:*.ogm=01;35:*.mp4=01;35:*.m4v=01;35:*.mp4v=01;35:*.vob=01;35:*.qt=01;35:*.nuv=01;35:*.wmv=01;35:*.asf=01;35:*.rm=01;35:*.rmvb=01;35:*.flc=01;35:*.avi=01;35:*.fli=01;35:*.flv=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.yuv=01;35:*.cgm=01;35:*.emf=01;35:*.ogv=01;35:*.ogx=01;35:*.aac=00;36:*.au=00;36:*.flac=00;36:*.m4a=00;36:*.mid=00;36:*.midi=00;36:*.mka=00;36:*.mp3=00;36:*.mpc=00;36:*.ogg=00;36:*.ra=00;36:*.wav=00;36:*.oga=00;36:*.opus=00;36:*.spx=00;36:*.xspf=00;36:
  XDG_CURRENT_DESKTOP=XFCE
  VTE_VERSION=6790
  XDG_SEAT_PATH=/org/freedesktop/DisplayManager/Seat0
  LESSCLOSE=/usr/bin/lesspipe %s %s
  XDG_SESSION_CLASS=user
  TERM=xterm-256color
  GTK_OVERLAY_SCROLLING=0
  LESSOPEN=| /usr/bin/lesspipe %s
  USER=xubuntu
  DISPLAY=:0.0
  SHLVL=1
  XDG_VTNR=7
  XDG_SESSION_ID=c2
  XDG_RUNTIME_DIR=/run/user/999
  
XDG_DATA_DIRS=/usr/share/xubuntu:/usr/share/xfce4:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/usr/share
  
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
  GDMSESSION=xubuntu
  DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/999/bus
  _=/usr/bin/exo-open

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/exo/+bug/1967111/+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 1967111] Re: exo-open --launch WebBrowser does not work with firefox snap

** Description changed:

  With Firefox set as the default browser, `exo-open --launch WebBrowser`
- only outputs the current env vars.
+ only outputs the current env vars (seen below).
+ 
+ Passing in an additional parameter (`exo-open --launch WebBrowser
+ google.com`) works as expected.
  
  SHELL=/bin/bash
  
SESSION_MANAGER=local/xubuntu:@/tmp/.ICE-unix/4173,unix/xubuntu:/tmp/.ICE-unix/4173
  WINDOWID=73400323
  QT_ACCESSIBILITY=1
  COLORTERM=truecolor
  XDG_CONFIG_DIRS=/etc/xdg/xdg-xubuntu:/etc/xdg:/etc/xdg
  XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session0
  XDG_MENU_PREFIX=xfce-
  CLUTTER_BACKEND=x11
  SSH_AUTH_SOCK=/run/user/999/keyring/ssh
  DESKTOP_SESSION=xubuntu
  XDG_SEAT=seat0
  PWD=/home/xubuntu
  LOGNAME=xubuntu
  XDG_SESSION_DESKTOP=xubuntu
  QT_QPA_PLATFORMTHEME=gtk2
  XDG_SESSION_TYPE=x11
  PANEL_GDK_CORE_DEVICE_EVENTS=0
  GPG_AGENT_INFO=/run/user/999/gnupg/S.gpg-agent:0:1
  XAUTHORITY=/home/xubuntu/.Xauthority
  XDG_GREETER_DATA_DIR=/var/lib/lightdm-data/xubuntu
  HOME=/home/xubuntu
  LANG=en_US.UTF-8
  
LS_COLORS=rs=0:di=01;34:ln=01;36:mh=00:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:mi=00:su=37;41:sg=30;43:ca=30;41:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arc=01;31:*.arj=01;31:*.taz=01;31:*.lha=01;31:*.lz4=01;31:*.lzh=01;31:*.lzma=01;31:*.tlz=01;31:*.txz=01;31:*.tzo=01;31:*.t7z=01;31:*.zip=01;31:*.z=01;31:*.dz=01;31:*.gz=01;31:*.lrz=01;31:*.lz=01;31:*.lzo=01;31:*.xz=01;31:*.zst=01;31:*.tzst=01;31:*.bz2=01;31:*.bz=01;31:*.tbz=01;31:*.tbz2=01;31:*.tz=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.war=01;31:*.ear=01;31:*.sar=01;31:*.rar=01;31:*.alz=01;31:*.ace=01;31:*.zoo=01;31:*.cpio=01;31:*.7z=01;31:*.rz=01;31:*.cab=01;31:*.wim=01;31:*.swm=01;31:*.dwm=01;31:*.esd=01;31:*.jpg=01;35:*.jpeg=01;35:*.mjpg=01;35:*.mjpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.svg=01;35:*.svgz=01;35:*.mng=01;35:*.pcx=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.m2v=01;35:*.mkv=01;35:*.webm=01;35:*.webp=01;35:*.ogm=01;35:*.mp4=01;35:*.m4v=01;35:*.mp4v=01;35:*.vob=01;35:*.qt=01;35:*.nuv=01;35:*.wmv=01;35:*.asf=01;35:*.rm=01;35:*.rmvb=01;35:*.flc=01;35:*.avi=01;35:*.fli=01;35:*.flv=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.yuv=01;35:*.cgm=01;35:*.emf=01;35:*.ogv=01;35:*.ogx=01;35:*.aac=00;36:*.au=00;36:*.flac=00;36:*.m4a=00;36:*.mid=00;36:*.midi=00;36:*.mka=00;36:*.mp3=00;36:*.mpc=00;36:*.ogg=00;36:*.ra=00;36:*.wav=00;36:*.oga=00;36:*.opus=00;36:*.spx=00;36:*.xspf=00;36:
  XDG_CURRENT_DESKTOP=XFCE
  VTE_VERSION=6790
  XDG_SEAT_PATH=/org/freedesktop/DisplayManager/Seat0
  LESSCLOSE=/usr/bin/lesspipe %s %s
  XDG_SESSION_CLASS=user
  TERM=xterm-256color
  GTK_OVERLAY_SCROLLING=0
  LESSOPEN=| /usr/bin/lesspipe %s
  USER=xubuntu
  DISPLAY=:0.0
  SHLVL=1
  XDG_VTNR=7
  XDG_SESSION_ID=c2
  XDG_RUNTIME_DIR=/run/user/999
  
XDG_DATA_DIRS=/usr/share/xubuntu:/usr/share/xfce4:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/usr/share
  
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
  GDMSESSION=xubuntu
  DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/999/bus
  _=/usr/bin/exo-open

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

Title:
  exo-open --launch WebBrowser does not work with firefox snap

Status in exo package in Ubuntu:
  New
Status in firefox package in Ubuntu:
  New

Bug description:
  With Firefox set as the default browser, `exo-open --launch
  WebBrowser` only outputs the current env vars (seen below).

  Passing in an additional parameter (`exo-open --launch WebBrowser
  google.com`) works as expected.

  SHELL=/bin/bash
  
SESSION_MANAGER=local/xubuntu:@/tmp/.ICE-unix/4173,unix/xubuntu:/tmp/.ICE-unix/4173
  WINDOWID=73400323
  QT_ACCESSIBILITY=1
  COLORTERM=truecolor
  XDG_CONFIG_DIRS=/etc/xdg/xdg-xubuntu:/etc/xdg:/etc/xdg
  XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session0
  XDG_MENU_PREFIX=xfce-
  CLUTTER_BACKEND=x11
  SSH_AUTH_SOCK=/run/user/999/keyring/ssh
  DESKTOP_SESSION=xubuntu
  XDG_SEAT=seat0
  PWD=/home/xubuntu
  LOGNAME=xubuntu
  XDG_SESSION_DESKTOP=xubuntu
  QT_QPA_PLATFORMTHEME=gtk2
  XDG_SESSION_TYPE=x11
  PANEL_GDK_CORE_DEVICE_EVENTS=0
  GPG_AGENT_INFO=/run/user/999/gnupg/S.gpg-agent:0:1
  XAUTHORITY=/home/xubuntu/.Xauthority
  XDG_GREETER_DATA_DIR=/var/lib/lightdm-data/xubuntu
  HOME=/home/xubuntu
  LANG=en_US.UTF-8

[Desktop-packages] [Bug 1967111] [NEW] exo-open --launch WebBrowser does not work with firefox snap

Public bug reported:

With Firefox set as the default browser, `exo-open --launch WebBrowser`
only outputs the current env vars.

SHELL=/bin/bash
SESSION_MANAGER=local/xubuntu:@/tmp/.ICE-unix/4173,unix/xubuntu:/tmp/.ICE-unix/4173
WINDOWID=73400323
QT_ACCESSIBILITY=1
COLORTERM=truecolor
XDG_CONFIG_DIRS=/etc/xdg/xdg-xubuntu:/etc/xdg:/etc/xdg
XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session0
XDG_MENU_PREFIX=xfce-
CLUTTER_BACKEND=x11
SSH_AUTH_SOCK=/run/user/999/keyring/ssh
DESKTOP_SESSION=xubuntu
XDG_SEAT=seat0
PWD=/home/xubuntu
LOGNAME=xubuntu
XDG_SESSION_DESKTOP=xubuntu
QT_QPA_PLATFORMTHEME=gtk2
XDG_SESSION_TYPE=x11
PANEL_GDK_CORE_DEVICE_EVENTS=0
GPG_AGENT_INFO=/run/user/999/gnupg/S.gpg-agent:0:1
XAUTHORITY=/home/xubuntu/.Xauthority
XDG_GREETER_DATA_DIR=/var/lib/lightdm-data/xubuntu
HOME=/home/xubuntu
LANG=en_US.UTF-8
LS_COLORS=rs=0:di=01;34:ln=01;36:mh=00:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:mi=00:su=37;41:sg=30;43:ca=30;41:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arc=01;31:*.arj=01;31:*.taz=01;31:*.lha=01;31:*.lz4=01;31:*.lzh=01;31:*.lzma=01;31:*.tlz=01;31:*.txz=01;31:*.tzo=01;31:*.t7z=01;31:*.zip=01;31:*.z=01;31:*.dz=01;31:*.gz=01;31:*.lrz=01;31:*.lz=01;31:*.lzo=01;31:*.xz=01;31:*.zst=01;31:*.tzst=01;31:*.bz2=01;31:*.bz=01;31:*.tbz=01;31:*.tbz2=01;31:*.tz=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.war=01;31:*.ear=01;31:*.sar=01;31:*.rar=01;31:*.alz=01;31:*.ace=01;31:*.zoo=01;31:*.cpio=01;31:*.7z=01;31:*.rz=01;31:*.cab=01;31:*.wim=01;31:*.swm=01;31:*.dwm=01;31:*.esd=01;31:*.jpg=01;35:*.jpeg=01;35:*.mjpg=01;35:*.mjpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.svg=01;35:*.svgz=01;35:*.mng=01;35:*.pcx=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.m2v=01;35:*.mkv=01;35:*.webm=01;35:*.webp=01;35:*.ogm=01;35:*.mp4=01;35:*.m4v=01;35:*.mp4v=01;35:*.vob=01;35:*.qt=01;35:*.nuv=01;35:*.wmv=01;35:*.asf=01;35:*.rm=01;35:*.rmvb=01;35:*.flc=01;35:*.avi=01;35:*.fli=01;35:*.flv=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.yuv=01;35:*.cgm=01;35:*.emf=01;35:*.ogv=01;35:*.ogx=01;35:*.aac=00;36:*.au=00;36:*.flac=00;36:*.m4a=00;36:*.mid=00;36:*.midi=00;36:*.mka=00;36:*.mp3=00;36:*.mpc=00;36:*.ogg=00;36:*.ra=00;36:*.wav=00;36:*.oga=00;36:*.opus=00;36:*.spx=00;36:*.xspf=00;36:
XDG_CURRENT_DESKTOP=XFCE
VTE_VERSION=6790
XDG_SEAT_PATH=/org/freedesktop/DisplayManager/Seat0
LESSCLOSE=/usr/bin/lesspipe %s %s
XDG_SESSION_CLASS=user
TERM=xterm-256color
GTK_OVERLAY_SCROLLING=0
LESSOPEN=| /usr/bin/lesspipe %s
USER=xubuntu
DISPLAY=:0.0
SHLVL=1
XDG_VTNR=7
XDG_SESSION_ID=c2
XDG_RUNTIME_DIR=/run/user/999
XDG_DATA_DIRS=/usr/share/xubuntu:/usr/share/xfce4:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/usr/share
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
GDMSESSION=xubuntu
DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/999/bus
_=/usr/bin/exo-open

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

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

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

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

Title:
  exo-open --launch WebBrowser does not work with firefox snap

Status in exo package in Ubuntu:
  New
Status in firefox package in Ubuntu:
  New

Bug description:
  With Firefox set as the default browser, `exo-open --launch
  WebBrowser` only outputs the current env vars.

  SHELL=/bin/bash
  
SESSION_MANAGER=local/xubuntu:@/tmp/.ICE-unix/4173,unix/xubuntu:/tmp/.ICE-unix/4173
  WINDOWID=73400323
  QT_ACCESSIBILITY=1
  COLORTERM=truecolor
  XDG_CONFIG_DIRS=/etc/xdg/xdg-xubuntu:/etc/xdg:/etc/xdg
  XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session0
  XDG_MENU_PREFIX=xfce-
  CLUTTER_BACKEND=x11
  SSH_AUTH_SOCK=/run/user/999/keyring/ssh
  DESKTOP_SESSION=xubuntu
  XDG_SEAT=seat0
  PWD=/home/xubuntu
  LOGNAME=xubuntu
  XDG_SESSION_DESKTOP=xubuntu
  QT_QPA_PLATFORMTHEME=gtk2
  XDG_SESSION_TYPE=x11
  PANEL_GDK_CORE_DEVICE_EVENTS=0
  GPG_AGENT_INFO=/run/user/999/gnupg/S.gpg-agent:0:1
  XAUTHORITY=/home/xubuntu/.Xauthority
  XDG_GREETER_DATA_DIR=/var/lib/lightdm-data/xubuntu
  HOME=/home/xubuntu
  LANG=en_US.UTF-8

[Desktop-packages] [Bug 1967109] [NEW] Xubuntu Docs installed at /usr/share/xubuntu-docs/index.html is not accessible with firefox snap

Public bug reported:

Xubuntu's documentation is stored at /usr/share/xubuntu-docs/index.html

The firefox snap is not able to access this file.

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

** Affects: xubuntu-default-settings (Ubuntu)
 Importance: Undecided
 Status: New

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

** Summary changed:

- Help installed at /usr/share/xubuntu-docs/index.html is not accessible with 
firefox snap
+ Xubuntu Docs installed at /usr/share/xubuntu-docs/index.html is not 
accessible with firefox snap

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

Title:
  Xubuntu Docs installed at /usr/share/xubuntu-docs/index.html is not
  accessible with firefox snap

Status in firefox package in Ubuntu:
  New
Status in xubuntu-default-settings package in Ubuntu:
  New

Bug description:
  Xubuntu's documentation is stored at /usr/share/xubuntu-
  docs/index.html

  The firefox snap is not able to access this file.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1967109/+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 1845362] Re: gnome-font-viewer crashed with signal 5 in _XEventsQueued()

** Tags added: jammy

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

Title:
  gnome-font-viewer crashed with signal 5 in _XEventsQueued()

Status in gnome-font-viewer package in Ubuntu:
  Confirmed
Status in gnome-font-viewer package in Debian:
  New

Bug description:
  Reproducible crash (tested on Ubuntu and Xubuntu) or freezing of
  application during ISO testing of a live-session.

  Application will crash if there is an attempt to close it or scroll
  through fonts. On one occasion my laptop was rendered unusable when
  Firefox was launched while trying to report the crash to Launchpad.

  After the bug report has been sent gnome-font-viewer will freeze when
  automatically restarted. No fonts are displayed.

  Work around
  ---
  gnome-font-viewer appears to start correctly when started from the command 
line of my Ubuntu 20.04 installation. Then subsequent attempts to start the 
program succeed when started from the dock or the Application Overview.

  I have found that this work around wasn't necessary when using Xubuntu
  20.04.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: gnome-font-viewer 3.34.0-1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CasperVersion: 1.416
  CurrentDesktop: XFCE
  Date: Wed Sep 25 17:34:17 2019
  ExecutablePath: /usr/bin/gnome-font-viewer
  LiveMediaBuild: Xubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190925)
  ProcCmdline: gnome-font-viewer
  ProcEnviron:
   LANGUAGE=en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  Signal: 5
  SourcePackage: gnome-font-viewer
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () from /lib/x86_64-linux-gnu/libX11.so.6
   XPending () from /lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-font-viewer crashed with signal 5 in _XEventsQueued()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-font-viewer/+bug/1845362/+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 1051952] Re: libgio's move-to-trash funciton freezes system when trashing files in kerberized, NFS mounted filesystems

2022-03-29 Thread Sean Davis

Expiring due to lack of confirmation.

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

** Changed in: thunar (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/1051952

Title:
  libgio's move-to-trash funciton freezes system when trashing files in
  kerberized, NFS mounted filesystems

Status in glib2.0 package in Ubuntu:
  Invalid
Status in nautilus package in Ubuntu:
  Invalid
Status in thunar package in Ubuntu:
  Invalid

Bug description:
  Description:Ubuntu 12.04.1 LTS
  Release:12.04

  nautilus:
Installed: 1:3.4.2-0ubuntu4
Candidate: 1:3.4.2-0ubuntu4
Version table:
   *** 1:3.4.2-0ubuntu4 0
  500 http://de.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:3.4.1-0ubuntu1 0
  500 http://de.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages

  thunar:
Installed: 1.2.3-3ubuntu2
Candidate: 1.2.3-3ubuntu2
Version table:
   *** 1.2.3-3ubuntu2 0
  500 http://de.archive.ubuntu.com/ubuntu/ precise/universe amd64 
Packages
  100 /var/lib/dpkg/status


  The setting is:

  - the user joeuser has a home directory which is mounted via NFS Version 4
  - the NFS4 mount uses Kerberos (-o sec=krb5) for authentication, which is the 
only non-default mount option
  - the user uses either Nautilus or Thunar as a graphical file manager
  - the user moves a small number of files to trash using either Thunar or 
Nautilus, after at most 20 times (independent on uptime or login time) the bug 
emerges: when the user moves file ~/foobar_21 to trash the operation takes a 
very long time (30 secs and longer)
  - during the wait we have observerd that nautious/thunar and other 
applications freeze or will not start
  -- top, as joeuser, will not start until the file ~/foobar_21 has been moved 
to trash
  -- cat ~/myfile.txt does not work until the file has been moved to trash
  -- the Thunar and Nautilus windows are not redrawn
  - ls does work and we can see that the original file ~/foobar_21 is deleted 
shortly before the end of the wait time

  The file managers Dolphin and Xfe work as expected taking well under a second 
to trash files.
  Other file managers have not been tested.

  
  FTR:
  dolphin:
Installed: 4:4.8.4-0ubuntu0.1
Candidate: 4:4.8.4-0ubuntu0.1
Version table:
   *** 4:4.8.4-0ubuntu0.1 0
  500 http://de.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   4:4.8.2-0ubuntu2 0
  500 http://de.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages

  xfe:
Installed: 1.32.4-3
Candidate: 1.32.4-3
Version table:
   *** 1.32.4-3 0
  500 http://de.archive.ubuntu.com/ubuntu/ precise/universe amd64 
Packages
  100 /var/lib/dpkg/status

  nfs-common:
Installed: 1:1.2.5-3ubuntu3
Candidate: 1:1.2.5-3ubuntu3
Version table:
   *** 1:1.2.5-3ubuntu3 0
  500 http://de.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages
  100 /var/lib/dpkg/status

  krb5-user:
Installed: 1.10+dfsg~beta1-2ubuntu0.3
Candidate: 1.10+dfsg~beta1-2ubuntu0.3
Version table:
   *** 1.10+dfsg~beta1-2ubuntu0.3 0
  500 http://de.archive.ubuntu.com/ubuntu/ precise-updates/universe 
amd64 Packages
  500 http://security.ubuntu.com/ubuntu/ precise-security/universe 
amd64 Packages
  100 /var/lib/dpkg/status
   1.10+dfsg~beta1-2 0
  500 http://de.archive.ubuntu.com/ubuntu/ precise/universe amd64 
Packages

  Linux HOSTNAME 3.2.0-30-generic #48-Ubuntu SMP Fri Aug 24 16:52:48 UTC
  2012 x86_64 x86_64 x86_64 GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1051952/+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 1778069] Re: [xfce] nautilus don't open files if set as default file manager

2022-03-29 Thread Sean Davis

Xubuntu 18.04 is no longer supported. Marking this ticket resolved for
20.04+.

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

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

Title:
  [xfce] nautilus don't open files if set as default file manager

Status in Exo:
  Fix Released
Status in exo package in Ubuntu:
  Fix Released
Status in nautilus package in Ubuntu:
  Invalid
Status in xubuntu-default-settings package in Ubuntu:
  Fix Released
Status in nautilus package in Debian:
  New

Bug description:
  If Nautilus is set as the preferred file manager with exo-preferred-
  applications, it no longer opens files. It opens only directories,
  .desktop files and executable files. Trying to open a file, be using
  Enter or with double mouse click, as a text file or a video makes
  Nautilus window blink for a instant and nothing happens. To be able to
  open the files, it's needed to choose to open with another application
  and then choose the application.

  Once Nautilus is unset as the default file manager (Thunar is chosen,
  for example), it starts to work fine again, opening files properly.

  Nautilus' Debian Sid version do not have this problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.3-0ubuntu4
  Uname: Linux 4.17.2-041702-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Jun 21 10:55:41 2018
  InstallationDate: Installed on 2017-06-13 (372 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to bionic on 2017-10-20 (244 days ago)
  usr_lib_nautilus: dropbox 2015.10.28

To manage notifications about this bug go to:
https://bugs.launchpad.net/exo/+bug/1778069/+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 1944519] Re: Xubuntu shutdown prompt is missing

2022-03-17 Thread Sean Davis

I've added plymouth back to this bug since this issue was originally a
plymouth+casper bug that was reportedly fixed:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1942987

We've had several additional reports of this issue, and I've reproduced
it on two different machines in the last couple of days with Xubuntu
Jammy. As always, the text is not displayed, but hitting the enter key
will continue the reboot process.


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

** Tags added: xubuntu

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

Title:
  Xubuntu shutdown prompt is missing

Status in Release Notes for Ubuntu:
  Fix Released
Status in casper package in Ubuntu:
  Confirmed
Status in plymouth package in Ubuntu:
  Confirmed

Bug description:
  Update: 2021-10-08 ISO issues appear with Xubuntu still; not with
  Ubuntu-MATE

  Live session shutdown prompt is missing - system reboots at once

  Testing Ubuntu Mate Impish ISO 22.09,2021

  Clicked restart now button after install and no shutdown prompt
  appeared - the system rebooted at once and I could then login as
  normal.

  Please see bug #1942987
  https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1942987 for
  history.

  I am filing this under plymouth - not sure if that is correct package.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: plymouth 0.9.5git20210406-0ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE
  Date: Wed Sep 22 06:59:59 2021
  DefaultPlymouth: 
/usr/share/plymouth/themes/ubuntu-mate-logo/ubuntu-mate-logo.plymouth
  InstallationDate: Installed on 2021-09-22 (0 days ago)
  InstallationMedia: Ubuntu-MATE 21.10 "Impish Indri" - Beta amd64 (20210922)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 046d:c535 Logitech, Inc. Dell Wireless Mouse WM123
   Bus 001 Device 004: ID 04f2:0402 Chicony Electronics Co., Ltd Genius 
LuxeMate i200 Keyboard
   Bus 001 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. OptiPlex 7040
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic 
root=UUID=731e4ccb-cceb-48e4-bbda-f97dbe3b6f40 ro quiet splash vt.handoff=7
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic 
root=UUID=731e4ccb-cceb-48e4-bbda-f97dbe3b6f40 ro quiet splash vt.handoff=7
  SourcePackage: plymouth
  TextPlymouth: 
/usr/share/plymouth/themes/ubuntu-mate-text/ubuntu-mate-text.plymouth
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/23/2020
  dmi.bios.release: 1.18
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.18.1
  dmi.board.name: 0Y7WYT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.18.1:bd12/23/2020:br1.18:svnDellInc.:pnOptiPlex7040:pvr:sku06B9:rvnDellInc.:rn0Y7WYT:rvrA00:cvnDellInc.:ct3:cvr:
  dmi.product.family: OptiPlex
  dmi.product.name: OptiPlex 7040
  dmi.product.sku: 06B9
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1944519/+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 1805197] Re: cannot switching keyboard layout with xfce4-keyboard-settings

2022-03-10 Thread Sean Davis

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

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

Title:
  cannot switching keyboard layout with xfce4-keyboard-settings

Status in Xfce4 Settings:
  Confirmed
Status in libxklavier package in Ubuntu:
  Confirmed
Status in xfce4-settings package in Ubuntu:
  Triaged

Bug description:
  This is on xubuntu 18.04:

  With xfce4-keyboard-settings I have loaded the keyboard layouts "English 
(US)" and "German".
  Both are listed in the "Keybord layout" table.
  When I change the order with [key up] or [key down] nothing happens, I still 
have the old keyboard layout active.
  To switch the layout I have to DELETE the other one!
  This was not the case with xubuntu 16.04: just changing the order was 
sufficent there.

To manage notifications about this bug go to:
https://bugs.launchpad.net/xfce4-settings/+bug/1805197/+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 1322275] Re: lightdm sessions started by dm-tool lock (or a session locker) never get closed

2022-03-07 Thread Sean Davis

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

** Changed in: lightdm-gtk-greeter (Ubuntu)
   Status: Incomplete => Invalid

** Changed in: upstart (Ubuntu)
   Status: Incomplete => 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/1322275

Title:
  lightdm sessions started by dm-tool lock (or a session locker) never
  get closed

Status in Light Display Manager:
  New
Status in lightdm package in Ubuntu:
  Invalid
Status in lightdm-gtk-greeter package in Ubuntu:
  Invalid
Status in upstart package in Ubuntu:
  Invalid

Bug description:
  dm-tool lock starts a new lightdm greeter (for unlocking) and a new
  logind session. After unlocking the greeter disappears, but the logind
  session never closes. loginctl session status c24 reports something
  like:

  c24 - lightdm (103)
 Since: Thu 2014-05-22 18:38:27 CEST; 30min ago
Leader: 7872
  Seat: seat0; vc8
   Display: :1
   Service: lightdm-greeter; type x11; class greeter
 State: closing
CGroup: systemd:/user/103.user/c24.session
└─7907 init --user --startup-event indicator-services-start

  This results in an accumulation of stale lightdm sessions after using
  e.g. a session locker for a while.

  I get this issue on a freshly installed and fully updated Xubuntu
  14.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1322275/+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 1874178] Re: Unlocking existing session needs two attempts after selecting Switch User

2021-09-23 Thread Sean Davis

** Package changed: lightdm (Ubuntu) => xfce4-screensaver (Ubuntu)

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

Title:
  Unlocking existing session needs two attempts after selecting Switch
  User

Status in xfce4-screensaver package in Ubuntu:
  Confirmed

Bug description:
  This has been occurring during the Xubuntu post-install test. It's not
  the same as Bug #1776475, as it's not necessary to have logged in as
  another user (or even for another user to exist) for the problem to
  happen.

  My sequence of actions is:

  *Create new user.
  *Open a program (usually Thunar or Terminal).
  *Lock session.
  *Click on "Switch User". <-- This is all that's necessary to trigger it.
  *Enter password to unlock my own session.
  *Then there's a delay and screen goes black, then the unlock prompt appears 
again.
  *The second time, my session unlocks.

  This particular report is from a QEMU/KVM vm, but it's also been
  happening on a bare-metal install.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: lightdm 1.30.0-0ubuntu3.1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Apr 22 15:30:29 2020
  InstallationDate: Installed on 2020-04-22 (0 days ago)
  InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200421)
  ProcEnviron:
   LANGUAGE=en_NZ:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_NZ.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xfce4-screensaver/+bug/1874178/+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 1921920] Re: Xubuntu 20.04.2.1 cannot log out, shut down or restart from a temporary guest session.

2021-07-15 Thread Sean Davis

Possibly related: https://bugs.launchpad.net/ubuntu/+source/xubuntu-
meta/+bug/1909393

** Also affects: lightdm (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/1921920

Title:
  Xubuntu 20.04.2.1 cannot log out, shut down or restart from a
  temporary guest session.

Status in lightdm package in Ubuntu:
  New
Status in xubuntu-meta package in Ubuntu:
  New

Bug description:
  I cannot log out, shut down or restart from an activated temporary guest 
session. Only via tty or REISUB. Clicking anything in the 
logout/restart/shutdown GUI dialog window will only result in the message "An 
error occurred while logging out"
  GDBus.Error:org.freedesktop.Dbus.Error.InvalidArgs: Type ofmessage, "(yb)", 
does not match expected type "(b)"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1921920/+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 1930695] [NEW] Noto Fonts (without color emoji) break non-color emoji in QT applications

2021-06-03 Thread Sean Davis

Public bug reported:

Originally reported on: https://bugs.launchpad.net/ubuntu/+source
/xubuntu-meta/+bug/1766976

> In a default fresh install of XUbuntu 20.04, Qt based applications, eg
Featherpad and Qt-Creator, will not display certain unicode characers,
eg, U+1F9C0 CHEESE WEDGE 燎 (a white rectangle is shown instead). Non Qt
apps, eg geany or gnome-terminal, show the cheese successfully. If Noto
fonts are manually uninstalled, then the problem is fixed; Featherpad
does display the cheese correctly. Conjecture: the Noto fonts were
providing a colour version of the cheese wedge; the Qt apps could not
display that but can display grey versions

Xubuntu does not include fonts-noto-color-emoji, but instead includes
fonts-symbola. While the Noto fonts are installed, Featherpad displays a
white rectangle instead of the B cheese wedge. Uninstalling the Noto
fonts leads Featherpad to display the correct emoji. I also tried
replacing fonts-symbola with fonts-noto-color-emoji, but to no avail.

** Affects: fonts-noto (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Noto Fonts (without color emoji) break non-color emoji in QT
  applications

Status in fonts-noto package in Ubuntu:
  New

Bug description:
  Originally reported on: https://bugs.launchpad.net/ubuntu/+source
  /xubuntu-meta/+bug/1766976

  > In a default fresh install of XUbuntu 20.04, Qt based applications,
  eg Featherpad and Qt-Creator, will not display certain unicode
  characers, eg, U+1F9C0 CHEESE WEDGE 燎 (a white rectangle is shown
  instead). Non Qt apps, eg geany or gnome-terminal, show the cheese
  successfully. If Noto fonts are manually uninstalled, then the problem
  is fixed; Featherpad does display the cheese correctly. Conjecture:
  the Noto fonts were providing a colour version of the cheese wedge;
  the Qt apps could not display that but can display grey versions

  Xubuntu does not include fonts-noto-color-emoji, but instead includes
  fonts-symbola. While the Noto fonts are installed, Featherpad displays
  a white rectangle instead of the B cheese wedge. Uninstalling the
  Noto fonts leads Featherpad to display the correct emoji. I also tried
  replacing fonts-symbola with fonts-noto-color-emoji, but to no avail.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fonts-noto/+bug/1930695/+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 977069] Re: After installaing and removing lightdm-gtk-greeter lightdm is left in a not working state

2021-06-02 Thread Sean Davis

** Changed in: lightdm-gtk-greeter (Ubuntu)
   Status: Incomplete => Invalid

** Changed in: unity-greeter (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  After installaing and removing lightdm-gtk-greeter lightdm is left in
  a not working state

Status in lightdm-gtk-greeter package in Ubuntu:
  Invalid
Status in unity-greeter package in Ubuntu:
  Invalid

Bug description:
  expected behaviour:
  unity greeter is used again

  actual behaviour
  lightdm wont start, falling back to console

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: lightdm 1.2.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14
  Uname: Linux 3.2.0-22-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0-0ubuntu4
  Architecture: amd64
  Date: Mon Apr  9 10:56:19 2012
  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-gtk-greeter/+bug/977069/+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 1312526] Re: Greeter uses previous session even if it is not available

2021-05-30 Thread Sean Davis

Is this still a problem with either greeter?

** Changed in: lightdm-gtk-greeter (Ubuntu)
   Status: Confirmed => Incomplete

** Changed in: unity-greeter (Ubuntu)
   Status: Triaged => Incomplete

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

Title:
  Greeter uses previous session even if it is not available

Status in lightdm-gtk-greeter package in Ubuntu:
  Incomplete
Status in unity-greeter package in Ubuntu:
  Incomplete

Bug description:
  I install using preseed files, and clobber a bit of /etc to configure
  ubuntu to be suitable for users to login with network credentials.  I
  use pam to make a home directory when users login with network
  credentials.

  On first boot, logging into the VTs works fine but I cannot log into
  the lightdm dislpay manager.  If I type my username and password
  right, I get a "Failed to start session" message and get bounced back
  to the start of the login process.

  If, however, I click one of the session types, e.g. 'ubuntu' or
  'fluxbox', then I can log in.  (I've tried uninstalling fluxbox, this
  doesn't seem to help).  At which point I can login, which I believe
  works until I reboot the machine.  (I will test this shortly).

  If I install the lightdm-gtk-greeter package then I do not encounter
  this bug.  Instead, I am automatically logged into the alphabetically
  first session type (at least, if I've got fluxbox available vs. either
  ubuntu or xfce, that seems to be what I get, if only ubuntu is install
  I get an ubunut session by default so I assume the preference is
  alphabetical).

  It does not seem to matter if I specify a 
  user-session=something
  (I have also tried not setting user-session at all)

  in lightdm.conf (well, I haven't tried it with the gtk-greeter, but it
  doesn't matter with the unity greeter).

  I've tried all of the other lightdm-greeter packages, and lightdm-
  greeter-gtk is the only one that does not suffer from this bug.

  the most relvant message in the logs I can find is:

  DEBUG: Seat: Failed to find session configuration true
  Seat: Can't find session 'true'

  What I would expect to happen is to get some default session; getting
  the alphabetically first session is kind-of/sort-of reasonable.  Total
  failure is not.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lightdm 1.10.0-0ubuntu3
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Apr 24 22:08:08 2014
  LightdmConfig:
   [SeatDefaults]
   user-session=true
   greeter-hide-users=true
   greeter-allow-guest=false
   session-setup-script=/bin/sh -l /etc/profile
  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-gtk-greeter/+bug/1312526/+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 1322275] Re: lightdm sessions started by dm-tool lock (or a session locker) never get closed

2021-05-30 Thread Sean Davis

Last updated in 2016. Is this still an issue with these greeters?

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

** Changed in: lightdm-gtk-greeter (Ubuntu)
   Status: Confirmed => Incomplete

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

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

Title:
  lightdm sessions started by dm-tool lock (or a session locker) never
  get closed

Status in Light Display Manager:
  New
Status in lightdm package in Ubuntu:
  Incomplete
Status in lightdm-gtk-greeter package in Ubuntu:
  Incomplete
Status in upstart package in Ubuntu:
  Incomplete

Bug description:
  dm-tool lock starts a new lightdm greeter (for unlocking) and a new
  logind session. After unlocking the greeter disappears, but the logind
  session never closes. loginctl session status c24 reports something
  like:

  c24 - lightdm (103)
 Since: Thu 2014-05-22 18:38:27 CEST; 30min ago
Leader: 7872
  Seat: seat0; vc8
   Display: :1
   Service: lightdm-greeter; type x11; class greeter
 State: closing
CGroup: systemd:/user/103.user/c24.session
└─7907 init --user --startup-event indicator-services-start

  This results in an accumulation of stale lightdm sessions after using
  e.g. a session locker for a while.

  I get this issue on a freshly installed and fully updated Xubuntu
  14.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1322275/+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 977069] Re: After installaing and removing lightdm-gtk-greeter lightdm is left in a not working state

2021-05-30 Thread Sean Davis

Is this still an issue with either greeter?

** Changed in: lightdm-gtk-greeter (Ubuntu)
   Status: Confirmed => Incomplete

** Changed in: unity-greeter (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  After installaing and removing lightdm-gtk-greeter lightdm is left in
  a not working state

Status in lightdm-gtk-greeter package in Ubuntu:
  Incomplete
Status in unity-greeter package in Ubuntu:
  Incomplete

Bug description:
  expected behaviour:
  unity greeter is used again

  actual behaviour
  lightdm wont start, falling back to console

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: lightdm 1.2.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14
  Uname: Linux 3.2.0-22-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0-0ubuntu4
  Architecture: amd64
  Date: Mon Apr  9 10:56:19 2012
  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-gtk-greeter/+bug/977069/+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 1873895] Re: Regression: block staircase display with side-by-side monitors of different pixel widths

2021-04-06 Thread Sean Davis

The problem exists with the AMD graphics drivers and using Xpresent.
Window managers can work around it by not using Xpresent, but there's
also a kernel fix available.

https://gitlab.freedesktop.org/xorg/driver/xf86-video-amdgpu/-/issues/10
https://gitlab.freedesktop.org/xorg/driver/xf86-video-amdgpu/-/merge_requests/52

https://gitlab.xfce.org/xfce/xfwm4/-/commit/7c00911a556c27c57c9f719c12cfda967016dc28

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

Title:
  Regression: block staircase display with side-by-side monitors of
  different pixel widths

Status in Linux:
  Unknown
Status in libxcb package in Ubuntu:
  Incomplete
Status in xfwm4 package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Incomplete
Status in libxcb source package in Focal:
  Incomplete
Status in xfwm4 source package in Focal:
  In Progress
Status in xserver-xorg-video-amdgpu source package in Focal:
  Incomplete
Status in libxcb source package in Groovy:
  Incomplete
Status in xfwm4 source package in Groovy:
  Fix Released
Status in xserver-xorg-video-amdgpu source package in Groovy:
  Incomplete

Bug description:
  [Impact]

   * This issue affects AMD graphics on Xfwm4 4.14.1.

   * Windows are displayed staggered with a multi-window layout

  [Test Plan]

   * Use AMD graphics drivers

   * Connect a second display at a different resolution

   * Open multiple windows

   * While the issue is present, the windows and desktop will appeared
  staggered

   * Once fixed, they display normally.

  [Where problems could occur]

   * Regression potential should be relatively low, as the release
  between 4.14.1 and 4.14.5 are bug releases.

   * With window managers, some changes could lead to different behavior
  and other broken displays. Non-AMD graphics users should also test for
  regressions.

  [Other Info]
   
   * Please see the Xfwm4 release notes for changes between 4.14.1 and 4.14.5: 
https://gitlab.xfce.org/xfce/xfwm4/-/blob/xfce-4.14/NEWS#L7-44

  [Original Report]

  Update based on further research.

  This only happens when the secondary external display is operating at
  a different pixel width to the internal. In this case eDP is 1920x1080
  whereas the external HDMI-A-0 is natively 1680x1050.

  It is caused by xfwm4's recent switch from using glx to xpresent for
  AMD GPUs.

  The underlying bug is in the AMD driver.

  I was able to reproduce on an external 1920x1200 display only when it
  was set to a non-native 1680x1050 resolution.

  ---
  Two identical Lenovo E495 laptops with 20.04 installed. The problem occurred 
initially on the laptop that is having package upgrades applied regularly.

  With dual monitors and the external monitor placed left or right the
  display has a blocked staircase effect shown in the attached
  photograph, and seems related to

  https://gitlab.freedesktop.org/xorg/driver/xf86-video-
  amdgpu/-/issues/10

  More detailed investigation suggests it only happens when the X
  coordinate of the two monitors is different. The symptom looks like an
  off-by-one error because it appears as if the display is divided into,
  say, 10 rows and 15 columns but the first row has 16 'columns' worth
  of blocks on it and so wraps to the beginning of the 2nd row, and so
  on.

  On the laptop without package upgrades being applied this didn't
  happen. So I upgraded it (314 packages) and restarted and it too sees
  the same problem.

  I suspected libxcomposite1 and downgraded it to 1:0.4.5-0ubuntu1 but
  that didn't solve it.

  I now suspect libxcb but so far haven't been able to prove it.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 
00 [VGA controller])
     Subsystem: Lenovo ThinkPad E595 [17aa:5124]
  InstallationDate: Installed on 2020-04-08 (11 days ago)
  InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200408)
  MachineType: LENOVO 20NECTO1WW
  Package: xserver-xorg-video-amdgpu 19.1.0-1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic 
root=/dev/mapper/ELLOE000-rootfs ro acpi_osi=! "acpi_osi=Windows 2016" quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Tags:  focal ubuntu ubuntu
  Uname: Linux 5.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sudo users
  _MarkForUpload: True
  dmi.bios.date: 12/23/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version:

[Desktop-packages] [Bug 1873895] Re: Regression: block staircase display with side-by-side monitors of different pixel widths

2021-04-06 Thread Sean Davis

Attaching debdiff for xfwm4_4.14.5-1ubuntu0.20.04.1, also uploaded to
the Xubuntu SRU Staging PPA:

https://launchpad.net/~xubuntu-dev/+archive/ubuntu/sru-staging

** Patch added: "xfwm4 debdiff"
   
https://bugs.launchpad.net/ubuntu/focal/+source/xfwm4/+bug/1873895/+attachment/5484646/+files/xfwm4_4.14.1-0ubuntu1_to_xfwm4_4.14.5-1ubuntu0.20.04.1.debdiff

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

** Changed in: xfwm4 (Ubuntu Focal)
 Assignee: (unassigned) => Sean Davis (bluesabre)

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

Title:
  Regression: block staircase display with side-by-side monitors of
  different pixel widths

Status in Linux:
  Unknown
Status in libxcb package in Ubuntu:
  Confirmed
Status in xfwm4 package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Confirmed
Status in libxcb source package in Focal:
  New
Status in xfwm4 source package in Focal:
  In Progress
Status in xserver-xorg-video-amdgpu source package in Focal:
  New
Status in libxcb source package in Groovy:
  New
Status in xfwm4 source package in Groovy:
  Fix Released
Status in xserver-xorg-video-amdgpu source package in Groovy:
  New

Bug description:
  [Impact]

   * This issue affects AMD graphics on Xfwm4 4.14.1.

   * Windows are displayed staggered with a multi-window layout

  [Test Plan]

   * Use AMD graphics drivers

   * Connect a second display at a different resolution

   * Open multiple windows

   * While the issue is present, the windows and desktop will appeared
  staggered

   * Once fixed, they display normally.

  [Where problems could occur]

   * Regression potential should be relatively low, as the release
  between 4.14.1 and 4.14.5 are bug releases.

   * With window managers, some changes could lead to different behavior
  and other broken displays. Non-AMD graphics users should also test for
  regressions.

  [Other Info]
   
   * Please see the Xfwm4 release notes for changes between 4.14.1 and 4.14.5: 
https://gitlab.xfce.org/xfce/xfwm4/-/blob/xfce-4.14/NEWS#L7-44

  [Original Report]

  Update based on further research.

  This only happens when the secondary external display is operating at
  a different pixel width to the internal. In this case eDP is 1920x1080
  whereas the external HDMI-A-0 is natively 1680x1050.

  It is caused by xfwm4's recent switch from using glx to xpresent for
  AMD GPUs.

  The underlying bug is in the AMD driver.

  I was able to reproduce on an external 1920x1200 display only when it
  was set to a non-native 1680x1050 resolution.

  ---
  Two identical Lenovo E495 laptops with 20.04 installed. The problem occurred 
initially on the laptop that is having package upgrades applied regularly.

  With dual monitors and the external monitor placed left or right the
  display has a blocked staircase effect shown in the attached
  photograph, and seems related to

  https://gitlab.freedesktop.org/xorg/driver/xf86-video-
  amdgpu/-/issues/10

  More detailed investigation suggests it only happens when the X
  coordinate of the two monitors is different. The symptom looks like an
  off-by-one error because it appears as if the display is divided into,
  say, 10 rows and 15 columns but the first row has 16 'columns' worth
  of blocks on it and so wraps to the beginning of the 2nd row, and so
  on.

  On the laptop without package upgrades being applied this didn't
  happen. So I upgraded it (314 packages) and restarted and it too sees
  the same problem.

  I suspected libxcomposite1 and downgraded it to 1:0.4.5-0ubuntu1 but
  that didn't solve it.

  I now suspect libxcb but so far haven't been able to prove it.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 
00 [VGA controller])
     Subsystem: Lenovo ThinkPad E595 [17aa:5124]
  InstallationDate: Installed on 2020-04-08 (11 days ago)
  InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200408)
  MachineType: LENOVO 20NECTO1WW
  Package: xserver-xorg-video-amdgpu 19.1.0-1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic 
root=/dev/mapper/ELLOE000-rootfs ro acpi_osi=! "acpi_osi=Windows 2016" quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Tags:  focal ubuntu ubuntu
  Uname: Linux 5.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sa

[Desktop-packages] [Bug 1873895] Re: Regression: block staircase display with side-by-side monitors of different pixel widths

2021-04-06 Thread Sean Davis

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

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

Title:
  Regression: block staircase display with side-by-side monitors of
  different pixel widths

Status in Linux:
  Unknown
Status in libxcb package in Ubuntu:
  Confirmed
Status in xfwm4 package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Confirmed
Status in libxcb source package in Focal:
  New
Status in xfwm4 source package in Focal:
  Confirmed
Status in xserver-xorg-video-amdgpu source package in Focal:
  New
Status in libxcb source package in Groovy:
  New
Status in xfwm4 source package in Groovy:
  Fix Released
Status in xserver-xorg-video-amdgpu source package in Groovy:
  New

Bug description:
  [Impact]

   * This issue affects AMD graphics on Xfwm4 4.14.1.

   * Windows are displayed staggered with a multi-window layout

  [Test Plan]

   * Use AMD graphics drivers

   * Connect a second display at a different resolution

   * Open multiple windows

   * While the issue is present, the windows and desktop will appeared
  staggered

   * Once fixed, they display normally.

  [Where problems could occur]

   * Regression potential should be relatively low, as the release
  between 4.14.1 and 4.14.5 are bug releases.

   * With window managers, some changes could lead to different behavior
  and other broken displays. Non-AMD graphics users should also test for
  regressions.

  [Other Info]
   
   * Please see the Xfwm4 release notes for changes between 4.14.1 and 4.14.5: 
https://gitlab.xfce.org/xfce/xfwm4/-/blob/xfce-4.14/NEWS#L7-44

  [Original Report]

  Update based on further research.

  This only happens when the secondary external display is operating at
  a different pixel width to the internal. In this case eDP is 1920x1080
  whereas the external HDMI-A-0 is natively 1680x1050.

  It is caused by xfwm4's recent switch from using glx to xpresent for
  AMD GPUs.

  The underlying bug is in the AMD driver.

  I was able to reproduce on an external 1920x1200 display only when it
  was set to a non-native 1680x1050 resolution.

  ---
  Two identical Lenovo E495 laptops with 20.04 installed. The problem occurred 
initially on the laptop that is having package upgrades applied regularly.

  With dual monitors and the external monitor placed left or right the
  display has a blocked staircase effect shown in the attached
  photograph, and seems related to

  https://gitlab.freedesktop.org/xorg/driver/xf86-video-
  amdgpu/-/issues/10

  More detailed investigation suggests it only happens when the X
  coordinate of the two monitors is different. The symptom looks like an
  off-by-one error because it appears as if the display is divided into,
  say, 10 rows and 15 columns but the first row has 16 'columns' worth
  of blocks on it and so wraps to the beginning of the 2nd row, and so
  on.

  On the laptop without package upgrades being applied this didn't
  happen. So I upgraded it (314 packages) and restarted and it too sees
  the same problem.

  I suspected libxcomposite1 and downgraded it to 1:0.4.5-0ubuntu1 but
  that didn't solve it.

  I now suspect libxcb but so far haven't been able to prove it.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 
00 [VGA controller])
     Subsystem: Lenovo ThinkPad E595 [17aa:5124]
  InstallationDate: Installed on 2020-04-08 (11 days ago)
  InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200408)
  MachineType: LENOVO 20NECTO1WW
  Package: xserver-xorg-video-amdgpu 19.1.0-1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic 
root=/dev/mapper/ELLOE000-rootfs ro acpi_osi=! "acpi_osi=Windows 2016" quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Tags:  focal ubuntu ubuntu
  Uname: Linux 5.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sudo users
  _MarkForUpload: True
  dmi.bios.date: 12/23/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R11ET32W (1.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20NECTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias:

[Desktop-packages] [Bug 1873895] Re: Regression: block staircase display with side-by-side monitors of different pixel widths

2021-04-05 Thread Sean Davis

** Description changed:

+ [Impact]
+ 
+  * This issue affects AMD graphics on Xfwm4 4.14.1.
+ 
+  * Windows are displayed staggered with a multi-window layout
+ 
+ [Test Plan]
+ 
+  * Use AMD graphics drivers
+ 
+  * Connect a second display at a different resolution
+ 
+  * Open multiple windows
+ 
+  * While the issue is present, the windows and desktop will appeared
+ staggered
+ 
+  * Once fixed, they display normally.
+ 
+ [Where problems could occur]
+ 
+  * Regression potential should be relatively low, as the release between
+ 4.14.1 and 4.14.5 are bug releases.
+ 
+  * With window managers, some changes could lead to different behavior
+ and other broken displays. Non-AMD graphics users should also test for
+ regressions.
+ 
+ [Other Info]
+  
+  * Please see the Xfwm4 release notes for changes between 4.14.1 and 4.14.5: 
https://gitlab.xfce.org/xfce/xfwm4/-/blob/xfce-4.14/NEWS#L7-44
+ 
+ [Original Report]
+ 
  Update based on further research.
  
  This only happens when the secondary external display is operating at a
  different pixel width to the internal. In this case eDP is 1920x1080
  whereas the external HDMI-A-0 is natively 1680x1050.
  
  It is caused by xfwm4's recent switch from using glx to xpresent for AMD
  GPUs.
  
  The underlying bug is in the AMD driver.
  
  I was able to reproduce on an external 1920x1200 display only when it
  was set to a non-native 1680x1050 resolution.
  
  ---
  Two identical Lenovo E495 laptops with 20.04 installed. The problem occurred 
initially on the laptop that is having package upgrades applied regularly.
  
  With dual monitors and the external monitor placed left or right the
  display has a blocked staircase effect shown in the attached photograph,
  and seems related to
  
  https://gitlab.freedesktop.org/xorg/driver/xf86-video-amdgpu/-/issues/10
  
  More detailed investigation suggests it only happens when the X
  coordinate of the two monitors is different. The symptom looks like an
  off-by-one error because it appears as if the display is divided into,
  say, 10 rows and 15 columns but the first row has 16 'columns' worth of
  blocks on it and so wraps to the beginning of the 2nd row, and so on.
  
  On the laptop without package upgrades being applied this didn't happen.
  So I upgraded it (314 packages) and restarted and it too sees the same
  problem.
  
  I suspected libxcomposite1 and downgraded it to 1:0.4.5-0ubuntu1 but
  that didn't solve it.
  
  I now suspect libxcb but so far haven't been able to prove it.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 
00 [VGA controller])
     Subsystem: Lenovo ThinkPad E595 [17aa:5124]
  InstallationDate: Installed on 2020-04-08 (11 days ago)
  InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200408)
  MachineType: LENOVO 20NECTO1WW
  Package: xserver-xorg-video-amdgpu 19.1.0-1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic 
root=/dev/mapper/ELLOE000-rootfs ro acpi_osi=! "acpi_osi=Windows 2016" quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Tags:  focal ubuntu ubuntu
  Uname: Linux 5.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sudo users
  _MarkForUpload: True
  dmi.bios.date: 12/23/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R11ET32W (1.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20NECTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR11ET32W(1.12):bd12/23/2019:svnLENOVO:pn20NECTO1WW:pvrThinkPadE495:rvnLENOVO:rn20NECTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad E495
  dmi.product.name: 20NECTO1WW
  dmi.product.sku: LENOVO_MT_20NE_BU_Think_FM_ThinkPad E495
  dmi.product.version: ThinkPad E495
  dmi.sys.vendor: LENOVO
  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 N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  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

-- 
You received this bug notification

[Desktop-packages] [Bug 1054923] Re: Window raises on click even if set not to raise in window manager settings (in Xfce)

2021-04-04 Thread Sean Davis

Upstream xfwm4 marked WONTFIX.

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

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

Title:
  Window raises on click even if set not to raise in window manager
  settings (in Xfce)

Status in Xfwm4:
  Confirmed
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in xfwm4 package in Ubuntu:
  Won't Fix

Bug description:
  Steps to reproduce: 
  1) Disable "Raise window when clicking inside application window" in Window 
Manager (xfwm?) settings in Xfce (in Focus tab).
  2) Move another window to partly overlap chromium browser window
  3) click on the chromium browser window below title bar
  Result: the window raises
  Expected result: window should not raise

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: chromium-browser 20.0.1132.47~r144678-0ubuntu0.12.04.1
  ProcVersionSignature: Ubuntu 3.2.0-31.50-generic 3.2.28
  Uname: Linux 3.2.0-31-generic i686
  ApportVersion: 2.0.1-0ubuntu13
  Architecture: i386
  Date: Sun Sep 23 13:03:55 2012
  Desktop-Session:
   DESKTOP_SESSION = xubuntu
   XDG_CONFIG_DIRS = /etc/xdg/xdg-xubuntu:/etc/xdg:/etc/xdg
   XDG_DATA_DIRS = /usr/share/xubuntu:/usr/local/share/:/usr/share/:/usr/share
  Env:
   MOZ_PLUGIN_PATH = None
   LD_LIBRARY_PATH = None
  InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Beta i386 (20110901)
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to precise on 2012-09-22 (0 days ago)
  chromium-default: CHROMIUM_FLAGS=""

To manage notifications about this bug go to:
https://bugs.launchpad.net/xfwm4/+bug/1054923/+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 1873895] Re: Regression: block staircase display with side-by-side monitors of different pixel widths

2021-03-31 Thread Sean Davis

Fixed in Xfwm4 4.14.2

** Also affects: libxcb (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: xfwm4 (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: xserver-xorg-video-amdgpu (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: libxcb (Ubuntu Groovy)
   Importance: Undecided
   Status: New

** Also affects: xfwm4 (Ubuntu Groovy)
   Importance: Undecided
   Status: New

** Also affects: xserver-xorg-video-amdgpu (Ubuntu Groovy)
   Importance: Undecided
   Status: New

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

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

Title:
  Regression: block staircase display with side-by-side monitors of
  different pixel widths

Status in Linux:
  Unknown
Status in libxcb package in Ubuntu:
  Confirmed
Status in xfwm4 package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Confirmed
Status in libxcb source package in Focal:
  New
Status in xfwm4 source package in Focal:
  New
Status in xserver-xorg-video-amdgpu source package in Focal:
  New
Status in libxcb source package in Groovy:
  New
Status in xfwm4 source package in Groovy:
  Fix Released
Status in xserver-xorg-video-amdgpu source package in Groovy:
  New

Bug description:
  Update based on further research.

  This only happens when the secondary external display is operating at
  a different pixel width to the internal. In this case eDP is 1920x1080
  whereas the external HDMI-A-0 is natively 1680x1050.

  It is caused by xfwm4's recent switch from using glx to xpresent for
  AMD GPUs.

  The underlying bug is in the AMD driver.

  I was able to reproduce on an external 1920x1200 display only when it
  was set to a non-native 1680x1050 resolution.

  ---
  Two identical Lenovo E495 laptops with 20.04 installed. The problem occurred 
initially on the laptop that is having package upgrades applied regularly.

  With dual monitors and the external monitor placed left or right the
  display has a blocked staircase effect shown in the attached
  photograph, and seems related to

  https://gitlab.freedesktop.org/xorg/driver/xf86-video-
  amdgpu/-/issues/10

  More detailed investigation suggests it only happens when the X
  coordinate of the two monitors is different. The symptom looks like an
  off-by-one error because it appears as if the display is divided into,
  say, 10 rows and 15 columns but the first row has 16 'columns' worth
  of blocks on it and so wraps to the beginning of the 2nd row, and so
  on.

  On the laptop without package upgrades being applied this didn't
  happen. So I upgraded it (314 packages) and restarted and it too sees
  the same problem.

  I suspected libxcomposite1 and downgraded it to 1:0.4.5-0ubuntu1 but
  that didn't solve it.

  I now suspect libxcb but so far haven't been able to prove it.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 
00 [VGA controller])
     Subsystem: Lenovo ThinkPad E595 [17aa:5124]
  InstallationDate: Installed on 2020-04-08 (11 days ago)
  InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200408)
  MachineType: LENOVO 20NECTO1WW
  Package: xserver-xorg-video-amdgpu 19.1.0-1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic 
root=/dev/mapper/ELLOE000-rootfs ro acpi_osi=! "acpi_osi=Windows 2016" quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Tags:  focal ubuntu ubuntu
  Uname: Linux 5.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sudo users
  _MarkForUpload: True
  dmi.bios.date: 12/23/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R11ET32W (1.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20NECTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR11ET32W(1.12):bd12/23/2019:svnLENOVO:pn20NECTO1WW:pvrThinkPadE495:rvnLENOVO:rn20NECTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad E495
  dmi.product.name: 20NECTO1WW
  dmi.product.sku: LENOVO_MT_20NE_BU_Think_FM_ThinkPad E495
  dmi.product.version: ThinkPad E495
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2

[Desktop-packages] [Bug 1898541] Re: [FFe] Update to 3.38.0

2020-10-08 Thread Sean Davis

No objections on the Xubuntu side.

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

Title:
  [FFe] Update to 3.38.0

Status in gnome-software package in Ubuntu:
  Fix Committed

Bug description:
  It would be good if we could ship gnome-software 3.38.0 with groovy.

  These are the 3.37.92 changes:

  Add sysprof support for profiling jobs
  Add webflow and basic auth support to flatpak plugin
  Coalesce refresh operations where possible
  Correctly mark layered rpm-ostree local packages as removable
  Fix flatpak bundle installation
  Handle invalid snap auth data
  Improve flatpak progress reporting for transactions
  Improve the heuristic for detecting old-style AppStream override files
  Many performance improvements in many areas of the code
  Only delete the firmware archive if we downloaded it to the cache
  Show a pulsing progress bar if progress is unknown
  Support loading appstream files from custom install prefix
  Use the runtime fwupd version for the user agent

  3.38.0 is a pure translation update.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1898541/+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 1898910] [NEW] gnome-shell crashes when in Wayland and you try to change the Resolution

2020-10-07 Thread Sean Miller Jr

Public bug reported:

Ubuntu on Wayland crashes when you try to change the resolution even if your 
display supports the 
Version: 3.38.0-1ubuntu2
Release: 20.10 Groovy Gorilla (development branch)
What I expected to happen
1. Login to Wayland 
2. Change the resolution 
3. Go on with my day

What actually happened
1. Login to Wayland
2. Change the resolution
3. Wait a minute to get kicked to the gdm login screen
4. Now I am here.

ProblemType: Crash
DistroRelease: Ubuntu 20.10
Package: gnome-shell 3.38.0-1ubuntu2
ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10
Uname: Linux 5.8.0-20-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu49
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct  7 12:55:35 2020
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
InstallationDate: Installed on 2020-10-07 (0 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930)
ProcCmdline: /usr/bin/gnome-shell
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
RelatedPackageVersions: mutter-common 3.38.0-1ubuntu1
Signal: 6
SourcePackage: gnome-shell
StacktraceTop:
 () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
 () at /usr/lib/gnome-shell/libst-1.0.so
 g_closure_invoke () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
 () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gnome-shell crashed with SIGABRT
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
separator:

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


** Tags: amd64 apport-crash groovy need-amd64-retrace

** Information type changed from Private to Public

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

Title:
  gnome-shell crashes when in Wayland and you try to change the
  Resolution

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Ubuntu on Wayland crashes when you try to change the resolution even if your 
display supports the 
  Version: 3.38.0-1ubuntu2
  Release: 20.10 Groovy Gorilla (development branch)
  What I expected to happen
  1. Login to Wayland 
  2. Change the resolution 
  3. Go on with my day

  What actually happened
  1. Login to Wayland
  2. Change the resolution
  3. Wait a minute to get kicked to the gdm login screen
  4. Now I am here.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.10
  Package: gnome-shell 3.38.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10
  Uname: Linux 5.8.0-20-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu49
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct  7 12:55:35 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2020-10-07 (0 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.38.0-1ubuntu1
  Signal: 6
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   () at /usr/lib/gnome-shell/libst-1.0.so
   g_closure_invoke () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-shell crashed with SIGABRT
  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/gnome-shell/+bug/1898910/+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 1855595] Re: CUPS fails to print to autodetected printers because of cups-browsed error

2020-09-18 Thread Sean

I've run into a similar issue.  I've found running 'cups-browsed' as my
user in a terminal allows me to get several print runs through.   Any
queued jobs will immediately print after I start up the process.

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

Title:
  CUPS fails to print to autodetected printers because of cups-browsed
  error

Status in cups-filters package in Ubuntu:
  New

Bug description:
  When trying to autodetected IPP printers, print job stays in queue.

  lpstat -l:

  HP_LaserJet_CM1415fn_44A808_-23 erik 30720   So 08 Dez 2019 
15:50:20 CET
  Status: No suitable destination host found by cups-browsed.
  Alarme: resources-are-not-ready
  in Warteschlange eingereiht für HP_LaserJet_CM1415fn_44A808_

  Removing the print job, restarting cups-browsed with `service cups-
  browsed restart` followed by `service cups restart` enables printing
  for one print job; the next one fails again with the same issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cups-browsed 1.25.13-1
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu13
  Architecture: amd64
  CurrentDesktop: LXQt
  Date: Sun Dec  8 16:06:02 2019
  InstallationDate: Installed on 2019-10-19 (50 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191019)
  Lpstat:
   device for HP_LaserJet_CM1415fn_44A808_: 
implicitclass://HP_LaserJet_CM1415fn_44A808_/
   device for Samsung_C48x_Series_SEC84251900EE44_: 
implicitclass://Samsung_C48x_Series_SEC84251900EE44_/
  MachineType: Dell Inc. Latitude E6530
  Papersize: a4
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP_LaserJet_CM1415fn_44A808_.ppd', 
'/etc/cups/ppd/Samsung_C48x_Series_SEC84251900EE44_.ppd'] failed with exit code 
2: grep: /etc/cups/ppd/HP_LaserJet_CM1415fn_44A808_.ppd: Permission denied
   grep: /etc/cups/ppd/Samsung_C48x_Series_SEC84251900EE44_.ppd: Permission 
denied
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_utwd0l@/vmlinuz-5.3.0-24-generic 
root=ZFS=rpool/ROOT/ubuntu_utwd0l ro quiet splash vt.handoff=1
  SourcePackage: cups-filters
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/30/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A22
  dmi.board.name: 07Y85M
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA22:bd11/30/2018:svnDellInc.:pnLatitudeE6530:pvr01:rvnDellInc.:rn07Y85M:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6530
  dmi.product.sku: Latitude E6530
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1855595/+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 1816497] Re: [snap] vaapi chromium no video hardware decoding

2020-09-06 Thread sean

Most of us have tryed h264ify it dose not help the issue seem to be with
the build

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

Title:
  [snap] vaapi chromium no video hardware decoding

Status in chromium-browser package in Ubuntu:
  In Progress

Bug description:
  News :

  - Candidate Chromium 83 Snap with vaapi enabled can be installed with
  :

  sudo snap install --channel=candidate/vaapi chromium

  Check that your vidéo is gpu decoded but checking "MojoVideoDecoder"
  in about:media-internals

  Widevine DRM streams will have DecryptingVideoDecoder

  Please report success/failure with

  - distro version
  - GPU Hardware used
  - Codec used

  --Original Bug report -

  Libva is no longer working for snap installed chromium 72.0.3626.109
  (Official Build) snap (64-bit)

  I followed this instruction
  sudo snap install --channel=candidate/vaapi chromium

  My amdgpu can use libva

  `vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM 
3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1)
  vainfo: Supported profile and entrypoints
    VAProfileMPEG2Simple:   VAEntrypointVLD
    VAProfileMPEG2Main  :   VAEntrypointVLD
    VAProfileVC1Simple  :   VAEntrypointVLD
    VAProfileVC1Main:   VAEntrypointVLD
    VAProfileVC1Advanced:   VAEntrypointVLD
    VAProfileH264ConstrainedBaseline:   VAEntrypointVLD
    VAProfileH264ConstrainedBaseline:   VAEntrypointEncSlice
    VAProfileH264Main   :   VAEntrypointVLD
    VAProfileH264Main   :   VAEntrypointEncSlice
    VAProfileH264High   :   VAEntrypointVLD
    VAProfileH264High   :   VAEntrypointEncSlice
    VAProfileHEVCMain   :   VAEntrypointVLD
    VAProfileHEVCMain10 :   VAEntrypointVLD
    VAProfileJPEGBaseline   :   VAEntrypointVLD
    VAProfileNone   :   VAEntrypointVideoProc`

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497/+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 1893449] [NEW] libbluray-bdj crashes on 20.04

2020-08-28 Thread Sean

Public bug reported:

libluray/libbluray-bdj crashes on 20.04 when playing certain blurays.
Issue does not happen on 18.04.

Description:Ubuntu 20.04.1 LTS
Release:20.04

libbluray-bdj:
  Installed: 1:1.2.0-1
  Candidate: 1:1.2.0-1
  Version table:
 *** 1:1.2.0-1 500
500 http://ca.archive.ubuntu.com/ubuntu focal/universe amd64 Packages
500 http://ca.archive.ubuntu.com/ubuntu focal/universe i386 Packages
100 /var/lib/dpkg/status


libbluray-bdj_1.0.2-3 from 18.04 plays the blurays correctly.


Jave error in log when using libbluray from 20.04:

Exception in thread "main"
PrintStream.java:java.io.PrintStream.println:823:
java.lang.NoClassDefFoundError: org/objectweb/asm/commons/SimpleRemapper

PrintStream.java:java.io.PrintStream.println:823:   at
org.videolan.BDJClassFileTransformer.rename(BDJClassFileTransformer.java:64)

PrintStream.java:java.io.PrintStream.println:823:   at
org.videolan.mmbd.Adapter.(Adapter.java:83)

PrintStream.java:java.io.PrintStream.println:823:   at
sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)

PrintStream.java:java.io.PrintStream.println:823:   at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)

PrintStream.java:java.io.PrintStream.println:823:   at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)

PrintStream.java:java.io.PrintStream.println:823:   at
java.lang.reflect.Constructor.newInstance(Constructor.java:423)

PrintStream.java:java.io.PrintStream.println:823:   at
java.lang.Class.newInstance(Class.java:442)

PrintStream.java:java.io.PrintStream.println:823:   at
org.videolan.Libbluray.loadAdapter(Libbluray.java:99)

PrintStream.java:java.io.PrintStream.println:823:   at
org.videolan.Libbluray.init(Libbluray.java:354)

bdj.c:737: Failed to initialize BD-J (uncaught exception)
GUIManager:0: ERROR: getInstance(): no instance !
bluray.c:3202: Can't play BD-J title 1
[7f81ec0062c0] libbluray demux error: bluray: stopping playback after fatal 
error

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

** Attachment added: "VLC error log"
   
https://bugs.launchpad.net/bugs/1893449/+attachment/5405477/+files/libbluray%20error%20log

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

Title:
  libbluray-bdj crashes on 20.04

Status in libbluray package in Ubuntu:
  New

Bug description:
  libluray/libbluray-bdj crashes on 20.04 when playing certain blurays.
  Issue does not happen on 18.04.

  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04

  libbluray-bdj:
Installed: 1:1.2.0-1
Candidate: 1:1.2.0-1
Version table:
   *** 1:1.2.0-1 500
  500 http://ca.archive.ubuntu.com/ubuntu focal/universe amd64 Packages
  500 http://ca.archive.ubuntu.com/ubuntu focal/universe i386 Packages
  100 /var/lib/dpkg/status

  
  libbluray-bdj_1.0.2-3 from 18.04 plays the blurays correctly.

  
  Jave error in log when using libbluray from 20.04:

  Exception in thread "main"
  PrintStream.java:java.io.PrintStream.println:823:
  java.lang.NoClassDefFoundError:
  org/objectweb/asm/commons/SimpleRemapper

  PrintStream.java:java.io.PrintStream.println:823:   at
  org.videolan.BDJClassFileTransformer.rename(BDJClassFileTransformer.java:64)

  PrintStream.java:java.io.PrintStream.println:823:   at
  org.videolan.mmbd.Adapter.(Adapter.java:83)

  PrintStream.java:java.io.PrintStream.println:823:   at
  sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)

  PrintStream.java:java.io.PrintStream.println:823:   at
  
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)

  PrintStream.java:java.io.PrintStream.println:823:   at
  
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)

  PrintStream.java:java.io.PrintStream.println:823:   at
  java.lang.reflect.Constructor.newInstance(Constructor.java:423)

  PrintStream.java:java.io.PrintStream.println:823:   at
  java.lang.Class.newInstance(Class.java:442)

  PrintStream.java:java.io.PrintStream.println:823:   at
  org.videolan.Libbluray.loadAdapter(Libbluray.java:99)

  PrintStream.java:java.io.PrintStream.println:823:   at
  org.videolan.Libbluray.init(Libbluray.java:354)

  bdj.c:737: Failed to initialize BD-J (uncaught exception)
  GUIManager:0: ERROR: getInstance(): no instance !
  bluray.c:3202: Can't play BD-J title 1
  [7f81ec0062c0] libbluray demux error: bluray: stopping playback after 
fatal error

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

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

[Desktop-packages] [Bug 1875528] Re: Extra frozen / stuck mouse cursor after auto screen lock / sleep

2020-08-25 Thread Sean Sweeney

To address the two other commenters who mentioned fractional scaling -
that's definitely the cause of the extra mouse cursor in my case. If I
set the display scaling back to 100%, the extra cursor goes away and
stays away between reboots and logout/login cycles. Upon setting it back
to 125%, the second cursor initially remains gone, but returns when I
reboot the machine or log out and then back in.

I'm also on 20.04, on a Thinkpad A485, Ryzen 7 Pro 2700U w/ Radeon Vega
gfx.

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

Title:
  Extra frozen / stuck mouse cursor after auto screen lock / sleep

Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Expected:

  After my computer had gone to sleep and I log in I should see only a
  single active mouse cursor.

  
  What happened instead:

  After my computer had gone to sleep and I logged in I noticed a second
  frozen/stuck mouse cursor was on screen and was rendered in one place
  over any active application windows.

  

  I recently upgraded to 20.04 from 19.10 but the same issue was
  occurring in 19.10 as well.

  Logging out completely then logging back in again removed the extra
  frozen cursor.

  

  lsb_release -rd
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  apt-cache policy mutter
  mutter:
Installed: 3.36.1-3ubuntu3
Candidate: 3.36.1-3ubuntu3
Version table:
   *** 3.36.1-3ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: mutter 3.36.1-3ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 27 19:53:03 2020
  InstallationDate: Installed on 2019-03-09 (415 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: mutter
  UpgradeStatus: Upgraded to focal on 2020-04-28 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1875528/+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 1816497] Re: [snap] vaapi chromium no video hardware decoding

2020-08-21 Thread sean

* now not working

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

Title:
  [snap] vaapi chromium no video hardware decoding

Status in chromium-browser package in Ubuntu:
  In Progress

Bug description:
  News :

  - Candidate Chromium 83 Snap with vaapi enabled can be installed with
  :

  sudo snap install --channel=candidate/vaapi chromium

  Check that your vidéo is gpu decoded but checking "MojoVideoDecoder"
  in about:media-internals

  Widevine DRM streams will have DecryptingVideoDecoder

  Please report success/failure with

  - distro version
  - GPU Hardware used
  - Codec used

  --Original Bug report -

  Libva is no longer working for snap installed chromium 72.0.3626.109
  (Official Build) snap (64-bit)

  I followed this instruction
  sudo snap install --channel=candidate/vaapi chromium

  My amdgpu can use libva

  `vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM 
3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1)
  vainfo: Supported profile and entrypoints
    VAProfileMPEG2Simple:   VAEntrypointVLD
    VAProfileMPEG2Main  :   VAEntrypointVLD
    VAProfileVC1Simple  :   VAEntrypointVLD
    VAProfileVC1Main:   VAEntrypointVLD
    VAProfileVC1Advanced:   VAEntrypointVLD
    VAProfileH264ConstrainedBaseline:   VAEntrypointVLD
    VAProfileH264ConstrainedBaseline:   VAEntrypointEncSlice
    VAProfileH264Main   :   VAEntrypointVLD
    VAProfileH264Main   :   VAEntrypointEncSlice
    VAProfileH264High   :   VAEntrypointVLD
    VAProfileH264High   :   VAEntrypointEncSlice
    VAProfileHEVCMain   :   VAEntrypointVLD
    VAProfileHEVCMain10 :   VAEntrypointVLD
    VAProfileJPEGBaseline   :   VAEntrypointVLD
    VAProfileNone   :   VAEntrypointVideoProc`

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497/+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 1816497] Re: [snap] vaapi chromium no video hardware decoding

2020-08-21 Thread sean

Was working last week even with vp9:

vainfo output:
libva info: VA-API version 1.7.0
libva info: User environment variable requested driver 'iHD'
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_7
libva info: va_openDriver() returns 0
vainfo: VA-API version: 1.7 (libva 2.9.0.pre1)
vainfo: Driver version: Intel iHD driver for Intel(R) Gen Graphics - 20.1.1 ()
vainfo: Supported profile and entrypoints
  VAProfileNone   : VAEntrypointVideoProc
  VAProfileNone   : VAEntrypointStats
  VAProfileMPEG2Simple: VAEntrypointVLD
  VAProfileMPEG2Simple: VAEntrypointEncSlice
  VAProfileMPEG2Main  : VAEntrypointVLD
  VAProfileMPEG2Main  : VAEntrypointEncSlice
  VAProfileH264Main   : VAEntrypointVLD
  VAProfileH264Main   : VAEntrypointEncSlice
  VAProfileH264Main   : VAEntrypointFEI
  VAProfileH264Main   : VAEntrypointEncSliceLP
  VAProfileH264High   : VAEntrypointVLD
  VAProfileH264High   : VAEntrypointEncSlice
  VAProfileH264High   : VAEntrypointFEI
  VAProfileH264High   : VAEntrypointEncSliceLP
  VAProfileVC1Simple  : VAEntrypointVLD
  VAProfileVC1Main: VAEntrypointVLD
  VAProfileVC1Advanced: VAEntrypointVLD
  VAProfileJPEGBaseline   : VAEntrypointVLD
  VAProfileJPEGBaseline   : VAEntrypointEncPicture
  VAProfileH264ConstrainedBaseline: VAEntrypointVLD
  VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
  VAProfileH264ConstrainedBaseline: VAEntrypointFEI
  VAProfileH264ConstrainedBaseline: VAEntrypointEncSliceLP
  VAProfileVP8Version0_3  : VAEntrypointVLD
  VAProfileVP8Version0_3  : VAEntrypointEncSlice
  VAProfileHEVCMain   : VAEntrypointVLD
  VAProfileHEVCMain   : VAEntrypointEncSlice
  VAProfileHEVCMain   : VAEntrypointFEI
  VAProfileHEVCMain10 : VAEntrypointVLD
  VAProfileHEVCMain10 : VAEntrypointEncSlice
  VAProfileVP9Profile0: VAEntrypointVLD
  VAProfileVP9Profile2: VAEntrypointVLD


media-internals Stuff:

render_id: 24
player_id: 43
origin_url: https://www.youtube.com/
kFrameUrl: https://www.youtube.com/watch?v=tEK7GIefwZE
kFrameTitle: 
url: blob:https://www.youtube.com/28d56b05-cb4e-4d58-abc1-a85d8b4d578a
info: Selected video track: [1]
pipeline_state: kPlaying
kVideoTracks: [object Object]
kAudioTracks: [object Object]
kIsAudioDecryptingDemuxerStream: false
kAudioDecoderName: FFmpegAudioDecoder
kIsPlatformAudioDecoder: false
error: 
{"causes":[{"causes":[],"data":{},"stack":[{"file":"../../media/filters/decrypting_video_decoder.cc","line":53}],"status_code":264,"status_message":""}],"data":{"Decoder
 
name":"DecryptingVideoDecoder"},"stack":[{"file":"../../media/filters/decoder_selector.cc","line":172}],"status_code":265,"status_message":""}
kIsVideoDecryptingDemuxerStream: false
kVideoDecoderName: VpxVideoDecoder
kIsPlatformVideoDecoder: false
event: kPlay
audio_buffering_state: [object Object]
dimensions: 1920x1080
kResolution: 1920x1080
video_buffering_state: [object Object]
pipeline_buffering_state: [object Object]
duration: 799.461

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

Title:
  [snap] vaapi chromium no video hardware decoding

Status in chromium-browser package in Ubuntu:
  In Progress

Bug description:
  News :

  - Candidate Chromium 83 Snap with vaapi enabled can be installed with
  :

  sudo snap install --channel=candidate/vaapi chromium

  Check that your vidéo is gpu decoded but checking "MojoVideoDecoder"
  in about:media-internals

  Widevine DRM streams will have DecryptingVideoDecoder

  Please report success/failure with

  - distro version
  - GPU Hardware used
  - Codec used

  --Original Bug report -

  Libva is no longer working for snap installed chromium 72.0.3626.109
  (Official Build) snap (64-bit)

  I followed this instruction
  sudo snap install --channel=candidate/vaapi chromium

  My amdgpu can use libva

  `vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM 
3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1)
  vainfo: Supported profile and entrypoints
    VAProfileMPEG2Simple:   VAEntrypointVLD
    VAProfileMPEG2Main  :   VAEntrypointVLD
    VAProfileVC1Simple  :   VAEntrypointVLD
    VAProfileVC1Main:   VAEntrypointVLD
    VAProfileVC1Advanced:   VAEntrypointVLD
    VAProfileH264ConstrainedBaseline:   VAEntrypointVLD
    VAProfileH264ConstrainedBaseline:

[Desktop-packages] [Bug 1877016] Re: ubuntu-wsl / wslu : needs /mnt/c/windows/system32/ in PATH env variable

2020-07-01 Thread Sean Fausett

Will this fix be released for versions of Ubuntu other than Groovy?

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

Title:
  ubuntu-wsl / wslu : needs /mnt/c/windows/system32/ in PATH env
  variable

Status in wslu package in Ubuntu:
  Fix Released
Status in wslu source package in Xenial:
  Confirmed
Status in wslu source package in Bionic:
  Confirmed
Status in wslu source package in Focal:
  Confirmed
Status in wslu source package in Groovy:
  Fix Released

Bug description:
  [Impact]

  This affects all wslu tools on all releases. When PATH do not include
  Windows path, the all tools will complain that reg.exe is not found.

  [Test Case]

   * Add appendWindowsPath = false under [interop] section in /etc/wsl.conf 
file, and restart the distribution
   * run any wslu tool (like wslfetch)
   * "/mnt/c/Windows/System32/reg.exe: Permission denied" should not be shown

  [Regression Potential]

  * For future release of wslu 3.1.0 proposed, huge refactoring will be
  needed.

  [Original Bug Report]

  ubuntu-wsl / wslu : needs /mnt/c/windows/system32/ in PATH env
  variable

  $ wslfetch
  /usr/bin/wslfetch: line 108: reg.exe: command not found
  /usr/bin/wslsys: line 108: reg.exe: command not found
  /usr/bin/wslsys: line 183: /mnt/c/Windows/System32/reg.exe: Permission denied
  /usr/bin/wslsys: line 185: /mnt/c/Windows/System32/reg.exe: Permission denied
  /usr/bin/wslsys: line 187: /mnt/c/Windows/System32/reg.exe: Permission denied
  /usr/bin/wslsys: line 189: /mnt/c/Windows/System32/reg.exe: Permission denied
  /usr/bin/wslsys: line 108: reg.exe: command not found
  /usr/bin/wslsys: line 183: /mnt/c/Windows/System32/reg.exe: Permission denied
  /usr/bin/wslsys: line 185: /mnt/c/Windows/System32/reg.exe: Permission denied
  /usr/bin/wslsys: line 187: /mnt/c/Windows/System32/reg.exe: Permission denied
  /usr/bin/wslsys: line 189: /mnt/c/Windows/System32/reg.exe: Permission denied
  /usr/bin/wslsys: line 108: reg.exe: command not found
  /usr/bin/wslsys: line 183: /mnt/c/Windows/System32/reg.exe: Permission denied
  /usr/bin/wslsys: line 185: /mnt/c/Windows/System32/reg.exe: Permission denied
  /usr/bin/wslsys: line 187: /mnt/c/Windows/System32/reg.exe: Permission denied
  /usr/bin/wslsys: line 189: /mnt/c/Windows/System32/reg.exe: Permission denied
  /usr/bin/wslsys: line 108: reg.exe: command not found
  /usr/bin/wslsys: line 183: /mnt/c/Windows/System32/reg.exe: Permission denied
  /usr/bin/wslsys: line 185: /mnt/c/Windows/System32/reg.exe: Permission denied
  /usr/bin/wslsys: line 187: /mnt/c/Windows/System32/reg.exe: Permission denied
  /usr/bin/wslsys: line 189: /mnt/c/Windows/System32/reg.exe: Permission denied
  /usr/bin/wslsys: line 108: reg.exe: command not found
  /usr/bin/wslsys: line 183: /mnt/c/Windows/System32/reg.exe: Permission denied
  /usr/bin/wslsys: line 185: /mnt/c/Windows/System32/reg.exe: Permission denied
  /usr/bin/wslsys: line 187: /mnt/c/Windows/System32/reg.exe: Permission denied
  /usr/bin/wslsys: line 189: /mnt/c/Windows/System32/reg.exe: Permission denied

    ./+o+-  Windows 10 Linux Subsystem
    y. 'yy+ rafaeldtinoco@lenovo
    .;//+/h yyo BUILD:
     .++ .:/++/-.`sss/` BRANCH:
   .:++o: `\/:---:/-RELEASE:Ubuntu 20.04 LTS
  o:+o+:++. `'-/ooo+\   KERNEL: Linux 4.4.0-18362-Microsoft
     .:+o:+o/.  `+sssooo+\  UPTIME: 0d 2h 6m
    .++/+ +oo+o:` \sssooo;
   /+++//+: oo+o
   \+/+o+++ o++o   ydddhh+
    .++.o+ +oo+:` /dddhhh;
     .+.o+oo:.   odd+
  \+.++o+o` -.:ohdh+
   `:o+++  oyo++os:
     .o: .syhhh'.oo++o.
     /osyyy.+++\
     ` +oo+++o:/
    `oo++'`

  After :

  echo $PATH
  
/snap/bin:/snap/sbin:/mnt/c/windows/system32/:/home/rafaeldtinoco/work/sources/upstream/ubuntu-dev-tools/:/usr/lib/ccache:/sbin:/bin:/usr/sbin:/usr/bin:/home/rafaeldtinoco/work/sources/bzr/ubuntu-archive-tools:/home/rafaeldtinoco/work/sources/upstream/lxd/bin:.

  $ wslfetch

    ./+o+-  Windows 10 Linux Subsystem
    y. 'yy+ rafaeldtinoco@lenovo
    .;//+/h yyo BUILD:18363
     .++ .:/++/-.`sss/` BRANCH:   19h1_release
   .:++o: `\/:---:/-RELEASE:  Ubuntu 20.04 LTS
  o:+o+:++. `'-/ooo+\   KERNEL:   Linux 4.4.0-18362-Microsoft
     .:+o:+o/.  `+sssooo+\  UPTIME:   0d 2h 19m
    .++/+ +oo+o:` \sssooo;
   /+++//+: oo+o
   \+/+o+++ o++o   ydddhh+
    .++.o+ +oo+:` /dddhhh;
     .+.o+oo:.   odd+
  \+.++o+o` -.:ohdh+
   `:o+++  oyo++os:

[Desktop-packages] [Bug 1531224] Re: lightdm-gtk-greeter flickers once little after lightdm starts

** Bug watch added: LightDM GTK+ Greeter Bugs #46
   https://github.com/Xubuntu/lightdm-gtk-greeter/issues/46

** Changed in: lightdm-gtk-greeter
   Importance: Undecided => Unknown

** Changed in: lightdm-gtk-greeter
   Status: New => Unknown

** Changed in: lightdm-gtk-greeter
 Remote watch: None => LightDM GTK+ Greeter Bugs #46

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

Title:
  lightdm-gtk-greeter flickers once little after lightdm starts

Status in LightDM GTK+ Greeter:
  Unknown
Status in xserver-xorg-video-intel package in Ubuntu:
  Confirmed

Bug description:
  Bug context:
   · Arch Linux x86_64 4.3.3-2-ARCH
   · systemd 228-3 (using lightdm-plymouth.service)
   · plymouth 0.9.2-8 (compiled from AUR)
   · lightdm 1:1.16.6-2
   · lightdm-gtk-greeter 1:2.0.1-2

  At the end of boot process, right after plymouth splash, lightdm starts 
normally and the GTK+ greeter login screen is shown for about 1 second, but 
then the screen instantly flickers (goes black) and the greeter is redrawn. 
From here on, everything works flawlessly, but the brief flickering is 
certainly annoying.
  This happens every time and no other greeter I have tried presents this 
issue, so I can confirm it is lightdm-gtk-greeter-related.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm-gtk-greeter/+bug/1531224/+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 1472143] Re: pause autologin-timeout when user active

** Bug watch added: LightDM GTK+ Greeter Bugs #39
   https://github.com/Xubuntu/lightdm-gtk-greeter/issues/39

** Changed in: lightdm-gtk-greeter
   Importance: Undecided => Unknown

** Changed in: lightdm-gtk-greeter
   Status: New => Unknown

** Changed in: lightdm-gtk-greeter
 Remote watch: None => LightDM GTK+ Greeter Bugs #39

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

Title:
  pause autologin-timeout when user active

Status in LightDM GTK+ Greeter:
  Unknown
Status in unity-greeter package in Ubuntu:
  Confirmed

Bug description:
  Xubuntu 15.04
  lightdm 2.0.0-0ubuntu1
  lightdm-gtk-greeter and unity-greeter

  autologin-user-timeout works, but doesn't take into account user
  activity. Timer should pause or reset ( i prefer reset ) when one user
  is trying to log into an other account than selected by autologin-user
  in order to avoid to log the user into a session he doesn't want to
  use.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm-gtk-greeter/+bug/1472143/+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 1121660] Re: No visual indication of automatic login

** Bug watch added: LightDM GTK+ Greeter Bugs #16
   https://github.com/Xubuntu/lightdm-gtk-greeter/issues/16

** Changed in: lightdm-gtk-greeter
   Importance: Undecided => Unknown

** Changed in: lightdm-gtk-greeter
   Status: New => Unknown

** Changed in: lightdm-gtk-greeter
 Remote watch: None => LightDM GTK+ Greeter Bugs #16

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

Title:
  No visual indication of automatic login

Status in LightDM GTK+ Greeter:
  Unknown
Status in unity-greeter package in Ubuntu:
  Triaged

Bug description:
  When automatically logging in there is no visual indication an
  autologin is about to occur and no way to cancel it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm-gtk-greeter/+bug/1121660/+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 1713313] Re: Unable to launch pkexec'ed applications on Wayland session

** Bug watch added: LightDM GTK+ Greeter Settings Bugs #5
   https://github.com/Xubuntu/lightdm-gtk-greeter-settings/issues/5

** Also affects: lightdm-gtk-greeter-settings via
   https://github.com/Xubuntu/lightdm-gtk-greeter-settings/issues/5
   Importance: Unknown
   Status: Unknown

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

Title:
  Unable to launch pkexec'ed applications on Wayland session

Status in Back In Time:
  Fix Released
Status in Boot-Info:
  Fix Released
Status in Boot-Repair:
  Fix Released
Status in GNOME Terminal:
  New
Status in HPLIP:
  New
Status in Settings editor for LightDM GTK+ Greeter:
  Unknown
Status in OS-Uninstaller:
  Fix Released
Status in Y PPA Manager:
  New
Status in apport package in Ubuntu:
  New
Status in apt-offline package in Ubuntu:
  New
Status in backintime package in Ubuntu:
  Confirmed
Status in budgie-welcome package in Ubuntu:
  Invalid
Status in caja-admin package in Ubuntu:
  New
Status in cinnamon package in Ubuntu:
  Invalid
Status in ettercap package in Ubuntu:
  Confirmed
Status in gdebi package in Ubuntu:
  Confirmed
Status in gdm3 package in Ubuntu:
  Won't Fix
Status in gnunet-gtk package in Ubuntu:
  Confirmed
Status in gparted package in Ubuntu:
  Invalid
Status in gui-ufw package in Ubuntu:
  Confirmed
Status in guidedog package in Ubuntu:
  New
Status in hplip package in Ubuntu:
  Confirmed
Status in italc package in Ubuntu:
  New
Status in laptop-mode-tools package in Ubuntu:
  New
Status in lightdm-gtk-greeter-settings package in Ubuntu:
  Confirmed
Status in nautilus-admin package in Ubuntu:
  New
Status in needrestart-session package in Ubuntu:
  Confirmed
Status in nemo package in Ubuntu:
  Confirmed
Status in policykit-1 package in Ubuntu:
  Invalid
Status in scanmem package in Ubuntu:
  Invalid
Status in scap-workbench package in Ubuntu:
  Confirmed
Status in sirikali package in Ubuntu:
  Fix Released
Status in synaptic package in Ubuntu:
  Confirmed
Status in thunar package in Ubuntu:
  New
Status in tuned package in Ubuntu:
  New
Status in ubuntustudio-controls package in Ubuntu:
  Fix Released
Status in update-notifier package in Ubuntu:
  New
Status in xdiagnose package in Ubuntu:
  Confirmed
Status in xubuntu-default-settings package in Ubuntu:
  Invalid
Status in zulucrypt package in Ubuntu:
  Fix Released

Bug description:
  *
  Main upstream discussion & fixes example to deal with wayland:
  https://bugzilla.gnome.org/show_bug.cgi?id=776437
  *

  


  Steps to reproduce:
  1. Install Ubuntu 17.10
  2. Install backintime-qt4 or gparted application from above list (full may be 
acquired from 
https://codesearch.debian.net/search?q=pkexec+filetype%3Adesktop+path%3A*%2Fapplications%2F*=1=4
 )
  3a. Try to launch backintime-qt4 from shortcut "Back In Time (root)" (located 
in /usr/share/applications/backintime-qt4-root.desktop, it uses pkexec
  ($ cat /usr/share/applications/backintime-qt4-root.desktop | grep Exec
  Exec=pkexec backintime-qt4)
  3b. Try to launch Gparted from shortcut "GParted" (located in 
/usr/share/applications/gparted.desktop, it uses gparted-pkexec)
  4a.1. Back In Time does not start from GUI.
  4a.2. Back In Time shows error message in console:
  4b. gparted-pkexec does not start, reports error
  $ gparted-pkexec
  Created symlink /run/systemd/system/-.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-1000.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-121.mount → /dev/null.
  Created symlink /run/systemd/system/tmp.mount → /dev/null.
  No protocol specified

  (gpartedbin:12831): Gtk-WARNING **: cannot open display: :0
  Removed /run/systemd/system/-.mount.
  Removed /run/systemd/system/run-user-1000.mount.
  Removed /run/systemd/system/run-user-121.mount.
  Removed /run/systemd/system/tmp.mount.

  $ pkexec backintime-qt4

  Back In Time
  Version: 1.1.12

  Back In Time comes with ABSOLUTELY NO WARRANTY.
  This is free software, and you are welcome to redistribute it
  under certain conditions; type `backintime --license' for details.

  No protocol specified
  app.py: cannot connect to X server :0

  Expected results:
  * backintime-qt4 may be run as root

  Actual results:
  * unable to run backintime-qt4 as root

  Workaround:
  * setting "xhost +si:localuser:root" helps.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: backintime-qt4 1.1.12-2
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic i686
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Sun Aug 27 14:23:14 2017
  InstallationDate: Installed on 2017-08-26 (0 days ago)
  InstallationMedia: Ubuntu 17.10

[Desktop-packages] [Bug 1713313] Re: Unable to launch pkexec'ed applications on Wayland session

2020-06-12 Thread Sean Davis

** No longer affects: lightdm-gtk-greeter-settings

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

Title:
  Unable to launch pkexec'ed applications on Wayland session

Status in Back In Time:
  Fix Released
Status in Boot-Info:
  Fix Released
Status in Boot-Repair:
  Fix Released
Status in GNOME Terminal:
  New
Status in HPLIP:
  New
Status in OS-Uninstaller:
  Fix Released
Status in Y PPA Manager:
  New
Status in apport package in Ubuntu:
  New
Status in apt-offline package in Ubuntu:
  New
Status in backintime package in Ubuntu:
  Confirmed
Status in budgie-welcome package in Ubuntu:
  Invalid
Status in caja-admin package in Ubuntu:
  New
Status in cinnamon package in Ubuntu:
  Invalid
Status in ettercap package in Ubuntu:
  Confirmed
Status in gdebi package in Ubuntu:
  Confirmed
Status in gdm3 package in Ubuntu:
  Won't Fix
Status in gnunet-gtk package in Ubuntu:
  Confirmed
Status in gparted package in Ubuntu:
  Invalid
Status in gui-ufw package in Ubuntu:
  Confirmed
Status in guidedog package in Ubuntu:
  New
Status in hplip package in Ubuntu:
  Confirmed
Status in italc package in Ubuntu:
  New
Status in laptop-mode-tools package in Ubuntu:
  New
Status in lightdm-gtk-greeter-settings package in Ubuntu:
  Confirmed
Status in nautilus-admin package in Ubuntu:
  New
Status in needrestart-session package in Ubuntu:
  Confirmed
Status in nemo package in Ubuntu:
  Confirmed
Status in policykit-1 package in Ubuntu:
  Invalid
Status in scanmem package in Ubuntu:
  Invalid
Status in scap-workbench package in Ubuntu:
  Confirmed
Status in sirikali package in Ubuntu:
  Fix Released
Status in synaptic package in Ubuntu:
  Confirmed
Status in thunar package in Ubuntu:
  New
Status in tuned package in Ubuntu:
  New
Status in ubuntustudio-controls package in Ubuntu:
  Fix Released
Status in ubuntustudio-default-settings package in Ubuntu:
  Invalid
Status in update-notifier package in Ubuntu:
  New
Status in xdiagnose package in Ubuntu:
  Confirmed
Status in xubuntu-default-settings package in Ubuntu:
  Invalid
Status in zulucrypt package in Ubuntu:
  Fix Released

Bug description:
  *
  Main upstream discussion & fixes example to deal with wayland:
  https://bugzilla.gnome.org/show_bug.cgi?id=776437
  *

  


  Steps to reproduce:
  1. Install Ubuntu 17.10
  2. Install backintime-qt4 or gparted application from above list (full may be 
acquired from 
https://codesearch.debian.net/search?q=pkexec+filetype%3Adesktop+path%3A*%2Fapplications%2F*=1=4
 )
  3a. Try to launch backintime-qt4 from shortcut "Back In Time (root)" (located 
in /usr/share/applications/backintime-qt4-root.desktop, it uses pkexec
  ($ cat /usr/share/applications/backintime-qt4-root.desktop | grep Exec
  Exec=pkexec backintime-qt4)
  3b. Try to launch Gparted from shortcut "GParted" (located in 
/usr/share/applications/gparted.desktop, it uses gparted-pkexec)
  4a.1. Back In Time does not start from GUI.
  4a.2. Back In Time shows error message in console:
  4b. gparted-pkexec does not start, reports error
  $ gparted-pkexec
  Created symlink /run/systemd/system/-.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-1000.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-121.mount → /dev/null.
  Created symlink /run/systemd/system/tmp.mount → /dev/null.
  No protocol specified

  (gpartedbin:12831): Gtk-WARNING **: cannot open display: :0
  Removed /run/systemd/system/-.mount.
  Removed /run/systemd/system/run-user-1000.mount.
  Removed /run/systemd/system/run-user-121.mount.
  Removed /run/systemd/system/tmp.mount.

  $ pkexec backintime-qt4

  Back In Time
  Version: 1.1.12

  Back In Time comes with ABSOLUTELY NO WARRANTY.
  This is free software, and you are welcome to redistribute it
  under certain conditions; type `backintime --license' for details.

  No protocol specified
  app.py: cannot connect to X server :0

  Expected results:
  * backintime-qt4 may be run as root

  Actual results:
  * unable to run backintime-qt4 as root

  Workaround:
  * setting "xhost +si:localuser:root" helps.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: backintime-qt4 1.1.12-2
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic i686
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Sun Aug 27 14:23:14 2017
  InstallationDate: Installed on 2017-08-26 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha i386 (20170826)
  PackageArchitecture: all
  SourcePackage: backintime
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1838008] Re: [snap] cursor theme isn't respected

2020-05-25 Thread Sean Davis

** Changed in: xubuntu-default-settings (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  [snap] cursor theme isn't respected

Status in chromium-browser package in Ubuntu:
  Confirmed
Status in xubuntu-default-settings package in Ubuntu:
  Fix Committed

Bug description:
  (initially reported at https://discourse.ubuntu.com/t/call-for-
  testing-chromium-browser-deb-to-snap-transition/11179/85)

  When changing the cursor theme with gnome-tweaks, I can observe that
  some themes aren't respected in the chromium snap. This appears to be
  specific to chromium, other snaps like evince or gimp use the correct
  cursors.

  Yaru and Adwaita are fine, but Redglass or Whiteglass aren't.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1838008/+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 1754872] Re: apt install xubuntu-desktop does not resolve dependencies properly

2020-05-25 Thread Sean Davis

** Changed in: xubuntu-docs (Ubuntu)
   Status: Confirmed => Triaged

** Summary changed:

- apt install xubuntu-desktop does not resolve dependencies properly
+ Document installation of xubuntu-desktop

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

Title:
  Document installation of xubuntu-desktop

Status in apt package in Ubuntu:
  Invalid
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in indicator-datetime package in Ubuntu:
  Invalid
Status in xfce4-session package in Ubuntu:
  Fix Released
Status in xubuntu-docs package in Ubuntu:
  Triaged
Status in xubuntu-meta package in Ubuntu:
  Invalid

Bug description:
  Steps to reproduce:
  1. Install `xubuntu-desktop` meta package on 18.04 LTS
  2. Login to session
  3a. Click on clock indicator on panel, select "Time & Date Settings"
  3b. Click on Gear, select "About this Computer" or "System Settings"
  3c. Click on keyboard layout indicator, select "Text Entry Settings"

  Expected results:
  xfce-oriented control center is opened

  Actual results:
  gnome-control-center is opened, but with empty window.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xubuntu-desktop 2.223
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Mar 10 21:10:11 2018
  SourcePackage: xubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1754872/+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 1838008] Re: [snap] cursor theme isn't respected

2020-05-25 Thread Sean Davis

Fix committed in xubuntu-default-settings:
- 
https://github.com/Xubuntu/xubuntu-default-settings/commit/7ea4e59df2394140b28cf92b2651d327a800f00f
- 
https://github.com/Xubuntu/xubuntu-default-settings/commit/f2ee8c4526862248edba19dc8a1aca9dfa10059b

Basically, we were referencing a theme that no longer exists, "Human",
so the theme was falling back on Default. There is no default theme in
gtk-common-themes, so the fallback X11 theme was used instead.

** Changed in: xubuntu-default-settings (Ubuntu)
   Status: Confirmed => Fix Committed

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

Title:
  [snap] cursor theme isn't respected

Status in chromium-browser package in Ubuntu:
  Confirmed
Status in xubuntu-default-settings package in Ubuntu:
  Fix Committed

Bug description:
  (initially reported at https://discourse.ubuntu.com/t/call-for-
  testing-chromium-browser-deb-to-snap-transition/11179/85)

  When changing the cursor theme with gnome-tweaks, I can observe that
  some themes aren't respected in the chromium snap. This appears to be
  specific to chromium, other snaps like evince or gimp use the correct
  cursors.

  Yaru and Adwaita are fine, but Redglass or Whiteglass aren't.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1838008/+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 1838008] Re: [snap] cursor theme isn't respected

2020-05-19 Thread Sean Davis

** Also affects: xubuntu-default-settings (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  [snap] cursor theme isn't respected

Status in chromium-browser package in Ubuntu:
  Confirmed
Status in xubuntu-default-settings package in Ubuntu:
  New

Bug description:
  (initially reported at https://discourse.ubuntu.com/t/call-for-
  testing-chromium-browser-deb-to-snap-transition/11179/85)

  When changing the cursor theme with gnome-tweaks, I can observe that
  some themes aren't respected in the chromium snap. This appears to be
  specific to chromium, other snaps like evince or gimp use the correct
  cursors.

  Yaru and Adwaita are fine, but Redglass or Whiteglass aren't.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1838008/+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 1874178] Re: Unlocking existing session needs two attempts after selecting Switch User

2020-04-22 Thread Sean Davis

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

** Changed in: lightdm (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  Unlocking existing session needs two attempts after selecting Switch
  User

Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  This has been occurring during the Xubuntu post-install test. It's not
  the same as Bug #1776475, as it's not necessary to have logged in as
  another user (or even for another user to exist) for the problem to
  happen.

  My sequence of actions is:

  *Create new user.
  *Open a program (usually Thunar or Terminal).
  *Lock session.
  *Click on "Switch User". <-- This is all that's necessary to trigger it.
  *Enter password to unlock my own session.
  *Then there's a delay and screen goes black, then the unlock prompt appears 
again.
  *The second time, my session unlocks.

  This particular report is from a QEMU/KVM vm, but it's also been
  happening on a bare-metal install.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: lightdm 1.30.0-0ubuntu3.1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Apr 22 15:30:29 2020
  InstallationDate: Installed on 2020-04-22 (0 days ago)
  InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200421)
  ProcEnviron:
   LANGUAGE=en_NZ:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_NZ.UTF-8
   SHELL=/bin/bash
  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/1874178/+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 1860330] Re: After upgrading from Eoan to Focal, I receive the error: "A newer version of Thunderbird may have made changes to your profile which are no longer compatible with

2020-01-20 Thread Sean Sosik-Hamor

I see to have found a workaround:

ubuntu@friendly:/usr/bin$ ./thunderbird -allow-downgrade

Users shouldn't need to manually run this. Chatter from the below Web
pages says:

mahmacc said:
> The instruction to change to the Thunderbird installation directory and then 
> run the command as ./thunderbird is not necessary for Linux users whose 
> paths are set up so the command above will work.)

Matt said:
> Hmm, and who has their path set correctly.  My experience is that the more 
> people need help the less likely they are to even know what a path is.  That 
> is certainly the case on Windows where very few appear to even have heard of 
> the path.  It is still there and works like it always did.  But the user base 
> of windows has no idea.


References:

 * https://support.mozilla.org/en-US/questions/1276736
 * 
https://thunderbirdtweaks.blogspot.com/2019/09/i-lost-my-profilemail-on-update-to.html

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

Title:
  After upgrading from Eoan to Focal, I receive the error: "A newer
  version of Thunderbird may have made changes to your profile which are
  no longer compatible with this older version. Use this profile only
  with that newer version, or create a new profile for this installation
  of Thunderbird. Creating a new profile requires setting up your
  accounts, calendars and add-ons again."

Status in Mozilla Thunderbird:
  Unknown
Status in thunderbird package in Ubuntu:
  New

Bug description:
  I've only ever used the default Thunderbird that came packaged with
  Ubuntu. After upgrading from Eoan to Focal I receive the following
  popup error dialog:

  "A newer version of Thunderbird may have made changes to your profile
  which are no longer compatible with this older version. Use this
  profile only with that newer version, or create a new profile for this
  installation of Thunderbird. Creating a new profile requires setting
  up your accounts, calendars and add-ons again."

  The only options are "Create New Profile" and "Quit" with no option to
  continue using my old profile.

  I tried running thunderbird -ProfileManager to force my current
  default profile but it continued to give me the same error.

  I'm assuming this is a bug as it's a major inconvenience to have to
  reconfigure Thunderbird from scratch after an upgrade.

  Terminal shows:

  JavaScript error: resource://gre/modules/XULStore.jsm, line 66: Error:
  Can't find profile directory.

  And after clicking Quit:

  JavaScript error: resource://gre/modules/AsyncShutdown.jsm, line 694:
  Error: Phase "xpcom-will-shutdown" is finished, it is too late to
  register completion condition "UserInteractionTimer 1 for document
  7f645eb33000"

  See attached screenshot: focal-thunderbird-profile-bug.png

  Thanks, Sean.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: thunderbird 1:68.4.1+build1-0ubuntu1
  ProcVersionSignature: User Name 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2592 F pulseaudio
  BuildID: 20200110122930
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 20 14:43:03 2020
  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/thunderbird/omni.ja:greprefs.js:1141
  DefaultProfilePrefSources: prefs.js
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-06-06 (593 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Profile1Extensions: extensions.sqlite corrupt or missing
  Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile1Locales: extensions.sqlite corrupt or missing
  Profile1PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/thunderbird/omni.ja:greprefs.js:1141
  Profile1PrefSources: prefs.js
  Profile1Prefs:
   extensions.lastAppVersion: "68.4.1" (prefs.js)
   security.sandbox.plugin.tempDirSuffix: 
"18138464-d6cb-4282-a9d4-88ab6acfec88" (prefs.js)
  Profile1Themes: extensions.sqlite corrupt

[Desktop-packages] [Bug 1860330] [NEW] After upgrading from Eoan to Focal, I receive the error: "A newer version of Thunderbird may have made changes to your profile which are no longer compatible wit

2020-01-20 Thread Sean Sosik-Hamor

Public bug reported:

I've only ever used the default Thunderbird that came packaged with
Ubuntu. After upgrading from Eoan to Focal I receive the following popup
error dialog:

"A newer version of Thunderbird may have made changes to your profile
which are no longer compatible with this older version. Use this profile
only with that newer version, or create a new profile for this
installation of Thunderbird. Creating a new profile requires setting up
your accounts, calendars and add-ons again."

The only options are "Create New Profile" and "Quit" with no option to
continue using my old profile.

I tried running thunderbird -ProfileManager to force my current default
profile but it continued to give me the same error.

I'm assuming this is a bug as it's a major inconvenience to have to
reconfigure Thunderbird from scratch after an upgrade.

Terminal shows:

JavaScript error: resource://gre/modules/XULStore.jsm, line 66: Error:
Can't find profile directory.

And after clicking Quit:

JavaScript error: resource://gre/modules/AsyncShutdown.jsm, line 694:
Error: Phase "xpcom-will-shutdown" is finished, it is too late to
register completion condition "UserInteractionTimer 1 for document
7f645eb33000"

See attached screenshot: focal-thunderbird-profile-bug.png

Thanks, Sean.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: thunderbird 1:68.4.1+build1-0ubuntu1
ProcVersionSignature: User Name 5.4.0-9.12-generic 5.4.3
Uname: Linux 5.4.0-9-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu15
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  ubuntu 2592 F pulseaudio
BuildID: 20200110122930
Channel: Unavailable
CurrentDesktop: ubuntu:GNOME
Date: Mon Jan 20 14:43:03 2020
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/thunderbird/omni.ja:greprefs.js:1141
DefaultProfilePrefSources: prefs.js
DefaultProfileThemes: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2018-06-06 (593 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Profile1Extensions: extensions.sqlite corrupt or missing
Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
Profile1Locales: extensions.sqlite corrupt or missing
Profile1PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/thunderbird/omni.ja:greprefs.js:1141
Profile1PrefSources: prefs.js
Profile1Prefs:
 extensions.lastAppVersion: "68.4.1" (prefs.js)
 security.sandbox.plugin.tempDirSuffix: "18138464-d6cb-4282-a9d4-88ab6acfec88" 
(prefs.js)
Profile1Themes: extensions.sqlite corrupt or missing
Profiles:
 Profile1 - LastVersion=68.4.1/20200110122930
 Profile0 (Default) - LastVersion=68.4.1/20200110143530 (Out of date)
RunningIncompatibleAddons: False
SourcePackage: thunderbird
UpgradeStatus: Upgraded to focal on 2020-01-20 (0 days ago)
dmi.bios.date: 09/05/2018
dmi.bios.vendor: System76
dmi.bios.version: 1.05.12-0
dmi.board.asset.tag: Tag 12345
dmi.board.name: Galago Pro
dmi.board.vendor: System76
dmi.board.version: galp2
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: System76
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnSystem76:bvr1.05.12-0:bd09/05/2018:svnSystem76:pnGalagoPro:pvrgalp2:rvnSystem76:rnGalagoPro:rvrgalp2:cvnSystem76:ct10:cvrN/A:
dmi.product.family: Not Applicable
dmi.product.name: Galago Pro
dmi.product.sku: Not Applicable
dmi.product.version: galp2
dmi.sys.vendor: System76

** Affects: thunderbird
 Importance: Unknown
 Status: Unknown

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


** Tags: amd64 apport-bug focal

** Attachment added: "focal-thunderbird-profile-bug.png"
   
https://bugs.launchpad.net/bugs/1860330/+attachment/5321703/+files/focal-thunderbird-profile-bug.png

** Bug watch added: Debian Bug tracker #946347
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946347

** Also affects: thunderbird via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946347
   Importance: Unknown
   Status: Unknown

** Description changed:

  I've only ever used the default Thunderbird that came packaged with
  Ubuntu. After upgrading from Eoan to Focal I receive the following popup
  error dialog:
  
  "A newer version of Thunderbird may have made changes to your profile
  which ar

[Desktop-packages] [Bug 1828664] Re: [snap] Broken link in theme directory

2019-12-19 Thread Sean Davis

@John

Which component is responsible for linking
~/snap/packagename/current/.themes? Is this a per snap functionality or
snapd that would produce this? Currently it's broken for at least the
snaps listed in the description.

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

Title:
  [snap] Broken link in theme directory

Status in gnome-characters package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  Invalid

Bug description:
  Reproduce steps
  ---
  1. $ snap install gnome-characters communitheme
  2. logoff and select communitheme session at the greeter (probably needs a 
reload of GDM or reboot, I'm running the wayland session but it also happened 
of X)
  3. $ snap run gnome-characters

  Affected snaps:
  gnome-characters
  gnome-calculator
  gnome-logs
  gnome-system-monitor
  libreoffice
  evince
  gnome-contacts
  eog

  Symptoms
  
  I'm using the communitheme and gnome-characters snap on Ubuntu 18.04 which 
broke at some point about two month ago. Screenshots are here: 
https://askubuntu.com/q/1142291/40581

  I found that ~/snap/gnome-characters/current/themes is a broken link
  even when removing the respective snap folder for the app, removing
  and then reinstalling the gnome-characters snap. This has worked
  before, please take a look at this.

  In the meantime I fixed this with the following commands, according
  the the error message:

  rm ~/snap/gnome-characters/current/.themes
  cp -av /snap/communitheme/current/share/themes 
~/snap/gnome-characters/current/.themes

  Version
  ---
  ```
  $ snap info {gnome-characters,communitheme} | grep -vE 
"^(summary|license|contact|description|commands):"
  name:  gnome-characters
  publisher: Canonical*
    Characters is a simple utility application to find and
    insert unusual characters.
    - gnome-characters
  snap-id:  qJcS3UjpF9AMJKWAiKwA5EWbm0y6Uduw
  tracking: stable
  refresh-date: heute um 04:19 CEST
  channels:
    stable:v3.32.1+git1.2050bba 2019-05-01 (258) 15MB -
    candidate: v3.32.1+git1.2050bba 2019-05-01 (258) 15MB -
    beta:  ^
    edge:  v3.32.0+git9.4424d0f 2019-05-08 (260) 15MB -
  installed:   v3.32.1+git1.2050bba(258) 15MB -
  ---
  name:  communitheme
  publisher: Didier Roche (didrocks)
    Yaru, formerly known as Communitheme, is the new Ubuntu theme built by the
    community. Yaru will become the default Ubuntu theme in Ubuntu 18.10. This
    package allows you to try out the theme on Ubuntu 18.04 LTS.

    To try out the theme, install this package on Ubuntu 18.04 LTS, restart
    your computer and select the "Ubuntu with communitheme snap" session from
    the login screen.

    More information is available at
    https://community.ubuntu.com/t/faq-ubuntu-new-theme/1930.
  snap-id:  Yd6CISPIf6tEf3ZEJ0cqSoEg9rG2VkRi
  tracking: stable
  refresh-date: 59 days ago, at 17:46 CET
  channels:
    stable:0.1 2019-03-13 (1768) 16MB -
    candidate: ^
    beta:  ^
    edge:  0.1 2019-05-08 (1799) 17MB -
  installed:   0.1(1768) 16MB -
  ```

  ---

  Further investigation
  -

  I'm also seeing broken links on an 19.04 machine where I'm not using
  the Communitheme snap but the preinstalled Yaru packages. I'm trying
  out the dark theme but all snaps launch with Adwaita instead.

  ```
  $ snap list
  Name Version Rev   Tracking  Publisher
 Notes
  android-studio   3.4.0.1875stablesnapcrafters 
 classic
  canonical-livepatch  9.3.0   77stablecanonical*   
 -
  core 16-2.38.1   6818  stablecanonical*   
 core
  core18   20190409941   stablecanonical*   
 base
  gedit3.30.2+git14.bed83e929  89stablecanonical*   
 -
  gnome-3-26-1604  3.26.0.20190228 82stable/…  canonical*   
 -
  gnome-3-28-1804  3.28.0-10-gaa70833.aa70833  40stablecanonical*   
 -
  gnome-calculator 3.32.1  406   stable/…  canonical*   
 -
  gnome-characters v3.32.1+git1.2050bba258   stablecanonical*   
 -
  gnome-logs   3.32.0-4-ge8f3f37ca861stable/…  canonical*   
 -
  gtk-common-themes0.1-16-g2287c87 1198  stable/…  canonical*   
 -

  
  $ find snap/gnome-characters -xtype l
  snap/gnome-characters/common/.cache/immodules/im-fcitx.so
  snap/gnome-characters/common/.cache/immodules/im-wayland.so
  snap/gnome-characters/common/.cache/immodules/im-broadway.so
  snap/gnome-characters/common/.cache/immodules/im-inuktitut.so
  snap/gnome-characters/common/.cache/immodules/im-cedilla.so
  snap/gnome-characters/common/.cache/immodules/im-ipa.so

[Desktop-packages] [Bug 1828664] Re: [snap] Broken link in theme directory

2019-12-18 Thread Sean Davis

Also tagging snap since the issue is present on snaps that have run in
the user session.

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

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

Title:
  [snap] Broken link in theme directory

Status in gnome-characters package in Ubuntu:
  Confirmed
Status in snap package in Ubuntu:
  New

Bug description:
  Reproduce steps
  ---
  1. $ snap install gnome-characters communitheme
  2. logoff and select communitheme session at the greeter (probably needs a 
reload of GDM or reboot, I'm running the wayland session but it also happened 
of X)
  3. $ snap run gnome-characters

  Affected snaps:
  gnome-characters
  gnome-calculator
  gnome-logs
  gnome-system-monitor
  libreoffice
  evince
  gnome-contacts
  eog

  Symptoms
  
  I'm using the communitheme and gnome-characters snap on Ubuntu 18.04 which 
broke at some point about two month ago. Screenshots are here: 
https://askubuntu.com/q/1142291/40581

  I found that ~/snap/gnome-characters/current/themes is a broken link
  even when removing the respective snap folder for the app, removing
  and then reinstalling the gnome-characters snap. This has worked
  before, please take a look at this.

  In the meantime I fixed this with the following commands, according
  the the error message:

  rm ~/snap/gnome-characters/current/.themes
  cp -av /snap/communitheme/current/share/themes 
~/snap/gnome-characters/current/.themes

  Version
  ---
  ```
  $ snap info {gnome-characters,communitheme} | grep -vE 
"^(summary|license|contact|description|commands):"
  name:  gnome-characters
  publisher: Canonical*
    Characters is a simple utility application to find and
    insert unusual characters.
    - gnome-characters
  snap-id:  qJcS3UjpF9AMJKWAiKwA5EWbm0y6Uduw
  tracking: stable
  refresh-date: heute um 04:19 CEST
  channels:
    stable:v3.32.1+git1.2050bba 2019-05-01 (258) 15MB -
    candidate: v3.32.1+git1.2050bba 2019-05-01 (258) 15MB -
    beta:  ^
    edge:  v3.32.0+git9.4424d0f 2019-05-08 (260) 15MB -
  installed:   v3.32.1+git1.2050bba(258) 15MB -
  ---
  name:  communitheme
  publisher: Didier Roche (didrocks)
    Yaru, formerly known as Communitheme, is the new Ubuntu theme built by the
    community. Yaru will become the default Ubuntu theme in Ubuntu 18.10. This
    package allows you to try out the theme on Ubuntu 18.04 LTS.

    To try out the theme, install this package on Ubuntu 18.04 LTS, restart
    your computer and select the "Ubuntu with communitheme snap" session from
    the login screen.

    More information is available at
    https://community.ubuntu.com/t/faq-ubuntu-new-theme/1930.
  snap-id:  Yd6CISPIf6tEf3ZEJ0cqSoEg9rG2VkRi
  tracking: stable
  refresh-date: 59 days ago, at 17:46 CET
  channels:
    stable:0.1 2019-03-13 (1768) 16MB -
    candidate: ^
    beta:  ^
    edge:  0.1 2019-05-08 (1799) 17MB -
  installed:   0.1(1768) 16MB -
  ```

  ---

  Further investigation
  -

  I'm also seeing broken links on an 19.04 machine where I'm not using
  the Communitheme snap but the preinstalled Yaru packages. I'm trying
  out the dark theme but all snaps launch with Adwaita instead.

  ```
  $ snap list
  Name Version Rev   Tracking  Publisher
 Notes
  android-studio   3.4.0.1875stablesnapcrafters 
 classic
  canonical-livepatch  9.3.0   77stablecanonical*   
 -
  core 16-2.38.1   6818  stablecanonical*   
 core
  core18   20190409941   stablecanonical*   
 base
  gedit3.30.2+git14.bed83e929  89stablecanonical*   
 -
  gnome-3-26-1604  3.26.0.20190228 82stable/…  canonical*   
 -
  gnome-3-28-1804  3.28.0-10-gaa70833.aa70833  40stablecanonical*   
 -
  gnome-calculator 3.32.1  406   stable/…  canonical*   
 -
  gnome-characters v3.32.1+git1.2050bba258   stablecanonical*   
 -
  gnome-logs   3.32.0-4-ge8f3f37ca861stable/…  canonical*   
 -
  gtk-common-themes0.1-16-g2287c87 1198  stable/…  canonical*   
 -

  
  $ find snap/gnome-characters -xtype l
  snap/gnome-characters/common/.cache/immodules/im-fcitx.so
  snap/gnome-characters/common/.cache/immodules/im-wayland.so
  snap/gnome-characters/common/.cache/immodules/im-broadway.so
  snap/gnome-characters/common/.cache/immodules/im-inuktitut.so
  snap/gnome-characters/common/.cache/immodules/im-cedilla.so
  snap/gnome-characters/common/.cache/immodules/im-ipa.so
  snap/gnome-characters/common/.cache/immodules/im-xim.so
  snap/gnome-characters/common/.cache/immodules/im-thai.so

[Desktop-packages] [Bug 1856298] [NEW] Tried to start xdiagnose and got error.

2019-12-13 Thread Sean Allen

Public bug reported:

No more details that  I know other than what's in the summary.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3.1
ProcVersionSignature: Ubuntu 4.15.0-72.81~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-72-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.21
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Fri Dec 13 03:32:46 2019
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:04d8]
InstallationDate: Installed on 2019-12-06 (7 days ago)
InstallationMedia: It
MachineType: Dell Inc. Dell System Inspiron N7110
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic 
root=UUID=29f55db3-5639-47d5-82af-087cfc3e019d ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/05/2012
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A13
dmi.board.name: 05VJ58
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: 0.1
dmi.modalias: 
dmi:bvnDellInc.:bvrA13:bd09/05/2012:svnDellInc.:pnDellSystemInspironN7110:pvr:rvnDellInc.:rn05VJ58:rvrA00:cvnDellInc.:ct8:cvr0.1:
dmi.product.family: HuronRiver System
dmi.product.name: Dell System Inspiron N7110
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.91-2~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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


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

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

Title:
  Tried to start xdiagnose and got error.

Status in xorg package in Ubuntu:
  New

Bug description:
  No more details that  I know other than what's in the summary.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-72.81~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-72-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.21
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Fri Dec 13 03:32:46 2019
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:04d8]
  InstallationDate: Installed on 2019-12-06 (7 days ago)
  InstallationMedia: It
  MachineType: Dell Inc. Dell System Inspiron N7110
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic 
root=UUID=29f55db3-5639-47d5-82af-087cfc3e019d ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/05/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A13
  dmi.board.name: 05VJ58
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA13:bd09/05/2012:svnDellInc.:pnDellSystemInspironN7110:pvr:rvnDellInc.:rn05VJ58:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.family: HuronRiver System
  dmi.product.name: Dell System Inspiron N7110
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2

[Desktop-packages] [Bug 1754872] Re: apt install xubuntu-desktop does not resolve dependencies properly

2019-11-03 Thread Sean Davis

Assigned this issue to xubuntu-docs. Let's document the correct way to
handle the installation of the xubuntu-desktop package, and make it easy
for users to find (and forums to point to) when these questions arise in
the future.


** Also affects: xubuntu-docs (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: xubuntu-docs (Ubuntu)
   Status: New => Confirmed

** Changed in: xubuntu-meta (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  apt install xubuntu-desktop does not resolve dependencies properly

Status in apt package in Ubuntu:
  Invalid
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in indicator-datetime package in Ubuntu:
  Invalid
Status in xfce4-session package in Ubuntu:
  Fix Released
Status in xubuntu-docs package in Ubuntu:
  Confirmed
Status in xubuntu-meta package in Ubuntu:
  Invalid

Bug description:
  Steps to reproduce:
  1. Install `xubuntu-desktop` meta package on 18.04 LTS
  2. Login to session
  3a. Click on clock indicator on panel, select "Time & Date Settings"
  3b. Click on Gear, select "About this Computer" or "System Settings"
  3c. Click on keyboard layout indicator, select "Text Entry Settings"

  Expected results:
  xfce-oriented control center is opened

  Actual results:
  gnome-control-center is opened, but with empty window.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xubuntu-desktop 2.223
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Mar 10 21:10:11 2018
  SourcePackage: xubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1754872/+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 1848766] Re: xubuntu still pulls in Python2 via the python-gtk2-dev b-d in libappindicator

2019-11-03 Thread Sean Davis

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

Thanks. jbicha referred to
https://bugs.launchpad.net/ubuntu/+source/libappindicator/+bug/1740637
and mentioned that the python2 support is going to be dropped from
libappindicator, so this should no longer be an issue for Xubuntu.
Thanks for bringing it to my attention!

** Changed in: xubuntu-meta (Ubuntu)
   Status: New => Invalid

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

** This bug has been marked a duplicate of bug 1740637
   Remove python-appindicator and gir1.2-appindicator-0.1

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

Title:
  xubuntu still pulls in Python2 via the python-gtk2-dev b-d in
  libappindicator

Status in libappindicator package in Ubuntu:
  New
Status in pygtk package in Ubuntu:
  Invalid
Status in xubuntu-meta package in Ubuntu:
  Invalid

Bug description:
  xubuntu still pulls in Python2 via the python-gtk2-dev b-d in
  libappindicator.  We don't want to have Python2 anymore in seeds and
  images.  So either xubuntu should stop using libappindicator, or
  libappindicator should provide Python3 packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libappindicator/+bug/1848766/+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 1848766] Re: xubuntu still pulls in Python2 via the python-gtk2-dev b-d in libappindicator

2019-11-03 Thread Sean Davis

Hey @doko,

>From what I can tell, we're not shipping libappindicator at all in
focal. Can you elaborate where this is coming from?

http://cdimage.ubuntu.com/xubuntu/daily-live/current/focal-desktop-
amd64.manifest

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

Title:
  xubuntu still pulls in Python2 via the python-gtk2-dev b-d in
  libappindicator

Status in libappindicator package in Ubuntu:
  New
Status in pygtk package in Ubuntu:
  New
Status in xubuntu-meta package in Ubuntu:
  New

Bug description:
  xubuntu still pulls in Python2 via the python-gtk2-dev b-d in
  libappindicator.  We don't want to have Python2 anymore in seeds and
  images.  So either xubuntu should stop using libappindicator, or
  libappindicator should provide Python3 packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libappindicator/+bug/1848766/+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 1754872] Re: apt install xubuntu-desktop does not resolve dependencies properly

2019-10-26 Thread Sean Davis

I've added this to the 20.04 development blueprint, so let's revisit and
discuss. If we can't solve the problem with packaging, let's document
the mini.iso installation process so others have an easier time.

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

Title:
  apt install xubuntu-desktop does not resolve dependencies properly

Status in apt package in Ubuntu:
  Invalid
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in indicator-datetime package in Ubuntu:
  Invalid
Status in xfce4-session package in Ubuntu:
  Fix Released
Status in xubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Install `xubuntu-desktop` meta package on 18.04 LTS
  2. Login to session
  3a. Click on clock indicator on panel, select "Time & Date Settings"
  3b. Click on Gear, select "About this Computer" or "System Settings"
  3c. Click on keyboard layout indicator, select "Text Entry Settings"

  Expected results:
  xfce-oriented control center is opened

  Actual results:
  gnome-control-center is opened, but with empty window.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xubuntu-desktop 2.223
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Mar 10 21:10:11 2018
  SourcePackage: xubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1754872/+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 1822179] Re: Resuming from sleep breaks desktop and lock screen background in GNOME

2019-10-04 Thread Sean Ferguson

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

I have the same issue,

Ubuntu 19.04 disco
Nvidia GeForce GTX 1050
Pentium G4600


nvidia-smi
Fri Oct  4 17:24:16 2019   
+-+
| NVIDIA-SMI 418.56   Driver Version: 418.56   CUDA Version: 10.1 |
|---+--+--+
| GPU  NamePersistence-M| Bus-IdDisp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap| Memory-Usage | GPU-Util  Compute M. |
|===+==+==|
|   0  GeForce GTX 1050Off  | :01:00.0  On |  N/A |
| 35%   34CP0N/A /  75W |430MiB /  1991MiB |  0%  Default |
+---+--+--+
   
+-+
| Processes:   GPU Memory |
|  GPU   PID   Type   Process name Usage  |
|=|
|0  1266  G   /usr/lib/xorg/Xorg26MiB |
|0  1300  G   /usr/bin/gnome-shell  47MiB |
|0  1520  G   /usr/lib/xorg/Xorg   111MiB |
|0  1659  G   /usr/bin/gnome-shell 241MiB |
+-+


lshw -C video
  *-display 
   description: VGA compatible controller
   product: GP107 [GeForce GTX 1050]
   vendor: NVIDIA Corporation
   physical id: 0
   bus info: pci@:01:00.0
   version: a1
   width: 64 bits
   clock: 33MHz
   capabilities: pm msi pciexpress vga_controller bus_master cap_list rom
   configuration: driver=nvidia latency=0
   resources: irq:125 memory:de00-deff memory:c000-cfff 
memory:d000-d1ff ioport:e000(size=128) memory:c-d

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

Title:
  Resuming from sleep breaks desktop and lock screen background in GNOME

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  CPU: AMD Ryzen 5 1600
  MOBO: MSI B350M MORTAR
  GPU: NVIDIA GTX 1060

  Ubuntu version: 19.04
  Nvidia driver version: 418.56

  
  The system is updated with the latest updates as today, 28 March 2019

  As the title says, in Ubuntu 19.04 the GNOME lockscreen gets
  corrupted, and the GNOME desktop has blank background after resuming
  from standby/sleep

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1822179/+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 1760068] Re: Wrong resolution at unlock screen

2019-09-28 Thread Sean Gray

Okay.For nvidia-435.21 I fixed it with:

Section "Files"
ModulePath "/usr/lib/x86_64-linux-gnu/nvidia/xorg"
ModulePath "/usr/lib/xorg/modules"
EndSection

Light-locker displays the correct resolution now.

//this is insane. They need to patch this on the light-locker side soon.

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

Title:
  Wrong resolution at unlock screen

Status in light-locker package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Confirmed

Bug description:
  After coming out of suspend - the unlock screen is at 640x480
  resolution.

  Expect to see unlock screen at 1920x1080 resolution.

  Using nvidia-340.

  Previously tested using nouveau driver where resolution at unlock
  screen was correct.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: light-locker 1.8.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Mar 30 11:31:20 2018
  InstallationDate: Installed on 2017-09-02 (209 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902)
  SourcePackage: light-locker
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1760068/+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 1532508] Re: Screen contents revealed briefly on resume, before even unlocking

2019-08-17 Thread Sean

Can confirm I am getting this on 19.04 ubuntu budgie and am up to date

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

Title:
  Screen contents revealed briefly on resume, before even unlocking

Status in GNOME Shell:
  In Progress
Status in Ubuntu GNOME:
  Confirmed
Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Xenial:
  Fix Released
Status in gnome-shell package in Debian:
  Confirmed

Bug description:
  [Impact]

  When lock is enabled, the screen doesn't get blank/covered by
  lockscreen before suspending, thus on early resume the content might
  be shown.

  Video showing the bug: https://youtu.be/dDOgtK1MldI

  Reproduced on Ubuntu 2015.10, Ubuntu 2014.04

  [Test case]

  1. Work on highly secret files
  2. Close the lid of your laptop and go have a break
  3. Anyone who opens the lid of the laptop can see the secret files for a half 
second before the lock screen appears

  [Possible Regression]

  Content on screen isn't painted anymore and screen stays black.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1532508/+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 1838856] [NEW] Cups printer installed but not recognized by application.

2019-08-03 Thread Sean Patrick Sneed

Public bug reported:

LibreOffice Writer fails with:

 "Could not start printer.  Please check your printer configuration."

and Notepad++ reports:

"Before you can perform printer-related tasks such as page setup or
printing a document, you need to install a printer.  Please install one
and retry."

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: cups 2.2.10-4ubuntu2
ProcVersionSignature: Ubuntu 5.0.0-21.22-generic 5.0.15
Uname: Linux 5.0.0-21-generic x86_64
ApportVersion: 2.20.10-0ubuntu27.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Aug  3 10:27:58 2019
InstallationDate: Installed on 2019-07-30 (4 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
Lpstat: device for LBP6230-6240: socket://192.168.1.4
MachineType: Acer Aspire E5-522
Papersize: letter
PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/LBP6230-6240.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/LBP6230-6240.ppd: Permission denied
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic 
root=UUID=72fc4deb-a416-4cf8-9607-32e97aa728e7 ro quiet splash vt.handoff=1
SourcePackage: cups
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/15/2015
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.08
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Nami_CZL
dmi.board.vendor: Acer
dmi.board.version: V1.08
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.08:bd09/15/2015:svnAcer:pnAspireE5-522:pvrV1.08:rvnAcer:rnNami_CZL:rvrV1.08:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.family: CZL
dmi.product.name: Aspire E5-522
dmi.product.sku: Aspire E5-522_0960_1.08
dmi.product.version: V1.08
dmi.sys.vendor: Acer

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


** Tags: amd64 apparmor apport-bug disco

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

Title:
  Cups printer installed but not recognized by application.

Status in cups package in Ubuntu:
  New

Bug description:
  LibreOffice Writer fails with:

   "Could not start printer.  Please check your printer configuration."

  and Notepad++ reports:

  "Before you can perform printer-related tasks such as page setup or
  printing a document, you need to install a printer.  Please install
  one and retry."

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: cups 2.2.10-4ubuntu2
  ProcVersionSignature: Ubuntu 5.0.0-21.22-generic 5.0.15
  Uname: Linux 5.0.0-21-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Aug  3 10:27:58 2019
  InstallationDate: Installed on 2019-07-30 (4 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lpstat: device for LBP6230-6240: socket://192.168.1.4
  MachineType: Acer Aspire E5-522
  Papersize: letter
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/LBP6230-6240.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/LBP6230-6240.ppd: Permission denied
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic 
root=UUID=72fc4deb-a416-4cf8-9607-32e97aa728e7 ro quiet splash vt.handoff=1
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/15/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.08
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Nami_CZL
  dmi.board.vendor: Acer
  dmi.board.version: V1.08
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.08:bd09/15/2015:svnAcer:pnAspireE5-522:pvrV1.08:rvnAcer:rnNami_CZL:rvrV1.08:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: CZL
  dmi.product.name: Aspire E5-522
  dmi.product.sku: Aspire E5-522_0960_1.08
  dmi.product.version: V1.08
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1838856/+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 1828606] Re: Ubuntu 18.04 "Files" app unable to show Samba/SMB shares where 'access based share enumeration = yes'

2019-05-15 Thread Sean McBride

https://gitlab.gnome.org/GNOME/gvfs/issues/398

** Bug watch added: gitlab.gnome.org/GNOME/gvfs/issues #398
https://gitlab.gnome.org/GNOME/gvfs/issues/398

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

Title:
Ubuntu 18.04 "Files" app unable to show Samba/SMB shares where 'access
based share enumeration = yes'

Status in gvfs:
Unknown
Status in gvfs package in Ubuntu:
New

Bug description:
From Ubuntu 18.04's GUI, if I open the "Files" app and go to "Other
Locations", I see my samba/SMB server. If I double click it, it then
lists *some* of my shares. Specifically, it lists those where I didn't
use Samba's 'access based share enumeration = yes'[1] (which allows
some shares to be made completely invisible to some users). Note that
Ubuntu has *not* yet asked me to authenticate, so it makes sense that
I shouldn't yet be able to see shares I'm not entitled to.

The bug is: even after I authenticate (and let it remember my
password), then go back to Other Locations>MyServer, it *still*
doesn't show the other shares. In fact, I can't find *any* way to see
the other shares.

Contrast this with macOS Finder. If I navigate to MyServer in the
share list, it doesn't show *any* shares until I authenticate, then it
shows *all* shares that the user has access to (and none of the shares
the user doesn't have access to).

Ubuntu could either:
- adopt macOS Finder behaviour and get authentication first, or
- update the share list after authentication is performed.

Its current behaviour makes some shares totally inaccessible (the crux
of the bug).

I doubt it matters, but my server is: FreeNAS 11.2-U4 (current newest)
using ZFS, running samba 4.9.6. Other users on the FreeNAS forum see
the same behaviour[2], so it's not particular to my setup.

[1] https://www.samba.org/samba/docs/current/man-html/smb.conf.5.html
[2]
https://www.ixsystems.com/community/threads/accessing-smb-shares-from-ubuntu-18-04-doesnt-show-all-shares-in-gui.75961/

To manage notifications about this bug go to:
https://bugs.launchpad.net/gvfs/+bug/1828606/+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 1828606] Re: Ubuntu 18.04 "Files" app unable to show Samba/SMB shares where 'access based share enumeration = yes'

2019-05-10 Thread Sean McBride

OK, I used "ubuntu-bug -w" and the package seems to be "nautilus
1:3.26.4-0~ubuntu18.04.4"

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

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

Title:
  Ubuntu 18.04 "Files" app unable to show Samba/SMB shares where 'access
  based share enumeration = yes'

Status in nautilus package in Ubuntu:
  New

Bug description:
  From Ubuntu 18.04's GUI, if I open the "Files" app and go to "Other
  Locations", I see my samba/SMB server. If I double click it, it then
  lists *some* of my shares. Specifically, it lists those where I didn't
  use Samba's 'access based share enumeration = yes'[1] (which allows
  some shares to be made completely invisible to some users). Note that
  Ubuntu has *not* yet asked me to authenticate, so it makes sense that
  I shouldn't yet be able to see shares I'm not entitled to.

  The bug is: even after I authenticate (and let it remember my
  password), then go back to Other Locations>MyServer, it *still*
  doesn't show the other shares. In fact, I can't find *any* way to see
  the other shares.

  Contrast this with macOS Finder. If I navigate to MyServer in the
  share list, it doesn't show *any* shares until I authenticate, then it
  shows *all* shares that the user has access to (and none of the shares
  the user doesn't have access to).

  Ubuntu could either:
   - adopt macOS Finder behaviour and get authentication first, or
   - update the share list after authentication is performed.

  Its current behaviour makes some shares totally inaccessible (the crux
  of the bug).

  I doubt it matters, but my server is: FreeNAS 11.2-U4 (current newest)
  using ZFS, running samba 4.9.6.  Other users on the FreeNAS forum see
  the same behaviour[2], so it's not particular to my setup.

  [1] https://www.samba.org/samba/docs/current/man-html/smb.conf.5.html
  [2] 
https://www.ixsystems.com/community/threads/accessing-smb-shares-from-ubuntu-18-04-doesnt-show-all-shares-in-gui.75961/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1828606/+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 1824283] Re: Nautilus progress bar is easily lead users to cancel the running task

2019-04-11 Thread Sean Wang

Done.
Thanks for the suggestion.
https://gitlab.gnome.org/GNOME/nautilus/issues/985

** Bug watch added: gitlab.gnome.org/GNOME/nautilus/issues #985
   https://gitlab.gnome.org/GNOME/nautilus/issues/985

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

Title:
  Nautilus  progress bar is easily lead users to cancel the running task

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  People often check the progress of tasks when they copying or deleting
  some large files using the nautilus progress bar. Usually, they would
  click a button to close the popped progress bar. The nautilus progress
  bar is very easy to lead users to click the cancel task button since
  there is only one button on the progress bar which is very like a
  closing window button. I suggest it add a confirm message box or
  change the cancel task button to other icons.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1824283/+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 1824283] [NEW] Nautilus progress bar is easily lead users to cancel the running task

2019-04-10 Thread Sean Wang

Public bug reported:

People often check the progress of tasks when they copying or deleting
some large files using the nautilus progress bar. Usually, they would
click a button to close the popped progress bar. The nautilus progress
bar is very easy to lead users to click the cancel task button since
there is only one button on the progress bar which is very like a
closing window button. I suggest it add a confirm message box or change
the cancel task button to other icons.

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


** Tags: feature suggest

** Attachment added: "Screenshot from 2019-04-11 13-28-30.png"
   
https://bugs.launchpad.net/bugs/1824283/+attachment/5254862/+files/Screenshot%20from%202019-04-11%2013-28-30.png

** Summary changed:

- Nautilus  progress bar is easily lead users to cancel
+ Nautilus  progress bar is easily lead users to cancel the running task

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

Title:
  Nautilus  progress bar is easily lead users to cancel the running task

Status in nautilus package in Ubuntu:
  New

Bug description:
  People often check the progress of tasks when they copying or deleting
  some large files using the nautilus progress bar. Usually, they would
  click a button to close the popped progress bar. The nautilus progress
  bar is very easy to lead users to click the cancel task button since
  there is only one button on the progress bar which is very like a
  closing window button. I suggest it add a confirm message box or
  change the cancel task button to other icons.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1824283/+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 1795135] Re: XFCE window buttons are not clickable at the top of the screen

This issue is resolved with greybird 3.22.10-1 and xfce4-panel 4.13.4-1

** Changed in: xfce4-panel (Ubuntu Disco)
   Status: Confirmed => Fix Released

** Changed in: greybird-gtk-theme (Ubuntu Cosmic)
   Status: New => Triaged

** Changed in: greybird-gtk-theme (Ubuntu Cosmic)
 Assignee: (unassigned) => Sean Davis (bluesabre)

** Changed in: xfce4-panel (Ubuntu Cosmic)
   Status: New => Triaged

** Changed in: xfce4-panel (Ubuntu Cosmic)
 Assignee: (unassigned) => Sean Davis (bluesabre)

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

Title:
  XFCE window buttons are not clickable at the top of the screen

Status in X.Org X server:
  New
Status in greybird-gtk-theme package in Ubuntu:
  Fix Released
Status in xfce4-panel package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Confirmed
Status in greybird-gtk-theme source package in Cosmic:
  Triaged
Status in xfce4-panel source package in Cosmic:
  Triaged
Status in xorg-server source package in Cosmic:
  New
Status in greybird-gtk-theme source package in Disco:
  Fix Released
Status in xfce4-panel source package in Disco:
  Fix Released
Status in xorg-server source package in Disco:
  Confirmed

Bug description:
  This bug affects greybird-gtk-theme and xfce4-panel in Xubuntu Cosmic.

  With Cosmic, it is not possible to click on the window buttons after
  moving the mouse cursor to the top of the screen. Unlike similar bugs,
  no amount of moving left or right triggers the hover event or the
  ability to click on the window button.

  With Adwaita and Numix, we see the same issues we see elsewhere, where
  the buttons can sometimes be clicked, but also have issue with the
  topmost part of the screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: greybird-gtk-theme 3.22.9-0ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Sep 29 09:05:24 2018
  InstallationDate: Installed on 2018-09-29 (0 days ago)
  InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180929)
  PackageArchitecture: all
  SourcePackage: greybird-gtk-theme
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1795135/+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 1795135] Re: XFCE window buttons are not clickable at the top of the screen

This issue is resolved with greybird 3.22.10-1 and xfce4-panel 4.13.4-1

** Changed in: greybird-gtk-theme (Ubuntu Disco)
   Status: New => Fix Released

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

Title:
  XFCE window buttons are not clickable at the top of the screen

Status in X.Org X server:
  New
Status in greybird-gtk-theme package in Ubuntu:
  Fix Released
Status in xfce4-panel package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Confirmed
Status in greybird-gtk-theme source package in Cosmic:
  Triaged
Status in xfce4-panel source package in Cosmic:
  Triaged
Status in xorg-server source package in Cosmic:
  New
Status in greybird-gtk-theme source package in Disco:
  Fix Released
Status in xfce4-panel source package in Disco:
  Fix Released
Status in xorg-server source package in Disco:
  Confirmed

Bug description:
  This bug affects greybird-gtk-theme and xfce4-panel in Xubuntu Cosmic.

  With Cosmic, it is not possible to click on the window buttons after
  moving the mouse cursor to the top of the screen. Unlike similar bugs,
  no amount of moving left or right triggers the hover event or the
  ability to click on the window button.

  With Adwaita and Numix, we see the same issues we see elsewhere, where
  the buttons can sometimes be clicked, but also have issue with the
  topmost part of the screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: greybird-gtk-theme 3.22.9-0ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Sep 29 09:05:24 2018
  InstallationDate: Installed on 2018-09-29 (0 days ago)
  InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180929)
  PackageArchitecture: all
  SourcePackage: greybird-gtk-theme
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1795135/+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 1795135] Re: XFCE window buttons are not clickable at the top of the screen

The new upstream url for the Xorg bug is
https://gitlab.freedesktop.org/xorg/xserver/issues/577

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

** Changed in: xorg-server
   Importance: Medium => Undecided

** Changed in: xorg-server
   Status: Unknown => New

** Changed in: xorg-server
 Remote watch: freedesktop.org Bugzilla #92681 => None

** Also affects: xfce4-panel (Ubuntu Disco)
   Importance: Undecided
 Assignee: Simon Steinbeiß (ochosi)
   Status: Confirmed

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

** Also affects: greybird-gtk-theme (Ubuntu Disco)
   Importance: Undecided
   Status: New

** Also affects: xfce4-panel (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

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

** Also affects: greybird-gtk-theme (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

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

Title:
  XFCE window buttons are not clickable at the top of the screen

Status in X.Org X server:
  New
Status in greybird-gtk-theme package in Ubuntu:
  New
Status in xfce4-panel package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed
Status in greybird-gtk-theme source package in Cosmic:
  New
Status in xfce4-panel source package in Cosmic:
  New
Status in xorg-server source package in Cosmic:
  New
Status in greybird-gtk-theme source package in Disco:
  New
Status in xfce4-panel source package in Disco:
  Confirmed
Status in xorg-server source package in Disco:
  Confirmed

Bug description:
  This bug affects greybird-gtk-theme and xfce4-panel in Xubuntu Cosmic.

  With Cosmic, it is not possible to click on the window buttons after
  moving the mouse cursor to the top of the screen. Unlike similar bugs,
  no amount of moving left or right triggers the hover event or the
  ability to click on the window button.

  With Adwaita and Numix, we see the same issues we see elsewhere, where
  the buttons can sometimes be clicked, but also have issue with the
  topmost part of the screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: greybird-gtk-theme 3.22.9-0ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Sep 29 09:05:24 2018
  InstallationDate: Installed on 2018-09-29 (0 days ago)
  InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180929)
  PackageArchitecture: all
  SourcePackage: greybird-gtk-theme
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1795135/+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 1818395] [NEW] Please demote lightdm greeter recommends to suggests