License: GNU General Public License v2.0
Mintstick is a graphical tool that allows you to format USB sticks and create bootable USB sticks.
To avoid the following error: dpkg-source: error: unrepresentable changes to source Build this package like this:
dpkg-buildpackage -i.git
Please use Launchpad to translate Mintstick: https://translations.launchpad.net/linuxmint/latest/.
The PO files in this project are imported from there.
I'm running mintstick 1.1.9 on lmde and my SanDisk Corp. Cruzer Blade 32gb flash drive is not detected by the utility. usb-creator-gtk on linux mint 13 is able to detect it correctly.
After using mintstick to write lmde's iso to a 4gb flash drive, lmde is unable to mount the created partition and when i load gparted it states "invalid partition table - recursive partition on /dev/sdb." linux mint 13 is able to mount the partition even though gparted gives the same error.
On Mint 17 KDE (and 16 too), the alert box which appears after a successful write/format causes 100% usage on a CPU core. It will only stop when the alert box is closed.
P.S.: Not tested on Cinnamon and MATE.
after install - USB Stick Formatter did not work - I run it in terminal with error:
mintstick -m format
File "/usr/lib/mintstick/raw_format.py", line 41
print "Geometry error - Can't create partition"
^
SyntaxError: invalid syntax
Pls advise...
Please see this Launchpad bug:
https://bugs.launchpad.net/linuxmint/+bug/1313295
Hi - I am not sure if it is Mint Stick related issue or with Cinnamon but after format I am unable write unless I log in as root. Should not be the case, I believe. For Format, root privileges are fine but data read / write should not require root privileges in my view.
Update: It worked fine on another machine. Still, keeping it open. Will check if it is can be reproduced again.
Could mintstick detect non-hybrid ISO images and issue an error (or at least a warning) that the resulting stick might not be bootable?
I don't expect there is a desire for mintstick to become Rufus or WoeUSB-ng, so writing ISO files that need to be manipulated to make them work is likely to remain out of scope. But that means the program is really going to work for hybrid images only. Something with a partition table, essentially. And it's easy enough to determine if there is one present or not to tell the user that they need something else, rather than perform the operation and fail silently.
I'm trying to get mintstick to work on OpenSUSE 13.2. I get this message when running from command line:
silviu@linux-hr4u:~> mintstick -m iso Downloads/ubuntu-14.04
ubuntu-14.04.1-desktop-amd64.iso ubuntu-14.04-startup-sounds.zip
silviu@linux-hr4u:~> mintstick -m iso Downloads/ubuntu-14.04.1-desktop-amd64.iso
/usr/lib/mintstick/mintstick.py:64: Warning: The property GtkButton:use-stock is deprecated and shouldn't be used anymore. It will be removed in a future version.
self.wTree.add_from_file(self.gladefile)
/usr/lib/mintstick/mintstick.py:64: Warning: The property GtkSettings:gtk-button-images is deprecated and shouldn't be used anymore. It will be removed in a future version.
self.wTree.add_from_file(self.gladefile)
/usr/lib/mintstick/mintstick.py:64: Warning: The property GtkImage:stock is deprecated and shouldn't be used anymore. It will be removed in a future version.
self.wTree.add_from_file(self.gladefile)
/usr/lib/mintstick/mintstick.py:64: Warning: The property GtkMisc:xpad is deprecated and shouldn't be used anymore. It will be removed in a future version.
self.wTree.add_from_file(self.gladefile)
raw_write took 4.110 ms
Traceback (most recent call last):
File "/usr/lib/mintstick/raw_write.py", line 85, in <module>
main()
File "/usr/lib/mintstick/raw_write.py", line 82, in main
raw_write(source, target)
File "/usr/lib/mintstick/raw_write.py", line 41, in raw_write
os.fsync(output.fileno())
OSError: [Errno 5] Input/output error
Image: /home/silviu/Downloads/ubuntu-14.04.1-desktop-amd64.iso
USB stick: /dev/sdf
Starting copy from /home/silviu/Downloads/ubuntu-14.04.1-desktop-amd64.iso to /dev/sdf
An error occurred.
This is what I see in dmesg:
[ 5716.379808] sdf: sdf1 sdf2
[ 5716.463196] usb 1-1.6: reset high-speed USB device number 5 using ehci-pci
[ 5716.550486] sd 12:0:0:0: [sdf] Unhandled sense code
[ 5716.550489] sd 12:0:0:0: [sdf]
[ 5716.550490] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 5716.550491] sd 12:0:0:0: [sdf]
[ 5716.550492] Sense Key : Vendor Specific(9) [current]
[ 5716.550494] Info fld=0x0
[ 5716.550495] sd 12:0:0:0: [sdf]
[ 5716.550496] Add. Sense: Logical unit not ready, cause not reportable
[ 5716.550497] sd 12:0:0:0: [sdf] CDB:
[ 5716.550498] Write(10): 2a 00 00 00 4e 80 00 00 f0 00
[ 5716.550502] end_request: I/O error, dev sdf, sector 20096
[ 5716.550504] Buffer I/O error on device sdf, logical block 2512
[ 5716.550505] lost page write due to I/O error on sdf
[ 5716.550510] Buffer I/O error on device sdf, logical block 2513
[ 5716.550510] lost page write due to I/O error on sdf
[ 5716.550512] Buffer I/O error on device sdf, logical block 2514
[ 5716.550513] lost page write due to I/O error on sdf
[ 5716.550515] Buffer I/O error on device sdf, logical block 2515
[ 5716.550515] lost page write due to I/O error on sdf
[ 5716.550517] Buffer I/O error on device sdf, logical block 2516
[ 5716.550518] lost page write due to I/O error on sdf
[ 5716.550520] Buffer I/O error on device sdf, logical block 2517
[ 5716.550520] lost page write due to I/O error on sdf
[ 5716.550522] Buffer I/O error on device sdf, logical block 2518
[ 5716.550523] lost page write due to I/O error on sdf
[ 5716.550525] Buffer I/O error on device sdf, logical block 2519
[ 5716.550525] lost page write due to I/O error on sdf
[ 5716.550527] Buffer I/O error on device sdf, logical block 2520
[ 5716.550528] lost page write due to I/O error on sdf
[ 5716.550530] Buffer I/O error on device sdf, logical block 2521
[ 5716.550530] lost page write due to I/O error on sdf
Hi,
I am using Linux Mint 19.3 Tricia.
The version of the mintstick I am using is:
$ apt policy mintstick
mintstick:
Installed: 1.4.1
Candidate: 1.4.1
Version table:
*** 1.4.1 500
500 http://packages.linuxmint.com tricia/main amd64 Packages
500 http://packages.linuxmint.com tricia/main i386 Packages
100 /var/lib/dpkg/status
The issue I am reporting is the following. When I delete a character in the "Volume label" text, the cursor always jumps to the end of the text. This happens with the backspace and delete keys. This issue is 100% reproducible in my system. Always when I use "USB Stick Formatter", after deleting a character, this issue happens.
This is an example using the delete key, but the same issue happens with the backspace key:
The volume label text is "USB STICK" and the cursor is at the beginning of the text (before the U).
Then I press the delete key and the volume label text is "SB STICK" and the cursor is at the end of the text (after the K).
Then without repositioning the cursor, if I type U, the volume label text is "SB STICKU".
Regards,
Ricardo
As a first contribution, here are two small tweaks to mintstick ui:
Thx for making Mint :-)
--- mintstick.ui 2016-07-14 15:24:48.172217833 +0200
+++ /usr/share/mintstick/mintstick.ui 2016-04-22 11:35:58.000000000 +0200
@@ -342,6 +342,7 @@
<property name="sensitive">False</property>
<property name="can_focus">False</property>
<property name="show_text">False</property>
+ <property name="valign">center</property>
<property name="pulse-step">0.2</property>
<property name="text" translatable="yes"> </property>
</object>
@@ -590,6 +591,7 @@
<property name="hscrollbar_policy">never</property>
<property name="vscrollbar_policy">automatic</property>
<property name="shadow_type">in</property>
+ <property name="min_content_height">80</property>
<child>
<object class="GtkTextView" id="detail_text">
<property name="height_request">100</property> * Nemo version 4.2.3
* Is issue with desktop or windowed nemo? windowed nemo
* Distribution - Mint 19.2
* Graphics hardware *and* driver used - not relevant
* 64 bit
Issue
I've downloaded redobackup-livecd-1.0.4.iso , write the image to USB stick but it doesn't boot.
Using Rufus on Windows 10 to create a bootable image with the same iso and the same USB-sticket works fine and boots Redo Backup
Steps to reproduce
-Within Nemo, right-click on the iso file and click something like (I have on the german version) "create bootable USB-stick".
Expected behaviour
after reboot of PC, Redo back should boot from the USB stick.
Other information
existing data was overwritten. I didn't format the stick specifically.
In format mode, the details section is useless. We should use it to show the output of the mkfs commands.
I translated this string:
https://translations.launchpad.net/linuxmint/latest/+pots/mintstick/hu/+translate?batch=10&show=all&search=will
but the confirmation window still shows the English string. Linux Mint/32bit/Cinnamon/Hungarian
Also reported here: https://bugs.launchpad.net/linuxmint/+bug/1390854
The main difference with Ubuntu USB Creator is the option for a persistence file. Is it possible here?
As far as I see, at the moment Mintstick does not verify the image on the usb stick after writing. It would be a big advantage to add this functionality. Just as Etcher already does successfully.
Every SD cards inserted on my embedded SD card reader of my laptop are mounted to /dev/mmcblk0 which is not detcted.
Mint 20.2 Cinnamon.
To reproduce:
EDITED.
If I remember correctly mintstick in LM 17.x already uses nemo as file chooser, and other applications automatically use nemo as well. The default GTK file chooser does not have all the features (such as the recent files list) and looks a bit out of place from a UX viewpoint.
After formatting, the device list reinits itself and the selection is empty... but the format button is still sensitive.
We should disable the button until a device is selected again.
My experiences writing an ISO to USB stick.
I'm sorry this is so long. I've endeavored to be complete (verbose).
Especially see '<<--' lines (there's 5 of them).
I use 'gparted' to format '/dev/sdb' to fat32.
'gparted' reports:
==================
Device Information
------------------
Model: USB Flash Memory
Serial: none
Size: 14.45 GiB
Path: /dev/sdb
Partition table: msdos <<-- NOTE: MSDOS part-table
Heads: 255
Sectors/track: 63
Cylinders: 1885
Total sectors: 30297216
Sector size: 512 <<-- NOTE sector size (can't be changed)
============
Partition #1
------------
File system: fat32
Label: USB Stick
UUID: 9142-EF76
Status: Mounted on /media/mark/9142-EF76
Used: 14.45 MiB
Unused: 14.42 GiB
Size: 14.45 GiB
Path: /dev/sdb1
Name:
Flags: boot
First sector: 2048
Last sector: 30281727
Total sectors: 30279680
===========
Unallocated
-----------
File system: unallocated
Size: 7.56 MiB
Path: unallocated
First sector: 30281728
Last sector: 30297215
Total sectors: 15488
I write 'linuxmint-18-cinnamon-64bit.iso' to the USB stick using 'mintstick -m iso'
I launch 'gparted'. When the scanner gets to '/dev/sdb', it complains:
"Libparted Warning
The driver descriptor says the physical block size is 2018 bytes, but Linux says it is 512 bytes.
[Cancel] [Ignore]"
I click [Ignore] button.
'gparted' reports:
==================
Device Information
------------------
Model: USB Flash Memory
Serial: none
Size: 57.79 GiB
Path: /dev/sdb
Partition table: mac <<-- NOTE: is this 'mac' as in 'macintosh'?
Heads: 255
Sectors/track: 63
Cylinders: 1885
Total sectors: 30297216
Sector size: 2048 <<-- NOTE sector size
============
Partition #1
------------
File system: unknown
Label: Linux Mint 18 Cinnamon 64-bit
UUID: 2016-06-28-12-50-06-00
Status: not mounted
Size: 4.00 KiB
Path: /dev/sdb1
Name:
Flags:
First sector: 1
Last sector: 2
Total sectors: 2
Warning:
Unable to detect file system! Possible reasons are:
- The file system is damaged
- The file system is unknown to GParted
- There is no file system available (unformatted)
- The device entry /dev/sdb1 is missing
===========
Unallocated
-----------
File system: unallocated
Size: 42.55 MiB
Path: unallocated
First sector: 3
Last sector: 21787
Total sectors: 21785
============
Partition #2
------------
File system: fat16
Label:
UUID: B1F5-0A13
Status: not mounted
Used: 2.30 MiB (100%)
Unused: 8.00 KiB (0%)
Size: 2.31 MiB
Path: /dev/sdb2
Name:
Flags:
First sector: 21788
Last sector: 22971
Total sectors: 1184
===========
Unallocated
-----------
File system: unallocated
Size: 57.74 GiB <<-- This is 4x what it should be (...4x==2048/512, the sector size is causing this?)
Path: unallocated
First sector: 22972
Last sector: 30297215
Total sectors: 30274244
Hmmm... NOTE the '-m' in 'mintstick -m iso' (above). Does that mean 'mac'? Should a different command line be used?
In 'terminal', I submit: 'mintstick --help'. I see:
mark@mark-Lenovo-V570 ~ $ mintstick --help
/usr/lib/mintstick/mintstick.py:10: PyGIWarning: Polkit was imported without specifying a version first. Use gi.require_version('Polkit', '1.0') before import to ensure that the right version gets loaded.
from gi.repository import GObject, Gio, Polkit, Gtk, GLib, UDisks
/usr/lib/mintstick/mintstick.py:10: PyGIWarning: Gtk was imported without specifying a version first. Use gi.require_version('Gtk', '3.0') before import to ensure that the right version gets loaded.
from gi.repository import GObject, Gio, Polkit, Gtk, GLib, UDisks
/usr/lib/mintstick/mintstick.py:10: PyGIWarning: UDisks was imported without specifying a version first. Use gi.require_version('UDisks', '2.0') before import to ensure that the right version gets loaded.
from gi.repository import GObject, Gio, Polkit, Gtk, GLib, UDisks
Usage: mintstick [--debug] -m [format|iso] : mode (format usb stick or burn iso image)
mintstick [--debug] -m iso [-i|--iso] iso_path
mintstick [--debug] -m format [-u|--usb] usb_device
[-f|--filesystem] filesystem
mark@mark-Lenovo-V570 ~ $
Hmmm... They all have '-m'. In 'terminal', I submit: 'man mintstick'. I read:
"SEE ALSO
"The full documentation for mintstick is maintained at http://github.com/linuxmint/mintstick
"Go to the project page to get access to the complete documentation."
I go to 'http://github.com/linuxmint/mintstick'. I can't find documentation. I can't find a project page.
I reboot so that the automounter will find the USB stick.
Rebooted, I launch 'gparted'. When the scanner gets to '/dev/sdb', again it complains:
"Libparted Warning
The driver descriptor says the physical block size is 2018 bytes, but Linux says it is 512 bytes.
[Cancel] [Ignore]"
I click [Ignore] button. Immediately, I see:
"Libparted Error
Partition(s) 1 on /dev/sdb have been written, but we have been
unable to inform the kernel of the change, probably because it/
they are in use. As a result, the old partition(s) will remain in
use. You should reboot now before making further changes.
[Cancel] [Ignore]"
I quit 'gparted' and reboot again. The sequence above repeats.
Nemo shows device 'Linux Mint 18 Cinnamon 64-bit' is mounted, and, when I browse into it, the file listing looks correct.
/media/mark/Linux Mint 18 Cinnamon 64-bit/boot/
/media/mark/Linux Mint 18 Cinnamon 64-bit/casper/
/media/mark/Linux Mint 18 Cinnamon 64-bit/dists/
/media/mark/Linux Mint 18 Cinnamon 64-bit/isolinux/
/media/mark/Linux Mint 18 Cinnamon 64-bit/pool/
/media/mark/Linux Mint 18 Cinnamon 64-bit/preseed/
/media/mark/Linux Mint 18 Cinnamon 64-bit/.disk/
/media/mark/Linux Mint 18 Cinnamon 64-bit/MD5SUMS
/media/mark/Linux Mint 18 Cinnamon 64-bit/README.diskdefines
If I boot to USB, boot fails with this message: "Error: File name '/boot/' not found."
I'm left with a black screen and no boot. When I reboot and allow it, Linux Mint launches normally.
Issues:
The resulting USB doesn't appear to be bootable ('Flags:' != 'boot').
Is the USB using 'grub'?
What's with the 'mac' ID for the new Partition table? Is this a problem with the Linux Mint ISO or with 'mintstick'?
Help is needed and appreciated. Cheers!
It would be great if this utility could be distributed as a flatpak package so that it is available universally for any distribution and version supporting flatpak.
Add a nemo action on devices
The man page reads:
"
The full documentation for mintstick is maintained at http://github.com/linuxmint/mintstick
Go to the project page to get access to the complete documentation.
"
However, I failed to find any explanation of the utility beyond an assumption to read the code.
While I am capable of doing that, I hardly call the available COPYING, TODO, and README
"complete documentation."
UDF support was requested. However I'm missing some info here...
In mintstick.py we could just add:
if os.path.exists("/usr/bin/mkudffs"):
self.fsmodel.append(["udf", "UDF"])
and in raw_format.py:
elif fstype == "udf":
os.system("mkudffs --blocksize=512 --media-type=hd --utf8 --lvid="%(label)s" --vid="%(label)s" --fsid="%(label)s" %(partition)s", {'label': volume_label, 'partition': partition.path})
The problem with this seems that mkudffs needs to apply to /dev/sdX.. not /dev/sdX1, otherwise we get an error...
Also I'm wondering if a partition needs to be created here.
clem@storm ~ $ sudo dd if=/dev/zero of=/dev/sdb bs=512 count=1
1+0 records in
1+0 records out
512 bytes (512 B) copied, 0.0017184 s, 298 kB/s
clem@storm ~ $ sudo mkudffs --blocksize=512 --media-type=hd --utf8 --vid="UDF Stick" --udfrev=0x0102 /dev/sdb1
trying to change type of multiple extents
Things seem fine if we specify /dev/sdb instead of /dev/sdb1... the stick is then mounted in read/write, though it produces error messages in other Linux boxes and isn't visible on a Samsung Smart TV.
I can create a pull request if there's demand for this. I'm leaving it aside for now.
To reproduce:
mintstick -m format without a USB stick inserted.What should happen:
At stage 3, either there should be no resizing or, better, the name of the USB stick should appear in the name field.
MintStick fails to detect Sandisk SDCZ80-032G "32gb Extreme USB 3.0", and probably many others.
In order to appear in the Windows XP bootloader, firmware erroneously reports DRIVE_FIXED instead of DRIVE_REMOVABLE per-
http://www.911cd.net/forums//index.php?s=38512613c2dfc5180aeaf70ed423a764&showtopic=19768&st=0&p=132085&#entry132085
udisks --dump, reports "Removable: 0", which mintstick.py (in Git) queries beginning on line 196, specifically on line 207 "and (str(dev.Get('', 'DeviceIsRemovable')) == "1") ".
The fault is the manufacturer's, and mintstick's behaviour is technically correct, but it makes life difficult for novice users with random USB sticks, and forum & IRC helpers.
"rufus" USB image writer for Windows has an Alt-F mode to enable fixed-disk detection, which works for this stick, per-
pbatard/rufus#134
A command-line switch ("mintstick --fixed" etc) could easily handle these drives without pestering users.
When using mintstick, I get 100% CPU usage and it completely freezes my xorg process.
This seems related to tbehan@488e557#diff-8e748d5cf67ed7503036953ff4241f50R155, where @tbehan experiences (and fixes) this same problem. It seems that his enhacement was only partially introduced in 3da82f0 (without the fix). Later I think other stuff related to this have been fixed, but in my case it's still happening.
Commenting out https://github.com/linuxmint/mintstick/blob/master/lib/mintstick.py#L339 workarounds the problem (no percentage shown, but I can write my stick and my computer doesn't freeze).
Thanks!
After write an image, and try again don't display the new selected image filename, and the new device.
On two Mint laptops, one Cinnamon and one XFCE, I tried to use the bundled USB formatting tool. On both computers, an icon for the stick (which is made by Lexar) appeared on my desktop and in both cases the stick was identified as being called 'Linux Mint'. On both laptops, though, the formatting program identified the stick as 'Kingston Data Traveller'. Earlier today I had had a Kingston USB in the drives of both computers.
Faced with this, I worried about the format and resorted to formatting the stick on . . Windows.
It would be really cool software if it supported multiple OSs on one flash drive
Hi,
Polkit action of Meson package's breaks polkit action of Mintstick.
I guess, the issue is due to the following line including /usr/bin/python3 command.
From polkit action file of meson
<annotate key="org.freedesktop.policykit.exec.path">/usr/bin/python3</annotate>
<annotate key="org.freedesktop.policykit.exec.argv1">/usr/bin/meson</annotate>
From polkit action file of mintstick
<annotate key="org.freedesktop.policykit.exec.path">/usr/bin/python3</annotate>
<annotate key="org.freedesktop.policykit.exec.argv1">/usr/lib/mintstick/raw_write.py</annotate>
<annotate key="org.freedesktop.policykit.exec.argv1">/usr/lib/mintstick/raw_format.py</annotate>
<annotate key="org.freedesktop.policykit.exec.allow_gui">true</annotate>
Any package including /usr/bin/python3 line in the polkit action file can also cause this issue.
Screenshot of issue
Screenshot of expected behaviour
Steps to reproduce
Install meson package
Restart nemo with nemo -q command
Format an USB keyring
Distribution
Linux Mint 20.2 Uma Cinnamon
The option to create a bootable stick is also displayed on folders ending with iso. The cause is the line Extensions=iso;img;. Maybe use MIME types instead like Mimetypes=application/x-iso9660-image;? I will provide a pull request to fix this shortly.
(I've tested mintstick mostly as the global apps-menu icon "USB Stick Formatter" rather than as "USB Image Writer.")
Suggestions:
pkexec dialog succeeds, because in some controls-themes (such as Mint-X), the blank throbber looks like an erroneously drawn control of some other kind.pkexec dialog, then don't show an error message-box and don't animate the throbber.--version command-line option.mintstick APT package version 1.3.1
Is this project still maintained and if yes, could you release versioned tarballs here on GitHub?
When using command line to format a warning and an error occurs
Quite easy to reproduce - replace sdy - with the testing device
Manjaro
Python 3.8
❯ mintstick -m format -u /dev/sdy -f vfat
/usr/lib/mintstick/mintstick.py:40: PyGIDeprecationWarning: Since version 3.11, calling threads_init is no longer needed. See: https://wiki.gnome.org/PyGObject/Threading
GObject.threads_init()
Traceback (most recent call last):
File "/usr/lib/mintstick/mintstick.py", line 602, in <module>
MintStick(iso_path, usb_path, filesystem, mode, debug)
File "/usr/lib/mintstick/mintstick.py", line 181, in __init__
iter = model.get_iter_first()
NameError: name 'model' is not defined
Error Report after sudo mintstick
Traceback (most recent call last):
File "/usr/lib/mintstick/mintstick.py", line 13, in <module>
import gi
ImportError: No module named gi
The gi package (python-gi) is not listed by aptitude as a dependency. Is this a transitive dependency issue? (A depends on B, B depends on C: therefore A depends on C)
Add a label to describe the fstypes.
I'm currently trying to create a bootable USB stick, but using a read-write filesystem, like fat32.
I used the USB Writer, but when it writes the ISO, the USB stick gets a iso9660 filesystem, that is a read-only one.
My suggestion is to create option on GUI or in command line, like the -f for formatting mode, for choosing a filesystem.
Would be useful when formatting USB sticks, atm it requires googling each filesystem to find out (unless you're the kind of person who knows that by heart).
So for example, the dropdown would contain:
After using Mintstick to create a bootable USB, I can longer use my USB flash drive: I can no longer write files to it or even format it. I tried disk utility but in vein. BTW it has corrupted 2 of my USB drives last time on Linux Mint 16 and I thought you have fixed this issue on Linux Mint 17. This tool is not stable at all and I think you should fork Unetbootin instead.
and BTW it does not detect my USB drive:
I have tried downloading the ISOs three times and used two different USB writing programs (PenDriveLInux for Windows and the included USB writer in Mint) and used two different USB drives. Both times when I try to boot from the USB drive I get an error saying that it cannot mount squashfs or something to that effect. Mint 17.0 installs fine from USB stick. I am using a Kingston 8GB DataTraveller and an 8GB Lexar Pendrive if this matters. My machine is a Dell XPS 8700 with Intel i7-4770k, 8GB RAM, 1TB HDD and ATI 7570 with 1GB video RAM. Also, other users claim to have no issues at all - so that is weird. The related thread on the forums can be read here: http://forums.linuxmint.com/viewtopic.php?f=60&t=183045
** Affects Mint 17.1 / 17.2, 32/64 bit, Cinnamon and Mate editions
Steps to reproduce (Cinnamon 17.2):
Workaround: Instead of browsing with nemo to mount the network share, manually mounting into a local folder with:
$ sudo mount -t cifs //1.2.3.4/sharename ~/mymountpoint -o username=myuser
... and selecting the ISO by browsing to ~/mymountpoint works just fine.
I can't figure why this is failing. Everything under /run/user/xxxx has current user/group ownership and read/write permissions. I can only assume that the parent dir ownerships of "root:root" for /run and /run/user might be tripping mintstick up here. Interestingly, using the "sudo mount" approach above, mountpoint permissions are "root:users", but permissions are 777. Perhaps that's enough for mintstick to work.
Is it possible to add exfat as a format option? Mintstick is my go to for everything relating to a usb, and currently the best gui option for formatting in exfat is to use the gnome-disk-utility (or booting into Windows - Vomit!). Having the simple option within Mintstick would really be nice. There is an application made specifically for Elementary OS that has an exfat format option which leads me to believe that this can be implemented into Mintstick. Here's the app here on Github (it's just called formatter): https://github.com/Djaler/Formatter
Basically seems that after formating, usb pen permissions get messed up, only opening as root we are able to move/copy things to it.
For FAT32 it says "- Kann nicht mit Dateien größer als 4GB umgehen" (i.e. con: can not work with files larger than 4GB).
For exFAT it says "- Kann mit Dateien größer als 4GB umgehen" (i.e. con: can work with files larger than 4GB).
That is misleading (AFAIK for exFAT the sentence is correct, but should be a pro instead of a con).
Btw: maybe also change 4GB to 4GiB?
Seen at Mint 20.1 cinnamon-edge (version number not available, see #85).
* Nemo version: 4.4.2
* Distribution: Mint 19.3 Cinnamon
* 64 bit
Issue
Please enable renaming a USB drive:
Other information
Rename… option is shown in the Contextual Menu like for ods files
Thank you
mintstick seems not to show a version, neither in GUI nor when called from shell, even with option --debug. Usual option "--version" is not recognized.
I have seen that in Mint 20.1 cinnamon-edge.
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
Django
The Web framework for perfectionists with deadlines.
Laravel
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft
Open source projects and samples from Microsoft.
Google
Google ❤️ Open Source for everyone.
Alibaba
Alibaba Open Source for everyone
D3
Data-Driven Documents codes.
Tencent
China tencent open source team.
