from:"Michael Hudson\-Doyle"

[Desktop-packages] [Bug 1974483] Re: autoinstall ssh:install-server:false is misleading in 22.04

2023-09-24 Thread Michael Hudson-Doyle

This is fixed in the 23.10 dailies. I'm not sure it's really practical
to fix this for the next 22.04 point release, unfortunately.

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

** Changed in: subiquity
   Status: Triaged => Fix Released

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

Title:
  autoinstall ssh:install-server:false is misleading in 22.04

Status in subiquity:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-meta source package in Jammy:
  Confirmed

Bug description:
  With 22.04, openssh-server is baked into the image curtin copies to
  the target.  The ssh:install-server key no longer controls whether
  openssh-server gets installed.  It should be easy enough to have the
  bit of code that installs openssh-server when the key is true also
  remove it when the key is false.

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


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

[Desktop-packages] [Bug 2035016] Re: one of 3 monitors "frozen" when a window moves there

2023-09-19 Thread Michael Hudson-Doyle

I have experienced this (or something very like this) a few times on my
t14 amd gen 3, which does not have  dual GPUs. I only updated to
libmutter 45 this morning though.

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

Title:
  one of 3 monitors "frozen" when a window moves there

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  When I move a window to one of my 3 monitors (not the main display),
  the monitor freezes. That means that moving the mouse there doesn't
  work and the picture is frozen on that monitor (including the mouse
  pointer which is visible there).

  The journal has those logs:

  Sep 10 07:21:49 clown-t14 gnome-shell[5640]: 
meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' 
failed
  Sep 10 07:21:49 clown-t14 systemd[5341]: Started 
vte-spawn-99883356-4f85-429c-a61b-60abac42.scope - VTE child process 15895 
launched by kgx process 7379.
  Sep 10 07:22:00 clown-t14 gnome-shell[5640]: Meta.Rectangle is deprecated, 
use Mtk.Rectangle instead
  Sep 10 07:22:04 clown-t14 gnome-shell[5640]: Meta.Rectangle is deprecated, 
use Mtk.Rectangle instead
  Sep 10 07:22:04 clown-t14 gnome-shell[5640]: Meta.Rectangle is deprecated, 
use Mtk.Rectangle instead
  Sep 10 07:22:04 clown-t14 gnome-shell[5640]: Meta.Rectangle is deprecated, 
use Mtk.Rectangle instead
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: Object 
.Gjs_ui_workspaceThumbnail_ThumbnailsBox (0x55b07b31e510), has been already 
disposed — impossible to get any property from it. This might be caused by the 
object having been destroyed from C code using something such as destroy(), 
dispose(), or remove() vfuncs.
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: == Stack trace for context 
0x55b0777837f0 ==
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #0   7ffe4d1d5260 b   
resource:///org/gnome/shell/ui/workspacesView.js:646 (276d81d44970 @ 33)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #1   7ffe4d1d53b0 b   
resource:///org/gnome/shell/ui/workspacesView.js:693 (276d81d44a10 @ 472)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #2   55b07789ddb8 i   
resource:///org/gnome/shell/ui/workspace.js:856 (276d81d040b0 @ 369)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #3   55b07789dd30 i   
resource:///org/gnome/shell/ui/workspace.js:808 (9aad18f9fb0 @ 17)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #4   55b07789dc98 i   
resource:///org/gnome/shell/ui/workspacesView.js:1014 (276d81d45420 @ 129)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #5   55b07789dc08 i   
resource:///org/gnome/shell/ui/overviewControls.js:699 (9aad188a100 @ 50)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #6   55b07789db80 i   
resource:///org/gnome/shell/ui/layout.js:372 (793307f55b0 @ 22)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #7   55b07789daf0 i   
resource:///org/gnome/shell/ui/overview.js:652 (9aad1885f10 @ 190)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #8   55b07789da70 i   
resource:///org/gnome/shell/ui/overview.js:635 (9aad1885ec0 @ 12)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #9   55b07789d9f0 i   
resource:///org/gnome/shell/ui/overviewControls.js:750 (9aad188a330 @ 55)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #10   7ffe4d1dc560 b   
resource:///org/gnome/shell/ui/environment.js:84 (7933077d560 @ 39)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #11   55b07789d968 i   
resource:///org/gnome/shell/ui/environment.js:250 (7933077da60 @ 14)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #12   55b07789d8d8 i   
resource:///org/gnome/shell/ui/init.js:21 (7933077d060 @ 48)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: == Stack trace for context 
0x55b0777837f0 ==
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #0   7ffe4d1d53b0 b   
resource:///org/gnome/shell/ui/workspacesView.js:695 (276d81d44a10 @ 489)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #1   55b07789ddb8 i   
resource:///org/gnome/shell/ui/workspace.js:856 (276d81d040b0 @ 369)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #2   55b07789dd30 i   
resource:///org/gnome/shell/ui/workspace.js:808 (9aad18f9fb0 @ 17)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #3   55b07789dc98 i   
resource:///org/gnome/shell/ui/workspacesView.js:1014 (276d81d45420 @ 129)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #4   55b07789dc08 i   
resource:///org/gnome/shell/ui/overviewControls.js:699 (9aad188a100 @ 50)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #5   55b07789db80 i   
resource:///org/gnome/shell/ui/layout.js:372 (793307f55b0 @ 22)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #6   55b07789daf0 i   
resource:///org/gnome/shell/ui/overview.js:652 (9aad1885f10 @ 190)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #7   55b07789da70 i   
resource:///org/gnome/shell/ui/overview.js:635 (9aad1885ec0 @ 12)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #8   55b07789d9f0 i

[Desktop-packages] [Bug 1993008] Re: ftbfs: E: fontconfig: alien-tag fc-cache-used-in-maintainer-script

2022-10-17 Thread Michael Hudson-Doyle

lintian errors do not count as a build failure. You could file this as a
bug in Debian if you like -- we'll pick up the fix from there in due
course.

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

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

Title:
  ftbfs: E: fontconfig: alien-tag fc-cache-used-in-maintainer-script

Status in fontconfig package in Ubuntu:
  Invalid

Bug description:
  When trying to build from source using

  debuild -us -uc -b

  the result errors out with

  Now running lintian fontconfig_2.13.1-4.4ubuntu1_amd64.changes ...
  E: fontconfig: alien-tag fc-cache-used-in-maintainer-script 
[usr/share/lintian/overrides/fontconfig:1]
  W: libfontconfig-doc: bad-whatis-entry 
[usr/share/man/man3/FcPatternIterNext.3.gz]

  from:
  
https://www.mit.edu/afs.new/sipb/project/debathena/lintian/www/tags/fc-cache-used-in-maintainer-script.html

  "This script apparently runs fc-cache. Updating of the fontconfig cache files 
is now handled automatically by triggers, so running fc-cache from maintainer 
scripts is no longer necessary."

   
  ubuntu: kinetic kudu

  libfontconfig1-dev:
Installed: 2.13.1-4.4ubuntu1
Candidate: 2.13.1-4.4ubuntu1
Version table:
   *** 2.13.1-4.4ubuntu1 500
  500 http://ubuntu.hysing.is/ubuntu kinetic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: libfontconfig-dev 2.13.1-4.4ubuntu1
  Uname: Linux 6.0.1-gnulibre x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Fri Oct 14 21:07:42 2022
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: fontconfig
  UpgradeStatus: Upgraded to kinetic on 2022-10-14 (0 days ago)

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


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

[Desktop-packages] [Bug 1689381] Re: FTBFS cp: cannot stat 'doc/fontconfig-user.html'

2022-10-17 Thread Michael Hudson-Doyle

fontconfig 2.13.1-4.4ubuntu1 built successfully for me in a kinetic
sbuild so I think this can be closed.

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

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

