[Ubuntu-x-swat] [Bug 1779531] Re: Please merge 1.4.0-1 from Debian Sid

[LocutusOfBorg]

done after removing the trailing newline on changelog file :p

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xinit in Ubuntu.
https://bugs.launchpad.net/bugs/1779531

Title:
  Please merge 1.4.0-1 from Debian Sid

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1779531] Re: Please merge 1.4.0-1 from Debian Sid

[LocutusOfBorg]

Seems you loose all the previous changelog history, and removed stuff
without no reason explained in the changelog entry.

** Changed in: xinit (Ubuntu)
   Status: In Progress => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xinit in Ubuntu.
https://bugs.launchpad.net/bugs/1779531

Title:
  Please merge 1.4.0-1 from Debian Sid

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1757024] Re: Sync libinput 1.10.3-2 (main) from Debian unstable (main)

[LocutusOfBorg]

This bug was fixed in the package libinput - 1.10.3-2
Sponsored for Simon Quigley (tsimonq2)

---
libinput (1.10.3-2) unstable; urgency=medium

  [ Jeremy Bicha ]
  * control: Update VCS urls.
  * control: Add more packages to libinput-dev Depends as a workaround for
buggy meson/pkg-config. (Closes: #893067)

 -- Timo Aaltonen   Sun, 18 Mar 2018 15:39:44 +0200

libinput (1.10.3-1) unstable; urgency=medium

  * New upstream release. (Closes: #892714)

 -- Timo Aaltonen   Wed, 14 Mar 2018 11:04:22 +0200

libinput (1.10.2-1) unstable; urgency=medium

  * New upstream release.
- touchpad fixes (LP: #1751190)

 -- Timo Aaltonen   Wed, 07 Mar 2018 17:51:58 +0200

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libinput in Ubuntu.
https://bugs.launchpad.net/bugs/1757024

Title:
  Sync libinput 1.10.3-2 (main) from Debian unstable (main)

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1757024] Re: Sync libinput 1.10.3-2 (main) from Debian unstable (main)

[LocutusOfBorg]

Considering that the package has been in unstable for 5 days already
(the RC bug is fixed and not a code bug, but rather a packaging one).

the only new bug is:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892916

and this is probably not worth a nack because of the ton of other fixes


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

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

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libinput in Ubuntu.
https://bugs.launchpad.net/bugs/1757024

Title:
  Sync libinput 1.10.3-2 (main) from Debian unstable (main)

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1757024] Re: Sync libinput 1.10.3-2 (main) from Debian unstable (main)

[LocutusOfBorg]

Considering how badly debian bug 893067 messed up things, I'll wait some
more days before syncing

** Changed in: libinput (Ubuntu)
 Assignee: (unassigned) => LocutusOfBorg (costamagnagianfranco)

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libinput in Ubuntu.
https://bugs.launchpad.net/bugs/1757024

Title:
  Sync libinput 1.10.3-2 (main) from Debian unstable (main)

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1749340] Re: Upgrade to libinput 1.10 in bionic

[LocutusOfBorg]

this is true, I didn't manually tweak the changes file, this is a plain
sync, and the Debian package didn't reference it :)

Anyhow, it is now in release, since 12h or so

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libinput in Ubuntu.
https://bugs.launchpad.net/bugs/1749340

Title:
  Upgrade to libinput 1.10 in bionic

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1749340] Re: Upgrade to libinput 1.10 in bionic

[LocutusOfBorg]

yes, but since I have a firefox/chrome open tab for it, and I usually
forget to close bugs, please let me close it, and I'll make sure it goes
in release pocket :)

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

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libinput in Ubuntu.
https://bugs.launchpad.net/bugs/1749340

Title:
  Upgrade to libinput 1.10 in bionic

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1749340] Re: Upgrade to libinput 1.10 in bionic

[LocutusOfBorg]

I sync'd for tsimonq2 some minutes ago :)

** Changed in: libinput (Ubuntu)
   Status: Triaged => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libinput in Ubuntu.
https://bugs.launchpad.net/bugs/1749340

Title:
  Upgrade to libinput 1.10 in bionic

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1647600] Re: Xvfb fails with new mesa, results in ubiquity FTBFS

[LocutusOfBorg]

https://bugs.launchpad.net/ubuntu/+source/ettercap/+bug/1713313

@Fadi

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libepoxy in Ubuntu.
https://bugs.launchpad.net/bugs/1647600

Title:
  Xvfb fails with new mesa, results in ubiquity FTBFS

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1647600] Re: Xvfb fails with new mesa, results in ubiquity FTBFS

[LocutusOfBorg]

** Changed in: libepoxy (Ubuntu Yakkety)
   Status: In Progress => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libepoxy in Ubuntu.
https://bugs.launchpad.net/bugs/1647600

Title:
  Xvfb fails with new mesa, results in ubiquity FTBFS

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1724810] Re: 17.10/wayland causing flashes in virtualbox

[LocutusOfBorg]

** Also affects: wayland via
   https://bugzilla.gnome.org/show_bug.cgi?id=788908
   Importance: Unknown
   Status: Unknown

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

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to wayland in Ubuntu.
https://bugs.launchpad.net/bugs/1724810

Title:
  17.10/wayland causing flashes in virtualbox

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1724810] Re: 17.10/wayland causing flashes in virtualbox

[LocutusOfBorg]

Yep, we got the same issue, not sure what wayland is doing, but probably
this is the issue (quoting upstream)

fun: Wayland crashes if you open and close a laptop lid too fast.  This is 
apparently not a bug but a design error in the protocol.
And it has been causing me endless fun over the past week.
https://phabricator.freedesktop.org/T7722
And likely to play havoc with VirtualBox dynamic resizing:
https://bugzilla.gnome.org/show_bug.cgi?id=788908

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

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

** Bug watch added: GNOME Bug Tracker #788908
   https://bugzilla.gnome.org/show_bug.cgi?id=788908

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

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

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

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to wayland in Ubuntu.
https://bugs.launchpad.net/bugs/1724810

Title:
  17.10/wayland causing flashes in virtualbox

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1713313] Re: Unable to launch pkexec'ed applications on Wayland session

[LocutusOfBorg]

the question is more tricky

ettercap has the pkexec file
#!/bin/sh
pkexec --disable-internal-agent "ettercap" "$@"


but it is using a polkit file

http://www.freedesktop.org/standards/PolicyKit/1/policyconfig.dtd;>


  
Authentication is required to run Ettercap
ettercap

  auth_admin
  auth_admin
  auth_admin

@INSTALL_BINDIR@/ettercap
true
  




so, as upstream, I don't know what to do :(

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

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

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1713313] Re: Unable to launch pkexec'ed applications on Wayland session

[LocutusOfBorg]

I don't get where is the problem, wayland or all the applications using
policykit?

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

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

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1687981] Re: Backport packages for 16.04.3 HWE stack

[LocutusOfBorg]

Installed virtualbox-hwe-guest-utils, guest-x11 guest-dkms and everything 
worked correctly.
Removed dkms package and installed vith module-assistant the 
virtualbox-guest-source package.

So far so good, reboot works correctly

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1687981

Title:
  Backport packages for 16.04.3 HWE stack

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1687981] Re: Backport packages for 16.04.3 HWE stack

[LocutusOfBorg]

