Choose style:

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - VandiumRoadrunner

Pages: [1] 2
1
New Users / Wget pdf's linked by .aspx files
« on: April 20, 2018, 12:27:46 pm »
Hello Neighbors!

I am trying to download a number pdfs on a physics education website http://websites.nylearns.org/bfejzo/2012/9/22/374140/page.aspx and usually I use some alternative of wget; however, I am really stuck because the pdf's are linked to a page.aspx file so when I used examples like.

Code: [Select]
wget -r -l 1 -nd -nH -A pdf http://websites.nylearns.org/bfejzo/2012/9/22/374140/page.aspx 

I get only a file; and options like

Code: [Select]
http://websites.nylearns.org/bfejzo/2012/9/22/374140/page.aspx

only gives me the directories with a .aspx file waiting at the end of it.

Help much appreciated! Thanks.


2
 ;D :D ;D

Hahaha....no, sadly no relation, friend or foe with CadmiumCoyote, but his stats on Battlefield 4 are quite nice!

Thank you so much for the tip, I was able to fix this in no time with your help, and in the process understand how to edit the OS on sourceforge bash scripts. Many thanks and cheers PCNetSpec.


3
Hey All,

I trying to install a software "Alltomp3" from the following website: https://alltomp3.org/, which should only take two steps:
1.
Code: [Select]
sudo pip install pathlib
2.
Code: [Select]
curl -s https://packagecloud.io/install/repositories/AllToMP3/alltomp3/script.deb.sh | sudo bash sudo apt-get install alltomp3

My issue though is that I get an error:
Code: [Select]
Detected operating system as Peppermint/xenial.
Checking for curl...
Detected curl...
Checking for gpg...
Detected gpg...
Running apt-get update... done.
Installing apt-transport-https... done.
Installing /etc/apt/sources.list.d/AllToMP3_alltomp3.list...curl: (22) The requested URL returned error: 404 Not Found


Unable to download repo config from: https://packagecloud.io/install/repositories/AllToMP3/alltomp3/config_file.list?os=Peppermint&dist=xenial&source=script

This usually happens if your operating system is not supported by
packagecloud.io, or this script's OS detection failed.

You can override the OS detection by setting os= and dist= prior to running this script.
You can find a list of supported OSes and distributions on our website: https://packagecloud.io/docs#os_distro_version

For example, to force Ubuntu Trusty: os=ubuntu dist=trusty ./script.sh

If you are running a supported OS, please email support@packagecloud.io and report this.

I understand that I need to override the OS settings, and I suppose I need to set it to os=ubuntu dist=xenial (I am currently using Peppermint 7 null) but I don't know how to do this. Literally I have been entering the following into the terminal:

Code: [Select]
os=ubuntu dist=trust curl -s https://packagecloud.io/install/repositories/AllToMP3/alltomp3/script.deb.sh
I know that this is incorrect, which is why I'd like to ask if anyone knows how to change these OS settings.

Many thanks!

4
New Users / Midori Browser Theme Help
« on: September 20, 2017, 05:13:34 pm »
Hello, and thank you for reading. I recently downloaded Midori, and I have found it to be a bit "flat" and not as shown on the website. It looks as if the Peppermint theme was the theme for the browser as all the borders are very dark. I was wondering if I could set up Midori through config files back as it should be as seen on the official website. Many thanks.

5
I installed PDF-Shuffler straight from the Peppermint's software manager.

6
 :D :D :D

Well Yippy! Master PDF EDITOR worked quite fine. I don't know what the issue was specially but this solved i! Thank you PCNetSpec!

7
 Hello Peppermint Community!

In the spring I used a wonderful application called PDF-Shuffler to merge and rotate .pdf files although it is able to crop and split .pdf’s as well. Recently I tried to rotate and merge some files that were scanned, and I got the following error

https://drive.google.com/file/d/0B-a93-EvfmviVGJPUmJTeW52ZTQ/view?usp=sharing


I checked if the software does anything else, and it does split .pdf’s no problem.

