Additional info: --no-install-recommends might be the culprit. It seems it is
to be used sparingly, not all the time.
I'd have to reinstall to be sure thoughn because even removing myself from
the input group works just fine now.
Well, regarding mouse and keyboard(s) being accessible from startx without
sudo, it definitely works :)
If I have other bad surprises, now I know I can add my user to more groups
for different purposes.
But I still don't like how it's a bit hacked (instead of a working directly
from a
Maybe there is a bug related to the encryption method. It seems the problem
is not that uncommon.
Is it working normally now?? That is great :)
I don't feel like I helped much but at least your machine is working now :D
Bingo, adding my user to input did work.
But I'm not satisfied:
* .xinitrc should load X automatically, it doesn't.
* Why do I need to add my user to the input group? Do I need to belong to
other groups just to have a functional machine?
And, uh, that would be pretty much it.
It seems I need to add myself in the input group:
https://github.com/bulletmark/libinput-gestures/issues/7
But How come I'm not into this group in the first place?
Well, I'll test that first, because there's no point to this question if it
doesn't solve the issue.
is it fine in terms of free software? If so, I guess I can find them on
nvidia's website?
But I thought my GPU worked just fine with Nouveau (which it does, even right
now with an incomplete startx launch).
Also try upgrading to jxself kernel.
Install nvdia drivers and blacklist nv as stated here:
troubleshooting X server. (EE) Failed to load module "nv" (module does not
exist, 0) - Ask Ubuntu -
https://askubuntu.com/questions/90915/troubleshooting-x-server-ee-failed-to-load-module-nv-module-does-not-exist
this
(https://unix.stackexchange.com/questions/149985/startx-cannot-open-dev-fb0-permission-denied)
seems interesting.
Before trying to fix (most likely format) my thumb drive and fetching the
full logs, I'll reboot into the new user and try startx again. It seems
startx might be occupied by the old user.
In the original user's xorg's log, in addition to what's listed for the new
test user:
* (WW) Falling back to old probe method for modesetting (and for fdev on the
line efter)
* (WW) Falling back to old probe method for vesa
* (WW) VGA arbiter: cannot open kernel arbiter, no multi-card
Good call, with the new user, I can't launch startx at all, and it seems I
have now access to some xorg log.
The plot unfolds (I hope so)!
Wait
New Idea... Could you create a new user and see if with a new user it works?
I am getting out of ideas :/ specially because you say it works on other
computers and it worked before.
This is weird. I hope that a fresh install will solve it then :/
Or maybe someone else could join and suggest something else??
Sure, I just added exec i3.
But my original one is like this:
#!/bin/sh
# /etc/X11/xinit/xinitrc
#
# global xinitrc file, used by all X sessions started by xinit (startx)
# invoke global X session script
. /etc/X11/Xsession
/usr/lib/polkit-gnome/polkit-gnome-authentication-agent-1 # &
exec
What does ~./xinitrc says could yei share it?
Could you check if you have xorg-xinit and it is configured properly?
https://wiki.archlinux.org/index.php/Xinit
Thoug, it must be because root works.. :/
Maybe install a different Desktop Environment see if it works?
Uh, something new:
* I deleted i3 (apt-get purge, autoremove, clean), and startx still lands me
in i3
* I removed the (empty) i3 folder present in .config, but I still land in
i3...
As it could be important, one thing I did during the install is the
following:
the /boot partition I set up as the one to be initialized.
But now in my directory tree, I see in / another /boot folder, and also
another /lost+found (the same I find in /home).
I only have a .bashrc, and a .profile which redirects to .bashrc.
I renamed it to _old (same wit .xinitrc), the issue still remains.
Compared to a working install, /home, and the folders and files inside it
have the same ownership and permissions.
I can try with a fresh copy of .xinitrc from /etc/X11/xinit and modify it
accordingly (with exec i3).
OK, I'll try this, thanks again.
Yes, no dedicated /home encryption, but an encrypted partition containing
/home, /root and /swap.
On the other hand, I have other fully encrypted disks (nothing installed on
them though).
No custom config files by default yet (besides the .xinitrc for testing).
I notice now that /home
As you said, checking files and directories permissions is also a good thing
to do.
If that doesn't... Then I would rename ~/.config/i3/config
And after that maybe .bash_profile or .bashrc or .bash
Rename them to something else, if the problem continues then you can change
the name back to the original.
In an extreme case I would rename all ~./config to something like
Ok.
So currently you have an install with only disk encryption apart from /boot
but /home has not its own encryption?
Do you have any custom config files? I would delete them first
Many thanks for your help albertoefg!
root user has a different config file that is not in /home but in /root
If you encrypted disk and /home when you unlock at boot you are only
unblocking the disk but not /home
Make sure /home is decrypted before startx
On the disk where
I3 requires to read config which is in /home
root user has a different config file that is not in /home but in /root
If you encrypted disk and /home when you unlock at boot you are only
unblocking the disk but not /home
Probably i3 freezes because it can't read config file and also all the
You're right, let me try again this way then:
* the keyboard and mouse respond very well in the shell (well not the mouse
of course), but after startx, which boots i3wm, it doesn't.
* the keyboard doesn't activate the screen after moments of inactivity.
* It did work after startx on an earlier
No, any of the bash files are the default ones.
The i3 config is also the default (I didn't have the opportunity to copy my
personal config yet).
It's basically a fresh install (with the drive erased) with xorg, i3 and
pcmanfm installed.
I added a personal .xinitrc just to see if it would
Try to describe more the current problem than your guesses or previous
problems
Describe the problem's symptoms, not your guesses
It's not useful to tell hackers what you think is causing your problem. (If
your diagnostic theories were such hot stuff, would you be consulting others
for
Did you modify ~/.bash or ~/.bash_profile or ~/.bashrc or something like
that?
Maybe your ./config/i3/config is executing some program you have not
installed or configured properly??
sudo startx worked.
It's not recommended, so it's not a solution.
I'm even more sure that i3/the X session didn't freeze as the time display
progresses.
This time I enabled the numpad, and what's odd is that he led stays on even
if I unplug, then replug the keyboard.
I tried to switch to a tty, or even kill the X session, but neither the mouse
or
Encryption shouldn't be an issue after unlocking the disks/partition. I don't
understand. The install went just the same way beyond the partitioning.
It must be something related to xorg.
It kinda makes sense for the USB keyboard not available until reaching the
shell though.
Hi,
the keyboard and mouse respond very well in the shell (well not the mouse of
course),
but after startx, which boots i3wm, it doesn't.
At first I thought i3wm was freezing, but the mouse pointer changed from the
waiting icon to the normal pointer after a bit (yet still immovable). And
35 matches
Mail list logo