** Tags removed: block-proposed verification-needed verification-needed-xenial
** Tags added: verification-done verification-done-xenial

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1687981

Title:
  Backport packages for 16.04.3 HWE stack

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1687981] Re: Backport packages for 16.04.3 HWE stack

[LocutusOfBorg]

** Changed in: virtualbox-hwe (Ubuntu)
   Status: New => Fix Committed

** Changed in: virtualbox-hwe (Ubuntu)
 Assignee: (unassigned) => LocutusOfBorg (costamagnagianfranco)

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1687981

Title:
  Backport packages for 16.04.3 HWE stack

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1701948] Re: package libepoxy-dev:amd64 1.3.1-1ubuntu1.17.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting c

[LocutusOfBorg]

please upgrade to .3.1-1ubuntu1.17.04.2

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

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libepoxy in Ubuntu.
https://bugs.launchpad.net/bugs/1701948

Title:
  package libepoxy-dev:amd64 1.3.1-1ubuntu1.17.04.1 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1687981] Re: Backport packages for 16.04.3 HWE stack

[LocutusOfBorg]

I uploaded virtualbox-lts-zesty and tested the hwe 16.04.3 in xenial VM,
installing virtualbox-guest-x11 and or 
virtualbox-guest-dkms/virtualbox-guest-source works.
Even the embedded kernel module works, so we should be good here.

You can test it on ppa:costamagnagianfranco/locutusofborg-ppa

** Tags removed: verification-failed-xenial
** Tags added: verification-needed-xenial

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1687981

Title:
  Backport packages for 16.04.3 HWE stack

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1687981] Re: Backport packages for 16.04.3 HWE stack

[LocutusOfBorg]

Nack on this.
Please wait for virtualbox-guest-x11 being updated.

** Tags removed: verification-done-xenial
** Tags added: block-proposed verification-failed-xenial

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1687981

Title:
  Backport packages for 16.04.3 HWE stack

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1698233] Re: [SRU] New libepoxy0 causes hang at boot for AMDGPU-PRO

[LocutusOfBorg]

** Tags removed: verification-needed
** Tags added: verification-done

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libepoxy in Ubuntu.
https://bugs.launchpad.net/bugs/1698233

Title:
  [SRU] New libepoxy0 causes hang at boot for AMDGPU-PRO

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1698233] Re: [SRU] New libepoxy0 causes hang at boot for AMDGPU-PRO

[LocutusOfBorg]

zesty seems to work correctly, Robert, can you please test xenial?'

** Tags removed: verification-needed-zesty
** Tags added: verification-done-zesty

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libepoxy in Ubuntu.
https://bugs.launchpad.net/bugs/1698233

Title:
  [SRU] New libepoxy0 causes hang at boot for AMDGPU-PRO

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1698233] Re: [SRU] New libepoxy0 causes hang at boot for AMDGPU-PRO

[LocutusOfBorg]

Hello, can you please followup with the upstream issue?
Of course I'll be able to do test-builds on top of the new 1.4* release, even 
if I think this issue should be fixed by reverting this particular patch

https://github.com/anholt/libepoxy/issues/130

thanks, your contribution will solve this issue in a better way, because
otherwise the new release will need to carry a patch and introduce
possible issues somewhere else

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libepoxy in Ubuntu.
https://bugs.launchpad.net/bugs/1698233

Title:
  [SRU] New libepoxy0 causes hang at boot for AMDGPU-PRO

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1489878] Re: multi-arch support missing

[LocutusOfBorg]

fixed in artful+ I think

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

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libepoxy in Ubuntu.
https://bugs.launchpad.net/bugs/1489878

Title:
  multi-arch support missing

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1698233] Re: [SRU] New libepoxy0 causes hang at boot for AMDGPU-PRO

[LocutusOfBorg]

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

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

** Changed in: libepoxy (Ubuntu Xenial)
 Assignee: (unassigned) => LocutusOfBorg (costamagnagianfranco)

** Changed in: libepoxy (Ubuntu Zesty)
 Assignee: (unassigned) => LocutusOfBorg (costamagnagianfranco)

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libepoxy in Ubuntu.
https://bugs.launchpad.net/bugs/1698233

Title:
  [SRU] New libepoxy0 causes hang at boot for AMDGPU-PRO

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1698233] Re: [SRU] New libepoxy0 causes hang at boot for AMDGPU-PRO

[LocutusOfBorg]

** Summary changed:

- New libepoxy0 causes hang at boot for AMDGPU-PRO
+ [SRU] New libepoxy0 causes hang at boot for AMDGPU-PRO

** Tags added: regression-proposed regression-release

** Description changed:

+ [Impact] 
+ * Updating libepoxy with the updates pocket (xenial) and the -proposed pocket 
(zesty) breaks systems with AMDGPU-PRO proprietary drivers
+ 
+ [Test Case]
+ * Have that driver/card
+ 
+ [Regression Potential] 
+ * None, I'm disabling a patch that I introduced in the last SRU.
+ * Debian opened an RC bug and will fix the same in the next point release,
+ and I'm discussing with upstream to revert that patch (they should have 
already reverted it)
+ * I just updated it to artful and Debian will follow in a few hours I guess
+ 
+ [Other info]
+ 
  When updating my Xubuntu 16.04.2 system today the upgrade from libepoxy0
  1.3.1-1 to libepoxy0 1.3.1-1ubuntu0.16.04.1 caused my system to hang
  right before the login screen.
  
  Unfortunately since this was a complete system lock up I can't provide
  any logs as I had to restore the entire root partition from backup.
  Since I can't get system recovery mode to work (it's been broken for a
  few years and times out within two minutes) it doesn't give me enough
  time gather any logs before it exits. I understand the system recovery
  problem is known, but I've tried all the solutions I could over the
  years, on multiple systems, and just can't get it to work without timing
  out anymore.
  
  In any case I verified the problem was libepoxy0 by applying all the
  available updates except libexpoxy0 and rebooting without any problems.
  I then allowed the upgrade of libepoxy0, libepoxy0:i386, and libeepoxy-
  dev and the system hung at boot as previously described. I went through
  the same procedure twice to confirm.
  
  I'm running kernel 4.9.31-040931-lowlatency with AMDGPU-PRO 16.50
  patched drivers, with all system updates. If you need more information
  please contact me and I'll get you anything I can. But as I said, since
  the system locks up I'm not sure what else I can garner.
  
  lsb_release -rd:
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04
  
  apt-cache policy libepoxy0:
  libepoxy0:
-   Installed: 1.3.1-1
-   Candidate: 1.3.1-1ubuntu0.16.04.1
-   Version table:
-  1.3.1-1ubuntu0.16.04.1 500
- 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
-  *** 1.3.1-1 500
- 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
- 100 /var/lib/dpkg/status
+   Installed: 1.3.1-1
+   Candidate: 1.3.1-1ubuntu0.16.04.1
+   Version table:
+  1.3.1-1ubuntu0.16.04.1 500
+ 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
+  *** 1.3.1-1 500
+ 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
+ 100 /var/lib/dpkg/status

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

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libepoxy in Ubuntu.
https://bugs.launchpad.net/bugs/1698233

Title:
  [SRU] New libepoxy0 causes hang at boot for AMDGPU-PRO

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1698233] Re: New libepoxy0 causes hang at boot for AMDGPU-PRO

