- Arch-general - lists.archlinux.org

Re: [arch-general] Segmentation fault and (possibly) file system bug while removing gnome-extra
by Robert W0ng 16 May '17

16 May '17

Hi, Guus. I've just run the memtest from archiso. Just passed, no error reported. So I'm afraid it has to be an fs bug or other hardware error... I'm looking forward to running a SMART test later. But the current Arch installation is on a Kingstom USB drive, is that okay with the SMART test? In fact, what confused me most now is why both pacman and fsck reported segmentation fault... It can't just be a coincidence, right? Oh, remembered one more thing. I tried to remove the gnome-extra group again this afternoon. The same error, the same output. More specifically, even exactly the same time the error happened (when attemptting to remove package telepathy-idle). Funny enough, Uhm? ;) Thx a lot! RW Guus Snijders <gsnijders(a)gmail.com> wrote: >Op 14 mei 2017 04:29 schreef "Robert W0ng via arch-general" < >arch-general(a)archlinux.org>: > >Hello again, All. > >Update: > >I ran fsck in archiso this morning, and found sth interesting. > >To sum up, fsck.f2fs exit with signal 11, arguing segmentation fault. > > >AFAIK segfaults are memory errors (where $program tries to read or write >memory that isn't his). > >If there is a problem with the fs, fsck should complain and if possible fix >it, not just crash. > >Try memtest86 (give it a few hours) and see if something comes up. > > >Mvg, Guus Snijders

2 1

[arch-general] Ardour 5.6 released - status on update
by Britt Yazel 16 May '17

16 May '17

Hey everyone, Not to be impatient, but Ardour had another update today to version 5.6, and the stable repo's only have version 4.7 and testing only has 5.4. Nearly a month ago Ray Rashif promised to get 5.4 pushed to stable before the end of the weekend, though that appears to have fallen by the wayside. No criticism to Ray, as I am aware that he is was devoted to this thesis defense, but I would really love to see this package updated as it is more than a year out of date at this point. -Britt

8 20

Re: [arch-general] Segmentation fault and (possibly) file system bug while removing gnome-extra
by Guus Snijders 14 May '17

14 May '17

Op 14 mei 2017 04:29 schreef "Robert W0ng via arch-general" < arch-general(a)archlinux.org>: Hello again, All. Update: I ran fsck in archiso this morning, and found sth interesting. To sum up, fsck.f2fs exit with signal 11, arguing segmentation fault. AFAIK segfaults are memory errors (where $program tries to read or write memory that isn't his). If there is a problem with the fs, fsck should complain and if possible fix it, not just crash. Try memtest86 (give it a few hours) and see if something comes up. Mvg, Guus Snijders

1 0

[arch-general] Segmentation fault and (likely) file system bug while removing gnome-extra
by Robert W0ng 14 May '17

14 May '17

Hi, All. For several reasons I decided to remove the group 'gnome-extra' from my system. During the uninstallation, something went wrong. For a 'funny' reason, which I may explain later, I wasn't able to post the error log in the form of text here, so I will upload a photo as an attachment[1] with this mail... So, I switched to a getty and started the uninstallation. No errors occourred until it reached the 15th package. The package name was 'telepathy-idle'. All of a sudden the system printed a large section of dmesg, saying something like it had run into a kernel bug(?). The pacman was then killed, leaving the zsh reporting a segmentation fault... I felt the possibility that I wasn't able to handle this problem on my own, so I took a photograph using my mobile without even thinking, which proved to be useful later. Then I ran # dmesg >> /root/dmesg.output hoping to save the error log. I tried to restart the uninstallation, but the pacman freezed. Even pressing CTRL-C didn't work. I switched to another getty attemptting to terminal in, but after I entered 'root' and pressed ENTER, no any output. The course was just left there, blinking. Having no choice, I reboot the system using the magic sysrq keys... Rebooted, I checked the package changes. Confusingly, no packages was removed, even the previous should-be-removed 15 ones! Bad feeling about this, I checked the /root directory, and here came the most confusing part: The dmesg.output file was GONE! It seemed that all the data that should have been written to the disk were discarded... (And that's the reason why I have to post the error log in the form of shooted image... Somehow, I found myself a potential prophet... :P JUST KID...) Judged by this, together with the previous error log, I would say it's a file system bug... But, confused, how can an uninstallation of packages end up like this way? :( I would appreciate any help from you guys. Truly would. Thank you in advance! :) PS: I'm not going to post my pacman.conf here because all modification I had ever done to this file was to enable the color output. I suppose it can be excluded from the possible causes... And if necessary, I would recur the uninstallation with '--debug' flag enabled and report it to the upstream developer... [1] Upadte: Unable to upload the image file because it's too big to be attached in this mailing list... So I uploaded it to a local website and I will post the image address here. Image Address: http://imgsrc.baidu.com/forum/pic/item/7bf9f2c4b74543a9b 9da16cf14178a82bb0114d4.jpg RW

2 1

[arch-general] Segmentation fault and (possibly) file system bug while removing gnome-extra
by Robert W0ng 14 May '17

14 May '17

Hi, All. For several reasons I decided to remove the group 'gnome-extra' from my system. During the uninstallation, something went wrong. For a 'funny' reason, which I may explain later, I wasn't able to post the error log in the form of text here, so I will upload a photo as an attachment[1] with this mail... So, I switched to a getty and started the uninstallation. No errors occourred until it reached the 15th package. The package name was 'telepathy-idle'. All of a sudden the system printed a large section of dmesg, saying something like it had run into a kernel bug(?). The pacman was then killed, leaving the zsh reporting a segmentation fault... I felt the possibility that I wasn't able to handle this problem on my own, so I took a photograph using my mobile without even thinking, which proved to be useful later. Then I ran # dmesg >> /root/dmesg.output hoping to save the error log. I tried to restart the uninstallation, but the pacman freezed. Even pressing CTRL-C didn't work. I switched to another getty attemptting to terminal in, but after I entered 'root' and pressed ENTER, no any output. The course was just left there, blinking. Having no choice, I reboot the system using the magic sysrq keys... Rebooted, I checked the package changes. Confusingly, no packages was removed, even the previous should-be-removed 15 ones! Bad feeling about this, I checked the /root directory, and here came the most confusing part: The dmesg.output file was GONE! It seemed that all the data that should have been written to the disk were discarded... (And that's the reason why I have to post the error log in the form of shooted image... Somehow, I found myself a potential prophet... :P JUST KID...) Judged by this, together with the previous error log, I would say it's a file system bug... But, confused, how can an uninstallation of packages end up like this way? :( I would appreciate any help from you guys. Truly would. Thank you in advance! :) PS: I'm not going to post my pacman.conf here because all modification I had ever done to this file was to enable the color output. I suppose it can be excluded from the possible causes... And if necessary, I would recur the uninstallation with '--debug' flag enabled and report it to the upstream developer... [1] Upadte: Unable to upload the image file because it's too big to be attached in this mailing list... So I uploaded it to a local website and I will post the image address here. Image Address: http://imgsrc.baidu.com/forum/pic/item/7bf9f2c4b74543a9b 9da16cf14178a82bb0114d4.jpg RW

3 3

Re: [arch-general] Can someone update lib32-p11-kit?
by Rafael Fontenelle 11 May '17

11 May '17

Em 10/05/2017 18:25, "DR via arch-general" <arch-general(a)archlinux.org> escreveu: On Wed, May 10, 2017 at 4:14 PM, Doug Newgard <scimmia(a)archlinux.info> wrote: > On Wed, 10 May 2017 15:33:59 -0400 > DR via arch-general <arch-general(a)archlinux.org> wrote: > > > It's breaking 32bit chrome and other stuffs. > > > > Regards. > > There is no 32 bit Chrome anymore. What "other stuffs"? > There's if I build it myself. Did you try building it in a clean chroot? Regards, Rafael Fontenelle

1 0

[arch-general] Can someone update lib32-p11-kit?
by DR 10 May '17

10 May '17

It's breaking 32bit chrome and other stuffs. Regards.

3 3

[arch-general] libx264 changes
by Carsten Mattner 08 May '17

08 May '17

Since the libx264 package does not include /usr/include and it's in x264 now, and because x264 depends on ffmpeg, I cannot use libx264 without also installing ffmpeg. For various reasons like missing features and wrong version I cannot use arch's ffmpeg package and have to build my own package, and this results in a cyclic dependency I cannot get out of. (lib)x264 packages have always been cumbersome due to 8bit vs 10bit and other issues and are uniquely special in arch, but since there's already so many x264 packages, let's have a libx264-headers package. Or keep it in libx264 since 8bit and 10bit cannot be installed in parallel anyway. Doug, you probably have good reasons for the recent headers change and see no way to fix it to make my scenario work, but I'd appreciate if you gave this a thought and shared your opinion. If you can't fix this, do you mind explaining what led to the removal of headers from libx264? I hope I don't have to build libx264 myself as well since my PKGBUILD would diverge or force me to build libx264 and x264 custom versions.

6 15

[arch-general] AIF-NG (feedback/Request for Comments)
by brent s. 08 May '17

08 May '17

Hello! Some of you may remember AIF (Arch Installation Framework). However, the project is dead ([0]) and has been for quite some time. Being that most major distributions have a way of installing their distribution in an unattended manner/via PXE: -Debian (and derivatives, incl. Ubuntu): preseed -RHEL/CentOS/SuSE (and derivatives): kickstart (cobbler, etc.) I felt that Arch would benefit from something similar. As such, I have written AIF-NG[1]. It's written in python 3 and uses an XML-driven configuration (see the documentation[2] for details[3]). I would welcome feedback on this (preferably via my bugtracker[4] unless it happens to be discussion-oriented), as I'd like to get it mature enough to propose it for inclusion in the official Arch install media (currently for this to be supported, that would only require two things: the "python" and "aif" (or "aif-git") packages, which can be found on the AUR[5][6]). [0] https://github.com/Dieterbe/aif [1] https://git.square-r00t.net/AIF-NG [2] https://aif.square-r00t.net/ [3] https://aif.square-r00t.net/#writing_an_xml_configuration_file [4] https://aif.square-r00t.net/#bug_reports_feature_requests [5] https://aur.archlinux.org/packages/aif/ [6] https://aur.archlinux.org/packages/aif-git/ -- brent saner https://www.square-r00t.net

2 2

Re: [arch-general] End of official PaX and grsecurity support in Arch Linux
by Alexander Harrigan 01 May '17

01 May '17

It looks Gentoo's Hardened Kernel Project oficially started. https://wiki.gentoo.org/wiki/Hardened/Hardened_Kernel_Project \-- Sent using MsgSafe.io's Free Plan Private, encrypted, online communication For everyone. https://www.msgsafe.io

2 1