[Stable Update] 2019-02-09 - Kernels, Deepin, Firefox, Wine, Python, Haskell

thank you.
I fixed it. and I have done Upgrade.


lsblk provides the size allocated to the partition
du -sh /boot provides the space used

there may be easier/better ways to find the information :wink:

1 Like
[bardo@bardothodol-pc ~]$ df -h
Sist.fichs      Tama  Ocup Livre Uso% Montado em
dev             3,0G     0  3,0G   0% /dev
run             3,0G  1,2M  3,0G   1% /run
/dev/sdb8       275G  246G   15G  95% /
tmpfs           3,0G   90M  2,9G   4% /dev/shm
tmpfs           3,0G     0  3,0G   0% /sys/fs/cgroup
tmpfs           3,0G   42M  2,9G   2% /tmp
tmpfs           596M   16K  596M   1% /run/user/1000
[bardo@bardothodol-pc ~]$ lsblk
sda      8:0    0 298,1G  0 disk 
├─sda1   8:1    0 151,6G  0 part /run/media/bardo/shiva
└─sda2   8:2    0 146,5G  0 part /run/media/bardo/36779f1c-f119-4cc7-8d4f-c41f48
sdb      8:16   0 698,7G  0 disk 
├─sdb1   8:17   0 322,1G  0 part 
├─sdb5   8:21   0     4G  0 part [SWAP]
├─sdb6   8:22   0  18,6G  0 part 
├─sdb7   8:23   0  74,5G  0 part 
└─sdb8   8:24   0 279,4G  0 part /
sdc      8:32   0 465,8G  0 disk 
├─sdc1   8:33   0   358G  0 part 
├─sdc2   8:34   0  53,5G  0 part 
├─sdc3   8:35   0    50G  0 part 
├─sdc5   8:37   0   3,9G  0 part 
└─sdc6   8:38   0   500M  0 part 
       254:0    0   496M  0 lvm  
sr0     11:0    1  1024M  0 rom  
sr1     11:1    1  1024M  0 rom  
[bardo@bardothodol-pc ~]$ 
fdisk -l /dev/sdb
Disk /dev/sdb: 698,7 GiB, 750155292160 bytes, 1465147055 sectors
Disk model: SAMSUNG HD753LJ 
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x0004966f

Device     Boot      Start        End   Sectors   Size Id Type
/dev/sdb1             2048  675509860 675507813 322,1G 83 Linux
/dev/sdb2        675510270 1465145343 789635074 376,5G  5 Extended
/dev/sdb5       1456762880 1465145343   8382464     4G 82 Linux swap / Solaris
/dev/sdb6  *    1261445880 1300508378  39062499  18,6G 83 Linux
/dev/sdb7       1300508380 1456758134 156249755  74,5G 83 Linux
/dev/sdb8        675510334 1261445878 585935545 279,4G 83 Linux

Great, Congrats. Thanks to Jonathon. :slight_smile:

No issues or whatsoever! Thanks guys! :slight_smile:

Kernels: linux419 & linux414!

I was able to resolve the **keyring is not writable** error by following these steps:

Clean the package cache:

sudo pacman -Scc

Rename the /etc/pacman.d/gnupg folder:

sudo mv /etc/pacman.d/gnupg /etc/pacman.d/gnupg.old

Init your keyring:

sudo pacman-key --init

Reinstall the keyrings:

sudo pacman -S archlinux-keyring manjaro-keyring

Repopulate pacman’s keyring:

sudo pacman-key --populate archlinux manjaro

Refresh them:

sudo pacman-key --refresh

Upgrade the system:

sudo pacman -Syyu

I hope this will help for those people with the same problem :blush:


du -sh /boot
55M /boot

Below is a minimalist bar graph from the Stable update’s forum post’s polls. Just wanted to checkout what the poll has to say about the last 10 stable updates.

Although this is not in any way a reliable/good enough benchmark to say anything about the stable updates, I felt it still somehow reflects the hard work of Manjaro developers! Just thought of sharing! :slight_smile:

Thanks again for another amazing, smooth update! :muscle:

NOTE: AGAIN, This is NOT a reliable benchmark for anything. This reflects what community shared about the stable updates through poll’s feature. :slight_smile:


Depicts my experience…never had as little trouble with my OS as in the last 3 years with Manjaro :smiley:


And then I have to change my os… :confused:

All 5 Dell/Intel machines updated fine through the tty.
As always great work and a big thank you :+1:


All ok, KDE kernel 4.19, tty pacman, working well, thanks Manjaro team

Update without problem. The only doubt is that I can not get into TTY mode with closed user session on my laptop through the combination of keys Ctrl-Alt-F2 …
The update I made via terminal with user session started with the command sudo pacman -Syyuu, is that correct?

  Host: atreides-pc Kernel: 4.20.7-1-MANJARO x86_64 bits: 64 
  Desktop: Gnome 3.30.2 Distro: Manjaro Linux 
  Type: Laptop System: Hewlett-Packard product: HP G62 Notebook PC 
  v: 0497100000252710001020000 serial: <root required> 
  Mobo: Hewlett-Packard model: 143A v: 60.21 serial: <root required> 
  BIOS: Hewlett-Packard v: F.0A date: 06/14/2010 
  Topology: Dual Core model: Intel Core i3 M 350 bits: 64 type: MT MCP 
  L2 cache: 3072 KiB 
  Speed: 1375 MHz min/max: 933/2266 MHz Core speeds (MHz): 1: 1136 2: 1429 
  3: 1441 4: 1399 
  Device-1: Intel Core Processor Integrated Graphics driver: i915 v: kernel 
  Device-2: AMD Park [Mobility Radeon HD 5430/5450/5470] driver: radeon 
  v: kernel 
  Display: x11 server: X.org 1.20.3 driver: radeon 
  resolution: <xdpyinfo missing> 
  OpenGL: renderer: Mesa DRI Intel Ironlake Mobile v: 2.1 Mesa 18.3.2 

Thanks Manjaro team

Powered by Google Translator :sweat_smile:

A post was split to a new topic: Deepin VM DM segfault

Unlike the last update, everything went well, but I was afraid a little bit, it will be a problem. :slight_smile:

What is the “safest” way to update per terminal?
Is it sudo pacman -Syyuu ?
Or are there better ways?
Thank you for your work!

1 Like

I prefer pacman -Syyu but always read the release notes at the top of each release.


The final u is only needed if you want to enable downgrade. sudo pacman -Syyu is the standard way. Otherwise, pamac update does exactly the same thing (sudo not needed here, pamac asks you for password).

I prefer pamac as it can check updates from the AUR too if you have it enabled. It also has a more “human” syntax. Check this - Pamac CLI


Permission problems also give those warnings. Sometime programs need a lower level read permission, but permissions change to root only rw.

1 Like

pacman is run as root though so that shouldn’t be the issue here?

1 Like

Forum kindly sponsored by