From elcorreo at deshackra.com Thu Apr 3 21:22:48 2014 From: elcorreo at deshackra.com (Jorge Araya Navarro) Date: Thu, 03 Apr 2014 15:22:48 -0600 Subject: [Assist] systemctl --user status Failed to get D-Bus connection: Connection refused Message-ID: <1396560168.3835.0.camel@localhost.localdomain> I'm trying to get running a user instance of systemd, I followed the instructions from Arch Linux wiki ( as read here https://wiki.archlinux.org/index.php/Systemd/User ), and even I check everything that should be checked, activate or enable everything that should be enabled and restart my laptop, it doesn't work. When I run `systemctl --user status` I got `Failed to get D-Bus connection: Connection refused`. Why the connection is refused? I have no idea. As far as I can remember, I never touch DBus configuration. Never. some help? -- Pax et bonum. Jorge Araya Navarro. Dise?ador publicitario, programador Python/C++ y colaborador en Parabola GNU/Linux-libre. -------------- next part -------------- An HTML attachment was scrubbed... URL: From lukeshu at sbcglobal.net Fri Apr 4 01:42:31 2014 From: lukeshu at sbcglobal.net (Luke T. Shumaker) Date: Thu, 03 Apr 2014 21:42:31 -0400 Subject: [Assist] systemctl --user status Failed to get D-Bus connection: Connection refused In-Reply-To: <1396560168.3835.0.camel@localhost.localdomain> References: <1396560168.3835.0.camel@localhost.localdomain> Message-ID: <87ha69x43c.wl%lukeshu@sbcglobal.net> At Thu, 03 Apr 2014 15:22:48 -0600, Jorge Araya Navarro wrote: > I'm trying to get running a user instance of systemd, I followed the > instructions from Arch Linux wiki ( as read here > https://wiki.archlinux.org/index.php/Systemd/User ), and even I check > everything that should be checked, activate or enable everything that > should be enabled and restart my laptop, it doesn't work. > > When I run `systemctl --user status` I got `Failed to get D-Bus > connection: Connection refused`. Why the connection is refused? I have > no idea. As far as I can remember, I never touch DBus configuration. > Never. > > some help? I hope this is the least helpful reply you get. Back in systemd ~202, I was trying to get user instances working on my laptop. I kept hitting issues. Eventually I found a post by Leonart that basically said "yeah, it's weird right now because we haven't really decided how that should work. It's still alpha." I'm not sure if that is still the case in 212. But, my point is that if you are doing everything right, I wouldn't rule out it being an issue with systemd itself. Happy hacking, ~ Luke Shumaker From lukeshu at sbcglobal.net Fri Apr 4 03:27:07 2014 From: lukeshu at sbcglobal.net (Luke T. Shumaker) Date: Thu, 03 Apr 2014 23:27:07 -0400 Subject: [Assist] systemctl --user status Failed to get D-Bus connection: Connection refused In-Reply-To: <1396560168.3835.0.camel@localhost.localdomain> References: <1396560168.3835.0.camel@localhost.localdomain> Message-ID: <8738htn59w.wl%lukeshu@sbcglobal.net> At Thu, 03 Apr 2014 15:22:48 -0600, Jorge Araya Navarro wrote: > I followed the > instructions from Arch Linux wiki ( as read here > https://wiki.archlinux.org/index.php/Systemd/User ), I'm not saying not to read that, there's some good stuff there, but on a scale of "garbage" to "quality documentation", that page is closer to the former. > When I run `systemctl --user status` I got `Failed to get D-Bus > connection: Connection refused`. Why the connection is refused? I have > no idea. As far as I can remember, I never touch DBus configuration. > Never. I believe you are experiencing a bug in systemd where /run/user//systemd/ (or, equivalently, $XDG_RUNTIME_DIR/systemd/ ) is not being created on login. Verify that is the case, then log out and back in until it exists. I've just logged out and in a couple times, and sometimes it is created, sometimes it isn't; with no pattern I've picked up on. Happy hacking, ~ Luke Shumaker From lukeshu at sbcglobal.net Fri Apr 4 04:41:48 2014 From: lukeshu at sbcglobal.net (Luke T. Shumaker) Date: Fri, 04 Apr 2014 00:41:48 -0400 Subject: [Assist] systemctl --user status Failed to get D-Bus connection: Connection refused In-Reply-To: <8738htn59w.wl%lukeshu@sbcglobal.net> References: <1396560168.3835.0.camel@localhost.localdomain> <8738htn59w.wl%lukeshu@sbcglobal.net> Message-ID: <871txd7lkj.wl%lukeshu@sbcglobal.net> At Thu, 03 Apr 2014 23:27:07 -0400, Luke T. Shumaker wrote: > I believe you are experiencing a bug in systemd where > /run/user//systemd/ (or, equivalently, > $XDG_RUNTIME_DIR/systemd/ ) is not being created on login. Specifically, ${XDG_RUNTIME_DIR}/systemd/private . It also creates /notify, but I wasn't sure which one was needed for this, so I just mentioned the directory (when I have it not show up, the whole systemd directory is missing) "private" should be created by systemd's src/core/dbus.c:bus_init_private(), but I imagine the problem actually comes from higher up. Unless I missed something, there are no relevent commits since release v212, no relevent emails on the mailing list, and no relevent bug-reports on bugzilla. If you like, I encourage you to report this bug with systemd. If you don't, I'll report it this weekend after digging in to the cause a bit more. Happy hacking, ~ Luke Shumaker From elcorreo at deshackra.com Fri Apr 4 07:26:35 2014 From: elcorreo at deshackra.com (Jorge Araya Navarro) Date: Fri, 04 Apr 2014 01:26:35 -0600 Subject: [Assist] systemctl --user status Failed to get D-Bus connection: Connection refused In-Reply-To: <8738htn59w.wl%lukeshu@sbcglobal.net> References: <1396560168.3835.0.camel@localhost.localdomain> <8738htn59w.wl%lukeshu@sbcglobal.net> Message-ID: <1396596395.4794.1.camel@localhost.localdomain> Here: <(jorge at abril)---(vie abr 04 01:24:02)> [~][3] $ LC_ALL=C stat /run/user/1000/systemd/ File: '/run/user/1000/systemd/' Size: 60 Blocks: 0 IO Block: 4096 directory Device: 22h/34d Inode: 19142 Links: 2 Access: (0755/drwxr-xr-x) Uid: ( 1000/ jorge) Gid: ( 100/ users) Access: 2014-04-03 15:42:18.933482807 -0600 Modify: 2014-04-03 15:42:19.166818399 -0600 Change: 2014-04-03 15:42:19.166818399 -0600 Birth: - <(jorge at abril)---(vie abr 04 01:24:09)> [~][4] $ LC_ALL=C stat /run/user/1000/systemd/private File: '/run/user/1000/systemd/private' Size: 0 Blocks: 0 IO Block: 4096 socket Device: 22h/34d Inode: 19152 Links: 1 Access: (0755/srwxr-xr-x) Uid: ( 1000/ jorge) Gid: ( 100/ users) Access: 2014-04-03 15:42:19.166818399 -0600 Modify: 2014-04-03 15:42:19.166818399 -0600 Change: 2014-04-03 15:42:19.166818399 -0600 Birth: - <(jorge at abril)---(vie abr 04 01:24:18)> [~][5] $ LC_ALL=C stat ${XDG_RUNTIME_DIR}/systemd/private File: '/run/user/1000/systemd/private' Size: 0 Blocks: 0 IO Block: 4096 socket Device: 22h/34d Inode: 19152 Links: 1 Access: (0755/srwxr-xr-x) Uid: ( 1000/ jorge) Gid: ( 100/ users) Access: 2014-04-03 15:42:19.166818399 -0600 Modify: 2014-04-03 15:42:19.166818399 -0600 Change: 2014-04-03 15:42:19.166818399 -0600 Birth: - <(jorge at abril)---(vie abr 04 01:24:45)> [~][6] $ So far, so good... and so confuse! What could be going wrong here? -- Pax et bonum. Jorge Araya Navarro. Dise?ador publicitario, programador Python/C++ y colaborador en Parabola GNU/Linux-libre. El jue, 03-04-2014 a las 23:27 -0400, Luke T.Shumaker escribi?: > At Thu, 03 Apr 2014 15:22:48 -0600, > Jorge Araya Navarro wrote: > > I followed the > > instructions from Arch Linux wiki ( as read here > > https://wiki.archlinux.org/index.php/Systemd/User ), > > I'm not saying not to read that, there's some good stuff there, but on > a scale of "garbage" to "quality documentation", that page is closer > to the former. Haha, very mean! -------------- next part -------------- An HTML attachment was scrubbed... URL: From lukeshu at sbcglobal.net Fri Apr 4 13:39:34 2014 From: lukeshu at sbcglobal.net (Luke Shumaker) Date: Fri, 04 Apr 2014 09:39:34 -0400 Subject: [Assist] systemctl --user status Failed to get D-Bus connection: Connection refused In-Reply-To: <1396596395.4794.1.camel@localhost.localdomain> References: <1396560168.3835.0.camel@localhost.localdomain> <8738htn59w.wl%lukeshu@sbcglobal.net> <1396596395.4794.1.camel@localhost.localdomain> Message-ID: <878urlw6w9.wl%lukeshu@sbcglobal.net> At Fri, 04 Apr 2014 01:26:35 -0600, Jorge Araya Navarro wrote: > Here: > <(jorge at abril)---(vie abr 04 01:24:02)> > [~][3] $ LC_ALL=C stat /run/user/1000/systemd/ > ... > > <(jorge at abril)---(vie abr 04 01:24:09)> > [~][4] $ LC_ALL=C stat /run/user/1000/systemd/private > ... > > So far, so good... and so confuse! What could be going wrong here? Did you also check that `systemctl --user status` was still giving you the D-Bus error message? Also, if you had run `systemctl --user exit`, and haven't logged out since, it is still dissabled. To clarify, when I say "log out", I mean log out of all user sessions. Verify that this was the case when you log back in by running `loginctl list-sessions`, and verifying that there is only one current session for your user. It is possible that a background process is keeping an old session alive. For example, I discovered that if I started X, then lxpanel would start menu-cached in the background, which would keep running and cause that session to persist even after I logged out. > El jue, 03-04-2014 a las 23:27 -0400, Luke T.Shumaker escribi?: > > At Thu, 03 Apr 2014 15:22:48 -0600, > > Jorge Araya Navarro wrote: > > > I followed the > > > instructions from Arch Linux wiki ( as read here > > > https://wiki.archlinux.org/index.php/Systemd/User ), > > > > I'm not saying not to read that, there's some good stuff there, but on > > a scale of "garbage" to "quality documentation", that page is closer > > to the former. > > Haha, very mean! To be fair, it's because it's all changing so quickly. There's "Setup" [for < 206], and "Setup since systemd 206"; BOTH of which contain information that is not true in systemd 212. It's just hard to keep up, and update the entire page. Basically, everything it says about setting up D-Bus is false. dbus.service/dbus.socket are now obsolete; this happens by default now. The DBUS_SESSION_BUS_ADDRESS is now $XDG_RUNTIME_DIR/systemd/private instead of $XDG_RUNTIME_DIR/bus or $XDG_RUNTIME_DIR/dbus/user_bus_socket (both of which are mentioned in the "since 206" section). That said, the DBUS_SESSION_BUS_ADDRESS environment variable should probably not be set. With no value, everything should just find the correct address. The systemd people are working to make this all simpler and not require these extra things, but sometimes that means yesterday's kludges break. The variable is is set by /etc/X11/xinit/xinitrc.d/30-dbus, but that doesn't seem to mess anything up on my box. If you are using a graphical login, the XDM or DE's session manager may be messing with D-Bus and actually mangaging to mess it up. Try logging into a TTY when debugging this. Happy hacking, ~ Luke Shumaker From elcorreo at deshackra.com Fri Apr 4 19:04:39 2014 From: elcorreo at deshackra.com (Jorge Araya Navarro) Date: Fri, 04 Apr 2014 13:04:39 -0600 Subject: [Assist] systemctl --user status Failed to get D-Bus connection: Connection refused In-Reply-To: <878urlw6w9.wl%lukeshu@sbcglobal.net> References: <1396560168.3835.0.camel@localhost.localdomain> <8738htn59w.wl%lukeshu@sbcglobal.net> <1396596395.4794.1.camel@localhost.localdomain> <878urlw6w9.wl%lukeshu@sbcglobal.net> Message-ID: <1396638279.8001.2.camel@localhost.localdomain> The directory and the socket are created, however both `systemctl --user status` and `systemctl --user exit` throws the exact same error. I'll try again log-in from a TTY later! -- Pax et bonum. Jorge Araya Navarro. Dise?ador publicitario, programador Python/C++ y colaborador en Parabola GNU/Linux-libre. El vie, 04-04-2014 a las 09:39 -0400, Luke Shumaker escribi?: > At Fri, 04 Apr 2014 01:26:35 -0600, > Jorge Araya Navarro wrote: > > Here: > > <(jorge at abril)---(vie abr 04 01:24:02)> > > [~][3] $ LC_ALL=C stat /run/user/1000/systemd/ > > ... > > > > <(jorge at abril)---(vie abr 04 01:24:09)> > > [~][4] $ LC_ALL=C stat /run/user/1000/systemd/private > > ... > > > > So far, so good... and so confuse! What could be going wrong here? > > Did you also check that `systemctl --user status` was still giving you > the D-Bus error message? Also, if you had run `systemctl --user > exit`, and haven't logged out since, it is still dissabled. > > To clarify, when I say "log out", I mean log out of all user sessions. > Verify that this was the case when you log back in by running > `loginctl list-sessions`, and verifying that there is only one current > session for your user. It is possible that a background process is > keeping an old session alive. For example, I discovered that if I > started X, then lxpanel would start menu-cached in the background, > which would keep running and cause that session to persist even after > I logged out. > > > El jue, 03-04-2014 a las 23:27 -0400, Luke T.Shumaker escribi?: > > > At Thu, 03 Apr 2014 15:22:48 -0600, > > > Jorge Araya Navarro wrote: > > > > I followed the > > > > instructions from Arch Linux wiki ( as read here > > > > https://wiki.archlinux.org/index.php/Systemd/User ), > > > > > > I'm not saying not to read that, there's some good stuff there, but on > > > a scale of "garbage" to "quality documentation", that page is closer > > > to the former. > > > > Haha, very mean! > > To be fair, it's because it's all changing so quickly. There's > "Setup" [for < 206], and "Setup since systemd 206"; BOTH of which > contain information that is not true in systemd 212. It's just hard > to keep up, and update the entire page. > > Basically, everything it says about setting up D-Bus is false. > dbus.service/dbus.socket are now obsolete; this happens by default > now. The DBUS_SESSION_BUS_ADDRESS is now > $XDG_RUNTIME_DIR/systemd/private instead of $XDG_RUNTIME_DIR/bus or > $XDG_RUNTIME_DIR/dbus/user_bus_socket (both of which are mentioned in > the "since 206" section). > > That said, the DBUS_SESSION_BUS_ADDRESS environment variable should > probably not be set. With no value, everything should just find the > correct address. The systemd people are working to make this all > simpler and not require these extra things, but sometimes that means > yesterday's kludges break. > > The variable is is set by /etc/X11/xinit/xinitrc.d/30-dbus, but that > doesn't seem to mess anything up on my box. If you are using a > graphical login, the XDM or DE's session manager may be messing with > D-Bus and actually mangaging to mess it up. Try logging into a TTY > when debugging this. > > Happy hacking, > ~ Luke Shumaker > _______________________________________________ > Assist mailing list > Assist at lists.parabolagnulinux.org > https://lists.parabolagnulinux.org/mailman/listinfo/assist -------------- next part -------------- An HTML attachment was scrubbed... URL: From elcorreo at deshackra.com Wed Apr 9 04:39:02 2014 From: elcorreo at deshackra.com (Jorge Araya Navarro) Date: Tue, 08 Apr 2014 22:39:02 -0600 Subject: [Assist] systemctl --user status Failed to get D-Bus connection: Connection refused In-Reply-To: <878urlw6w9.wl%lukeshu@sbcglobal.net> References: <1396560168.3835.0.camel@localhost.localdomain> <8738htn59w.wl%lukeshu@sbcglobal.net> <1396596395.4794.1.camel@localhost.localdomain> <878urlw6w9.wl%lukeshu@sbcglobal.net> Message-ID: <1397018342.8365.1.camel@localhost.localdomain> I don't know what happen, but I like it! <(jorge at abril)---(mar abr 08 22:36:38)> [~][1] $ ps axxx | grep user 7395 ? Ss 0:00 /usr/lib/systemd/systemd --user 7533 ? Sl 0:00 /usr/lib/gvfs//gvfsd-fuse /run/user/1000/gvfs -f -o big_writes 8363 pts/1 R+ 0:00 grep --color=auto user <(jorge at abril)---(mar abr 08 22:36:44)> [~][2] $ syste systemctl systemd-coredumpctl systemd-nspawn systemd-analyze systemd-delta systemd-run systemd-ask-password systemd-detect-virt systemd-stdio-bridge systemd-cat systemd-inhibit systemd-tmpfiles systemd-cgls systemd-machine-id-setup systemd-tty-ask-password-agent systemd-cgtop systemd-notify systemsettings <(jorge at abril)---(mar abr 08 22:36:44)> [~][2] $ systemctl --user status ? abril State: running Jobs: 0 queued Failed: 0 units Since: mar 2014-04-08 10:12:01 CST; 12h ago CGroup: /user.slice/user-1000.slice/user at 1000.service ??7395 /usr/lib/systemd/systemd --user ??7407 (sd-pam) <(jorge at abril)---(mar abr 08 22:37:05)> [~][3] $ <(jorge at abril)---(mar abr 08 22:38:11)> [~][4] $ systemctl --version systemd 212 +PAM -AUDIT -SELINUX -IMA -SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ +SECCOMP -APPARMOR <(jorge at abril)---(mar abr 08 22:38:15)> [~][5] $ :D -- Pax et bonum. Jorge Araya Navarro. Dise?ador publicitario, programador Python/C++ y colaborador en Parabola GNU/Linux-libre. El vie, 04-04-2014 a las 09:39 -0400, Luke Shumaker escribi?: > At Fri, 04 Apr 2014 01:26:35 -0600, > Jorge Araya Navarro wrote: > > Here: > > <(jorge at abril)---(vie abr 04 01:24:02)> > > [~][3] $ LC_ALL=C stat /run/user/1000/systemd/ > > ... > > > > <(jorge at abril)---(vie abr 04 01:24:09)> > > [~][4] $ LC_ALL=C stat /run/user/1000/systemd/private > > ... > > > > So far, so good... and so confuse! What could be going wrong here? > > Did you also check that `systemctl --user status` was still giving you > the D-Bus error message? Also, if you had run `systemctl --user > exit`, and haven't logged out since, it is still dissabled. > > To clarify, when I say "log out", I mean log out of all user sessions. > Verify that this was the case when you log back in by running > `loginctl list-sessions`, and verifying that there is only one current > session for your user. It is possible that a background process is > keeping an old session alive. For example, I discovered that if I > started X, then lxpanel would start menu-cached in the background, > which would keep running and cause that session to persist even after > I logged out. > > > El jue, 03-04-2014 a las 23:27 -0400, Luke T.Shumaker escribi?: > > > At Thu, 03 Apr 2014 15:22:48 -0600, > > > Jorge Araya Navarro wrote: > > > > I followed the > > > > instructions from Arch Linux wiki ( as read here > > > > https://wiki.archlinux.org/index.php/Systemd/User ), > > > > > > I'm not saying not to read that, there's some good stuff there, but on > > > a scale of "garbage" to "quality documentation", that page is closer > > > to the former. > > > > Haha, very mean! > > To be fair, it's because it's all changing so quickly. There's > "Setup" [for < 206], and "Setup since systemd 206"; BOTH of which > contain information that is not true in systemd 212. It's just hard > to keep up, and update the entire page. > > Basically, everything it says about setting up D-Bus is false. > dbus.service/dbus.socket are now obsolete; this happens by default > now. The DBUS_SESSION_BUS_ADDRESS is now > $XDG_RUNTIME_DIR/systemd/private instead of $XDG_RUNTIME_DIR/bus or > $XDG_RUNTIME_DIR/dbus/user_bus_socket (both of which are mentioned in > the "since 206" section). > > That said, the DBUS_SESSION_BUS_ADDRESS environment variable should > probably not be set. With no value, everything should just find the > correct address. The systemd people are working to make this all > simpler and not require these extra things, but sometimes that means > yesterday's kludges break. > > The variable is is set by /etc/X11/xinit/xinitrc.d/30-dbus, but that > doesn't seem to mess anything up on my box. If you are using a > graphical login, the XDM or DE's session manager may be messing with > D-Bus and actually mangaging to mess it up. Try logging into a TTY > when debugging this. > > Happy hacking, > ~ Luke Shumaker > _______________________________________________ > Assist mailing list > Assist at lists.parabolagnulinux.org > https://lists.parabolagnulinux.org/mailman/listinfo/assist -------------- next part -------------- An HTML attachment was scrubbed... URL: From roman at mailoo.org Tue Apr 22 08:27:42 2014 From: roman at mailoo.org (=?ISO-8859-1?Q?Rom=E1n?=) Date: Tue, 22 Apr 2014 10:27:42 +0200 Subject: [Assist] Install problem. Message-ID: <8fd12f35-6666-4fb4-aaaf-82bbf4494e66@email.android.com> Hi everybody. I am trying to install this great libre-distro but I get this error: error: parabola-keyring: signature from Andre Silva is unknown trust when I executed pacman -Sy parabola-keyring How can I do to fix this problem? Thanks. Regards. Rom?n. -- Enviado desde mi tel?fono con K-9 Mail. ------------ pr?xima parte ------------ Se ha borrado un adjunto en formato HTML... URL: From nicolasfloquet59 at gmail.com Thu Apr 24 15:21:05 2014 From: nicolasfloquet59 at gmail.com (nicolasfloquet59 at gmail.com) Date: Thu, 24 Apr 2014 17:21:05 +0200 Subject: [Assist] Install problem. In-Reply-To: <8fd12f35-6666-4fb4-aaaf-82bbf4494e66@email.android.com> (=?utf-8?Q?=22Rom=C3=A1n=22's?= message of "Tue, 22 Apr 2014 10:27:42 +0200") References: <8fd12f35-6666-4fb4-aaaf-82bbf4494e66@email.android.com> Message-ID: <87oazq92ji.fsf@biopteeepc.i-did-not-set--mail-host-address--so-tickle-me> Rom?n writes: > Hi everybody. > > I am trying to install this great libre-distro but I get this error: > > error: parabola-keyring: signature from Andre Silva is unknown trust > > when I executed pacman -Sy parabola-keyring > > How can I do to fix this problem? > > Thanks. > > Regards. > Rom?n. Hi Roman, I don't know myself how to solve your problem. Have you tried to question in the channel #parabola on the freenode IRC server ? (Actually, I have exactly the same problem what I have avoided according to a manipulation that I think it's bad. LOL, so I can't recommand it. ^_^) So,try IRC. ^^ Regards, -- Nicolas Floquet 5, impasse du bois 61450 La Ferri?re-aux-?tangs, Normandie, France 06 32 93 03 51 Mail r?dig? avec des logiciels libres (GNU/Linux et Emacs). From moritz at klammler.eu Fri Apr 25 09:07:31 2014 From: moritz at klammler.eu (Moritz Klammler) Date: Fri, 25 Apr 2014 11:07:31 +0200 Subject: [Assist] Install problem. In-Reply-To: <8fd12f35-6666-4fb4-aaaf-82bbf4494e66@email.android.com> Message-ID: <891twlvkto.fsf@klammler.eu> It has been a while since I have installed it myself but back then, I had to run # pacman -Sy parabola-keyring # pacman -Sy parabola-keyring (yes, twice!) right after booting into the live system and then again pass the package to pacstrap # pacstrap /mnt base [...] parabola-keyring I have figured this out mostly by trial and error and cannot provide a good explanation why it works. Rom?n writes: > Hi everybody. > I am trying to install this great libre-distro but I get this error: > error: parabola-keyring: signature from Andre Silva is unknown trust > when I executed pacman -Sy parabola-keyring > How can I do to fix this problem? > Thanks. > Regards. > Rom?n. -- OpenPGP: Public Key: http://openpgp.klammler.eu Fingerprint: 80C1 EC79 B554 3D84 0A35 A728 7057 B288 CE61 2235 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: not available URL: From contact at gnuvideo.ro Sat Apr 26 11:06:43 2014 From: contact at gnuvideo.ro (Nicu B.) Date: Sat, 26 Apr 2014 14:06:43 +0300 Subject: [Assist] Grub Installation Message-ID: <07a90e624200783cea39ccd5817310b0@gnuvideo.ro> Hello, I'm new to Parabola and I have a question about GRUB. Should I install grub-legacy package or grub-bios ? Thanks, -- www.gnuvideo.ro www.jurnal.gnuvideo.ro contact at gnuvideo.ro From mimex at fipasoft.com.mx Sat Apr 26 16:40:48 2014 From: mimex at fipasoft.com.mx (Miguel Trujillo) Date: Sat, 26 Apr 2014 11:40:48 -0500 Subject: [Assist] Grub Installation In-Reply-To: <07a90e624200783cea39ccd5817310b0@gnuvideo.ro> References: <07a90e624200783cea39ccd5817310b0@gnuvideo.ro> Message-ID: <535BE190.6000101@fipasoft.com.mx> On 26/04/14 06:06, Nicu B. wrote: > Hello, > > I'm new to Parabola and I have a question about GRUB. Should I install > grub-legacy package or grub-bios ? > > Thanks, > The last version of 'grub' package works fine. I think you don't need 'grub-legacy'. -- Miguel mimex at fipasoft.com.mx From elcorreo at deshackra.com Tue Apr 29 04:29:21 2014 From: elcorreo at deshackra.com (Jorge Araya Navarro) Date: Mon, 28 Apr 2014 22:29:21 -0600 Subject: [Assist] systemctl --user status Failed to get D-Bus connection: Connection refused In-Reply-To: <878urlw6w9.wl%lukeshu@sbcglobal.net> References: <1396560168.3835.0.camel@localhost.localdomain> <8738htn59w.wl%lukeshu@sbcglobal.net> <1396596395.4794.1.camel@localhost.localdomain> <878urlw6w9.wl%lukeshu@sbcglobal.net> Message-ID: <1398745761.19361.4.camel@localhost.localdomain> El vie, 04-04-2014 a las 09:39 -0400, Luke Shumaker escribi?: > At Fri, 04 Apr 2014 01:26:35 -0600, > Jorge Araya Navarro wrote: > > Here: > > <(jorge at abril)---(vie abr 04 01:24:02)> > > [~][3] $ LC_ALL=C stat /run/user/1000/systemd/ > > ... > > > > <(jorge at abril)---(vie abr 04 01:24:09)> > > [~][4] $ LC_ALL=C stat /run/user/1000/systemd/private > > ... > > > > So far, so good... and so confuse! What could be going wrong here? > > Did you also check that `systemctl --user status` was still giving you > the D-Bus error message? Also, if you had run `systemctl --user > exit`, and haven't logged out since, it is still dissabled. > > To clarify, when I say "log out", I mean log out of all user sessions. > Verify that this was the case when you log back in by running > `loginctl list-sessions`, and verifying that there is only one current > session for your user. It is possible that a background process is > keeping an old session alive. For example, I discovered that if I > started X, then lxpanel would start menu-cached in the background, > which would keep running and cause that session to persist even after > I logged out. > > > El jue, 03-04-2014 a las 23:27 -0400, Luke T.Shumaker escribi?: > > > At Thu, 03 Apr 2014 15:22:48 -0600, > > > Jorge Araya Navarro wrote: > > > > I followed the > > > > instructions from Arch Linux wiki ( as read here > > > > https://wiki.archlinux.org/index.php/Systemd/User ), > > > > > > I'm not saying not to read that, there's some good stuff there, but on > > > a scale of "garbage" to "quality documentation", that page is closer > > > to the former. > > > > Haha, very mean! > > To be fair, it's because it's all changing so quickly. There's > "Setup" [for < 206], and "Setup since systemd 206"; BOTH of which > contain information that is not true in systemd 212. It's just hard > to keep up, and update the entire page. > > Basically, everything it says about setting up D-Bus is false. > dbus.service/dbus.socket are now obsolete; this happens by default > now. The DBUS_SESSION_BUS_ADDRESS is now > $XDG_RUNTIME_DIR/systemd/private instead of $XDG_RUNTIME_DIR/bus or > $XDG_RUNTIME_DIR/dbus/user_bus_socket (both of which are mentioned in > the "since 206" section). > > That said, the DBUS_SESSION_BUS_ADDRESS environment variable should > probably not be set. With no value, everything should just find the > correct address. The systemd people are working to make this all > simpler and not require these extra things, but sometimes that means > yesterday's kludges break. > > The variable is is set by /etc/X11/xinit/xinitrc.d/30-dbus, but that > doesn't seem to mess anything up on my box. If you are using a > graphical login, the XDM or DE's session manager may be messing with > D-Bus and actually mangaging to mess it up. Try logging into a TTY > when debugging this. > > Happy hacking, > ~ Luke Shumaker > _______________________________________________ > Assist mailing list > Assist at lists.parabolagnulinux.org > https://lists.parabolagnulinux.org/mailman/listinfo/assist Something that I cannot get working is the activation of the services after I login into my session. I did `systemctl --user enable emacs`, the next morning I turn on my computer and then login into my session but emacs do not start! <(jorge at abril)---(lun abr 28 22:27:00)> [~][4] $ systemctl --user status ? abril State: running Jobs: 0 queued Failed: 0 units Since: lun 2014-04-28 09:33:26 CST; 12h ago CGroup: /user.slice/user-1000.slice/user at 1000.service ??1769 /usr/lib/systemd/systemd --user ??1781 (sd-pam) <(jorge at abril)---(lun abr 28 22:27:11)> [~][6] $ systemctl --user status emacs ? emacs.service - Emacs: the extensible, self-documenting text editor Loaded: loaded (/home/jorge/.config/systemd/user/emacs.service; enabled) Active: inactive (dead) <(jorge at abril)---(lun abr 28 22:27:30)> [~][7] $ What am I doing wrong? -- Pax et bonum. Jorge Araya Navarro. Dise?ador publicitario, programador Python/C++ y colaborador en Parabola GNU/Linux-libre. -------------- next part -------------- An HTML attachment was scrubbed... URL: From GNUtoo at no-log.org Tue Apr 29 20:51:12 2014 From: GNUtoo at no-log.org (Denis 'GNUtoo' Carikli) Date: Tue, 29 Apr 2014 22:51:12 +0200 Subject: [Assist] Grub Installation In-Reply-To: <535BE190.6000101@fipasoft.com.mx> References: <07a90e624200783cea39ccd5817310b0@gnuvideo.ro> <535BE190.6000101@fipasoft.com.mx> Message-ID: <20140429225112.06b49dbf@X60> On Sat, 26 Apr 2014 11:40:48 -0500 Miguel Trujillo wrote: > On 26/04/14 06:06, Nicu B. wrote: > > I'm new to Parabola and I have a question about GRUB. Should I > > install grub-legacy package or grub-bios ? [...] > The last version of 'grub' package works fine. I think you don't need > 'grub-legacy'. The confusion was probably caused by the wiki which advised to install grub-bios or grub-efi on its installation page, and the fact that none of theses were present in the repositories. I updated that part on the installation guide last weekend. I often install parabola for virtual machines, NFS usage, or specific needs(like ultra fast booting). Denis. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: not available URL: From csanyipal at gmail.com Wed Apr 30 16:46:34 2014 From: csanyipal at gmail.com (=?UTF-8?B?Q3PDoW55aSBQw6Fs?=) Date: Wed, 30 Apr 2014 18:46:34 +0200 Subject: [Assist] Original Oracle/Sun Java on ParabolaGNUlinux? Message-ID: On the SweetHome3D forum in the thread: http://www.sweethome3d.com/support/forum/viewthread_thread,4976 there I get an advice that I must uninstall all Java versions and can only have the original Oracle/Sun Java installed. "For many flavours of Linux goes that you should un-install ALL Java versions and only have the original Oracle/Sun Java installed." This is not the ParabolaGNU way, right? Is the Oracle/Sun Java free software? Can I install it on my ParabolaGNUlinux system so my system remain totally free? -- Regards from Pal -------------- next part -------------- An HTML attachment was scrubbed... URL: