tde-users December 2018

users@trinitydesktop.org

26 participants
46 discussions

New Thread: USB Hard drive not being recognized after first plug out.

by Kate Draven

> Hi Guys, > Probably nothing to do with this problem, but anyway: > > If I have a HDD connected via a USB adaptor, I've found that after an > initial plugging and use, then safely removing it, going back to it, > in the same session, it may or may not be recognised. Doing a hard > reboot seems to clear what ever causes this. Simply logging out and > logging back in doesn't seem to work. > > > -- > Best Regards: > Baron > > --------------------------------------------------------------------- I've seen this before. Sometimes it just helps to plug out the unit out and do the following. If you can, power it down, then connect it, power it back up. If it works, it's like the unit. If it doesn't, then it's software. Another thing you can try is to wait for a few mins, until the drive spins up, plug it out, wait 10s plug in again. It could be the drive is really slow to spin up. Good luck, let us know what happens. Kate

6 years

Re: Re: [trinity-users] and one thing more

by Kate Draven

> This is a multi-part message in MIME format. > --91626a50229013ceb57f9457a7f16e63ffea9a6df59ad197899567da5f6a > Content-Transfer-Encoding: 7bit > Content-Type: Text/Plain; charset="utf-8" > > said Kate Draven: > | > This is a multi-part message in MIME format. > | > --321beddf790282e20a201e2fb814b00f0e341ca0a537735f3b2940717f43 > | > Content-Transfer-Encoding: 7bit > | > Content-Type: Text/Plain; charset="us-ascii" > | > > | > when i try to start firefox: > | > > | > dep@dep-desktop:~$ firefox > | > > | > (firefox:2619): Gtk-ERROR **: GTK+ 2.x symbols detected. Using GTK+ > | > 2.x and GTK+ 3 in the same process is not supported > | > ExceptionHandler::GenerateDump cloned child 2627 > | > ExceptionHandler::SendContinueSignalToChild sent continue signal to > | > child ExceptionHandler::WaitForContinueSignal waiting for continue > | > signal... > | > > | > (crashreporter:2632): Gtk-ERROR **: GTK+ 2.x symbols detected. Using > | > GTK+ 2.x and GTK+ 3 in the same process is not supported > | > > | > again, nothing changed in either software or configuration. > | > > | > this is very, very weird. > | > -- > | > dep > | > > | > Sent with ProtonMail Secure Email. Because privacy matters. > | > > | > --321beddf790282e20a201e2fb814b00f0e341ca0a537735f3b2940717f43 > | > Content-Disposition: attachment; filename="publickey - > | > | dep(a)drippingwithirony.com.asc.pgp" > | > | > Content-Transfer-Encoding: base64 > | > Content-Type: application/pgp-key; name="publickey - > | > | dep(a)drippingwithirony.com" > | > | The last time I experienced something like this. Me hard drive was > | dying. All I can think of. > > here's something stranger still: if i dump out of TDE and start gnome, the > misbehaving applications work just fine. so i'm thinking something has > gone flaky with tde here. i'm running 14.0.5 on ubuntu 16.04LTS. > -- > dep > > Sent with ProtonMail Secure Email. Because privacy matters. > > --91626a50229013ceb57f9457a7f16e63ffea9a6df59ad197899567da5f6a > Content-Disposition: attachment; filename="publickey - dep(a)drippingwithirony.com.asc.pgp" > Content-Transfer-Encoding: base64 > Content-Type: application/pgp-key; name="publickey - dep(a)drippingwithirony.com" Create a new blank user and log into tde. If it all works, you're user is pharted. That's why I always make backups. Good luck. Kate

6 years

Re: [trinity-users] and one thing more

by Kate Draven

> This is a multi-part message in MIME format. > --321beddf790282e20a201e2fb814b00f0e341ca0a537735f3b2940717f43 > Content-Transfer-Encoding: 7bit > Content-Type: Text/Plain; charset="us-ascii" > > when i try to start firefox: > > dep@dep-desktop:~$ firefox > > (firefox:2619): Gtk-ERROR **: GTK+ 2.x symbols detected. Using GTK+ 2.x and > GTK+ 3 in the same process is not supported > ExceptionHandler::GenerateDump cloned child 2627 > ExceptionHandler::SendContinueSignalToChild sent continue signal to child > ExceptionHandler::WaitForContinueSignal waiting for continue signal... > > (crashreporter:2632): Gtk-ERROR **: GTK+ 2.x symbols detected. Using GTK+ > 2.x and GTK+ 3 in the same process is not supported > > again, nothing changed in either software or configuration. > > this is very, very weird. > -- > dep > > Sent with ProtonMail Secure Email. Because privacy matters. > > --321beddf790282e20a201e2fb814b00f0e341ca0a537735f3b2940717f43 > Content-Disposition: attachment; filename="publickey - dep(a)drippingwithirony.com.asc.pgp" > Content-Transfer-Encoding: base64 > Content-Type: application/pgp-key; name="publickey - dep(a)drippingwithirony.com" > The last time I experienced something like this. Me hard drive was dying. All I can think of. Sorry. Kate

