tde-users

users@trinitydesktop.org

20 participants
4181 discussions

Re: [trinity-users] konqueror classifies files with no extension as octet-stream

by Nathan Rugg

On 09/17/2016 09:57 AM, Kate Draven wrote: >> I recently installed Trinity and everything is going well except that >> konqueror classifies all files with no extension as octet-stream. Any >> idea how to fix that problem? If I use `file` from the command line like >> this `file --mime-type FILENAME`, it will give the correct mime type. >> GTK programs also work correctly. It appears to be something specific >> with TDE. >> >> Thanks. >> >> Nathan > Use kcontrol or tcontrol? Either way go to file associations. Usually under > kde/TDE Components. I don't have a TDE computer in front of me now so I'm > only going be memory. This should be enough to get you there. > > However, I have to point out that it seems odd that the distro can't identify > the files. > > Hope this helps, > > Kate Hi Kate, Thanks for the reply. I've looked in the File Associations settings, but I can't see a way to fix files without an extension. Files with an extension are recognized just fine. But konqueror should be able to check the magic number thing to determine the type of a file, but something caused this to stop working.

8 years, 4 months

konqueror classifies files with no extension as octet-stream

by Nathan Rugg

I recently installed Trinity and everything is going well except that konqueror classifies all files with no extension as octet-stream. Any idea how to fix that problem? If I use `file` from the command line like this `file --mime-type FILENAME`, it will give the correct mime type. GTK programs also work correctly. It appears to be something specific with TDE. Thanks. Nathan

8 years, 4 months

systemsettings and tdenetworkmanager switching between wired and wireless problem with DNS server

by Uwe Brauer

Hi - I used /opt/trinity/bin/systemsettings for setting the wired net - and tdenetworkmanager for the wireless net. Maybe this is not smart and I had no problems, when passing from wired --> wireless but problems when passing from wireless --> wired since the wireless deleted the DNS server entries in the resolv.conf So usually I manually copied a backup of resolv.conf to /etc and run sudo /etc/init.d/networking restart But this does not work anymore in 14.04 as we discussed. So what is the smart way of configuring wired/wireless and what is the smart way of switching between wired/wireless???? Relying entirely on systemsettings or on tdenetworkmanager? Uwe Brauer

8 years, 4 months

Reducing the number of supported distributions

by Slávek Banko

Hello to everybody, I want to inform you that for the upcoming maintenance release R14.0.4 the number of supported distributions will be reduced. Will be excluded versions of Ubuntu that are no longer supported. In the same way will be reduced distributions in the Preliminary Stable Builds repository. Supported distributions: + Debian 9 - Stretch (preliminary) + Debian 8 - Jessie + Debian 7 - Wheezy + Debian 6 - Squeeze + Raspbian Wheezy + Ubuntu 16.10 - Yakkety (preliminary) + Ubuntu 16.04 - Xenial (LTS) + Ubuntu 14.04 - Trusty (LTS) + Ubuntu 12.04 - Precise (LTS) + Ubuntu 10.04 - Lucid (LTS) Discontinued distribution: + Ubuntu 15.10 - Wily + Ubuntu 15.04 - Vivid + Ubuntu 14.10 - Utopic + Ubuntu 13.10 - Saucy + Ubuntu 13.04 - Raring + Ubuntu 12.10 - Quantal + Ubuntu 11.10 - Oneiric + Ubuntu 11.04 - Natty + Ubuntu 10.10 - Maverick Please, if you use one of discontinued Ubuntu distributions, you should consider upgrading to one of the LTS versions. Cheers -- Slávek

8 years, 4 months

Kubuntu 14.04 and trinity:problems with wired network

by Uwe Brauer

Hi This is the first time I have such an experience. I installed Kubuntu 14.04 and trinity via deb http://mirror.xcer.cz/trinity-sb trusty deps-r14 main-r14 deb-src http://mirror.xcer.cz/trinity-sb trusty deps-r14 main-r14 Everything went smooth wireless net can be configured with tdenetworkmanager, but when I try to set up the wired net, via the networktool I run into a problem. I use all the parameters I used in previous trinity + Kubuntu installations (namely 10.04 and 12.04) static IP number DNS server Gateway. The connection works for a couple of seconds and then crashes the problem see to be the Gateway, when I restart the configuration tool the value has been deleted. Anybody has an idea what do? That is a very serious problem, right now use the Wifi connection, but this has severe restriction in the network I am using. Thanks Uwe Brauer

8 years, 4 months

kweather-trinity not working

by Ken Heard

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The kweather-trinity applet version 4:14.0.3-0debian8.0.0+0 no longer works in Jessie. When I tried to use it claims that all the weather stations in the weather stations setup window do not exist. Regards, Ken Heard -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAle9zGcACgkQlNlJzOkJmTd/VQCfSa6qFaiN0BdV0A66VdHMf6jx BakAnRvVuS80XYJCbO2iQYO0vhGp8jaI =RJ7c -----END PGP SIGNATURE-----

8 years, 4 months

KMilo not working on ThinkPad R61 with Debian Wheezy

by Jan Stolarek

