[Desktop-packages] [Bug 1408107] Re: Can't remove huge files from samba share on first attempt - Input/output error

2015-03-08 Thread Ross Lagerwall
I've seen at least once before an embedded Samba server which crashed
due to the client's access pattern, even though the client was sending
valid commands.

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

Title:
  Can't remove huge files from samba share on first attempt -
  Input/output error

Status in gvfs package in Ubuntu:
  New

Bug description:
  I'm using Ubuntu 14.04. I'm trying to delete huge (10-20 gigs) files
  from a samba share but it always fails for the first try:

  
username@hostname:/run/user/1000/gvfs/smb-share:server=192.168.1.1,share=download$
 rm -r Testdir/
  rm: cannot remove ‘Testdir/13gigs-Testfile.mkv’: Input/output error
  
username@hostname:/run/user/1000/gvfs/smb-share:server=192.168.1.1,share=download$
 rm -r Testdir/
  
username@hostname:/run/user/1000/gvfs/smb-share:server=192.168.1.1,share=download$
 rm -r Testdir/
  rm: cannot remove ‘Testdir/’: No such file or directory
  
username@hostname:/run/user/1000/gvfs/smb-share:server=192.168.1.1,share=download$
 

  The same thing is happening if I use Nautilus. This is bugging me a lot 
because I'm always having a hard time deleting stuff.
  My quess is that the deletion process times out too early so it doesn't have 
