[Desktop-packages] [Bug 1387134] Re: when enabled nvidia graphics card, desktop freezes

2016-01-14 Thread donquixote
For the record: This happens to me a lot with PhpStorm (based on Java).

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

Title:
  when enabled nvidia graphics card, desktop freezes

Status in X.Org X server:
  Incomplete
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Screen freezes occasionally while simply browsing the web, can be recovered 
by ctrl+alt+f1 and ctrl+alt+f7 
  This has been the case in 14.04, and it's still the case in 14.10 (64 bit)
  Asus UX32V
   331.89-0ubuntu5
   *** 331.89-0ubuntu5 0
  500 http://nl.archive.ubuntu.com/ubuntu/ utopic/restricted amd64 
Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: xorg 1:7.7+7ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Ez egy könyvtár: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  331.89  Tue Jul  1 13:30:18 
PDT 2014
   GCC version:  gcc version 4.9.1 (Ubuntu 4.9.1-16ubuntu6)
  .tmp.unity.support.test.0:
   
  .tmp.unity.support.test.1:
   
  ApportVersion: 2.14.7-0ubuntu8
  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
  CurrentDesktop: Unity
  Date: Wed Oct 29 12:40:01 2014
  DistUpgraded: 2014-10-28 11:18:50,177 DEBUG enabling apt cron job
  DistroCodename: utopic
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 3.16.0-23-generic, x86_64: installed
   bbswitch, 0.7, 3.16.0-24-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:1507]
 Subsystem: ASUSTeK Computer Inc. GeForce GT 620M [1043:1507]
  InstallationDate: Installed on 2014-05-31 (150 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: ASUSTeK COMPUTER INC. UX32VD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic.efi.signed 
root=UUID=690e7454-2b46-48e2-9b5e-57228f67864a ro quiet splash 
processor.ignore_ppc=1 vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to utopic on 2014-10-28 (1 days ago)
  dmi.bios.date: 01/29/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX32VD.214
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX32VD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX32VD.214:bd01/29/2013:svnASUSTeKCOMPUTERINC.:pnUX32VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX32VD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914-1~exp1ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Wed Oct 29 12:00:13 2014
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   NVIDIA(0): Failed to initiate mode change.
   NVIDIA(0): Failed to complete mode change
   NVIDIA(0): Failed to initiate mode change.
   NVIDIA(0): Failed to complete mode change
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id4931 
   vendor CMN
  xserver.version: 2:1.16.0-1ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1387134/+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 1387134] Re: when enabled nvidia graphics card, desktop freezes

2016-01-13 Thread donquixote
Alberto Salvia Novella (es20490446e) had set this as incomplete because he 
wanted to see it reported on bugs.freedesktop.org.
This has happened. At least 4 bug reports already exist on bugs.freedesktop.org.
So I restore the "Confirmed" status.

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

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

Title:
  when enabled nvidia graphics card, desktop freezes

