Issue updates for project peazip on Google Code

Update 5 to issue 160 ("Click on "Desktop" opens home directory")

2012-05-24T06:55:37Z

Desktop detection has to be improved: PeaZip currently search for 'Desktop' directory in user's home, which was good on old Linux distributions, and is still good for system localized in English or for some distributions/versions that still follows the convention of naming the directory Desktop also for some other non-English languages.
An improvement would be querying the system's environment variables (which may vary due to the system version, distribution's customizations, and installed desktop manager environments) to find if the Desktop directory path is declared in most common possible ways.

Update 4 to issue 160 ("Click on "Desktop" opens home directory")

2012-05-23T19:51:48Z

Thanks for this information. Now I have successfully set the correct path in Options > Settings.

But how does PeaZip try to auto-detect desktop path in Linux environments?

On my german localized Ubuntu installation
echo ${XDG_DESKTOP_DIR:-$HOME/Desktop}
prints the correct path to desktop which is:
/home/norbert/Arbeitsfläche

Could you use this way to auto-detect path to Desktop in Linux as default Desktop path?

Update 3 to issue 160 ("Click on "Desktop" opens home directory")

2012-05-23T19:49:47Z

Thanks for this information. Now I have successfully set the correct path in Options > Settings.

But how does PeaZip try to auto-detect desktop path in Linux environments?

On my german localized Ubuntu installation
echo ${XDG_DESKTOP_DIR:-$HOME/Desktop}
prints the correct path to desktop which is:
/home/norbert/Arbeitsfläche

Could you use this way to auto-detect path to Desktop in Linux?

Update 2 to issue 160 ("Click on "Desktop" opens home directory")

2012-05-23T19:48:10Z

Thanks for this information. I have set the correct path in Options > Settings.

But how does PeaZip try to auto-detect desktop path in Linux environments?

On my german localized Ubuntu installation
echo ${XDG_DESKTOP_DIR:-$HOME/Desktop}
prints the correct path to desktop which is:
/home/norbert/Arbeitsfläche

Could you use this way to auto-detect path to Desktop in Linux?

Update 1 to issue 160 ("Click on "Desktop" opens home directory")

2012-05-23T06:03:39Z

This happens when PeaZip is unable to locate the desktop path, it currently falls back on home instead. As alternative, desktop path can be explicitly set (or customized) in Options > Settings.

Issue 160 created: "Click on "Desktop" opens home directory"

2012-05-22T19:47:02Z

Click on "Desktop" in diretory tree opens the users home directory instead of the Desktop.

Found with peazip_4.5.1.LINUX.GTK2-2_all under...

DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=11.10
DISTRIB_CODENAME=oneiric
DISTRIB_DESCRIPTION="Ubuntu 11.10"

Update 3 to issue 159 ("Problems with displaying single files in subfolders (7z)")

2012-05-19T19:10:27Z

Here are screenshots for the examples above. I've also noticed this time that in the second example, PeaZip - incorrectly - opens in Flat mode.

Update 2 to issue 159 ("Problems with displaying single files in subfolders (7z)")

2012-05-17T11:35:14Z

The issue here is only about displaying (opening) archives, not creating them (I was using a terminal to run 7z and create an archive).

Update 1 to issue 159 ("Problems with displaying single files in subfolders (7z)")

2012-05-17T10:31:04Z

