Quantcast
Channel: Pinguy OS Forum - All Forums
Viewing all 1646 articles
Browse latest View live

xfs filing system support

$
0
0
... and before you ask I've never heard of this one until received on G+

(https://plus.google.com/+KaranKalyani/posts/Mt6cCmsQ3Hr)

Current budgie-remix ubiquity fails at the partition stage. This is because the packages xfsprogs and xfsdump [https://wiki.ubuntu.com/XFS] are missing.

Should these two packages be added to the ISO builder?

Note - at beta 2 even after manually installing those two packages, ubiquity failed. However all works well (after installing those two packages) on a test ISO I made over this weekend - so I guess Canonical fixed something very recently.

Solving the Grub instal error and freeze up at booting

$
0
0
I am totaly new to Linux and a friend recommended Pinguy OS 14.04
The live version works great, but getting the bootable version to work
was a lot harder. I used a dvd for installation.

After nearly finishing the installation, I got the grub cannot install error
and was left with a system that could not boot. After Grub was installed,
the system froze up when booting.
I tried so solve these problems 1st after rebooting, with the liveCD
but that didn't work. I also tried linux rescue disks but Grub wouldn't budge.

After 2 days of reading several forums, I came up with this solution
Hope I can help some other people with this.

Start liveCD.
install PinguyOS from the desktop.
If Grub fails, choose to accept the OS without grub and do the following.

So don't reboot yet

1st
If you are manually installing/reinstalling grub from your LiveCD,
the commands would look like this (this assumes your root drive is /dev/sda1)
Open a terminal window:
Quote:sudo mount /dev/sda1 /mnt
then
Quote:sudo grub-install --root-directory=/mnt /dev/sda

don't reboot yet

2nd
To remove the freeze up during booting for the 1st time.
the error results come from the fake start-stop-daemon and the fake initctl.

To open a new terminal window with admin rights: (enter user password when asked)
Quote:sudo gnome-terminal

In the new terminal window enter:
Quote:apt-get install --reinstall dpkg upstart

After this close the new terminal when the program has finished.

Restart and all should be well Biggrin

Black screen after grub menu

$
0
0
Hello! I use ubuntu 16.04 final edition and installed Pinguy Builder to make a live-cd, but something went wrong. Came a black screen at startup, and the problem is reflected in the CD that is created. I've tried everything to solve, I observed that with disabling nVidia driver works normally, but is desirable to use it.

Does anyone have any suggestions for this case? Sad

[Image: jjqatn0.png]

I appreciate any help!

Marcos

How to use SOCKS proxy with Firefox

$
0
0
If you own a server running Linux you can ssh into it to run a SOCKS proxy.

In Ubuntu or other Linux systems (including OS X) you can open a terminal and run:

Code:
ssh -D 1337 -f -C -q -N User@ServerIP -p 22
  • -D 1337 tells ssh to launch a SOCKS server on port 1337 locally.
  • -f forks the process into the background.
  • -C Turns on compression.
  • -q enables "Quiet mode", since the purpose here is only to tunnel we don't really care about error output and such.
  • -N tells ssh that no commands will be sent (-f complains if we don’t specify this).
  • -p specifies what port to use; obviously this is defaulted to 22 so the statement above is pointless, but included for clarity.

If you’re on Windows, you can use PuTTY.

Next grab this addon for Firefox so it is easy to enable and disable the proxy from the toolbar.

This is the default settings.

Image

IP: 127.0.0.1
PORT: 1337

How to keep Nvidia drivers loaded in the .iso builder image ?

$
0
0
Hello all,

I'm on Ubuntu 16.04 and using a Nvidia GTX 970.

There is a similar thread on the subject from http://forum.pinguyos.com/User-eightbit but no answer.
The problem for me is that the driver nouveau is enable to recognise the Nvidia chipset NV124 et so I get stocked loading the Builder iso.
I was wondering if there was no walk-around for keeping the nvidia drivers during the builder iso creation ?

Thanks for your help and talk to you soon.

Stefx1

Can Pinguy Builder build a non-GUI image

$
0
0
Good morning all;

I need to create an Lubuntu image that will run in text only mode.

I have the machine itself already built and customized.
There is no GUI installed at all.

Think of it as an iinternal image that is all CLI based. No GUI required or desired.

Can PinGuy Builder still be used to build an image with this configuration?
It looks like all the tools are GUI based and there won't be a GUI present.

Thanks in advance

Little app, screen right?

$
0
0
How do I access this app that starts when desktop is opened?
The weather was displaying when I installed OS but no data is being presented now.
CPU and Memory has data.
Sorry for such a newbe question but I couldn't see how or what this app works/is called.
Huh

Bug in PinguyBuilder 4.3.8_all-beta and the fix

$
0
0
First of all I apologize for posting this here. I guess there must be a bug tracker somewhere, but I have not found it and it's very late. If I don't post this somewhere I'm probably not going to post it at all, so bear with me.

Also, I would like to thank the people who are currently working on PinguyBuilder. I was missing Remastersys dearly, and thank god you forked it!

I'm using pinguybuilder_4.3-8_all-beta.deb

Today I have tested PinguyBuilder on Ubuntu 16.04 for the first time, and it failed at the end of the procedure.

Fortunately, the terminal window outputs a useful message, and I have been able to trace the problem and find a workaround.

What happens is this:

At line 727 in /usr/bin/PinguyBuilder we have:
Code:
unsquashfs -lls $WORKDIR/ISOTMP/casper/filesystem.squashfs | grep -v " inodes " | grep -v "unsquashfs:" | awk '{print $3}' | grep -v "," > /tmp/size.tmp

If you manually run the following part:
Code:
unsquashfs -lls $WORKDIR/ISOTMP/casper/filesystem.squashfs | grep -v " inodes "
you will notice that at the end of the listing, grep adds a comment. In French it is:
Code:
Fichier binaire (entrée standard) correspondant
Which means "Binary file (standard input) matches". Grep is saying that it has found something that matches the regexp.

This last line will survive the next filters in line 727, and so on my computer the bottom of the /tmp/size.tmp file is:
Code:
...
751
1430
803
(entrée

At line 729, PinguyBuilder attempts to compute an arithmetic sum of all the lines in size.tmp, which results in a syntax error, caused by the "é" character.

This error will show up ONLY in some locale. It shows up in French because the 3rd word after the 3rd filter in line 727 contains a non-ASCII character. It would have gone unnoticed if the word "entrée" had been in the first or fourth word of the sentence.

A way to fix this bug is to change line 727 to:
Code:
unsquashfs -lls $WORKDIR/ISOTMP/casper/filesystem.squashfs | grep -v " inodes " | grep -v "unsquashfs:" | awk '{print $3}' | grep -v "," | grep [[:digit:]] > /tmp/size.tmp

because this will reject all the lines that don't have numbers in them.

Thank you for your attention on this matter, and keep up the good work!

The process was interrupted

$
0
0
Hi there,

I've tried searching the forum and can't find an answer to my question so am hoping it's okay to post here.

I use this great application to build my distro for distribution. So far I've made two 64 bit versions and a third 32 bit version. All have been downloaded by a few people tested and working no problem. Great!

My issue is with my fourth 32 bit build.

I keep getting stopped at the very end of the build process with "The process was interrupted" so although the build has finished, my ISO isn't saved.

Has anyone else experienced this issue?

Please see attached screenshot for the error.

Image

Thanks in advance.

Error while creating ISO

$
0
0
hey all,
I'm trying to create custom iso with ubuntu 16.04. But after the iso creation it gives a small (in size of about 34kB). How to tackle this error. Anybody got successful output in 16.04? The log file is attached Smile

Thanks!
PinguyBuilder.txt
File Type: .txt
Downloaded: 5 times
Size: 28.95 KB

Major issues with the builder.

$
0
0
I have attempted to use your remaster tool pinguybuilder_3.3-7_all.deb and all the required packages are installed. I'm trying to remaster Ubuntu Mate 16.04 LTS.
Everything seems to be going fine until it makes the iso file. I've had the same issue with the respin tool. The generated iso file is 34 k in size. I don't know what is causing this. Should I be using your beta version ? pinguybuilder_4.3-8_all-beta.deb ???

thanks in advance.

Some sort of PB issue w/16.04

$
0
0
Hi, I just registered. I want to thank you so much for forking Remastersys -- it's absolutely necessary software for the Ubuntuverse. It has worked beautifully up to 16.04. Now with 16.04 I'm having some sort of issue I don't understand yet, and I'll just have to describe the main symptoms and then if anyone would like more info from me, I'll keep checking in to provide what I can.

I am using an older Lenovo laptop, pretty basic, and nearly fresh installs of 16.04, updated to latest as of today and including just a few basic apps, nothing system-changing except for the Pinguy Builder package and dependencies themselves.

1. The building process seems to go smoothly, but upon installation, it invariably crashes when trying to "Retrieve files" if and only if I am connected to the internet on the live CD. If I do not connect to the internet, installation completes successfully (albeit with the sudo su issue described in the blog or twitter or wherever I read it). This happens whether I check or uncheck the 'Download updates' option; if I'm connected to a network, it seems to want to try and hangs.

2. However, once installed totally offline, the new system lacks Plymouth animations upon boot up (but not shutdown) and the LightDM login wallpaper no longer changes per user, but is stuck on default. I have double checked user wallpapers for permissions status, and they indicate no problems that would prevent their use with LightDM.

Is this part of some kind of pervasive permissions problem with the current close-to-release Ubiquity as usual (at least, I always ran into similar chaos with Remastersys with new Ubuntu releases too), or a PB bug? Just letting you know. I don't think it's anything I did (because I just did a straight GUI dist build with minimal changes to vanilla Xenial) or anything peculiar to my rig (because it's pretty common and does not have these problems with a plain Ubuntu install).

Thank you for taking the time to read my post. I hope this is pilot error on my part, and you can straighten me out. Smile

PB Ubiquity issue w/16.04 + Unconfigurable Display Manager Fix

$
0
0
Hi, I just registered. I want to thank you so much for forking Remastersys -- it's absolutely necessary software for the Ubuntuverse. It has worked beautifully up to 16.04. Now with 16.04 I'm having some sort of issue I don't understand yet, and I'll just have to describe the main symptoms and then if anyone would like more info from me, I'll keep checking in to provide what I can.

I am using an older Lenovo laptop, pretty basic, and nearly fresh installs of 16.04, updated to latest as of today and including just a few basic apps, nothing system-changing except for the Pinguy Builder package and dependencies themselves.

1. The building process seems to go smoothly, but upon installation, it invariably crashes when trying to "Retrieve files" if and only if I am connected to the internet on the live CD. If I do not connect to the internet, installation completes successfully (albeit with the sudo su issue described in the blog or twitter or wherever I read it). This happens whether I check or uncheck the 'Download updates' option; if I'm connected to a network, it seems to want to try and hangs.

2. However, once installed totally offline, the new system lacks Plymouth animations upon boot up (but not shutdown) and the LightDM login wallpaper no longer changes per user, but is stuck on default. I have double checked user wallpapers for permissions status, and they indicate no problems that would prevent their use with LightDM.

Is this part of some kind of pervasive permissions problem with the current close-to-release Ubiquity as usual (at least, I always ran into similar chaos with Remastersys with new Ubuntu releases too), or a PB bug? Just letting you know. I don't think it's anything I did (because I just did a straight GUI dist build with minimal changes to vanilla Xenial) or anything peculiar to my rig (because it's pretty common and does not have these problems with a plain Ubuntu install).

Thank you for taking the time to read my post. I hope this is pilot error on my part, and you can straighten me out. Smile

Looking to make a video tutorial of Pinguy Builder

$
0
0
Hi I am a long time user of Remastersys. It has served me well. I had no idea of the Pinguy builder until today. I like the way both the script and GUI load in the same install.

One problem I have had with Remastersys was creating a oem version. I have settled for creating iso files using the same user name and pass word and then just set up a new account manualy each time. (400 computers later) I havnt used Pinguy Builder but I see it has options to select the user of choice. I am hoping this will achive what I need.

I use Linux Mint 17.3 as my base.

I am really hoping that Pinguy Builder will do all I require as I feeel it is a valuable tool that many can benefit from. If all goes well I intend to make a 'how to' video tutrorial about Pinguy builder, and point it back to here. I'll let you know how it goes.

Regards Benny

could not find image vesamenu.c32

$
0
0
I made my first ISO with Pinguy builder today and I received an error when trying to boot it from a USB stick. The message said "could not find image vesamenu.c32" It didnt even get as far as grubloader.

I have used Remastersys MANY times over the years and have never had this issue.

Any ideas?

Thinking of killing off Pinguy OS

Grub-update Fatal error

$
0
0
Hi everyone, hope you're going fine !
I've made a custom remix of mint 17.3 which is for my students and try to make it iso distributable.
My live CD is working well but when I'm trying to install it the installation fail at the end because it is unable to run grub-update and tells me "fatal error" so impossible to install grub. I'm trying for 3 days to make it work and have red a lot of posts on the internet to find a solution...
Do you have an idea to fix it ? I really would like to redistribute my remix.

Thanks in advance for any clue
best regards

hxc

Teamviewer Hack Attacks

$
0
0
Ars Technica reports that some users who keep Teamviewer running might be vulnerable to attacks where the attacker will log into your machine and perform malicious actions such as attempting to dump passwords (possibly also installing keyloggers and such), steal login credentials and even transfer money to the attacker.

Attackers are possibly trying passwords from other websites that were hacked (e.g.: linkedin, mint forums, etc), meaning that users should be using unique passwords for their teamviewer account.

Those who keep teamviewer running are advised to turn on security features such as two-factor authentication, as well as change their passwords.

Evolution address book

$
0
0
Hi. Using latest Pinguy, 64-bit. A problem with Evolution.

Pinguy is stuck at Evolution 3.10.x, which doesn't play well with Google's address book. In later versions of Evolution, you can set up an online account in Gnome 3 and Evolution will see Google's address book. Not so with Evolution 3.10.x.

Why is the version in the repos so old? Can we somehow upgrade so we're not stuck with this problem?

Thanks.

Lampshade Screenlock

$
0
0
I want to know how the Pinguy Lampshade Screenlock works. I haven't seen it in other distros, I really like it, and I hear that Pinguy might be going away.
Viewing all 1646 articles
Browse latest View live