I downloaded PDFsam Basic and PDF Mod which are comparable programs, and they also are not able to do the specific function I am looking for. This suggests for me that there is something wrong at a foundational level (as in I am missing some library or something else), but that is all I know.

I would appreciate any help, and many thanks if you do!

8
Hardware / Re: Boot slow after battery was low
« on: April 23, 2017, 11:59:57 pm »
Hello PCNetSpec

I am writing to say that I have still been looking for a solution online, and I ran across an forum blog that you also assisted on https://linuxforums.org.uk/index.php?topic=12919.15

Can you comment on if the same strategy would work for me? Thanks again.

10
Hardware / Re: Boot slow after battery was low
« on: April 22, 2017, 05:28:06 pm »
sda5 is your Linux swap partition. It usually gets created automatically at installation and works similarly to the "page file" in Windows. I wouldn't worry about that, it's something that's supposed to be there and shouldn't cause an extra delay.

Thanks murraymint:)

11
Hardware / Re: Boot slow after battery was low
« on: April 21, 2017, 01:36:31 am »
On Wednesday when this all happened, I updated two things: Chrome and linux-tools-virtual-hwe-16.04-edge. Could the linux tools have something to do with, and if so could I uninstall the newest versions for the one before?

12
Hardware / Re: Boot slow after battery was low
« on: April 21, 2017, 12:37:50 am »
So I reread your questions, and I use wireless mostly. I don't "mount" anything as in a usb hotspot or anything like that.

13
Hardware / Re: Boot slow after battery was low
« on: April 20, 2017, 11:52:41 pm »
Hey PCNetSpec I really appreciate everything your doing. First, I'll give you the outputs of what you asked in the respective order that your requested each four, and then I'll comment at the end.
Code: [Select]
/dev/sda1 ext4 /

Code: [Select]
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xd42c7b41

Device     Boot      Start        End    Sectors   Size Id Type
/dev/sda1  *          2048 1452673023 1452670976 692.7G 83 Linux
/dev/sda2       1452675070 1465147391   12472322     6G  5 Extended
/dev/sda5       1452675072 1465147391   12472320     6G 82 Linux swap / Solaris


Disk /dev/sdb: 14.9 GiB, 16012804096 bytes, 31275008 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00000000

Device     Boot    Start      End  Sectors Size Id Type
/dev/sdb1           8192 25081855 25073664  12G  c W95 FAT32 (LBA)
/dev/sdb2       25081856 31260671  6178816   3G  b W95 FAT32

Code: [Select]
/dev/sda1: UUID="8f755c3f-5150-48b4-bc2a-e669ae8a39e3" TYPE="ext4" PARTUUID="d42c7b41-01"
/dev/sda5: UUID="fff87b78-fd61-4155-8d44-409c7ffb6604" TYPE="swap" PARTUUID="d42c7b41-05"
/dev/sdb1: UUID="A294-B7E0" TYPE="vfat"
/dev/sdb2: UUID="A4ED-EA20" TYPE="vfat"


Code: [Select]
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/sda1 during installation
UUID=8f755c3f-5150-48b4-bc2a-e669ae8a39e3 /               ext4    errors=remount-ro 0       1
# swap was on /dev/sda5 during installation
UUID=fff87b78-fd61-4155-8d44-409c7ffb6604 none            swap    sw              0       0

