[Touch-packages] [Bug 1330037] Re: [FFe] upower 0.99.1 transition

2014-09-14 Thread Sean Davis
As Xubuntu Technical Lead and on behalf of the Xubuntu Release Team, I
too would like to strongly object to this FFe.

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

Title:
  [FFe] upower 0.99.1 transition

Status in “cairo-dock-plug-ins” package in Ubuntu:
  Fix Committed
Status in “cinnamon-control-center” package in Ubuntu:
  New
Status in “cinnamon-session” package in Ubuntu:
  New
Status in “cinnamon-settings-daemon” package in Ubuntu:
  New
Status in “gnome-applets” package in Ubuntu:
  In Progress
Status in “gnome-control-center” package in Ubuntu:
  In Progress
Status in “gnome-packagekit” package in Ubuntu:
  Fix Released
Status in “gnome-power-manager” package in Ubuntu:
  In Progress
Status in “gnome-session” package in Ubuntu:
  In Progress
Status in “gnome-settings-daemon” package in Ubuntu:
  In Progress
Status in “gnome-shell” package in Ubuntu:
  In Progress
Status in “gnome-shell-pomodoro” package in Ubuntu:
  New
Status in “indicator-power” package in Ubuntu:
  Fix Released
Status in “kde-workspace” package in Ubuntu:
  Fix Released
Status in “mate-applets” package in Ubuntu:
  Fix Released
Status in “mate-power-manager” package in Ubuntu:
  Fix Released
Status in “mate-session-manager” package in Ubuntu:
  Fix Released
Status in “mutter” package in Ubuntu:
  In Progress
Status in “powerd” package in Ubuntu:
  New
Status in “python-dbusmock” package in Ubuntu:
  Fix Released
Status in “razorqt” package in Ubuntu:
  New
Status in “sugar-0.96” package in Ubuntu:
  New
Status in “sugar-0.98” package in Ubuntu:
  New
Status in “telepathy-mission-control-5” package in Ubuntu:
  Fix Released
Status in “tracker” package in Ubuntu:
  Fix Committed
Status in “ubuntu-system-settings” package in Ubuntu:
  Triaged
Status in “unity-control-center” package in Ubuntu:
  New
Status in “unity-settings-daemon” package in Ubuntu:
  New
Status in “upower” package in Ubuntu:
  In Progress
Status in “xfce4-power-manager” package in Ubuntu:
  Fix Committed
Status in “xfce4-session” package in Ubuntu:
  Fix Released
Status in “xfce4-settings” package in Ubuntu:
  In Progress
Status in “xfce4-systemload-plugin” package in Ubuntu:
  Fix Committed
Status in “xfce4-weather-plugin” package in Ubuntu:
  Invalid
Status in “wmbattery” package in Debian:
  Fix Released

Bug description:
  upower 0.99 needs uploading for gnome 3.12 to enter ubuntu. It drops
  the suspend/hibernate functions, as logind now does that. All major
  DEs have support for this,so nearly everything just needs a rebuild.
  This bug tracks the transition.

  A transition is required as some features were removed and the SONAME
  was changed

  All packages (and build logs) are staged in
  https://launchpad.net/~noskcaj/+archive/upower/+packages

  sugar will probably need removing. If a package only needs a rebuild,
  mark it fix commited, if something else is needed, in progress.

  cairo-dock-plug-ins: needs rebuilding
  gnome-shell - ready, just need to drop upower revert.
  gnome-control-center: WIP
  gnome-packagekit: Upower dropped from newest upstream release.
  gnome-power-manager: Fixed in newest upstream release. Merge from debian
  gnome-session: Done in ppa, needs patches from git or new upstream release
  gnome-settings-daemon: 3.12 is ready out of the box, however that also 
requires gnome-desktop transition. 3.8 and also u-s-d: I have a package that is 
mostly working, however had to cherry-pick quite a few patches and may just be 
better to backport 3.12 power plugin. (considering g-s-d patches will be 
temporary, but u-s-d not so)
  kde: works fine with systemd, suspend broken with upstart, no rebuilds needed
  cinnamon: Rebuild
  mate: all mate packages need rebuilding
  python-dbusmock: needs rebuild
  sugar: Upstream bug now filed. Unlikely to be ready in time for 14.10. We 
should remove this from the archive till the next upstream release
  telepathy-mission-control-5: Debian has dropped upower support, so it's done
  wmbattery: needs rebuild
  xfce4-power-manager: Needs rebuilding
  xfce4-session: Fixed already, since we switched to logind
  xfce4-settings: Needs rebuild
  xfce4-systemload-plugin: needs rebuild

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cairo-dock-plug-ins/+bug/1330037/+subscriptions

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


[Touch-packages] [Bug 1379287] [NEW] Blank Volume notification displayed at startup and when scrolling the indicator.

2014-10-09 Thread Sean Davis
Public bug reported:

As of the latest indicator-sound package in Utopic, there is a blank Volume 
notification that is displayed:
1) at system startup.
2) when scrolling the indicator (along with the normal volume indicator).

Please see the attached screenshot.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: indicator-sound 12.10.2+14.10.20141007-0ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-21.28-generic 3.16.4
Uname: Linux 3.16.0-21-generic x86_64
ActionStates: ({'mute': (true, signature '', [false]), 'phone-settings': 
(true, '', []), 'next.gmusicbrowser.desktop': (true, '', []), 'mic-volume': 
(true, '', [1.0]), 'scroll': (true, 'i', []), 
'play-playlist.gmusicbrowser.desktop': (true, 's', []), 
'gmusicbrowser.desktop': (true, '', [{'running': false, 'state': 
'Paused'}]), 'desktop-settings': (true, '', []), 'volume': (true, 'i', 
[0.67987060546875]), 'root': (true, '', [{'title': 'Sound', 
'accessible-desc': 'Volume (67%)', 'icon': ('themed', 
['audio-volume-medium-panel', 'audio-volume-medium', 'audio-volume', 
'audio']), 'visible': true}]), 'previous.gmusicbrowser.desktop': (true, 
'', []), 'play.gmusicbrowser.desktop': (true, '', ['Paused'])},)
ApportVersion: 2.14.7-0ubuntu5
Architecture: amd64
CurrentDesktop: XFCE
Date: Thu Oct  9 06:57:23 2014
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-08-09 (60 days ago)
InstallationMedia: Xubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140809)
SourcePackage: indicator-sound
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: indicator-sound (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug utopic

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

Title:
  Blank Volume notification displayed at startup and when scrolling
  the indicator.

Status in “indicator-sound” package in Ubuntu:
  New

Bug description:
  As of the latest indicator-sound package in Utopic, there is a blank Volume 
notification that is displayed:
  1) at system startup.
  2) when scrolling the indicator (along with the normal volume indicator).

  Please see the attached screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: indicator-sound 12.10.2+14.10.20141007-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-21.28-generic 3.16.4
  Uname: Linux 3.16.0-21-generic x86_64
  ActionStates: ({'mute': (true, signature '', [false]), 'phone-settings': 
(true, '', []), 'next.gmusicbrowser.desktop': (true, '', []), 'mic-volume': 
(true, '', [1.0]), 'scroll': (true, 'i', []), 
'play-playlist.gmusicbrowser.desktop': (true, 's', []), 
'gmusicbrowser.desktop': (true, '', [{'running': false, 'state': 
'Paused'}]), 'desktop-settings': (true, '', []), 'volume': (true, 'i', 
[0.67987060546875]), 'root': (true, '', [{'title': 'Sound', 
'accessible-desc': 'Volume (67%)', 'icon': ('themed', 
['audio-volume-medium-panel', 'audio-volume-medium', 'audio-volume', 
'audio']), 'visible': true}]), 'previous.gmusicbrowser.desktop': (true, 
'', []), 'play.gmusicbrowser.desktop': (true, '', ['Paused'])},)
  ApportVersion: 2.14.7-0ubuntu5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Oct  9 06:57:23 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-08-09 (60 days ago)
  InstallationMedia: Xubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140809)
  SourcePackage: indicator-sound
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1379287] Re: Blank Volume notification displayed at startup and when scrolling the indicator.

2014-10-09 Thread Sean Davis
Attached screenshot of behavior.

** Attachment added: Screenshot
   
https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1379287/+attachment/4229511/+files/Screenshot%20-%2010092014%20-%2007%3A01%3A27%20AM.png

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

Title:
  Blank Volume notification displayed at startup and when scrolling
  the indicator.

Status in “indicator-sound” package in Ubuntu:
  New

Bug description:
  As of the latest indicator-sound package in Utopic, there is a blank Volume 
notification that is displayed:
  1) at system startup.
  2) when scrolling the indicator (along with the normal volume indicator).

  Please see the attached screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: indicator-sound 12.10.2+14.10.20141007-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-21.28-generic 3.16.4
  Uname: Linux 3.16.0-21-generic x86_64
  ActionStates: ({'mute': (true, signature '', [false]), 'phone-settings': 
(true, '', []), 'next.gmusicbrowser.desktop': (true, '', []), 'mic-volume': 
(true, '', [1.0]), 'scroll': (true, 'i', []), 
'play-playlist.gmusicbrowser.desktop': (true, 's', []), 
'gmusicbrowser.desktop': (true, '', [{'running': false, 'state': 
'Paused'}]), 'desktop-settings': (true, '', []), 'volume': (true, 'i', 
[0.67987060546875]), 'root': (true, '', [{'title': 'Sound', 
'accessible-desc': 'Volume (67%)', 'icon': ('themed', 
['audio-volume-medium-panel', 'audio-volume-medium', 'audio-volume', 
'audio']), 'visible': true}]), 'previous.gmusicbrowser.desktop': (true, 
'', []), 'play.gmusicbrowser.desktop': (true, '', ['Paused'])},)
  ApportVersion: 2.14.7-0ubuntu5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Oct  9 06:57:23 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-08-09 (60 days ago)
  InstallationMedia: Xubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140809)
  SourcePackage: indicator-sound
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1559245] Re: Pulseaudio selects HSP instead of A2DP and no way to set default action