enough time to delete such big files.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gvfs 1.20.1-1ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
  Uname: Linux 3.13.0-43-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jan  6 22:22:30 2015
  InstallationDate: Installed on 2013-10-30 (433 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: gvfs
  UpgradeStatus: Upgraded to trusty on 2014-05-04 (247 days ago)

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

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


[Desktop-packages] [Bug 410288] Re: Nautilus does not handle FTP timeouts well

2015-03-05 Thread Ross Lagerwall
See the bottom of the log: "Attempt to unlock mutex that was not locked"

The problem is that glib 2.42, used in Ubuntu 14.10 became more strict
about lock checking, and you're using a version of gvfs from a older
version of GNOME which had a locking bug. See this commit
https://git.gnome.org/browse/gvfs/commit/?id=2153d300f24d3388d7c4ab75a55451ad5a581b5a

Unfortunately, mixing and matching bits from different GNOME releases
can cause problems...

For a solution, you could ask the Ubuntu maintainers to add that patch.

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

Title:
  Nautilus does not handle FTP timeouts well

Status in GVFS:
  Fix Released
Status in Nautilus:
  New
Status in gvfs package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: gvfs

  I connected to a FTP server via gvfs in Nautilus. After some time the
  FTP connection is closed automatically, as I observed with wireshark
  (421 No transfer timeout (300 seconds): closing control connection).

  After that, everytime I open a folder on the FTP server I get only an
  "unexpected end of stream" error. To access the FTP server again I
  have to disconnect and then connect again. Nautilus does not seem to
  know that the connection closed.

  A better behaviour IMHO would be to try and reconnect to the FTP
  server.

  ProblemType: Bug
  Architecture: i386
  Date: Fri Aug  7 15:16:05 2009
  DistroRelease: Ubuntu 9.10
  ExecutablePath: /usr/bin/nautilus
  LiveMediaBuild: Ubuntu 9.10 "Karmic Koala" - Alpha i386 (20090722.2)
  Package: nautilus 1:2.27.4-0ubuntu4
  ProcEnviron:
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-5.24-generic
  SourcePackage: nautilus
  Uname: Linux 2.6.31-5-generic i686

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

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


[Desktop-packages] [Bug 410288] Re: Nautilus does not handle FTP timeouts well

2015-03-02 Thread Ross Lagerwall
Oh, after you run the command, mount the ftp share and reproduce the
problem before uploading the log.

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

Title:
  Nautilus does not handle FTP timeouts well

Status in GVFS:
  Fix Released
Status in Nautilus:
  New
Status in gvfs package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: gvfs

  I connected to a FTP server via gvfs in Nautilus. After some time the
  FTP connection is closed automatically, as I observed with wireshark
  (421 No transfer timeout (300 seconds): closing control connection).

  After that, everytime I open a folder on the FTP server I get only an
  "unexpected end of stream" error. To access the FTP server again I
  have to disconnect and then connect again. Nautilus does not seem to
  know that the connection closed.

  A better behaviour IMHO would be to try and reconnect to the FTP
  server.

  ProblemType: Bug
  Architecture: i386
  Date: Fri Aug  7 15:16:05 2009
  DistroRelease: Ubuntu 9.10
  ExecutablePath: /usr/bin/nautilus
  LiveMediaBuild: Ubuntu 9.10 "Karmic Koala" - Alpha i386 (20090722.2)
  Package: nautilus 1:2.27.4-0ubuntu4
  ProcEnviron:
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-5.24-generic
  SourcePackage: nautilus
  Uname: Linux 2.6.31-5-generic i686

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

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


[Desktop-packages] [Bug 410288] Re: Nautilus does not handle FTP timeouts well

2015-03-02 Thread Ross Lagerwall
If you want to help, please run the following in a terminal:
pkill gvfs; GVFS_DEBUG=all `find /usr/lib* -name 'gvfsd'` &> ~/log.txt
and then upload log.txt in your home directory so we can see a log of what is 
happening.

sftp is a completely different protocol so it's expected to be
different.

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

Title:
  Nautilus does not handle FTP timeouts well

Status in GVFS:
  Fix Released
Status in Nautilus:
  New
Status in gvfs package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: gvfs

  I connected to a FTP server via gvfs in Nautilus. After some time the
  FTP connection is closed automatically, as I observed with wireshark
  (421 No transfer timeout (300 seconds): closing control connection).

  After that, everytime I open a folder on the FTP server I get only an
  "unexpected end of stream" error. To access the FTP server again I
  have to disconnect and then connect again. Nautilus does not seem to
  know that the connection closed.

  A better behaviour IMHO would be to try and reconnect to the FTP
  server.

  ProblemType: Bug
  Architecture: i386
  Date: Fri Aug  7 15:16:05 2009
  DistroRelease: Ubuntu 9.10
  ExecutablePath: /usr/bin/nautilus
  LiveMediaBuild: Ubuntu 9.10 "Karmic Koala" - Alpha i386 (20090722.2)
  Package: nautilus 1:2.27.4-0ubuntu4
  ProcEnviron:
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-5.24-generic
  SourcePackage: nautilus
  Uname: Linux 2.6.31-5-generic i686

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

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


[Desktop-packages] [Bug 1408107] Re: Can't remove huge files from samba share on first attempt - Input/output error

2015-02-18 Thread Ross Lagerwall
Unfortunately, gvfs can't control the timeouts that libsmbclient uses. I
recommend filing a bug at https://bugzilla.samba.org/ or asking a
question on the mailing list:
https://lists.samba.org/mailman/listinfo/samba

Alternatively, you could try poke about on the router and see what is
happening, e.g. if the server crashes or something.

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

Title:
  Can't remove huge files from samba share on first attempt -
  Input/output error

Status in gvfs package in Ubuntu:
  New

Bug description:
  I'm using Ubuntu 14.04. I'm trying to delete huge (10-20 gigs) files
  from a samba share but it always fails for the first try:

  
username@hostname:/run/user/1000/gvfs/smb-share:server=192.168.1.1,share=download$
 rm -r Testdir/
  rm: cannot remove ‘Testdir/13gigs-Testfile.mkv’: Input/output error
  
username@hostname:/run/user/1000/gvfs/smb-share:server=192.168.1.1,share=download$
 rm -r Testdir/
  
username@hostname:/run/user/1000/gvfs/smb-share:server=192.168.1.1,share=download$
 rm -r Testdir/
  rm: cannot remove ‘Testdir/’: No such file or directory
  
username@hostname:/run/user/1000/gvfs/smb-share:server=192.168.1.1,share=download$
 

  The same thing is happening if I use Nautilus. This is bugging me a lot 
because I'm always having a hard time deleting stuff.
  My quess is that the deletion process times out too early so it doesn't have 
enough time to delete such big files.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gvfs 1.20.1-1ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
  Uname: Linux 3.13.0-43-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jan  6 22:22:30 2015
  InstallationDate: Installed on 2013-10-30 (433 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: gvfs
  UpgradeStatus: Upgraded to trusty on 2014-05-04 (247 days ago)

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

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


[Desktop-packages] [Bug 1408107] Re: Can't remove huge files from samba share on first attempt - Input/output error

2015-02-17 Thread Ross Lagerwall
I don't think this is a gvfs issue, the timeout is coming from
libsmbclient which gvfs uses to communicate with the server. Deleting a
file should be quick though so timing out is strange.

How long does it take to timeout? Maybe there's something strange
happening like the server crashing which causes the connection to
timeout?

This is the interesting bit from the logs, where two stat() calls in a
row give different results:

smbc_stat(smb://192.168.1.1/download/test123/test123.1080p.mkv)
SMBC_getatr: sending qpathinfo
num_setup=1, max_setup=0, param_total=60, this_param=60, max_param=2, 
data_total=0, this_data=0, max_data=65535, param_offset=68, param_pad=0, 
param_disp=0, data_offset=128, data_pad=0, data_disp=0
send_reply(0x8a18d0), failed=0 ()

smbc_stat(smb://192.168.1.1/download/test123/test123.1080p.mkv)
SMBC_getatr: sending qpathinfo
num_setup=1, max_setup=0, param_total=60, this_param=60, max_param=2, 
data_total=0, this_data=0, max_data=65535, param_offset=68, param_pad=0, 
param_disp=0, data_offset=128, data_pad=0, data_disp=0
map_errno_from_nt_status: 32 bit codes: code=c0b5
smbc errno NT_STATUS_IO_TIMEOUT -> 110
send_reply(0x8b3940), failed=1 (Időtúllépés a kapcsolatban)

smbc_stat(smb://192.168.1.1/download/test123)
SMBC_getatr: sending qpathinfo
num_setup=1, max_setup=0, param_total=24, this_param=24, max_param=2, 
data_total=0, this_data=0, max_data=65535, param_offset=68, param_pad=0, 
param_disp=0, data_offset=92, data_pad=0, data_disp=0
map_errno_from_nt_status: 32 bit codes: code=c0b5
smbc errno NT_STATUS_IO_TIMEOUT -> 110
send_reply(0x7f5c38002c00), failed=1 (Időtúllépés a kapcsolatban)

Are you using a Windows server or some kind of Samba server?

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

Title:
  Can't remove huge files from samba share on first attempt -
  Input/output error

Status in gvfs package in Ubuntu:
  New

Bug description:
  I'm using Ubuntu 14.04. I'm trying to delete huge (10-20 gigs) files
  from a samba share but it always fails for the first try:

  
username@hostname:/run/user/1000/gvfs/smb-share:server=192.168.1.1,share=download$
 rm -r Testdir/
  rm: cannot remove ‘Testdir/13gigs-Testfile.mkv’: Input/output error
  
username@hostname:/run/user/1000/gvfs/smb-share:server=192.168.1.1,share=download$
 rm -r Testdir/
  
username@hostname:/run/user/1000/gvfs/smb-share:server=192.168.1.1,share=download$
 rm -r Testdir/
  rm: cannot remove ‘Testdir/’: No such file or directory
  
username@hostname:/run/user/1000/gvfs/smb-share:server=192.168.1.1,share=download$
 

  The same thing is happening if I use Nautilus. This is bugging me a lot 
because I'm always having a hard time deleting stuff.
  My quess is that the deletion process times out too early so it doesn't have 
enough time to delete such big files.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gvfs 1.20.1-1ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
  Uname: Linux 3.13.0-43-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jan  6 22:22:30 2015
  InstallationDate: Installed on 2013-10-30 (433 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: gvfs
  UpgradeStatus: Upgraded to trusty on 2014-05-04 (247 days ago)

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

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


[Desktop-packages] [Bug 1403149] Re: Unable to mount OSX Yosemite causing excessive (~25%) CPU usage and moderate desktop sluggishness

2015-02-01 Thread Ross Lagerwall
Nah, neither of them have the required patches (which made only made it
into 1.20.3). It's an idle timeout issue, so it depends one the activity
on the share.

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

Title:
  Unable to mount OSX Yosemite causing excessive (~25%) CPU usage and
  moderate desktop sluggishness

Status in GVFS:
  Fix Released
Status in gvfs package in Ubuntu:
  Fix Committed

Bug description:
  1) lsb_release -rd
  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04

  2) apt-cache policy gvfs
  gvfs:
    Installed: 1.20.1-1ubuntu1
    Candidate: 1.20.1-1ubuntu1
    Version table:
   *** 1.20.1-1ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

  3) What is expected to happen is when one mounts a shared folder from
  OSX Yosemite, the connection is unmountable, and doesn't cause
  excessive (~25%) CPU usage.

  4) What happens instead is the mount is unmountable, and is consuming
  (~25%) CPU as per the attached screenshot. This causes moderate
  desktop sluggishness. Tried restarting OSX, no change.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gvfs 1.20.1-1ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-28.37~14.04.1-generic 3.16.7-ckt1
  Uname: Linux 3.16.0-28-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Dec 16 11:28:39 2014
  InstallationDate: Installed on 2014-06-21 (177 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: gvfs
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1416891] Re: Update to 1.20.3

2015-02-01 Thread Ross Lagerwall
Thanks for this.

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

Title:
  Update to 1.20.3

Status in gvfs package in Ubuntu:
  Fix Released
Status in gvfs source package in Trusty:
  Confirmed

Bug description:
  [Impact]
  Ubuntu 14.04 LTS currently contains 1.20.1. There have been stable updates 
since then. The maintainer has requested we update [1].

  [Test Case]
  Update to 1.20.3. Still should keep working as before.

  [Regression Potential]
  Some risk of other bugs being created by changes. Code inspection shows 
changes are relatively simple.

  [1] https://lists.ubuntu.com/archives/ubuntu-
  devel/2015-February/038668.html

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

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


[Desktop-packages] [Bug 410288] Re: Nautilus does not handle FTP timeouts well

2015-02-01 Thread Ross Lagerwall
It would be good to get these commits from gvfs 1.20.3 to fix this:
https://git.gnome.org/browse/gvfs/commit/?id=562906889bde44f4ef9e7a34343f7c9339941ecb
https://git.gnome.org/browse/gvfs/commit/?id=8c58ceb7d5f07fd007e21dae1557f35be92a56b6
https://git.gnome.org/browse/gvfs/commit/?id=7b1d51379bd1b28de9426aebc0832bc959760cf6

(or just update to 1.20.3 :-) )

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

Title:
  Nautilus does not handle FTP timeouts well

Status in GVFS:
  Fix Released
Status in Nautilus:
  New
Status in gvfs package in Ubuntu:
  Fix Committed

Bug description:
  Binary package hint: gvfs

  I connected to a FTP server via gvfs in Nautilus. After some time the
  FTP connection is closed automatically, as I observed with wireshark
  (421 No transfer timeout (300 seconds): closing control connection).

  After that, everytime I open a folder on the FTP server I get only an
  "unexpected end of stream" error. To access the FTP server again I
  have to disconnect and then connect again. Nautilus does not seem to
  know that the connection closed.

  A better behaviour IMHO would be to try and reconnect to the FTP
  server.

  ProblemType: Bug
  Architecture: i386
  Date: Fri Aug  7 15:16:05 2009
  DistroRelease: Ubuntu 9.10
  ExecutablePath: /usr/bin/nautilus
  LiveMediaBuild: Ubuntu 9.10 "Karmic Koala" - Alpha i386 (20090722.2)
  Package: nautilus 1:2.27.4-0ubuntu4
  ProcEnviron:
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-5.24-generic
  SourcePackage: nautilus
  Uname: Linux 2.6.31-5-generic i686

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

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


[Desktop-packages] [Bug 1403149] Re: Unable to mount OSX Yosemite causing excessive (~25%) CPU usage and moderate desktop sluggishness

2015-02-01 Thread Ross Lagerwall
Oh, yeah somehow I messed up the commit id but you got the right one.

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

Title:
  Unable to mount OSX Yosemite causing excessive (~25%) CPU usage and
  moderate desktop sluggishness

Status in GVFS:
  Fix Released
Status in gvfs package in Ubuntu:
  Fix Released

Bug description:
  1) lsb_release -rd
  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04

  2) apt-cache policy gvfs
  gvfs:
    Installed: 1.20.1-1ubuntu1
    Candidate: 1.20.1-1ubuntu1
    Version table:
   *** 1.20.1-1ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

  3) What is expected to happen is when one mounts a shared folder from
  OSX Yosemite, the connection is unmountable, and doesn't cause
  excessive (~25%) CPU usage.

  4) What happens instead is the mount is unmountable, and is consuming
  (~25%) CPU as per the attached screenshot. This causes moderate
  desktop sluggishness. Tried restarting OSX, no change.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gvfs 1.20.1-1ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-28.37~14.04.1-generic 3.16.7-ckt1
  Uname: Linux 3.16.0-28-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Dec 16 11:28:39 2014
  InstallationDate: Installed on 2014-06-21 (177 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: gvfs
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1408107] Re: Can't remove huge files from samba share on first attempt - Input/output error

