[Bug 367318] Re: in VT, screen not being saved (vcsa permission problem to blame)

Shentino shentino at gmail.com
Fri May 22 06:24:04 UTC 2009


** Description changed:

  Binary package hint: mc
  
  Release:  Jaunty Jackalope
  Version of MC:  Current as of apr 26, 2009
  Expected:
  
- MC able to save and restore the shell screen
+ MC able to save and restore the subshell screen
  
  Actual:
  
  MC blanks out
  
- Detail:
+ To reproduce:
  
- When on a virtual console,
+     Log into vt 1 (/dev/tty1)
+     Start mc, then use C-o to switch to the subshell.  Observe that the screen is blanked.
+     Exit mc
+     sudo chown you:you /dev/vcsa1 # this is the workaround
+     Start mc again
+     Use C-o to switch to the subshell and notice that the subshell screen is now properly saved and restored
  
- Using control-O to flip between MC and the subshell causes the screen to
- be erased.
+ User's diagnosis:
  
- Diagnosis:
+ For some reason /dev/vcsa* permissions aren't being properly set up when
+ a user logs in on a virtual console.
  
- The problem is that for some reason a vc login isn't granting the appropriate permissions on /dev/vcs*
- Which in turn means that mc is unable to read /dev/vcsa*
- 
- Kludgy workaround:
- 
- I wrote a suid-root C program to grant world rwx to /dev/vcs* every time
- I log in on VC.
- 
- Changing the files so that the user has read/write permission to
- /dev/vcsa* solves the problem.  I suspect that mc is a victim of a bug
- elsewhere that fails to grant a console user the appropriate permissions
- /dev/vcs* upon a login.
+ I move that this be considered a bug for which mc is a victim.
  
  ProblemType: Bug
  Architecture: i386
  DistroRelease: Ubuntu 9.04
  NonfreeKernelModules: nvidia
  Package: mc 2:4.6.2~git20080311-4ubuntu1
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: mc
  Uname: Linux 2.6.28-11-generic i686

-- 
in VT, screen not being saved (vcsa permission problem to blame)
https://bugs.launchpad.net/bugs/367318
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs at lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs




More information about the universe-bugs mailing list