After the last upgrade of 64 bit Sparky Multimedia Testing Edition:
I can't open my external data and apps partitions (both are ntfs). They are invisible in pcmanfm, even as root.
And when I tried to open gparted, I received the following error message:
Unit -.mount does not exist, proceeding anyway.
I then tried to reinstall mount using synaptic but received the following error message:
E: /var/cache/apt/archives/libmypaint-1.3-0_1.3.0-dmo2_amd64.deb: trying to overwrite '/usr/share/locale/ca/LC_MESSAGES/libmypaint.mo', which is also in package mypaint-data 1.2.0-4.1
What now? TIA
Would using the Rescue DVD be likely to help?
Try:
sudo dpkg --remove --force-remove-reinstreq mypaint
sudo dpkg --remove --force-remove-reinstreq mypaint-data
then:
sudo apt update
sudo apt upgrade
sudo apt dist-upgrade
Thanks, pavroo.
I'll reboot back into Sparky and try that now.
Quote from: pavroo on January 09, 2018, 09:28:03 AM
Try:
sudo dpkg --remove --force-remove-reinstreq mypaint
sudo dpkg --remove --force-remove-reinstreq mypaint-data
then:
sudo apt update
sudo apt upgrade
sudo apt dist-upgrade
After the first part I couldn't proceed without reinstalling what was removed with
apt --fix-broken install
Then I could proceed and everything continued normally and I rebooted.
However after rebooting I still can't access my external partitions, of any kind.
This is what I get when I try:
Not authorized to perform operation
I am using the liquorix kernel and may reboot into the debian/sparky kernel to see what happens.
Looks like you have Openbox desktop as default, do you?
If not, let me know what it is.
Quote from: pavroo on January 09, 2018, 03:04:44 PM
Looks like you have Openbox desktop as default, do you?
If not, let me know what it is.
Yes, that is correct. (I add other things -like the xfce4-panel- as needed).
I rebooted into the Sparky Kernel but the condition persists (even a new btrfs partition can't be accessed).
What next?
All Operating Systems break sometimes (especially the most advanced ones).
Sparky is the best Debian derivative and has given me a lot of service. With time I'll learn more about how to fix it (but meanwhile this problem prevents me from accessing my data).
Show me:
apt-cache policy sparky-polkit
cat ~/.config/openbox/autostart.sh
pidof polkit-gnome-authentication-agent-1
pidof lxpolkit
Quote from: pavroo on January 09, 2018, 03:23:57 PM
Show me:
apt-cache policy sparky-polkit
cat ~/.config/openbox/autostart.sh
pidof polkit-gnome-authentication-agent-1
pidof lxpolkit
I'll try that now
Quote from: pavroo on January 09, 2018, 03:23:57 PM
Show me:
apt-cache policy sparky-polkit
cat ~/.config/openbox/autostart.sh
pidof polkit-gnome-authentication-agent-1
pidof lxpolkit
$ apt-cache policy sparky-polkit
sparky-polkit:
Installed: 0.1.2
Candidate: 0.1.2
Version table:
*** 0.1.2 1001
1001 https://sparkylinux.org/repo testing/main amd64 Packages
1001 https://sparkylinux.org/repo testing/main i386 Packages
100 /var/lib/dpkg/status
$ cat ~/.config/openbox/autostart.sh
#! /bin/bash
nitrogen --restore && \
tint2 &
xscreensaver --nosplash &
$pidof polkit-gnome-authentication-agent-1
Nothing was returned (the upgrade ended with some gnome code being removed with auto-remove).
$ pidof lxpolkit
Nothing was returned.
Should I reinstall both or one of those?
lxpolkit
and
polkit-gnome-authentication-agent-1
Ok, show me:
apt-cache policy policykit-1-gnome
apt-cache policy lxpolkit
and:
pidof lxqt-policykit-agent
apt-cache policy lxqt-policykit
Quote from: pavroo on January 09, 2018, 03:54:06 PM
Ok, show me:
apt-cache policy policykit-1-gnome
apt-cache policy lxpolkit
and:
pidof lxqt-policykit-agent
apt-cache policy lxqt-policykit
$ apt-cache policy policykit-1-gnome
apt-cache policy policykit-1-gnome
$ apt-cache policy lxpolkit
lxpolkit:
Installed: 0.5.3-2
Candidate: 0.5.3-2
Version table:
*** 0.5.3-2 500
500 http://ftp.debian.org/debian testing/main amd64 Packages
100 /var/lib/dpkg/status
$ pidof lxqt-policykit-agent
Nothing
$ apt-cache policy lxqt-policykit
lxqt-policykit:
Installed: (none)
Candidate: 0.12.0-3
Version table:
0.12.0-3 500
500 http://ftp.debian.org/debian testing/main amd64 Packages
Synaptic shows nothing when I search on "lxqt-policykit-agent"
ok, what about:
apt-cache policy policykit-1-gnome
it's not completed
Quote from: pavroo on January 09, 2018, 04:08:18 PM
ok, what about:
apt-cache policy policykit-1-gnome
it's not completed
$ apt-cache policy policykit-1-gnome
policykit-1-gnome:
Installed: 0.105-6
Candidate: 0.105-6
Version table:
*** 0.105-6 500
500 http://ftp.debian.org/debian testing/main amd64 Packages
100 /var/lib/dpkg/status
Ok, the point is that sparky-polkit runs policykit-1-gnome or lxpolkit whatever you have installed, but... no one runs on your machine, so...
Try to run it manualy to find where is a problem (in a terminal emulator to see output):
sparky-polkit
then:
pidof polkit-gnome-authentication-agent-1
if the output shows pid number - it's ok, try to mount your ntfs disk/partition.
If not, run:
/usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1
then:
pidof polkit-gnome-authentication-agent-1
if the output shows pid number - it's ok, try to mount your ntfs disk/partition.
and let me know whatever happend.
Quote from: pavroo on January 09, 2018, 04:17:43 PM
Ok, the point is that sparky-polkit runs policykit-1-gnome or lxpolkit whatever you have installed, but... no one runs on your machine, so...
Try to run it manualy to find where is a problem (in a terminal emulator to see output):
sparky-polkit
[quote/]
$ sparky-polkit
shows:
$ Xlib: extension "GLX" missing on display ":0.0".
That's the problem (at least to start with).
ok, what about the second one?
If not, run:
/usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1
then:
pidof polkit-gnome-authentication-agent-1
or run:
lxpolkit
$ pidof polkit-gnome-authentication-agent-1
returns
6701
And all of a sudden everything works!
ok, so add the line:
/usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1 &
to the file:
~HOME/.config/openbox/autostart.sh
Then reboot to check it out.
talking about the Xlib error, check here:
http://forums.debian.net/viewtopic.php?f=6&t=73028
Running sparky-polkit seemed to fix it.
Now I get no error message when I run it-
Do I still need to add:
/usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1 &
to the fil
to the .config/openbox/autostart.sh
File?
If you haven't added the line to openbox autostart yet, but after rebooting everything works - you do not have to add it.
Quote from: pavroo on January 09, 2018, 05:03:36 PM
If you haven't added the line to openbox autostart yet, but after rebooting everything works - you do not have to add it.
You did a great job, pavroo.
Much appreciated.
Sparky is the best debian derivative by far and the most complete OS I have installed, at present.
It's what I use most (except for the rare times it is down).
My system is now working but not as it should be.
Although I followed your (pavroo's) instructions, polkit is not autoloading.
That's not a big problem since I run the xfce4-panel at bottom and loaded what I need to do first to it's favorites list.
Tint2 (up top) doesn't load either so I load that first and from there run sparky-polkit with gexec.
My wallpaper doesn't load either so I run Nitrogen also from the favorites list.
The system is hanging up more often causing me to reboot.
Which polkit is best?
I purchased a new hard drive Saturday and may reinstall the most multimedia edition from scratch.
Would it run well with either a large Btrfs or ZFS partition, or is ext4 recommended?
Thanks in advance.
Quote from: dhinds on January 11, 2018, 08:27:27 AM
My system is now working but not as it should be.
Although I followed your (pavroo's) instructions, polkit is not autoloading.
That's not a big problem since I run the xfce4-panel at bottom and loaded what I need to do first to it's favorites list.
Tint2 (up top) doesn't load either so I load that first and from there run sparky-polkit with gexec.
My wallpaper doesn't load either so I run Nitrogen also from the favorites list.
The system is hanging up more often causing me to reboot.
Which polkit is best?
I purchased a new hard drive Saturday and may reinstall the most multimedia edition from scratch.
Would it run well with either a large Btrfs or ZFS partition, or is ext4 recommended?
Thanks in advance.
dhimbs ?
can you explain . what debian you have installed ? 4 or 5?
personally I have installed sparky stable 4(xfce) times ago. No problem at all.
my advice.
install one version. do not mix things ( some people install one version/desktop and mix with other things from other desktops. for example - one insyall lxde or lxqt desktop and after mix with utilities from xfce )
about hanging and reboot.
are you sure that distro you downloaded has right HASH?( check md5 or other hash).
are you sure that you have no any problem with heating, memory and so on.
can you post your inxi -F?
If you change nothing in your openbox autostart.sh, the most probably problem would be with broken updates, so show me:
sudo apt update
sudo apt full-upgrade
dhimbs ?
can you explain . what debian you have installed ? 4 or 5?
personally I have installed sparky stable 4(xfce) times ago. No problem at all.
my advice.
install one version. do not mix things ( some people install one version/desktop and mix with other things from other desktops. for example - one insyall lxde or lxqt desktop and after mix with utilities from xfce )
about hanging and reboot.
are you sure that distro you downloaded has right HASH?( check md5 or other hash).
are you sure that you have no any problem with heating, memory and so on.
can you post your inxi -F?
[/quote]
Thank you for your point of view and suggestions.
But Xfce, LXDE and LXQt are modular and I have been mixing them for years.
And am using Sparky Multimedia Testing which has no Desktop Environment.
Sparky is and has been for years the best (and only) Debian I use.
Thanks again.
Quote from: pavroo on January 11, 2018, 02:15:08 PM
If you change nothing in your openbox autostart.sh, the most probably problem would be with broken updates, so show me:
sudo apt update
sudo apt full-upgrade
I updated and upgraded yesterday with no problems other than what I mentioned above.
I'll try it again and post the results.
(The most probable cause of the problem ...)
if your upgrade went ok, but the openbox autostart doesn't start, so...
Run it manually:
~/.config/openbox/autostart.sh
show the output and say whatever happend.
Quote from: pavroo on January 11, 2018, 05:23:09 PM
if your upgrade went ok, but the openbox autostart doesn't start, so...
Run it manually:
~/.config/openbox/autostart.sh
show the output and say whatever happend.
Quote~$ show the output and say whatever
(nitrogen:2907): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
xscreensaver: 10:44:48: unknown option "--nosplash". Try "-help".
** (polkit-gnome-authentication-agent-1:2908): WARNING **: Unable to register authentication agent: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: An authentication agent already exists for the given subject
Cannot register authentication agent: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: An authentication agent already exists for the given subject
The program 'nitrogen' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
(Details: serial 1795 error_code 3 request_code 20 minor_code 0)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
and show me what is inside:
cat ~/.config/openbox/autostart.sh
Quote from: pavroo on January 11, 2018, 06:34:50 PM
and show me what is inside:
cat ~/.config/openbox/autostart.sh
Quote#! /bin/bash
nitrogen --restore && \
tint2 &
xscreensaver --nosplash &
/usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1 &dhinds@cmdddhddd
Quote** (polkit-gnome-authentication-agent-1:2908): WARNING **: Unable to register authentication agent: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: An authentication agent already exists for the given subject
Looks like the gnome-polkit agent works fine launched by sparky-polkit so remove the last line from the openbox/autostart.sh:
/usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1 &
Then relogin/reboot and let me know how is going.
Quote from: pavroo on January 11, 2018, 07:20:46 PM
Quote** (polkit-gnome-authentication-agent-1:2908): WARNING **: Unable to register authentication agent: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: An authentication agent already exists for the given subject
Looks like the gnome-polkit agent works fine launched by sparky-polkit so remove the last line from the openbox/autostart.sh:
/usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1 &
Then relogin/reboot and let me know how is going.
Remember that I am starting polkit manualy, each time I reboot by running <sparky-polkit> with gexec
I would have to do reboot first and run the command again, then send the results.
But since everything is functioning (albeit manually) and I am using the computer for tasks I need to finish with other people here, I'll have to wait on that. (Sparky is running on all the computers. This one is the main one but has always been more problematic).
You're doing a a great job, and it's appreciated.
Quote from: pavroo on January 11, 2018, 06:34:50 PM
and show me what is inside:
cat ~/.config/openbox/autostart.sh
I rebooted to the most recent amd64 kernel (I was using the liquorix), updated and upgraded and ran
cat ~/.config/openbox/autostart.sh
again, without activating sparky-polkit manually.
This what I got:
Quotenitrogen --restore && \
tint2 &
xscreensaver --nosplash &
/usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1 &dhinds@cmgx58i7:
Do you still think I should remove the last line from
Quoteopenbox/autostart.sh:
?
After rebooting, I observed that the Liquorix Kernel was what was upgraded.
Otherwise everything is as it was:
I had to load tint2, conky, the background and sparky-polkit manually (which isn't difficult).
The openbox autostart.sh loads tint2, conky and nitrogen (background).
If the tools don't start, the problem is with the autostart.sh script so revert it to default:
#! /bin/bash
nitrogen --restore && \
tint2 &
xscreensaver --nosplash &
then reboot and let me know what happend.
OK. But since the computer is in use I might have to wait until later today or tomorrow.
(The manual fixes are letting me get my work done for now).
Thanks again pavroo for demonstrating why Sparky is the best debian derivative. The performance is there and the support is too.
Quote from: pavroo on January 12, 2018, 03:05:53 PM
The openbox autostart.sh loads tint2, conky and nitrogen (background).
If the tools don't start, the problem is with the autostart.sh script so revert it to default:
#! /bin/bash
nitrogen --restore && \
tint2 &
xscreensaver --nosplash &
then reboot and let me know what happend.
This is what I got before rebooting:
Quotedhinds# ! /bin/bash
root@cmgx58i7:/home/dhinds# nitrogen --restore && \
> tint2 &
[1] 2215
root@cmgx58i7:/home/dhinds# xscreensaver --nosplash &
(nitrogen:2216): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
Could not get bg groups from config file.
tint2: xRandr: Found crtc's: 2
tint2: xRandr: Linking output VGA-0 with crtc 0
tint2: xRandr: crtc 1 seems disabled
tint2: No XSETTINGS manager, tint2 uses config option 'launcher_icon_theme'.
tint2: could not find a config file! Creating a default one.
tint2: Loading config file: /root/.config/tint2/tint2rc
tint2: deprecated config option "primary_monitor_first"
Please see the documentation regarding the alternatives.
tint2: real transparency off.... depth: 24
tint2: panel items: LTSC
tint2: Systray composited rendering off
tint2: systray_asb forced to 100 0 0
tint2: nb monitors 1, nb monitors used 1, nb desktops 10
tint2: Could not open file /root/.local/share/applications/tint2conf.desktop
tint2: Could not open file /usr/local/share/applications/tint2conf.desktop
tint2: Loading icon theme cache...
Icon path not found in cache: theme = hicolor, icon = tint2conf, size = 24
tint2: Loading icon theme hicolor:
tint2: 'hicolor',tint2:
Adding icon path to cache: theme = hicolor, icon = tint2conf, size = 24, path = /usr/share/icons/hicolor/scalable/apps/tint2conf.svg
tint2: Could not open file /root/.local/share/applications/firefox.desktop
tint2: Could not open file /usr/local/share/applications/firefox.desktop
tint2: Could not open file /usr/share/applications/firefox.desktop
tint2: Could not open file /usr/share/applications/kde4/firefox.desktop
tint2: Could not open file /usr/share/applications/screensavers/firefox.desktop
tint2: Could not open file /opt/share/applications/firefox.desktop
tint2: Could not open file /root/.local/share/applications/iceweasel.desktop
tint2: Could not open file /usr/local/share/applications/iceweasel.desktop
tint2: Could not open file /usr/share/applications/iceweasel.desktop
tint2: Could not open file /usr/share/applications/kde4/iceweasel.desktop
tint2: Could not open file /usr/share/applications/screensavers/iceweasel.desktop
tint2: Could not open file /opt/share/applications/iceweasel.desktop
tint2: Could not open file /root/.local/share/applications/chromium-browser.desktop
tint2: Could not open file /usr/local/share/applications/chromium-browser.desktop
tint2: Could not open file /usr/share/applications/chromium-browser.desktop
tint2: Could not open file /usr/share/applications/kde4/chromium-browser.desktop
tint2: Could not open file /usr/share/applications/screensavers/chromium-browser.desktop
tint2: Could not open file /opt/share/applications/chromium-browser.desktop
tint2: Could not open file /root/.local/share/applications/google-chrome.desktop
tint2: Could not open file /usr/local/share/applications/google-chrome.desktop
tint2: Could not open file /usr/share/applications/google-chrome.desktop
tint2: Could not open file /usr/share/applications/kde4/google-chrome.desktop
tint2: Could not open file /usr/share/applications/screensavers/google-chrome.desktop
tint2: Could not open file /opt/share/applications/google-chrome.desktop
tint2: Kernel uevent interface initialized...
Icon path not found in cache: theme = hicolor, icon = tint2conf, size = 22
Adding icon path to cache: theme = hicolor, icon = tint2conf, size = 22, path = /usr/share/icons/hicolor/scalable/apps/tint2conf.svg
tint2: Could not find icon '(null)', using default.
Icon path not found in cache: theme = hicolor, icon = application-x-executable, size = 22
tint2: Icon not found in default theme: application-x-executable
tint2: Loading additional icon themes (this means your icon theme is incomplete)...
tint2: 'breeze-dark',tint2:
tint2: 'default',tint2: 'Adwaita',tint2:
tint2: 'Tango',tint2: 'gnome',tint2: 'crystalsvg',tint2:
tint2: 'HighContrast',tint2:
tint2: 'default.kde4',tint2:
tint2: 'ultra-flat-icons',tint2:
tint2: 'oxygen',tint2:
tint2: 'breeze',tint2:
Adding icon path to cache: theme = hicolor, icon = application-x-executable, size = 22, path = /usr/share/icons/breeze-dark/mimetypes/22/application-x-executable.svg
tint2: Could not find icon '(null)', using default.
tint2: Could not find icon '(null)', using default.
tint2: Could not find icon '(null)', using default.
tint2: Saving icon theme cache...
tint2: another systray is running, cannot use systraytint2: pid=1754
(I had opened tint2 manually before that).
I ran this in two steps:
First:
! /bin/bash
as root.
Then the rest, together
Now I am going to reboot.
A suggestion to fix your problem would be to install alternatives to see how they work with your system and preferences.
Try changing the display manager from gdm to lightdm, I went from gdm to lightdm to sddm.
Change openbox to another desktop and window manager. From the basic SparkyLXQT 64 I'm on a now very solid kdeplasma with kwin and sddm.
Conky? -Uninstalled 12 months ago after it began using up all my cpu resources.
Tint2?- No longer necessary if not using openbox.
#! Those are the programs I used when I bought my EEE and fell in love with openbox and crunchbang, time flies - 7 years?
In apt full-upgrade today on sparky machine openbox was upgraded.
From http://metadata.ftp-master.debian.org/changelogs/main/o/openbox/openbox_3.6.1-6_changelog
openbox (3.6.1-6) unstable; urgency=medium
+ Move openbox-menu to Recommends. (Closes: #872983)
* Drop depends on gconf2: (Closes: #886050 LP: #1740420)
https://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=openbox;dist=unstable
Note: affects me not as I have deprecated openbox in favour of xfwm4 for lxqt. But, nice to see more work on openbox. It is still a click away for me as an option.
I did a quick search at BunsenLabs Forum (no one is more into tint2, nitrogen and openbox than them) and did not see anything new from them in the last week or two since I was by.
Conky on my Debian stable lets me know it is -22C in Winterpeg MB CA. I took it off of the eee and aspire, for cpu cycles. There was the big change in scripting for a year or two back. Bunsenlabs has 32 pages in forum on conky.
Tint2 is ancient and has had minimal slow development - but 7 pages in Bunsenlabs over Tint2 15.2.
Nitrogen was always very dependable, but I have not used in awhile.
Quote from: Wombat on January 14, 2018, 01:48:20 AM
A suggestion to fix your problem would be to install alternatives to see how they work with your system and preferences.
Try changing the display manager from gdm to lightdm, I went from gdm to lightdm to sddm.
Change openbox to another desktop and window manager. From the basic SparkyLXQT 64 I'm on a now very solid kdeplasma with kwin and sddm.
Conky? -Uninstalled 12 months ago after it began using up all my cpu resources.
Tint2?- No longer necessary if not using openbox.
Since I installed a new hard drive recently I could try a fresh installation of sparky testing kde plasma but my personal take on the situation (FLOSS) in general and GNU/Linux in particular is that the most lamentable aspect is precisely the incompatibilities, discrepancies and redundancies present between GTK and Qt.
That where openbox comes in as an alternative for a full (and fully committed) desktop environment. And I think both pavroo and Hong Jen Yee recognize this and striving to maintain both compatibility and diversity through the use of modular systems.
I'm using the Sparky Multimedia edition since it follows that orientation.
And I'm considering doing a fresh install on a journaling partition that saves snapshots than can be fallen back on, like btrfsn, zfs or nilfs2 - but I'm not sure which of those is supported by debian best.
Quote from: paxmark1 on January 14, 2018, 05:33:41 AM
#! Those are the programs I used when I bought my EEE and fell in love with openbox and crunchbang, time flies - 7 years?
In apt full-upgrade today on sparky machine openbox was upgraded.
From http://metadata.ftp-master.debian.org/changelogs/main/o/openbox/openbox_3.6.1-6_changelog
openbox (3.6.1-6) unstable; urgency=medium
+ Move openbox-menu to Recommends. (Closes: #872983)
* Drop depends on gconf2: (Closes: #886050 LP: #1740420)
https://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=openbox;dist=unstable
Note: affects me not as I have deprecated openbox in favour of xfwm4 for lxqt. But, nice to see more work on openbox. It is still a click away for me as an option.
I did a quick search at BunsenLabs Forum (no one is more into tint2, nitrogen and openbox than them) and did not see anything new from them in the last week or two since I was by.
Conky on my Debian stable lets me know it is -22C in Winterpeg MB CA. I took it off of the eee and aspire, for cpu cycles. There was the big change in scripting for a year or two back. Bunsenlabs has 32 pages in forum on conky.
Tint2 is ancient and has had minimal slow development - but 7 pages in Bunsenlabs over Tint2 15.2.
Nitrogen was always very dependable, but I have not used in awhile.
I don't mind activating the background, tint2, polkit and conky manually. The problem is that the system is hanging up - freezing on me regularly and I'm not sure how to determine what's causing that. I suppose there's a log that could show this.
If I can't correct it I'll have to attempt a fresh installation (as I mentioned above to wombat, I'm considering doing a fresh install on a journaling partition that saves snapshots than can be fallen back on, like btrfsn, zfs or nilfs2 - but I'm not sure which of those is supported by debian best.
Small suggestion - remove tint2 from the openbox autostart.sh - you use xfce4-panel if I remember well, so it should look like:
#! /bin/bash
nitrogen --restore && \
#tint2 &
xscreensaver --nosplash &
Quote from: pavroo on January 14, 2018, 12:43:48 PM
Small suggestion - remove tint2 from the openbox autostart.sh - you use xfce4-panel if I remember well, so it should look like:
#! /bin/bash
nitrogen --restore && \
#tint2 &
xscreensaver --nosplash &
There is no openbox-autostart.sh
The results of a catfish files search shows an "openbox-autostart" in
/usr/lib/x86_64-linux-gnu
The contents of that file are:
#!/bin/sh
# Set a background color
BG=""
if which hsetroot >/dev/null 2>/dev/null; then
BG=hsetroot
elif which esetroot >/dev/null 2>/dev/null; then
BG=esetroot
elif which xsetroot >/dev/null 2>/dev/null; then
BG=xsetroot
fi
#test -z $BG || $BG -solid "#303030"
GLOBALAUTOSTART="/etc/xdg/openbox/autostart"
AUTOSTART="${XDG_CONFIG_HOME:-"$HOME/.config"}/openbox/autostart"
# Run the global openbox autostart script
if test -f $GLOBALAUTOSTART; then
sh $GLOBALAUTOSTART
elif test -f $GLOBALAUTOSTART.sh; then
sh $GLOBALAUTOSTART.sh
fi
# Run the user openbox autostart script
if test -f $AUTOSTART; then
sh $AUTOSTART
elif test -f $AUTOSTART.sh; then
sh $AUTOSTART.sh
fi
# Run the XDG autostart stuff. These are found in /etc/xdg/autostart and
# in $HOME/.config/autostart. This requires PyXDG to be installed.
# See openbox-xdg-autostart --help for more details.
if which xdg-autostart >/dev/null 2>/dev/null; then
CMD=xdg-autostart
else
CMD=/usr/lib/x86_64-linux-gnu/openbox-xdg-autostart
fi
exec $CMD "$@"
Yes, there is, still the same, we talk about for a while:
~/.config/openbox/autostart.sh
Quote from: pavroo on January 14, 2018, 02:33:11 PM
Yes, there is, still the same, we talk about for a while:
~/.config/openbox/autostart.sh
You mean the one in
/home/dhinds/.config/openbox
The contents of that one is:
#! /bin/bash
nitrogen --restore && \
tint2 &
xscreensaver --nosplash &
/usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1 &
So it should read:
#! /bin/bash
nitrogen --restore && \
xscreensaver --nosplash &
/usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1 &
Removing:
tint2 &
Is that correct?
Yes:
/home/dhinds/.config/openbox/autostart.sh
If you use xfce4-panel and load it manulaly, I suggest to change tint2 to xfce4-panel so you do not have to load it manually.
Simply set the /home/dhinds/.config/openbox/autostart.sh file as follow:
#! /bin/bash
nitrogen --restore && \
xfce4-panel &
xscreensaver --nosplash &
/usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1 &
save the file, reboot and tell me whatever happend.
Don't load anything manually, the autostart script has to do that for you.
The xfce4-panel is the only one that DOES load automatically when I boot Sparky Multimedia and that is what makes loading the other ones easy since I use the whisker menu and have them included as "favorites".
Once tint2 is loaded, it has a gexec button which has "sparky-polkit"
already typed.
The catfish file search results on "/" didn't show autostart.sh.
But using spacefm file search and including hidden files did
So set the /home/dhinds/.config/openbox/autostart.sh file as follow:
#! /bin/bash
nitrogen --restore && \
xscreensaver --nosplash &
/usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1 &
then save the file and reboot.
And don't load anything manually.
Doing that now.
I have also been updating and upgrading continuously (daily) and sio far during this session nothing has frozen.
When you do that and reboot, with no loading extra scripts by you, show me:
pidof polkit-gnome-authentication-agent-1
and tell does the wallpaper start itself?
Quote from: pavroo on January 14, 2018, 03:14:32 PM
So set the /home/dhinds/.config/openbox/autostart.sh file as follow:
#! /bin/bash
nitrogen --restore && \
xscreensaver --nosplash &
/usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1 &
then save the file and reboot.
And don't load anything manually.
After changing autostart.sh and rebooting the same situation persists:
Nothing except the xfce4-panel loads automatically. Everything else has to loaded manually (which is easy, as I described it:
tint2 is loaded via the whisker menu's favorites;
tint2's gexec icon loads sparky-polkit.
and nitrogen and conky are loaded via the whisker menu's favorites.
Having to do that is not a major problem.
However, I may do a fresh installation of Sparky Mult-Media on the new hard drive and wondered if support is there from debian for a partition format that creates snapshots (i.e. btrfs, zfs or nilfs2).
What do you know about that?
I am aware that debian has worked on adding zfs support but don't know how far along it is. (I did add native zfs capacity to the liquorix kernel for it via synaptic already, though).
Can you show me:
ls -l ~/.config/openbox/autostart.sh
Quote from: pavroo on January 14, 2018, 04:21:03 PM
Can you show me:
ls -l ~/.config/openbox/autostart.sh
-rwxr-xr-x 1 dhinds dhinds 129 Jan 14 08:55 /home/dhinds/.config/openbox/autostart.sh
It's ok, but... the script doesn't load the tools it should. Never seen before that it doesn't launch tools.
I have no more ideas, sorry, give up.
Quote from: pavroo on January 14, 2018, 04:31:00 PM
It's ok, but... the script doesn't load the tools it should. Never seen before that it doesn't launch tools.
I have no more ideas, sorry, give up.
In the same location there is an autostart file (without the .sh).
That is available via the "Advanced Settings > Openbox > Openbox Autostart" menus that appear when right clicking on the desktop.
The contents of that are:
xfce4-panel
sparky-polkit
tint2
But only the xfce4-panel loads.
What can you tell me about debian support for btrfs, zfs or nilfs2?
If the support for one or more of those is there, installing to one would provide snapshots to fall back to.
Aaaaaaaa.........
You have two autostart files...
Openbox reads the autostart (with no "sh" extension) as first.
The first line is xfce4-panel, thats why it loads it itself, but the file is not set properly so next lines commands don't start.
So...
Go to /home/dhinds/.config/openbox directory
Delete /home/dhinds/.config/openbox/autostart file.
Edit /home/dhinds/.config/openbox/autostart.sh file and set is as follow:
#! /bin/bash
nitrogen --restore && \
xfce4-panel &
xscreensaver --nosplash &
/usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1 &
then reboot and let me know what happend.
don't start sparky-polkit manually, have to know is gnome-polkit started itself, so check:
pidof polkit-gnome-authentication-agent-1
QuoteWhat can you tell me about debian support for btrfs, zfs or nilfs2?
sorry, you have to check it at Debian's wiki or so.
Doing that now.
Rebooting.
Now everything loads except tint2
Good Job, pavroo.
(So Sparky is not designed for use with btrfs or zfs)?
If you need tint2 to be loaded, simply add it to the /home/dhinds/.config/openbox/autostart.sh
tint2 &
on the end ot the file.
Btrfs status check here:
https://wiki.debian.org/Btrfs
zfs:
https://github.com/zfsonlinux/zfs/wiki/Debian
Quote from: pavroo on January 14, 2018, 05:37:08 PM
If you need tint2 to be loaded, simply add it to the /home/dhinds/.config/openbox/autostart.sh
tint2 &
on the end ot the file.
Btrfs status check here:
https://wiki.debian.org/Btrfs
zfs:
https://github.com/zfsonlinux/zfs/wiki/Debian
Perfect.
Thanks a lot, pavroo.
Once again you have demonstrated conclusively why Sparky is the best debian derivative available.