Title:
  FTBFS cp: cannot stat 'doc/fontconfig-user.html'

Status in fontconfig package in Ubuntu:
  Fix Released

Bug description:
  while attempting to build with debuild:

  debuild -us -uc -b
  ...
  Adding cdbs dependencies to debian/libfontconfig1-dbg.substvars
  dh_installdirs -plibfontconfig1-dbg \

  dh_installdocs -pfontconfig ./README ./NEWS ./AUTHORS
  cp: cannot stat 'doc/fontconfig-user.html': No such file or directory
  dh_installdocs: cp --reflink=auto -a doc/fontconfig-user.html 
debian/fontconfig/usr/share/doc/fontconfig returned exit code 1
  /usr/share/cdbs/1/rules/debhelper.mk:235: recipe for target 
'binary-install/fontconfig' failed
  make: *** [binary-install/fontconfig] Error 2
  dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 
2
  debuild: fatal error at line 1116:
  dpkg-buildpackage -rfakeroot -us -uc -b failed
  z@aisha:~/fontconfig/fontconfig-2.11.94/debian$ 

  ubuntu: 17.10 artful
  libfontconfig1-dev:  2.11.94-0ubuntu2

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libfontconfig1-dev (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Mon May  8 19:23:10 2017
  InstallationDate: Installed on 2016-05-07 (366 days ago)
  InstallationMedia:
   
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: fontconfig
  UpgradeStatus: Upgraded to artful on 2017-05-08 (0 days ago)

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


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

[Desktop-packages] [Bug 1992688] Re: firefox deb not installed

2022-10-16 Thread Michael Hudson-Doyle

This just needs to be backported to Jammy now?

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

Title:
  firefox deb not installed

Status in firefox package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in firefox source package in Jammy:
  New
Status in ubuntu-meta source package in Jammy:
  Triaged

Bug description:
  Bug 1964036 leads me to believe that the firefox deb provides some
  important functionality (the firefox favourite icon in the gnome shell
  dock) but there is nothing that would require the deb to be installed
  (it is not seeded nor has an rdep) and the package description
  indicates that it can be safely removed. Is there some important
  functionality that it provides?

  ProblemType: BugDistroRelease: Ubuntu 22.10
  Package: ubuntu-release-upgrader-core 1:22.10.8
  ProcVersionSignature: User Name 5.19.0-19.19-generic 5.19.7
  Uname: Linux 5.19.0-19-generic x86_64
  ApportVersion: 2.23.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckMismatches: ./boot/grub/grub.cfg
  CasperMD5CheckResult: fail
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 12 11:30:46 2022
  InstallationDate: Installed on 2022-04-27 (167 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bashSourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to kinetic on 2022-10-12 (0 days ago)
  VarLogDistupgradeTermlog:

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


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

[Desktop-packages] [Bug 1872124] Re: Please integrate ubuntu-drivers --gpgpu into Ubuntu Server

2022-08-25 Thread Michael Hudson-Doyle

The version of subiquity in 22.04.1 supports this now.

** Changed in: subiquity
   Status: Triaged => Fix Released

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

Title:
  Please integrate ubuntu-drivers --gpgpu into Ubuntu Server

Status in cloud-init:
  Incomplete
Status in MAAS:
  Incomplete
Status in subiquity:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Could subiquity provide an option in the UI to install and execute
  ubuntu-drivers-common on the target? The use case I'm interested in is
  an "on-rails" installation of Nvidia drivers for servers being
  installed for deep learning workloads.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1872124/+subscriptions


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

[Desktop-packages] [Bug 1962170] Re: DEP8 failure with samba 4.15.5

2022-03-07 Thread Michael Hudson-Doyle

Didier merged a better version of the fix I uploaded so presumably he'll
upload that soon and we can see where things fall.

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

Title:
  DEP8 failure with samba 4.15.5

Status in adsys package in Ubuntu:
  New

Bug description:
  The DEP8 tests of adsys started to fail[1] with my samba 4.15.5
  upload.

  Some hints:

   ahasenack: it seems we can’t start our smbd local daemon to
  simulate Active Directory smb server


   ahasenack: yeah, I’m puzzled because on smbd start failure, we do 
print stderr (not stdout though): 
https://github.com/ubuntu/adsys/blob/main/internal/testutils/samba.go#L16
   
https://github.com/ubuntu/adsys/blob/main/internal/testutils/samba.go#L43 in 
particular
   you can see here how we start it: 
https://github.com/ubuntu/adsys/blob/main/internal/testutils/samba.go#L21
   and the config template is at 
https://github.com/ubuntu/adsys/blob/20e6f962eb87f667f5e29800be0715ab2496a10d/internal/testutils/samba.go#L55
   2022/02/24 03:13:59 Setup: smbd hasn’t started successfully
   that's here: 
https://github.com/ubuntu/adsys/blob/main/internal/testutils/samba.go#L129
   you wait for the port to be open?
   which port is that, 445/tcp?
   we wait on the port to be opened, and this one is passed as a 
parameter, see the template. For the argument we pass in ad tests, once sec, 
looking
   1446
   
https://github.com/ubuntu/adsys/blob/20e6f962eb87f667f5e29800be0715ab2496a10d/cmd/integration_tests/adsys_test.go#L47

  
   you just need to run go test . in internal/ad/
   the failure is as the pre-test setup

  
  1. 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/a/adsys/20220224_031434_4d453@/log.gz

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


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

[Desktop-packages] [Bug 1962170] Re: DEP8 failure with samba 4.15.5

2022-03-01 Thread Michael Hudson-Doyle

Hm no, if I apply this patch (or something like it)
https://paste.ubuntu.com/p/vVTyzHMqvr/ the build succeeds. Wtf.

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

Title:
  DEP8 failure with samba 4.15.5

Status in adsys package in Ubuntu:
  In Progress

Bug description:
  The DEP8 tests of adsys started to fail[1] with my samba 4.15.5
  upload.

  Some hints:

   ahasenack: it seems we can’t start our smbd local daemon to
  simulate Active Directory smb server


   ahasenack: yeah, I’m puzzled because on smbd start failure, we do 
print stderr (not stdout though): 
https://github.com/ubuntu/adsys/blob/main/internal/testutils/samba.go#L16
   
https://github.com/ubuntu/adsys/blob/main/internal/testutils/samba.go#L43 in 
particular
   you can see here how we start it: 
https://github.com/ubuntu/adsys/blob/main/internal/testutils/samba.go#L21
   and the config template is at 
https://github.com/ubuntu/adsys/blob/20e6f962eb87f667f5e29800be0715ab2496a10d/internal/testutils/samba.go#L55
   2022/02/24 03:13:59 Setup: smbd hasn’t started successfully
   that's here: 
https://github.com/ubuntu/adsys/blob/main/internal/testutils/samba.go#L129
   you wait for the port to be open?
   which port is that, 445/tcp?
   we wait on the port to be opened, and this one is passed as a 
parameter, see the template. For the argument we pass in ad tests, once sec, 
looking
   1446
   
https://github.com/ubuntu/adsys/blob/20e6f962eb87f667f5e29800be0715ab2496a10d/cmd/integration_tests/adsys_test.go#L47

  
   you just need to run go test . in internal/ad/
   the failure is as the pre-test setup

  
  1. 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/a/adsys/20220224_031434_4d453@/log.gz

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


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

[Desktop-packages] [Bug 1962170] Re: DEP8 failure with samba 4.15.5

2022-03-01 Thread Michael Hudson-Doyle

So fwiw the build failure on ppc64el is hanging on the the call to
io.ReadAll(stderr) in SetupSmb (i.e. here:
https://github.com/ubuntu/adsys/blob/v0.8/internal/testutils/samba.go#L38).
No idea why, but my sense from poking around is that the test has
already failed when the hang occurs so maybe it's some pipe buffer being
full nonsense.

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

Title:
  DEP8 failure with samba 4.15.5

Status in adsys package in Ubuntu:
  In Progress

Bug description:
  The DEP8 tests of adsys started to fail[1] with my samba 4.15.5
  upload.

  Some hints:

   ahasenack: it seems we can’t start our smbd local daemon to
  simulate Active Directory smb server


   ahasenack: yeah, I’m puzzled because on smbd start failure, we do 
print stderr (not stdout though): 
https://github.com/ubuntu/adsys/blob/main/internal/testutils/samba.go#L16
   
https://github.com/ubuntu/adsys/blob/main/internal/testutils/samba.go#L43 in 
particular
   you can see here how we start it: 
https://github.com/ubuntu/adsys/blob/main/internal/testutils/samba.go#L21
   and the config template is at 
https://github.com/ubuntu/adsys/blob/20e6f962eb87f667f5e29800be0715ab2496a10d/internal/testutils/samba.go#L55
   2022/02/24 03:13:59 Setup: smbd hasn’t started successfully
   that's here: 
https://github.com/ubuntu/adsys/blob/main/internal/testutils/samba.go#L129
   you wait for the port to be open?
   which port is that, 445/tcp?
   we wait on the port to be opened, and this one is passed as a 
parameter, see the template. For the argument we pass in ad tests, once sec, 
looking
   1446
   
https://github.com/ubuntu/adsys/blob/20e6f962eb87f667f5e29800be0715ab2496a10d/cmd/integration_tests/adsys_test.go#L47

  
   you just need to run go test . in internal/ad/
   the failure is as the pre-test setup

  
  1. 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/a/adsys/20220224_031434_4d453@/log.gz

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


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

[Desktop-packages] [Bug 1952147] [NEW] no way to list drivers "ubuntu-drivers list --gpgpu" will install

2021-11-24 Thread Michael Hudson-Doyle

Public bug reported:

I'm pretty sure that "ubuntu-drivers install --gpgpu" will install
something if and only if "ubuntu-drivers list --gpgpu" has non-empty
output, but the logic of which of the things list returns gets installed
seems a bit non-trivial

The context for this is in the server installer, I want to say "we think
you should install nvidia-headless-no-dkms-470-server and linux-modules-
nvidia-470-server-generic", shall we go ahead and install them?

My current spike just says "there are some drivers you might want to
install, shall we install them?" which just seems a bit opaque

Alberto suggested a flag so that I could run "ubuntu-drivers list
--gpgpu --recommended" in the installer. I should just make very clear
that I'd want "ubuntu-drivers list --recommended" (i.e. without --gpgpu)
to work the same way :)

** Affects: ubuntu-drivers-common (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  no way to list drivers "ubuntu-drivers list --gpgpu" will install

Status in ubuntu-drivers-common package in Ubuntu:
  New

Bug description:
  I'm pretty sure that "ubuntu-drivers install --gpgpu" will install
  something if and only if "ubuntu-drivers list --gpgpu" has non-empty
  output, but the logic of which of the things list returns gets
  installed seems a bit non-trivial

  The context for this is in the server installer, I want to say "we
  think you should install nvidia-headless-no-dkms-470-server and linux-
  modules-nvidia-470-server-generic", shall we go ahead and install
  them?

  My current spike just says "there are some drivers you might want to
  install, shall we install them?" which just seems a bit opaque

  Alberto suggested a flag so that I could run "ubuntu-drivers list
  --gpgpu --recommended" in the installer. I should just make very clear
  that I'd want "ubuntu-drivers list --recommended" (i.e. without
  --gpgpu) to work the same way :)

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


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

[Desktop-packages] [Bug 1942975] [NEW] gcr 3.40.0-2 ftbfs

2021-09-07 Thread Michael Hudson-Doyle

Public bug reported:

Reported upstream as https://gitlab.gnome.org/GNOME/gcr/-/issues/84.
Looks like it might be a flaky test?

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


** Tags: ftbfs update-excuse

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

Title:
  gcr 3.40.0-2 ftbfs

Status in gcr package in Ubuntu:
  New

Bug description:
  Reported upstream as https://gitlab.gnome.org/GNOME/gcr/-/issues/84.
  Looks like it might be a flaky test?

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


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

[Desktop-packages] [Bug 1888062] Re: autopkgtest became very flaky in Groovy

2020-08-03 Thread Michael Hudson-Doyle

** Tags added: rls-gg-incoming

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

Title:
  autopkgtest became very flaky in Groovy

Status in udisks2 package in Ubuntu:
  Confirmed

Bug description:
  https://autopkgtest.ubuntu.com/packages/u/udisks2/groovy/amd64

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-
  groovy/groovy/amd64/u/udisks2/20200710_213220_c8468@/log.gz

  ...
  SMART status of first internal hard disk ... Failed to query whether SMART is 
available: Operation not supported
  [N/A] ok

  ==
  ERROR: test_0_create_teardown (__main__.Luks)
  LUKS create/teardown
  --
  Traceback (most recent call last):
File "src/tests/integration-test", line 1361, in test_0_create_teardown
  self.setup_crypto_device()
File "src/tests/integration-test", line 1330, in setup_crypto_device
  self.fs_create(None, 'ext4', GLib.Variant('a{sv}', {
File "src/tests/integration-test", line 354, in fs_create
  block.call_format_sync(fs_type, options, None)
  gi.repository.GLib.GError: udisks-error-quark: 
GDBus.Error:org.freedesktop.UDisks2.Error.Failed: Error synchronizing after 
initial wipe: Timed out waiting for object (0)

  ...

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

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

[Desktop-packages] [Bug 1862478] Re: gnome-system-monitor can't measure network transfer rate

2020-02-23 Thread Michael Hudson-Doyle

I fixed this upstream https://gitlab.gnome.org/GNOME/gnome-system-
monitor/-/commit/c031de0a3469faf5020768de506c6169e1e71ac0, not sure if
there will be a release before focal or if this should be cherrypicked.

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

Title:
  gnome-system-monitor can't measure network transfer rate

Status in gnome-system-monitor package in Ubuntu:
  Confirmed

Bug description:
  It started happening since I updated today and version 3.35.90 got
  installed. It had been working normally before that.

  The total number of bytes received seems to be accurate (I really
  downloaded a bit over 1GB of data when the screenshot was taken), but
  the transfer rate is not being measured accurately. The real transfer
  rate when the screenshot was taken was around 10 MB/s while it shows
  just a few bytes/second.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-system-monitor 3.35.90-1
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb  8 22:29:41 2020
  InstallationDate: Installed on 2019-05-15 (269 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: gnome-system-monitor
  UpgradeStatus: Upgraded to focal on 2020-01-20 (19 days ago)

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

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

[Desktop-packages] [Bug 1863473] Re: Network History graph not showing actual network throughput.

2020-02-23 Thread Michael Hudson-Doyle

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

** This bug has been marked a duplicate of bug 1862478
   gnome-system-monitor can't measure network transfer rate

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

Title:
  Network History graph not showing actual network throughput.

Status in gnome-system-monitor package in Ubuntu:
  Confirmed

Bug description:
  Network History graph not showing actual network throughput. Probably
  not scaled. nmon shows current throughput correctly.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-system-monitor 3.35.90-1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Feb 16 15:51:48 2020
  ExecutablePath: /usr/bin/gnome-system-monitor
  InstallationDate: Installed on 2020-02-16 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
  SourcePackage: gnome-system-monitor
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1759540] Re: [MIR] ubuntu-report: send telemetry data to ubuntu server

2018-04-16 Thread Michael Hudson-Doyle

The package looks fine to me now.

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

Title:
  [MIR] ubuntu-report: send telemetry data to ubuntu server

Status in ubuntu-report package in Ubuntu:
  New

Bug description:
  Note that only the C library ("libsysmetrics1") and the command line
  ("ubuntu-report") packages are needed in main (we should also promote
  "libsysmetrics-dev" package, even if not necessary). We don't need the
  Go API "golang-github-ubuntu-ubuntu-report-dev" which has many go
  package dependencies in universe.

  [Availability]
  Available and built on all archs.

  [Rationale]
  We want to provide telemetry upload features, collected by ubiquity, 
do-release-upgrader and that package in ubnutu 18.04. see 
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1755456 for more 
rationales and details.

  [Security]
  No security issue reported, as brand new package.
  The package do a POST message over https to an ubuntu server, data being sent 
are really limited to garantee anynomous informations.
  See example of what is sent on https://github.com/ubuntu/ubuntu-report README.

  [Quality assurance]
  The canonical desktop team is the upstream maintainer and will continue 
maintening it.
  Upstream has CI built-in on every commit + coverage report. The package build 
and runs (currently) 243 tests from unit to integration tests. Autopkgtests 
ensuring that building works and tests still pass is also provided.

  In addition the documentation and C API are continously strongly
  tested (with examples extracted from the documentation, built, linked
  against a on-demand generated C library, and tests ran against it).

  [Dependencies]
  Upstream is using a vendor/ directory, but the ubuntu package remove it on 
build and use the distribution packaged build-deps equivalent.
  No runtime dep in the 3 packages that needs to be promoted.

  [Standards compliance]
  Package follow latest debian packaging standard compliant. No lintian 
override files, and binaries/packages follows Debian standard FHS. Note that 
there is no .symbols file as the generated C API export internal symbols 
(starting with _) which names contains a hash dependant of the source file, and 
per arch specific. The exported symbols from the public API have a stable name 
though: https://godoc.org/github.com/ubuntu/ubuntu-report/pkg/sysmetrics/C

  [Maintenance]
  Canonical desktop team being the usptream and downstream maintainer, strongly 
backed by tests, will follow bugs and maintenance.

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

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

[Desktop-packages] [Bug 1759540] Re: [MIR] ubuntu-report: send telemetry data to ubuntu server

2018-04-09 Thread Michael Hudson-Doyle

Doko asked me to look at the package and it seems OK to me on a quick
glance. (Only spent a few minutes, let me know if you'd like a deeper
review!)

On the packaging side, I'm a bit surprised at the use of go:generate to
create the shared lib but it works I guess. Another thing that's more on
the taste side is that rather than knowing that debhelper puts build
artefacts in obj-$(DEB_HOST_GNU_TYPE), I prefer to pass
--builddirectory=_build or whatever to dh.

I'd generally be happier if the vendor directory wasn't in the source
tarball at all (which would also get you out of updating
debian/copyright :-p). I think you can do this by putting tar-ignore
=ubuntu-report/vendor into debian/source/options? (Side comment: why is
debian/ in .gitignore??)

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

Title:
  [MIR] ubuntu-report: send telemetry data to ubuntu server

Status in ubuntu-report package in Ubuntu:
  Incomplete

Bug description:
  Note that only the C library ("libsysmetrics1") and the command line
  ("ubuntu-report") packages are needed in main (we should also promote
  "libsysmetrics-dev" package, even if not necessary). We don't need the
  Go API "golang-github-ubuntu-ubuntu-report-dev" which has many go
  package dependencies in universe.

  [Availability]
  Available and built on all archs.

  [Rationale]
  We want to provide telemetry upload features, collected by ubiquity, 
do-release-upgrader and that package in ubnutu 18.04. see 
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1755456 for more 
rationales and details.

  [Security]
  No security issue reported, as brand new package.
  The package do a POST message over https to an ubuntu server, data being sent 
are really limited to garantee anynomous informations.
  See example of what is sent on https://github.com/ubuntu/ubuntu-report README.

  [Quality assurance]
  The canonical desktop team is the upstream maintainer and will continue 
maintening it.
  Upstream has CI built-in on every commit + coverage report. The package build 
and runs (currently) 243 tests from unit to integration tests. Autopkgtests 
ensuring that building works and tests still pass is also provided.

  In addition the documentation and C API are continously strongly
  tested (with examples extracted from the documentation, built, linked
  against a on-demand generated C library, and tests ran against it).

  [Dependencies]
  Upstream is using a vendor/ directory, but the ubuntu package remove it on 
build and use the distribution packaged build-deps equivalent.
  No runtime dep in the 3 packages that needs to be promoted.

  [Standards compliance]
  Package follow latest debian packaging standard compliant. No lintian 
override files, and binaries/packages follows Debian standard FHS. Note that 
there is no .symbols file as the generated C API export internal symbols 
(starting with _) which names contains a hash dependant of the source file, and 
per arch specific. The exported symbols from the public API have a stable name 
though: https://godoc.org/github.com/ubuntu/ubuntu-report/pkg/sysmetrics/C

  [Maintenance]
  Canonical desktop team being the usptream and downstream maintainer, strongly 
backed by tests, will follow bugs and maintenance.

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

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

[Desktop-packages] [Bug 1713803] Re: replacement of resolvconf with systemd needs integration

2018-03-26 Thread Michael Hudson-Doyle

I had a quick look at unbound, it seems quite difficult. People who
install unbound probably want it so they can have DNSSEC supported in
their local resolver which we can't really do by integrating with
resolved. OTOH, if installing unbound replaces (in some sense) resolved
and everything else integrates with resolved, that has problems too.

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

Title:
  replacement of resolvconf with systemd needs integration

Status in android-androresolvd package in Ubuntu:
  Triaged
Status in avahi package in Ubuntu:
  Triaged
Status in bind9 package in Ubuntu:
  Triaged
Status in cloud-init package in Ubuntu:
  Incomplete
Status in cloud-initramfs-tools package in Ubuntu:
  Invalid
Status in dhcpcd5 package in Ubuntu:
  New
Status in dibbler package in Ubuntu:
  Won't Fix
Status in dnscrypt-proxy package in Ubuntu:
  Confirmed
Status in dnsmasq package in Ubuntu:
  Invalid
Status in dnssec-trigger package in Ubuntu:
  Invalid
Status in fetchmail package in Ubuntu:
  Confirmed
Status in freedombox-setup package in Ubuntu:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in ndisc6 package in Ubuntu:
  Fix Released
Status in netscript-2.4 package in Ubuntu:
  Won't Fix
Status in open-iscsi package in Ubuntu:
  Triaged
Status in openvpn package in Ubuntu:
  Confirmed
Status in postfix package in Ubuntu:
  New
Status in pppconfig package in Ubuntu:
  Confirmed
Status in pump package in Ubuntu:
  Confirmed
Status in resolvconf package in Ubuntu:
  Invalid
Status in sendmail package in Ubuntu:
  New
Status in squid3 package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Invalid
Status in unbound package in Ubuntu:
  New
Status in vpnc package in Ubuntu:
  Invalid
Status in vpnc-scripts package in Ubuntu:
  Invalid
Status in whereami package in Ubuntu:
  Triaged

Bug description:
  There is a plan to remove resolvconf from the Ubuntu Server image.
  resolvconf integrated with other parts of the system in 2 ways:
   * hooks invoked on change (/etc/resolvconf/update.d/)
   * resolvconf tool (invoked with -a and -d or -u)

  Packages which install files into /etc/resolvconf/update.d are:
  - dnsmasq: This may be mostly covered by systemd-resolved itself (the dns
    caching path).
  - resolvconf: This probably isn't necessary in systemd-resolved path.
  - unbound: This is another "validating, recursive, caching DNS resolver".

  The list of Depends/Suggests/Recommends on resolvconf.

  # for pkg in $(apt-cache rdepends resolvconf | grep -v openreso | grep -v 
Reverse); do out=$(apt-cache show $pkg | grep resolvconf); src=$(apt-cache show 
$pkg | awk '$1 == "Source:" { print $2 }'); [ -n "$src" ] || src=$pkg; case 
"$out" in Depends:*resolvconf) r=depends;; Suggests:*) r=suggests;; 
Recommends:*) r=recommends;; esac; echo "$r $src"; done  | sort -u
  depends android-androresolvd
  recommends avahi
  recommends dhcpcd5
  recommends dibbler
  recommends ndisc6
  recommends whereami
  suggests bind9
  suggests dnscrypt-proxy
  suggests dnsmasq
  suggests dnssec-trigger
  suggests fetchmail
  suggests freedombox-setup
  suggests isc-dhcp
  suggests netscript-2.4
  suggests openvpn
  suggests postfix
  suggests pppconfig
  suggests pump
  suggests resolvconf
  suggests sendmail
  suggests squid3
  suggests vpnc
  suggests vpnc-scripts

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu9
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: amd64
  Date: Tue Aug 29 18:53:50 2017
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-11-generic 
root=UUID=f897b32a-eacf-4191-9717-844918947069 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.vendor: Intel Corporation

  Related bugs:
   * bug 1698181: Switch to netplan renderer in Artful
   * bug 1714308: dns does not work in initramfs after configure_networking
   * bug 1717983 replacement of isc-dhcp-client with with systemd-networkd for 
