The officially official Devuan Forum!

You are not logged in.

#1 Re: Hardware & System Configuration » [SOLVED] WD MyBook Live with Devuan » 2022-04-13 06:14:27

You may find this helpful.

nfotinks.com/clone-partition-tables-gpt-mbr-sfdisk-sgdisk/

#2 Re: Desktop and Multimedia » Rhythmbox throwing error after update/upgrade » 2022-02-04 22:39:37

Head_on_a_Stick wrote:

Have you tried full-upgrade? It might be needed for a "clean" upgrade. But it might also break things more.

Random things breaking is to be expected when running ceres. That's why it's also called "unstable" wink

Safe-upgrade updated all possible packages available. 

I've run sid and ceres for decades and I'm still almost always surprised at package breakage.  It just doesn't happen very often.  And almost always happens when there is a backlog of packages that can't be full-upgraded due to major system package upgrades. 

Must be really great to be as smart and knowledgeable as you.

#3 Desktop and Multimedia » Rhythmbox throwing error after update/upgrade » 2022-02-04 20:58:08

garyk
Replies: 3

I bought a new audio cd a few days ago and ripped it to my hard drive collection which I use Rhythmbox to play my music collection.  The new album played fine.

This morning I did an aptitude update/upgrade and after that Rhythmbox throws an error every time I play that one new album:  "Your Gstreamer installation is missing a plugin".

I am running ceres. Here is the output from the aptitude update/upgrade.

  aptitude safe-upgrade
Resolving dependencies...                
The following NEW packages will be installed:
  libldacbt-enc2{a} libopenaptx0{a} 
The following packages will be REMOVED:
  libmms0{u} libofa0{u} 
The following packages will be upgraded:
  gir1.2-gst-plugins-base-1.0 gir1.2-gstreamer-1.0 gstreamer1.0-alsa gstreamer1.0-gl gstreamer1.0-gtk3 gstreamer1.0-libav gstreamer1.0-plugins-bad gstreamer1.0-plugins-base 
  gstreamer1.0-plugins-good gstreamer1.0-plugins-ugly gstreamer1.0-pulseaudio gstreamer1.0-x libgstreamer-gl1.0-0 libgstreamer-plugins-bad1.0-0 libgstreamer-plugins-base1.0-0 
  libgstreamer1.0-0 
16 packages upgraded, 2 newly installed, 2 to remove and 0 not upgraded.
Need to get 29.3 MB of archives. After unpacking 3,331 kB will be used.
Do you want to continue? [Y/n/?] 
Get: 1 http://deb.devuan.org/merged ceres/main amd64 libgstreamer1.0-0 amd64 1.20.0-1 [2,289 kB]
Get: 2 http://deb.devuan.org/merged ceres/main amd64 libgstreamer-plugins-base1.0-0 amd64 1.20.0-1 [2,261 kB]
Get: 3 http://deb.devuan.org/merged ceres/main amd64 gstreamer1.0-plugins-good amd64 1.20.0-2 [3,310 kB]
Get: 4 http://deb.devuan.org/merged ceres/main amd64 gstreamer1.0-plugins-ugly amd64 1.20.0-1 [401 kB]
Get: 5 http://deb.devuan.org/merged ceres/main amd64 gstreamer1.0-gtk3 amd64 1.20.0-2 [1,436 kB]
Get: 6 http://deb.devuan.org/merged ceres/main amd64 gstreamer1.0-gl amd64 1.20.0-1 [1,518 kB]
Get: 7 http://deb.devuan.org/merged ceres/main amd64 gstreamer1.0-plugins-bad amd64 1.20.0-2 [4,589 kB]
Get: 8 http://deb.devuan.org/merged ceres/main amd64 gstreamer1.0-plugins-base amd64 1.20.0-1 [2,065 kB]
Get: 9 http://deb.devuan.org/merged ceres/main amd64 libgstreamer-gl1.0-0 amd64 1.20.0-1 [1,590 kB]
Get: 10 http://deb.devuan.org/merged ceres/main amd64 libgstreamer-plugins-bad1.0-0 amd64 1.20.0-2 [2,545 kB]
Get: 11 http://deb.devuan.org/merged ceres/main amd64 libldacbt-enc2 amd64 2.0.2.3+git20200429+ed310a0-4 [24.6 kB]
Get: 12 http://deb.devuan.org/merged ceres/main amd64 libopenaptx0 amd64 0.2.0-6 [14.2 kB]
Get: 13 http://deb.devuan.org/merged ceres/main amd64 gir1.2-gstreamer-1.0 amd64 1.20.0-1 [1,242 kB]
Get: 14 http://deb.devuan.org/merged ceres/main amd64 gir1.2-gst-plugins-base-1.0 amd64 1.20.0-1 [1,498 kB]
Get: 15 http://deb.devuan.org/merged ceres/main amd64 gstreamer1.0-alsa amd64 1.20.0-1 [1,444 kB]
Get: 16 http://deb.devuan.org/merged ceres/main amd64 gstreamer1.0-libav amd64 1.20.0-1 [219 kB]
Get: 17 http://deb.devuan.org/merged ceres/main amd64 gstreamer1.0-pulseaudio amd64 1.20.0-2 [1,417 kB]
Get: 18 http://deb.devuan.org/merged ceres/main amd64 gstreamer1.0-x amd64 1.20.0-1 [1,482 kB]
Fetched 29.3 MB in 3s (8,637 kB/s)         
Reading changelogs... Done
(Reading database ... 294949 files and directories currently installed.)
Preparing to unpack .../00-libgstreamer1.0-0_1.20.0-1_amd64.deb ...
Unpacking libgstreamer1.0-0:amd64 (1.20.0-1) over (1.18.5-1) ...
Preparing to unpack .../01-libgstreamer-plugins-base1.0-0_1.20.0-1_amd64.deb ...
Unpacking libgstreamer-plugins-base1.0-0:amd64 (1.20.0-1) over (1.18.5-1) ...
Preparing to unpack .../02-gstreamer1.0-plugins-good_1.20.0-2_amd64.deb ...
Unpacking gstreamer1.0-plugins-good:amd64 (1.20.0-2) over (1.18.5-2) ...
Preparing to unpack .../03-gstreamer1.0-plugins-ugly_1.20.0-1_amd64.deb ...
Unpacking gstreamer1.0-plugins-ugly:amd64 (1.20.0-1) over (1.18.5-1) ...
Preparing to unpack .../04-gstreamer1.0-gtk3_1.20.0-2_amd64.deb ...
Unpacking gstreamer1.0-gtk3:amd64 (1.20.0-2) over (1.18.5-2) ...
Preparing to unpack .../05-gstreamer1.0-gl_1.20.0-1_amd64.deb ...
Unpacking gstreamer1.0-gl:amd64 (1.20.0-1) over (1.18.5-1) ...
Preparing to unpack .../06-gstreamer1.0-plugins-bad_1.20.0-2_amd64.deb ...
Unpacking gstreamer1.0-plugins-bad:amd64 (1.20.0-2) over (1.18.5-1+b4) ...
Preparing to unpack .../07-gstreamer1.0-plugins-base_1.20.0-1_amd64.deb ...
Unpacking gstreamer1.0-plugins-base:amd64 (1.20.0-1) over (1.18.5-1) ...
Preparing to unpack .../08-libgstreamer-gl1.0-0_1.20.0-1_amd64.deb ...
Unpacking libgstreamer-gl1.0-0:amd64 (1.20.0-1) over (1.18.5-1) ...
Preparing to unpack .../09-libgstreamer-plugins-bad1.0-0_1.20.0-2_amd64.deb ...
Unpacking libgstreamer-plugins-bad1.0-0:amd64 (1.20.0-2) over (1.18.5-1+b4) ...
Selecting previously unselected package libldacbt-enc2:amd64.
Preparing to unpack .../10-libldacbt-enc2_2.0.2.3+git20200429+ed310a0-4_amd64.deb ...
Unpacking libldacbt-enc2:amd64 (2.0.2.3+git20200429+ed310a0-4) ...
Selecting previously unselected package libopenaptx0:amd64.
Preparing to unpack .../11-libopenaptx0_0.2.0-6_amd64.deb ...
Unpacking libopenaptx0:amd64 (0.2.0-6) ...
(Reading database ... 294969 files and directories currently installed.)
Removing libmms0:amd64 (0.6.4-3) ...
Removing libofa0:amd64 (0.9.3-21) ...
(Reading database ... 294957 files and directories currently installed.)
Preparing to unpack .../0-gir1.2-gstreamer-1.0_1.20.0-1_amd64.deb ...
Unpacking gir1.2-gstreamer-1.0:amd64 (1.20.0-1) over (1.18.5-1) ...
Preparing to unpack .../1-gir1.2-gst-plugins-base-1.0_1.20.0-1_amd64.deb ...
Unpacking gir1.2-gst-plugins-base-1.0:amd64 (1.20.0-1) over (1.18.5-1) ...
Preparing to unpack .../2-gstreamer1.0-alsa_1.20.0-1_amd64.deb ...
Unpacking gstreamer1.0-alsa:amd64 (1.20.0-1) over (1.18.5-1) ...
Preparing to unpack .../3-gstreamer1.0-libav_1.20.0-1_amd64.deb ...
Unpacking gstreamer1.0-libav:amd64 (1.20.0-1) over (1.18.5-1) ...
Preparing to unpack .../4-gstreamer1.0-pulseaudio_1.20.0-2_amd64.deb ...
Unpacking gstreamer1.0-pulseaudio:amd64 (1.20.0-2) over (1.18.5-2) ...
Preparing to unpack .../5-gstreamer1.0-x_1.20.0-1_amd64.deb ...
Unpacking gstreamer1.0-x:amd64 (1.20.0-1) over (1.18.5-1) ...
Setting up libldacbt-enc2:amd64 (2.0.2.3+git20200429+ed310a0-4) ...
Setting up libopenaptx0:amd64 (0.2.0-6) ...
Setting up libgstreamer1.0-0:amd64 (1.20.0-1) ...
Setcap worked! gst-ptp-helper is not suid!
Setting up gir1.2-gstreamer-1.0:amd64 (1.20.0-1) ...
Setting up libgstreamer-plugins-base1.0-0:amd64 (1.20.0-1) ...
Setting up libgstreamer-plugins-bad1.0-0:amd64 (1.20.0-2) ...
Setting up libgstreamer-gl1.0-0:amd64 (1.20.0-1) ...
Setting up gstreamer1.0-plugins-base:amd64 (1.20.0-1) ...
Setting up gstreamer1.0-plugins-ugly:amd64 (1.20.0-1) ...
Setting up gstreamer1.0-libav:amd64 (1.20.0-1) ...
Setting up gstreamer1.0-gl:amd64 (1.20.0-1) ...
Setting up gstreamer1.0-x:amd64 (1.20.0-1) ...
Setting up gstreamer1.0-alsa:amd64 (1.20.0-1) ...
Setting up gstreamer1.0-plugins-good:amd64 (1.20.0-2) ...
Setting up gir1.2-gst-plugins-base-1.0:amd64 (1.20.0-1) ...
Setting up gstreamer1.0-gtk3:amd64 (1.20.0-2) ...
Setting up gstreamer1.0-plugins-bad:amd64 (1.20.0-2) ...
Setting up gstreamer1.0-pulseaudio:amd64 (1.20.0-2) ...
Processing triggers for libc-bin (2.33-5) ...