6 years

weirdness involving the panel, gtk stuff, and everything

by dep

much peculiarity, beginning about an hour ago. first, protonmail bridge collapsed, and i route kmail through it, which required a reboot. it came back, but the little network icon now didn't come back -- i forget the tde network app, so i can't test it from the commandline -- so i can't switch to the VPN, which is a pain. then came the video setting. each reboot, i need to run nvidia settings so as to set my monitor array correctly. this has worked without fail for years. but now: dep@dep-desktop:~$ /usr/bin/nvidia-settings (nvidia-settings:2540): GLib-GObject-WARNING **: specified instance size for type 'CtkWindow' is smaller than the parent type's 'GtkWindow' instance size (nvidia-settings:2540): GLib-GObject-CRITICAL **: g_object_new: assertion 'G_TYPE_IS_OBJECT (object_type)' failed (nvidia-settings:2540): Gtk-CRITICAL **: IA__gtk_container_set_border_width: assertion 'GTK_IS_CONTAINER (container)' failed Segmentation fault (core dumped) to the best of my knowledge, i have changed nothing on the system. oh, and the kicker panel, which i have set to autohide, won't autohide. all this in the last hour. what to do? thanks in advance. -- dep Sent with ProtonMail Secure Email. Because privacy matters.

6 years

ugly VLC after Stretch

by Felmon Davis

Greets! I decided to upgrade from Jessie to Stretch last night. it seems to have worked though there are some oddities. now VLC has grotesquely large control buttons ("Pause", etc.); the interface in general seems to run on a different 'theme' and anyway is over-large. I have tried the "forced window style" option under "preferences" but none of the various options but they make no different in these respects. maybe 'CDE' comes closest. I have purged and re-installed VLC also to no avail. I have looked at the 'themes' VLC offers. awful. just want my orange-colored working interface back. the only other application I've found which has undergone similar changes is Pan - it has a more 'pastel' shaded control set which I don't appreciate but can ignore. note a complication: I had Devuan installed and just did the Stretch update but not sure of its relevance (thus I mention it). f. -- Felmon Davis

6 years

kmail foibles

by Gene Heskett

Greetings all; I have been harassed by bad index files notices, but I may have found the cause. I just went thru every folder in its Mail corpus finding several dozen leftover claws files, either in the root of each folder, in the cur or tmp subdirs, nuked them all and restarted kmail, which then bitched about every folder I had cleaned up. I closed the advisory and fully expected to see kmail hogging the cpu up to 100% for an hour or more as it had done in the past, but it was done reindexing everything in just a long minute! All of the claws crap carried dates in 2013 to 2014, which would be about the time frame I did have it installed. So if your kmail is acting likes its infected with flooby dust, see what happens if you do a bit of housecleaning in your ~/Mail subdir. I think it was getting confused over encountering strange file names. Time will tell the truth of this tail of course. -- 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>

6 years

replacement for tdelibs needs a reboot, but didn't ask for one

by Gene Heskett

I wondered about it at the time, but not doing it crashed 2 machines who were linked via an ssh login were locked up tight last night, this one and one of my machine controllers. I had to get dressed to walk up the hill in 20F weather and press the reset buttons on both it and this one. Its been yonks since a crash, took me by surprise. And I'd tried to run latency-test from linuxcnc on this machine last night after the reboot, and found a passle of rtapi_app and rtapi running this morning that weren't killable by a root session of htop. Some sort of a ghost or??, as stopping htop, and restarting it made them go away. Strange goings on but it seems to be running normally now. -- 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>

6 years

Re: Re: [trinity-users] Unable to mount this device error when using usb stick but not always

by Kate Draven

