Testing Lithium iso discussion

malm · 2020-01-21 20:36:04

Don’t worry about the lockfile.

The message below is an x11 error. Not sure what the issue is. A google search shows all sorts if suggestions (nvidia, incorrect DISPLAY variable, etc).
Do you get any clues if you set verbosity=3 in jgmenurc?

Does the same happen with similar apps such as dmenu and rofi?

Last edited by malm (2020-01-21 20:37:02)

s-rod · 2020-01-21 22:52:33

With verbosity=3 set

info: 1 xrandr crt controller(s) found
    - monitor-1: x0=0; y0=0; w=1600; h=837
info: using monitor '1'
info: screen:        (0,0,1600,837)
info: _NET_WORKAREA: (0,0,1600,837)
info: got font from jgmenurc
info: set font to 'Sans 10'
info: using monitor '1'
X Error of failed request:  BadMatch (invalid parameter attributes)
  Major opcode of failed request:  78 (X_CreateColormap)
  Serial number of failed request:  23
  Current serial number in output stream:  26

malm · 2020-01-22 06:13:32

Looks tidy.
echo $DISPLAY
dmenu okay?

s-rod · 2020-01-22 17:21:15

echo $DISPLAY shows :50
dmenu_run launched from terminal appears to be fine from within the x2go session.

Also noticed that when the x2go session starts there is no wall paper or tint2. Running nitrogen --restore will bring up the wallpaper with the following errors (the host machine has 3 monitors attached).

(nitrogen:8139): Gtk-WARNING **: 15:05:02.384: Unable to locate theme engine in module_path: "adwaita",

(nitrogen:8139): Gtk-WARNING **: 15:05:02.384: Unable to locate theme engine in module_path: "adwaita",
Could not find Xinerama screen number 2
Could not find Xinerama screen number 1

(nitrogen:8139): Gtk-WARNING **: 15:05:02.425: Unable to locate theme engine in module_path: "adwaita",

(nitrogen:8139): Gtk-WARNING **: 15:05:02.425: Unable to locate theme engine in module_path: "adwaita",

.

Then I can run tint2 which shows the following

tint2: xRandr: Found crtc's: 1
tint2: xRandr: Linking output default with crtc 0, resolution 800x600, DPI 96
tint2: No XSETTINGS manager, tint2 uses config option 'launcher_icon_theme'.
tint2: Loading config file: /home/stever/.config/tint2/tint2rc
tint2: real transparency off.... depth: 24
tint2: warning : monitor not found. tint2 default to all monitors.
tint2: panel items: PTSCP
tint2: Systray composited rendering off
tint2: systray_asb forced to 100 0 0
tint2: nb monitors 1, nb monitors used 1, nb desktops 4
tint2: panel 1 uses scale 1 
tint2: Loading icon theme cache...
Icon path not found in cache: theme = Papirus-Bunsen-Dark-bluegrey, icon = start-here, size = 0
tint2: Loading icon theme Papirus-Bunsen-Dark-bluegrey:
tint2:  'Papirus-Bunsen-Dark-bluegrey',tint2:  'Papirus-Dark',tint2:  'breeze-dark',tint2:  'gnome',tint2:  'hicolor',tint2: 
Adding icon path to cache: theme = Papirus-Bunsen-Dark-bluegrey, icon = start-here, size = 0, path = /usr/share/icons/Papirus-Bunsen-Dark-bluegrey/16x16/apps/start-here.png
***** Imlib2 Developer Warning ***** :
	This program is calling the Imlib call:

	imlib_image_set_has_alpha();

	With the parameter:

	image

	being NULL. Please fix your program.
***** Imlib2 Developer Warning ***** :
	This program is calling the Imlib call:

	imlib_image_get_data();

	With the parameter:

	image

	being NULL. Please fix your program.
***** Imlib2 Developer Warning ***** :
	This program is calling the Imlib call:

	imlib_image_put_back_data();

	With the parameter:

	image

	being NULL. Please fix your program.
Icon path not found in cache: theme = Papirus-Bunsen-Dark-bluegrey, icon = /usr/share/images/bunsen/exit/light/poweroff.png, size = 0
Adding icon path to cache: theme = Papirus-Bunsen-Dark-bluegrey, icon = /usr/share/images/bunsen/exit/light/poweroff.png, size = 0, path = /usr/share/images/bunsen/exit/light/poweroff.png
***** Imlib2 Developer Warning ***** :
	This program is calling the Imlib call:

	imlib_image_set_has_alpha();

	With the parameter:

	image

	being NULL. Please fix your program.
