Re: [arch-general] Thinkpad 770 - Init exists but couldn't execute it (error -26)
On mié, 2016-04-13 at 22:22 -0400, Serge Hooge wrote: > Just an update, I got the RAM changed with the brand new sticks, but > the problem persisted. > > Seems to be an issue with systemd-based distros, because I managed to > get Devuan, FreeBSD and Slackware booted, while modern Debian crashed > on > me with the same result as Arch. > Serge, your problem got me thinking and I remembered a similar situation I had many years ago with some Dell OptiPlex boxes that wouldn't boot Linux even with a gun to their PSUs. The solution was to add the 'acpi_os_name="Microsoft Windows"' boot parameter to the kernel boot command line. See https://www.kernel.org/doc/Documentation/kernel- parameters.txt for all the acpi tricks you may try with yout laptop. -- Pedro A. López-Valencia http://about.me/palopezv Recession is when your neighbor loses his job. Depression is when you lose yours. -Ronald Reagan
Re: [arch-general] Archlinux banana pi probem kodi
On dom, 2016-03-27 at 15:44 +0200, Maykel Franco wrote: > Hi, I followed this guide install archlinux in banana pi and works > fine: > > https://wiki.archlinux.org/index.php/Banana_Pi > > > [[snip] > Can I help me please? Err... No. As <https://wiki.archlinux.org/index.php/Category:ARM_architecture> clearly states: Note: * Support for the ARM architecture is provided by Arch Linux ARM, which is a different project than Arch Linux. Seek support on the Arch Linux ARM forums. * The ARM abbreviation also refers to Arch Rollback Machine, which however provides packages for the Arch Linux official architectures i686 and x86_64. (Links removed, please read the above link for full reference). -- Pedro A. López-Valencia http://about.me/palopezv Recession is when your neighbor loses his job. Depression is when you lose yours. -Ronald Reagan
Re: [arch-general] Cannot use monitor in 1920x1080 anymore
On 04/04/15 14:59, Patrick Burroughs (Celti) wrote:
On Sat, 04 Apr 2015 11:29:26 -0500 Pedro A. López-Valencia
vorb...@gmail.com wrote:
Hmmm... Martin, if you still have a Xorg.log it means you have a
really old installation, or you installed syslog-ng and integrated it
with journalctl, something that is not standard anymore. Heck,
OpenSUSE just removed it of Tumbleweed, it's a sign of the times.
That would only be true if systemd launched Xorg directly. Xorg writes
its log file on its own, not through syslog and not to the journal; I
can tell you that on my fully up-to-date system, at least, Xorg writes
to /var/log/Xorg.X.log (or to ~/.local/share/xorg/Xorg.X.log for
non-root Xorg).
You mean the contents of the xorg-server.install file?
post_upgrade() {
if (( $(vercmp $2 1.16.0-3) 0 )); then
post_install
fi
}
post_install() {
cat MSG
xorg-server has now the ability to run without root rights with
the help of systemd-logind. xserver will fail to run if not
launched
from the same virtual terminal as was used to log in.
Without root rights, log files will be in ~/.local/share/xorg/
directory.
Old behavior can be restored through Xorg.wrap config file.
See Xorg.wrap man page (man xorg.wrap).
MSG
}
xorg-server.install (END)
That was true for versions under 1.16.0-3 as evidenced by the version
comparison, but it is not true anymore, Xserver 1.17 dumps its logs to
syslog. And syslog is trapped by journalctl.
--
Pedro A. López-Valencia
http://about.me/palopezv
Re: [arch-general] Cannot use monitor in 1920x1080 anymore
On 04/04/15 14:59, Patrick Burroughs (Celti) wrote: That would only be true if systemd launched Xorg directly. Xorg writes its log file on its own, not through syslog and not to the journal; I can tell you that on my fully up-to-date system, at least, Xorg writes to /var/log/Xorg.X.log (or to ~/.local/share/xorg/Xorg.X.log for non-root Xorg). I did some testing, and found we both are right, although what I said isn't. If you launch the xserver manually or with a display manager that is not well integrated with systemd, you'll get your text logs. If it is well integrated, namely GDM, everything will go into journalctl. -- Pedro A. López-Valencia http://about.me/palopezv
Re: [arch-general] Cannot use monitor in 1920x1080 anymore
On 30/03/15 06:24, Martin S. Weber wrote:
On 2015-03-30 13:08:11, Alfredo Palhares wrote:
Any ideas how can I debug this problem further ?
Have a look at X's logfile, /var/log/Xorg.log. There should be messages that
say the modes
are being removed, and why (not enough Vram, some parameter out of range,
etc.). It's likely
warning or errors, so it should be among the output of egrep '\([WE]{2}\)'
Xorg.0.log.
Good luck,
-Martin
Hmmm... Martin, if you still have a Xorg.log it means you have a really
old installation, or you installed syslog-ng and integrated it with
journalctl, something that is not standard anymore. Heck, OpenSUSE just
removed it of Tumbleweed, it's a sign of the times.
Alfredo, as Arch uses systemd/journalctl, you need to use the command:
journalctl -b0 _EXE=/usr/lib/xorg-server/Xorg
If you are not in the systemd-journal group, you may need to run the
command in a root shell or with sudo.
--
Pedro A. López-Valencia
http://about.me/palopezv
Re: [arch-general] Linphone-3.8.0
El 14/03/2015 a las 12:03 a. m., Mark Lee escribió: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 While this may not be the proper way of submitting packages, linphone is out of date and repackaging it does require some fiddling. The major change is the use of bzrtp for zrtp encryption now. I've attached the PKGBUILDs I used to build linphone-3.8.0 so the maintainers can avoid some duplication of effort if they'd like. Note, I enabled GLX for linphone video calls in my version of mediastreamer. Regards, Mark Hi Mark, The proper way to propose a change in a PKGBUILD for a package in the official repositories is to file a bug report in Flyspray. In the particular case of a community package, there is a whole section dedicated to it (make sure to select that when filing the report). One of the bug wranglers will assign the bug to the proper person. BTW, considering the nature of the bug: new version with who knows what security bug fixes and new dependencies, I'd report it as high or even critical; but that's just me. :-) P.
Re: [arch-general] Apache PID File not readable
El jul 30, 2013 2:10 AM, Stefan Tatschner stefan.tatsch...@gmail.com escribió: My first answer was rejected because I messed up the conversation history. Here is a new try. 2013/7/29 Jameson imntr...@gmail.com: What does cat /usr/lib/tmpfiles.d/apache.conf return? stefan@archvm ~ $ sudo cat /usr/lib/tmpfiles.d/apache.conf d /run/httpd 0755 root root - That seems to be the problem... Override it. Copy it to /etc/tempfiles.d/ and edit it to fulfil your requirements.
Re: [arch-general] CLI diffing tool other than Vim?
IMnsHO, teach this person to use the tools already available: both nano, diffutils and less are part of base. Teach person to use diff -u combined with less and to excersise some judgement about the difference between the working copies and the new files. Most of the time it is a matter of jotting down a couple of lines in a piece of paper (anathema) and edit the already working file to add a couple of lines or change a couple of settings to new defaults. Make sure to emphasize the use of nano -w and you won't have broken lines in the config files. On Tue, Jul 30, 2013 at 3:43 AM, Paul Gideon Dann pdgid...@gmail.comwrote: Hi guys, I run a couple of Arch servers, and I'm trying to teach someone how to go about maintaining it (for when I'm not around). The difficulty is that when it comes to package updates that require merging .pacnew files, I always use Vim to merge changes. That's quite a steep learning curve to impose on someone who's not all that familiar with a UNIX environment yet. Does anyone know of any good simple(ish) alternative for merging files over SSH? Paul -- http://about.me/palopezv
Re: [arch-general] CLI diffing tool other than Vim?
On Tue, Jul 30, 2013 at 3:09 PM, Daniel Micay danielmi...@gmail.com wrote: On Tue, Jul 30, 2013 at 3:54 PM, P. A. palop...@gmail.com wrote: On Tue, 2013-07-30 at 20:05 +0200, Lukas Jirkovsky wrote: On 30 July 2013 16:33, Pedro Alejandro López-Valencia palop...@gmail.com wrote: IMnsHO, teach this person to use the tools already available: both nano, diffutils and less are part of base. Teach person to use diff -u ... The only diff tool comparable to vimdiff that comes into my mind is emacs diff mode. You are correct, but both vimdiff and emacs diff mode are sophisticated crutches. They're not crutches, they offer an elegant presentation of the differences between the files, and you can merge the changes one-by-one without losing context. It only takes a few minutes to learn, and you'll be happy you did. Matter of opinion. I value learning from first principles. From that point of view: merging graphical tools are crutches if you don't have the foggiest idea of what is actually going on underneath. If you arrived at a later stage of the computer OS evolution game, graphical tools are what you know and that's the hammer you use to hit all nails. My hammer is vi, btw. Not vim; plain, old fashioned vi. You should learn the basic tools to be able to understand the sophisticated ones later and make good use of them. That's absolutely untrue, there's no secret knowledge you'll gain from torturing yourself with an awful tool. It's only useful for generating patches, not merging files. See my answer above. Using CLI UNIX tools is alien to a person who is used to graphical tools. That doesn't mean they are actually awful, only alien. -- http://about.me/palopezv
Re: [arch-general] CLI diffing tool other than Vim?
On Tue, Jul 30, 2013 at 4:50 PM, Daniel Micay danielmi...@gmail.com wrote: There's absolutely no part of the merging process `vimdiff` is hiding from you. You're enamoured with doing tedious, repetitive work but most of us would rather invest a few minutes in learning a more powerful tool or writing a bit of code than wasting our time. And you are enamoured with trying desperately to prove random, unknown people in the internet that you are right, because you have being given the divine right to be always correct as dispensed to you by God. Child, I stopped doing that several decades ago. You win by default. -- http://about.me/palopezv
Re: [arch-general] Kernel bug #60539
On Tue, 2013-07-30 at 22:49 +0300, Josh Liberty wrote: Hi people, I've just had to downgrade my kernel back to 3.9.9 because of this bug: https://bugzilla.kernel.org/show_bug.cgi?id=60530 Does anyone know when one may expect the fix to arrive at the stable kernel builds? - Josh The fix mentioned in bugzilla is in the 3.10.3 changelog[1]. Why don't you give it a try? [1] https://www.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.10.3 Commit f8ee0e2e9db4d11d3b6593d9e2fba464caa0ff0c
Re: [arch-general] Apache PID File not readable
On Mon, Jul 29, 2013 at 12:15 PM, Jameson imntr...@gmail.com wrote: On Sun, Jul 28, 2013 at 8:03 AM, Stefan Tatschner stefan.tatsch...@gmail.com wrote: I always get this message after restarting apache via systemctl: PID file /run/httpd/httpd.pid not readable (yet?) after start. What does cat /usr/lib/tmpfiles.d/apache.conf return? There lies Stefan's problem. It creates the directory as root:root. And this can be a bug or not a bug depending on your take: a.) A bug: The default apache config uses user and group http but the install script doesn't create them!!! And the tmpfile config should user http as user and group for the pid directory. b.) Not a bug. Those are software defaults, you should make sure everything is configured with tight security and no default values will help you there. Furthermore, there is already a nobody user and group defined, use that. So, pick you battle and file a bug, or not. :-) -- http://about.me/palopezv
Re: [arch-general] XFCE broken with Gnome 3.8?
On Tue, Apr 23, 2013 at 12:01 AM, David Rosenstrauch dar...@darose.netwrote: Apparently when I whack my XFCE session cache file (~/.cache/sessions/xfce4-**session-daroselin:0) the problem goes away and I can start up XFCE no problem. But as soon as I save the session, creating a new session cache file, XFCE starts to crap out at startup. Instead of saving a session, use the XDG autostart directory ($HOME/.config/ autostart). Copy the .desktop files from /usr/share/applications, log out and log in again. That should work better. -- Only my skepticism keeps me from being an atheist. —Voltaire http://about.me/palopezv