2015-02-01 Thread Ross Lagerwall
Please run the following in a terminal:
pkill gvfs; GVFS_DEBUG=all GVFS_SMB_DEBUG=10 `find /usr/lib* -name 'gvfsd'` &> 
~/log.txt

Then mount the smb share, reproduce the problem, and then upload log.txt
in your home directory so we can see a log of what is happening.

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

Title:
  Can't remove huge files from samba share on first attempt -
  Input/output error

Status in gvfs package in Ubuntu:
  New

Bug description:
  I'm using Ubuntu 14.04. I'm trying to delete huge (10-20 gigs) files
  from a samba share but it always fails for the first try:

  
username@hostname:/run/user/1000/gvfs/smb-share:server=192.168.1.1,share=download$
 rm -r Testdir/
  rm: cannot remove ‘Testdir/13gigs-Testfile.mkv’: Input/output error
  
username@hostname:/run/user/1000/gvfs/smb-share:server=192.168.1.1,share=download$
 rm -r Testdir/
  
username@hostname:/run/user/1000/gvfs/smb-share:server=192.168.1.1,share=download$
 rm -r Testdir/
  rm: cannot remove ‘Testdir/’: No such file or directory
  
username@hostname:/run/user/1000/gvfs/smb-share:server=192.168.1.1,share=download$
 

  The same thing is happening if I use Nautilus. This is bugging me a lot 
because I'm always having a hard time deleting stuff.
  My quess is that the deletion process times out too early so it doesn't have 
enough time to delete such big files.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gvfs 1.20.1-1ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
  Uname: Linux 3.13.0-43-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jan  6 22:22:30 2015
  InstallationDate: Installed on 2013-10-30 (433 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: gvfs
  UpgradeStatus: Upgraded to trusty on 2014-05-04 (247 days ago)

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

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


[Desktop-packages] [Bug 1403149] Re: Unable to mount OSX Yosemite causing excessive (~25%) CPU usage and moderate desktop sluggishness

2015-02-01 Thread Ross Lagerwall
The Ubuntu gvfs maintainers should cherry-pick
e9c320e49cace543450b961af32ea7ffeb8d512f and
2e3eee275a97abf4d6055c06683f04c7d8f3f7ca from upstream.

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

Title:
  Unable to mount OSX Yosemite causing excessive (~25%) CPU usage and
  moderate desktop sluggishness

Status in gvfs package in Ubuntu:
  New

Bug description:
  1) lsb_release -rd
  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04

  2) apt-cache policy gvfs
  gvfs:
Installed: 1.20.1-1ubuntu1
Candidate: 1.20.1-1ubuntu1
Version table:
   *** 1.20.1-1ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

  3) What is expected to happen is when one mounts a samba shared folder
  from OSX Yosemite, the connection is unmountable, and doesn't cause
  excessive (~25%) CPU usage.

  4) What happens instead is the mount is unmountable, and is consuming
  (~25%) CPU as per the attached screenshot. This causes moderate
  desktop sluggishness. Tried restarting OSX, no change.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gvfs 1.20.1-1ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-28.37~14.04.1-generic 3.16.7-ckt1
  Uname: Linux 3.16.0-28-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Dec 16 11:28:39 2014
  InstallationDate: Installed on 2014-06-21 (177 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: gvfs
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1403149] Re: Unable to mount OSX Yosemite causing excessive (~25%) CPU usage and moderate desktop sluggishness

2015-02-01 Thread Ross Lagerwall
Oh, btw it's an afp not smb share you're using.

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

Title:
  Unable to mount OSX Yosemite causing excessive (~25%) CPU usage and
  moderate desktop sluggishness

