2015-02-02 18:27 GMT+01:00 Ralf Mardorf :
> Most likely it's a user issue,
I confess I did many times system upgrade without taking into account
the advice given here:
https://wiki.archlinux.org/index.php/General_recommendations
it is imperative to keep up to date with changes in Arch Linux tha
On Mon, 2 Feb 2015 19:27:57 +0100
Csányi Pál wrote:
> 2015-02-02 18:27 GMT+01:00 Ralf Mardorf :
> > On Mon, 2 Feb 2015 17:29:25 +0100, Csányi Pál wrote:
> >> So I can tell that the RAM is all right on this desktop PC box, right?
> >
> > Most likely the main memory is _not_ defect. However, when p
2015-02-02 18:27 GMT+01:00 Ralf Mardorf :
> On Mon, 2 Feb 2015 17:29:25 +0100, Csányi Pál wrote:
>> So I can tell that the RAM is all right on this desktop PC box, right?
>
> Most likely the main memory is _not_ defect. However, when passing the
> memtest it's without guarantee that the RAM is ok a
On Mon, 2 Feb 2015 17:29:25 +0100, Csányi Pál wrote:
> So I can tell that the RAM is all right on this desktop PC box, right?
Most likely the main memory is _not_ defect. However, when passing the
memtest it's without guarantee that the RAM is ok and if there would
have been errors, it also wouldn
2015-02-01 17:42 GMT+01:00 Marcel Kleinfeller :
> Just do two or three passes that should be enough.
> Am 01.02.2015 um 13:48 schrieb Csányi Pál:
>
>> 2015-02-01 13:42 GMT+01:00 Guus Snijders :
>>>
>>> Op 1 feb. 2015 12:41 schreef "Csányi Pál" het
>>> volgende:
>>>
2015-01-31 23:12 GMT+01:00
Just do two or three passes that should be enough.
Am 01.02.2015 um 13:48 schrieb Csányi Pál:
2015-02-01 13:42 GMT+01:00 Guus Snijders :
Op 1 feb. 2015 12:41 schreef "Csányi Pál" het
volgende:
2015-01-31 23:12 GMT+01:00 Guus Snijders :
2015-01-31 21:20 GMT+01:00 Christian Demsar :
[...]
At
2015-02-01 13:42 GMT+01:00 Guus Snijders :
> Op 1 feb. 2015 12:41 schreef "Csányi Pál" het
> volgende:
>
>> 2015-01-31 23:12 GMT+01:00 Guus Snijders :
>> > 2015-01-31 21:20 GMT+01:00 Christian Demsar :
>> > [...]
>> >> At this point, I'd backup configuration files and home directories and
>> >> do
2015-01-31 23:12 GMT+01:00 Guus Snijders :
> 2015-01-31 21:20 GMT+01:00 Christian Demsar :
> [...]
>> At this point, I'd backup configuration files and home directories and
>> do a full reinstall. Sounds like there's something going terribly wrong.
>> Hopefully that works...
>
> Hmm, I'd first chec
2015-01-31 21:20 GMT+01:00 Christian Demsar :
[...]
> At this point, I'd backup configuration files and home directories and
> do a full reinstall. Sounds like there's something going terribly wrong.
> Hopefully that works...
Hmm, I'd first check if dmesg shows SATA error (bus reset, seek
failed,
On Sat, Jan 31, 2015, at 12:13 PM, Csányi Pál wrote:
> Indeed. I find the solution at:
> https://wiki.manjaro.org/index.php?title=Clamav
>
> > Okay, so in regards to ClamAV, I encountered no errors [1] starting
> > clamd with the service file in the clamav package [2].
>
> > [2] http://pastebin.c
2015-01-31 0:53 GMT+01:00 Christian Demsar :
>> > So I just installed clamav but when I'm trying to start it with:
>> >>
>> > 'sudo systemctl start clamd.service'
>> >>
>> >> I get:
>> >> Job for clamd.service failed. See "systemctl status clamd.service" and
>> >> "journalctl -xe" for details.
>> >
> > So I just installed clamav but when I'm trying to start it with:
> >>
> > 'sudo systemctl start clamd.service'
> >>
> >> I get:
> >> Job for clamd.service failed. See "systemctl status clamd.service" and
> >> "journalctl -xe" for details.
> >>
> >> 'systemctl status clamd.service'
> >> clamd.s
> > So I just installed clamav but when I'm trying to start it with:
> >>
> > 'sudo systemctl start clamd.service'
> >>
> >> I get:
> >> Job for clamd.service failed. See "systemctl status clamd.service" and
> >> "journalctl -xe" for details.
> >>
> >> 'systemctl status clamd.service'
> >> clamd.s
>> Your pacman log and journalctl might give some clues.
> I guess he meant more or less complete logs. Give a journalctl log of a
> boot where you had the issue together with a pacman log including your
> latest updates (maybe since the problem began/ reappeared together with
> exact dates)
>
>>
>
>
> >> Your pacman log and journalctl might give some clues.
>
I guess he meant more or less complete logs. Give a journalctl log of a
boot where you had the issue together with a pacman log including your
latest updates (maybe since the problem began/ reappeared together with
exact dates)
> > I
2015-01-30 21:10 GMT+01:00 Csányi Pál :
> 2015-01-30 20:33 GMT+01:00 Christian Demsar :
>> On January 30, 2015 2:21:34 PM EST, "Csányi Pál" wrote:
>>>2015-01-30 20:04 GMT+01:00 Csányi Pál :
Hi Damjan,
2015-01-30 19:39 GMT+01:00 Damjan Georgievski :
>> I'm thinking now about foll
2015-01-30 20:33 GMT+01:00 Christian Demsar :
> On January 30, 2015 2:21:34 PM EST, "Csányi Pál" wrote:
>>2015-01-30 20:04 GMT+01:00 Csányi Pál :
>>> Hi Damjan,
>>>
>>> 2015-01-30 19:39 GMT+01:00 Damjan Georgievski :
> I'm thinking now about following.
> Whether to purge my Desktop Arch li
On January 30, 2015 2:21:34 PM EST, "Csányi Pál" wrote:
>2015-01-30 20:04 GMT+01:00 Csányi Pál :
>> Hi Damjan,
>>
>> 2015-01-30 19:39 GMT+01:00 Damjan Georgievski :
I'm thinking now about following.
Whether to purge my Desktop Arch linux installation from hard disk
>and
install a fr
2015-01-30 20:04 GMT+01:00 Csányi Pál :
> Hi Damjan,
>
> 2015-01-30 19:39 GMT+01:00 Damjan Georgievski :
>>> I'm thinking now about following.
>>> Whether to purge my Desktop Arch linux installation from hard disk and
>>> install a fresh Arch linux again, or not?
>>>
>>> What would you do in my cas
Hi Damjan,
2015-01-30 19:39 GMT+01:00 Damjan Georgievski :
>> I'm thinking now about following.
>> Whether to purge my Desktop Arch linux installation from hard disk and
>> install a fresh Arch linux again, or not?
>>
>> What would you do in my case? ( I'm not a bash and Arch linux guru. )
>
> Fir
> I'm thinking now about following.
> Whether to purge my Desktop Arch linux installation from hard disk and
> install a fresh Arch linux again, or not?
>
> What would you do in my case? ( I'm not a bash and Arch linux guru. )
First thing is, how did it happen to become broken again.
Normally it s
Hello again,
the kernel panic error appeares again.
I fix my desktop system with commands:
lsblk
mkdir /mnt/arch
mount /dev/sda3 /mnt/arch
systemd-nspawn -D /mnt/arch
pacman -S base
mkinitcpio -p linux
exit
reboot
I'm thinking now about following.
Whether to purge my Desktop Arch linux installat
On 01/18/2015 11:20 PM, Uwe Koloska wrote:
> Am 18.01.2015 um 20:31 schrieb Ralf Mardorf:
>> I would ignore "0 missing files" to stay on top of things.
>>
>> sudo pacman -Qk | grep -v "0 missing files"
>
> If you don't use english as your system language you should use the
> following or the grep
On Sun, 18 Jan 2015 14:57:29 -0600, Troy Engel wrote:
> A bug report should be filed for that package
I don't use this package, but I have nothing to do, IOW I've got much
time so I add a comment.
"Comment by Ralf_Mardorf
2015-01-18 22:29
Another user is using your PKGBUILD and noticed that you
Am 18.01.2015 um 20:31 schrieb Ralf Mardorf:
> I would ignore "0 missing files" to stay on top of things.
>
> sudo pacman -Qk | grep -v "0 missing files"
If you don't use english as your system language you should use the
following or the grep misses the localized output:
sudo LANG=C pacman -Q
On Sun, 18 Jan 2015 14:57:29 -0600, Troy Engel wrote:
> A bug report should be filed for that package:
>
> https://aur.archlinux.org/packages/ce/celestia-addon-sun/PKGBUILD
>
> They're installing that JPG to /tmp/ for some odd reason, that's just
> wrong on any Linux distribution.
Full ACK.
J
On Sun, Jan 18, 2015 at 2:40 PM, Ralf Mardorf
wrote:
> On Sun, 18 Jan 2015 21:12:26 +0100, Oliver Temlin wrote:
>> On 18 January 2015 at 21:04, Csányi Pál wrote:
>> >>> warning: celestia-addon-sun: /tmp/
>> >> tmp?
>> > What does it mean?
>>
>> Ramdisk is mount
On Sun, 18 Jan 2015 21:12:26 +0100, Oliver Temlin wrote:
> On 18 January 2015 at 21:04, Csányi Pál wrote:
> >>> warning: celestia-addon-sun: /tmp/
> >> tmp?
> > What does it mean?
>
> Ramdisk is mounted on /tmp, thus any file installed to it is lost
> after a r
On Sun, Jan 18, 2015 at 2:14 PM, Csányi Pál wrote:
>
> /usr/bin/virt-host-validate,libaudit.so.1
> /usr/bin/playerjoy,libboost_system.so.1.55.0
> /usr/bin/gtkam,libgphoto2_port.so.10
> /usr/bin/downgrader,libalpm.so.8
> /usr/bin/sensord,librrd.so.4
OK you have a couple problems that are a little
2015-01-18 19:47 GMT+00:00 Troy Engel :
> On Sun, Jan 18, 2015 at 1:31 PM, Ralf Mardorf
> wrote:
>> On Sun, 18 Jan 2015 20:24:54 +0100, Damjan Georgievski wrote:
>>> > After I reinstalled gcc-libs package, I can start firefox.
>>>
>>> Your system might still have broken packages after those conver
On Sun, 18 Jan 2015 20:04:21 +, Csányi Pál wrote:
> 2015-01-18 20:01 GMT+00:00 Ralf Mardorf :
> > On Sun, 18 Jan 2015 19:47:13 +, Csányi Pál wrote:
> >> I found only one package has missing 1 file:
> >> warning: celestia-addon-sun: /tmp/
> > tmp?
>
> Wha
On 18 January 2015 at 21:04, Csányi Pál wrote:
>>> warning: celestia-addon-sun: /tmp/
>> tmp?
> What does it mean?
Ramdisk is mounted on /tmp, thus any file installed to it is lost after a
reboot.
--Oliver Temlin
Hello Troy,
2015-01-18 19:47 GMT+00:00 Troy Engel :
> On Sun, Jan 18, 2015 at 1:31 PM, Ralf Mardorf
> wrote:
>> On Sun, 18 Jan 2015 20:24:54 +0100, Damjan Georgievski wrote:
>>> > After I reinstalled gcc-libs package, I can start firefox.
>>>
>>> Your system might still have broken packages after
2015-01-18 20:01 GMT+00:00 Ralf Mardorf :
> On Sun, 18 Jan 2015 19:47:13 +, Csányi Pál wrote:
>> I found only one package has missing 1 file:
>> warning: celestia-addon-sun: /tmp/
> tmp?
What does it mean?
--
Regards from Pal
On Sun, 18 Jan 2015 19:47:13 +, Csányi Pál wrote:
> I found only one package has missing 1 file:
> warning: celestia-addon-sun: /tmp/
tmp?
On Sun, Jan 18, 2015 at 1:31 PM, Ralf Mardorf
wrote:
> On Sun, 18 Jan 2015 20:24:54 +0100, Damjan Georgievski wrote:
>> > After I reinstalled gcc-libs package, I can start firefox.
>>
>> Your system might still have broken packages after those conversions
>> you were doing.
>>
>> Use pacman {-Q --
2015-01-18 19:31 GMT+00:00 Ralf Mardorf :
> On Sun, 18 Jan 2015 20:24:54 +0100, Damjan Georgievski wrote:
>> > After I reinstalled gcc-libs package, I can start firefox.
>>
>> Your system might still have broken packages after those conversions
>> you were doing.
>>
>> Use pacman {-Q --query} with
On Sun, 18 Jan 2015 20:24:54 +0100, Damjan Georgievski wrote:
> > After I reinstalled gcc-libs package, I can start firefox.
>
> Your system might still have broken packages after those conversions
> you were doing.
>
> Use pacman {-Q --query} with
> -k, --check check that package file
> After I reinstalled gcc-libs package, I can start firefox.
Your system might still have broken packages after those conversions
you were doing.
Use pacman {-Q --query} with
-k, --check check that package files exist (-kk for file properties)
to check everything.
--
damjan
2015-01-18 19:05 GMT+00:00 Troy Engel :
> On Sun, Jan 18, 2015 at 1:01 PM, Csányi Pál wrote:
>>
>> I cn now login and start X Window, but say I can't run firefox.
>> When started firefox I get error message:
>> error while loading shared libraries: libstdc++.so.6: cannot open
>> shared object file
On Sun, 18 Jan 2015 13:05:53 -0600, Troy Engel wrote:
> $ pacman -Qo /usr/lib/libstdc++.so.6
> /usr/lib/libstdc++.so.6 is owned by gcc-libs 4.9.2-2
My apologies, indeed libstdc++.so.6 is installed here too.
On Sun, 18 Jan 2015 20:01:27 +0100, Csányi Pál wrote:
> I cn now login and start X Window, but say I can't run firefox.
> When started firefox I get error message:
> error while loading shared libraries: libstdc++.so.6: cannot open
> shared object file: No such file or directory.
I've got Firefiox
On Sun, Jan 18, 2015 at 1:01 PM, Csányi Pál wrote:
>
> I cn now login and start X Window, but say I can't run firefox.
> When started firefox I get error message:
> error while loading shared libraries: libstdc++.so.6: cannot open
> shared object file: No such file or directory.
>
> Thank you all
On Sun, 18 Jan 2015 19:45:18 +0100, Damjan Georgievski wrote:
> check what files you have in /usr/lib64/ and why. if they are from
> packages remove those packages.
JFTR
$ pacman -Qo /path/to/file/foo/bar
/path/to/file/foo/bar is owned by...
IIUC the OP is aware that /usr/lib64/ should be a link
2015-01-18 19:45 GMT+01:00 Damjan Georgievski :
> On 18 January 2015 at 19:40, Csányi Pál wrote:
>>
>> 2015-01-18 19:28 GMT+01:00 Damjan Georgievski :
>> >
>> >> >> it won't overwrite the /usr/lib64 folder.
>> >> >
>> >> > post the exact errors you're getting
>> >>
>> >> The output of `pacman -S b
On Sun, 18 Jan 2015 19:28:27 +0100, Damjan Georgievski wrote:
> which means /usr/lib64 is a directory on your system??
So the OP should ensure that it's a link by running:
ls -ld /usr/lib*
On Sun, 18 Jan 2015 19:40:57 +0100, Csányi Pál wrote:
> I did update almost every day.
Another shot in the dark I would try is to downgrade systemd. Actually
I'm still using systemd 217-8 and didn't upgrade to 218-1. I always
wait and read mails for a while before I upgrade systemd.
On 18 January 2015 at 19:40, Csányi Pál wrote:
>
> 2015-01-18 19:28 GMT+01:00 Damjan Georgievski :
> >
> >> >> it won't overwrite the /usr/lib64 folder.
> >> >
> >> > post the exact errors you're getting
> >>
> >> The output of `pacman -S base' command is:
> >> (50/50) checking keys in keyring
> >
2015-01-18 19:28 GMT+01:00 Damjan Georgievski :
>
>> >> it won't overwrite the /usr/lib64 folder.
>> >
>> > post the exact errors you're getting
>>
>> The output of `pacman -S base' command is:
>> (50/50) checking keys in keyring
>> (50/50) checking package integrity
>> (50/50) loading package file
On Sun, 18 Jan 2015 19:24:00 +0100, Csányi Pál wrote:
> 2015-01-18 19:04 GMT+01:00 Troy Engel :
> > On Sun, Jan 18, 2015 at 11:49 AM, Csányi Pál
> > wrote:
> >> 2015-01-18 18:20 GMT+01:00 Damjan Georgievski :
> >>>
> >>>
> >>> there's no /init outside of the ramdisk, so his problem seems to
> >>>
> >> it won't overwrite the /usr/lib64 folder.
> >
> > post the exact errors you're getting
>
> The output of `pacman -S base' command is:
> (50/50) checking keys in keyring
> (50/50) checking package integrity
> (50/50) loading package files
> (50/50) checking for file conflicts
> (50/50) checking
2015-01-18 19:04 GMT+01:00 Troy Engel :
> On Sun, Jan 18, 2015 at 11:49 AM, Csányi Pál wrote:
>> 2015-01-18 18:20 GMT+01:00 Damjan Georgievski :
>>>
>>>
>>> there's no /init outside of the ramdisk, so his problem seems to be in the
>>> initramfs, but probably because his base system is a bit borke
On Sun, Jan 18, 2015 at 11:49 AM, Csányi Pál wrote:
> 2015-01-18 18:20 GMT+01:00 Damjan Georgievski :
>>
>>
>> there's no /init outside of the ramdisk, so his problem seems to be in the
>> initramfs, but probably because his base system is a bit borked and it
>> mkinitcpio creates the initramfs ou
53 matches
Mail list logo