2016-03-19 Thread Sean Davis
Changing project to pulseaudio.  This is likely an issue with the
pulseaudio bluetooth components, the kernel, or blueman.

** Package changed: xubuntu-meta (Ubuntu) => pulseaudio (Ubuntu)

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

Title:
  Pulseaudio selects HSP instead of A2DP and no way to set default
  action

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I am trying to use a bluetooth headphone with ubuntu 14.04 and system
  defaults to using HSP. The problem is that Once it connects, it should
  use A2DP and become default device because I am using it from KODI and
  it is very inconvenient to set it from command line. Otherwise HSP is
  providing very bad quality audio. There is no way to set a default
  action, and system does not retain the last set setting. Eg. I can go
  and set the headphones to use A2DP but when I connect next time, it
  switches back to HSP. (I believe it could remember the device from the
  device id at least!)

  I asked about this on launchpad answers and somebody closed it and said I 
should report it as a bug. If you think this shouldn't have been reported as a 
bug, blame the person who closed my question at launchpad answers :) Below is 
the link to it and more information and the ugly workaround I implemented in my 
system:
  https://answers.launchpad.net/ubuntu/+question/288799

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

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


[Touch-packages] [Bug 1562338] Re: Need to upload po files to LP

2016-03-26 Thread Sean Davis
** Package changed: apt (Ubuntu) => ubiquity-slideshow-ubuntu (Ubuntu)

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

Title:
  Need to upload po files to LP

Status in ubiquity-slideshow-ubuntu package in Ubuntu:
  New

Bug description:
  I need to upload translated po file for ubiquity-slideshow-xubuntu-bn

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

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


[Touch-packages] [Bug 1656399] Re: Unable to unlock Xubuntu XFCE session after suspend.

2017-01-17 Thread Sean Davis
** Changed in: light-locker (Ubuntu)
   Importance: Undecided => Critical

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

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

Title:
  Unable to unlock Xubuntu XFCE session after suspend.

Status in light-locker package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  New

Bug description:
  Unable to unlock Xubuntu XFCE session after suspend. I'm presented
  with unlock screen, and entering credentials will redirect to a black
  screen with "This session is locked", and "you will be redirected to
  unlock screen".

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

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


[Touch-packages] [Bug 1627310] Dependencies.txt

2016-09-24 Thread Sean Davis
apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1627310/+attachment/4747750/+files/Dependencies.txt

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

Title:
  Guest session fails to log out

Status in lightdm package in Ubuntu:
  Confirmed
Status in xfce4-session package in Ubuntu:
  Confirmed

Bug description:
  Vanilla Xubuntu install. When logging out from the guest session,
  everything is closed and the desktop wallpaper is the only thing that
  remains. The user is never returned to the login screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xfce4-session 4.12.1-3ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6
  Uname: Linux 4.8.0-11-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Sep 24 09:18:31 2016
  InstallationDate: Installed on 2016-09-24 (0 days ago)
  InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160921)
  SourcePackage: xfce4-session
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.10
  InstallationDate: Installed on 2016-09-24 (0 days ago)
  InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160921)
  Package: lightdm 1.19.4-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6
  Tags:  yakkety
  Uname: Linux 4.8.0-11-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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


[Touch-packages] [Bug 1627310] JournalErrors.txt

2016-09-24 Thread Sean Davis
apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1627310/+attachment/4747751/+files/JournalErrors.txt

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

Title:
  Guest session fails to log out

Status in lightdm package in Ubuntu:
  Confirmed
Status in xfce4-session package in Ubuntu:
  Confirmed

Bug description:
  Vanilla Xubuntu install. When logging out from the guest session,
  everything is closed and the desktop wallpaper is the only thing that
  remains. The user is never returned to the login screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xfce4-session 4.12.1-3ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6
  Uname: Linux 4.8.0-11-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Sep 24 09:18:31 2016
  InstallationDate: Installed on 2016-09-24 (0 days ago)
  InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160921)
  SourcePackage: xfce4-session
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.10
  InstallationDate: Installed on 2016-09-24 (0 days ago)
  InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160921)
  Package: lightdm 1.19.4-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6
  Tags:  yakkety
  Uname: Linux 4.8.0-11-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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


[Touch-packages] [Bug 1627310] Re: Guest session fails to log out

2016-09-24 Thread Sean Davis
Comments #2 - 8 are from using apport-collect with lightdm

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

Title:
  Guest session fails to log out

Status in lightdm package in Ubuntu:
  Confirmed
Status in xfce4-session package in Ubuntu:
  Confirmed

Bug description:
  Vanilla Xubuntu install. When logging out from the guest session,
  everything is closed and the desktop wallpaper is the only thing that
  remains. The user is never returned to the login screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xfce4-session 4.12.1-3ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6
  Uname: Linux 4.8.0-11-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Sep 24 09:18:31 2016
  InstallationDate: Installed on 2016-09-24 (0 days ago)
  InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160921)
  SourcePackage: xfce4-session
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.10
  InstallationDate: Installed on 2016-09-24 (0 days ago)
  InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160921)
  Package: lightdm 1.19.4-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6
  Tags:  yakkety
  Uname: Linux 4.8.0-11-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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


[Touch-packages] [Bug 1627310] LightdmGreeterLog.txt

2016-09-24 Thread Sean Davis
apport information

** Attachment added: "LightdmGreeterLog.txt"
   
https://bugs.launchpad.net/bugs/1627310/+attachment/4747753/+files/LightdmGreeterLog.txt

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

Title:
  Guest session fails to log out

Status in lightdm package in Ubuntu:
  Confirmed
Status in xfce4-session package in Ubuntu:
  Confirmed

Bug description:
  Vanilla Xubuntu install. When logging out from the guest session,
  everything is closed and the desktop wallpaper is the only thing that
  remains. The user is never returned to the login screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xfce4-session 4.12.1-3ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6
  Uname: Linux 4.8.0-11-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Sep 24 09:18:31 2016
  InstallationDate: Installed on 2016-09-24 (0 days ago)
  InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160921)
  SourcePackage: xfce4-session
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.10
  InstallationDate: Installed on 2016-09-24 (0 days ago)
  InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160921)
  Package: lightdm 1.19.4-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6
  Tags:  yakkety
  Uname: Linux 4.8.0-11-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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


[Touch-packages] [Bug 1627310] LightdmDisplayLog.txt

2016-09-24 Thread Sean Davis
apport information

** Attachment added: "LightdmDisplayLog.txt"
   
https://bugs.launchpad.net/bugs/1627310/+attachment/4747752/+files/LightdmDisplayLog.txt

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

Title:
  Guest session fails to log out

Status in lightdm package in Ubuntu:
  Confirmed
Status in xfce4-session package in Ubuntu:
  Confirmed

Bug description:
  Vanilla Xubuntu install. When logging out from the guest session,
  everything is closed and the desktop wallpaper is the only thing that
  remains. The user is never returned to the login screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xfce4-session 4.12.1-3ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6
  Uname: Linux 4.8.0-11-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Sep 24 09:18:31 2016
  InstallationDate: Installed on 2016-09-24 (0 days ago)
  InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160921)
  SourcePackage: xfce4-session
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.10
  InstallationDate: Installed on 2016-09-24 (0 days ago)
  InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160921)
  Package: lightdm 1.19.4-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6
  Tags:  yakkety
  Uname: Linux 4.8.0-11-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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


[Touch-packages] [Bug 1627310] LightdmLog.txt

2016-09-24 Thread Sean Davis
apport information

** Attachment added: "LightdmLog.txt"
   
https://bugs.launchpad.net/bugs/1627310/+attachment/4747754/+files/LightdmLog.txt

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

Title:
  Guest session fails to log out

Status in lightdm package in Ubuntu:
  Confirmed
Status in xfce4-session package in Ubuntu:
  Confirmed

Bug description:
  Vanilla Xubuntu install. When logging out from the guest session,
  everything is closed and the desktop wallpaper is the only thing that
  remains. The user is never returned to the login screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xfce4-session 4.12.1-3ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6
  Uname: Linux 4.8.0-11-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Sep 24 09:18:31 2016
  InstallationDate: Installed on 2016-09-24 (0 days ago)
  InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160921)
  SourcePackage: xfce4-session
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.10
  InstallationDate: Installed on 2016-09-24 (0 days ago)
  InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160921)
  Package: lightdm 1.19.4-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6
  Tags:  yakkety
  Uname: Linux 4.8.0-11-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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


[Touch-packages] [Bug 1627310] LightdmUsersConfig.txt

2016-09-24 Thread Sean Davis
apport information

** Attachment added: "LightdmUsersConfig.txt"
   
https://bugs.launchpad.net/bugs/1627310/+attachment/4747755/+files/LightdmUsersConfig.txt

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

Title:
  Guest session fails to log out

Status in lightdm package in Ubuntu:
  Confirmed
Status in xfce4-session package in Ubuntu:
  Confirmed

Bug description:
  Vanilla Xubuntu install. When logging out from the guest session,
  everything is closed and the desktop wallpaper is the only thing that
  remains. The user is never returned to the login screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xfce4-session 4.12.1-3ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6
  Uname: Linux 4.8.0-11-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Sep 24 09:18:31 2016
  InstallationDate: Installed on 2016-09-24 (0 days ago)
  InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160921)
  SourcePackage: xfce4-session
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.10
  InstallationDate: Installed on 2016-09-24 (0 days ago)
  InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160921)
  Package: lightdm 1.19.4-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6
  Tags:  yakkety
  Uname: Linux 4.8.0-11-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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


[Touch-packages] [Bug 1627310] ProcEnviron.txt

2016-09-24 Thread Sean Davis
apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1627310/+attachment/4747756/+files/ProcEnviron.txt

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

Title:
  Guest session fails to log out

Status in lightdm package in Ubuntu:
  Confirmed
Status in xfce4-session package in Ubuntu:
  Confirmed