dhclient needs integration

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

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

[Desktop-packages] [Bug 1709806] [NEW] autopkgtest fails on ppc64el

2017-08-10 Thread Michael Hudson-Doyle

Public bug reported:

Ever since version 2.6.5-2ubuntu1, the autopkgtest for udisks2 has been
very flaky (failing ~80% of the time) on ppc64el:
http://autopkgtest.ubuntu.com/packages/u/udisks2/artful/ppc64el

We attempted to debug a little and managed to reproduce in a VM but we
got confused trying to debug:

[00:09:15]  Summary:
[00:09:17]  - directly calling asubtest fails (call_lock_sync), you 
need to run all Luks tests as they depend on each other
[00:09:18]$ sudo src/tests/integration-test Luks
[00:09:19]There it mostly fails at one of (always a different) 
test
[00:09:21]  - Once the bug was triggered by any of the tests in Luks 
it can be ran into with a subtest alone like
[00:09:23]$ sudo src/tests/integration-test 
Luks.test_ascii_keyfile_newline
[00:09:24]  - at some point after the issue further tests block at 
being unable to remove scsi_debug (needs reboot)
[00:09:26]  - nothing obvious in dmesg, or journal neither on usidk 
nor scsi_debug
[00:09:27]  - I've run a small dbus checker and it lists 
org.freedesktop.UDisks2 still as active
[00:09:28]  With udisk giving neither a crash nor any sort of message 
and the test only reporting a lost connection on the Dbus service I leave it to 
you to continue tmrw
[00:09:31]  mwhudson ^^

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

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