***** Imlib2 Developer Warning ***** :
	This program is calling the Imlib call:

	imlib_image_get_data();

	With the parameter:

	image

	being NULL. Please fix your program.
***** Imlib2 Developer Warning ***** :
	This program is calling the Imlib call:

	imlib_image_put_back_data();

	With the parameter:

	image

	being NULL. Please fix your program.
tint2: Kernel uevent interface initialized...
Icon path not found in cache: theme = Papirus-Bunsen-Dark-bluegrey, icon = start-here, size = 28
Adding icon path to cache: theme = Papirus-Bunsen-Dark-bluegrey, icon = start-here, size = 28, path = /usr/share/icons/Papirus-Bunsen-Dark-bluegrey/32x32/apps/start-here.png
tint2: systray window 12582923
tint2: systray started
Icon path not found in cache: theme = Papirus-Bunsen-Dark-bluegrey, icon = /usr/share/images/bunsen/exit/light/poweroff.png, size = 28
Adding icon path to cache: theme = Papirus-Bunsen-Dark-bluegrey, icon = /usr/share/images/bunsen/exit/light/poweroff.png, size = 28, path = /usr/share/images/bunsen/exit/light/poweroff.png
add_icon: 8388610 (NetworkManager Applet), pid 7963, visual 0x55b879cdcb80, colormap 221, depth 24, width 16, height 16
add_icon: 6291458 (xfce4-power-manager), pid 7985, visual 0x55b879cdcb80, colormap 221, depth 24, width 16, height 16

After tint2 is running I can click on the Main Menu Launcher and the jgmenu displays on the host machines second monitor (1) and not within the x2go session.
I have used x2go to remote multiple BL machines prior to Lithium and did not experienced the wall paper, tint2 issues.
Again, this is a very minor issue as I have now customized the obmenu for my needs.

Last edited by s-rod (2020-01-22 21:28:40)

malm · 2020-01-22 21:25:58

@s-rod, I'll PM you so that we don't take over this thread too much.

rbh · 2020-01-23 10:18:04

I think it would be good to have a shortcut to root terminal, or at least a shortcut to helpfile about editing poolkit, so one self can edit policy and allow pkexec run a terminal.

I can start root terminal with workaround:
In user terminal:

sudo su -
exit
sudo lxterminal &

....

Also a helpfile about running application as root, would be good.

Last edited by rbh (2020-01-23 10:18:33)

damo · 2020-01-23 11:01:57

^ An argument against that idea is that "a little knowledge can be dangerous". That is, making it easy for someone to use applications as root, without being aware of the possible consequences, might not be adviseable.

Those who have taken the trouble to learn something about it should be able to use pkexec themselves. Opinions on this may vary!

rbh · 2020-01-23 11:29:37

damo wrote:

^ An argument against that idea is that "a little knowledge can be dangerous". That is, making it easy for someone to use applications as root, without being aware of the possible consequences, might not be adviseable.
Those who have taken the trouble to learn something about it should be able to use pkexec themselves. Opinions on this may vary!

But some info and warnings about running program as root, and why / how it is restricted?

Before I could not launch synaptic with pkecec, thought it was not allowed. But I must have misstyped password, for now it was ok.
I did edit policy for pkexec for a year ago, but have forgot howto. Have been thinking that I must take time and reread about it, but time slips...

It is a delicate balance. GParted and GDebi is on the menu, but not synaptic...
Maybe it should be little more easy for a new user to add a new package?

BTW, the meny choice Applications => Systemtools => Tint2 (panel), gives a new tintpanel, that is not as pleasant as default one.

Last edited by rbh (2020-01-23 11:30:10)

johnraff · 2020-01-23 11:51:11

rbh wrote:

GParted and GDebi is on the menu, but not synaptic...

Beg to differ. smile
Menu > System > Synaptic Package Manager
or
Menu > Applications > System > Synaptic Package Manager

As for launching a terminal emulator as root, why not just launch a regular terminal emulator and then either get root powers with sudo, or open a root shell with 'sudo su -' or a variant?

rbh · 2020-01-23 13:07:45

johnraff wrote:

Beg to differ.
Menu > System > Synaptic Package Manager

Hmmm, forgive my old tired eyes. The difference between gmrun => synaptic and gparted, is maybe by intent. When starting parted, password is required, bot synaptic starts without admin priviliges.

As for launching a terminal emulator as root, why not just launch a regular terminal emulator and then either get root powers with sudo, or open a root shell with 'sudo su -' or a variant?

I have solved it. Many other dists, have a shortcut for "Root Terminal". But, it's no big deal...

damo · 2020-01-23 14:57:22

rbh wrote:

.... When starting parted, password is required, bot synaptic starts without admin priviliges...

Synaptic doesn't require admin privileges in order to run - they are only required for the equivalent apt/aptitude/apt-get tools. You don't need sudo for apt-cache <option> for example.

johnraff · 2020-01-24 06:08:14

^ & ^^ but if you launch synaptic from the menu (either place) it will popup a window requesting a password.

hhh · 2020-01-24 07:09:32

rbh wrote:

I think it would be good to have a shortcut to root terminal, or at least a shortcut to helpfile about editing poolkit, so one self can edit policy and allow pkexec run a terminal.
I can start root terminal with workaround:
In user terminal:
sudo su -
exit
sudo lxterminal & 
....

Root terminal... Open a terminal

rachel@TyrellCorp:~$ sudo -i
[sudo] password for rachel: 
root@TyrellCorp:~#

Synaptic via terminal

rachel@TyrellCorp:~$ pkexec synaptic

(synaptic:11975): dbind-WARNING **: 02:07:38.455: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.ServiceUnknown: The name org.a11y.Bus was not provided by any .service files

Password GUI prompt opens. The error message is because I've removed the accessibility daemon (at-spi2-core) from my system.

Am I misunderstanding the question?

rbh · 2020-01-24 13:51:50

hhh wrote:

rachel@TyrellCorp:~$ sudo -i

Ah, did not knew that gave right to start x-apps. Thanks.
Does poolkit control which apps it is possible to start from thereafter?

rachel@TyrellCorp:~$ pkexec synaptic

Which configfile controls which apps user can run with admin rights?

I just tested another vm. After a coupe of minutes there was a message, roughly: Could not get exclusive locking ...
I was runing an upgrade on that, had forgotten that. (CPU-load 100%)
On a third vm, it worked, took maybe 20 s. to start synaptic...

I know that gmrun => "pkexec synaptic", did not funktion before (on Lithium). I thoght it was by intent. Has any bunsen-configs ben changed?

Or, maybe it only is working and hard to say why it did not work before...

damo · 2020-01-24 13:59:19

rbh wrote:

...
Which configfile controls which apps user can run with admin rights?
...

Look in /usr/share/polkit-1/ for all the policykit settings files.

hhh · 2020-01-24 19:41:41

@rbh, I can't advise regarding VM. I hate the abstraction of a VM so I prefer to add disc partitions and boot to the test OS on real hardware.

I realize that virtual machines are very useful. But I hate them, they're posers to me.

It's like watching somebody pass me and my fixie on an electric bicycle.

rbh · 2020-01-24 23:29:51

Now on my old IBM T43. Migrated from Helium to Lithium when dev repo became available.
Pkexec terminator/lxterminal gives "Unable to init server: Could not connect: Connection refused".
But "pkexec synaptic" works.

Looking through /etc/polkit-1/ and "man polkit",has not made me any wiser. I will reread https://wiki.archlinux.org/index.php/Polkit, but I think I need "Polkit for Dumies"...

damo · 2020-01-25 00:26:55

rbh wrote:

Now on my old IBM T43. Migrated from Helium to Lithium when dev repo became available.
Pkexec terminator/lxterminal gives "Unable to init server: Could not connect: Connection refused".
But "pkexec synaptic" works.

'pkexec bl-terminal-emulator' should be working though, which is set by BL.

Looking through /etc/polkit-1/ and "man polkit",has not made me any wiser. I will reread https://wiki.archlinux.org/index.php/Polkit, but I think I need "Polkit for Dumies"...

You should have looked at the filepath I gave you previously ^^^: /usr/share/polkit-1/. Have a look particularly at /usr/share/polkit-1/actions/org.bunsenlabs.pkexec.policy - it should give you enough information to hack your own policy (if you really need one).

johnraff · 2020-01-25 01:37:43

damo wrote:

'pkexec bl-terminal-emulator' should be working though, which is set by BL.

This is a bit of a gnarly subject, but we do not provide polkit support for pkexec bl-terminal-emulator. This came after a long discussion of the (de)merits of starting X apps as root, and the compromise we reached was to allow pkexec bl-text-editor and pkexec bl-cli-editor (the latter opens a terminal emulator with a text editor inside). Thunar, synaptic and gparted already provide their own polkit files. (A user can add any others of course.)

damo · 2020-01-25 01:50:56

