Search found 4857 matches
- Sun May 28, 2017 9:27 am
- Forum: Bugs and Non-Package Requests Forum
- Topic: [solved] USB stick good for booting but does not mount afterwards
- Replies: 5
- Views: 53
Try clicking on the exclamation symbol. It may give some information. Also you can check drive properties from the view menu. It generally means the system had trouble accessing data on the drive.
I purchased the Icydock and am very pleased with it. Hot sawp works. Ejection buttons for both 2.5 and 3.5 work well. I particularly like the power buttons for both 3.5 HDD' and 2.5 SSD allowing you not to power the drive not inserted. Also both types of drives can be present at the same time.
Well we do not have many reports of this phenomena, (2 possible), and the vast majority of users do not experience it. So it would not be appropriate to characterize it as a bug at this point. As I suggested earlier your best approach would be to reinstall and take it from there. It may be a bad bur...
Using the PM section of your user control panel you can set up PM rules. Examples include deleting messages , moving them to other folders plus others, based on sender, subject, content and other criteria.
- Fri May 26, 2017 2:38 pm
- Forum: Software / Configuration
- Topic: [Solved] MX 17 or MX 16 Stretch/Testing?
- Replies: 5
- Views: 156
Is there a site or another forum where I can learn more about them?
Undoubtedly anti, if he swishes to respond, will do so in a PM.
A few answers : $ uname -a Linux ttx 4.7.0-0.bpo.1-amd64 #1 SMP MX 4.7.8-1mx16+3 (2017-02-23) x86_64 GNU/Linux tt@ttx:~ $ apt-cache search indicator-keylock tt@ttx:~ I went to MX Tools > Package Installer and I did not find any of "Stable Repo" or "Refresh list" button. Click on...
It is in the repos for MX 15 and 16. Not sure what version of MX you are using. root@mx1:/home/richard# apt-cache policy indicator-keylock indicator-keylock: Installed: (none) Candidate: 3.0.1-2mx150+1 Version table: 3.0.1-2mx150+1 0 500 http://iso.mxrepo.com/mx/repo/ mx15/main amd64 Packages MX is ...
Since the checksum of md5 hash was quite ok, maybe something went wrong during the burning process!? That could very well be. Since you have done no configuration, a reinstall would be a good next step rather than chasing this odd issue. I would recommend burning at a slow speed, or using a USB sti...