Title:
  autopkgtest fails on ppc64el

Status in udisks2 package in Ubuntu:
  New

Bug description:
  Ever since version 2.6.5-2ubuntu1, the autopkgtest for udisks2 has
  been very flaky (failing ~80% of the time) on ppc64el:
  http://autopkgtest.ubuntu.com/packages/u/udisks2/artful/ppc64el

  We attempted to debug a little and managed to reproduce in a VM but we
  got confused trying to debug:

  [00:09:15]  Summary:
  [00:09:17]  - directly calling asubtest fails (call_lock_sync), you 
need to run all Luks tests as they depend on each other
  [00:09:18]$ sudo src/tests/integration-test Luks
  [00:09:19]There it mostly fails at one of (always a different) 
test
  [00:09:21]  - Once the bug was triggered by any of the tests in 
Luks it can be ran into with a subtest alone like
  [00:09:23]$ sudo src/tests/integration-test 
Luks.test_ascii_keyfile_newline
  [00:09:24]  - at some point after the issue further tests block at 
being unable to remove scsi_debug (needs reboot)
  [00:09:26]  - nothing obvious in dmesg, or journal neither on usidk 
nor scsi_debug
  [00:09:27]  - I've run a small dbus checker and it lists 
org.freedesktop.UDisks2 still as active
  [00:09:28]  With udisk giving neither a crash nor any sort of 