So, this is how I see the situation. When I originally installed linux, I was replacing a corrupted Windows 7 OS. When I did the partitioning or I knew I had /dev/sda1 and /dev/sda2. This is not a live usb, its on my hard drive. Granted, I do not know if I needed to have these two "files" or "partitions" (I'm sorry, 6 months and still learning the lingo). But, until Wednesday evening, I never say this /dev/sda5 Solaris Swap folder ever (I am referencing when you see the black screen right before you type in your password ones sees something like [files304203420:034230block] and the /dev/sda1 and /dev/sda2 and I have not seen this /dev/sda5 folder. I am confused as to why it is here and what it means. Does my machine detect a usb or port and try to connect to it before it goes to the hard drive and boot Peppermint properly? That is what I am thinking. Is there something in the boot menu F2 or F12 that I can do to fix the problem.

I have no idea how I got into this pickle, I just went from 8% battery to 0% battery on my laptop and then plugged up and rebooted. Sorry for the hassle.

14
Hardware / Re: Boot slow after battery was low
« on: April 20, 2017, 07:58:22 pm »
Thanks for the tips about office macros and  AV's. I'm a noob, and learning as I go, so AV was simply one of those regular things that I thought I need.

I purged sophos, but for a weird reason that only shaved of like 5s so I am still booting about 45s.

So running :
Code: [Select]
dmesg
and still have the two errors that I was showed earlier. I'll give more context:
Code: [Select]
[    3.141720] Btrfs loaded
[    3.804340] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
[    3.863894] sd 6:0:0:0: [sdb] 31275008 512-byte logical blocks: (16.0 GB/14.9 GiB)
[    3.864956] sd 6:0:0:0: [sdb] Write Protect is on
[    3.864968] sd 6:0:0:0: [sdb] Mode Sense: 03 00 80 00
[    3.866032] sd 6:0:0:0: [sdb] No Caching mode page found
[    3.866034] sd 6:0:0:0: [sdb] Assuming drive cache: write through
[    3.870796]  sdb: sdb1 sdb2
[    3.874162] sd 6:0:0:0: [sdb] Attached SCSI removable disk
[    3.931702] random: nonblocking pool is initialized
Then I ran what you asked:
Code: [Select]
systemd-analyze critical-chain
I got:
Code: [Select]
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.

graphical.target @36.428s
└─multi-user.target @36.415s
  └─smbd.service @36.180s +235ms
    └─nmbd.service @34.405s +1.759s
      └─network-online.target @34.390s
        └─NetworkManager-wait-online.service @28.380s +6.009s
          └─NetworkManager.service @23.191s +5.167s
            └─dbus.service @17.408s
              └─basic.target @17.395s
                └─sockets.target @17.395s
                  └─dbus.socket @17.395s
                    └─sysinit.target @15.890s
                      └─apparmor.service @6.254s +9.635s
                        └─local-fs.target @6.254s
                          └─local-fs-pre.target @6.254s
                            └─systemd-remount-fs.service @6.112s +102ms
                              └─systemd-journald.socket @2.329s
                                └─-.slice @2.313s
then
Code: [Select]
          9.635s apparmor.service
          8.711s dev-sda1.device
          8.417s mintsystem.service
          8.101s timidity.service
          7.758s grub-common.service
          7.301s console-kit-log-system-start.service
          6.810s irqbalance.service
          6.777s networking.service
          6.738s ondemand.service
          6.094s lightdm.service
          6.009s NetworkManager-wait-online.service
          5.167s NetworkManager.service
          2.948s ModemManager.service
          2.793s accounts-daemon.service
          1.896s console-setup.service
          1.849s upower.service
          1.815s systemd-tmpfiles-setup.service
          1.811s systemd-modules-load.service
          1.777s geoclue.service
          1.759s nmbd.service
          1.700s systemd-udevd.service
          1.678s winbind.service
          1.583s samba-ad-dc.service
          1.525s systemd-tmpfiles-setup-dev.service
          1.417s plymouth-start.service
          1.144s udisks2.service
          1.142s systemd-rfkill.service
          1.045s polkitd.service
          1.031s keyboard-setup.service
           896ms iio-sensor-proxy.service
           867ms systemd-journald.service
           845ms binfmt-support.service
           761ms systemd-backlight@backlight:acpi_video0.service
           708ms gpu-manager.service
           618ms systemd-update-utmp.service
           618ms systemd-udev-trigger.service
           541ms ufw.service
           527ms sys-kernel-debug.mount
           525ms dev-hugepages.mount
           449ms dev-mqueue.mount
           441ms systemd-logind.service
lines 1-41

Is Samba causing this problem? I am not sure.


15
Hardware / Re: Boot slow after battery was low
« on: April 20, 2017, 03:28:19 pm »
Thanks PCNetSpec for getting back to me.

Yes, I do have sophos anti-virus running, and I think that is the problem.

I ran:

Code: [Select]
[b]sudo[/b] touch /forcesfck

and booted twice, but no avail.

Here are the code outputs, respectively as you gave them to me.

Code: [Select]
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.

graphical.target @1min 10.573s
└─multi-user.target @1min 10.555s
  └─smbd.service @1min 5.541s +5.013s
    └─nmbd.service @55.423s +10.100s
      └─network-online.target @55.419s
        └─NetworkManager-wait-online.service @30.737s +24.676s
          └─NetworkManager.service @25.305s +5.420s
            └─dbus.service @17.393s
              └─basic.target @17.372s
                └─paths.target @17.372s
                  └─acpid.path @17.372s
                    └─sysinit.target @16.121s
                      └─apparmor.service @6.023s +9.767s
                        └─local-fs.target @5.931s
                          └─run-user-1000-gvfs.mount @47.836s
                            └─run-user-1000.mount @44.910s
                              └─local-fs-pre.target @5.905s
                                └─systemd-remount-fs.service @5.837s +44ms
                                  └─systemd-journald.socket @2.396s
                                    └─-.slice @2.390s
lines 1-23...skipping...
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.

graphical.target @1min 10.573s
└─multi-user.target @1min 10.555s
  └─smbd.service @1min 5.541s +5.013s
    └─nmbd.service @55.423s +10.100s
      └─network-online.target @55.419s
        └─NetworkManager-wait-online.service @30.737s +24.676s
          └─NetworkManager.service @25.305s +5.420s
            └─dbus.service @17.393s
              └─basic.target @17.372s
                └─paths.target @17.372s
                  └─acpid.path @17.372s
                    └─sysinit.target @16.121s
                      └─apparmor.service @6.023s +9.767s
                        └─local-fs.target @5.931s
                          └─run-user-1000-gvfs.mount @47.836s
                            └─run-user-1000.mount @44.910s
                              └─local-fs-pre.target @5.905s
                                └─systemd-remount-fs.service @5.837s +44ms
                                  └─systemd-journald.socket @2.396s
                                    └─-.slice @2.390s
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~

and

Code: [Select]
 39.199s sav-protect.service
         24.676s NetworkManager-wait-online.service
         16.681s networking.service
         15.432s irqbalance.service
         10.232s accounts-daemon.service
         10.100s nmbd.service
          9.884s winbind.service
          9.767s apparmor.service
          9.200s console-kit-log-system-start.service
          9.020s mintsystem.service
          8.863s timidity.service
          8.790s dev-sda1.device
          8.439s samba-ad-dc.service
          8.369s grub-common.service
          7.975s gpu-manager.service
          7.934s iio-sensor-proxy.service
          7.933s systemd-user-sessions.service
          7.927s rsyslog.service
          7.897s avahi-daemon.service
          7.460s ondemand.service
          7.409s lightdm.service
          5.420s NetworkManager.service
          5.013s smbd.service
          2.505s console-setup.service
          2.471s ModemManager.service
          1.849s binfmt-support.service
          1.759s plymouth-start.service
          1.557s systemd-udevd.service
          1.539s systemd-tmpfiles-setup-dev.service
          1.260s udisks2.service
          1.105s systemd-journald.service
          1.048s upower.service
          1.036s polkitd.service
          1.019s systemd-modules-load.service
           853ms systemd-rfkill.service
           790ms geoclue.service
           747ms systemd-logind.service
           741ms systemd-backlight@backlight:acpi_video0.service
           732ms keyboard-setup.service
           555ms systemd-udev-trigger.service
           512ms systemd-tmpfiles-setup.service
lines 1-41

I think I see sophos eating up the most rescouces so I guess that the battery drain must have corrupted something. Is a complete uninstall and purge the best way to fix this error? I am not married to sophos, I just have it as a precaution because as a teacher I frequently get .doc and .zip files from the web. Let me know if this is the only solution or if there is another fix. Is there anything else you think that is slowing me down?

Thank you again so much.

Pages: [1] 2