Are Big Sacrifice

66 réponses [Dernière contribution]
Connochaetes

I am a member!

Hors ligne
A rejoint: 12/13/2017

To those who use an up-to-date Uruk GNU/Linux: Does Uruk (or probably just its default file manager, I think it was Caja, in its default configuration) still have these two bugs?
One was that it tried to open everything and their dog using the image viewer (or document viewer?): When you use the file manager for a search, move focus to one of the results, an ogg file for example, call up the context menu and select "open containing folder", expected behaviour would be that you will see the contents of the folder listed in a file manager window, be it a new one or the one you were using. Instead, this will summon up the viewer which will immediately tell you that it was unable to open the thing. There were other, non-search related cases where the file manager (or Uruk) thought the viewer would be best to open a common file type when it obviously was neither an image nor a document.
The second bug that bugged me was: In the file manager, move focus to a listed file, press F2, use Ctrl+← or Ctrl+→. Expected behaviour: Cursor (or "caret"?) moves left or right within the file name, word by word. Observed behaviour: As soon as you hit Ctrl, focus jumps to the left side pane where the shortcuts are, canceling the file renaming. I can't remember if pressing Ctrl triggered this focus move when I wasn't trying to rename a file, for example to select non-adjacent files by holding Ctrl.

fbit

I am a member!

Hors ligne
A rejoint: 07/07/2013

Hello ariellab,

If I understand correctly, you are using a librebooted computer. If so, GRUB is in libreboot; meaning GRUB resides on your ROM chip, not on your harddisk.

To look at -- and modify -- the GRUB configuration, you'll need to use "flashrom" to get an image of the current ROM (follow step #2 in the how-to linked below).

**Important** Once you have downloaded the image, keep it as a backup somewhere safe!

You can then extract, modify and re-insert specific files using cbfstool. Finally you can flash the image to the ROM chip again (provided it was not locked when setup, otherwise you would need to re-flash it externally).

** Important** When making configuration changes, make them to grubtest.cfg first and make things permanent *only* after things are working well. Otherwise, you risk being left with an unbootable machine.

You should be able to ask for help at #libreboot on IRC if you run into trouble.

You can follow Magic Banana's instructions for the actual modifications to GRUB config.

https://libreboot.org/docs/gnulinux/grub_cbfs.html

ariellab
Hors ligne
A rejoint: 02/19/2015

Thanks so much for the input. I ended up reaching out to Minifree who set up the laptop and asked them. I was too afraid of doing flashrom related things, so instead they gave me a solution that involved symbolic-linking vmlinuz and initrd.img to the updated kernel version files in /boot.

ariellab
Hors ligne
A rejoint: 02/19/2015

Guys, good news. Leah gave me a super simple solution to get the kernel updated. It's ok to use linux-libre for the updated kernels, but then:

ariella@/ $ sudo rm vmlinuz initrd.img
ariella@/ $ sudo ln -s /boot/vmlinuz-4.14.13-gnu vmlinuz
ariella@/ $ sudo ln -s /boot/initrd.img-4.14.13-gnu initrd.img

Reboot, DONE!

ADFENO
Hors ligne
A rejoint: 12/31/2012

Awesome! ;)

Based on your shell prefix ("ariella@/ $ ", particularly the "/" part),
if you plan to write a guide, please take care to do any of these:

a) tell the reader to change directory to "/";

b) write all references of the exact phrases "vmlinuz" and "initrd.img"
as "/vmlinuz" and "/initrd.img", respectively, this includes the `rm'
and `ln' commands.

I hope this helps. ;)

2018-01-19T23:42:03+0100 name at domain wrote:
> Guys, good news. Leah gave me a super simple solution to get the
> kernel updated. It's ok to use linux-libre for the updated kernels,
> but then:
>
> ariella@/ $ sudo rm vmlinuz initrd.img
> ariella@/ $ sudo ln -s /boot/vmlinuz-4.14.13-gnu vmlinuz
> ariella@/ $ sudo ln -s /boot/initrd.img-4.14.13-gnu initrd.img
>
> Reboot, DONE!
>

--
- https://libreplanet.org/wiki/User:Adfeno
- Palestrante e consultor sobre /software/ livre (não confundir com
gratis).
- "WhatsApp"? Ele não é livre. Por favor, veja formas de se comunicar
instantaneamente comigo no endereço abaixo.
- Contato: https://libreplanet.org/wiki/User:Adfeno#vCard
- Arquivos comuns aceitos (apenas sem DRM): Corel Draw, Microsoft
Office, MP3, MP4, WMA, WMV.
- Arquivos comuns aceitos e enviados: CSV, GNU Dia, GNU Emacs Org, GNU
GIMP, Inkscape SVG, JPG, LibreOffice (padrão ODF), OGG, OPUS, PDF
(apenas sem DRM), PNG, TXT, WEBM.

ariellab
Hors ligne
A rejoint: 02/19/2015

Good call! Best practices absorbed.

Yes, please everyone, please prefix my previously mentioned steps with this first step (change directory to root of boot volume):

$ cd /

MD. SHAHIDUL ISLAM
Hors ligne
A rejoint: 10/14/2015

Now I am with mate desktop and uruk. At this time, mate-menu is a problem for me. When I used uruk 1.0, I faced this problem also.
Problem- After starting or rebooting when I click on mate-menu it start after 4-5 second. After that it start quickly. But why it take long time at first time?

hayderctee
Hors ligne
A rejoint: 05/02/2015

We will replace it in the next version :)