message and the test only reporting a lost connection on the Dbus service I 
leave it to you to continue tmrw
  [00:09:31]  mwhudson ^^

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

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

[Desktop-packages] [Bug 1704238] [NEW] ftbfs on non-amd64

2017-07-13 Thread Michael Hudson-Doyle

Public bug reported:

The build of the test package fails with:

make[6]: Leaving directory '/tmp/tmp9tnlt7ag/melticecream'
 dpkg-genbuildinfo --build=binary
dpkg-genbuildinfo: error: binary build with no binary artifacts found; 
.buildinfo is meaningless
dpkg-buildpackage: error: dpkg-genbuildinfo --build=binary gave error exit 
status 2

Changing the test packages to be arch: all rather than arch: any still
leaves test_subsequent_runs_with_new_script failing, with

 self.assertTrue(re.match("Using '{}' directory\nFile '{files}_test.sh 
already migrated, skipping\nFile '{files}_test.sh already migrated, skipping\n"
 "File '{files}_test.sh already migrated, 
skipping\nExecuting: {}\nExecuting: {}\n".format(self.script_path, 
os.path.join(self.script_path, '08_test.sh'),

  os.path.join(self.script_path, 
'08_testexecute.sh'),

  files='(01|02|10)'),
stdout))

failing to match this output:

Using 
'/<>/session-migration-0.3.1+ppa4/obj-x86_64-linux-gnu/tests/data/main/session-migration/scripts'
 directory
File '02_test.sh already migrated, skipping
File '01_test.sh already migrated, skipping
File '10_test.sh already migrated, skipping
Executing: 
/<>/session-migration-0.3.1+ppa4/obj-x86_64-linux-gnu/tests/data/main/session-migration/scripts/08_test.sh
Executing: 
/<>/session-migration-0.3.1+ppa4/obj-x86_64-linux-gnu/tests/data/main/session-migration/scripts/08_testexecute.sh

(as an aside, these tests are not written in such a way as to make
failures easy to diagnose!)

** Affects: session-migration (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  ftbfs on non-amd64

Status in session-migration package in Ubuntu:
  New

Bug description:
  The build of the test package fails with:

  make[6]: Leaving directory '/tmp/tmp9tnlt7ag/melticecream'
   dpkg-genbuildinfo --build=binary
  dpkg-genbuildinfo: error: binary build with no binary artifacts found; 
.buildinfo is meaningless
  dpkg-buildpackage: error: dpkg-genbuildinfo --build=binary gave error exit 
status 2

  Changing the test packages to be arch: all rather than arch: any still
  leaves test_subsequent_runs_with_new_script failing, with

   self.assertTrue(re.match("Using '{}' directory\nFile 
'{files}_test.sh already migrated, skipping\nFile '{files}_test.sh already 
migrated, skipping\n"
   "File '{files}_test.sh already migrated, 
skipping\nExecuting: {}\nExecuting: {}\n".format(self.script_path, 
os.path.join(self.script_path, '08_test.sh'),

os.path.join(self.script_path, 
'08_testexecute.sh'),

files='(01|02|10)'),
  stdout))

  failing to match this output:

  Using 
'/<>/session-migration-0.3.1+ppa4/obj-x86_64-linux-gnu/tests/data/main/session-migration/scripts'
 directory
  File '02_test.sh already migrated, skipping
  File '01_test.sh already migrated, skipping
  File '10_test.sh already migrated, skipping
  Executing: 
/<>/session-migration-0.3.1+ppa4/obj-x86_64-linux-gnu/tests/data/main/session-migration/scripts/08_test.sh
  Executing: 