Status in X.Org X server:
  Incomplete
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Screen freezes occasionally while simply browsing the web, can be recovered 
by ctrl+alt+f1 and ctrl+alt+f7 
  This has been the case in 14.04, and it's still the case in 14.10 (64 bit)
  Asus UX32V
   331.89-0ubuntu5
   *** 331.89-0ubuntu5 0
  500 http://nl.archive.ubuntu.com/ubuntu/ utopic/restricted amd64 
Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: xorg 1:7.7+7ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Ez egy könyvtár: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  331.89  Tue Jul  1 13:30:18 
PDT 2014
   GCC version:  gcc version 4.9.1 (Ubuntu 4.9.1-16ubuntu6)
  .tmp.unity.support.test.0:
   
  .tmp.unity.support.test.1:
   
  ApportVersion: 2.14.7-0ubuntu8
  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
  CurrentDesktop: Unity
  Date: Wed Oct 29 12:40:01 2014
  DistUpgraded: 2014-10-28 11:18:50,177 DEBUG enabling apt cron job
  DistroCodename: utopic
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 3.16.0-23-generic, x86_64: installed
   bbswitch, 0.7, 3.16.0-24-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:1507]
 Subsystem: ASUSTeK Computer Inc. GeForce GT 620M [1043:1507]
  InstallationDate: Installed on 2014-05-31 (150 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: ASUSTeK COMPUTER INC. UX32VD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic.efi.signed 
root=UUID=690e7454-2b46-48e2-9b5e-57228f67864a ro quiet splash 
processor.ignore_ppc=1 vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to utopic on 2014-10-28 (1 days ago)
  dmi.bios.date: 01/29/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX32VD.214
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX32VD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX32VD.214:bd01/29/2013:svnASUSTeKCOMPUTERINC.:pnUX32VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX32VD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914-1~exp1ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Wed Oct 29 12:00:13 2014
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   NVIDIA(0): Failed to initiate mode change.
   NVIDIA(0): Failed to complete mode change
   NVIDIA(0): Failed to initiate mode change.
   NVIDIA(0): Failed to complete mode change
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id4931 
   vendor CMN
  xserver.version: 2:1.16.0-1ubuntu1

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

-- 
Mailing list: 

[Desktop-packages] [Bug 1387134] Re: when enabled nvidia graphics card, desktop freezes

2016-01-13 Thread donquixote
> Please:
> 1. Report to .
> 2. Paste the new report URL here.
> 3. Set this bug status back to "confirmed".

This has already been reported multiple times, it seems:
https://bugs.freedesktop.org/show_bug.cgi?id=70117
https://bugs.freedesktop.org/show_bug.cgi?id=73694
https://bugs.freedesktop.org/show_bug.cgi?id=90451
https://bugs.freedesktop.org/show_bug.cgi?id=83516

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

Title:
  when enabled nvidia graphics card, desktop freezes

Status in X.Org X server:
  Incomplete
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Screen freezes occasionally while simply browsing the web, can be recovered 
by ctrl+alt+f1 and ctrl+alt+f7 
  This has been the case in 14.04, and it's still the case in 14.10 (64 bit)
  Asus UX32V
   331.89-0ubuntu5
   *** 331.89-0ubuntu5 0
  500 http://nl.archive.ubuntu.com/ubuntu/ utopic/restricted amd64 
Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: xorg 1:7.7+7ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Ez egy könyvtár: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  331.89  Tue Jul  1 13:30:18 
PDT 2014
   GCC version:  gcc version 4.9.1 (Ubuntu 4.9.1-16ubuntu6)
  .tmp.unity.support.test.0:
   
  .tmp.unity.support.test.1:
   
  ApportVersion: 2.14.7-0ubuntu8
  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
  CurrentDesktop: Unity
  Date: Wed Oct 29 12:40:01 2014
  DistUpgraded: 2014-10-28 11:18:50,177 DEBUG enabling apt cron job
  DistroCodename: utopic
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 3.16.0-23-generic, x86_64: installed
   bbswitch, 0.7, 3.16.0-24-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:1507]
 Subsystem: ASUSTeK Computer Inc. GeForce GT 620M [1043:1507]
  InstallationDate: Installed on 2014-05-31 (150 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: ASUSTeK COMPUTER INC. UX32VD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic.efi.signed 
root=UUID=690e7454-2b46-48e2-9b5e-57228f67864a ro quiet splash 
processor.ignore_ppc=1 vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to utopic on 2014-10-28 (1 days ago)
  dmi.bios.date: 01/29/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX32VD.214
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX32VD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX32VD.214:bd01/29/2013:svnASUSTeKCOMPUTERINC.:pnUX32VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX32VD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914-1~exp1ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Wed Oct 29 12:00:13 2014
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   NVIDIA(0): Failed to initiate mode change.
   NVIDIA(0): Failed to complete mode change
   NVIDIA(0): Failed to initiate mode change.
   NVIDIA(0): Failed to complete mode change
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id4931 
   vendor CMN
  xserver.version: 2:1.16.0-1ubuntu1

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1387134] Re: when enabled nvidia graphics card, desktop freezes

2016-01-13 Thread donquixote
Affects me with UX32VD and external monitor connected.
Linux Mint 17.1, Cinnamon 64-bit.

"[drm:intel_dp_start_link_train], too many voltage retries, give up"

The Ctrl+F1 and back helps to get out of freeze, but I have to do this a
lot.

It seems the freeze happens more often if more windows are open..

I already have external usb mouse and external usb keyboard connected,
and the external monitor (1920*1080) on micro-vga.