Bug description:
  Vanilla Xubuntu install. When logging out from the guest session,
  everything is closed and the desktop wallpaper is the only thing that
  remains. The user is never returned to the login screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xfce4-session 4.12.1-3ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6
  Uname: Linux 4.8.0-11-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Sep 24 09:18:31 2016
  InstallationDate: Installed on 2016-09-24 (0 days ago)
  InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160921)
  SourcePackage: xfce4-session
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.10
  InstallationDate: Installed on 2016-09-24 (0 days ago)
  InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160921)
  Package: lightdm 1.19.4-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6
  Tags:  yakkety
  Uname: Linux 4.8.0-11-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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


[Touch-packages] [Bug 1622303] Re: Fails to unlock/ resumes to black screen

2016-09-24 Thread Sean Davis
I tagged LightDM and LightDM GTK+ Greeter since they may be directly
related.

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

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

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

Title:
  Fails to unlock/ resumes to black screen

Status in light-locker package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  New
Status in lightdm-gtk-greeter package in Ubuntu:
  New

Bug description:
  Lock screen (or suspend)

  System allows for password to unlock

  No desktop shown after unlocking

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xfce4-power-manager 1.4.4-4ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
  Uname: Linux 4.4.0-9136-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sun Sep 11 10:04:39 2016
  InstallationDate: Installed on 2016-06-11 (91 days ago)
  InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160611)
  SourcePackage: xfce4-power-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.10
  InstallationDate: Installed on 2016-06-11 (95 days ago)
  InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160611)
  Package: light-locker 1.7.0-2ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
  Tags:  yakkety
  Uname: Linux 4.4.0-9136-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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


[Touch-packages] [Bug 1627310] [NEW] Guest session fails to log out

2016-09-24 Thread Sean Davis
Public bug reported:

Vanilla Xubuntu install. When logging out from the guest session,
everything is closed and the desktop wallpaper is the only thing that
remains. The user is never returned to the login screen.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: xfce4-session 4.12.1-3ubuntu2
ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6
Uname: Linux 4.8.0-11-generic x86_64
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
CurrentDesktop: XFCE
Date: Sat Sep 24 09:18:31 2016
InstallationDate: Installed on 2016-09-24 (0 days ago)
InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160921)
SourcePackage: xfce4-session
UpgradeStatus: No upgrade log present (probably fresh install)
--- 
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
CurrentDesktop: XFCE
DistroRelease: Ubuntu 16.10
InstallationDate: Installed on 2016-09-24 (0 days ago)
InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160921)
Package: lightdm 1.19.4-0ubuntu1
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6
Tags:  yakkety
Uname: Linux 4.8.0-11-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True

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

** Affects: xfce4-session (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: amd64 apport-bug apport-collected yakkety

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

** Tags added: apport-collected

** Description changed:

  Vanilla Xubuntu install. When logging out from the guest session,
  everything is closed and the desktop wallpaper is the only thing that
  remains. The user is never returned to the login screen.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xfce4-session 4.12.1-3ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6
  Uname: Linux 4.8.0-11-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Sep 24 09:18:31 2016
  InstallationDate: Installed on 2016-09-24 (0 days ago)
  InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160921)
  SourcePackage: xfce4-session
  UpgradeStatus: No upgrade log present (probably fresh install)
+ --- 
+ ApportVersion: 2.20.3-0ubuntu7
+ Architecture: amd64
+ CurrentDesktop: XFCE
+ DistroRelease: Ubuntu 16.10
+ InstallationDate: Installed on 2016-09-24 (0 days ago)
+ InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160921)
+ Package: lightdm 1.19.4-0ubuntu1
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6
+ Tags:  yakkety
+ Uname: Linux 4.8.0-11-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True

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

Title:
  Guest session fails to log out

Status in lightdm package in Ubuntu:
  Confirmed
Status in xfce4-session package in Ubuntu:
  Confirmed

Bug description:
  Vanilla Xubuntu install. When logging out from the guest session,
  everything is closed and the desktop wallpaper is the only thing that
  remains. The user is never returned to the login screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xfce4-session 4.12.1-3ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6
  Uname: Linux 4.8.0-11-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Sep 24 09:18:31 2016
  InstallationDate: Installed on 2016-09-24 (0 days ago)
  InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160921)
  SourcePackage: xfce4-session
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.10
  InstallationDate: Installed on 2016-09-24 (0 days ago)
  InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160921)
  Package: lightdm 1.19.4-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6
  Tags:  yakkety
  Uname: Linux 4.8.0-11-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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


[Touch-packages] [Bug 1622303] Re: Fails to unlock/ resumes to black screen

2016-09-27 Thread Sean Davis
I tried downgrading lightdm (and related packages) to their xenial
versions (1.18.x) and the bug persists, so it seems less likely to be
directly related to lightdm.

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

Title:
  Fails to unlock/ resumes to black screen

Status in light-locker package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  New
Status in lightdm-gtk-greeter package in Ubuntu:
  New

Bug description:
  Lock screen (or suspend)

  System allows for password to unlock

  No desktop shown after unlocking

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xfce4-power-manager 1.4.4-4ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
  Uname: Linux 4.4.0-9136-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sun Sep 11 10:04:39 2016
  InstallationDate: Installed on 2016-06-11 (91 days ago)
  InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160611)
  SourcePackage: xfce4-power-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.10
  InstallationDate: Installed on 2016-06-11 (95 days ago)
  InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160611)
  Package: light-locker 1.7.0-2ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
  Tags:  yakkety
  Uname: Linux 4.4.0-9136-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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


[Touch-packages] [Bug 1622303] Re: Fails to unlock/ resumes to black screen

2016-09-28 Thread Sean Davis
@flocculant Thanks for looking into this. I spoke with pitti about this
and we correctly identified the issue being related to the session
switch to system user units. For now, we'll roll back the session
changes.

Affected packages: xfce4-session, xubuntu-default-settings

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

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

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

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

** Changed in: xubuntu-default-settings (Ubuntu)
 Assignee: (unassigned) => Sean Davis (bluesabre)

** Changed in: xubuntu-default-settings (Ubuntu)
   Status: New => In Progress

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

Title:
  Fails to unlock/ resumes to black screen

Status in light-locker package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  New
Status in lightdm-gtk-greeter package in Ubuntu:
  New
Status in xfce4-session package in Ubuntu:
  In Progress
Status in xubuntu-default-settings package in Ubuntu:
  In Progress

Bug description:
  Lock screen (or suspend)

  System allows for password to unlock

  No desktop shown after unlocking

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xfce4-power-manager 1.4.4-4ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
  Uname: Linux 4.4.0-9136-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sun Sep 11 10:04:39 2016
  InstallationDate: Installed on 2016-06-11 (91 days ago)
  InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160611)
  SourcePackage: xfce4-power-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.10
  InstallationDate: Installed on 2016-06-11 (95 days ago)
  InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160611)
  Package: light-locker 1.7.0-2ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
  Tags:  yakkety
  Uname: Linux 4.4.0-9136-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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


[Touch-packages] [Bug 1643129] Re: Drop system-config-printer-gnome package

