* I can only start an X server in guix as root
@ 2017-03-18 0:50 Joshua Branson
2017-03-18 14:50 ` pelzflorian (Florian Pelz)
0 siblings, 1 reply; 4+ messages in thread
From: Joshua Branson @ 2017-03-18 0:50 UTC (permalink / raw)
To: help-guix@gnu.org
[-- Attachment #1: Type: text/plain, Size: 876 bytes --]
Hello,
I currently dual boot guixSD and Parabola. I use a macbook 7,1, and I
am unable to start an X server in guix as my normal user. I can login
to gnome via my root user, but obviously this is not ideal. I can login
to a virtual console as my normal user and access Emacs (yeah), but it
would be nice to be able to start gnome as my normal user. Just today I ran
guix pull; sudo guix pull; guix system reconfigure /etc/gnome-xfce.scm
It updated fine. I rebooted and the problem still persists. Parabola
and guix have seperate / partitions, but they share the same /home.
I've set up guix to create my normal user (joshua) with a uid of 2000,
because that is the uid that the user joshua has on parabola.
I'm attaching my config.scm file and some errors that I've found that
are probably relevant. Any help would be nice.
[-- Attachment #2: guix-X-errors.txt --]
[-- Type: text/plain, Size: 3880 bytes --]
grep WW Xorg.0.log
[ 6357.578] (WW) xf86CloseConsole: VT_ACTIVATE failed: Input/output error
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 47.212] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[ 47.212] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[ 47.237] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[ 47.385] (WW) Warning, couldn't open module nv
[ 47.393] (WW) Warning, couldn't open module fbdev
[ 47.393] (WW) Warning, couldn't open module vesa
[ 47.394] (WW) Falling back to old probe method for modesetting
[ 47.395] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
[ 6357.578] (WW) xf86CloseConsole: KDSETMODE failed: Input/output error
[ 6357.578] (WW) xf86CloseConsole: VT_GETMODE failed: Input/output error
[ 6357.578] (WW) xf86CloseConsole: VT_ACTIVATE failed: Input/output error
grep EE Xorg.1.log
[ 47.080] Current Operating System: Linux parabola 4.10.1-gnu-1 #1 SMP PREEMPT Mon Feb 27 17:40:02 UYT 2017 x86_64
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 47.385] (EE) Failed to load module "nv" (module does not exist, 0)
[ 47.393] (EE) Failed to load module "fbdev" (module does not exist, 0)
[ 47.393] (EE) Failed to load module "vesa" (module does not exist, 0)
[ 47.580] (EE) NOUVEAU(0): [COPY] failed to allocate class.
[ 6357.259] (EE) systemd-logind: failed to release device: Connection is closed
[ 6357.284] (EE) systemd-logind: failed to release device: Connection is closed
[ 6357.309] (EE) systemd-logind: failed to release device: Connection is closed
[ 6357.346] (EE) systemd-logind: failed to release device: Connection is closed
[ 6357.366] (EE) systemd-logind: failed to release device: Connection is closed
[ 6357.379] (EE) systemd-logind: failed to release device: Connection is closed
[ 6357.393] (EE) systemd-logind: failed to release device: Connection is closed
[ 6357.578] (EE) systemd-logind: ReleaseControl failed: Connection is closed
tail -n 10000 /var/log/messages | grep WARNING -m 5 -n
223:Jan 3 15:14:42 localhost avahi-daemon[326]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
691:Feb 4 10:27:09 localhost avahi-daemon[326]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
1694:Feb 4 11:07:13 localhost avahi-daemon[324]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
2626:Feb 4 11:12:58 localhost avahi-daemon[326]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
3364:Feb 4 17:58:05 localhost avahi-daemon[326]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
tail -n 10000 /var/log/messages | grep ERROR -m 5 -n
1225:Feb 4 10:33:46 localhost ntpd[321]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized
3909:Feb 4 18:07:39 localhost ntpd[322]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized
6121:Mar 14 15:51:34 localhost ntpd[320]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized
6916:Mar 15 16:17:38 localhost ntpd[318]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized
7687:Mar 16 13:29:37 localhost ntpd[319]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized
some other old errors
Dec 5 21:09:54 localhost gnome-session-binary[443]: WARNING: Could not parse desktop file xscreensaver.desktop or it references a not found TryExec binary
Dec 5 21:09:55 localhost gnome-keyring-daemon[475]: couldn't access control socket: /run/user/0/keyring/control: No such file or directory
Dec 5 21:09:55 localhost gnome-keyring-daemon[476]: couldn't access control socket: /run/user/0/keyring/control: No such file or directory
Dec 5 21:09:55 localhost gnome-keyring-daemon[477]: couldn't access control socket: /run/user/0/keyring/control: No such file or directory
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #3: gnome-xfce.scm --]
[-- Type: text/x-scheme; name="gnome-xfce.scm", Size: 4610 bytes --]
;; This is an operating system configuration template
;; for a "desktop" setup with GNOME and Xfce and awesome.
;; I am using this file as of march 17th
(use-modules (gnu) (gnu system nss))
(use-service-modules desktop)
(use-package-modules certs gnome)
(operating-system
(host-name "GuixSD")
(timezone "America/Indianapolis")
(locale "en_US.UTF-8")
;;blacklist this keyboard module. It might help my mouse to load properly.
;;http://debbugs.gnu.org/cgi/bugreport.cgi?bug=20433
;; (kernel-arguments '("modprobe.blacklist=usbkdb"))
(swap-devices '("/dev/sda3"))
;; Assuming /dev/sdX is the target hard disk, and "my-root"
;; is the label of the target root file system.
(bootloader (grub-configuration (device "/dev/sda")
;; This bug was fixed with a newer version of guix. Cool!
;; Here is my hack (grub-configuration appends bzImage to `linux')
;; to add a custom entry for debian on /dev/sda3 to the Grub menu
;; On Debian, do:
;; sudo mkdir -p /boot/latest
;; sudo ln -s $(ls -t /boot/vmlinuz*|head -1) /boot/latest/bzImage
;; sudo ln -s $(ls -t /boot/initramfs*|head -1) /boot/latest/initrd
(menu-entries
(list (menu-entry
(label "Parabola")
(linux "(hd0,1)/boot/vmlinuz-linux-libre")
(linux-arguments '("root=/dev/sda1 ro"))
(initrd "(hd0,1)/boot/initramfs-linux-libre.img"))))))
(file-systems (cons* (file-system
(device "my-root")
(title 'label)
(mount-point "/")
(type "ext4"))
(file-system
(mount-point "/home")
(device "/dev/sda4")
(type "ext4"))
%base-file-systems))
(users (cons (user-account
(name "joshua")
(comment "joshua")
;;I need to specify that joshua has the uid of 2000.
(uid 2000)
(group "users")
(supplementary-groups '("wheel" "netdev"
"audio" "video" "home"))
(home-directory "/home/joshua"))
%base-user-accounts))
(groups (cons (user-group
(name "home")
;;I need to specify that there is a home group. Most of my files in my home directory are owned by the group home.
;;Though I could probably just make them owned by joshua.
(id 2000))
%base-groups))
;; This is where we specify system-wide packages.
(packages (cons*
;;awesome
nss-certs ;for HTTPS access
;;emacs
;;icecat
;;adding in extra window managers, so maybe I'll be able to login.
;;i3-wm
;;xmonad
;;ratpoison
%base-packages))
;; (packages (append (map specification->package
;; '(
;;"awesome"
;;"brasero"
;;"devhelp"
;;"diction"
;;"emacs"
;;"emacs-async"
;;"emacs-ace-window"
;;"emacs-dash"
;;"emacs-emms"
;;"emacs-evil"
;;"emacs-f"
;;"emacs-flycheck"
;;"emacs-helm"
;;"emacs-js2-mode"
;;"emacs-magit-popup"
;;"emacs-mmm-mode"
;;"emacs-org"
;;"emacs-paredit"
;;"emacs-pdf-tools"
;;"emacs-projectile"
;;"emacs-rainbow-delimiters"
;;"emacs-smart-mode-line"
;;"emacs-web-mode"
;;"emacs-zenburn-theme"
;;"geiser"
;;code is guile like in python
;;"font-hack"
;;"font-dejavu"
;;"icecat"
;; for HTTPS access
;; "nss-certs"))
;; %base-packages))
;; Add GNOME and/or Xfce---we can choose at the log-in
;; screen with F1. Use the "desktop" services, which
;; include the X11 log-in service, networking with Wicd,
;; and more.
(services (cons* (gnome-desktop-service)
(xfce-desktop-service)
;; apparently syslog is provided by default
;;(syslog-service)
;;make the console use the dvorak keyboard layout
(console-keymap-service "dvorak")
%desktop-services))
;; Allow resolution of '.local' host names with mDNS.
(name-service-switch %mdns-host-lookup-nss))
^ permalink raw reply [flat|nested] 4+ messages in thread* Re: I can only start an X server in guix as root
2017-03-18 0:50 I can only start an X server in guix as root Joshua Branson
@ 2017-03-18 14:50 ` pelzflorian (Florian Pelz)
2017-03-19 21:04 ` Ludovic Courtès
0 siblings, 1 reply; 4+ messages in thread
From: pelzflorian (Florian Pelz) @ 2017-03-18 14:50 UTC (permalink / raw)
To: help-guix
On 03/18/2017 01:50 AM, Joshua Branson wrote:
>
>
> Hello,
>
>
> I currently dual boot guixSD and Parabola. I use a macbook 7,1, and I
> am unable to start an X server in guix as my normal user. I can login
> to gnome via my root user, but obviously this is not ideal. I can login
> to a virtual console as my normal user and access Emacs (yeah), but it
> would be nice to be able to start gnome as my normal user. Just today I ran
>
> guix pull; sudo guix pull; guix system reconfigure /etc/gnome-xfce.scm
>
>
> It updated fine. I rebooted and the problem still persists. Parabola
> and guix have seperate / partitions, but they share the same /home.
> I've set up guix to create my normal user (joshua) with a uid of 2000,
> because that is the uid that the user joshua has on parabola.
>
> I'm attaching my config.scm file and some errors that I've found that
> are probably relevant. Any help would be nice.
>
So I’m not going to be of much help, but I want to rule out the obvious:
For me most of the time GNOME starts only on the second log-in attempt
on GuixSD. I assume you have tried logging in multiple times in a row?
Other than that I see no significant differences between my config file
and yours, but I haven’t tried.
> grep EE Xorg.1.log
> [ 47.080] Current Operating System: Linux parabola 4.10.1-gnu-1 #1 SMP PREEMPT Mon Feb 27 17:40:02 UYT 2017 x86_64
> (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
>
Why does your log say Parabola?
Regards,
Florian
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: I can only start an X server in guix as root
2017-03-18 14:50 ` pelzflorian (Florian Pelz)
@ 2017-03-19 21:04 ` Ludovic Courtès
2017-03-30 13:01 ` bug#26158: " Joshua Branson
0 siblings, 1 reply; 4+ messages in thread
From: Ludovic Courtès @ 2017-03-19 21:04 UTC (permalink / raw)
To: pelzflorian (Florian Pelz); +Cc: help-guix
Hi!
"pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de> skribis:
> So I’m not going to be of much help, but I want to rule out the obvious:
> For me most of the time GNOME starts only on the second log-in attempt
> on GuixSD. I assume you have tried logging in multiple times in a row?
That is weird. Does ~/.xsession-errors contain any hints after a failed
attempt?
Also, did you try to reproduce it in a VM as produced by ‘guix system
vm’? If it’s reproducible in a VM, we could start debugging in
parallel. :-)
Thanks,
Ludo’.
^ permalink raw reply [flat|nested] 4+ messages in thread
* bug#26158: I can only start an X server in guix as root
2017-03-19 21:04 ` Ludovic Courtès
@ 2017-03-30 13:01 ` Joshua Branson
0 siblings, 0 replies; 4+ messages in thread
From: Joshua Branson @ 2017-03-30 13:01 UTC (permalink / raw)
To: help-guix@gnu.org, 26158@debbugs.gnu.org
Hello,
I've responded to this email on the guix-bugs emailing list located
here: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=26158
I did try a guix system vm /path/to/config-file.scm; and I could still
not log into guixSD.
I think I might create another guix user. If I can't login as joshua,
perhaps I'll try logging in as "rupert" and see if that works (I'll do
this via editing my config file and running guix system reconfigure).
Thanks,
Joshua
On 03/19/2017 05:04 PM, Ludovic Courtès wrote:
> Hi!
>
> "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de> skribis:
>
>> So I’m not going to be of much help, but I want to rule out the obvious:
>> For me most of the time GNOME starts only on the second log-in attempt
>> on GuixSD. I assume you have tried logging in multiple times in a row?
> That is weird. Does ~/.xsession-errors contain any hints after a failed
> attempt?
>
> Also, did you try to reproduce it in a VM as produced by ‘guix system
> vm’? If it’s reproducible in a VM, we could start debugging in
> parallel. :-)
>
> Thanks,
> Ludo’.
>
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2017-03-30 13:01 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2017-03-18 0:50 I can only start an X server in guix as root Joshua Branson
2017-03-18 14:50 ` pelzflorian (Florian Pelz)
2017-03-19 21:04 ` Ludovic Courtès
2017-03-30 13:01 ` bug#26158: " Joshua Branson
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).