[LocutusOfBorg]

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

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

** Also affects: libepoxy (Ubuntu Zesty)
   Importance: Undecided
   Status: New

** Also affects: libepoxy (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libepoxy in Ubuntu.
https://bugs.launchpad.net/bugs/1698233

Title:
  New libepoxy0 causes hang at boot for AMDGPU-PRO

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1698233] Re: New libepoxy0 causes hang at boot for AMDGPU-PRO

[LocutusOfBorg]

https://github.com/anholt/libepoxy/issues/130
this is now the upstream issue

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libepoxy in Ubuntu.
https://bugs.launchpad.net/bugs/1698233

Title:
  New libepoxy0 causes hang at boot for AMDGPU-PRO

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1698233] Re: New libepoxy0 causes hang at boot

[LocutusOfBorg]

Can you please test libepoxy in this ppa?
https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/costamagnagianfranco-ppa/+packages

I upgraded to the latest 1.4 release, lets see if this is fixed upstream
in a different way.

So, in case testing is good, I'll try to apply some more patch
if testing fails, I'll remove the above patch and re-upload into the archive.

In the meanwhile I'm opening an upstream issue, to trace down this
problem

** Summary changed:

- New libepoxy0 causes hang at boot
+ New libepoxy0 causes hang at boot for AMDGPU-PRO

** Bug watch added: github.com/anholt/libepoxy/issues #130
   https://github.com/anholt/libepoxy/issues/130

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libepoxy in Ubuntu.
https://bugs.launchpad.net/bugs/1698233

Title:
  New libepoxy0 causes hang at boot for AMDGPU-PRO

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1698233] Re: New libepoxy0 causes hang at boot

[LocutusOfBorg]

>On the other hand I know development resources are limited and I won't
blame you if you decide it's not worth the effort because of the very
few people it affects, and the fact that it's AMD's fault not Ubuntu's.

this is something I don't understand, sorry.
I caused a regression, and I will fix it.
I don't care about how difficult it might be, or how many times I'll have to 
ask you to test a fix, but if you agree, lets trace this issue to the bottom, 
and then forward the issue upstream.

I did a new test build, since the difference between the working one and the 
bad one are 4 patches, and two of them are just null pointer checks, I disabled 
one of the two,
in particular:
"upstream/8d58c890646fc1f43bcab702bb9ed6bae94daefe.patch"

this patch changes a little bit the API to get the gl context, so maybe
since the proprietary drivers are old, it might be causing your issue.

The other patch that might be source of troubles is this one:
debian/patches/upstream/b3b8bd9af7bf1fcfe544fd131f4d4f0d117ae7bc.patch

because of this change:

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libepoxy in Ubuntu.
https://bugs.launchpad.net/bugs/1698233

Title:
  New libepoxy0 causes hang at boot

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1698233] Re: New libepoxy0 causes hang at boot

[LocutusOfBorg]

(no edit button, sigh)

-ret = client < server  ?  client  :  server

that changed to:
+ret = client <= server  ?  client  :  server

now, if server is equaul to client, there is no point in returning the former 
or the latter
(same value), so I would exclude this one too.

the package to test is uploaded on my ppa
 libepoxy - 1.3.1-1ubuntu1.16.04.2 

and the url you have to add in sources.list to grab it is:
"deb http://ppa.launchpad.net/costamagnagianfranco/locutusofborg-ppa/ubuntu 
xenial main"

please test if possible, thanks!

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libepoxy in Ubuntu.
https://bugs.launchpad.net/bugs/1698233

Title:
  New libepoxy0 causes hang at boot

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1698233] Re: New libepoxy0 causes hang at boot

[LocutusOfBorg]

@Robert, please dpkg -l |grep libepox
on the system that is not starting.
thanks

you are giving me two opposite answers, lets start from that :)

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libepoxy in Ubuntu.
https://bugs.launchpad.net/bugs/1698233

Title:
  New libepoxy0 causes hang at boot

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1698233] Re: New libepoxy0 causes hang at boot

[LocutusOfBorg]

so, even a no-change rebuild is bad... this is completely unrelated to my fix 
then.
Will try to have a look tomorrow

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libepoxy in Ubuntu.
https://bugs.launchpad.net/bugs/1698233

Title:
  New libepoxy0 causes hang at boot

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1698233] Re: New libepoxy0 causes hang at boot

[LocutusOfBorg]

E.g. I uploaded a libepoxy that is the same as the xenial working one, just 
rebuilt on top of new dependencies.
I would like to ask you to test it, just to make sure the eventual regression 
is not coming from somewhere else
(e.g. a bug in the toolchain can be spot with a no-change rebuild)
please test
https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/locutusofborg-ppa/+packages
 libepoxy - 1.3.1-1ubuntu1 

thanks!

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libepoxy in Ubuntu.
https://bugs.launchpad.net/bugs/1698233

Title:
  New libepoxy0 causes hang at boot

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1698233] Re: New libepoxy0 causes hang at boot

[LocutusOfBorg]

Interestingly, I would add a question for you:
are you available to test some ppa libepoxy versions?
I admit, you are the first one reporting this issue, with a package that has 
thousand installations.

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libepoxy in Ubuntu.
https://bugs.launchpad.net/bugs/1698233

Title:
  New libepoxy0 causes hang at boot

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1647600] Re: Xvfb fails with new mesa, results in ubiquity FTBFS

[LocutusOfBorg]

dpkg-deb: building package 'ubiquity-frontend-gtk' in 
'../ubiquity-frontend-gtk_17.04.9_amd64.deb'.
dpkg-deb: building package 'ubiquity' in '../ubiquity_17.04.9_amd64.deb'.
dpkg-deb: building package 'ubiquity-frontend-debconf' in 
'../ubiquity-frontend-debconf_17.04.9_amd64.deb'.

it builds fine!

** Tags removed: verification-needed
** Tags added: verification-done-zesty

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libepoxy in Ubuntu.
https://bugs.launchpad.net/bugs/1647600

Title:
  Xvfb fails with new mesa, results in ubiquity FTBFS

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1647600] Re: Xvfb fails with new mesa, results in ubiquity FTBFS

[LocutusOfBorg]

Get:333 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 
libepoxy-dev amd64 1.3.1-1ubuntu0.16.04.1 [112 kB]
[...]
dh_md5sums
NO_PNG_PKG_MANGLE=1 dh_builddeb -- -Zxz
dpkg-deb: building package 'ubiquity' in '../ubiquity_2.21.63.3_amd64.deb'.
dpkg-deb: building package 'ubiquity-frontend-debconf' in 
'../ubiquity-frontend-debconf_2.21.63.3_amd64.deb'.
dpkg-deb: building package 'ubiquity-frontend-gtk' in 
'../ubiquity-frontend-gtk_2.21.63.3_amd64.deb'.
 dpkg-genchanges  >../ubiquity_2.21.63.3_amd64.changes


seems good

** Tags removed: verification-needed
** Tags added: verification-done-xenial

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libepoxy in Ubuntu.
https://bugs.launchpad.net/bugs/1647600

Title:
  Xvfb fails with new mesa, results in ubiquity FTBFS

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1647600] Re: Xvfb fails with new mesa, results in ubiquity FTBFS

[LocutusOfBorg]