2016-12-03 Thread Sean Davis
** Also affects: xubuntu-meta (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Drop system-config-printer-gnome package

Status in Ubuntu GNOME:
  Triaged
Status in system-config-printer package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  New
Status in xubuntu-meta package in Ubuntu:
  New

Bug description:
  I don't think the system-config-printer-gnome split makes sense any
  more and it would be nice to get this package closer in sync with
  Debian. In other words, let's drop system-config-printer-gnome and
  move most of its contents back to system-config-printer but a few
  files will end up in system-config-printer-common.

  The last explicit merge was almost a decade ago:
  https://launchpad.net/ubuntu/+source/system-config-printer/0.7.70-1ubuntu1 )

  The split was done in 2008 for KDE's benefit:
  
https://launchpad.net/ubuntu/+source/system-config-printer/0.7.78+svn1799-0ubuntu2

  - system-config-printer-kde no longer exists (it appears to have been
  part of the kdeadmin source package which was removed a few years ago)

  - Kubuntu only ships system-config-printer-udev so they aren't affected now
  
http://cdimage.ubuntu.com/cdimage/kubuntu/daily-live/current/zesty-desktop-amd64.manifest

  - Ubuntu GNOME does not need the files shipped in system-config-
  printer since GNOME has its own integrated Printers Settings panel.

  https://packages.debian.org/sid/all/system-config-printer/filelist

  In Ubuntu 16.10 I attempted to follow Debian's gnome-control-center
  packaging and depend on system-config-printer-common only, but it
  broke the Printers panel since Ubuntu's packaging moved the dbus
  service to the system-config-printer-gnome package (See bug 1496860 &
  bug 1623150 & bug 1637466 ).

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

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


[Touch-packages] [Bug 1686081] Re: If -synaptics is installed, GNOME Mouse & Touchpad Settings doesn't work

2017-09-18 Thread Sean Davis
Xfce still needs -synaptics, addressed with http://bazaar.launchpad.net
/~xubuntu-dev/ubuntu-seeds/xubuntu.artful/revision/1015

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

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

Title:
  If -synaptics is installed, GNOME Mouse & Touchpad Settings doesn't
  work

Status in xorg package in Ubuntu:
  Confirmed
Status in xubuntu-meta package in Ubuntu:
  New

Bug description:
  I'm splitting this issue off from LP: #1685542 (which made xserver-
  xorg-input-all no longer recommend xserver-xorg-input-synaptics) for
  tracking the remaining issues.

  gnome-control-center only supports libinput. If xserver-xorg-input-
  synaptics is installed (because it's used by some desktops which
  haven't been ported to libinput yet), synaptics overrides libinput.
  That makes gnome-control-center's Mouse & Touchpad settings panel only
  show basic settings and important configurations don't work.

  Questions
  -
  1. Which desktops/apps still need -synaptics?
  - Unity
  - Xfce?
  - LXDE? LXQt?
  All the other major desktops have already been ported (LP: #1417980)

  2. Can these apps be ported or removed before 18.04 LTS is released?

  3. Can the desktops be ported and how bad is it if they are not ported
  and -synaptics is no longer available?

  4. If -synaptics can't be removed completely from 18.04 LTS, does it
  make sense to have gnome-control-center Conflicts: xserver-xorg-input-
  synaptics?

  5. Is there any other way we can fix this conflict?

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

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


[Touch-packages] [Bug 1754836] Re: Xubuntu: ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to activate service

2018-03-13 Thread Sean Davis
This might be related to the undocumented addition of pulseaudio-module-
bluetooth to blueman 2.0.5-1

http://launchpadlibrarian.net/345214644/blueman_2.0.4-1ubuntu3_2.0.5-1ubuntu1.diff.gz

diff -Nru blueman-2.0.4/debian/control blueman-2.0.5/debian/control
--- blueman-2.0.4/debian/control2016-03-30 04:43:33.0 +
+++ blueman-2.0.5/debian/control2017-11-10 10:13:52.0 +
@@ -19,7 +19,7 @@
  libpulse-mainloop-glib0, gir1.2-gtk-3.0, gir1.2-gdkpixbuf-2.0,
  gir1.2-glib-2.0, gir1.2-pango-1.0, gir1.2-notify-0.7, python3-cairo,
  python3-gi-cairo, gir1.2-appindicator3-0.1
-Recommends: policykit-1
+Recommends: policykit-1, pulseaudio-module-bluetooth
 Description: Graphical bluetooth manager
  Blueman is a GTK+ bluetooth management utility for GNOME using bluez D-Bus

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

Title:
  Xubuntu: ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez:
  dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut:
  Failed to activate service 'org.bluez': timed out
  (service_start_timeout=25000ms)

Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Xubuntu seeing long first time boot to desktop from login.

  Possibly also causing the long time to desktop from try/install
  livesession dialogue.

  Including xsession-errors from the first time boot on installed
  system.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  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 11:32:59 2018
  InstallationDate: Installed on 2018-03-08 (1 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  InterestingModules: bluetooth
  MachineType: NOVATECH LTD MBB-44608
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=8d9f054a-4c7a-481f-966e-fc2cd6f51aca ro quiet splash
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/19/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-DS2V
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: 7383241-001
  dmi.chassis.type: 3
  dmi.chassis.vendor: NOVATECH LTD
  dmi.chassis.version: V1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnMBB-44608:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0:
  dmi.product.family: AMI PLATFORM
  dmi.product.name: MBB-44608
  dmi.product.version: V1.0
  dmi.sys.vendor: NOVATECH LTD
  hciconfig:
   
  rfkill:
   
  syslog: Mar 10 11:30:16 test-MBB-44608 NetworkManager[679]:   
[1520681416.8951] Loaded device plugin: NMBluezManager 
(/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so)

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

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


[Touch-packages] [Bug 1754872] Re: gnome-control-center is unusable on xubuntu-desktop, but called from Gear (About this Computer, System Settings) icon, Text Entry Settings, clock (Time & Date Settin

2018-03-13 Thread Sean Davis
This does not affect a base install of Xubuntu, but one that is shared
with other installed sessions that pull in the GNOME Control Center and
the Date Time Indicator.

The GNOME Control Center only displays it's configuration tools inside
of a GNOME or GNOME-like environment, and will just show up blank
anywhere else.

To populate these settings, just launch the control center with the
below command.

env XDG_CURRENT_DESKTOP=GNOME gnome-control-center

Moving this bug to indicator-datetime since it could be made aware of
the running desktop and gnome-control-center since it seems to be an
intentional functionality of the GNOME desktop.

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

** Also affects: gnome-control-center (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: xubuntu-meta (Ubuntu)

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

Title:
  gnome-control-center is unusable on xubuntu-desktop, but called from
  Gear (About this Computer, System Settings) icon, Text Entry Settings,
  clock (Time & Date Settings)

Status in gnome-control-center package in Ubuntu:
  New
Status in indicator-datetime package in Ubuntu:
  New

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/gnome-control-center/+bug/1754872/+subscriptions

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


[Touch-packages] [Bug 1754888] Re: Menulibre: invalid desktop files detected!

2018-03-13 Thread Sean Davis
Pushed a fix for lp:xubuntu-default-settings,
https://bazaar.launchpad.net/~xubuntu-dev/xubuntu-default-
settings/trunk/revision/666

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

Title:
  Menulibre: invalid desktop files detected!

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

Bug description:
  Not sure whether to report this as a bug, but:

  Running xubuntu 18.04, updated.

  Linux Xubuntu-18-04 4.15.0-10-generic #11-Ubuntu SMP Tue Feb 13
  18:23:35 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  Menulibre 2.1.5

  On starting menulibre I get a warning: Menulibre: invalid desktop
  files detected!

  See: http://i.imgur.com/Jqdge9z.png

  If I click on details, I get:

  http://i.imgur.com/H7RwsOO.png

  I think these invalid desktop files are part of the initial installation of 
menulibre/xubuntu.
  As a simple end user I do not know what to do with this warning.

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

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


[Touch-packages] [Bug 1754888] Re: Menulibre: invalid desktop files detected!

2018-03-13 Thread Sean Davis
After reviewing the package for vim, it doesn't seem like there's a good
way to resolve this issue for the vim source package. So this leaves two
options.

1) Xubuntu provides vim instead of vim-tiny.
2) MenuLibre adds a way to ignore errors, and Xubuntu provides this override 
for the base install.

It's still reasonable to leave this bug open since the provided .desktop
file is invalid.

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

Title:
  Menulibre: invalid desktop files detected!

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

Bug description:
  Not sure whether to report this as a bug, but:

  Running xubuntu 18.04, updated.

  Linux Xubuntu-18-04 4.15.0-10-generic #11-Ubuntu SMP Tue Feb 13
  18:23:35 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  Menulibre 2.1.5

  On starting menulibre I get a warning: Menulibre: invalid desktop
  files detected!

  See: http://i.imgur.com/Jqdge9z.png

  If I click on details, I get:

  http://i.imgur.com/H7RwsOO.png

  I think these invalid desktop files are part of the initial installation of 
menulibre/xubuntu.
  As a simple end user I do not know what to do with this warning.

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

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


[Touch-packages] [Bug 1754888] Re: Menulibre: invalid desktop files detected!

2018-03-13 Thread Sean Davis
xubuntu-default-settings, affected files:

/usr/share/xubuntu/applications/Thunar-bulk-rename.desktop
/usr/share/xubuntu/applications/Thunar.desktop
/usr/share/xubuntu/applications/debian-uxterm.desktop
/usr/share/xubuntu/applications/debian-xterm.desktop
/usr/share/xubuntu/applications/thunar-settings.desktop
/usr/share/xubuntu/applications/xfce4-terminal.desktop

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

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

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

Title:
  Menulibre: invalid desktop files detected!

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

Bug description:
  Not sure whether to report this as a bug, but:

  Running xubuntu 18.04, updated.

  Linux Xubuntu-18-04 4.15.0-10-generic #11-Ubuntu SMP Tue Feb 13
  18:23:35 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  Menulibre 2.1.5

  On starting menulibre I get a warning: Menulibre: invalid desktop
  files detected!

  See: http://i.imgur.com/Jqdge9z.png

  If I click on details, I get:

  http://i.imgur.com/H7RwsOO.png

  I think these invalid desktop files are part of the initial installation of 
menulibre/xubuntu.
  As a simple end user I do not know what to do with this warning.

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

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


[Touch-packages] [Bug 1754888] Re: Menulibre: invalid desktop files detected!

2018-03-13 Thread Sean Davis
vim, affected file:

/usr/share/applications/vim.desktop

This file is provided by the vim-common package, which is required by
vim-tiny package, but provides a launcher for the vim binary, which is
provided by the vim package.

** No longer affects: menulibre

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

Title:
  Menulibre: invalid desktop files detected!

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

Bug description:
  Not sure whether to report this as a bug, but:

  Running xubuntu 18.04, updated.

  Linux Xubuntu-18-04 4.15.0-10-generic #11-Ubuntu SMP Tue Feb 13
  18:23:35 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  Menulibre 2.1.5

  On starting menulibre I get a warning: Menulibre: invalid desktop
  files detected!

  See: http://i.imgur.com/Jqdge9z.png

  If I click on details, I get:

  http://i.imgur.com/H7RwsOO.png

  I think these invalid desktop files are part of the initial installation of 
menulibre/xubuntu.
  As a simple end user I do not know what to do with this warning.

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

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


[Touch-packages] [Bug 1754836] Re: Xubuntu: ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to activate service

2018-04-03 Thread Sean Davis
If this bug does not affect Ubuntu directly, this is a list of shared
differences that Ubuntu MATE and Xubuntu have with Ubuntu. Hopefully
this can help identify where the issue exists.

** Attachment added: "Differences with Ubuntu"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1754836/+attachment/5099620/+files/ubuntu_vs_mate_and_xubuntu.txt

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

Title:
  Xubuntu: ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez:
  dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut:
  Failed to activate service 'org.bluez': timed out
  (service_start_timeout=25000ms)

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

Bug description:
  Xubuntu seeing long first time boot to desktop from login.

  Also causing the long time to desktop from try/install livesession
  dialogue.

  Including xsession-errors from the first time boot on installed
  system.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  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 11:32:59 2018
  InstallationDate: Installed on 2018-03-08 (1 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  InterestingModules: bluetooth
  MachineType: NOVATECH LTD MBB-44608
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=8d9f054a-4c7a-481f-966e-fc2cd6f51aca ro quiet splash
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/19/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-DS2V
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: 7383241-001
  dmi.chassis.type: 3
  dmi.chassis.vendor: NOVATECH LTD
  dmi.chassis.version: V1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnMBB-44608:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0:
  dmi.product.family: AMI PLATFORM
  dmi.product.name: MBB-44608
  dmi.product.version: V1.0
  dmi.sys.vendor: NOVATECH LTD
  hciconfig:

  rfkill:

  syslog: Mar 10 11:30:16 test-MBB-44608 NetworkManager[679]: 
  [1520681416.8951] Loaded device plugin: NMBluezManager
  (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-
  bluetooth.so)

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

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


[Touch-packages] [Bug 1754836] Re: Xubuntu: ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to activate service

2018-04-03 Thread Sean Davis
Since it seemed like this issue was coming from bluez or blueman, I did
some package removal tests and was surprised by the results. These were
done in order, which all packages removed in the previous step still
removed in the following step.

1. Remove pulseaudio-module-bluetooth, no change.
2. Remove blueman, no change.
3. Remove bluez, bluez-cups, bluez-obexd, no change.
4. Autoremoved libbluetooth3 (brltty brltty-x11 libbluetooth3 network-manager 
network-manager-gnome network-manager-pptp network-manager-pptp-gnome), and 
still no change.

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

Title:
  Xubuntu: ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez:
  dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut:
  Failed to activate service 'org.bluez': timed out
  (service_start_timeout=25000ms)

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

Bug description:
  Xubuntu seeing long first time boot to desktop from login.

  Also causing the long time to desktop from try/install livesession
  dialogue.

  Including xsession-errors from the first time boot on installed
  system.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  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 11:32:59 2018
  InstallationDate: Installed on 2018-03-08 (1 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  InterestingModules: bluetooth
  MachineType: NOVATECH LTD MBB-44608
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=8d9f054a-4c7a-481f-966e-fc2cd6f51aca ro quiet splash
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/19/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-DS2V
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: 7383241-001
  dmi.chassis.type: 3
  dmi.chassis.vendor: NOVATECH LTD
  dmi.chassis.version: V1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnMBB-44608:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0:
  dmi.product.family: AMI PLATFORM
  dmi.product.name: MBB-44608
  dmi.product.version: V1.0
  dmi.sys.vendor: NOVATECH LTD
  hciconfig:

  rfkill:

  syslog: Mar 10 11:30:16 test-MBB-44608 NetworkManager[679]: 
  [1520681416.8951] Loaded device plugin: NMBluezManager
  (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-
  bluetooth.so)

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

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


[Touch-packages] [Bug 1754872] Re: gnome-control-center is unusable on xubuntu-desktop, but called from Gear (About this Computer, System Settings) icon, Text Entry Settings, clock (Time & Date Settin

2018-04-19 Thread Sean Davis
I just tried using the netboot iso and installed the Xubuntu Desktop
task. Once installation finished and rebooted, I have a pristine Xubuntu
desktop with no additional indicators.

dpkg -l listing attached.

I will try another mini iso without a selected desktop if possible.

** Attachment added: "dpkg after Xubuntu Desktop task installation"
   
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1754872/+attachment/5122515/+files/dpkg_output.txt

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

Title:
  gnome-control-center is unusable on xubuntu-desktop, but called from
  Gear (About this Computer, System Settings) icon, Text Entry Settings,
  clock (Time & Date Settings)

Status in gnome-control-center package in Ubuntu:
  New
Status in indicator-datetime package in Ubuntu:
  New
Status in xubuntu-meta package in Ubuntu:
  New

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/gnome-control-center/+bug/1754872/+subscriptions

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


[Touch-packages] [Bug 1754836] Re: Xubuntu: ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to activate service

2018-03-31 Thread Sean Davis
Turned up the importance for this bug. For a user, a 75-second wait time
when they are used to 0-10 would be an indication there is a serious bug
and the software (Xubuntu, Ubuntu MATE, and anything else yet
unidentified) does not run on their system.

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

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

Title:
  Xubuntu: ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez:
  dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut:
  Failed to activate service 'org.bluez': timed out
  (service_start_timeout=25000ms)

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

Bug description:
  Xubuntu seeing long first time boot to desktop from login.

  Also causing the long time to desktop from try/install livesession
  dialogue.

  Including xsession-errors from the first time boot on installed
  system.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  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 11:32:59 2018
  InstallationDate: Installed on 2018-03-08 (1 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  InterestingModules: bluetooth
  MachineType: NOVATECH LTD MBB-44608
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=8d9f054a-4c7a-481f-966e-fc2cd6f51aca ro quiet splash
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/19/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-DS2V
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: 7383241-001
  dmi.chassis.type: 3
  dmi.chassis.vendor: NOVATECH LTD
  dmi.chassis.version: V1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnMBB-44608:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0:
  dmi.product.family: AMI PLATFORM
  dmi.product.name: MBB-44608
  dmi.product.version: V1.0
  dmi.sys.vendor: NOVATECH LTD
  hciconfig:

  rfkill:

  syslog: Mar 10 11:30:16 test-MBB-44608 NetworkManager[679]: 
  [1520681416.8951] Loaded device plugin: NMBluezManager
  (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-
  bluetooth.so)

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

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


[Touch-packages] [Bug 1760073] Re: No network from suspend resume

2018-03-31 Thread Sean Davis
Not seeing this on my machine, so it may be kernel related.

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

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

Title:
  No network from suspend resume

Status in lightdm package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  Following a resume from suspend - no network available on machine.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: lightdm 1.25.2-0ubuntu1
  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: Fri Mar 30 11:53:22 2018
  InstallationDate: Installed on 2018-03-08 (21 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  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/1760073/+subscriptions

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


[Touch-packages] [Bug 1760078] Re: Double login required from suspend

2018-03-31 Thread Sean Davis
Not seeing this currently. I have seen this in the past when VT
switching from the lock screen.

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

Title:
  Double login required from suspend

Status in lightdm package in Ubuntu:
  New

Bug description:
  Following a suspend.

  Get unlock screen - which then gets me a desktop.

  Returned to unlock screen to enter password a second time.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: lightdm 1.25.2-0ubuntu1
  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: Fri Mar 30 12:09:46 2018
  InstallationDate: Installed on 2018-03-08 (21 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  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/1760078/+subscriptions

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


[Touch-packages] [Bug 1754888] Re: Menulibre: invalid desktop files detected!

2018-03-16 Thread Sean Davis
Vim's desktop file is actually working as expected here. The TryExec key
is used to determine if the desktop file is usable... and when the vim
binary is missing, it is not.

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

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

** Also affects: menulibre
   Importance: Undecided
   Status: New

** Changed in: menulibre
   Status: New => Fix Committed

** Changed in: menulibre
 Assignee: (unassigned) => Sean Davis (bluesabre)

** Changed in: menulibre
Milestone: None => 2.2.0

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

Title:
  Menulibre: invalid desktop files detected!

Status in MenuLibre:
  Fix Committed
Status in menulibre package in Ubuntu:
  New
Status in vim package in Ubuntu:
  Invalid
Status in xubuntu-default-settings package in Ubuntu:
  New

Bug description:
  Not sure whether to report this as a bug, but:

  Running xubuntu 18.04, updated.

  Linux Xubuntu-18-04 4.15.0-10-generic #11-Ubuntu SMP Tue Feb 13
  18:23:35 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  Menulibre 2.1.5

  On starting menulibre I get a warning: Menulibre: invalid desktop
  files detected!

  See: http://i.imgur.com/Jqdge9z.png

  If I click on details, I get:

  http://i.imgur.com/H7RwsOO.png

  I think these invalid desktop files are part of the initial installation of 
menulibre/xubuntu.
  As a simple end user I do not know what to do with this warning.

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

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


[Touch-packages] [Bug 1754888] Re: Menulibre: invalid desktop files detected!

2018-03-16 Thread Sean Davis
** Changed in: menulibre
   Status: Fix Committed => Fix Released

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

Title:
  Menulibre: invalid desktop files detected!

Status in MenuLibre:
  Fix Released
Status in menulibre package in Ubuntu:
  New
Status in vim package in Ubuntu:
  Invalid
Status in xubuntu-default-settings package in Ubuntu:
  New

Bug description:
  Not sure whether to report this as a bug, but:

  Running xubuntu 18.04, updated.

  Linux Xubuntu-18-04 4.15.0-10-generic #11-Ubuntu SMP Tue Feb 13
  18:23:35 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  Menulibre 2.1.5

  On starting menulibre I get a warning: Menulibre: invalid desktop
  files detected!

  See: http://i.imgur.com/Jqdge9z.png

  If I click on details, I get:

  http://i.imgur.com/H7RwsOO.png

  I think these invalid desktop files are part of the initial installation of 
menulibre/xubuntu.
  As a simple end user I do not know what to do with this warning.

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

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


[Touch-packages] [Bug 1693038] Re: needs to support restart on Lubuntu and Xubuntu

2018-03-01 Thread Sean Davis
Hi Brian! With bug 1693032 being marked as fixed today, I just wanted to
make sure this fix would still be considered before Bionic goes stable.

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

Title:
  needs to support restart on Lubuntu and Xubuntu

Status in software-properties package in Ubuntu:
  Triaged

Bug description:
  The fix for bug 1241210 only works in gnome-session based sessions.
  Let's make sure that the driver restart button works on Xubuntu and
  Lubuntu.

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

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


[Touch-packages] [Bug 1818395] [NEW] Please demote lightdm greeter recommends to suggests

2019-03-03 Thread Sean Davis
Public bug reported:

Please see https://bugs.launchpad.net/ubuntu/+source/indicator-
datetime/+bug/1754872/comments/25 for some background on this bug
report.

I'd like to request that the lightdm greeter Recommends...
unity-greeter | lightdm-greeter (virtual package) | lightdm-kde-greeter

be moved to Suggests. It seems the apt installation order causes unity-
greeter (and other unity components) to be installed along with lightdm-
gtk-greeter when installing the xubuntu-desktop task.

Since each of the lightdm greeters should depend on lightdm, I think
this change helps make greeter installation more explicit and should
prevent the installation of multiple greeters when only one is needed or
requested.

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

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

Title:
  Please demote lightdm greeter recommends to suggests

Status in lightdm package in Ubuntu:
  New

Bug description:
  Please see https://bugs.launchpad.net/ubuntu/+source/indicator-
  datetime/+bug/1754872/comments/25 for some background on this bug
  report.

  I'd like to request that the lightdm greeter Recommends...
  unity-greeter | lightdm-greeter (virtual package) | lightdm-kde-greeter

  be moved to Suggests. It seems the apt installation order causes
  unity-greeter (and other unity components) to be installed along with
  lightdm-gtk-greeter when installing the xubuntu-desktop task.

  Since each of the lightdm greeters should depend on lightdm, I think
  this change helps make greeter installation more explicit and should
  prevent the installation of multiple greeters when only one is needed
  or requested.

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

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


[Touch-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 Ubuntu
Touch seeded packages, which is subscribed to apt 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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-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 Ubuntu
Touch seeded packages, which is subscribed to apt 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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


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

2019-10-09 Thread Sean Davis
** Also affects: xubuntu-meta (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: xubuntu-meta (Ubuntu)
 Assignee: (unassigned) => Sean Davis (bluesabre)

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

Title:
  [FFe] Ubiquity with zfs install option

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

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

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

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

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

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

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

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

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

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

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

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


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

2019-10-11 Thread Sean Davis
** Also affects: xubuntu-meta (Ubuntu)
   Importance: Undecided
   Status: New

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

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

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

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

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

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

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


[Touch-packages] [Bug 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 Ubuntu
Touch seeded 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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1759950] Re: Lid-close suspend: blank screen when switching to user session

2020-05-25 Thread Sean Davis
** Changed in: xubuntu-default-settings (Ubuntu)
   Importance: Undecided => High

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

Title:
  Lid-close suspend: blank screen when switching to user session

Status in Light-Locker:
  New
Status in Xfce4 Power Manager:
  Confirmed
Status in light-locker package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Confirmed
Status in xfce4-power-manager package in Ubuntu:
  Confirmed
Status in xfce4-settings package in Ubuntu:
  Confirmed
Status in xubuntu-default-settings package in Ubuntu:
  Confirmed

Bug description:
  I'm currently testing Xubuntu 18.04 after a do-release-upgrade from
  16.04.

  I discovered a very weird issue. When doing S3 sleep via closing the
  lid, on resume the lock screen appears, I authenticate, but as soon as
  it switches to the user session the screen goes blank - not even a
  backlight.

  Switching to other ttys works and they display correctly but the GUI
  user session remains blank.

  If the system is manually suspended (not using the lid), then resumed
  either by opening the lid or pressing the power button, the GUI user
  session is fine.

  I narrowed it down to xfce4-power-manager and discovered disabling the
  lock-screen cured the issue.

  I cloned the repository and reviewed commits between 1.7 and 1.8.
  Fortunately there aren't many. Looking at 6365683 "Proper exit status
  for light-locker-command" I suspected the change in the SetActive
  return value, and reverted it.

  After a build/install cycle I've found the system now behaves
  correctly so I think the change should be reverted.

  I've created an issue upstream for this at

  https://github.com/the-cavalry/light-locker/issues/108

To manage notifications about this bug go to:
https://bugs.launchpad.net/light-locker/+bug/1759950/+subscriptions

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


[Touch-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 Ubuntu
Touch seeded packages, which is subscribed to apt 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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-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 Ubuntu
Touch seeded packages, which is subscribed to gdebi 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:

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

2020-06-14 Thread Sean Davis
** 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 Ubuntu
Touch seeded packages, which is subscribed to gdebi 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 

[Touch-packages] [Bug 1907956] [NEW] ubiquity crash on whoopsie removal, Xubuntu 21.04 minimal install

2020-12-13 Thread Sean Davis
Public bug reported:

Xubuntu hirsute 20201213 minimal install crashed on whoopsie removal but
finished installing. This is 1907951 with hopefully more crash
information.

Related logs identified:
Dec 13 12:37:05 xubuntu ubiquity: Purging configuration files for whoopsie 
(0.2.73) ...
Dec 13 12:37:05 xubuntu ubiquity: #015
Dec 13 12:37:05 xubuntu ubiquity: Running in chroot, ignoring command 
'daemon-reload'#015
Dec 13 12:37:05 xubuntu ubiquity: message repeated 2 times: [ Running in 
chroot, ignoring command 'daemon-reload'#015]
Dec 13 12:37:05 xubuntu ubiquity: rm:
Dec 13 12:37:05 xubuntu ubiquity: cannot remove '/var/lib/whoopsie/whoopsie-id'
Dec 13 12:37:05 xubuntu ubiquity: : No such file or directory
Dec 13 12:37:05 xubuntu ubiquity: #015
Dec 13 12:37:05 xubuntu ubiquity: dpkg: error processing package whoopsie 
(--purge):
Dec 13 12:37:05 xubuntu ubiquity: #015
Dec 13 12:37:05 xubuntu ubiquity:  installed whoopsie package post-removal 
script subprocess returned error exit status 1
Dec 13 12:37:05 xubuntu ubiquity: #015

Looks like it's a bug in the postrm script:
#! /bin/sh

set -e

#DEBHELPER#

if [ "$1" = "purge" ]; then
deluser --quiet --system whoopsie > /dev/null || true
chmod g-s /var/crash >/dev/null 2>&1
chgrp root /var/crash >/dev/null 2>&1
rm /var/lib/whoopsie/whoopsie-id >/dev/null
fi

exit 0

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: ubiquity 21.04.3
ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
Uname: Linux 5.8.0-25-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu55
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.456
Date: Sun Dec 13 07:40:33 2020
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/xubuntu.seed 
maybe-ubiquity quiet splash ---
LiveMediaBuild: Xubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201213)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=C.UTF-8
RebootRequiredPkgs:
 linux-image-5.8.0-25-generic
 linux-base
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

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

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


** Tags: amd64 apport-bug hirsute ubiquity-21.04.3 xubuntu

** Description changed:

  Xubuntu hirsute 20201213 minimal install crashed on whoopsie removal but
  finished installing. This is 1907951 with hopefully more crash
  information.
+ 
+ Related logs identified:
+ Dec 13 12:37:05 xubuntu ubiquity: Purging configuration files for whoopsie 
(0.2.73) ...
+ Dec 13 12:37:05 xubuntu ubiquity: #015
+ Dec 13 12:37:05 xubuntu ubiquity: Running in chroot, ignoring command 
'daemon-reload'#015
+ Dec 13 12:37:05 xubuntu ubiquity: message repeated 2 times: [ Running in 
chroot, ignoring command 'daemon-reload'#015]
+ Dec 13 12:37:05 xubuntu ubiquity: rm: 
+ Dec 13 12:37:05 xubuntu ubiquity: cannot remove 
'/var/lib/whoopsie/whoopsie-id'
+ Dec 13 12:37:05 xubuntu ubiquity: : No such file or directory
+ Dec 13 12:37:05 xubuntu ubiquity: #015
+ Dec 13 12:37:05 xubuntu ubiquity: dpkg: error processing package whoopsie 
(--purge):
+ Dec 13 12:37:05 xubuntu ubiquity: #015
+ Dec 13 12:37:05 xubuntu ubiquity:  installed whoopsie package post-removal 
script subprocess returned error exit status 1
+ Dec 13 12:37:05 xubuntu ubiquity: #015
  
  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: ubiquity 21.04.3
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu55
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.456
  Date: Sun Dec 13 07:40:33 2020
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/xubuntu.seed 
maybe-ubiquity quiet splash ---
  LiveMediaBuild: Xubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201213)
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=C.UTF-8
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=C.UTF-8
  RebootRequiredPkgs:
-  linux-image-5.8.0-25-generic
-  linux-base
+  linux-image-5.8.0-25-generic
+  linux-base
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

** Description changed:

  Xubuntu hirsute 20201213 minimal install crashed on whoopsie removal but
  finished installing. This is 1907951 with hopefully more crash
  information.
  
  Related logs identified:
  Dec 13 12:37:05 xubuntu ubiquity: Purging configuration files for whoopsie 
(0.2.73) ...
  Dec 13 12:37:05 xubuntu ubiquity: #015
  Dec 13 12:37:05 xubuntu ubiquity: Running in chroot, ignoring command 
'daemon-reload'#015
  Dec 13 12:37:05 xubuntu ubiquity: message repeated 2 times: [ Running in 
chroot, 

[Touch-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 Ubuntu
Touch seeded 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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


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

[Touch-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 Ubuntu
Touch seeded 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: 

[Touch-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 Ubuntu
Touch seeded 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 lpadm

[Touch-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 Ubuntu
Touch seeded 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 

[Touch-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 Ubuntu
Touch seeded 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
  

[Touch-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 Ubuntu
Touch seeded 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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-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 Ubuntu
Touch seeded 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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-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 Ubuntu
Touch seeded 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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1778695] Re: ristretto ignores cr2 files

2022-03-07 Thread Sean Davis
Fixed in ristretto 0.8.5
https://gitlab.xfce.org/apps/ristretto/-/blob/master/NEWS#L235


** Changed in: ristretto (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  ristretto ignores cr2 files

Status in file package in Ubuntu:
  Invalid
Status in ristretto package in Ubuntu:
  Fix Released

Bug description:
  Ristretto does not show canon .cr2 files, neither on 16.04.4 nor on
  18.04.

  
  For 16.04:

  lsb_release -rd
  Description:  Ubuntu 16.04.4 LTS
  Release:  16.04
  apt-cache policy ristretto 
  ristretto:
Installed: 0.8.0-1
Candidate: 0.8.0-1
Version table:
   *** 0.8.0-1 500
  500 http://ch.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status

  for 18.04

  lsb_release -rd
  Description:  Ubuntu 18.04 LTS
  Release:  18.04
  apt-cache policy ristretto 
  ristretto:
Installed: 0.8.2-1ubuntu1
Candidate: 0.8.2-1ubuntu1
Version table:
   *** 0.8.2-1ubuntu1 500
  500 http://ch.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
  100 /var/lib/dpkg/status

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


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


[Touch-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 Ubuntu
Touch seeded 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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1921920] Re: Xubuntu 20.04.2.1 cannot log out, shut down or restart from a temporary guest session.

2022-10-29 Thread Sean Davis
** Package changed: xubuntu-meta (Ubuntu) => xfce4-session (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/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 xfce4-session 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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1993493] Re: lightdm crashed after switching users (lightdm-gtk-greeter, xfce4-screensaver)

2022-10-19 Thread Sean Davis
Previous session

** Attachment added: ".xsession-errors.old"
   
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1993493/+attachment/5625118/+files/.xsession-errors.old

** Description changed:

  Running the Xubuntu Post-install test on GNOME Boxes...
  
  1. Create a new user
  2. Lock your session (xflock4)
  3. Switch user (xfce4-screensaver)
  4. Log in as the new user (lightdm-gtk-greeter)
  5. Log out
  6. Log back in as the original user
  7. The screen goes black, and the original user is logged out
+ 
+ I've seen this a few times with 22.10, but thought it was a weird one-
+ off issue. Repeating the test with a new session does not seem to
+ reproduce the issue.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: lightdm 1.30.0-0ubuntu7
  ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
  Uname: Linux 5.19.0-21-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: XFCE
  Date: Wed Oct 19 04:33:32 2022
  InstallationDate: Installed on 2022-10-19 (0 days ago)
  InstallationMedia: Xubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221018)
  LightdmConfig:
-  [Seat:*]
-  autologin-guest=false
-  autologin-user=oem
-  autologin-user-timeout=0
+  [Seat:*]
+  autologin-guest=false
+  autologin-user=oem
+  autologin-user-timeout=0
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

** Description changed:

- Running the Xubuntu Post-install test on GNOME Boxes...
+ Running the Xubuntu Post-install test on GNOME Boxes. This is on a fresh
+ install, first boot.
  
  1. Create a new user
  2. Lock your session (xflock4)
  3. Switch user (xfce4-screensaver)
  4. Log in as the new user (lightdm-gtk-greeter)
  5. Log out
  6. Log back in as the original user
  7. The screen goes black, and the original user is logged out
  
  I've seen this a few times with 22.10, but thought it was a weird one-
  off issue. Repeating the test with a new session does not seem to
  reproduce the issue.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: lightdm 1.30.0-0ubuntu7
  ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
  Uname: Linux 5.19.0-21-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: XFCE
  Date: Wed Oct 19 04:33:32 2022
  InstallationDate: Installed on 2022-10-19 (0 days ago)
  InstallationMedia: Xubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221018)
  LightdmConfig:
   [Seat:*]
   autologin-guest=false
   autologin-user=oem
   autologin-user-timeout=0
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  lightdm crashed after switching users (lightdm-gtk-greeter,
  xfce4-screensaver)

Status in lightdm package in Ubuntu:
  New

Bug description:
  Running the Xubuntu Post-install test on GNOME Boxes. This is on a
  fresh install, first boot.

  1. Create a new user
  2. Lock your session (xflock4)
  3. Switch user (xfce4-screensaver)
  4. Log in as the new user (lightdm-gtk-greeter)
  5. Log out
  6. Log back in as the original user
  7. The screen goes black, and the original user is logged out

  I've seen this a few times with 22.10, but thought it was a weird one-
  off issue. Repeating the test with a new session does not seem to
  reproduce the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: lightdm 1.30.0-0ubuntu7
  ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
  Uname: Linux 5.19.0-21-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: XFCE
  Date: Wed Oct 19 04:33:32 2022
  InstallationDate: Installed on 2022-10-19 (0 days ago)
  InstallationMedia: Xubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221018)
  LightdmConfig:
   [Seat:*]
   autologin-guest=false
   autologin-user=oem
   autologin-user-timeout=0
  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/1993493/+subscriptions


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


[Touch-packages] [Bug 1993493] Re: lightdm crashed after switching users (lightdm-gtk-greeter, xfce4-screensaver)

2022-10-19 Thread Sean Davis
Current session

** Attachment added: ".xsession-errors"
   
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1993493/+attachment/5625117/+files/.xsession-errors

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

Title:
  lightdm crashed after switching users (lightdm-gtk-greeter,
  xfce4-screensaver)

Status in lightdm package in Ubuntu:
  New

Bug description:
  Running the Xubuntu Post-install test on GNOME Boxes. This is on a
  fresh install, first boot.

  1. Create a new user
  2. Lock your session (xflock4)
  3. Switch user (xfce4-screensaver)
  4. Log in as the new user (lightdm-gtk-greeter)
  5. Log out
  6. Log back in as the original user
  7. The screen goes black, and the original user is logged out

  I've seen this a few times with 22.10, but thought it was a weird one-
  off issue. Repeating the test with a new session does not seem to
  reproduce the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: lightdm 1.30.0-0ubuntu7
  ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
  Uname: Linux 5.19.0-21-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: XFCE
  Date: Wed Oct 19 04:33:32 2022
  InstallationDate: Installed on 2022-10-19 (0 days ago)
  InstallationMedia: Xubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221018)
  LightdmConfig:
   [Seat:*]
   autologin-guest=false
   autologin-user=oem
   autologin-user-timeout=0
  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/1993493/+subscriptions


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


[Touch-packages] [Bug 1993493] [NEW] lightdm crashed after switching users (lightdm-gtk-greeter, xfce4-screensaver)

2022-10-19 Thread Sean Davis
Public bug reported:

Running the Xubuntu Post-install test on GNOME Boxes. This is on a fresh
install, first boot.

1. Create a new user
2. Lock your session (xflock4)
3. Switch user (xfce4-screensaver)
4. Log in as the new user (lightdm-gtk-greeter)
5. Log out
6. Log back in as the original user
7. The screen goes black, and the original user is logged out

I've seen this a few times with 22.10, but thought it was a weird one-
off issue. Repeating the test with a new session does not seem to
reproduce the issue.

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: lightdm 1.30.0-0ubuntu7
ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
Uname: Linux 5.19.0-21-generic x86_64
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: XFCE
Date: Wed Oct 19 04:33:32 2022
InstallationDate: Installed on 2022-10-19 (0 days ago)
InstallationMedia: Xubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221018)
LightdmConfig:
 [Seat:*]
 autologin-guest=false
 autologin-user=oem
 autologin-user-timeout=0
SourcePackage: lightdm
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug kinetic

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

Title:
  lightdm crashed after switching users (lightdm-gtk-greeter,
  xfce4-screensaver)

Status in lightdm package in Ubuntu:
  New

Bug description:
  Running the Xubuntu Post-install test on GNOME Boxes. This is on a
  fresh install, first boot.

  1. Create a new user
  2. Lock your session (xflock4)
  3. Switch user (xfce4-screensaver)
  4. Log in as the new user (lightdm-gtk-greeter)
  5. Log out
  6. Log back in as the original user
  7. The screen goes black, and the original user is logged out

  I've seen this a few times with 22.10, but thought it was a weird one-
  off issue. Repeating the test with a new session does not seem to
  reproduce the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: lightdm 1.30.0-0ubuntu7
  ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
  Uname: Linux 5.19.0-21-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: XFCE
  Date: Wed Oct 19 04:33:32 2022
  InstallationDate: Installed on 2022-10-19 (0 days ago)
  InstallationMedia: Xubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221018)
  LightdmConfig:
   [Seat:*]
   autologin-guest=false
   autologin-user=oem
   autologin-user-timeout=0
  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/1993493/+subscriptions


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


[Touch-packages] [Bug 1500307] Re: xubuntu does not disable gtk overlay scrollbars (i.e. use solid scrollbars)

2022-09-16 Thread Sean Davis
Closing as won't fix. This won't be addressed by Xubuntu.

** Changed in: xubuntu-default-settings (Ubuntu)
   Status: Opinion => Won't Fix

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

Title:
  xubuntu does not disable gtk overlay scrollbars (i.e. use solid
  scrollbars)

Status in One Hundred Papercuts:
  Confirmed
Status in PolicyKit:
  Won't Fix
Status in policykit-1 package in Ubuntu:
  New
Status in xubuntu-default-settings package in Ubuntu:
  Won't Fix

Bug description:
  xubuntu does not disable gtk overlay scrollbars (i.e. use solid
  scrollbars)

  On this page http://tracker.xubuntu.org/ in the source code, Sean
  Davis is assigned to disable gtk3.16 overlay scrollbars in xubuntu-
  default-settings (i.e. use solid scrollbars) and
  https://blueprints.launchpad.net/ubuntu/+spec/xubuntu-w-development
  shows also that the work is done.

  I am running xubuntu 15.10 beta 2 and this is not the case.

  Opening up ubuntu-modified programmes shows solid scrollbars (like the
  non-csd-ized, non-header-bar-ized evince), but synaptic shows overlay
  scrollbars.

  I find it very annoying. There is no visual clue of a scrollbar until
  I move my mouse over the window, and unlike Android or iOS scrollbars,
  the width changes and the transparency changes depending on how close
  my mouse is.

  Very hard to use.

  Please fix.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xubuntu-default-settings 15.10.3
  ProcVersionSignature: Ubuntu 4.2.0-11.13-generic 4.2.1
  Uname: Linux 4.2.0-11-generic x86_64
  ApportVersion: 2.18.1-0ubuntu1
  Architecture: amd64
  CasperVersion: 1.365
  CurrentDesktop: XFCE
  Date: Mon Sep 28 04:43:49 2015
  LiveMediaBuild: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: xubuntu-default-settings
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Touch-packages] [Bug 1833863] Re: Incorrect logic for

2022-10-01 Thread Sean Davis
** Bug watch added: gitlab.xfce.org/xfce/garcon/-/issues #32
   https://gitlab.xfce.org/xfce/garcon/-/issues/32

** Also affects: garcon via
   https://gitlab.xfce.org/xfce/garcon/-/issues/32
   Importance: Unknown
   Status: Unknown

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

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

Title:
  Incorrect logic for 

Status in Garcon:
  Unknown
Status in PyXDG:
  New
Status in garcon package in Ubuntu:
  Triaged
Status in pyxdg package in Ubuntu:
  New
Status in xubuntu-default-settings package in Ubuntu:
  Fix Released

Bug description:
  XFCE & Xubuntu use  in their menu files, which
  python-xdg currently (all current versions) does not handle correctly:

  https://gitlab.freedesktop.org/xdg/pyxdg/issues/12

  I think the fix is as simple as

  --- Menu.py.a   2019-06-23 17:44:24.992850139 +0100
  +++ Menu.py.b   2019-06-23 17:44:41.052807584 +0100
  @@ -997,7 +997,7 @@
   for menuentry in menu.MenuEntries:
   if menuentry not in tmp_e:
   menu.Entries.append(menuentry)
  -elif order[1] == "menus" or order[1] == "all":
  +if order[1] == "menus" or order[1] == "all":
   menu.Submenus.sort()
   for submenu in menu.Submenus:
   if submenu.Name not in tmp_s:

  But as it can also be trivially worked around by replacing  with , I
  wonder if this should be done in XFCE/Xubuntu?

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


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


[Touch-packages] [Bug 2009145] [NEW] Xubuntu defaults in /etc/xdg/xdg-xubuntu are ignored

2023-03-03 Thread Sean Davis
Public bug reported:

Related to https://salsa.debian.org/xorg-team/xorg/-/merge_requests/17

The dbus-x11 package is being deprecated. As a result, the Xfce packages
from upstream Debian no longer pull it in. Until the xorg packages have
been updated accordingly in Ubuntu, the Xubuntu settings found in
/etc/xdg/xdg-xubuntu are ignored.

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

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


** Tags: lunar

** Summary changed:

- Xubuntu defaults are ignored
+ Xubuntu defaults in /etc/xdg/xdg-xubuntu are ignored

** Description changed:

  Related to https://salsa.debian.org/xorg-team/xorg/-/merge_requests/17
  
  The dbus-x11 package is being deprecated. As a result, the Xfce packages
  from upstream Debian no longer pull it in. Until the xorg packages have
  been updated accordingly in Ubuntu, the Xubuntu settings found in
- /etc/xdg are ignored.
+ /etc/xdg/xdg-xubuntu are ignored.

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

** Tags added: lunar

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

Title:
  Xubuntu defaults in /etc/xdg/xdg-xubuntu are ignored

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

Bug description:
  Related to https://salsa.debian.org/xorg-team/xorg/-/merge_requests/17

  The dbus-x11 package is being deprecated. As a result, the Xfce
  packages from upstream Debian no longer pull it in. Until the xorg
  packages have been updated accordingly in Ubuntu, the Xubuntu settings
  found in /etc/xdg/xdg-xubuntu are ignored.

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


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


[Touch-packages] [Bug 2013071] [NEW] Session crash after initial login

2023-03-28 Thread Sean Davis
Public bug reported:

Xubuntu lunar beta 20230328, GNOME Boxes 43.2, "Install third-party
software for graphics and Wi-Fi hardware and additional media formats"
selected during install.

When logging in for the first time, the session immediately crashes and
returns to the login screen.

Attempting to login again without rebooting is successful.
Attempting to login again after rebooting reproduces the issue.

ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6
Uname: Linux 6.2.0-18-generic x86_64
ApportVersion: 2.26.0-0ubuntu2
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: XFCE
Date: Tue Mar 28 07:47:04 2023
DistUpgraded: Fresh install
DistroCodename: lunar
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Red Hat, Inc. QXL paravirtual graphic card [1b36:0100] (rev 05) (prog-if 00 
[VGA controller])
   Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100]
InstallationDate: Installed on 2023-03-28 (0 days ago)
InstallationMedia: Xubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230328)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
 Bus 001 Device 002: ID 08e6:4433 Gemalto (was Gemplus) GemPC433-Swap
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
 /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 5000M
 /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M
 |__ Port 1: Dev 2, If 0, Class=Chip/SmartCard, Driver=, 12M
 |__ Port 2: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 480M
MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-18-generic 
root=UUID=0a9a1a3f-22b7-4cef-b7d4-a193beb89089 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.release: 0.0
dmi.bios.vendor: SeaBIOS
dmi.bios.version: 1.16.1-2.fc37
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-q35-7.0
dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.16.1-2.fc37:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-7.0:cvnQEMU:ct1:cvrpc-q35-7.0:sku:
dmi.product.name: Standard PC (Q35 + ICH9, 2009)
dmi.product.version: pc-q35-7.0
dmi.sys.vendor: QEMU
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.114-1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.3.6-1ubuntu2
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug lunar ubuntu

** Description changed:

  Xubuntu lunar beta 20230328
  
  When logging in for the first time, the session immediately crashes and
- returns to the login screen. Attempting to login again is successful.
+ returns to the login screen.
+ 
+ Attempting to login again without rebooting is successful.
+ Attempting to login again after rebooting reproduces the issue.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6
  Uname: Linux 6.2.0-18-generic x86_64
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Tue Mar 28 07:47:04 2023
  DistUpgraded: Fresh install
  DistroCodename: lunar
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
-  Red Hat, Inc. QXL paravirtual graphic card [1b36:0100] (rev 05) (prog-if 00 
[VGA controller])
-Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100]
+  Red Hat, Inc. QXL paravirtual graphic card [1b36:0100] (rev 05) (prog-if 00 
[VGA controller])
+    Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100]
  InstallationDate: Installed on 2023-03-28 (0 days ago)
  InstallationMedia: Xubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230328)
  Lsusb:
-  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
-  Bus 001 Device 003: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
-  Bus 001 Device 002: ID 08e6:4433 Gemalto (was Gemplus) GemPC433-Swap
-  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 003: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
+  Bus 001 Device 002: ID 08e6:4433 Gemalto (was Gemplus) GemPC433-Swap
+  Bus 001 Device 

[Touch-packages] [Bug 2013071] Re: Session crash after initial login

2023-03-28 Thread Sean Davis
** Description changed:

  Xubuntu lunar beta 20230328, GNOME Boxes 43.2, "Install third-party
  software for graphics and Wi-Fi hardware and additional media formats"
  selected during install.
  
  When logging in for the first time, the session immediately crashes and
  returns to the login screen.
  
  Attempting to login again without rebooting is successful.
  Attempting to login again after rebooting reproduces the issue.
+ 
+ The issue doesn't seem to present itself if "Install third-party software for 
graphics and Wi-Fi hardware and additional media formats" is not selected 
during install. Differences in installed packages:
+ - chromium-codecs-ffmpeg-extra
+ - gimp-help-common
+ - gimp-help-en
+ - gstreamer1.0-plugins-ugly
+ - gstreamer1.0-vaapi
+ - hyphen-en-us
+ - liba52-0.7.4
+ - libmpeg2-4
+ - libopencore-amrnb0
+ - libopencore-amrwb0
+ - libreoffice-help-common
+ - libreoffice-help-en-us
+ - libsidplay1v5
+ - libva-wayland2
+ - mythes-en-us
+ - thunderbird-locale-en
+ - thunderbird-locale-en-us
+ - ubuntu-restricted-addons
+ - wbritish
+ 
+ Since it seems unlikely that the language pack packages are
+ interfering... maybe libva-wayland2 is to blame?
  
  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6
  Uname: Linux 6.2.0-18-generic x86_64
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Tue Mar 28 07:47:04 2023
  DistUpgraded: Fresh install
  DistroCodename: lunar
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Red Hat, Inc. QXL paravirtual graphic card [1b36:0100] (rev 05) (prog-if 00 
[VGA controller])
     Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100]
  InstallationDate: Installed on 2023-03-28 (0 days ago)
  InstallationMedia: Xubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230328)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   Bus 001 Device 002: ID 08e6:4433 Gemalto (was Gemplus) GemPC433-Swap
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M
   |__ Port 1: Dev 2, If 0, Class=Chip/SmartCard, Driver=, 12M
   |__ Port 2: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-18-generic 
root=UUID=0a9a1a3f-22b7-4cef-b7d4-a193beb89089 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.release: 0.0
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.16.1-2.fc37
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-7.0
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.16.1-2.fc37:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-7.0:cvnQEMU:ct1:cvrpc-q35-7.0:sku:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-7.0
  dmi.sys.vendor: QEMU
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.114-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.3.6-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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

Title:
  Session crash after initial login

Status in xorg package in Ubuntu:
  New

Bug description:
  Xubuntu lunar beta 20230328, GNOME Boxes 43.2, "Install third-party
  software for graphics and Wi-Fi hardware and additional media formats"
  selected during install.

  When logging in for the first time, the session immediately crashes
  and returns to the login screen.

  Attempting to login again without rebooting is successful.
  Attempting to login again after rebooting reproduces the issue.

  The issue doesn't seem to present itself if "Install third-party software for 
graphics and Wi-Fi hardware and additional media formats" is not selected 
during install. Differences in installed packages:
  - chromium-codecs-ffmpeg-extra
  - gimp-help-common
  - gimp-help-en
  - gstreamer1.0-plugins-ugly
  - gstreamer1.0-vaapi
  - hyphen-en-us
  - liba52-0.7.4
  - libmpeg2-4
  - libopencore-amrnb0
  - libopencore-amrwb0
  - 

[Touch-packages] [Bug 2009145] Re: Xubuntu defaults in /etc/xdg/xdg-xubuntu are ignored

2024-01-23 Thread Sean Davis
There's this linked bug in Debian:
https://salsa.debian.org/xorg-team/xorg/-/merge_requests/17

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

Title:
  Xubuntu defaults in /etc/xdg/xdg-xubuntu are ignored

Status in xorg package in Ubuntu:
  New
Status in xubuntu-meta package in Ubuntu:
  Fix Released

Bug description:
  Related to https://salsa.debian.org/xorg-team/xorg/-/merge_requests/17

  The dbus-x11 package is being deprecated. As a result, the Xfce
  packages from upstream Debian no longer pull it in. Until the xorg
  packages have been updated accordingly in Ubuntu, the Xubuntu settings
  found in /etc/xdg/xdg-xubuntu are ignored.

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


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


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

2024-03-23 Thread Sean Davis
Super low priority and doesn't really fix anything. Declining for
Xubuntu.

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

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

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

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

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

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


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