** Bug watch added: freedesktop.org Bugzilla #70117
   https://bugs.freedesktop.org/show_bug.cgi?id=70117

** Bug watch added: freedesktop.org Bugzilla #73694
   https://bugs.freedesktop.org/show_bug.cgi?id=73694

** Bug watch added: freedesktop.org Bugzilla #90451
   https://bugs.freedesktop.org/show_bug.cgi?id=90451

** Bug watch added: freedesktop.org Bugzilla #83516
   https://bugs.freedesktop.org/show_bug.cgi?id=83516

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

Title:
  when enabled nvidia graphics card, desktop freezes

Status in X.Org X server:
  Incomplete
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Screen freezes occasionally while simply browsing the web, can be recovered 
by ctrl+alt+f1 and ctrl+alt+f7 
  This has been the case in 14.04, and it's still the case in 14.10 (64 bit)
  Asus UX32V
   331.89-0ubuntu5
   *** 331.89-0ubuntu5 0
  500 http://nl.archive.ubuntu.com/ubuntu/ utopic/restricted amd64 
Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: xorg 1:7.7+7ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Ez egy könyvtár: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  331.89  Tue Jul  1 13:30:18 
PDT 2014
   GCC version:  gcc version 4.9.1 (Ubuntu 4.9.1-16ubuntu6)
  .tmp.unity.support.test.0:
   
  .tmp.unity.support.test.1:
   
  ApportVersion: 2.14.7-0ubuntu8
  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
  CurrentDesktop: Unity
  Date: Wed Oct 29 12:40:01 2014
  DistUpgraded: 2014-10-28 11:18:50,177 DEBUG enabling apt cron job
  DistroCodename: utopic
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 3.16.0-23-generic, x86_64: installed
   bbswitch, 0.7, 3.16.0-24-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:1507]
 Subsystem: ASUSTeK Computer Inc. GeForce GT 620M [1043:1507]
  InstallationDate: Installed on 2014-05-31 (150 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: ASUSTeK COMPUTER INC. UX32VD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic.efi.signed 
root=UUID=690e7454-2b46-48e2-9b5e-57228f67864a ro quiet splash 
processor.ignore_ppc=1 vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to utopic on 2014-10-28 (1 days ago)
  dmi.bios.date: 01/29/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX32VD.214
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX32VD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX32VD.214:bd01/29/2013:svnASUSTeKCOMPUTERINC.:pnUX32VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX32VD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914-1~exp1ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Wed Oct 29 12:00:13 2014
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   

[Desktop-packages] [Bug 666863] Re: Nautilus sftp suspend

2013-04-24 Thread donquixote
Hi,
is there any hope for this on Lucid?
I am using Lucid Lynx with Nautilus 2.30.1. Is there a way to get a more 
up-to-date version, without leaving Lucid?

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

Title:
  Nautilus sftp   suspend

Status in Nautilus:
  Fix Released
Status in “gvfs” package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: nautilus

  When connected to sftp,  nautilus behaves unpredictable after a 
suspend/wakeup cycle. Just now I was connected to a sftp-server at work. I put 
the laptop in suspend, went home, and then woke the computer again. The 
sftp-connection is displayed as still active. When I press the reload-button in 
nautilus, the file-manager hangs for approx 60 seconds. Then it fails to 
reload, with the following two error-messages: 
  - The folder contents could not be displayed.
  Sorry, could not display all the contents of category: DBus error 
org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes 
include: the remote application did not send a reply, the message bus security 
policy blocked the reply, the reply timeout expired, or the network connection 
was broken.

  ... and ...

  - Could not display 
sftp://utv...@utvikling.arcg...ner/html/com_content/category;.
  Error: DBus error org.freedesktop.DBus.Error.NoReply: Did not receive a 
reply. Possible causes include: the remote application did not send a reply, 
the message bus security policy blocked the reply, the reply timeout expired, 
or the network connection was broken.
  Please select another viewer and try again.

  Clicking the unmount-icon in nautilus, and the reconnecting, nautilus
  connects without problems.

  However, I have experienced that a shorter/different suspend/awake-
  cycle might give a different result.

  Expected result: Trying to reload a folder should ultimately try to
  disconnect and reconnect the connection if the connection is broken.
  Alternatively, nautilus should fail gracefully with a single,
  understandable error message.

  regards Jonas

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: nautilus 1:2.30.1-0ubuntu1.1
  ProcVersionSignature: Ubuntu 2.6.32-25.45-generic 2.6.32.21+drm33.7
  Uname: Linux 2.6.32-25-generic i686
  NonfreeKernelModules: nvidia
  Architecture: i386
  Date: Tue Oct 26 17:50:20 2010
  InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100429)
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: nautilus

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/666863/+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 745556] Re: nautilus ssh connection after suspend to ram - browsing location lost