I can see that ubiquity now is building correctly, and nobody reported
regressions so far

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libepoxy in Ubuntu.
https://bugs.launchpad.net/bugs/1647600

Title:
  Xvfb fails with new mesa, results in ubiquity FTBFS

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1647600] Re: Xvfb fails with new mesa, results in ubiquity FTBFS

[LocutusOfBorg]

Ping, can anybody please verify this?

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libepoxy in Ubuntu.
https://bugs.launchpad.net/bugs/1647600

Title:
  Xvfb fails with new mesa, results in ubiquity FTBFS

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1574886] Re: All gtk applications Segfault if no GLX context is active

[LocutusOfBorg]

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

can you please test libepoxy from my ppa?
 https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/locutusofborg-ppa

please report back results on bug:
https://bugs.launchpad.net/ubuntu/+source/libepoxy/+bug/1647600

this is a duplicate bug.

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libepoxy in Ubuntu.
https://bugs.launchpad.net/bugs/1574886

Title:
  All gtk applications Segfault if no GLX context is active

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1664742] Re: libepoxy causes a crash when there is no GL

[LocutusOfBorg]

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

can you please test libepoxy from my ppa?
 https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/locutusofborg-ppa

please report back results on bug:
https://bugs.launchpad.net/ubuntu/+source/libepoxy/+bug/1647600

this is a duplicate bug.

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libepoxy in Ubuntu.
https://bugs.launchpad.net/bugs/1664742

Title:
  libepoxy causes a crash when there is no GL

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1647600] Re: Xvfb fails with new mesa, results in ubiquity FTBFS

[LocutusOfBorg]

can anybody please test my ppa?
I pushed no change rebuilds for ubiquity and the fixes for libepoxy there
https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/locutusofborg-ppa

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

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

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

** Changed in: libepoxy (Ubuntu Xenial)
 Assignee: (unassigned) => LocutusOfBorg (costamagnagianfranco)

** Changed in: libepoxy (Ubuntu Zesty)
 Assignee: (unassigned) => LocutusOfBorg (costamagnagianfranco)

** Changed in: libepoxy (Ubuntu Yakkety)
 Assignee: (unassigned) => LocutusOfBorg (costamagnagianfranco)

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libepoxy in Ubuntu.
https://bugs.launchpad.net/bugs/1647600

Title:
  Xvfb fails with new mesa, results in ubiquity FTBFS

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1647600] Re: Xvfb fails with new mesa, results in ubiquity FTBFS

[LocutusOfBorg]

** Attachment added: "debdiff-zesty"
   
https://bugs.launchpad.net/ubuntu/+source/libepoxy/+bug/1647600/+attachment/4889895/+files/debdiff-zesty

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libepoxy in Ubuntu.
https://bugs.launchpad.net/bugs/1647600

Title:
  Xvfb fails with new mesa, results in ubiquity FTBFS

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1647600] Re: Xvfb fails with new mesa, results in ubiquity FTBFS

[LocutusOfBorg]

** Changed in: libepoxy (Ubuntu Yakkety)
   Status: New => In Progress

** Changed in: libepoxy (Ubuntu Zesty)
   Status: New => In Progress

** Description changed:

  [Impact]
  
  fakeroot ./debian/rules tests
  
  from ubiquity 17.04.1 package, from zesty-proposed to build
  successfully.
  
  It does in zesty-release. It does in zesty-proposed too, if one
  downgrades: libgl1-mesa-glx libglapi-mesa
  
  If one uses libgl1-mesa-glx libglapi-mesa from zesty-proposed, the Xvfb
  fails to spawn and thus tests fail, and the build fails.
  
  [Test case]
  
+ * try an ssh -X and start emacs
+ * launch apport-gtk with new mesa installed
+ 
  [Regression potential]
+ * none, part of upstream code, they are checks for null pointer exceptions, 
missing in the current code

** Attachment added: "debdiff-yakkety"
   
https://bugs.launchpad.net/ubuntu/+source/libepoxy/+bug/1647600/+attachment/4889894/+files/debdiff-yakkety

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libepoxy in Ubuntu.
https://bugs.launchpad.net/bugs/1647600

Title:
  Xvfb fails with new mesa, results in ubiquity FTBFS

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1647600] Re: Xvfb fails with new mesa, results in ubiquity FTBFS

[LocutusOfBorg]

** Also affects: libepoxy (Ubuntu Zesty)
   Importance: Undecided
   Status: New

** Also affects: libepoxy (Ubuntu Artful)
   Importance: Critical
 Assignee: Timo Aaltonen (tjaalton)
   Status: Fix Released

** Also affects: libepoxy (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libepoxy in Ubuntu.
https://bugs.launchpad.net/bugs/1647600

Title:
  Xvfb fails with new mesa, results in ubiquity FTBFS

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1647600] Re: Xvfb fails with new mesa, results in ubiquity FTBFS

[LocutusOfBorg]

** Attachment added: "debdiff-xenial"
   
https://bugs.launchpad.net/ubuntu/+source/libepoxy/+bug/1647600/+attachment/4889868/+files/debdiff-xenial

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libepoxy in Ubuntu.
https://bugs.launchpad.net/bugs/1647600

Title:
  Xvfb fails with new mesa, results in ubiquity FTBFS

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1647600] Re: Xvfb fails with new mesa, results in ubiquity FTBFS

[LocutusOfBorg]

I did a sync and rebased the above patch, would be nice to recheck it on
artful

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libepoxy in Ubuntu.
https://bugs.launchpad.net/bugs/1647600

Title:
  Xvfb fails with new mesa, results in ubiquity FTBFS

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1671377] Re: Crash in VirtualBox with libdrm/intel, fixed in git

[LocutusOfBorg]

Michael you rock! I tried hard to understand the reasons for that
failure/crash, thanks for fixing!

** Changed in: libdrm (Ubuntu)
   Status: Confirmed => Fix Committed

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

Title:
  Crash in VirtualBox with libdrm/intel, fixed in git

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1666059] Re: Main virtualbox window resizes itself 3 or 4 times - then no desktop start

[LocutusOfBorg]

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

Timo, you rock!
it works with that patch, uploaded in Ubuntu


** This bug has been marked a duplicate of bug 1671377
   Crash in VirtualBox with libdrm/intel, fixed in git

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1666059

Title:
  Main virtualbox window resizes itself 3 or 4 times - then no desktop
  start

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1666059] Re: Main virtualbox window resizes itself 3 or 4 times - then no desktop start

[LocutusOfBorg]

it is not helping... I did test with a vbox custom on my
ppa:costamagnagianfranco/locutusofborg-ppa

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1666059

Title:
  Main virtualbox window resizes itself 3 or 4 times - then no desktop
  start

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1666059] Re: Main virtualbox window resizes itself 3 or 4 times - then no desktop start

[LocutusOfBorg]

that vboxvideo has been dropped upstream, I also tried an rm on my zesty
vm of that file but it didn't change the boot issue.

I don't understand your modeset sentence, because actually I don't understand
what vboxvideo does (kernel module)
what the driver is supposed to do, and what/how that vbox*GL* libs can replace 
the vboxvideo_drv

I mostly do what upstream does here:
https://anonscm.debian.org/cgit/pkg-virtualbox/virtualbox.git/tree/src/VBox/Additions/linux/installer/vboxadd.sh#n223