Status in gvfs package in Ubuntu:
  New

Bug description:
  1) lsb_release -rd
  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04

  2) apt-cache policy gvfs
  gvfs:
Installed: 1.20.1-1ubuntu1
Candidate: 1.20.1-1ubuntu1
Version table:
   *** 1.20.1-1ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

  3) What is expected to happen is when one mounts a samba shared folder
  from OSX Yosemite, the connection is unmountable, and doesn't cause
  excessive (~25%) CPU usage.

  4) What happens instead is the mount is unmountable, and is consuming
  (~25%) CPU as per the attached screenshot. This causes moderate
  desktop sluggishness. Tried restarting OSX, no change.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gvfs 1.20.1-1ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-28.37~14.04.1-generic 3.16.7-ckt1
  Uname: Linux 3.16.0-28-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Dec 16 11:28:39 2014
  InstallationDate: Installed on 2014-06-21 (177 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: gvfs
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 227808] Re: file permissions destroyed by vim/gvfs/fuse

2014-07-04 Thread Ross Lagerwall
This is fixed upstream in gvfs 1.21.1.

Interesting to note that despite all the comments, no one bothered to
file a bug upstream.

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

Title:
  file permissions destroyed by vim/gvfs/fuse

Status in GVFS:
  New
Status in “gvfs” package in Ubuntu:
  Confirmed

Bug description:
  This bug is a little difficult to explain, but I will do my best. I'm
  using Ubuntu Hardy Heron with no third party repositories. Every
  package is up to date as of this posting.

  It goes like this. When I edit files with vim or gvim through
  gvfs/fuse/sftp the file permissions on the real remote file system get
  destroyed. Here is a procedure you can follow to duplicate this bug.
  The only non-default package you need installed is vim or gvim.

  1 - Open a terminal and ssh to a remote machine.
  2 - In this terminal create a text file on the remote machine, and set the 
permissions to 644. 
  3 - Go to the Places->Connect to Server... menu item, and create an SSH 
connection to the remote machine.
  4 - Double click the new sftp folder icon that appears on the desktop to open 
nautilus.
  5 - In nautilus browse to the directory containing the text file you just 
created.
  6 - Use the command ls -l in the ssh terminal to verify the permissions of 
the file are still 644.
  7 - In nautilus right-click on the text file, open it with "Text Editor" 
(gedit)
  8 - Make a change to the file in gedit and save it.
  9 - Use the ls -l command in the terminal to verify that the permissions of 
the file are still 644.
  10 - Exit gedit.
  11 - In nautilus right-click on the text file and select the option to open 
it with "GVim Text Editor"
  12 - Make some changes to the file in GVim, and save those changes.
  13 - Use the ls -l command in the terminal, and you will see that the 
permissions of the file are now 600, not 644.

  Some interesting things to note about this bug.

  If you open the text editors from the command line, instead of through
  nautilus, the same problem happens.

  So opening gedit like this:
  gedit ~/.gvfs/sftp\ on\ remote/home/user/test.txt
  will not damage the permissions.

  However, opening vim like this:
  vim ~/.gvfs/sftp\ on\ remote/home/user/test.txt
  will damage the permissions.

  Also, I notice that if you do this
  ls -l ~/.gfvs/sftp\ on\ remote/home/user/
  the permissions of test.txt (and every other file) will appear to be 600 (700 
for directories), regardless of the file permissions on the "real" remote file 
system. If you attempt to chmod any files, it will result in a chmod of the 
actual permissions on the remote file system, but it will not change the 
permissions of the file in the local ~/.gvfs directory. 

  This has led me to conclude that this bug is a combination of two
  things. First, using the chmod command on files through gvfs/fuse/sftp
  does not work in an expected fashion. Secondly, gvim and vim appear to
  be chmod-ing files when they write to those files.

  I'm not sure this bug is an actual security risk. It seems it can only
  result in file permissions becoming more strict, not more permissive.
  However, I have checked the security box just to be safe. If file
  permissions involved, there could always be an unseen security issue.
  I can see a situation where an application losing the ability to read
  a needed file causes system breakage, if not a security hole.

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

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


[Desktop-packages] [Bug 1184720] Re: Nautilus does not properly navigate symbolic links

2014-06-17 Thread Ross Lagerwall
Any update on this? I don't see any pending fixes in proposed anymore.

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

Title:
  Nautilus does not properly navigate symbolic links

Status in Nautilus:
  Fix Released
Status in “nautilus” package in Ubuntu:
  Fix Released
Status in “nautilus” source package in Trusty:
  In Progress

Bug description:
  Impact:
  Navigating symlinks in nautilus leads to incorrect directories

  Test case:
  1. Create a directory in Home called Folder
  2. Right click on Folder in Nautilus and select 'make link'
  3. Drag created link to Desktop
  4. Double-click on Link to Folder to open it in Nautilus

  Clicking the back arrow in Nautilus behaves as it should--it takes you
  back to Desktop, not the parent folder of the target of the link.

  However, the architecture displayed near the top of the Nautilus
  window shows the parent directory of the target, not of the link
  (i.e., it shows [Home][Folder], not [Home][Desktop][Link to Folder]

  Pressing alt+up also takes you to the parent of the target, not the
  link.

  Regression potential:
  check that creating symlinks and navigating those works correctly

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

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


[Desktop-packages] [Bug 1152165]

2013-08-20 Thread Ross Lagerwall
(In reply to comment #22)
> (In reply to comment #20)
> > Hopefully https://patchwork.kernel.org/patch/2841344/ is the right fix.
> 
> Can you please test the above patch?

Unfortunately, as I said in comment #17, I don't have access to the IVB
hardware anymore so I can't test the patch.

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

Title:
  [ivb] GPU lockup  IPEHR: 0x upon context restore

Status in X.org xf86-video-intel:
  Invalid
Status in “xserver-xorg-video-intel” package in Ubuntu:
  Confirmed

Bug description:
  Had SuperTuxKart open and Chromium running in the background; then
  computer locked up.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: xserver-xorg-video-intel 2:2.21.3-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-11.20-generic 3.8.2
  Uname: Linux 3.8.0-11-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.9-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Thu Mar  7 08:09:00 2013
  DistUpgraded: Fresh install
  DistroCodename: raring
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 4.1.22, 3.8.0-11-generic, x86_64: installed
   virtualbox, 4.1.22, 3.8.0-4-generic, x86_64: installed
   virtualbox, 4.1.22, 3.8.0-6-generic, x86_64: installed
   virtualbox, 4.1.22, 3.8.0-7-generic, x86_64: installed
   virtualbox, 4.1.22, 3.8.0-8-generic, x86_64: installed
  DuplicateSignature: GPU lockup  IPEHR: 0x IPEHR: 0x0b140001 Ubuntu 
13.04
  ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: This is the first time
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Apple Inc. Device [106b:00fd]
  InstallationDate: Installed on 2013-01-18 (48 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64+mac (20130117)
  InterpreterPath: /usr/bin/python3.3
  MachineType: Apple Inc. MacBookAir5,1
  MarkForUpload: True
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gpu-error-intel.py
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-11-generic 
root=UUID=ceb00db8-a161-4759-80d9-a9fce83fe29f ro i915.i915_enable_rc6=1
  RelatedPackageVersions:
   xserver-xorg 1:7.7+1ubuntu4
   libdrm2  2.4.42-0ubuntu1
   xserver-xorg-video-intel 2:2.21.3-0ubuntu1
  SourcePackage: xserver-xorg-video-intel
  Title: GPU lockup  IPEHR: 0x IPEHR: 0x0b140001
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 11/27/2012
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBA51.88Z.00EF.B02.1211271028
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-66F35F19FE2A0D05
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookAir5,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-66F35F19FE2A0D05
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBA51.88Z.00EF.B02.1211271028:bd11/27/2012:svnAppleInc.:pnMacBookAir5,1:pvr1.0:rvnAppleInc.:rnMac-66F35F19FE2A0D05:rvrMacBookAir5,1:cvnAppleInc.:ct10:cvrMac-66F35F19FE2A0D05:
  dmi.product.name: MacBookAir5,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  version.compiz: compiz 1:0.9.9~daily13.03.06-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.42-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.2-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.2-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.3-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.6-0ubuntu3
  xserver.bootTime: Wed Mar  6 11:28:46 2013
  xserver.configfile: default
  xserver.errors:
   intel(0): Detected a hung GPU, disabling acceleration.
   intel(0): When reporting this, please include i915_error_state from debugfs 
and the full dmesg.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.13.2-0ubuntu2
  xserver.video_driver: intel

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

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


[Desktop-packages] [Bug 1152165]

2013-07-01 Thread Ross Lagerwall
I can confirm that I did see strange white corruption when playing the
game, but I thought it was unrelated or an application error.

Unfortunately, I don't have access to the hardware anymore so I cannot
further test anything.  However, given that the hangs happened on two
different OSes, with the latest kernel versions, it should be easy
enough to reproduce.

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

Title:
  [ivb] GPU lockup  IPEHR: 0x upon context restore

Status in X.org xf86-video-intel:
  Confirmed
Status in “xserver-xorg-video-intel” package in Ubuntu:
  Confirmed

Bug description:
  Had SuperTuxKart open and Chromium running in the background; then
  computer locked up.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: xserver-xorg-video-intel 2:2.21.3-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-11.20-generic 3.8.2
  Uname: Linux 3.8.0-11-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.9-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Thu Mar  7 08:09:00 2013
  DistUpgraded: Fresh install
  DistroCodename: raring
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 4.1.22, 3.8.0-11-generic, x86_64: installed
   virtualbox, 4.1.22, 3.8.0-4-generic, x86_64: installed
   virtualbox, 4.1.22, 3.8.0-6-generic, x86_64: installed
   virtualbox, 4.1.22, 3.8.0-7-generic, x86_64: installed
   virtualbox, 4.1.22, 3.8.0-8-generic, x86_64: installed
  DuplicateSignature: GPU lockup  IPEHR: 0x IPEHR: 0x0b140001 Ubuntu 
13.04
  ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: This is the first time
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Apple Inc. Device [106b:00fd]
  InstallationDate: Installed on 2013-01-18 (48 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64+mac (20130117)
  InterpreterPath: /usr/bin/python3.3
  MachineType: Apple Inc. MacBookAir5,1
  MarkForUpload: True
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gpu-error-intel.py
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-11-generic 
root=UUID=ceb00db8-a161-4759-80d9-a9fce83fe29f ro i915.i915_enable_rc6=1
  RelatedPackageVersions:
   xserver-xorg 1:7.7+1ubuntu4
   libdrm2  2.4.42-0ubuntu1
   xserver-xorg-video-intel 2:2.21.3-0ubuntu1
  SourcePackage: xserver-xorg-video-intel
  Title: GPU lockup  IPEHR: 0x IPEHR: 0x0b140001
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 11/27/2012
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBA51.88Z.00EF.B02.1211271028
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-66F35F19FE2A0D05
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookAir5,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-66F35F19FE2A0D05
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBA51.88Z.00EF.B02.1211271028:bd11/27/2012:svnAppleInc.:pnMacBookAir5,1:pvr1.0:rvnAppleInc.:rnMac-66F35F19FE2A0D05:rvrMacBookAir5,1:cvnAppleInc.:ct10:cvrMac-66F35F19FE2A0D05:
  dmi.product.name: MacBookAir5,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  version.compiz: compiz 1:0.9.9~daily13.03.06-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.42-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.2-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.2-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.3-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.6-0ubuntu3
  xserver.bootTime: Wed Mar  6 11:28:46 2013
  xserver.configfile: default
  xserver.errors:
   intel(0): Detected a hung GPU, disabling acceleration.
   intel(0): When reporting this, please include i915_error_state from debugfs 
and the full dmesg.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.13.2-0ubuntu2
  xserver.video_driver: intel

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

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

[Desktop-packages] [Bug 1152165]

2013-07-01 Thread Ross Lagerwall
On Wed, Jun 26, 2013 at 11:04:43PM +, bugzilla-dae...@freedesktop.org wrote:
> https://bugs.freedesktop.org/show_bug.cgi?id=64073
> 
> --- Comment #18 from Ben Widawsky  ---
> If someone can reproduce this, can they read back register 0x20f4?
> 

Would that not be in the error state dump I attached?

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

Title:
  [ivb] GPU lockup  IPEHR: 0x upon context restore

Status in X.org xf86-video-intel:
  Confirmed
Status in “xserver-xorg-video-intel” package in Ubuntu:
  Confirmed

Bug description:
  Had SuperTuxKart open and Chromium running in the background; then
  computer locked up.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: xserver-xorg-video-intel 2:2.21.3-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-11.20-generic 3.8.2
  Uname: Linux 3.8.0-11-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.9-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Thu Mar  7 08:09:00 2013
  DistUpgraded: Fresh install
  DistroCodename: raring
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 4.1.22, 3.8.0-11-generic, x86_64: installed
   virtualbox, 4.1.22, 3.8.0-4-generic, x86_64: installed
   virtualbox, 4.1.22, 3.8.0-6-generic, x86_64: installed
   virtualbox, 4.1.22, 3.8.0-7-generic, x86_64: installed
   virtualbox, 4.1.22, 3.8.0-8-generic, x86_64: installed
  DuplicateSignature: GPU lockup  IPEHR: 0x IPEHR: 0x0b140001 Ubuntu 
13.04
  ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: This is the first time
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Apple Inc. Device [106b:00fd]
  InstallationDate: Installed on 2013-01-18 (48 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64+mac (20130117)
  InterpreterPath: /usr/bin/python3.3
  MachineType: Apple Inc. MacBookAir5,1
  MarkForUpload: True
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gpu-error-intel.py
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-11-generic 
root=UUID=ceb00db8-a161-4759-80d9-a9fce83fe29f ro i915.i915_enable_rc6=1
  RelatedPackageVersions:
   xserver-xorg 1:7.7+1ubuntu4
   libdrm2  2.4.42-0ubuntu1
   xserver-xorg-video-intel 2:2.21.3-0ubuntu1
  SourcePackage: xserver-xorg-video-intel
  Title: GPU lockup  IPEHR: 0x IPEHR: 0x0b140001
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 11/27/2012
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBA51.88Z.00EF.B02.1211271028
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-66F35F19FE2A0D05
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookAir5,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-66F35F19FE2A0D05
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBA51.88Z.00EF.B02.1211271028:bd11/27/2012:svnAppleInc.:pnMacBookAir5,1:pvr1.0:rvnAppleInc.:rnMac-66F35F19FE2A0D05:rvrMacBookAir5,1:cvnAppleInc.:ct10:cvrMac-66F35F19FE2A0D05:
  dmi.product.name: MacBookAir5,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  version.compiz: compiz 1:0.9.9~daily13.03.06-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.42-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.2-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.2-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.3-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.6-0ubuntu3
  xserver.bootTime: Wed Mar  6 11:28:46 2013
  xserver.configfile: default
  xserver.errors:
   intel(0): Detected a hung GPU, disabling acceleration.
   intel(0): When reporting this, please include i915_error_state from debugfs 
and the full dmesg.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.13.2-0ubuntu2
  xserver.video_driver: intel

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

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


[Desktop-packages] [Bug 1152165]

2013-05-25 Thread Ross Lagerwall
Created attachment 79626
i915 error state from v3.10-rc2

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

Title:
  [ivb] GPU lockup  IPEHR: 0x upon context restore

Status in X.org xf86-video-intel:
  Confirmed
Status in “xserver-xorg-video-intel” package in Ubuntu:
  Confirmed

Bug description:
  Had SuperTuxKart open and Chromium running in the background; then
  computer locked up.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: xserver-xorg-video-intel 2:2.21.3-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-11.20-generic 3.8.2
  Uname: Linux 3.8.0-11-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.9-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Thu Mar  7 08:09:00 2013
  DistUpgraded: Fresh install
  DistroCodename: raring
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 4.1.22, 3.8.0-11-generic, x86_64: installed
   virtualbox, 4.1.22, 3.8.0-4-generic, x86_64: installed
   virtualbox, 4.1.22, 3.8.0-6-generic, x86_64: installed
   virtualbox, 4.1.22, 3.8.0-7-generic, x86_64: installed
   virtualbox, 4.1.22, 3.8.0-8-generic, x86_64: installed
  DuplicateSignature: GPU lockup  IPEHR: 0x IPEHR: 0x0b140001 Ubuntu 
13.04
  ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: This is the first time
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Apple Inc. Device [106b:00fd]
  InstallationDate: Installed on 2013-01-18 (48 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64+mac (20130117)
  InterpreterPath: /usr/bin/python3.3
  MachineType: Apple Inc. MacBookAir5,1
  MarkForUpload: True
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gpu-error-intel.py
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-11-generic 
root=UUID=ceb00db8-a161-4759-80d9-a9fce83fe29f ro i915.i915_enable_rc6=1
  RelatedPackageVersions:
   xserver-xorg 1:7.7+1ubuntu4
   libdrm2  2.4.42-0ubuntu1
   xserver-xorg-video-intel 2:2.21.3-0ubuntu1
  SourcePackage: xserver-xorg-video-intel
  Title: GPU lockup  IPEHR: 0x IPEHR: 0x0b140001
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 11/27/2012
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBA51.88Z.00EF.B02.1211271028
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-66F35F19FE2A0D05
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookAir5,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-66F35F19FE2A0D05
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBA51.88Z.00EF.B02.1211271028:bd11/27/2012:svnAppleInc.:pnMacBookAir5,1:pvr1.0:rvnAppleInc.:rnMac-66F35F19FE2A0D05:rvrMacBookAir5,1:cvnAppleInc.:ct10:cvrMac-66F35F19FE2A0D05:
  dmi.product.name: MacBookAir5,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  version.compiz: compiz 1:0.9.9~daily13.03.06-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.42-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.2-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.2-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.3-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.6-0ubuntu3
  xserver.bootTime: Wed Mar  6 11:28:46 2013
  xserver.configfile: default
  xserver.errors:
   intel(0): Detected a hung GPU, disabling acceleration.
   intel(0): When reporting this, please include i915_error_state from debugfs 
and the full dmesg.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.13.2-0ubuntu2
  xserver.video_driver: intel

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

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


[Desktop-packages] [Bug 1152165]

2013-05-25 Thread Ross Lagerwall
Created attachment 79627
System log from v3.10-rc2

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

Title:
  [ivb] GPU lockup  IPEHR: 0x upon context restore

Status in X.org xf86-video-intel:
  Confirmed
Status in “xserver-xorg-video-intel” package in Ubuntu:
  Confirmed

Bug description:
  Had SuperTuxKart open and Chromium running in the background; then
  computer locked up.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: xserver-xorg-video-intel 2:2.21.3-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-11.20-generic 3.8.2
  Uname: Linux 3.8.0-11-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.9-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Thu Mar  7 08:09:00 2013
  DistUpgraded: Fresh install
  DistroCodename: raring
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 4.1.22, 3.8.0-11-generic, x86_64: installed
   virtualbox, 4.1.22, 3.8.0-4-generic, x86_64: installed
   virtualbox, 4.1.22, 3.8.0-6-generic, x86_64: installed
   virtualbox, 4.1.22, 3.8.0-7-generic, x86_64: installed
   virtualbox, 4.1.22, 3.8.0-8-generic, x86_64: installed
  DuplicateSignature: GPU lockup  IPEHR: 0x IPEHR: 0x0b140001 Ubuntu 
13.04
  ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: This is the first time
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Apple Inc. Device [106b:00fd]
  InstallationDate: Installed on 2013-01-18 (48 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64+mac (20130117)
  InterpreterPath: /usr/bin/python3.3
  MachineType: Apple Inc. MacBookAir5,1
  MarkForUpload: True
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gpu-error-intel.py
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-11-generic 
root=UUID=ceb00db8-a161-4759-80d9-a9fce83fe29f ro i915.i915_enable_rc6=1
  RelatedPackageVersions:
   xserver-xorg 1:7.7+1ubuntu4
   libdrm2  2.4.42-0ubuntu1
   xserver-xorg-video-intel 2:2.21.3-0ubuntu1
  SourcePackage: xserver-xorg-video-intel
  Title: GPU lockup  IPEHR: 0x IPEHR: 0x0b140001
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 11/27/2012
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBA51.88Z.00EF.B02.1211271028
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-66F35F19FE2A0D05
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookAir5,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-66F35F19FE2A0D05
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBA51.88Z.00EF.B02.1211271028:bd11/27/2012:svnAppleInc.:pnMacBookAir5,1:pvr1.0:rvnAppleInc.:rnMac-66F35F19FE2A0D05:rvrMacBookAir5,1:cvnAppleInc.:ct10:cvrMac-66F35F19FE2A0D05:
  dmi.product.name: MacBookAir5,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  version.compiz: compiz 1:0.9.9~daily13.03.06-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.42-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.2-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.2-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.3-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.6-0ubuntu3
  xserver.bootTime: Wed Mar  6 11:28:46 2013
  xserver.configfile: default
  xserver.errors:
   intel(0): Detected a hung GPU, disabling acceleration.
   intel(0): When reporting this, please include i915_error_state from debugfs 
and the full dmesg.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.13.2-0ubuntu2
  xserver.video_driver: intel

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

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


[Desktop-packages] [Bug 1152165]

2013-05-25 Thread Ross Lagerwall
On the same machine, I tried running SuperTuxKart on Arch Linux with
Linux kernel 3.10-rc2, mesa 9.1.2 and Intel drivers 2.21.6.

I seemed to get the same hang, even though 3.10-rc2 contains the above-
mentioned commit. I will attach the error state and relevant dmesg log.

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

Title:
  [ivb] GPU lockup  IPEHR: 0x upon context restore

Status in X.org xf86-video-intel:
  Confirmed
Status in “xserver-xorg-video-intel” package in Ubuntu:
  Confirmed

Bug description:
  Had SuperTuxKart open and Chromium running in the background; then
  computer locked up.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: xserver-xorg-video-intel 2:2.21.3-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-11.20-generic 3.8.2
  Uname: Linux 3.8.0-11-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.9-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Thu Mar  7 08:09:00 2013
  DistUpgraded: Fresh install
  DistroCodename: raring
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 4.1.22, 3.8.0-11-generic, x86_64: installed
   virtualbox, 4.1.22, 3.8.0-4-generic, x86_64: installed
   virtualbox, 4.1.22, 3.8.0-6-generic, x86_64: installed
   virtualbox, 4.1.22, 3.8.0-7-generic, x86_64: installed
   virtualbox, 4.1.22, 3.8.0-8-generic, x86_64: installed
  DuplicateSignature: GPU lockup  IPEHR: 0x IPEHR: 0x0b140001 Ubuntu 
13.04
  ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: This is the first time
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Apple Inc. Device [106b:00fd]
  InstallationDate: Installed on 2013-01-18 (48 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64+mac (20130117)
  InterpreterPath: /usr/bin/python3.3
  MachineType: Apple Inc. MacBookAir5,1
  MarkForUpload: True
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gpu-error-intel.py
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-11-generic 
root=UUID=ceb00db8-a161-4759-80d9-a9fce83fe29f ro i915.i915_enable_rc6=1
  RelatedPackageVersions:
   xserver-xorg 1:7.7+1ubuntu4
   libdrm2  2.4.42-0ubuntu1
   xserver-xorg-video-intel 2:2.21.3-0ubuntu1
  SourcePackage: xserver-xorg-video-intel
  Title: GPU lockup  IPEHR: 0x IPEHR: 0x0b140001
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 11/27/2012
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBA51.88Z.00EF.B02.1211271028
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-66F35F19FE2A0D05
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookAir5,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-66F35F19FE2A0D05
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBA51.88Z.00EF.B02.1211271028:bd11/27/2012:svnAppleInc.:pnMacBookAir5,1:pvr1.0:rvnAppleInc.:rnMac-66F35F19FE2A0D05:rvrMacBookAir5,1:cvnAppleInc.:ct10:cvrMac-66F35F19FE2A0D05:
  dmi.product.name: MacBookAir5,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  version.compiz: compiz 1:0.9.9~daily13.03.06-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.42-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.2-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.2-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.3-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.6-0ubuntu3
  xserver.bootTime: Wed Mar  6 11:28:46 2013
  xserver.configfile: default
  xserver.errors:
   intel(0): Detected a hung GPU, disabling acceleration.
   intel(0): When reporting this, please include i915_error_state from debugfs 
and the full dmesg.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.13.2-0ubuntu2
  xserver.video_driver: intel

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

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


[Desktop-packages] [Bug 1152165]

2013-05-07 Thread Ross Lagerwall
(In reply to comment #9)
> Can you please check whether cherry-picking the referenced patch to a stable
> kernel fixes the issues, too?

Yes, applying it on top of the Ubuntu 3.8 kernel worked fine.

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

Title:
  [ivb] GPU lockup  IPEHR: 0x upon context restore

Status in X.org xf86-video-intel:
  Fix Released
Status in “xserver-xorg-video-intel” package in Ubuntu:
  Confirmed

Bug description:
  Had SuperTuxKart open and Chromium running in the background; then
  computer locked up.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: xserver-xorg-video-intel 2:2.21.3-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-11.20-generic 3.8.2
  Uname: Linux 3.8.0-11-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.9-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Thu Mar  7 08:09:00 2013
  DistUpgraded: Fresh install
  DistroCodename: raring
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 4.1.22, 3.8.0-11-generic, x86_64: installed
   virtualbox, 4.1.22, 3.8.0-4-generic, x86_64: installed
   virtualbox, 4.1.22, 3.8.0-6-generic, x86_64: installed
   virtualbox, 4.1.22, 3.8.0-7-generic, x86_64: installed
   virtualbox, 4.1.22, 3.8.0-8-generic, x86_64: installed
  DuplicateSignature: GPU lockup  IPEHR: 0x IPEHR: 0x0b140001 Ubuntu 
13.04
  ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: This is the first time
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Apple Inc. Device [106b:00fd]
  InstallationDate: Installed on 2013-01-18 (48 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64+mac (20130117)
  InterpreterPath: /usr/bin/python3.3
  MachineType: Apple Inc. MacBookAir5,1
  MarkForUpload: True
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gpu-error-intel.py
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-11-generic 
root=UUID=ceb00db8-a161-4759-80d9-a9fce83fe29f ro i915.i915_enable_rc6=1
  RelatedPackageVersions:
   xserver-xorg 1:7.7+1ubuntu4
   libdrm2  2.4.42-0ubuntu1
   xserver-xorg-video-intel 2:2.21.3-0ubuntu1
  SourcePackage: xserver-xorg-video-intel
  Title: GPU lockup  IPEHR: 0x IPEHR: 0x0b140001
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 11/27/2012
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBA51.88Z.00EF.B02.1211271028
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-66F35F19FE2A0D05
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookAir5,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-66F35F19FE2A0D05
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBA51.88Z.00EF.B02.1211271028:bd11/27/2012:svnAppleInc.:pnMacBookAir5,1:pvr1.0:rvnAppleInc.:rnMac-66F35F19FE2A0D05:rvrMacBookAir5,1:cvnAppleInc.:ct10:cvrMac-66F35F19FE2A0D05:
  dmi.product.name: MacBookAir5,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  version.compiz: compiz 1:0.9.9~daily13.03.06-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.42-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.2-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.2-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.3-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.6-0ubuntu3
  xserver.bootTime: Wed Mar  6 11:28:46 2013
  xserver.configfile: default
  xserver.errors:
   intel(0): Detected a hung GPU, disabling acceleration.
   intel(0): When reporting this, please include i915_error_state from debugfs 
and the full dmesg.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.13.2-0ubuntu2
  xserver.video_driver: intel

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

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


[Desktop-packages] [Bug 1152165]

2013-05-03 Thread Ross Lagerwall
(In reply to comment #7)
> This will be interesting to see if
> 
> commit 4615d4c9e27eda42c3e965f208a4b4065841498c
> Author: Chris Wilson 
> Date:   Mon Apr 8 14:28:40 2013 +0100
> 
> drm/i915: Use MLC (l3$) for context objects
> 
> has any impact. Can you please try the current drm-intel-nightly kernel from
> ppa:mainline?

Yes, it seems to work well with the drm-intel-nightly kernel.

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

Title:
  [ivb] GPU lockup  IPEHR: 0x upon context restore

Status in X.org xf86-video-intel:
  Incomplete
Status in “xserver-xorg-video-intel” package in Ubuntu:
  Confirmed

Bug description:
  Had SuperTuxKart open and Chromium running in the background; then
  computer locked up.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: xserver-xorg-video-intel 2:2.21.3-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-11.20-generic 3.8.2
  Uname: Linux 3.8.0-11-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.9-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Thu Mar  7 08:09:00 2013
  DistUpgraded: Fresh install
  DistroCodename: raring
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 4.1.22, 3.8.0-11-generic, x86_64: installed
   virtualbox, 4.1.22, 3.8.0-4-generic, x86_64: installed
   virtualbox, 4.1.22, 3.8.0-6-generic, x86_64: installed
   virtualbox, 4.1.22, 3.8.0-7-generic, x86_64: installed
   virtualbox, 4.1.22, 3.8.0-8-generic, x86_64: installed
  DuplicateSignature: GPU lockup  IPEHR: 0x IPEHR: 0x0b140001 Ubuntu 
13.04
  ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: This is the first time
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Apple Inc. Device [106b:00fd]
  InstallationDate: Installed on 2013-01-18 (48 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64+mac (20130117)
  InterpreterPath: /usr/bin/python3.3
  MachineType: Apple Inc. MacBookAir5,1
  MarkForUpload: True
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gpu-error-intel.py
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-11-generic 
root=UUID=ceb00db8-a161-4759-80d9-a9fce83fe29f ro i915.i915_enable_rc6=1
  RelatedPackageVersions:
   xserver-xorg 1:7.7+1ubuntu4
   libdrm2  2.4.42-0ubuntu1
   xserver-xorg-video-intel 2:2.21.3-0ubuntu1
  SourcePackage: xserver-xorg-video-intel
  Title: GPU lockup  IPEHR: 0x IPEHR: 0x0b140001
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 11/27/2012
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBA51.88Z.00EF.B02.1211271028
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-66F35F19FE2A0D05
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookAir5,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-66F35F19FE2A0D05
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBA51.88Z.00EF.B02.1211271028:bd11/27/2012:svnAppleInc.:pnMacBookAir5,1:pvr1.0:rvnAppleInc.:rnMac-66F35F19FE2A0D05:rvrMacBookAir5,1:cvnAppleInc.:ct10:cvrMac-66F35F19FE2A0D05:
  dmi.product.name: MacBookAir5,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  version.compiz: compiz 1:0.9.9~daily13.03.06-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.42-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.2-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.2-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.3-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.6-0ubuntu3
  xserver.bootTime: Wed Mar  6 11:28:46 2013
  xserver.configfile: default
  xserver.errors:
   intel(0): Detected a hung GPU, disabling acceleration.
   intel(0): When reporting this, please include i915_error_state from debugfs 
and the full dmesg.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.13.2-0ubuntu2
  xserver.video_driver: intel

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

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

[Desktop-packages] [Bug 1137418] [NEW] colord-sane crashed with SIGSEGV in libusb_get_device_list()

2013-03-01 Thread Ross Lagerwall
Public bug reported:

This occurred when running the live daily image for 2013-03-01.

I wasn't doing anything in particular, the "system error has occurred"
message just popped up.

I am running in QEMU with a Linux host.

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: colord 0.1.23-0ubuntu3
ProcVersionSignature: Ubuntu 3.8.0-8.17-generic 3.8.0
Uname: Linux 3.8.0-8-generic x86_64
ApportVersion: 2.8-0ubuntu4
Architecture: amd64
CasperVersion: 1.330
Date: Fri Mar  1 09:27:15 2013
ExecutablePath: /usr/lib/x86_64-linux-gnu/colord/colord-sane
LiveMediaBuild: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130301)
MarkForUpload: True
ProcCmdline: /usr/lib/x86_64-linux-gnu/colord/colord-sane
ProcEnviron:
 
SegvAnalysis:
 Segfault happened at: 0x7f3769ed7d60:  cmpb   $0x0,(%rsi)
 PC (0x7f3769ed7d60) ok
 source "$0x0" ok
 destination "(%rsi)" (0x) not located in a known VMA region (needed 
writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: colord
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 ?? () from /lib/x86_64-linux-gnu/libusb-1.0.so.0
 libusb_get_device_list () from /lib/x86_64-linux-gnu/libusb-1.0.so.0
 ?? () from /usr/lib/libhpmud.so.0
 hpmud_probe_devices () from /usr/lib/libhpmud.so.0
Title: colord-sane crashed with SIGSEGV in libusb_get_device_list()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

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


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

** Information type changed from Private to Public

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

Title:
  colord-sane crashed with SIGSEGV in libusb_get_device_list()

Status in “colord” package in Ubuntu:
  New

Bug description:
  This occurred when running the live daily image for 2013-03-01.

  I wasn't doing anything in particular, the "system error has occurred"
  message just popped up.

  I am running in QEMU with a Linux host.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: colord 0.1.23-0ubuntu3
  ProcVersionSignature: Ubuntu 3.8.0-8.17-generic 3.8.0
  Uname: Linux 3.8.0-8-generic x86_64
  ApportVersion: 2.8-0ubuntu4
  Architecture: amd64
  CasperVersion: 1.330
  Date: Fri Mar  1 09:27:15 2013
  ExecutablePath: /usr/lib/x86_64-linux-gnu/colord/colord-sane
  LiveMediaBuild: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130301)
  MarkForUpload: True
  ProcCmdline: /usr/lib/x86_64-linux-gnu/colord/colord-sane
  ProcEnviron:
   
  SegvAnalysis:
   Segfault happened at: 0x7f3769ed7d60:cmpb   $0x0,(%rsi)
   PC (0x7f3769ed7d60) ok
   source "$0x0" ok
   destination "(%rsi)" (0x) not located in a known VMA region (needed 
writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: colord
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libc.so.6
   ?? () from /lib/x86_64-linux-gnu/libusb-1.0.so.0
   libusb_get_device_list () from /lib/x86_64-linux-gnu/libusb-1.0.so.0
   ?? () from /usr/lib/libhpmud.so.0
   hpmud_probe_devices () from /usr/lib/libhpmud.so.0
  Title: colord-sane crashed with SIGSEGV in libusb_get_device_list()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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