[Desktop-packages] [Bug 1791981] Re: X Server session crash for "No space left on device"

2019-11-07 Thread Ben Echols
This is happening to me right now (On Ubuntu 19.10, kernel 5.3.0 and
5.3.9, nvidia drivers version 435 and 440)


It only happens when using nvidia GPU. If I prime-select my intel GPU then 
there is no issue.

It seems related to the laptop display being on some internal display
port that gets disconnected when the lid is closed.

If I type 'systemctl suspend' before closing my lid everything works
fine when I open.

I suspect this is actually a bug in nvidia drivers and not in xorg-
server

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

Title:
  X Server session crash for "No space left on device"

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu Release: Ubuntu 18.04.1 LTS
  Package version: xserver-xorg: 1:7.7+19ubuntu7.1

  When my laptop resumes after suspend, the desktop session crashes and a new 
one is started. So each time I lose all open applications and unsaved data!
  The expected behavior would be obviously to restore the suspended session.

  I had a look through log files and found that Xorg.0.log ends with the
  following error lines:

  [  6004.019] (II) NVIDIA(0): Setting mode "NULL"
  [  6004.026] (EE) modeset(G0): failed to set mode: No space left on device
  [  6004.026] (EE) 
  Fatal server error:
  [  6004.026] (EE) EnterVT failed for gpu screen 0
  [  6004.027] (EE) 
  [  6004.027] (EE) 
  Please consult the The X.Org Foundation support 
 at http://wiki.x.org
   for help. 
  [  6004.027] (EE) Please also check the log file at "/var/log/Xorg.0.log" for 
additional information.
  [  6004.027] (EE) 
  [  6004.065] (EE) Server terminated with error (1). Closing log file.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1791981/+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 1322728] Re: VPN Connection Failed With 2 Factor Authentication

2019-10-30 Thread Ben Echols
I just tried on 19.10 and have the same issue. Let me know any logs or
anything is needed to help debug the issue.

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

Title:
  VPN Connection Failed With 2 Factor Authentication

Status in network-manager-fortisslvpn package in Ubuntu:
  Confirmed
Status in network-manager-openvpn package in Ubuntu:
  Confirmed

Bug description:
  Hi all,

  my setup is an openvpn access server with google 2 factor auth

  i was trying to connect to my VPN using the gnome openvpn module and
  get the following errors on syslog:

  May 23 22:23:00 laptop nm-openvpn[18049]: [OpenVPN Server] Peer Connection 
Initiated with [AF_INET]xx.xx.xx.xx:1194
  May 23 22:23:02 laptop nm-openvpn[18049]: AUTH: Received control message: 
AUTH_FAILED,CRV1:R,E:d1r12r21df232+owqrf23t23t23tCn:aXRf3r2s=:Enter Google 
Authenticator Code
  May 23 22:23:02 laptop nm-openvpn[18049]: SIGTERM[soft,auth-failure] 
received, process exiting
  May 23 22:23:02 laptop NetworkManager[1043]:  VPN plugin failed: 0

  i looked in the documentation but didn't found anything useful.

  any help will be appreciated

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-fortisslvpn/+bug/1322728/+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 1546641] Re: unity-settings-daemon crashed with SIGSEGV in up_exported_daemon_get_lid_is_closed()

2016-05-02 Thread Ben Echols
This issue occurs on my lenovo laptop when I install nvidia drivers and then 
plug in a second monitor.
If I do not plug in a second monitor this issue never appears for me.

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

Title:
  unity-settings-daemon crashed with SIGSEGV in
  up_exported_daemon_get_lid_is_closed()

Status in unity-settings-daemon package in Ubuntu:
  Triaged
Status in upower package in Ubuntu:
  New
Status in unity-settings-daemon source package in Xenial:
  Triaged
Status in upower source package in Xenial:
  New
Status in unity-settings-daemon source package in Yakkety:
  Triaged
Status in upower source package in Yakkety:
  New

Bug description:
  https://errors.ubuntu.com/problem/8ca9c548fc4e2fc1d4bf827bbd85c72df59313f8

  Ubuntu 16.04 crashes immediately on login. Default settings not
  applied and appearance is a bit ugly (incorrect font hinting, in-
  window menus etc).

  ---

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
  Uname: Linux 4.4.0-6-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  Date: Wed Feb 17 13:52:13 2016
  ExecutablePath: /usr/lib/unity-settings-daemon/unity-settings-daemon
  InstallationDate: Installed on 2016-02-08 (8 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160205)
  ProcCmdline: /usr/lib/unity-settings-daemon/unity-settings-daemon
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/false
  SegvAnalysis:
   Segfault happened at: 0x3aae60fe69 : 
mov(%rbx),%rdi
   PC (0x3aae60fe69) ok
   source "(%rbx)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: unity-settings-daemon
  StacktraceTop:
   up_exported_daemon_get_lid_is_closed () from 
/usr/lib/x86_64-linux-gnu/libupower-glib.so.3
   gsd_power_manager_start () from 
/usr/lib/unity-settings-daemon-1.0/libpower.so
   ?? () from /usr/lib/unity-settings-daemon-1.0/libpower.so
   gnome_settings_plugin_info_activate ()
   ?? ()
  Title: unity-settings-daemon crashed with SIGSEGV in 
up_exported_daemon_get_lid_is_closed()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1546641/+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 1507676] Re: Nvidia-Prime not switching from intel to nvidia leading to a black screen

2016-02-25 Thread Ben Echols
Just a quick update -- disabling gpu-manager in grub (using nogpumanager
option) lets me get to login screen. However actually logging in the
screen flickers black, and then I hear the login drums again and am back
to login. (just like the description of this bug)

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

Title:
  Nvidia-Prime not switching from intel to nvidia leading to a black
  screen

Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-intel package in Ubuntu:
  In Progress

Bug description:
  STEPS:
  1. Install 15.10 on a laptop that supports optimus nvidia/intel hybrid 
graphics
  2. Install nvidia and nvidia-prime
  3. Open nvidia settings
  4. Switch to nvidia
  5. Log out
  6. Hear the login drums

  EXPECTED:
  I expect to see the lightdm login page

  ACTUAL:
  You are presented with a black page

  TEMP WORKAROUND:
  1. Tap ctrl-alt-f1
  2. login
  3. run sudo prime-select intel
  4. run sudo service lightdm restart
  5. System is back running on the intel stack alone.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1507676/+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 1507676] Re: Nvidia-Prime not switching from intel to nvidia leading to a black screen

2016-02-25 Thread Ben Echols
I have a system with intel graphics and nvidia k2100m. I was running
nvidia-358 and nvidia-prime.

I updated to the newest intel drivers yesterday and now on boot I get an
error about my xorg.conf being incorrect.

If I uninstall nvidia entirely everything boots just fine (i can use
nouveau and intel still).

I tracked that down to https://bugs.launchpad.net/ubuntu/+source/ubuntu-
drivers-common/+bug/1419507 which apparently people thought the issue
was related to gpu-manager but Alberto Milone says is related to
xserver-xorg-video-intel which led me to this bug.

I am not sure if my bug is exactly the same cause or not but I am
willing to do anything to help figure this out... It is very
frusterating being unable to use my nvidia drivers.

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

Title:
  Nvidia-Prime not switching from intel to nvidia leading to a black
  screen

Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-intel package in Ubuntu:
  In Progress

Bug description:
  STEPS:
  1. Install 15.10 on a laptop that supports optimus nvidia/intel hybrid 
graphics
  2. Install nvidia and nvidia-prime
  3. Open nvidia settings
  4. Switch to nvidia
  5. Log out
  6. Hear the login drums

  EXPECTED:
  I expect to see the lightdm login page

  ACTUAL:
  You are presented with a black page

  TEMP WORKAROUND:
  1. Tap ctrl-alt-f1
  2. login
  3. run sudo prime-select intel
  4. run sudo service lightdm restart
  5. System is back running on the intel stack alone.

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