2011-12-23 Thread donquixote
Just saying, this thing is not fixed.

Atm, what I see mostly happen:
I wake up from suspend-to-ram with 4 nautilus tabs open to an ssh location.
These are unresponsive, until I unmount the dead ssh connection. I try browsing 
them to a local folder, but they do not respond.
When I do this, the tabs just close.

This means, I cannot easily interrupt my work on ssh with suspend or
hibernate.

There are several solutions imaginable for this.
- On the dead ssh connection, in addition to unmount, there could be a 
reconnect or restore connection option.
- Unresponsive nautilus tabs, that depend on a dead ssh connection, could have 
a reconnect/unmount button.
- Unmounting the ssh connection would still close all those tabs.

I think, the same would make sense for external storage devices. Think of 
external HD, that gets disconnected from power supply during suspend / 
hibernate.
When they are removed / unmounted in a controlled fashion, then the nautilus 
tabs can close.
When they are removed / switched off during suspend or hibernate, and then just 
missing, the nautilus tabs should remain in a pending state, with a note 
asking to reconnect the device.

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

Title:
  nautilus ssh connection after suspend to ram - browsing location lost

Status in “nautilus” package in Ubuntu:
  Incomplete

Bug description:
  10.04 LTS - the Lucid Lynx

  Following steps:
  1. Places  Bookmarks  ssh on server xyz
  (that's a bookmark I made in a remote folder)
  2. I type the password to open the nautilus window with the remote folder.
  3. Ctrl-T to open two other nautilus tabs in different remote folders on the 
same ssh connection. Navigate around in all three tabs, but stay on the remote 
server.
  4. Open one of the remote files in gedit.
  5. Suspend to RAM.
  6. Wake up from Suspend.

  Now we are in a strange situation:
  - The gedit remote file looks like it is still open, but doing anything in 
there makes the gedit tab unresponsive.
  - All three nautilus tabs look like they are still open, but they are 
unresponsive.

  The only way to fix it:
  7. Unmount the ssh connection (in the nautilus side pane)
  (btw, left-clicking it makes the side pane scroll state jump down)

  Now all but one of the remote nautilus tabs is being closed, and instead we 
get one nautilus tab in a local location.
  The file in gedit is still open.

  Now we can either
  8.a) Save the file in gedit - asks me for the ssh password, and the ssh 
connection is back. (but nautilus location is still lost) Or
  8.b) Hit Back in nautilus - asks me for the ssh password, the ssh 
connection is back, and the nautilus location is restored - for one of the 
tabs. The other tabs are still closed, the location lost.
  8.c) Use again the bookmark to get to the remote location.

  Now the problem is, the other two tabs are lost, and I need to navigate again 
to get to these locations.
  So,
  9. Ctrl-T to open two other Nautilus tabs. Navigate around until we are back 
at the locations where we have been.

  To summarize, the problems are:
  - Having to click around more than necessary to reconnect the ssh connection.
  - Having to navigate again to get back to the folders, instead of them being 
remembered.

  Thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/745556/+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 745556] Re: nautilus ssh connection after suspend to ram - browsing location lost

2011-12-23 Thread donquixote
And why is this incomplete?
This has followed me from version to version, and I suppose it would be easy 
for anyone to reproduce.

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

Title:
  nautilus ssh connection after suspend to ram - browsing location lost

Status in “nautilus” package in Ubuntu:
  Incomplete