Dear Trinity users, I can't get KMilo plugin to work on my ThinkPad R61 under Debian Wheezy. Firstly, I need kmilo-legacy-trinity for the KMilo plugin to show up in the Control Center. The /dev/nvram device exists and has corect permissions (666). I select the checkbox to activate KMilo but nothing happens. None of the special buttons work, eg. when I press the ThinkVantage button it does not launch Konsole. The only things that work are sound and brightness control buttons, but these used to work without KMilo. Also, I believe KMilo should provide a nice OSD for sound and brightness changes but I have no OSD when changing any of these. Can anyone offer suggestions how to solve, or at least diagnose, the problem? Jan --- Politechnika Łódzka Lodz University of Technology Treść tej wiadomości zawiera informacje przeznaczone tylko dla adresata. Jeżeli nie jesteście Państwo jej adresatem, bądź otrzymaliście ją przez pomyłkę prosimy o powiadomienie o tym nadawcy oraz trwałe jej usunięcie. This email contains information intended solely for the use of the individual to whom it is addressed. If you are not the intended recipient or if you have received this message in error, please notify the sender and delete it from your system.

8 years, 4 months

fail2ban advice needed

by Gene Heskett

Greetings all; Is there someone familiar with fail2ban here? I just installed it and started it with the installation defaults, which I do not know since the init script has no "dump" option. However that bit of hungry guard dog only protects this machine, leaving the other 4 or sometimes 5 on my local network still open. So specifically, is there a way to broadcast the rules it applies to the other 4 or 5 machines, protecting them at the same time? Or possibly broadcast them to the router, which is running dd-wrt, and which is considered one of the more bulletproof reflash's about. I may be lucky, but since I do have a port forward to allow my web server, there is a potential attack point. Advice to a fail2ban new bee? Thank you. Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene>

8 years, 4 months

Re: (OT kinda) Newly-discovered TCP flaw

by Gene Heskett

On Thursday 11 August 2016 15:44:24 Doug wrote: > On 08/11/2016 12:50 PM, Gene Heskett wrote: > > On Thursday 11 August 2016 12:47:09 Nicolas George wrote: > > CC:ing emc-developers, and trinity-users who may not yet be aware of > > this tcp attack vector thats quite dangerous. And my post to > > trinity-users was in error, so this corrects it. > > > >> Le quintidi 25 thermidor, an CCXXIV, Gene Heskett a écrit : > >>> to add should be changed to forward slashes: > >> > >> You are wrong, sysctl supports both slashes and dots as separators. > >> > >> Regards, > > > > I changed it back Nicolas, and sysctl -p now returns: > > root@coyote:/etc/init.d# sysctl -p > > sysctl: cannot stat /proc/sys//net.ipv4.tcp_challenge_ack_limit: No > > such file or directory > > > > Put the slashes back and I get this: > > root@coyote:/etc/init.d# sysctl -p > > .net.ipv4.tcp_challenge_ack_limit = 999999999 > > > > Which I assume is the correct response. And yet the echo shows all > > dots. > > > > WTH? Ahh, my bad, no damned biscuit, an extra leading slash snuck > > in. But if a dot and a slash are the same to sysctl, I should have a > > file in the wrong place? But I do not. /net is empty. It is in the > > right place now. And cats the correct value. > > > > Sorry about the confusion everybody. > > > > Cheers, Gene Heskett > > Running PCLOS. I put in the original command with dots. When I run > sysctl.p from a root environment I get no response, but no error > either. Don't know the significance of that. > > --doug Neither do I Doug, sorry. See the announcement on /. today & read the link to the post from the guys that found it that is in the story, UCsomething IIRC, see below. A closer read may answer it. <https://ucrtoday.ucr.edu/39030> And please keep things like this on the list you read it from. A PM is unfair to the other readers of the list you read it on, so I'll cc the three lists it was cross posted to as it sounds pretty serious to me. And I just noted that the sysctl command you quoted above is incorrect, its sysctl -p, not sysctl.p. Maybe that helps? Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene>

8 years, 5 months

Re: (OT kinda) Newly-discovered TCP flaw

by Gene Heskett

On Thursday 11 August 2016 12:47:09 Nicolas George wrote: CC:ing emc-developers, and trinity-users who may not yet be aware of this tcp attack vector thats quite dangerous. And my post to trinity-users was in error, so this corrects it. > Le quintidi 25 thermidor, an CCXXIV, Gene Heskett a écrit : > > to add should be changed to forward slashes: > > You are wrong, sysctl supports both slashes and dots as separators. > > Regards, I changed it back Nicolas, and sysctl -p now returns: root@coyote:/etc/init.d# sysctl -p sysctl: cannot stat /proc/sys//net.ipv4.tcp_challenge_ack_limit: No such file or directory Put the slashes back and I get this: root@coyote:/etc/init.d# sysctl -p .net.ipv4.tcp_challenge_ack_limit = 999999999 Which I assume is the correct response. And yet the echo shows all dots. WTH? Ahh, my bad, no damned biscuit, an extra leading slash snuck in. But if a dot and a slash are the same to sysctl, I should have a file in the wrong place? But I do not. /net is empty. It is in the right place now. And cats the correct value. Sorry about the confusion everybody. Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene>

8 years, 5 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

tde-users