So running as normal user, the 'save' action for flashing doesn't work because of missing permissions. The docs suggest that I run `brickv` as root, but that doesn't work either, because the GUI doesn't come up:

 

$ sudo brickv
X Error: BadAccess (attempt to access private resource denied) 10
  Extension:    130 (MIT-SHM)
  Minor opcode: 1 (X_ShmAttach)
  Resource id:  0x159
X Error: BadShmSeg (invalid shared segment parameter) 128
  Extension:    130 (MIT-SHM)
  Minor opcode: 5 (X_ShmCreatePixmap)
  Resource id:  0x2400010
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
  Major opcode: 62 (X_CopyArea)
  Resource id:  0x2400011
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
  Major opcode: 62 (X_CopyArea)
  Resource id:  0x2400011

 

I also tried `sudo adduser myself dialout`, followed by regular `brickv` start, no success.

 

So it seems like a catch-22 here.

Note that `brick-flash` worked, so it's not urgent, but perhaps it worth checking that the UI flashing actually works on Linux.

Not sure why you get strange X server errors when running brickv as root. This just works for me.

 

The correct way to add the existing user "myself" to the existing group "dialout" is this:

 

sudo usermod -a -G dialout myself

 

Afterwards you need to logout and login again, because group changes do not apply directly. Then you should be able to flash a Brick from Brick Viewer started as user.