Current status: 0 (-16) upgradable.

Anyone have any idea as to what went wrong in the upgrade?

#4 Re: Desktop and Multimedia » [SOLVED] Delete track number from music file names » 2021-11-25 14:48:45

Just an fyi on renaming large numbers of files.  sed works really well.

#5 Re: Desktop and Multimedia » Beowulf is broken » 2021-05-25 20:13:11

golinux wrote:

Maybe a hardware issue?

I suppose that's one possible answer, but I have the same problem on Ceres.  If I try to run two different videos at the same type my system freezes solid.  The only way out is to press and hold down the power off button.  That's not a good option.

#6 Re: Other Issues » No updates for days (Chimaera), last time it was an issue for weeks... » 2021-03-24 22:04:10

I use ceres and have a what may be a related issue.

I spent more than 10 minutes trying to run an "aptitude update" on deb.devuan.org today which aptitude finally exited reporting a no connection error.  This is the worst it's been, but extremely slow updates have been happening on and off for a month or more. It's not been unusual for an update to take a couple of minutes to complete on a 150 megabit connection. Aptitude upgrade download speeds haven't been anything to write home about but have been at least around 1/2 of the normal speeds I have gotten up til now using Devuan. 

I've never seen updates take so long to complete in the approximately 20 years I've spent using first Debian and now Devuan.   

 aptitude update