but there is one difference, installing the guest additions works, the
my approach worked in Debian and works in Debian, and worked in Ubuntu
before zesty.

Zesty changed something I can't understand (and breaks only my build,
not the upstream install script)

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

Title:
  Main virtualbox window resizes itself 3 or 4 times - then no desktop
  start

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1666059] Re: Main virtualbox window resizes itself 4 or 4 times - then no start

[LocutusOfBorg]

putting xorg developers in the loop

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

Title:
  Main virtualbox window resizes itself 4 or 4 times - then no start

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1666059] Re: Main virtualbox window resizes itself 4 or 4 times - then no start

[LocutusOfBorg]

not sure if mesa has something to do here, because we are using ld to
override the ld.so.conf.d EGL and GL configuration files

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

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

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1666059

Title:
  Main virtualbox window resizes itself 4 or 4 times - then no start

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1247528] Re: [SRU] Build and distribute intel-virtual-output

[LocutusOfBorg]

the new binary is here now.

** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  [SRU] Build and distribute intel-virtual-output

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1247528] Re: [SRU] Build and distribute intel-virtual-output

[LocutusOfBorg]

** Summary changed:

- Build and distribute intel-virtual-output
+ [SRU] Build and distribute intel-virtual-output

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

Title:
  [SRU] Build and distribute intel-virtual-output

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1247528] Re: Build and distribute intel-virtual-output

[LocutusOfBorg]

Hi, I sponsored it, even if the package increased its size for about 1MB.
The patch was sane enough, a cherry-pick from later releases, and just a new 
tool added
(I also melded both changelogs, to see if the new dependencies were carrying 
new hidden tools/flags).
the package is now in unapproved queue
https://launchpad.net/ubuntu/trusty/+queue?queue_state=1_text=

** Changed in: xserver-xorg-video-intel (Ubuntu Trusty)
   Status: In Progress => Fix Committed

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

Title:
  Build and distribute intel-virtual-output

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1247528] Re: Build and distribute intel-virtual-output

[LocutusOfBorg]

it seems to be not building
https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/locutusofborg-ppa/+build/11521054

** Changed in: xserver-xorg-video-intel (Ubuntu)
   Status: In Progress => Incomplete

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

Title:
  Build and distribute intel-virtual-output

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1636728] Re: [MIR] khronos-opencl-clhpp

[LocutusOfBorg]

I pinged Ubuntu-x-swat team over irc and subscribed it to this bug :)

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1636728

Title:
  [MIR] khronos-opencl-clhpp

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/khronos-opencl-clhpp/+bug/1636728/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1412441] Re: [MIR] libclc

[LocutusOfBorg]

The fixed llvm is on proposed

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libclc in Ubuntu.
https://bugs.launchpad.net/bugs/1412441

Title:
  [MIR] libclc

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1412441] Re: [MIR] libclc

[LocutusOfBorg]

I would appreciate to wait a little bit, I asked to Sylvestre (the
Debian Developer and Maintainer of llvm) an ack about my changes.

Please hold on.

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libclc in Ubuntu.
https://bugs.launchpad.net/bugs/1412441

Title:
  [MIR] libclc

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1320990] Re: [xorg-edgers] BOINC can't find CUDA driver with xorg-edgers packages

[LocutusOfBorg]

Thanks for confirming the fix!

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

Title:
  [xorg-edgers] BOINC can't find CUDA driver with xorg-edgers packages

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1320990] Re: [xorg-edgers] BOINC can't find CUDA driver with xorg-edgers packages

[LocutusOfBorg]

Yes, I know, I did some hard work on the last two days :)

cheers!

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

Title:
  [xorg-edgers] BOINC can't find CUDA driver with xorg-edgers packages

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1511649] [NEW] please merge xorg-server from debian

[LocutusOfBorg]

Public bug reported:

I would like to have the new xorg-legacy package to fix the virtualbox
installation.

NOTE: I'm not asking for a sponsor, I'm providing a debdiff just for
your best convenience.

This merge will introduce the new rootless X mode, but AFAICS systemd-
logind is already in place here.

builds ongoing on
https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/locutusofborg-ppa/+build/8220795

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


** Tags: patch

** Patch added: "debdiff"
   https://bugs.launchpad.net/bugs/1511649/+attachment/4509116/+files/debdiff

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

Title:
  please merge xorg-server from debian

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1129409] Re: [SRU] Nvidia and AMD graphics drivers should indicate whether they provide libcuda.so.1, libOpenCL.so.1, etc.

[LocutusOfBorg]

I could install fglrx-installer and wine1.6 together. everything seems
fine to me.

thanks for fixing!

** Tags removed: verification-needed
** Tags added: verification-done

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1129409

Title:
  [SRU] Nvidia and AMD graphics drivers should indicate whether they
  provide libcuda.so.1, libOpenCL.so.1, etc.

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1129409] Re: [SRU] Nvidia and AMD graphics drivers should indicate whether they provide libcuda.so.1, libOpenCL.so.1, etc.

[LocutusOfBorg]

I tested it and I succeeded in installing them together.

** Tags removed: verification-needed
** Tags added: verification-done

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1129409

Title:
  [SRU] Nvidia and AMD graphics drivers should indicate whether they
  provide libcuda.so.1, libOpenCL.so.1, etc.

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1443668] Re: package fglrx 2:15.200-0ubuntu0.1 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 2

[LocutusOfBorg]

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

** This bug has been marked a duplicate of bug 1443016
   package fglrx-updates-core 2:15.200-0ubuntu0.1 failed to install/upgrade: 
trying to overwrite '/etc/acpi/fglrx-powermode.sh', which is also in package 
fglrx-updates 2:13.350.1-0ubuntu2

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1443668

Title:
  package fglrx 2:15.200-0ubuntu0.1 failed to install/upgrade: sub-
  processo script post-installation instalado retornou estado de saída
  de erro 2

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1129409] Re: Nvidia and AMD graphics drivers should indicate whether they provide libcuda.so.1, libOpenCL.so.1, etc.

[LocutusOfBorg]

Can anybody please follow up with the SRU?
alsot this patch should be applied, right?
http://launchpadlibrarian.net/200634903/fglrx-installer_2%3A15.200-0ubuntu1_2%3A15.200-0ubuntu2.diff.gz

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1129409

Title:
  Nvidia and AMD graphics drivers should indicate whether they provide
  libcuda.so.1, libOpenCL.so.1, etc.

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1129409] Re: Nvidia and AMD graphics drivers should indicate whether they provide libcuda.so.1, libOpenCL.so.1, etc.

[LocutusOfBorg]

utopic debdiff for installer

** Attachment added: debdiff-installer-utopic
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-cuda-toolkit/+bug/1129409/+attachment/4350064/+files/debdiff-installer-utopic

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1129409

Title:
  [SRU] Nvidia and AMD graphics drivers should indicate whether they
  provide libcuda.so.1, libOpenCL.so.1, etc.

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1129409] Re: Nvidia and AMD graphics drivers should indicate whether they provide libcuda.so.1, libOpenCL.so.1, etc.

[LocutusOfBorg]

I don't know about the trusty fix.

** Summary changed:

- Nvidia and AMD graphics drivers should indicate whether they provide 
libcuda.so.1, libOpenCL.so.1, etc.
+ [SRU] Nvidia and AMD graphics drivers should indicate whether they provide 
libcuda.so.1, libOpenCL.so.1, etc.