/<>/session-migration-0.3.1+ppa4/obj-x86_64-linux-gnu/tests/data/main/session-migration/scripts/08_testexecute.sh

  (as an aside, these tests are not written in such a way as to make
  failures easy to diagnose!)

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

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

[Desktop-packages] [Bug 1679831] Re: pygobject FTBFS on all arches during zesty test rebuild

2017-05-09 Thread Michael Hudson-Doyle

This will end up blocking the enablement of python 3.6 as a supported
version. Any idea who might know how to fix this?

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

Title:
  pygobject FTBFS on all arches during zesty test rebuild

Status in pygobject package in Ubuntu:
  New

Bug description:
  pygobject version 3.22.0-2 failed to build from source on all arches
  during a test rebuild of zesty.  The build log file can be found here:

  https://launchpadlibrarian.net/312383047/buildlog_ubuntu-zesty-
  amd64.pygobject_3.22.0-2_BUILDING.txt.gz

  The failure seems to be:

  bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. 
-I../../tests -I..   -Wdate-time -D_FORTIFY_SOURCE=2  -pthread 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
-I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/freetype2 
-I/usr/include/libpng16 -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -g -O2 
-fdebug-prefix-map=/<>=. -fPIE -fstack-protector-strong -Wformat 
-Werror=format-security -Wall -Werror=unused-variable -fno-strict-aliasing 
-Werror=declaration-after-statement  -Wall -Wstrict-prototypes -Wnested-externs 
-Werror=missing-prototypes -Werror=implicit-function-declaration 
-Werror=pointer-arith -Werror=init-self -Werror=format-security 
-Werror=format=2 -Werror=missing-include-dirs -Werror=return-type   -c -o 
libregress_la-regress.lo `test -f 
'/usr/share/gobject-introspection-1.0/tests/regress.c' || echo 
'../../tests/'`/usr/share/gobject-introspection-1.0/tests/regress.c
  libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../../tests -I.. -Wdate-time 
-D_FORTIFY_SOURCE=2 -pthread -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/cairo 
-I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng16 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wall -Werror=unused-variable -fno-strict-aliasing 
-Werror=declaration-after-statement -Wall -Wstrict-prototypes -Wnested-externs 
-Werror=missing-prototypes -Werror=implicit-function-declaration 
-Werror=pointer-arith -Werror=init-self -Werror=format-security 
-Werror=format=2 -Werror=missing-include-dirs -Werror=return-type -c 
/usr/share/gobject-introspection-1.0/tests/regress.c  -fPIC -DPIC -o 
.libs/libregress_la-regress.o
  /usr/share/gobject-introspection-1.0/tests/regress.c:3448:3: error: no 
previous prototype for ‘_regress_test_fundamental_hidden_sub_object_get_type’ 
[-Werror=missing-prototypes]
 _regress_test_fundamental_hidden_sub_object_get_type
 ^
  /usr/share/gobject-introspection-1.0/tests/regress.c:3448:3: note: in 
definition of macro ‘regress_test_fundamental_hidden_sub_object_get_type’
 _regress_test_fundamental_hidden_sub_object_get_type
 ^~~~
  /usr/include/glib-2.0/gobject/gtype.h:1737:60: note: in expansion of macro 
‘_G_DEFINE_TYPE_EXTENDED_BEGIN’
   #define G_DEFINE_TYPE_EXTENDED(TN, t_n, T_P, _f_, _C_) 
_G_DEFINE_TYPE_EXTENDED_BEGIN (TN, t_n, T_P, _f_) {_C_;} 
_G_DEFINE_TYPE_EXTENDED_END()
  
^
  /usr/include/glib-2.0/gobject/gtype.h:1595:43: note: in expansion of macro 
‘G_DEFINE_TYPE_EXTENDED’
   #define G_DEFINE_TYPE(TN, t_n, T_P)   G_DEFINE_TYPE_EXTENDED (TN, t_n, 
T_P, 0, {})
 ^~
  /usr/share/gobject-introspection-1.0/tests/regress.c:3456:1: note: in 