> On Tuesday 04 December 2018 08:01:22 pm Kate Draven wrote: > > > On Tuesday 04 December 2018 07:26:54 pm Kate Draven wrote: > > > > Out of the blue I started getting this error msg. > > > > Using PCLOS 64bit > > > > > > > > Unable to mount this device. > > > > Potential reasons include: > > > > Improper device and/or user privilege level > > > > Corrupt data on storage device > > > > Technical details: > > > > org.freedesktop.UDisks2.Error.Failed: Error mounting /dev/sdk1 > > > > at /media/Lexar: Command-line > > > > `mount -t "vfat" -o > > > > > > "uhelper=3Dudisks2,nodev,nosuid,uid=3D0,gid=3D0,shortname=3Dmixed,utf8= > =3D1,showexec > > >,f > > > > > > >lush,noatime,shortname=3Dlower" "/dev/sdk1" "/media/Lexar"' exited with > > > > non-zero exit status 32: mount: /mnt/Lexar: /dev/sdk1 already mounted > > > > or mount point busy. > > > > > > > > It's random and sometimes suddenly goes away. > > > > I've tried it with a variety of USB sticks. > > > > > > I've had "mount point busy" come from both an open shell and a file > > > manager that's sitting on the mount point before. It can also block us= > er > > > > un-mounting > > > > > as well (although I think root umount force un-mounts?). > > > > > > --------------------------------------------------------------------- > > > > To my knowledge there is nothing at that mount point. > > I can connect 5 usb sticks and they will all give the same error. > > 5 different sticks are almost guaranteed to have different mount points, so= > =20 > having an open shell sitting at /mnt/Lexar/mystuff wouldn=E2=80=99t whack t= > he other=20 > 4. :( > > Do you have access to another comp to test one of the sticks, so you have=20 > a =E2=80=98known good?=E2=80=99 You could then try re-installing whatever = > provides UDisks2. =20 > After that file a bug with PCLOS so they can file an upstream bug. > > Best, > Michael > > --------------------------------------------------------------------- Michael My thinking exactly. I do have several computers in me wee lab. The sticks are all fine, mount and umount on all other computers, including another pclos 64 with the same kernels. At first I thought it was a kernel bug, wrong. I can only guess I'm installing something that messes it up. I reinstalled the OS into the test computer and incrementally installing packages until I find the culprit. I've noticed some odd behavior with some trinity packages such as trinity-tdeio-umountwrapper, it removes the "safely remove" from all menus related to removable drives. I think I'm installing an incompatible packages. I've done it before. Honestly I'm my own worst enemy. Thanks for the UDisks2 tip. I'll check into that. Kate

6 years

Re: [trinity-users] Unable to mount this device error when using usb stick but not always

by Michael

On Tuesday 04 December 2018 08:01:22 pm Kate Draven wrote: > > On Tuesday 04 December 2018 07:26:54 pm Kate Draven wrote: > > > Out of the blue I started getting this error msg. > > > Using PCLOS 64bit > > > > > > Unable to mount this device. > > > Potential reasons include: > > > Improper device and/or user privilege level > > > Corrupt data on storage device > > > Technical details: > > > org.freedesktop.UDisks2.Error.Failed: Error mounting /dev/sdk1 > > > at /media/Lexar: Command-line > > > `mount -t "vfat" -o > > > > "uhelper=udisks2,nodev,nosuid,uid=0,gid=0,shortname=mixed,utf8=1,showexec > >,f > > > > >lush,noatime,shortname=lower" "/dev/sdk1" "/media/Lexar"' exited with > > > non-zero exit status 32: mount: /mnt/Lexar: /dev/sdk1 already mounted > > > or mount point busy. > > > > > > It's random and sometimes suddenly goes away. > > > I've tried it with a variety of USB sticks. > > > > I've had "mount point busy" come from both an open shell and a file > > manager that's sitting on the mount point before. It can also block user > > un-mounting > > > as well (although I think root umount force un-mounts?). > > > > --------------------------------------------------------------------- > > To my knowledge there is nothing at that mount point. > I can connect 5 usb sticks and they will all give the same error. 5 different sticks are almost guaranteed to have different mount points, so having an open shell sitting at /mnt/Lexar/mystuff wouldn’t whack the other 4. :( Do you have access to another comp to test one of the sticks, so you have a ‘known good?’ You could then try re-installing whatever provides UDisks2. After that file a bug with PCLOS so they can file an upstream bug. Best, Michael

6 years

Unable to mount this device error when using usb stick but not always

by Kate Draven

Out of the blue I started getting this error msg. Using PCLOS 64bit Unable to mount this device. Potential reasons include: Improper device and/or user privilege level Corrupt data on storage device Technical details: org.freedesktop.UDisks2.Error.Failed: Error mounting /dev/sdk1 at /media/Lexar: Command-line `mount -t "vfat" -o "uhelper=udisks2,nodev,nosuid,uid=0,gid=0,shortname=mixed,utf8=1,showexec,flush,noatime,shortname=lower" "/dev/sdk1" "/media/Lexar"' exited with non-zero exit status 32: mount: /mnt/Lexar: /dev/sdk1 already mounted or mount point busy. It's random and sometimes suddenly goes away. I've tried it with a variety of USB sticks. It happens as user and root. Anyone have any idea what this might mean. I've also noticed uuidd doesn't start, claiming "failed to open/create /run/uuidd/uuidd.pid" Thanks for any help. Kate

6 years

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

tde-users December 2018