** Description changed:

+ [Impact]
+ 
+ * wine and fglrx are not coinstallable.
+ 
+ [Test Case]
+ 
+  * try to install them
+  * there is a conflict with libopencl1 in control file, preventing 
coinstallation.
+ 
  The nvidia-cuda-toolkit package needs to depend on a minimum version of the 
CUDA library included in nvidia-graphics-drivers.
  The current Debian version of nvidia-cuda-toolkit (5.0.35-4) does this on 
Debian systems by checking the version of libcuda1 and on Ubuntu systems by 
checking the version of nvidia-current, nvidia-curent-updates, 
nvidia-experimental-304 or nvidia-experimental-310.
  
  It would greatly simplify maintenance of packages building against
  libcuda.so.1 and libOpenCL.so.1 if the nvidia-graphics drivers could
  provide virtual packages that reflect the API level, for example,
  libcuda-5.0-1 and libopencl-1.2-1.
  
  It was decided that the nvidia drivers packages will provide libcuda-5.0-1, 
libopencl1 and opencl-icd (LP: #763457) virtual packages. Additionally, 
nvidia-*.shlibs would contain:
  libOpenCL  1 libopencl1
  libcuda1 libcuda-5.0-1
  libGL 1 libgl1
  
  Similarly, the amd drivers package will provide libopencl1 and opencl-icd 
virtual packages, as well as an .shlibs containing:
  libOpenCL  1 libopencl1
  libGL 1 libgl1

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1129409

Title:
  [SRU] Nvidia and AMD graphics drivers should indicate whether they
  provide libcuda.so.1, libOpenCL.so.1, etc.

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1129409] Re: Nvidia and AMD graphics drivers should indicate whether they provide libcuda.so.1, libOpenCL.so.1, etc.

[LocutusOfBorg]

Uploading on ppa:costamagnagianfranco/locutusofborg-ppa

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1129409

Title:
  [SRU] Nvidia and AMD graphics drivers should indicate whether they
  provide libcuda.so.1, libOpenCL.so.1, etc.

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1129409] Re: Nvidia and AMD graphics drivers should indicate whether they provide libcuda.so.1, libOpenCL.so.1, etc.

[LocutusOfBorg]

utopic debdiff for updates

** Attachment added: debdiff-updates-utopic
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-cuda-toolkit/+bug/1129409/+attachment/4350065/+files/debdiff-updates-utopic

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1129409

Title:
  [SRU] Nvidia and AMD graphics drivers should indicate whether they
  provide libcuda.so.1, libOpenCL.so.1, etc.

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1129409] Re: Nvidia and AMD graphics drivers should indicate whether they provide libcuda.so.1, libOpenCL.so.1, etc.

[LocutusOfBorg]

@Graham

sudo apt-get install nvidia-libopencl1-331-updates wine
Reading package lists... Done
Building dependency tree   
Reading state information... Done
nvidia-libopencl1-331-updates is already the newest version.
nvidia-libopencl1-331-updates set to manually installed.
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 wine : Depends: wine1.6 but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

--

sudo apt-get install wine
[snip]
The following packages will be REMOVED:
  nvidia-libopencl1-331-updates


ubuntu 14.04 with latest updates.

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1129409

Title:
  Nvidia and AMD graphics drivers should indicate whether they provide
  libcuda.so.1, libOpenCL.so.1, etc.

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1129409] Re: Nvidia and AMD graphics drivers should indicate whether they provide libcuda.so.1, libOpenCL.so.1, etc.

[LocutusOfBorg]

@graham in my tests on trusty I can install both wine and fglrx
together.

I can't install wine and nvidia-331-updates or nvidia-
libopencl1-331-updates together.

So it seems a different bug, right?

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1129409

Title:
  Nvidia and AMD graphics drivers should indicate whether they provide
  libcuda.so.1, libOpenCL.so.1, etc.

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1129409] Re: Nvidia and AMD graphics drivers should indicate whether they provide libcuda.so.1, libOpenCL.so.1, etc.

[LocutusOfBorg]

hi @nukedathlonman I suggest you to propose a patch :)

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1129409

Title:
  Nvidia and AMD graphics drivers should indicate whether they provide
  libcuda.so.1, libOpenCL.so.1, etc.

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1129409] Re: Nvidia and AMD graphics drivers should indicate whether they provide libcuda.so.1, libOpenCL.so.1, etc.

[LocutusOfBorg]

Hi Graham,
are you sure trusty is affected? I grabbed today a debian directory and seemed 
not affected, but I might be wrong!
BTW thanks for the proposed mapping hint, it will simplify the overall process 
:-)

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1129409

Title:
  Nvidia and AMD graphics drivers should indicate whether they provide
  libcuda.so.1, libOpenCL.so.1, etc.

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1129409] Re: Nvidia and AMD graphics drivers should indicate whether they provide libcuda.so.1, libOpenCL.so.1, etc.

[LocutusOfBorg]

** Patch added: utopic-fglrx-installer-updates.debdiff
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-cuda-toolkit/+bug/1129409/+attachment/4341572/+files/utopic-fglrx-installer-updates.debdiff

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1129409

Title:
  Nvidia and AMD graphics drivers should indicate whether they provide
  libcuda.so.1, libOpenCL.so.1, etc.

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1129409] Re: Nvidia and AMD graphics drivers should indicate whether they provide libcuda.so.1, libOpenCL.so.1, etc.

[LocutusOfBorg]

oops utopic-fglrx-installer.debdiff should be against utopic-proposed

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1129409

Title:
  Nvidia and AMD graphics drivers should indicate whether they provide
  libcuda.so.1, libOpenCL.so.1, etc.

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1129409] Re: Nvidia and AMD graphics drivers should indicate whether they provide libcuda.so.1, libOpenCL.so.1, etc.

[LocutusOfBorg]

Packages are ready in
https://launchpad.net/~costamagnagianfranco/+archive/ubuntu
/locutusofborg-ppa

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1129409

Title:
  Nvidia and AMD graphics drivers should indicate whether they provide
  libcuda.so.1, libOpenCL.so.1, etc.

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1129409] Re: Nvidia and AMD graphics drivers should indicate whether they provide libcuda.so.1, libOpenCL.so.1, etc.

[LocutusOfBorg]

** Patch added: utopic-fglrx-installer.debdiff
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-cuda-toolkit/+bug/1129409/+attachment/4341571/+files/utopic-fglrx-installer.debdiff

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1129409

Title:
  Nvidia and AMD graphics drivers should indicate whether they provide
  libcuda.so.1, libOpenCL.so.1, etc.

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1129409] Re: Nvidia and AMD graphics drivers should indicate whether they provide libcuda.so.1, libOpenCL.so.1, etc.

[LocutusOfBorg]

now that the bug is fixed in the current development release I prepared
two debdiffs against utopic.

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1129409

Title:
  Nvidia and AMD graphics drivers should indicate whether they provide
  libcuda.so.1, libOpenCL.so.1, etc.

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1129409] Re: Nvidia and AMD graphics drivers should indicate whether they provide libcuda.so.1, libOpenCL.so.1, etc.

[LocutusOfBorg]