expansion of macro ‘G_DEFINE_TYPE’
   G_DEFINE_TYPE (RegressTestFundamentalHiddenSubObject,
   ^
  cc1: some warnings being treated as errors
  Makefile:567: recipe for target 'libregress_la-regress.lo' failed
  make[4]: *** [libregress_la-regress.lo] Error 1
  make[4]: Leaving directory '/<>/build-2.7/tests'
  Makefile:679: recipe for target 'all-recursive' failed
  make[3]: *** [all-recursive] Error 1
  make[3]: Leaving directory '/<>/build-2.7'
  Makefile:502: recipe for target 'all' failed
  make[2]: *** [all] Error 2
  make[2]: Leaving directory '/<>/build-2.7'
  dh_auto_build: make -j1 returned exit code 2
  debian/rules:28: recipe for target 'override_dh_auto_build' failed
  make[1]: *** [override_dh_auto_build] Error 2
  make[1]: Leaving directory '/<>'
  debian/rules:20: recipe for target 'build' failed
  make: *** [build] Error 2
  dpkg-buildpackage: error: debian/rules build gave error exit status 2

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

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

[Desktop-packages] [Bug 1632357] Re: Sync llvm-toolchain-3.6 1:3.6.2-4 (main) from Debian unstable (main)

2016-10-26 Thread Michael Hudson-Doyle

In fact it seems once we merge clamav we can drop llvm-toolchain-3.6
entirely, or at least demote it from main.

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

Title:
  Sync llvm-toolchain-3.6 1:3.6.2-4 (main) from Debian unstable (main)

Status in llvm-toolchain-3.6 package in Ubuntu:
  Incomplete

Bug description:
  Please sync llvm-toolchain-3.6 1:3.6.2-4 (main) from Debian unstable
  (main)

  Explanation of the Ubuntu delta and why it can be dropped:
[ Gianfranco Costamagna ]
* remove powerpc from gold architectures.
  (see e.g. LP: #1611227)
* powerpcspe in findstring is making powerpc enabled again.
  Using filter will work.
* Do not link executables with a version script.
* Do not link executables with a version script.
* [AArch64] Fix invalid use of references to BuildMI, taken from the trunk.
* No-change rebuild against ocaml 4.02. (LP: #1515031)

  Everything merged in Debian

  Changelog entries since current yakkety version 1:3.6.2-3ubuntu4:

  llvm-toolchain-3.6 (1:3.6.2-4) unstable; urgency=medium

* Team upload

[ Gianfranco Costamagna ]
* Import some changes from Ubuntu.
* Fix powerpc sadness by not using gold linker.

[ Matthias Klose ]
* d/p/rL235088.diff:
  - [AArch64] Fix invalid use of references to BuildMI, taken from the 
trunk.
* d/p/no-version-script-for-executables.diff:
  - Do not link executables with a version script.

[ Louis Bouchard ]
* d/rules: Fix the regex for the GCC_VERSION so it takes version 6
  into account. Otherwise, this causes an FTBS (Closes: #835582)

   -- Gianfranco Costamagna   Fri, 07 Oct 2016
  08:21:03 +0200

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-3.6/+bug/1632357/+subscriptions

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

[Desktop-packages] [Bug 1632357] Re: Sync llvm-toolchain-3.6 1:3.6.2-4 (main) from Debian unstable (main)

2016-10-26 Thread Michael Hudson-Doyle

The request seems fine but 1:3.6.2-4 seems to have been removed from
sid. What's going on? Do we still want to sync it? (I presume copy-
package can be persuaded to copy a deleted package...). If there are not
going to be any more updates I guess there's not a lot of point...

** Changed in: llvm-toolchain-3.6 (Ubuntu)
   Status: New => Incomplete

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

Title:
  Sync llvm-toolchain-3.6 1:3.6.2-4 (main) from Debian unstable (main)

Status in llvm-toolchain-3.6 package in Ubuntu:
  Incomplete

Bug description:
  Please sync llvm-toolchain-3.6 1:3.6.2-4 (main) from Debian unstable
  (main)

  Explanation of the Ubuntu delta and why it can be dropped:
[ Gianfranco Costamagna ]
* remove powerpc from gold architectures.
  (see e.g. LP: #1611227)
* powerpcspe in findstring is making powerpc enabled again.
  Using filter will work.
* Do not link executables with a version script.
* Do not link executables with a version script.
* [AArch64] Fix invalid use of references to BuildMI, taken from the trunk.
* No-change rebuild against ocaml 4.02. (LP: #1515031)

  Everything merged in Debian

  Changelog entries since current yakkety version 1:3.6.2-3ubuntu4:

  llvm-toolchain-3.6 (1:3.6.2-4) unstable; urgency=medium

* Team upload

[ Gianfranco Costamagna ]
* Import some changes from Ubuntu.
* Fix powerpc sadness by not using gold linker.

[ Matthias Klose ]
* d/p/rL235088.diff:
  - [AArch64] Fix invalid use of references to BuildMI, taken from the 
trunk.
* d/p/no-version-script-for-executables.diff:
  - Do not link executables with a version script.

[ Louis Bouchard ]
* d/rules: Fix the regex for the GCC_VERSION so it takes version 6
  into account. Otherwise, this causes an FTBS (Closes: #835582)

   -- Gianfranco Costamagna   Fri, 07 Oct 2016
  08:21:03 +0200

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-3.6/+bug/1632357/+subscriptions

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

[Desktop-packages] [Bug 1572493] Re: pulseaudio 8.0 drops connections after playing audio in a firejail

2016-06-01 Thread Michael Hudson-Doyle

Ah sorry, I invalidated it because the original reporter asked me to.

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

Title:
  pulseaudio 8.0 drops connections after playing audio in a firejail

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from Ubuntu 15.10 to 16.04 (pulseaudio 6 -> 8), I
  notice that my audio output stops working every few hours.  When this
  happens, if I run pavucontrol, it seems to wait forever trying to
  connect to pulseaudio.  Killing pulseaudio and starting it again fixes
  the problem for a little while.

  I don't think anything fancy is needed to cause a hang; usually, I'm
  just using Chrome.

  This never happened with pulseaudio 6 over hundreds of hours of use.

  I am using the default pulseaudio config files on an HP EliteBook
  8460p, which has this audio sink:

  1 sink(s) available.
* index: 0
name: 
driver: 
flags: HARDWARE HW_MUTE_CTRL HW_VOLUME_CTRL DECIBEL_VOLUME LATENCY 
DYNAMIC_LATENCY
state: IDLE
suspend cause: 
priority: 9959
volume: front-left: 61870 /  94% / -1.50 dB,   front-right: 61870 /  
94% / -1.50 dB
balance 0.00
base volume: 65536 / 100% / 0.00 dB
volume steps: 65537
muted: no
current latency: 38.86 ms
max request: 6 KiB
max rewind: 64 KiB
monitor source: 0
sample spec: s16le 2ch 44100Hz
channel map: front-left,front-right
 Stereo
used by: 0
linked by: 1
configured latency: 40.00 ms; range is 0.50 .. 371.52 ms
card: 1 
module: 7
properties:
alsa.resolution_bits = "16"
device.api = "alsa"
device.class = "sound"
alsa.class = "generic"
alsa.subclass = "generic-mix"
alsa.name = "92HD81B1X5 Analog"
alsa.id = "92HD81B1X5 Analog"
alsa.subdevice = "0"
alsa.subdevice_name = "subdevice #0"
alsa.device = "0"
alsa.card = "0"
alsa.card_name = "HDA Intel PCH"
alsa.long_card_name = "HDA Intel PCH at 0xd452 irq 40"
alsa.driver_name = "snd_hda_intel"
device.bus_path = "pci-:00:1b.0"
sysfs.path = "/devices/pci:00/:00:1b.0/sound/card0"
device.bus = "pci"
device.vendor.id = "8086"
device.vendor.name = "Intel Corporation"
device.product.id = "1c20"
device.product.name = "6 Series/C200 Series Chipset Family High 
Definition Audio Controller"
device.form_factor = "internal"
device.string = "front:0"
device.buffering.buffer_size = "65536"
device.buffering.fragment_size = "32768"
device.access_mode = "mmap+timer"
device.profile.name = "analog-stereo"
device.profile.description = "Analog Stereo"
device.description = "Built-in Audio Analog Stereo"
alsa.mixer_name = "IDT 92HD81B1X5"
alsa.components = "HDA:111d7605,103c3588,00100105 
HDA:11c11040,103c3066,00100200"
module-udev-detect.discovered = "1"
device.icon_name = "audio-card-pci"
ports:
analog-output-lineout: Line Out (priority 9900, latency offset 
0 usec, available: no)
properties:

analog-output-speaker: Speakers (priority 1, latency offset 
0 usec, available: unknown)
properties:
device.icon_name = "audio-speakers"
analog-output-headphones: Headphones (priority 9000, latency 
offset 0 usec, available: no)
properties:
device.icon_name = "audio-headphones"
active port: 



  # dpkg -l | grep pulse
  ii  libpulse-mainloop-glib0:amd64   1:8.0-0ubuntu3   amd64
PulseAudio client libraries (glib support)
  ii  libpulse0:amd64 1:8.0-0ubuntu3   amd64
PulseAudio client libraries
  ii  libpulse0:i386  1:8.0-0ubuntu3   i386 
PulseAudio client libraries
  ii  libpulsedsp:amd64   1:8.0-0ubuntu3   amd64
PulseAudio OSS pre-load library
  ii  pulseaudio  1:8.0-0ubuntu3   amd64
PulseAudio sound server
  ii  pulseaudio-utils1:8.0-0ubuntu3   amd64
Command line tools for the PulseAudio sound server

  # uname -a
  Linux laptop 4.4.0-21-generic #37-Ubuntu SMP Mon Apr 18 18:33:37 UTC 2016 
x86_64 x86_64

[Desktop-packages] [Bug 1572493] Re: pulseaudio 8.0 drops connections after playing audio in a firejail

2016-04-20 Thread Michael Hudson-Doyle

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

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

Title:
  pulseaudio 8.0 drops connections after playing audio in a firejail

Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  After upgrading from Ubuntu 15.10 to 16.04 (pulseaudio 6 -> 8), I
  notice that my audio output stops working every few hours.  When this
  happens, if I run pavucontrol, it seems to wait forever trying to
  connect to pulseaudio.  Killing pulseaudio and starting it again fixes
  the problem for a little while.

  I don't think anything fancy is needed to cause a hang; usually, I'm
  just using Chrome.

  This never happened with pulseaudio 6 over hundreds of hours of use.

  I am using the default pulseaudio config files on an HP EliteBook
  8460p, which has this audio sink:

  1 sink(s) available.
* index: 0
name: 
driver: 
flags: HARDWARE HW_MUTE_CTRL HW_VOLUME_CTRL DECIBEL_VOLUME LATENCY 
DYNAMIC_LATENCY
state: IDLE
suspend cause: 
priority: 9959
volume: front-left: 61870 /  94% / -1.50 dB,   front-right: 61870 /  
94% / -1.50 dB
balance 0.00
base volume: 65536 / 100% / 0.00 dB
volume steps: 65537
muted: no
current latency: 38.86 ms
max request: 6 KiB
max rewind: 64 KiB
monitor source: 0
sample spec: s16le 2ch 44100Hz
channel map: front-left,front-right
 Stereo
used by: 0
linked by: 1
configured latency: 40.00 ms; range is 0.50 .. 371.52 ms
card: 1 
module: 7
properties:
alsa.resolution_bits = "16"
device.api = "alsa"
device.class = "sound"
alsa.class = "generic"
alsa.subclass = "generic-mix"
alsa.name = "92HD81B1X5 Analog"
alsa.id = "92HD81B1X5 Analog"
alsa.subdevice = "0"
alsa.subdevice_name = "subdevice #0"
alsa.device = "0"
alsa.card = "0"
alsa.card_name = "HDA Intel PCH"
alsa.long_card_name = "HDA Intel PCH at 0xd452 irq 40"
alsa.driver_name = "snd_hda_intel"
device.bus_path = "pci-:00:1b.0"
sysfs.path = "/devices/pci:00/:00:1b.0/sound/card0"
device.bus = "pci"
device.vendor.id = "8086"
device.vendor.name = "Intel Corporation"
device.product.id = "1c20"
device.product.name = "6 Series/C200 Series Chipset Family High 
Definition Audio Controller"
device.form_factor = "internal"
device.string = "front:0"
device.buffering.buffer_size = "65536"
device.buffering.fragment_size = "32768"
device.access_mode = "mmap+timer"
device.profile.name = "analog-stereo"
device.profile.description = "Analog Stereo"
device.description = "Built-in Audio Analog Stereo"
alsa.mixer_name = "IDT 92HD81B1X5"
alsa.components = "HDA:111d7605,103c3588,00100105 
HDA:11c11040,103c3066,00100200"
module-udev-detect.discovered = "1"
device.icon_name = "audio-card-pci"
ports:
analog-output-lineout: Line Out (priority 9900, latency offset 
0 usec, available: no)
properties:

analog-output-speaker: Speakers (priority 1, latency offset 
0 usec, available: unknown)
properties:
device.icon_name = "audio-speakers"
analog-output-headphones: Headphones (priority 9000, latency 
offset 0 usec, available: no)
properties:
device.icon_name = "audio-headphones"
active port: 



  # dpkg -l | grep pulse
  ii  libpulse-mainloop-glib0:amd64   1:8.0-0ubuntu3   amd64
PulseAudio client libraries (glib support)
  ii  libpulse0:amd64 1:8.0-0ubuntu3   amd64
PulseAudio client libraries
  ii  libpulse0:i386  1:8.0-0ubuntu3   i386 
PulseAudio client libraries
  ii  libpulsedsp:amd64   1:8.0-0ubuntu3   amd64
PulseAudio OSS pre-load library
  ii  pulseaudio  1:8.0-0ubuntu3   amd64
PulseAudio sound server
  ii  pulseaudio-utils1:8.0-0ubuntu3   amd64
Command line tools for the PulseAudio sound server

  # uname -a
  Linux laptop 4.4.0-21-generic #37-Ubuntu SMP Mon Apr 18 18:33:37 UTC 2016 
x86_64 x86_64 x86_64

[Desktop-packages] [Bug 1467595] Re: cursor sometimes disappears on XPS 13 9343 and external monitor

2015-11-16 Thread Michael Hudson-Doyle

FWIW, I haven't seen this for a few months now. It's always hard when
things are so intermittent, but I think it might be fixed...

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

Title:
  cursor sometimes disappears on XPS 13 9343 and external monitor

Status in Unity:
  Confirmed
Status in unity package in Ubuntu:
  Confirmed
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I have a new Dell XPS 13 9343 with the HiDPI touch screen and am using
  an external display port monitor. Occasionally, the mouse cursor
  disappears (sometimes after screen lock, other times just normal
  usage). I saw something on stack exchange that said this might help:

  gsettings set org.gnome.settings-daemon.plugins.cursor active false

  I've done this and it sometimes helps and sometimes doesn't. I've also
  just seen the cursor come back on its own after a few minutes without
  doing anything. Trying to interact with the touch screen, then the
  mouse has no effect. Unplugging and replugging the mouse has no
  effect. Using the touchpad has no effect.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity 7.3.2+15.04.20150420-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8
  Uname: Linux 3.19.0-21-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity.support.test.0:

  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Jun 22 11:19:40 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.248+bdcom, 3.19.0-18-generic, x86_64: installed
   bcmwl, 6.30.223.248+bdcom, 3.19.0-20-generic, x86_64: installed
   bcmwl, 6.30.223.248+bdcom, 3.19.0-21-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:0665]
  InstallationDate: Installed on 2015-06-13 (8 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Dell Inc. XPS 13 9343
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-21-generic 
root=UUID=7bc4dcd2-0bd8-4e42-b8b7-9f1ed6b8a3e9 ro libata.force=noncq quiet 
splash vt.handoff=7
  SourcePackage: unity
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/25/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A03
  dmi.board.name: 0310JH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd03/25/2015:svnDellInc.:pnXPS139343:pvr01:rvnDellInc.:rn0310JH:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2build1
  xserver.bootTime: Mon Jun 22 10:53:54 2015
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5153
   vendor SHP
  xserver.version: 2:1.17.1-0ubuntu3

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

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

[Desktop-packages] [Bug 1974483] Re: autoinstall ssh:install-server:false is misleading in 22.04

[Desktop-packages] [Bug 2035016] Re: one of 3 monitors "frozen" when a window moves there

[Desktop-packages] [Bug 1993008] Re: ftbfs: E: fontconfig: alien-tag fc-cache-used-in-maintainer-script

[Desktop-packages] [Bug 1689381] Re: FTBFS cp: cannot stat 'doc/fontconfig-user.html'

[Desktop-packages] [Bug 1992688] Re: firefox deb not installed

[Desktop-packages] [Bug 1872124] Re: Please integrate ubuntu-drivers --gpgpu into Ubuntu Server

[Desktop-packages] [Bug 1962170] Re: DEP8 failure with samba 4.15.5

[Desktop-packages] [Bug 1962170] Re: DEP8 failure with samba 4.15.5

[Desktop-packages] [Bug 1962170] Re: DEP8 failure with samba 4.15.5

[Desktop-packages] [Bug 1952147] [NEW] no way to list drivers "ubuntu-drivers list --gpgpu" will install

[Desktop-packages] [Bug 1942975] [NEW] gcr 3.40.0-2 ftbfs

[Desktop-packages] [Bug 1888062] Re: autopkgtest became very flaky in Groovy

[Desktop-packages] [Bug 1862478] Re: gnome-system-monitor can't measure network transfer rate

[Desktop-packages] [Bug 1863473] Re: Network History graph not showing actual network throughput.

[Desktop-packages] [Bug 1759540] Re: [MIR] ubuntu-report: send telemetry data to ubuntu server

[Desktop-packages] [Bug 1759540] Re: [MIR] ubuntu-report: send telemetry data to ubuntu server

[Desktop-packages] [Bug 1713803] Re: replacement of resolvconf with systemd needs integration

[Desktop-packages] [Bug 1709806] [NEW] autopkgtest fails on ppc64el

[Desktop-packages] [Bug 1704238] [NEW] ftbfs on non-amd64

[Desktop-packages] [Bug 1679831] Re: pygobject FTBFS on all arches during zesty test rebuild

[Desktop-packages] [Bug 1632357] Re: Sync llvm-toolchain-3.6 1:3.6.2-4 (main) from Debian unstable (main)

[Desktop-packages] [Bug 1632357] Re: Sync llvm-toolchain-3.6 1:3.6.2-4 (main) from Debian unstable (main)

[Desktop-packages] [Bug 1572493] Re: pulseaudio 8.0 drops connections after playing audio in a firejail

[Desktop-packages] [Bug 1572493] Re: pulseaudio 8.0 drops connections after playing audio in a firejail

[Desktop-packages] [Bug 1467595] Re: cursor sometimes disappears on XPS 13 9343 and external monitor

25 matches

Site Navigation

Mail list logo

Footer information