Puppy Stardust 006
- prehistoric
- Posts: 1744
- Joined: Tue 23 Oct 2007, 17:34
what happened to jpeg format?
Zigbert,
We have a problem connected with the libraries for reading jpg files. When I went to change the wallpaper to something not in /usr/share/backgrounds, I got the message that the file contained no data. Nor could mtpaint open the file. Installing gimp 2.6, and trying to convert to png that way also failed with the message "unrecognized file format".
We have a problem connected with the libraries for reading jpg files. When I went to change the wallpaper to something not in /usr/share/backgrounds, I got the message that the file contained no data. Nor could mtpaint open the file. Installing gimp 2.6, and trying to convert to png that way also failed with the message "unrecognized file format".
Thanks pemasu,
I've just edited the post and added a link for a free hosting site where the file is.
I'm also going to check a fresh install, I believe there is an old definitions file there, if so I'll make a pet without it in. Just update defs then.
I've just edited the post and added a link for a free hosting site where the file is.
I'm also going to check a fresh install, I believe there is an old definitions file there, if so I'll make a pet without it in. Just update defs then.
Rob
-
The moment after you press "Post" is the moment you actually see the typso 8)
-
The moment after you press "Post" is the moment you actually see the typso 8)
OK, I can make a small pet which will overcome all this.
F-prot is not installed on a fresh Puppy but it is once the menu link is pressed. It needs an internet connection then it downloads f-prot and virus definitions.
So the Puppy iso does not contain the larger app with virus definitions.
Install before downloading f-prot. I don't know if it will work if you have already downloaded. Perhaps someone can report?
F-prot is not installed on a fresh Puppy but it is once the menu link is pressed. It needs an internet connection then it downloads f-prot and virus definitions.
So the Puppy iso does not contain the larger app with virus definitions.
Install before downloading f-prot. I don't know if it will work if you have already downloaded. Perhaps someone can report?
- Attachments
-
- XFProt-0.2.pet
- (129.69 KiB) Downloaded 465 times
Rob
-
The moment after you press "Post" is the moment you actually see the typso 8)
-
The moment after you press "Post" is the moment you actually see the typso 8)
I didn't know. This could have saved me some worktrapster wrote:I have not tried Stardust006 yet. Hard keeping up with this and puppeee updates
Is your Pmenu an upgrade of my Pmenu or something totally new?
(though obviously, anything you do is an upgrade to anything I've done)
Sigmund
Re: what happened to jpeg format?
I tested no some jpgs, and they work fine in viewnior, mtpaint and gimp. Does your images work in Puppy 4.3.1?prehistoric wrote:Zigbert,
We have a problem connected with the libraries for reading jpg files. When I went to change the wallpaper to something not in /usr/share/backgrounds, I got the message that the file contained no data. Nor could mtpaint open the file. Installing gimp 2.6, and trying to convert to png that way also failed with the message "unrecognized file format".
Sigmund
- prehistoric
- Posts: 1744
- Joined: Tue 23 Oct 2007, 17:34
not jpeg problem, wallpaper setter to blame
Zigbert,
The wallpaper setter in Puppy Stardust 006 is in serious need of house training. After pursuing several false leads, based on the mistaken idea about jpeg libraries, I went back, and looked at the images I was using. That was when I discovered the wallpaper setter was modifying the pictures themselves, and creating a parallel directory for Originals. All the pictures I had tried were clobbered, and the files ending in jpg really didn't hold data.
Bad dog! No, no, no!
This is a little strange when working with /usr/share/backgrounds, and becomes positively unreal when I use something in /mnt/home/pictures, or some similar location I thought safe from Stardust.
You want to leave the originals where you find them, and make working copies in a place where no one will mind. You also need to fix a bug in the wallpaper setter which clobbers those jpg files once they are used.
The wallpaper setter in Puppy Stardust 006 is in serious need of house training. After pursuing several false leads, based on the mistaken idea about jpeg libraries, I went back, and looked at the images I was using. That was when I discovered the wallpaper setter was modifying the pictures themselves, and creating a parallel directory for Originals. All the pictures I had tried were clobbered, and the files ending in jpg really didn't hold data.
Bad dog! No, no, no!
This is a little strange when working with /usr/share/backgrounds, and becomes positively unreal when I use something in /mnt/home/pictures, or some similar location I thought safe from Stardust.
You want to leave the originals where you find them, and make working copies in a place where no one will mind. You also need to fix a bug in the wallpaper setter which clobbers those jpg files once they are used.
Re: not jpeg problem, wallpaper setter to blame
Barry did some adjustment to the wallpaper setter in 431 (base of stardust), that is to auto-adjust the image to fit widescreen nicelyprehistoric wrote:Zigbert,
The wallpaper setter in Puppy Stardust 006 is in serious need of house training. After pursuing several false leads, based on the mistaken idea about jpeg libraries, I went back, and looked at the images I was using. That was when I discovered the wallpaper setter was modifying the pictures themselves, and creating a parallel directory for Originals. All the pictures I had tried were clobbered, and the files ending in jpg really didn't hold data.
Bad dog! No, no, no!
This is a little strange when working with /usr/share/backgrounds, and becomes positively unreal when I use something in /mnt/home/pictures, or some similar location I thought safe from Stardust.
You want to leave the originals where you find them, and make working copies in a place where no one will mind. You also need to fix a bug in the wallpaper setter which clobbers those jpg files once they are used.
Wallpaper setter problem
This happens to me too.The wallpaper setter in Puppy Stardust 006 is in serious need of house training. That was when I discovered the wallpaper setter was modifying the pictures themselves, and creating a parallel directory for Originals. All the pictures I had tried were clobbered, and the files ending in jpg really didn't hold data.
Re: not jpeg problem, wallpaper setter to blame
Is this a specific Stadust bug, or does it also happen in Puppy 4.3.1?prehistoric wrote:Zigbert,
The wallpaper setter in Puppy Stardust 006 is in serious need of house training. After pursuing several false leads, based on the mistaken idea about jpeg libraries, I went back, and looked at the images I was using. That was when I discovered the wallpaper setter was modifying the pictures themselves, and creating a parallel directory for Originals. All the pictures I had tried were clobbered, and the files ending in jpg really didn't hold data.
Sigmund
- prehistoric
- Posts: 1744
- Joined: Tue 23 Oct 2007, 17:34
clobbering wallpaper images
Zigbert,
My first idea, about jpeg libraries, misled me. I had tested under stock 4.3.1 and found things working that did not appear to work under Stardust. This was simply because I had not used the wallpaper setter on those images. I've now rebooted and run tests on the same machine under stock 4.3.1, and reproduced the behavior. I'm really surprised we haven't heard about this before.
I've attached a screen shot, made with stock 4.3.1, showing a bizarre collection of "Original" directories created on my home partition. The modified jpg files were corrupted, but the original is accessible in a different directory.
My first idea, about jpeg libraries, misled me. I had tested under stock 4.3.1 and found things working that did not appear to work under Stardust. This was simply because I had not used the wallpaper setter on those images. I've now rebooted and run tests on the same machine under stock 4.3.1, and reproduced the behavior. I'm really surprised we haven't heard about this before.
I've attached a screen shot, made with stock 4.3.1, showing a bizarre collection of "Original" directories created on my home partition. The modified jpg files were corrupted, but the original is accessible in a different directory.
- Attachments
-
- screenshot-wallpaper-dirs.jpg
- rescaled screen shot of directories on /mnt/home produced by wallpaper setter
- (92.98 KiB) Downloaded 539 times
- prehistoric
- Posts: 1744
- Joined: Tue 23 Oct 2007, 17:34
backgrounds
Getting backgrounds to work is not the problem, as you can see in that screen shot. The behavior which causes trouble is modifying files nobody expected to be modified. Creating new directories in some place where I store images I want to keep is a problem. People who take photos and want to try them on the desktop will be ticked if they lose the date and time the file was last modified. Just try to sort 1,000 pictures from a holiday without times, and you'll catch on quickly. There are ways around this, but that is not something you want naive users to run into. One scrambled collection of pictures, and the word that Puppy is too dangerous for photographers to use will get around. We don't want that.jpeps wrote:No biggee...just convert the jpg's in /usr/share/background_original to png's in /usr/share/background. Bottom line...use png format for background. (although I think they worked in 005)
Re: backgrounds
On my settup, jpg's in /usr/share/background corrupt right away, and don't load.prehistoric wrote:Getting backgrounds to work is not the problem, as you can see in that screen shot.jpeps wrote:No biggee...just convert the jpg's in /usr/share/background_original to png's in /usr/share/background. Bottom line...use png format for background. (although I think they worked in 005)
Has there been a change in the CUPS program. It is working perfectly on 005 but when I made a seperate installation of 006 (both hard disk installs on separate partitions) it goes through the motions including identifying the printer involved (HP5550 Deskjet) but will not print a test page. I rebooted to 005 and it works perfectly. Any thoughts?
Other than that I have been using 005 as my primary OS and am very satisfied with it ,staying true to Barrys original with useful mods seems to be the answer.
Regards Dennis .
Other than that I have been using 005 as my primary OS and am very satisfied with it ,staying true to Barrys original with useful mods seems to be the answer.
Regards Dennis .
I will remove /usr/sbin/background_reshape to avoid image cropping when changing wallpaper. This is a tool Barry introduced to keep format of wallpapers when stretching. It does only work for jpgs and for pictures in 4:3 format, and relies on some apps from the netpbm package which I of course want to get rid of .......... to be honest, I don't see the value of such a program on Stardust. The wallpapers in the iso are all stretchable, and when user chooses his/her own, it will be chosen because it fits screen.
dalderton mentioned that printing testpage works in 005. Good news. That means it is not a font, but a netpbm tool. probably some of them......I will find out.
Sigmund
dalderton mentioned that printing testpage works in 005. Good news. That means it is not a font, but a netpbm tool. probably some of them......I will find out.
Sigmund