So I extract the debdiff
diff -Nru fglrx-installer-14.201/debian/changelog 
fglrx-installer-14.201/debian/changelog
--- fglrx-installer-14.201/debian/changelog 2014-10-14 13:25:29.0 
+
+++ fglrx-installer-14.201/debian/changelog 2015-01-14 03:46:21.0 
+
@@ -1,3 +1,10 @@
+fglrx-installer (2:14.201-0ubuntu2ppa1) utopic; urgency=high
+
+  * Change dependencies to allow installing of fglrx and wine
+together (#1129409)
+
+ -- David William Richmond Jones dwr...@gmail.com  Wed, 14 Jan 2015 03:38:03 
+
+
 fglrx-installer (2:14.201-0ubuntu2) utopic; urgency=medium
 
   * debian/fglrx-core.postinst.in, debian/fglrx-core.postrm.in,
diff -Nru fglrx-installer-14.201/debian/control 
fglrx-installer-14.201/debian/control
--- fglrx-installer-14.201/debian/control   2014-10-14 13:25:44.0 
+
+++ fglrx-installer-14.201/debian/control   2015-01-14 03:46:26.0 
+
@@ -27,8 +27,8 @@
 Architecture: amd64 i386
 Depends: ${shlibs:Depends}, lib32gcc1 [amd64], libc6-i386 [amd64], dkms, make, 
linux-libc-dev,
  ${misc:Depends}
-Provides: fglrx-driver-core, libopencl1
-Conflicts: fglrx-driver-core, libopencl1
+Provides: fglrx-driver-core
+Conflicts: fglrx-driver-core
 Replaces: fglrx-driver-core, libopencl1
 Description: Minimal video driver for the AMD graphics accelerators
  Minimal video driver for the AMD Radeon and FireGL graphics accelerators.
diff -Nru fglrx-installer-14.201/debian/control.in 
fglrx-installer-14.201/debian/control.in
--- fglrx-installer-14.201/debian/control.in2014-10-14 13:24:50.0 
+
+++ fglrx-installer-14.201/debian/control.in2015-01-14 03:41:56.0 
+
@@ -27,8 +27,8 @@
 Architecture: amd64 i386
 Depends: ${shlibs:Depends}, lib32gcc1 [amd64], libc6-i386 [amd64], dkms, make, 
linux-libc-dev,
  ${misc:Depends}
-Provides: fglrx-driver-core, libopencl1
-Conflicts: fglrx-driver-core, libopencl1
+Provides: fglrx-driver-core
+Conflicts: fglrx-driver-core
 Replaces: fglrx-driver-core, libopencl1
 Description: Minimal video driver for the AMD graphics accelerators
  Minimal video driver for the AMD Radeon and FireGL graphics accelerators.


diff -Nru fglrx-installer-updates-14.201/debian/changelog 
fglrx-installer-updates-14.201/debian/changelog
--- fglrx-installer-updates-14.201/debian/changelog 2014-10-14 
13:29:06.0 +
+++ fglrx-installer-updates-14.201/debian/changelog 2015-01-14 
04:27:42.0 +
@@ -1,3 +1,10 @@
+fglrx-installer-updates (2:14.201-0ubuntu2ppa1) utopic; urgency=high
+
+  * Change dependencies to allow installng of fglrx and wine
+together (#1129409)
+
+ -- David William Richmond Jones dwr...@gmail.com  Wed, 14 Jan 2015 04:24:29 
+
+
 fglrx-installer-updates (2:14.201-0ubuntu2) utopic; urgency=medium
 
   * debian/fglrx-updates-core.postinst.in, debian/fglrx-updates-core.postrm.in,
diff -Nru fglrx-installer-updates-14.201/debian/control 
fglrx-installer-updates-14.201/debian/control
--- fglrx-installer-updates-14.201/debian/control   2014-10-14 
13:29:20.0 +
+++ fglrx-installer-updates-14.201/debian/control   2015-01-14 
04:29:32.0 +
@@ -27,8 +27,8 @@
 Architecture: amd64 i386
 Depends: ${shlibs:Depends}, lib32gcc1 [amd64], libc6-i386 [amd64], dkms, make, 
linux-libc-dev,
  ${misc:Depends}
-Provides: fglrx-driver-core, libopencl1
-Conflicts: fglrx-driver-core, libopencl1
+Provides: fglrx-driver-core
+Conflicts: fglrx-driver-core
 Replaces: fglrx-driver-core, libopencl1
 Description: Minimal video driver for the AMD graphics accelerators
  Minimal video driver for the AMD Radeon and FireGL graphics accelerators.
diff -Nru fglrx-installer-updates-14.201/debian/control.in 
fglrx-installer-updates-14.201/debian/control.in
--- fglrx-installer-updates-14.201/debian/control.in2014-10-14 
13:24:50.0 +
+++ fglrx-installer-updates-14.201/debian/control.in2015-01-14 
04:24:24.0 +
@@ -27,8 +27,8 @@
 Architecture: amd64 i386
 Depends: ${shlibs:Depends}, lib32gcc1 [amd64], libc6-i386 [amd64], dkms, make, 
linux-libc-dev,
  ${misc:Depends}
-Provides: fglrx-driver-core, libopencl1
-Conflicts: fglrx-driver-core, libopencl1
+Provides: fglrx-driver-core
+Conflicts: fglrx-driver-core
 Replaces: fglrx-driver-core, libopencl1
 Description: Minimal video driver for the AMD graphics accelerators
  Minimal video driver for the AMD Radeon and FireGL graphics accelerators.

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-313-updates in Ubuntu.
https://bugs.launchpad.net/bugs/1129409

Title:
  Nvidia and AMD graphics drivers should indicate whether they provide
  libcuda.so.1, libOpenCL.so.1, etc.

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : 

[Ubuntu-x-swat] [Bug 1129409] Re: Nvidia and AMD graphics drivers should indicate whether they provide libcuda.so.1, libOpenCL.so.1, etc.

[LocutusOfBorg]

Can you please post the debdiff here and subscribe ubuntu-sponsors?

thanks

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-313-updates in Ubuntu.
https://bugs.launchpad.net/bugs/1129409

Title:
  Nvidia and AMD graphics drivers should indicate whether they provide
  libcuda.so.1, libOpenCL.so.1, etc.

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1129409] Re: Nvidia and AMD graphics drivers should indicate whether they provide libcuda.so.1, libOpenCL.so.1, etc.

[LocutusOfBorg]

Hi David, can you please tell what is missing for that? I see most
packages have been fixed, can you help with a debdiff or a package name?

thanks

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-313-updates in Ubuntu.
https://bugs.launchpad.net/bugs/1129409

Title:
  Nvidia and AMD graphics drivers should indicate whether they provide
  libcuda.so.1, libOpenCL.so.1, etc.

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1129409] Re: Nvidia and AMD graphics drivers should indicate whether they provide libcuda.so.1, libOpenCL.so.1, etc.

[LocutusOfBorg]

So I did the easy trick and uploaded the patch on
ppa:costamagnagianfranco/locutusofborg-ppa

please test it!

(uploaded for trusty/utopic/vivid)

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-313-updates in Ubuntu.
https://bugs.launchpad.net/bugs/1129409

Title:
  Nvidia and AMD graphics drivers should indicate whether they provide
  libcuda.so.1, libOpenCL.so.1, etc.

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1129409] Re: Nvidia and AMD graphics drivers should indicate whether they provide libcuda.so.1, libOpenCL.so.1, etc.