Thanks for reporting. Can you paste examples of command lines (from Console tab) failing to create archives with expected structure?
For reference the current behavior of 7z backend should be (consistently on Windows and Linux):
- adding i.e a folder named 'example_folder' to the archive it will add the file(s) in the path archive.7z/example_folder/ and will create the path is it does not exist in the archive - this works for practically unlimited levels of nesting
- adding a file by its name, even including the path, i.e. /example_folder/example_file.txt will add example_file.txt in the root of the archive (as documented in http://code.google.com/p/peazip/issues/detail?id=59 )

Issue 159 created: "Problems with displaying single files in subfolders (7z)"

2012-05-17T09:22:53Z

What steps will reproduce the problem?
For example,
1. cd /usr/local/share/PeaZip
2. 7z a ~/example.7z FreeDesktop_integration res/altconf.txt  # Here 7z creates 'res' subfolder for 'altconf.txt'
3. Open example.7z in PeaZip

What is the expected output? What do you see instead?
'res' folder isn't displayed at all.

Another case is when we pack only individual files in subfolders, like:
7z a ~/example2.7z FreeDesktop_integration/peazip.desktop res/altconf.txt

In this case, files are displayed straight in the archive root, not inside folders.

What version of the product are you using? On what operating system?
PeaZip 4.5.1 GTK, Fedora Linux. Also reproduced on PeaZip 4.2

Issue 158 created: "replace monotonous IF to ELSIF"

2012-05-14T14:10:32Z

What version of the product are you using? On what operating system?
4.5.1, any OS.

Please provide any additional information below.
E.g. 'pea_utils.pas', ln.802:
{{{
...
//imagine there is match right now
if upcase(obj_algo)='NOALGO' then authsize:=0;
//but it still executes upcase and compares strings
if upcase(obj_algo)='ADLER32' then authsize:=4;
//again
if upcase(obj_algo)='CRC32' then authsize:=4;
//and again
if upcase(obj_algo)='CRC64' then authsize:=8;
//...
if upcase(obj_algo)='MD5' then authsize:=16;
if upcase(obj_algo)='RIPEMD160' then authsize:=20;
if upcase(obj_algo)='SHA1' then authsize:=20;
if upcase(obj_algo)='SHA256' then authsize:=32;
if upcase(obj_algo)='SHA512' then authsize:=64;
if upcase(obj_algo)='WHIRLPOOL' then authsize:=64;
//wasting resources AND TIME
...
}}}
Using ELSIF, each IF block ends with |JMP to_end_of_IFs| = BREAK.

Good luck.

Issue 157 created: "add support to total commander plugin."

2012-05-14T09:01:32Z

add support to total commander plugin.

Update 1 to issue 152 ("Test on ReactOS")

2012-05-10T09:35:20Z

 
 
Labels: -Type-Enhancement Type-Other

Update 1 to issue 155 ("Bug navigating through \\-pathes (without drive letter)")

2012-05-10T09:34:43Z

Thank you for reporting. The bug is now fixed in release 4.5.1.
 
 
Status: Fixed

Update 18 to issue 19 ("Support for more achive formats, add here requests")

2012-05-09T17:24:16Z

.mht
.webarchive

Update 1 to issue 156 ("[Some Linux distributions] Missing libgdk_pixbuf-2.0")

2012-05-06T14:43:26Z

libgdk-pixbuf is a GNOME Developer Kit library, it is available for all current Ubuntu releases http://packages.ubuntu.com/search?keywords=libgdk-pixbuf2.0&searchon=names&suite=all&section=all
Alternatively, it can be found in GNOME Developer Kit http://live.gnome.org

In some distribution it seems to have a different name or being moved to a different path, and missing links with proper path/name can break any software relying on it, as shown in this bug report: https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/665768
 
 
Summary: [Some Linux distributions] Missing libgdk_pixbuf-2.0
Labels: -Type-Defect Type-Other

Issue 156 created: "不能运行error while loading shared libraries: "

2012-05-06T12:43:51Z

fuhaoyun@fuhaoyun-ThinkPad-SL:~$ peazip 
peazip: error while loading shared libraries: libgdk_pixbuf-2.0.so.0: cannot open shared object file: No such file or directory


Ubuntu 12.04 /unity /amd64

peazip_4.5.LINUX.GTK2-2_all.deb

Issue 155 created: "Bug navigating through \\-pathes (without drive letter)"

2012-04-29T09:12:05Z

What steps will reproduce the problem?

1. Enter a windows network path in the path box (without drive letter) that begins with \\

2. Confirm with enter. peazip correctly opens the path.

3. Click on of the breadcrumbs buttons in the path box to navigate to a higher directory

An error message appears. See screenshot.

Update 4 to issue 94 ("No integrated cascade menu when launching from total commander")

2012-04-16T09:48:06Z

Issue 154 has been merged into this issue.

Update 1 to issue 154 ("Context menus doesn't work with Altap Salamander file manager 2.54")

2012-04-16T09:48:06Z

On Windows 7 PeaZip uses the new method recommended by Microsoft for creating cascaded context menus, some software don't yet support that method so does not display the menus created in that way, but being it a new standard they should update the way they handle system's context menu.
http://msdn.microsoft.com/en-us/library/cc144171(v=vs.85).aspx#static_cascading

As temporary workaround users can run PeaZip's system configuration (or run custom installation) and unflag cascaded menu option for Windows 7 systems, so context menu entries are created in the classic way and any third party file manager can handle it.
 
 
Status: Duplicate
Mergedinto: 94