^ Yes, my bad - I was looking at my old polkit file I reckon. And anyway, I meant "x-terminal-emulator" ops

malm · 2020-02-02 20:37:09

Original message: https://forums.bunsenlabs.org/viewtopic … 045#p96045

s-rod wrote:

I regularly remote my work pc from home using x2go. Within an x2go session jgmenu does not work and the default openbox menu is presented.

When using x2go, composite extension is not supported, so the color-depth becomes 24 bit (rgb - without alpha).

jgmenu has been fixed to support color-depths other than 32 bit.
See github issue https://github.com/johanmalm/jgmenu/issues/111

s-rod wrote:

Also noticed that when the x2go session starts there is no wall paper or tint2. Running nitrogen --restore will bring up the wallpaper with the following errors
--cut--
I have used x2go to remote multiple BL machines prior to Lithium and did not experienced the wall paper, tint2 issues.

This is because ~/.config/openbox/autostart has changed name. When running x2goclient, choose "bunsenlabs-session" rather than "openbox" or "openbox-session". Or create a new ~/.config/openbox/autostart file. @s-rod solved this, but thought the answer should be included here for reference.

kozimodo · 2020-02-14 02:25:32

Installed on my Acer S7-392 and everything is great with one exception -- light-locker sometimes freezes up. I initially thought it was the power manager but the last time it happened right after trying to sign back in and accidentally typing the wrong password. When it freezes, I have to ssh in and restart lightdm. I had no such problem with helium.

Thoughts, ideas?

Dendrobats · 2020-02-14 15:06:28

Hello,

Maybe not the right place for this post, but I have Theme suggestion for the next major release of BunshenLabs.
I always have believed that the first look of the distro should be beautiful and simple, so people would like to use it.

BUNSHENLABS SIMPLE
Tint2+Conky

Clean & Simple

With Paper icons

Files Tint2+Conky

Images should be copied in usr/shar/tint2
Any icon theme can be used I use Majove-CT

Last edited by Dendrobats (2020-02-17 06:46:03)

damo · 2020-02-14 16:21:38

^ PLEASE USE LINKED THUMBNAIL IMAGES, as per the Forum Rules (see my sig)!

Do not embed images larger than 250x250px into posts, use thumbnails linking to a hosted image instead.

dumetrulo · 2020-02-18 15:04:42

@Dendrobats This looks very nice indeed. In my opinion, the paper icons look better than the other ones.

Does this properly scale with resolution, and work with multiple screens?

#101 2020-01-21 20:36:04

Re: Testing Lithium iso discussion

#102 2020-01-21 22:52:33

Re: Testing Lithium iso discussion

#103 2020-01-22 06:13:32

Re: Testing Lithium iso discussion

#104 2020-01-22 17:21:15

Re: Testing Lithium iso discussion

#105 2020-01-22 21:25:58

Re: Testing Lithium iso discussion

#106 2020-01-23 10:18:04

Re: Testing Lithium iso discussion

#107 2020-01-23 11:01:57

Re: Testing Lithium iso discussion

#108 2020-01-23 11:29:37

Re: Testing Lithium iso discussion

#109 2020-01-23 11:51:11

Re: Testing Lithium iso discussion

#110 2020-01-23 13:07:45

Re: Testing Lithium iso discussion

#111 2020-01-23 14:57:22

Re: Testing Lithium iso discussion

#112 2020-01-24 06:08:14

Re: Testing Lithium iso discussion

#113 2020-01-24 07:09:32

Re: Testing Lithium iso discussion

#114 2020-01-24 13:51:50

Re: Testing Lithium iso discussion

#115 2020-01-24 13:59:19

Re: Testing Lithium iso discussion

#116 2020-01-24 19:41:41

Re: Testing Lithium iso discussion

#117 2020-01-24 23:29:51

Re: Testing Lithium iso discussion

#118 2020-01-25 00:26:55

Re: Testing Lithium iso discussion

#119 2020-01-25 01:37:43

Re: Testing Lithium iso discussion

#120 2020-01-25 01:50:56

Re: Testing Lithium iso discussion

#121 2020-02-02 20:37:09

Re: Testing Lithium iso discussion

#122 2020-02-14 02:25:32

Re: Testing Lithium iso discussion

#123 2020-02-14 15:06:28

Re: Testing Lithium iso discussion

#124 2020-02-14 16:21:38

Re: Testing Lithium iso discussion

#125 2020-02-18 15:04:42

Re: Testing Lithium iso discussion

Board footer