Bug description:
  10.04 LTS - the Lucid Lynx

  Following steps:
  1. Places  Bookmarks  ssh on server xyz
  (that's a bookmark I made in a remote folder)
  2. I type the password to open the nautilus window with the remote folder.
  3. Ctrl-T to open two other nautilus tabs in different remote folders on the 
same ssh connection. Navigate around in all three tabs, but stay on the remote 
server.
  4. Open one of the remote files in gedit.
  5. Suspend to RAM.
  6. Wake up from Suspend.

  Now we are in a strange situation:
  - The gedit remote file looks like it is still open, but doing anything in 
there makes the gedit tab unresponsive.
  - All three nautilus tabs look like they are still open, but they are 
unresponsive.

  The only way to fix it:
  7. Unmount the ssh connection (in the nautilus side pane)
  (btw, left-clicking it makes the side pane scroll state jump down)

  Now all but one of the remote nautilus tabs is being closed, and instead we 
get one nautilus tab in a local location.
  The file in gedit is still open.

  Now we can either
  8.a) Save the file in gedit - asks me for the ssh password, and the ssh 
connection is back. (but nautilus location is still lost) Or
  8.b) Hit Back in nautilus - asks me for the ssh password, the ssh 
connection is back, and the nautilus location is restored - for one of the 
tabs. The other tabs are still closed, the location lost.
  8.c) Use again the bookmark to get to the remote location.

  Now the problem is, the other two tabs are lost, and I need to navigate again 
to get to these locations.
  So,
  9. Ctrl-T to open two other Nautilus tabs. Navigate around until we are back 
at the locations where we have been.

  To summarize, the problems are:
  - Having to click around more than necessary to reconnect the ssh connection.
  - Having to navigate again to get back to the folders, instead of them being 
remembered.

  Thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/745556/+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 745556] Re: nautilus ssh connection after suspend to ram - browsing location lost

2011-09-15 Thread donquixote
I think this behavior is not as it should be.
At the time I wrote the previous message, it did work with suspend-to-ram.
Now I checked with hibernate, and again I need to manually cut ssh connection 
and then do something to reconnect. And before I cut the connection, things 
freeze.

So, the problems I have:
- the freeze on some things (Nautilus, gedit) before I cut the (broken) 
connection.
- the steps needed to get back to the connection and nautilus browsing state 
that i had before hibernation.

I suggest some of the people at ubuntu should test this, and then decide
what is the intended / desirable behavior in this kind of situation. Atm
it seems that there is no intentional spec about this, just anything can
happen.

And please, be careful with modal dialogs, that interrupt the flow at
the wrong time. The user should not care about the broken connection,
until she wants to interact with the nautilus or gedit tab that depends
on the connection.

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

Title:
  nautilus ssh connection after suspend to ram - browsing location lost

Status in “nautilus” package in Ubuntu:
  Incomplete

Bug description:
  10.04 LTS - the Lucid Lynx

  Following steps:
  1. Places  Bookmarks  ssh on server xyz
  (that's a bookmark I made in a remote folder)
  2. I type the password to open the nautilus window with the remote folder.
  3. Ctrl-T to open two other nautilus tabs in different remote folders on the 
same ssh connection. Navigate around in all three tabs, but stay on the remote 
server.
  4. Open one of the remote files in gedit.
  5. Suspend to RAM.
  6. Wake up from Suspend.

  Now we are in a strange situation:
  - The gedit remote file looks like it is still open, but doing anything in 
there makes the gedit tab unresponsive.
  - All three nautilus tabs look like they are still open, but they are 
unresponsive.

  The only way to fix it:
  7. Unmount the ssh connection (in the nautilus side pane)
  (btw, left-clicking it makes the side pane scroll state jump down)

  Now all but one of the remote nautilus tabs is being closed, and instead we 
get one nautilus tab in a local location.
  The file in gedit is still open.

  Now we can either
  8.a) Save the file in gedit - asks me for the ssh password, and the ssh 
connection is back. (but nautilus location is still lost) Or
  8.b) Hit Back in nautilus - asks me for the ssh password, the ssh 
connection is back, and the nautilus location is restored - for one of the 
tabs. The other tabs are still closed, the location lost.
  8.c) Use again the bookmark to get to the remote location.

  Now the problem is, the other two tabs are lost, and I need to navigate again 
to get to these locations.
  So,
  9. Ctrl-T to open two other Nautilus tabs. Navigate around until we are back 
at the locations where we have been.

  To summarize, the problems are:
  - Having to click around more than necessary to reconnect the ssh connection.
  - Having to navigate again to get back to the folders, instead of them being 
remembered.

  Thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/745556/+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