Advertising

Author Topic: Upgrade Problem  (Read 1764 times)

Offline dhinds

  • Full Member
  • ***
  • Posts: 236
Re: Upgrade Problem
« Reply #30 on: January 11, 2018, 05:46:57 pm »
if your upgrade went ok, but the openbox autostart doesn't start, so...
Run it manually:
Code: [Select]
~/.config/openbox/autostart.shshow 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.)

Offline pavroo

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 1821
    • SparkyLinux
Re: Upgrade Problem
« Reply #31 on: January 11, 2018, 06:34:50 pm »
and show me what is inside:
Code: [Select]
cat ~/.config/openbox/autostart.sh
Nothing is easy as it looks.
Danielle Steel

Offline dhinds

  • Full Member
  • ***
  • Posts: 236
Re: Upgrade Problem
« Reply #32 on: January 11, 2018, 06:37:51 pm »
and show me what is inside:
Code: [Select]
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

Offline pavroo

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 1821
    • SparkyLinux
Re: Upgrade Problem
« Reply #33 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:
Code: [Select]
/usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1 &Then relogin/reboot and let me know how is going.
Nothing is easy as it looks.
Danielle Steel

Offline dhinds

  • Full Member
  • ***
  • Posts: 236
Re: Upgrade Problem
« Reply #34 on: January 11, 2018, 07:36:52 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:
Code: [Select]
/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.

Offline dhinds

  • Full Member
  • ***
  • Posts: 236
Re: Upgrade Problem
« Reply #35 on: January 12, 2018, 01:43:54 am »
and show me what is inside:
Code: [Select]
cat ~/.config/openbox/autostart.sh

I rebooted to the most recent amd64 kernel (I was using the liquorix), updated and upgraded  and ran
Code: [Select]
cat ~/.config/openbox/autostart.shagain, without activating sparky-polkit manually.

This what I got:

Quote
nitrogen --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
Quote
openbox/autostart.sh:
?


Offline dhinds

  • Full Member
  • ***
  • Posts: 236
Re: Upgrade Problem
« Reply #36 on: January 12, 2018, 02:02:07 am »

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).

Offline pavroo

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 1821
    • SparkyLinux
Re: Upgrade Problem
« Reply #37 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:
Code: [Select]
#! /bin/bash

nitrogen --restore && \
tint2 &
xscreensaver --nosplash &

then reboot and let me know what happend.
Nothing is easy as it looks.
Danielle Steel

Offline dhinds

  • Full Member
  • ***
  • Posts: 236
Re: Upgrade Problem
« Reply #38 on: January 12, 2018, 11:10:40 pm »
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.

Offline dhinds

  • Full Member
  • ***
  • Posts: 236
Re: Upgrade Problem
« Reply #39 on: January 14, 2018, 12:09:40 am »
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:
Code: [Select]
#! /bin/bash

nitrogen --restore && \
tint2 &
xscreensaver --nosplash &

then reboot and let me know what happend.

This is what I got before rebooting:

Quote
dhinds# ! /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:

Code: [Select]
! /bin/bash
as root.

Then the rest, together

Now I am going to reboot.

Offline Wombat

  • Jr. Member
  • **
  • Posts: 53
Re: Upgrade Problem
« Reply #40 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.



Offline paxmark1

  • Sr. Member
  • ****
  • Posts: 349
Re: Upgrade Problem
« Reply #41 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. 
Don't make a FrankenDebian

Offline dhinds

  • Full Member
  • ***
  • Posts: 236
Re: Upgrade Problem
« Reply #42 on: January 14, 2018, 10:26:33 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.

Offline dhinds

  • Full Member
  • ***
  • Posts: 236
Re: Upgrade Problem
« Reply #43 on: January 14, 2018, 10:37:22 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.


Offline pavroo

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 1821
    • SparkyLinux
Re: Upgrade Problem
« Reply #44 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:
Code: [Select]
#! /bin/bash

nitrogen --restore && \
#tint2 &
xscreensaver --nosplash &
Nothing is easy as it looks.
Danielle Steel