[LocutusOfBorg]

** Attachment added: debdiff.fglrx-installer-updates
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-cuda-toolkit/+bug/1129409/+attachment/4297176/+files/debdiff.fglrx-installer-updates

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-313-updates in Ubuntu.
https://bugs.launchpad.net/bugs/1129409

Title:
  Nvidia and AMD graphics drivers should indicate whether they provide
  libcuda.so.1, libOpenCL.so.1, etc.

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1129409] Re: Nvidia and AMD graphics drivers should indicate whether they provide libcuda.so.1, libOpenCL.so.1, etc.

[LocutusOfBorg]

** Attachment added: debdiff.fglrx-installer
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-cuda-toolkit/+bug/1129409/+attachment/4297175/+files/debdiff.fglrx-installer

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-313-updates in Ubuntu.
https://bugs.launchpad.net/bugs/1129409

Title:
  Nvidia and AMD graphics drivers should indicate whether they provide
  libcuda.so.1, libOpenCL.so.1, etc.

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1129409] Re: Nvidia and AMD graphics drivers should indicate whether they provide libcuda.so.1, libOpenCL.so.1, etc.

[LocutusOfBorg]

So I hope Alberto will fix this issue, I don't know how to best deal
with it then.

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-313-updates in Ubuntu.
https://bugs.launchpad.net/bugs/1129409

Title:
  Nvidia and AMD graphics drivers should indicate whether they provide
  libcuda.so.1, libOpenCL.so.1, etc.

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1320990] Re: [xorg-edgers] BOINC can't find CUDA driver with xorg-edgers packages

[LocutusOfBorg]

fix committed in debian anonscm.debian.org/gitweb/?p=pkg-
boinc/boinc.git;a=commitdiff;h=be4e9eb

will be fixed in boinc in the next few months.

But I think this isn't a boinc bug

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

Title:
  [xorg-edgers] BOINC can't find CUDA driver with xorg-edgers packages

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 905686] Re: nautilus assert failure: nautilus: ../../src/xcb_io.c:528: _XAllocID: Assertion `ret != inval_id' failed.

[LocutusOfBorg]

** Changed in: nautilus (Ubuntu)
 Assignee: W1zz4r (cesar309bermudez) = (unassigned)

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libx11 in Ubuntu.
https://bugs.launchpad.net/bugs/905686

Title:
  nautilus assert failure: nautilus: ../../src/xcb_io.c:528: _XAllocID:
  Assertion `ret != inval_id' failed.

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1263800] Re: xserver broken after ubuntu update: nvidia api mismatch

[LocutusOfBorg]

** Also affects: nvidia-graphics-drivers (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  xserver broken after ubuntu update: nvidia api mismatch

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1129409] Re: Nvidia and AMD graphics drivers should indicate whether they provide libcuda.so.1, libOpenCL.so.1, etc.

[LocutusOfBorg]

Fix released on debian, this bug will be automatically fixed on the next
sync

** Changed in: boinc (Ubuntu)
   Status: Confirmed = Fix Committed

** Changed in: boinc (Ubuntu)
 Assignee: (unassigned) = LocutusOfBorg (costamagnagianfranco)

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-313-updates in Ubuntu.
https://bugs.launchpad.net/bugs/1129409

Title:
  Nvidia and AMD graphics drivers should indicate whether they provide
  libcuda.so.1, libOpenCL.so.1, etc.

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1129409] Re: nvidia-graphics-drivers should indicate which versions of libcuda.so.1 and libOpenCL.so.1 they include

[LocutusOfBorg]

Ok thanks, do you plan to release a libcuda1-ia32 package too?
http://packages.debian.org/it/squeeze/libcuda1-ia32

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-313-updates in Ubuntu.
https://bugs.launchpad.net/bugs/1129409

Title:
  nvidia-graphics-drivers should indicate which versions of libcuda.so.1
  and libOpenCL.so.1 they include

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1129409] Re: nvidia-graphics-drivers should indicate which versions of libcuda.so.1 and libOpenCL.so.1 they include

[LocutusOfBorg]

Alberto I don't understand, should now ubuntu provide a libcuda1 package
like debian does?

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-313-updates in Ubuntu.
https://bugs.launchpad.net/bugs/1129409

Title:
  nvidia-graphics-drivers should indicate which versions of libcuda.so.1
  and libOpenCL.so.1 they include

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1155327] Re: skype crashed with SIGSEGV in malloc@plt()

[LocutusOfBorg]

did you try to delete /usr/share/doc/libqtwebkit4/changelog.Debian.gz ?

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

Title:
  skype crashed with SIGSEGV in malloc@plt()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1155327/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1155327] Re: skype crashed with SIGSEGV in malloc@plt()

[LocutusOfBorg]

did you run sudo apt-get update?

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

Title:
  skype crashed with SIGSEGV in malloc@plt()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1155327/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1129409] Re: nvidia-graphics-drivers should indicate which CUDA version they include

[LocutusOfBorg]

what should we do on the boinc side?
the problem is in libcuda, not in boinc, right?

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

Title:
  nvidia-graphics-drivers should indicate which CUDA version they
  include

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1134466] Re: Update request and SRU request - Update to Mesa 9.0.3 stable

[LocutusOfBorg]

Why this update wants to remove google earth, wine, teamviewer and so
on?

I seguenti pacchetti saranno RIMOSSI:
  google-earth-stable ia32-libs ia32-libs-multiarch:i386 libgl1-mesa-dri:i386 
libgl1-mesa-glx:i386 libglapi-mesa:i386 libglu1-mesa:i386
  libqt4-opengl:i386 libvisual-0.4-plugins:i386 teamviewer wine1.4 
wine1.4-amd64 wine1.4-common wine1.4-i386:i386
I seguenti pacchetti sono stati mantenuti alla versione attuale:
  linux-headers-generic linux-image-generic
I seguenti pacchetti saranno aggiornati:
  libgl1-mesa-dev libgl1-mesa-dri libgl1-mesa-glx libglapi-mesa mesa-common-dev
5 aggiornati, 0 installati, 14 da rimuovere e 2 non aggiornati.
È necessario scaricare 3286 kB di archivi.

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1134466

Title:
  Update request and SRU request - Update to Mesa 9.0.3 stable

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1134466] Re: Update request and SRU request - Update to Mesa 9.0.3 stable

[LocutusOfBorg]

Updating the system BREAKS everything.

No more teamviewer, wine, ia32-libs and so on.

** Tags removed: verification-needed
** Tags added: verification-failed

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1134466

Title:
  Update request and SRU request - Update to Mesa 9.0.3 stable

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1134466] Re: Update request and SRU request - Update to Mesa 9.0.3 stable

[LocutusOfBorg]

Sorry, I missed this, I looked into the build logs but I missed it... :)
I have to drink more coffee before complaining! ;)

** Tags removed: verification-failed
** Tags added: verification-needed

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1134466

Title:
  Update request and SRU request - Update to Mesa 9.0.3 stable

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 993187] Re: ubuntu 12.04 completely freezes frequently.

[LocutusOfBorg]

If you need to look for a log I suggest to run ls with the thor
powers.

ls -thor gives you the log ordered by date and time :)

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

Title:
  ubuntu 12.04 completely freezes frequently.

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp