tag:blogger.com,1999:blog-307524065547561336.comments2023-06-19T09:29:17.275-07:00Low.Fat.DaemonDaemonixhttp://www.blogger.com/profile/12590623729223339323noreply@blogger.comBlogger4125tag:blogger.com,1999:blog-307524065547561336.post-77751721937556766362019-11-14T22:50:00.292-08:002019-11-14T22:50:00.292-08:00I like your post very much. It is very much useful...I like your post very much. It is very much useful for my research. I hope you to share more info about this. Keep posting <b><a href="https://onlineitguru.com/core-java-online-training-placement.html" rel="nofollow">java online course</a></b><br />IThttps://www.blogger.com/profile/05377540743753557373noreply@blogger.comtag:blogger.com,1999:blog-307524065547561336.post-49471317026479252962017-04-20T02:05:07.401-07:002017-04-20T02:05:07.401-07:00This comment has been removed by the author.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-307524065547561336.post-69948508587331330992016-01-24T12:03:45.994-08:002016-01-24T12:03:45.994-08:00KDE Device notifier was hosed. A newly installed K...KDE Device notifier was hosed. A newly installed KDE installed with a newer distro needed merely a second to display the flash drive. I guess that the device itself contains a serial number string which never changes across formats; that string could persist in a corrupted device notifier index, where the remaining data in that record associated to the immutable device string would contain corrupted information. Ye Olde Doodhttps://www.blogger.com/profile/00970039850744065283noreply@blogger.comtag:blogger.com,1999:blog-307524065547561336.post-84546448030031453362013-06-25T14:07:06.729-07:002013-06-25T14:07:06.729-07:00So far, so good. One problem, maybe you have a tip...So far, so good. One problem, maybe you have a tip?<br /><br />The device is a Sandisk Cruzer 16Gig Flash drive.<br /><br />I have written to it with unetbootin, and tried several other methods to use it a bootable install medium and/or a bootable live distro drive. Time passes, I gave up on those, and eventually I wanted it back as a storage device once more.<br /><br />No matter what I've tried, it now takes forever to get seen in the Device Notifier of KDE (Kubuntu 12.10).<br /><br />I have fsck'd it, reformatted it as ext2, then ext3, then NTFS, then FAT32, I have tried cfdisk -z, fdisk, parted, and a few others. nothing makes this ONE flash drive mount like all my other flash media - shows in device notifier in less than a second for other flash media in my system, this ONE flash drive takes 45 seconds or more, and often never shows. When device notifier sees it, it usually works fine, but the wait is dreadful. I've even deleted all the partitions (many times) and tried using the drive as a whole device (mkdosfs -I -F 32 /dev/sdf) and it still suffers delays.<br /><br />Current iteration of format efforts has it displaying exactly one time for each login, then, if I disconnect from it, it will not show again until I restart X (and thus restart KDE).<br /><br />dmesg | tail shows the device was seen by the system in a fraction of a second, so I wonder if there is a string coming from the bowels of this device which tosses KDE for a loop.<br /><br />Any ideas for deeper remediation?Ye Olde Doodhttps://www.blogger.com/profile/00970039850744065283noreply@blogger.com