Get: 1 http://deb.devuan.org/merged ceres InRelease [33.2 kB]
Get: 2 http://deb.devuan.org/merged ceres/main amd64 Packages [8,740 kB]
Ign http://deb.devuan.org/merged ceres/main amd64 Packages                                                                                                                  
Get: 3 http://deb.devuan.org/merged ceres/main amd64 Packages [8,740 kB]                                                                                                    
Get: 4 http://deb.devuan.org/merged ceres/main amd64 Packages [11.5 MB]                                                                                                     
Ign http://deb.devuan.org/merged ceres/main amd64 Packages                                                                                                                  
Get: 5 http://deb.devuan.org/merged ceres/main amd64 Packages [11.5 MB]
Err http://deb.devuan.org/merged ceres/main amd64 Packages                                                                                                                  
  Connection timed out [IP: 195.85.215.180 80]
Fetched 33.2 kB in 8min 21s (66 B/s)                                                                                                                                        
W: Failed to fetch http://deb.devuan.org/merged/dists/ceres/main/binary-amd64/Packages: Connection timed out [IP: 195.85.215.180 80]
E: Some index files failed to download. They have been ignored, or old ones used instead.
     

#7 Re: Installation » lost basic user account i think anyway » 2021-01-01 10:25:39

Have you checked to see if the /home/user directory has been created?

#8 Re: Other Issues » DeleteService » 2020-07-05 17:46:33

Thanks for the answers guys.  Unfortunately, or fortunately, as the case may be, on reboot the DeleteService process hasn't returned.  So any searches for it are now moot.  If it ever returns I'll try your suggestions and report what I find.  I do know it was running under my account but don't remember the PID.  It was just so weird that it didn't show up under ps -AF that it kind of threw me for a loop.  I've never seen a process that showed up under -e that didn't show up under the -AF options before.

#9 Other Issues » DeleteService » 2020-07-03 00:21:47

garyk
Replies: 3

When running atop a service titled DeleteService shows up near the top of the process list.  It also shows up if I run the following command from a bash prompt: ps -e | grep DeleteService.  All that shows though is that the process exists which is not a lot of help.  But, if I run ps -eF | grep DeleteService to find out more about it it does not show up in the list of running processes.  Nor does it show up running ps -AF | grep DeleteService. 

I've done some searches looking for this on the internet and can find nothing about this process.  I get some systemd returns to my searches but nothing about the DeleteService process itself.  Is this an artifact left over from removing systemd?  Or is this something else as to the best of my memory I can not remember ever seeing this process before.

#10 Re: Other Issues » Calibre bug » 2020-06-16 15:10:32

sgage wrote:
garyk wrote:
sgage wrote:

Hi garyk,

Just wanted to let you know of my latest exploits. I am thinking that the problem doesn't lie with Calibre, as such. In both Chimaera  and Debian bullseye (on which Chimaera is based), Calibre worked fine this morning. After a sizeable update, both exhibited the problem you describe - the reader window comes up for a second, then... gone. Calibre was not among the updated packages. There were a few python related odds and ends. I suspect an interaction with some new python component that hadn't been tested against. You just happened to get it before me.

I think you're right - we are probably going to see rapid updates of Calibre as it dances along with continuing component updates in Python.

Just to let you know, I did an upgrade tonight and the following python file was upgraded:  python3-pyqt5.qtwebengine (5.15.0-1.  Calibre is now working fine once again.  Good call on a python package being the problem.  cool

Hmmm... still on 5:14 here. I wonder why you get upgrades before I do? Luck of the draw on mirrors? I'll probably get it tomorrow. Good to know it's fixed - for now...  :-)

Here's the one and only non-commented out line in my /etc/apt/sources.list file:  deb http://deb.devuan.org/merged ceres main non-free contrib.

Before I went to this url I had problems getting timely updates after I moved to Devuan.  I'd sometimes have to wait a week or more before updates would percolate out to whatever mirror I was connecting to at the time.  If I didn't dislike systemd so much I'd have moved back to Debian and said goodby to Devuan over that source of frustration.  big_smile

#11 Re: Other Issues » Calibre bug » 2020-06-15 06:44:18

sgage wrote:

Hi garyk,

Just wanted to let you know of my latest exploits. I am thinking that the problem doesn't lie with Calibre, as such. In both Chimaera  and Debian bullseye (on which Chimaera is based), Calibre worked fine this morning. After a sizeable update, both exhibited the problem you describe - the reader window comes up for a second, then... gone. Calibre was not among the updated packages. There were a few python related odds and ends. I suspect an interaction with some new python component that hadn't been tested against. You just happened to get it before me.

I think you're right - we are probably going to see rapid updates of Calibre as it dances along with continuing component updates in Python.

Just to let you know, I did an upgrade tonight and the following python file was upgraded:  python3-pyqt5.qtwebengine (5.15.0-1.  Calibre is now working fine once again.  Good call on a python package being the problem.  cool

#12 Re: Other Issues » Calibre bug » 2020-06-15 05:50:50

sgage wrote:

Hi garyk,

Just wanted to let you know of my latest exploits. I am thinking that the problem doesn't lie with Calibre, as such. In both Chimaera  and Debian bullseye (on which Chimaera is based), Calibre worked fine this morning. After a sizeable update, both exhibited the problem you describe - the reader window comes up for a second, then... gone. Calibre was not among the updated packages. There were a few python related odds and ends. I suspect an interaction with some new python component that hadn't been tested against. You just happened to get it before me.

I think you're right - we are probably going to see rapid updates of Calibre as it dances along with continuing component updates in Python.

I'm glad to hear that this has shown up in Debian now as that ensures the bug will be fixed soon. 

Thanks for the info.  And yes, I expect Calibre will continue to be a bumpy road for a while as upgrading from Python 2 to Python 3 is not a trivial upgrade.

#13 Re: Other Issues » Calibre bug » 2020-06-14 02:51:52

sgage wrote:

OK, Calibre has no problems opening/reading epub and mobi on my ceres system. However, I seem to be running a slightly different version. The package version is 4.99.4+dfsg+really4.17.0-1. And apt update doesn't offer anything newer. And the program itself reports 4.99.5!

In any case, it's working nominally here...

I did an update yesterday in which Calibre was upgraded to the new version.  I suspect that's where the bug I'm experiencing came from as I use Calibre on a daily basis.  I was reading a pdf book yesterday so when I finished that book and went to read an epub book today that's when I ran into the problem. 

Calibre is moving from Python 2.x to 3.x and there have been a bunch of bugs affecting it in the last couple of months.  There have been frequent updates to it.  On my machine Calibre itself reports the same version as you see.  There are going to be a lot of 4.99.x versions during the Python upgrade as when the entire upgrade to Python 3 is finished Calibre will be termed version 5. Until then it's going to be version 4.99.x

#14 Re: Other Issues » Reportbug, again » 2020-06-13 17:35:56

I realized I left out the very important data of Devuan version and reportbug version.  ***brainfart***

I'm running Ceres and version number of reportbug is 7.6.0+devuan1.

#15 Re: Other Issues » Calibre bug » 2020-06-13 17:29:23

sgage wrote:
garyk wrote:

Calibre's internal viewer crashes upon opening any book no matter what the file format is.  The only books now readable are ones that use an external viewer such as pdf, doc, or odt files.  As I do a lot of reading and the vast majority of my books are in epub format this is a big deal to me as it makes more than 3100 of my books unavailable.

As reportbug also does not work I am using this site to report the bug.

I am not seeing this issue at all with epub or mobi. This is on an up-to-date beowulf installation. Calibre version 3.39.1.

My bad.  I should have given the version #.

I'm running Ceres and the Calibre version is 4.99.4+dfsg+really4.18.0-1.

#16 Other Issues » Calibre bug » 2020-06-13 15:17:52

garyk
Replies: 12

Calibre's internal viewer crashes upon opening any book no matter what the file format is.  The only books now readable are ones that use an external viewer such as pdf, doc, or odt files.  As I do a lot of reading and the vast majority of my books are in epub format this is a big deal to me as it makes more than 3100 of my books unavailable.

As reportbug also does not work I am using this site to report the bug.

#17 Other Issues » Reportbug, again » 2020-06-13 14:51:38

garyk
Replies: 1

I ran across a bug in calibre and tried to report it but ran into a bug in reportbug doing that.  So, as the only way open to me to report a bug is to post here here's the bug.

What I have run across is reportbug bypasses the page for actually entering the bug.  Here's what happens.

1.  Open reportbug and hit next.  Works as it should.
2. Enter name of package with bug and hit next.  Works as it should.
3. Enter problem in package and hit next.  Works as it should.
4.  Enter severity of bug and hit next.  Works as it should.
5.  Do any of the following apply to this report? Click on appropriate entry in list, if any.
6.  Hit next button on bottom of above page and reportbug goes to "Hit Enter to exit reportbug".  From there reportbug exits. 

There is no capability of filing any bugs.

#18 Re: Other Issues » Reportbug » 2020-06-13 14:33:56

fsmithred wrote:

Reportbug is partially broken. I believe you can use it to generate a report, but you have to email the report manually.

To submit a new bug report, send email to submit@bugs.devuan.org with a descriptive subject line and the first line of the body should be
Package: <package name>

Follow-up messages go to <number>@bugs.devuan.org

Thanks for this, belatedly.  I have been filing bug reports by doing that as it was the only way I could figure out how to send one.

#19 Re: Installation » (beowulf) no ALSA available? » 2020-03-06 00:38:28

I puzzled over getting alsa running too.  I believe the package I installed to get it running is the libasound2, plus whatever dependencies it pulled in with it.

edit: Plus once you get that you will need to install the alsamixergui package to set volume levels and the like.

#20 Other Issues » Reportbug » 2020-02-21 06:50:22

garyk
Replies: 3

I Filed a bug this evening using Reportbug.  I got a response saying I had sent the report to a list of which I am not a member and I should not report bugs to owner@bugs.devuan.org unless it is a bug in Reportbug.  That email address was supplied by default by Reportbug itself. 

I used Reportbug for almost 2 decades while running Debian and I've never seen this issue before.  Is this now the default Devuan configuration for Reportbug? Should I be chasing down package maintainer's email addresses and inserting them in Reportbug as a normal operation, or is this a bug specific to Devuan?   

I am running Ceres. 

The other issue I have with Reportbug is that my ISP provides only IMAP email with no possibility of a POP account and I cannot get Reportbug to work with the IMAP server.  I've configured it to use the correct ports, the correct password, the correct encryption, and the correct user name but attempted reports are always rejected by the IMAP server leaving me with the only option of creating the bug report file in /tmp and then copying it from there into an email and sending it that way.

Anyone else ever have this problem with configuring Reportbug to work with an IMAP server?  My default email client is Evolution.

#21 Re: Desktop and Multimedia » Very odd problem with Evolution (solved) » 2019-11-12 15:13:26

OK.  This is now solved.  I got some help from a Gnome developer on the Gnome evolution-list mailing list.  He said it was most likely a recent update that broke Evolution for me.

I have used Evolution for years but hadn't been into the Network Preferences tab inside Preferences in years as there wasn't really anything to set there before.  There's a new, or at least new to me, drop down list that gives several options for network detection.  I had to change from "default" to "base" to get wireless to start working again. It still throws the same error when starting Evolution from a bash prompt, but at least it is working now.  The other options on the list didn't work for me. 

So, if anyone else has Evolution network detection broken that drop down list is the solution.

#22 Re: Desktop and Multimedia » Very odd problem with Evolution (solved) » 2019-11-10 12:00:09

rolfie wrote:

A first look at gateway and DNS of the two connections?

Rolfie

Both wired and wireless connections are supplied by the same router.  So if I had gateway issues or DNS issues I couldn't be posting here as all internet access would be affected.  I'm posting here using wireless.  The only symptom is no wireless email using Evolution.  Everything else works fine.  I can get email over the wireless connection using kmail and both applications use the same wireless connection. 

The problem is specific to Evolution.  That is the only application that is having any issue related to wireless.

The problem, but I'm only guessing at this point, seems to me to be related to the behind the gui processes that evolution uses to access wireless networking.  It just doesn't seem logical to me though that it would use different processes to access wired and wireless networking.  It looks to me by the error reported in starting evolution from a bash prompt like some configuration file is corrupted somewhere in the process of starting Evolution because of the GTK warnings printed out.  But I know next to nothing about those processes.

#23 Re: Desktop and Multimedia » Very odd problem with Evolution (solved) » 2019-11-10 00:00:42

OK.  I found some info today from here.  You can see the result below when running the command.  Evolution will download email until it is closed and then on startup it will once again report the network outage when trying to connect to the wireless network. 

 GIO_USE_NETWORK_MONITOR=base evolution

(evolution:18079): Gtk-WARNING **: 15:25:41.507: Failed to register client: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: Method "RegisterClient" with signature "ss" on interface "org.xfce.Session.Manager" doesn't exist

(evolution:18079): evolution-util-WARNING **: 15:26:02.074: Nonsensical (120% complete) reported on activity "Fetching summary information for new messages in “username@isp.net : INBOX”"
   

Starting evolution this way after the first attempt reproduces the first error but not the second.  Starting it from the bash prompt or from the gui menu forces it offline once again.  The why of it failing to startup normally when using wireless and successfully starting up and reaching a wired connection baffles me.  Why would it produce the error in one mode and not the other?

#24 Desktop and Multimedia » Very odd problem with Evolution (solved) » 2019-11-09 19:45:40

garyk
Replies: 4

For the last couple of months I've had a problem where evolution could not reach my ISP's imap server.  It would work intermittently for a couple of weeks and then stop for a week or two, and then start up and work again consistently for a week or so.  Then two weeks ago all communication between Evolution and the email server stopped. 

In my efforts to solve this I finally tried directly wiring my laptop to my router.  Immediately success.  My email worked again.  Unplugged the ethernet cable and no more email.  I messed around purging evolution and reinstalling it with no joy.  I installed kmail and once again had email via wireless. 

Anyone else ever run across something like this before? 

I'm running Beowulf and it is up to date.

#25 Re: Hardware & System Configuration » [Solved] Webserver: connection refused » 2019-05-16 19:12:18

Rolf,

Just as an aside, if you are interested in learning a little more about the system startup/shutdown process in devuan check out the /etc/rc0-6.d and /etc/rcS.d directories with their startup and kill scripts.  What you will find in there are symbolic links pointing to the scripts found in /etc/init.d.  Their naming convention is such that the symbolic link names starting with an S are startup links.  The ones starting with a K are shutdown, or kill, links.  The update commands you were given add those links, but they hide what actually happens to modify the start up and shutdown procedures from the admin.  Sometimes to actually know what/where/how all of this actually works is good to know. 

One other nitpick is that running an /etc/init.d link does not require the "sh" at the start of the command.  All that is required is the path to the startup/shutdown/restart link and whatever command you're wanting to invoke such as start, restart, stop.  As long as the file you are pointing to from the bash prompt is an executable the sh command is optional.  For instance, to restart apache2, the apache webserver, all that is required is /etc/init.d/apache2 restart. 

If you read the LSB scripts in /etc/init.d at the very top of each script is the line #! /bin/sh.  That tells the system that this is an sh script, but if you check out the /bin directory, and the /bin/sh path specifically with ls -l it shows you that sh is a link to /bin/dash which the system uses to run scripts at start up as it's faster than bash.   

Just a little trivia but it all helps in understanding how your system starts up, runs, and shuts down.

Board footer

Forum Software