Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #275421 > unrolled thread
| Started by | gene heskett <gheskett@shentel.net> |
|---|---|
| First post | 2024-12-09 16:00 +0100 |
| Last post | 2024-12-12 04:30 +0100 |
| Articles | 20 on this page of 130 — 19 participants |
Back to article view | Back to linux.debian.user
restart lasts maybe a minute till next freeze gene heskett <gheskett@shentel.net> - 2024-12-09 16:00 +0100
Re: restart lasts maybe a minute till next freeze Bret Busby <bret@busby.net> - 2024-12-09 16:30 +0100
Re: restart lasts maybe a minute till next freeze "Andrew M.A. Cater" <amacater@einval.com> - 2024-12-09 20:50 +0100
Re: restart lasts maybe a minute till next freeze gene heskett <gheskett@shentel.net> - 2024-12-09 22:40 +0100
Re: restart lasts maybe a minute till next freeze David Christensen <dpchrist@holgerdanske.com> - 2024-12-10 03:00 +0100
Re: restart lasts maybe a minute till next freeze gene heskett <gheskett@shentel.net> - 2024-12-10 23:00 +0100
Re: restart lasts maybe a minute till next freeze Greg Wooledge <greg@wooledge.org> - 2024-12-11 03:10 +0100
Re: restart lasts maybe a minute till next freeze David Christensen <dpchrist@holgerdanske.com> - 2024-12-11 05:10 +0100
Re: restart lasts maybe a minute till next freeze gene heskett <gheskett@shentel.net> - 2024-12-11 06:20 +0100
Re: restart lasts maybe a minute till next freeze David Christensen <dpchrist@holgerdanske.com> - 2024-12-12 02:00 +0100
Re: restart lasts maybe a minute till next freeze gene heskett <gheskett@shentel.net> - 2024-12-16 00:20 +0100
Re: restart lasts maybe a minute till next freeze Max Nikulin <manikulin@gmail.com> - 2024-12-16 15:20 +0100
Re: restart lasts maybe a minute till next freeze David Christensen <dpchrist@holgerdanske.com> - 2024-12-16 18:10 +0100
Re: restart lasts maybe a minute till next freeze David Christensen <dpchrist@holgerdanske.com> - 2024-12-11 03:10 +0100
Re: restart lasts maybe a minute till next freeze gene heskett <gheskett@shentel.net> - 2024-12-11 07:20 +0100
Re: restart lasts maybe a minute till next freeze Bob McGowan <ramjr0915@gmail.com> - 2024-12-11 08:00 +0100
Re: restart lasts maybe a minute till next freeze David Christensen <dpchrist@holgerdanske.com> - 2024-12-12 02:30 +0100
Re: restart lasts maybe a minute till next freeze "Andrew M.A. Cater" <amacater@einval.com> - 2024-12-11 22:20 +0100
Re: restart lasts maybe a minute till next freeze gene heskett <gheskett@shentel.net> - 2024-12-12 02:50 +0100
Re: restart lasts maybe a minute till next freeze David Christensen <dpchrist@holgerdanske.com> - 2024-12-12 06:00 +0100
Re: restart lasts maybe a minute till next freeze gene heskett <gheskett@shentel.net> - 2024-12-12 09:50 +0100
Re: restart lasts maybe a minute till next freeze David Christensen <dpchrist@holgerdanske.com> - 2024-12-12 18:40 +0100
Re: restart lasts maybe a minute till next freeze <tomas@tuxteam.de> - 2024-12-12 18:50 +0100
Re: restart lasts maybe a minute till next freeze gene heskett <gheskett@shentel.net> - 2024-12-12 19:20 +0100
Re: restart lasts maybe a minute till next freeze <tomas@tuxteam.de> - 2024-12-12 19:30 +0100
Re: restart lasts maybe a minute till next freeze gene heskett <gheskett@shentel.net> - 2024-12-12 21:50 +0100
Re: restart lasts maybe a minute till next freeze David Christensen <dpchrist@holgerdanske.com> - 2024-12-12 20:30 +0100
Re: restart lasts maybe a minute till next freeze eben@gmx.us - 2024-12-12 21:00 +0100
Re: restart lasts maybe a minute till next freeze Charles Curley <charlescurley@charlescurley.com> - 2024-12-12 20:30 +0100
Re: restart lasts maybe a minute till next freeze <tomas@tuxteam.de> - 2024-12-13 07:40 +0100
Re: restart lasts maybe a minute till next freeze gene heskett <gheskett@shentel.net> - 2024-12-13 08:00 +0100
Re: restart lasts maybe a minute till next freeze <tomas@tuxteam.de> - 2024-12-13 10:00 +0100
Re: restart lasts maybe a minute till next freeze gene heskett <gheskett@shentel.net> - 2024-12-13 10:50 +0100
Re: restart lasts maybe a minute till next freeze tomas@tuxteam.de - 2024-12-13 11:00 +0100
Re: restart lasts maybe a minute till next freeze gene heskett <gheskett@shentel.net> - 2024-12-13 11:30 +0100
Re: restart lasts maybe a minute till next freeze Greg Wooledge <greg@wooledge.org> - 2024-12-13 13:10 +0100
Re: restart lasts maybe a minute till next freeze Tom Dial <tddial@comcast.net> - 2024-12-14 00:50 +0100
Re: restart lasts maybe a minute till next freeze gene heskett <gheskett@shentel.net> - 2024-12-14 01:10 +0100
Re: restart lasts maybe a minute till next freeze gene heskett <gheskett@shentel.net> - 2024-12-14 01:10 +0100
Re: restart lasts maybe a minute till next freeze Max Nikulin <manikulin@gmail.com> - 2024-12-14 04:30 +0100
Re: restart lasts maybe a minute till next freeze gene heskett <gheskett@shentel.net> - 2024-12-14 05:30 +0100
Re: restart lasts maybe a minute till next freeze David Christensen <dpchrist@holgerdanske.com> - 2024-12-14 07:00 +0100
Re: restart lasts maybe a minute till next freeze gene heskett <gheskett@shentel.net> - 2024-12-14 15:30 +0100
Re: restart lasts maybe a minute till next freeze Max Nikulin <manikulin@gmail.com> - 2024-12-14 16:50 +0100
Re: restart lasts maybe a minute till next freeze David Christensen <dpchrist@holgerdanske.com> - 2024-12-14 17:40 +0100
Re: restart lasts maybe a minute till next freeze Max Nikulin <manikulin@gmail.com> - 2024-12-15 16:00 +0100
Re: restart lasts maybe a minute till next freeze gene heskett <gheskett@shentel.net> - 2024-12-14 17:50 +0100
Re: restart lasts maybe a minute till next freeze "Andrew M.A. Cater" <amacater@einval.com> - 2024-12-14 18:50 +0100
Re: restart lasts maybe a minute till next freeze Max Nikulin <manikulin@gmail.com> - 2024-12-15 05:20 +0100
Re: restart lasts maybe a minute till next freeze gene heskett <gheskett@shentel.net> - 2024-12-15 17:50 +0100
Re: restart lasts maybe a minute till next freeze Max Nikulin <manikulin@gmail.com> - 2024-12-15 16:10 +0100
SOLVED ? Re: restart lasts maybe a minute till next freeze gene heskett <gheskett@shentel.net> - 2024-12-15 18:40 +0100
Re: SOLVED ? Re: restart lasts maybe a minute till next freeze Anssi Saari <anssi.saari@debian-user.mail.kapsi.fi> - 2024-12-16 14:00 +0100
Re: restart lasts maybe a minute till next freeze David Christensen <dpchrist@holgerdanske.com> - 2024-12-14 07:00 +0100
Re: restart lasts maybe a minute till next freeze Tom Dial <tddial@comcast.net> - 2024-12-14 23:50 +0100
Re: restart lasts maybe a minute till next freeze gene heskett <gheskett@shentel.net> - 2024-12-13 11:20 +0100
Re: restart lasts maybe a minute till next freeze Max Nikulin <manikulin@gmail.com> - 2024-12-13 04:30 +0100
Re: restart lasts maybe a minute till next freeze gene heskett <gheskett@shentel.net> - 2024-12-13 07:40 +0100
Re: restart lasts maybe a minute till next freeze <tomas@tuxteam.de> - 2024-12-13 07:50 +0100
Re: restart lasts maybe a minute till next freeze gene heskett <gheskett@shentel.net> - 2024-12-13 08:10 +0100
Re: restart lasts maybe a minute till next freeze pocket@homemail.com - 2024-12-13 15:10 +0100
Re: restart lasts maybe a minute till next freeze Greg Wooledge <greg@wooledge.org> - 2024-12-13 15:10 +0100
Re: restart lasts maybe a minute till next freeze pocket@homemail.com - 2024-12-13 15:30 +0100
Re: restart lasts maybe a minute till next freeze gene heskett <gheskett@shentel.net> - 2024-12-13 16:20 +0100
Re: restart lasts maybe a minute till next freeze gene heskett <gheskett@shentel.net> - 2024-12-13 15:40 +0100
Re: restart lasts maybe a minute till next freeze Andy Smith <andy@strugglers.net> - 2024-12-13 18:40 +0100
Re: restart lasts maybe a minute till next freeze Charles Curley <charlescurley@charlescurley.com> - 2024-12-13 16:10 +0100
Re: restart lasts maybe a minute till next freeze Max Nikulin <manikulin@gmail.com> - 2024-12-13 17:20 +0100
Re: restart lasts maybe a minute till next freeze Greg Wooledge <greg@wooledge.org> - 2024-12-13 17:50 +0100
Re: restart lasts maybe a minute till next freeze Greg Wooledge <greg@wooledge.org> - 2024-12-13 18:20 +0100
Re: restart lasts maybe a minute till next freeze gene heskett <gheskett@shentel.net> - 2024-12-13 21:20 +0100
Re: restart lasts maybe a minute till next freeze Max Nikulin <manikulin@gmail.com> - 2024-12-13 18:20 +0100
Re: restart lasts maybe a minute till next freeze gene heskett <gheskett@shentel.net> - 2024-12-13 17:40 +0100
Re: restart lasts maybe a minute till next freeze David Christensen <dpchrist@holgerdanske.com> - 2024-12-13 18:50 +0100
Re: restart lasts maybe a minute till next freeze Andy Smith <andy@strugglers.net> - 2024-12-13 18:30 +0100
Re: restart lasts maybe a minute till next freeze <tomas@tuxteam.de> - 2024-12-13 19:30 +0100
Installer and assistive technologies (was: Re: restart lasts maybe a minute till next freeze) Max Nikulin <manikulin@gmail.com> - 2024-12-13 16:00 +0100
Re: Installer and assistive technologies (was: Re: restart lasts maybe aminute till next freeze) gene heskett <gheskett@shentel.net> - 2024-12-13 16:40 +0100
Re: Installer and assistive technologies (was: Re: restart lasts maybe aminute till next freeze) "Andrew M.A. Cater" <amacater@einval.com> - 2024-12-13 19:50 +0100
Re: Installer and assistive technologies (was: Re: restart lastsmaybe aminute till next freeze) gene heskett <gheskett@shentel.net> - 2024-12-13 22:10 +0100
Re: Installer and assistive technologies David Christensen <dpchrist@holgerdanske.com> - 2024-12-14 09:00 +0100
Re: Installer and assistive technologies gene heskett <gheskett@shentel.net> - 2024-12-14 15:50 +0100
Re: Installer and assistive technologies David Christensen <dpchrist@holgerdanske.com> - 2024-12-14 18:40 +0100
Re: Installer and assistive technologies gene heskett <gheskett@shentel.net> - 2024-12-14 21:50 +0100
Re: Installer and assistive technologies David Christensen <dpchrist@holgerdanske.com> - 2024-12-14 22:30 +0100
Orca install repeating - can't reproduce [WAS Re: Installer and assistive technologies] "Andrew M.A. Cater" <amacater@einval.com> - 2024-12-14 23:30 +0100
Re: Orca install repeating - can't reproduce [WAS Re: Installer and assistive technologies] Max Nikulin <manikulin@gmail.com> - 2024-12-15 05:10 +0100
Re: Orca install repeating - can't reproduce [WAS Re: Installer andassistive technologies] gene heskett <gheskett@shentel.net> - 2024-12-15 14:30 +0100
Re: Orca install repeating - can't reproduce [WAS Re: Installer andassistive technologies] Max Nikulin <manikulin@gmail.com> - 2024-12-15 15:50 +0100
Re: Orca install repeating - can't reproduce [WAS Re: Installerandassistive technologies] gene heskett <gheskett@shentel.net> - 2024-12-15 18:10 +0100
Re: Orca install repeating - can't reproduce [WAS Re: Installerandassistive technologies] "Andrew M.A. Cater" <amacater@einval.com> - 2024-12-15 18:40 +0100
SOLVED Re: Orca install repeating - can't reproduce [WAS Re:Installerandassistive technologies] gene heskett <gheskett@shentel.net> - 2024-12-15 19:00 +0100
Re: Orca install repeating - can't reproduce [WAS Re: Installer and assistive technologies] Michael Stone <mstone@debian.org> - 2024-12-15 15:30 +0100
Re: Orca install repeating - can't reproduce [WAS Re: Installer and assistive technologies] Jeffrey Walton <noloader@gmail.com> - 2024-12-15 19:30 +0100
Re: restart lasts maybe a minute till next freeze Andy Smith <andy@strugglers.net> - 2024-12-13 18:30 +0100
Re: restart lasts maybe a minute till next freeze Larry Martell <larry.martell@gmail.com> - 2024-12-13 22:00 +0100
Re: restart lasts maybe a minute till next freeze gene heskett <gheskett@shentel.net> - 2024-12-13 22:50 +0100
Re: restart lasts maybe a minute till next freeze gene heskett <gheskett@shentel.net> - 2024-12-13 23:00 +0100
Re: restart lasts maybe a minute till next freeze <tomas@tuxteam.de> - 2024-12-14 07:50 +0100
Re: restart lasts maybe a minute till next freeze Anssi Saari <anssi.saari@debian-user.mail.kapsi.fi> - 2024-12-16 17:50 +0100
Re: restart lasts maybe a minute till next freeze gene heskett <gheskett@shentel.net> - 2024-12-13 22:00 +0100
Re: restart lasts maybe a minute till next freeze Greg Wooledge <greg@wooledge.org> - 2024-12-13 22:10 +0100
Re: restart lasts maybe a minute till next freeze gene heskett <gheskett@shentel.net> - 2024-12-13 22:50 +0100
Re: restart lasts maybe a minute till next freeze David Christensen <dpchrist@holgerdanske.com> - 2024-12-14 07:00 +0100
Re: restart lasts maybe a minute till next freeze gene heskett <gheskett@shentel.net> - 2024-12-14 15:30 +0100
Re: restart lasts maybe a minute till next freeze <tomas@tuxteam.de> - 2024-12-14 16:10 +0100
Re: restart lasts maybe a minute till next freeze gene heskett <gheskett@shentel.net> - 2024-12-14 17:30 +0100
Re: restart lasts maybe a minute till next freeze "Thomas Schmitt" <scdbackup@gmx.net> - 2024-12-14 18:40 +0100
Re: restart lasts maybe a minute till next freeze gene heskett <gheskett@shentel.net> - 2024-12-14 21:30 +0100
Re: restart lasts maybe a minute till next freeze "Thomas Schmitt" <scdbackup@gmx.net> - 2024-12-15 10:50 +0100
Re: restart lasts maybe a minute till next freeze Max Nikulin <manikulin@gmail.com> - 2024-12-15 16:40 +0100
Re: restart lasts maybe a minute till next freeze gene heskett <gheskett@shentel.net> - 2024-12-15 19:00 +0100
Re: restart lasts maybe a minute till next freeze Andy Smith <andy@strugglers.net> - 2024-12-14 20:40 +0100
Re: restart lasts maybe a minute till next freeze Michael Stone <mstone@debian.org> - 2024-12-14 21:10 +0100
Re: restart lasts maybe a minute till next freeze "Thomas Schmitt" <scdbackup@gmx.net> - 2024-12-14 21:10 +0100
Re: restart lasts maybe a minute till next freeze gene heskett <gheskett@shentel.net> - 2024-12-14 21:50 +0100
Re: restart lasts maybe a minute till next freeze Max Nikulin <manikulin@gmail.com> - 2024-12-14 16:30 +0100
Re: restart lasts maybe a minute till next freeze David Christensen <dpchrist@holgerdanske.com> - 2024-12-14 17:30 +0100
Re: restart lasts maybe a minute till next freeze gene heskett <gheskett@shentel.net> - 2024-12-14 18:00 +0100
Re: restart lasts maybe a minute till next freeze gene heskett <gheskett@shentel.net> - 2024-12-12 18:50 +0100
Re: restart lasts maybe a minute till next freeze David Christensen <dpchrist@holgerdanske.com> - 2024-12-12 19:00 +0100
Re: restart lasts maybe a minute till next freeze Max Nikulin <manikulin@gmail.com> - 2024-12-13 04:20 +0100
Re: restart lasts maybe a minute till next freeze gene heskett <gheskett@shentel.net> - 2024-12-13 07:40 +0100
Disabling orca (was: Re: restart lasts maybe a minute till next freeze) Max Nikulin <manikulin@gmail.com> - 2024-12-13 16:10 +0100
Re: restart lasts maybe a minute till next freeze Max Nikulin <manikulin@gmail.com> - 2024-12-12 13:30 +0100
Re: restart lasts maybe a minute till next freeze gene heskett <gheskett@shentel.net> - 2024-12-12 16:40 +0100
Re: restart lasts maybe a minute till next freeze David Christensen <dpchrist@holgerdanske.com> - 2024-12-12 02:30 +0100
Re: restart lasts maybe a minute till next freeze Andy Smith <andy@strugglers.net> - 2024-12-12 02:50 +0100
Re: restart lasts maybe a minute till next freeze gene heskett <gheskett@shentel.net> - 2024-12-12 04:10 +0100
Re: restart lasts maybe a minute till next freeze Greg Wooledge <greg@wooledge.org> - 2024-12-12 04:30 +0100
Page 2 of 7 — ← Prev page 1 [2] 3 4 5 6 7 Next page →
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2024-12-12 09:50 +0100 |
| Message-ID | <JSN3r-glxM-3@gated-at.bofh.it> |
| In reply to | #275558 |
On 12/11/24 23:52, David Christensen wrote: > On 12/11/24 17:42, gene heskett wrote: >> First, I don't own a wired mouse except the serial interfaced one on >> my now dead from nearly 40 yo caps trs-80 color computer > > > I thought you ran a graphical desktop environment (?). Doing so > without a pointing device sounds like a lot of work. > > > If a lack of a pointing device causes d-i to install accessibility > tools that you do not want, I suggest connecting a pointing device > during installation. The point you are missing is hat the mouse is a wireless mouse, rx'd by a usb button. There is not a surviving wired mouse in West Virginia. I suggested that the installer was broken and got all kinds of hell for that. So let me ask then what the heck do I use for a pointing device????? _ALL_ other usb stuff was unplugged for those roughly 30 installs. Apt would not remove them after the install, complaining about dependencies. So I wound up finding and rm'ing the executables. Having orca yelling every keystroke at around 130 db, during which time other keystrokes are missed makes using a computer VERY frustrating. I am hoping however, that by the time trixie is out, that might be fixed. But the attitude seems to indicate it won't be. This however, is still buckets better than fedora where you are always the sickly lab rat. But possibly another clue. As I type this, t-b is trying to save the draft every 5 minutes and failing, popping up a requestor asking if it should wait or quit. Any key cancels the requester, and the bottom line of t-b says copy failed. Another is that about half the time, send is instant, but the next time it might take 2 to 5 more minutes, size of msgs doesn't seem to have any effect. IMO, we are wasting everybodies time, I am generally getting what I want to do, done, sometimes slower, but still getting it done. Learning composition tricks that speed up OpenSCAD. Uptime's are generally in the 2 week category till it totally freezes half way to the next workspace, which I usually have a dozen of with up to 8 tabs per workspace open. I'm running t-b from the cli as me, and I've chowned -R gene:gene /home many times in case its a perms problem. t-b seems to have problems. > >> 3. So hooking that up would probably trigger the install of orca and >> brltty despite specifically skipping by that question from the >> installer.. IDK, haven't tried it. > > > I have an older PS/2 VGA KVM switch with too many adapters. The mouse > and/or keyboard die periodically, and I must power cycle the right > equipment to get them working again. I run the Xfce desktop, and the > KVM episodes do not trigger installation of accessibility software. > > >> Won't do this below either, because putting it back together would be >> the equ of pulling a new mobo out of the box and building it all up >> from scratch again. > > > Yes. Reduce complexity, document your work so that it is repeatable, > and you will be in a much better position to troubleshoot any issues. > > >> Those 2 slots, rumor has it only 1 will work, but which one? No one >> can tell me. > > > On 12/9/24 17:51, David Christensen wrote: > >> 2. Connect the 1 TB WD Black M.2 NVMe PCIe x4 SSD into motherboard > >> slot M.2_1. > > > Please RTFM: > > https://www.asus.com/motherboards-components/motherboards/prime/prime-z370-a-ii/helpdesk_manual?model2Name=PRIME-Z370-A-II > > > >> They are buried UNDER several other cards, > > > That should be removed during the next fresh install. > > >> Maybe by then wifi will be secure, it is sure not now when a neighbor >> with a hell fone can use 60GB of my bandwidth a month w/o leaving a >> log. That was not found until i had a new printer do a band scan and >> it showed up in my ipv4 address block. > > > Please configure your gateway and/or access points: > > - Enable WPA2/WPA3 security and set a secure password. > > - Enable MAC filtering, enter the MAC addresses of your devices, and > block all other MAC addresses. > > > David > > . Cheers, Gene Heskett, CET. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis
[toc] | [prev] | [next] | [standalone]
| From | David Christensen <dpchrist@holgerdanske.com> |
|---|---|
| Date | 2024-12-12 18:40 +0100 |
| Message-ID | <JSVkl-grJN-3@gated-at.bofh.it> |
| In reply to | #275562 |
On 12/12/24 00:44, gene heskett wrote: > > On 12/11/24 23:52, David Christensen wrote: >> On 12/11/24 17:42, gene heskett wrote: >>> First, I don't own a wired mouse except the serial interfaced one on >>> my now dead from nearly 40 yo caps trs-80 color computer >> >> >> I thought you ran a graphical desktop environment (?). Doing so >> without a pointing device sounds like a lot of work. >> >> >> If a lack of a pointing device causes d-i to install accessibility >> tools that you do not want, I suggest connecting a pointing device >> during installation. > > The point you are missing is hat the mouse is a wireless mouse, rx'd by > a usb button. So, that mouse is incompatible with d-i. Use a mouse that is compatible. I prefer Microsoft Wheel Mouse Optical USB and PS/2 Compatible. They work with every computer and KVM switch I use. David
[toc] | [prev] | [next] | [standalone]
| From | <tomas@tuxteam.de> |
|---|---|
| Date | 2024-12-12 18:50 +0100 |
| Message-ID | <JSVu2-grNv-7@gated-at.bofh.it> |
| In reply to | #275588 |
[Multipart message — attachments visible in raw view] — view raw
On Thu, Dec 12, 2024 at 09:29:23AM -0800, David Christensen wrote: > On 12/12/24 00:44, gene heskett wrote: > > > > On 12/11/24 23:52, David Christensen wrote: > > > On 12/11/24 17:42, gene heskett wrote: > > > > First, I don't own a wired mouse except the serial interfaced > > > > one on my now dead from nearly 40 yo caps trs-80 color computer > > > > > > > > > I thought you ran a graphical desktop environment (?). Doing so > > > without a pointing device sounds like a lot of work. > > > > > > > > > If a lack of a pointing device causes d-i to install accessibility > > > tools that you do not want, I suggest connecting a pointing device > > > during installation. > > > > The point you are missing is hat the mouse is a wireless mouse, rx'd by > > a usb button. > > > So, that mouse is incompatible with d-i. Use a mouse that is compatible. I > prefer Microsoft Wheel Mouse Optical USB and PS/2 Compatible. They work > with every computer and KVM switch I use. For some weird reason, it seems that said mouse is hitting a "braille device" entry in the USB database? Either the database is in error, or the mouse vendor is cheating, doesn't want to pay their fees to the consortium and is stealing an ID. This, at least, is my hunch. Gene, if you want to do us a favour: do a "sudo lsusb -vv" and show us the entry which corresponds to the mouse (the output to the command above is *long*, so be careful). Cheers -- t
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2024-12-12 19:20 +0100 |
| Message-ID | <JSVX3-gsdk-19@gated-at.bofh.it> |
| In reply to | #275590 |
Bus 003 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 0 bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x046d Logitech, Inc. idProduct 0xc52b Unifying Receiver bcdDevice 12.11 iManufacturer 1 Logitech iProduct 2 USB Receiver iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 0x0054 bNumInterfaces 3 bConfigurationValue 1 iConfiguration 4 RQR12.11_B0032 bmAttributes 0xa0 (Bus Powered) Remote Wakeup MaxPower 98mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 3 Human Interface Device bInterfaceSubClass 1 Boot Interface Subclass bInterfaceProtocol 1 Keyboard iInterface 0 HID Device Descriptor: bLength 9 bDescriptorType 33 bcdHID 1.11 bCountryCode 0 Not supported bNumDescriptors 1 bDescriptorType 34 Report wDescriptorLength 59 Report Descriptors: ** UNAVAILABLE ** Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0008 1x 8 bytes bInterval 8 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 3 Human Interface Device bInterfaceSubClass 1 Boot Interface Subclass bInterfaceProtocol 2 Mouse iInterface 0 HID Device Descriptor: bLength 9 bDescriptorType 33 bcdHID 1.11 bCountryCode 0 Not supported bNumDescriptors 1 bDescriptorType 34 Report wDescriptorLength 148 Report Descriptors: ** UNAVAILABLE ** Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0008 1x 8 bytes bInterval 2 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 2 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 3 Human Interface Device bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 HID Device Descriptor: bLength 9 bDescriptorType 33 bcdHID 1.11 bCountryCode 0 Not supported bNumDescriptors 1 bDescriptorType 34 Report wDescriptorLength 93 Report Descriptors: ** UNAVAILABLE ** Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0020 1x 32 bytes bInterval 2 can't get device qualifier: Resource temporarily unavailable can't get debug descriptor: Resource temporarily unavailable Device Status: 0x0000 (Bus Powered) On 12/12/24 12:42, tomas@tuxteam.de wrote: > sudo lsusb -vv Cheers, Gene Heskett, CET. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis
[toc] | [prev] | [next] | [standalone]
| From | <tomas@tuxteam.de> |
|---|---|
| Date | 2024-12-12 19:30 +0100 |
| Message-ID | <JSW6J-gsgs-1@gated-at.bofh.it> |
| In reply to | #275595 |
[Multipart message — attachments visible in raw view] — view raw
On Thu, Dec 12, 2024 at 01:15:54PM -0500, gene heskett wrote: > Bus 003 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver > Device Descriptor: [...] Thanks, Gene. Unfortunately, I don't see anything supporting my hypothesis. The mystery remains. Cheers -- t
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2024-12-12 21:50 +0100 |
| Message-ID | <JSYie-gtvJ-19@gated-at.bofh.it> |
| In reply to | #275598 |
On 12/12/24 13:28, tomas@tuxteam.de wrote: > On Thu, Dec 12, 2024 at 01:15:54PM -0500, gene heskett wrote: >> Bus 003 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver >> Device Descriptor: > [...] > > Thanks, Gene. > > Unfortunately, I don't see anything supporting my hypothesis. > > The mystery remains. > > Cheers That it does, thanks for taking a look Tomas. Cheers, Gene Heskett, CET. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis
[toc] | [prev] | [next] | [standalone]
| From | David Christensen <dpchrist@holgerdanske.com> |
|---|---|
| Date | 2024-12-12 20:30 +0100 |
| Message-ID | <JSX2N-gsPA-9@gated-at.bofh.it> |
| In reply to | #275595 |
On 12/12/24 10:15, gene heskett wrote: > Bus 003 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver > Device Descriptor: I would remove the USB receiver, the wireless keyboard, and the wireless mouse. Connect a known good wired USB keyboard and a known good wired USB mouse. Then try the teardown and install. David
[toc] | [prev] | [next] | [standalone]
| From | eben@gmx.us |
|---|---|
| Date | 2024-12-12 21:00 +0100 |
| Message-ID | <JSXvQ-gsZk-7@gated-at.bofh.it> |
| In reply to | #275603 |
On 12/12/24 14:25, David Christensen wrote: > On 12/12/24 10:15, gene heskett wrote: >> Bus 003 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver >> Device Descriptor: > > I would remove the USB receiver, the wireless keyboard, and the wireless > mouse. Connect a known good wired USB keyboard and a known good wired USB > mouse. Then try the teardown and install. Or no mouse, if you really want fewer drivers in the mix. X is functional without a mouse, but I wouldn't want to do it as a matter of course.
[toc] | [prev] | [next] | [standalone]
| From | Charles Curley <charlescurley@charlescurley.com> |
|---|---|
| Date | 2024-12-12 20:30 +0100 |
| Message-ID | <JSX2N-gsPA-19@gated-at.bofh.it> |
| In reply to | #275595 |
On Thu, 12 Dec 2024 13:15:54 -0500
gene heskett <gheskett@shentel.net> wrote:
> Bus 003 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver
Well, that's interesting. I have one of those; I'm using it right now.
I vaguely recall buying it about ten years ago. It works fine for me.
However, it is possible that Gene and I have different chip sets, either
in the receiver or in the keyboard or rodent, that make for some subtle
differences.
Just for the halibut:
--------------------------------------------------
charles@hawk:~$ lsusb -s 2:6 -vv
Bus 002 Device 006: ID 046d:c52b Logitech, Inc. Unifying Receiver
Couldn't open device, some information will be missing
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 32
idVendor 0x046d Logitech, Inc.
idProduct 0xc52b Unifying Receiver
bcdDevice 24.10
iManufacturer 1 Logitech
iProduct 2 USB Receiver
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 0x0054
bNumInterfaces 3
bConfigurationValue 1
iConfiguration 4
bmAttributes 0xa0
(Bus Powered)
Remote Wakeup
MaxPower 98mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass 1 Boot Interface Subclass
bInterfaceProtocol 1 Keyboard
iInterface 0
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.11
bCountryCode 0 Not supported
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 59
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0008 1x 8 bytes
bInterval 8
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass 1 Boot Interface Subclass
bInterfaceProtocol 2 Mouse
iInterface 0
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.11
bCountryCode 0 Not supported
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 148
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0008 1x 8 bytes
bInterval 2
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 2
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass 0
bInterfaceProtocol 0
iInterface 0
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.11
bCountryCode 0 Not supported
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 98
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0020 1x 32 bytes
bInterval 2
charles@hawk:~$ lsusb -V
lsusb (usbutils) 014
charles@hawk:~$
--------------------------------------------------
--
Does anybody read signatures any more?
https://charlescurley.com
https://charlescurley.com/blog/
[toc] | [prev] | [next] | [standalone]
| From | <tomas@tuxteam.de> |
|---|---|
| Date | 2024-12-13 07:40 +0100 |
| Message-ID | <JT7vb-gzlA-3@gated-at.bofh.it> |
| In reply to | #275604 |
[Multipart message — attachments visible in raw view] — view raw
On Thu, Dec 12, 2024 at 05:38:13PM -0600, David Wright wrote: > On Thu 12 Dec 2024 at 12:26:11 (-0700), Charles Curley wrote: > > On Thu, 12 Dec 2024 13:15:54 -0500 > > gene heskett <gheskett@shentel.net> wrote: > > > > > Bus 003 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver > > > > Well, that's interesting. I have one of those; I'm using it right now. > > I vaguely recall buying it about ten years ago. It works fine for me. > > > > However, it is possible that Gene and I have different chip sets, either > > in the receiver or in the keyboard or rodent, that make for some subtle > > differences. > > Stepping back a moment — > > Andy Cater wrote "The 30 installs you did resulted in a whole stream > of annoyed emails: that was almost entirely because you had a USB > serial device. Simplify, simplify, simplify." [...] > So now Gene describes his mouse, and takes the opportunity to > recapitulate all (some of?) his woes, starting with the speaking > installer, and then moving on to the 30-sec requester lag, > not forgetting the tbird problem and the freeze. Suddenly the > poor old mouse is under suspicion as the source of all Gene's woes. [...] > Seems unlikely. I'm in agreement with Andy Cater and Andy Smith. That would mean that, with "just" that mouse on USB (and perhaps a keyboard), the installer wouldn't try to yell at Gene anymore. Is this so, Gene? You don't have to follow through with the installation, mind you: just going so far as to ascertain whether it starts in "vision impaired" mode; OTOH I'd accept that your curiosity is limited at this point. AFAIK, and having had a look at the Linux USB ID repo [1], where vendor and ID are alright (the clear text part in the lsusb output also confirms that), I'd exculpate that mouse. My main hypothesis (that the installer at some point (mis-)identified some widget hanging off the USB as a device a vision impaired person would have had and helpfully switching to audio mode) stays. Cheers [1] http://www.linux-usb.org/usb-ids.html -- t
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2024-12-13 08:00 +0100 |
| Message-ID | <JT7Ox-gzt6-1@gated-at.bofh.it> |
| In reply to | #275620 |
On 12/13/24 01:36, tomas@tuxteam.de wrote: > On Thu, Dec 12, 2024 at 05:38:13PM -0600, David Wright wrote: >> On Thu 12 Dec 2024 at 12:26:11 (-0700), Charles Curley wrote: >>> On Thu, 12 Dec 2024 13:15:54 -0500 >>> gene heskett <gheskett@shentel.net> wrote: >>> >>>> Bus 003 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver >>> Well, that's interesting. I have one of those; I'm using it right now. >>> I vaguely recall buying it about ten years ago. It works fine for me. >>> >>> However, it is possible that Gene and I have different chip sets, either >>> in the receiver or in the keyboard or rodent, that make for some subtle >>> differences. >> Stepping back a moment — >> >> Andy Cater wrote "The 30 installs you did resulted in a whole stream >> of annoyed emails: that was almost entirely because you had a USB >> serial device. Simplify, simplify, simplify." > [...] > >> So now Gene describes his mouse, and takes the opportunity to >> recapitulate all (some of?) his woes, starting with the speaking >> installer, and then moving on to the 30-sec requester lag, >> not forgetting the tbird problem and the freeze. Suddenly the >> poor old mouse is under suspicion as the source of all Gene's woes. > [...] > >> Seems unlikely. I'm in agreement with Andy Cater and Andy Smith. > That would mean that, with "just" that mouse on USB (and perhaps > a keyboard), the installer wouldn't try to yell at Gene anymore. > > Is this so, Gene? That was the system config at the original install, and every one of the subsequent installs, nothing I did with the installer prevented it from installing orca and brltty. Text only, several variations of graphical have been tried. Another clue perhaps: where does t-bird try to save a draft copy of a msg while editing it?, its driving me crazy with failed to write a draft msg every 5 minutes. > You don't have to follow through with the installation, mind you: > just going so far as to ascertain whether it starts in "vision > impaired" mode; OTOH I'd accept that your curiosity is limited at > this point. > > AFAIK, and having had a look at the Linux USB ID repo [1], where > vendor and ID are alright (the clear text part in the lsusb output > also confirms that), I'd exculpate that mouse. > > My main hypothesis (that the installer at some point (mis-)identified > some widget hanging off the USB as a device a vision impaired person > would have had and helpfully switching to audio mode) stays. I agree with that but dammit system, give me a clue, its not bitching, just lagging quietly but the system is frozen during the lag. > > Cheers > > [1] http://www.linux-usb.org/usb-ids.html Cheers, Gene Heskett, CET. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis
[toc] | [prev] | [next] | [standalone]
| From | <tomas@tuxteam.de> |
|---|---|
| Date | 2024-12-13 10:00 +0100 |
| Message-ID | <JT9GF-gAF2-5@gated-at.bofh.it> |
| In reply to | #275623 |
[Multipart message — attachments visible in raw view] — view raw
On Fri, Dec 13, 2024 at 01:53:55AM -0500, gene heskett wrote: [...] > That was the system config at the original install, and every one of the > subsequent installs, nothing I did with the installer prevented it from > installing orca and brltty. Text only, several variations of graphical have > been tried. Hm. Difficult to tell, then. > Another clue perhaps: where does t-bird try to save a draft copy of a msg > while editing it?, its driving me crazy with failed to write a draft msg > every 5 minutes. I'd venture the strong guess that this is a totally unrelated rabbit hole. In our trade, there are several of them, as you quite certainly know. Cheers -- t
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2024-12-13 10:50 +0100 |
| Message-ID | <JTat3-gBcW-1@gated-at.bofh.it> |
| In reply to | #275626 |
On 12/13/24 03:52, tomas@tuxteam.de wrote: > On Fri, Dec 13, 2024 at 01:53:55AM -0500, gene heskett wrote: > > [...] > >> That was the system config at the original install, and every one of the >> subsequent installs, nothing I did with the installer prevented it from >> installing orca and brltty. Text only, several variations of graphical have >> been tried. > Hm. Difficult to tell, then. > >> Another clue perhaps: where does t-bird try to save a draft copy of a msg >> while editing it?, its driving me crazy with failed to write a draft msg >> every 5 minutes. > I'd venture the strong guess that this is a totally unrelated rabbit > hole. In our trade, there are several of them, as you quite certainly > know. > > Cheers Wherever it try's, t-b seemto be interpreting the lag as a possible perms denial. I did an ls -lR on the directory in home where I put the unpacked .xz, and I own every byte of it. The only thing I don't own in /home/gene is .. That's root:root as expected. Cheers, Gene Heskett, CET. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis
[toc] | [prev] | [next] | [standalone]
| From | tomas@tuxteam.de |
|---|---|
| Date | 2024-12-13 11:00 +0100 |
| Message-ID | <JTaCK-gBgH-1@gated-at.bofh.it> |
| In reply to | #275627 |
[Multipart message — attachments visible in raw view] — view raw
On Fri, Dec 13, 2024 at 04:48:09AM -0500, gene heskett wrote: > > On 12/13/24 03:52, tomas@tuxteam.de wrote: > > On Fri, Dec 13, 2024 at 01:53:55AM -0500, gene heskett wrote: > > > > [...] > > > > > That was the system config at the original install, and every one of the > > > subsequent installs, nothing I did with the installer prevented it from > > > installing orca and brltty. Text only, several variations of graphical have > > > been tried. > > Hm. Difficult to tell, then. > > > > > Another clue perhaps: where does t-bird try to save a draft copy of a msg > > > while editing it?, its driving me crazy with failed to write a draft msg > > > every 5 minutes. > > I'd venture the strong guess that this is a totally unrelated rabbit > > hole. In our trade, there are several of them, as you quite certainly > > know. > > > > Cheers > Wherever it try's, t-b seemto be interpreting the lag as a possible perms > denial. I did an ls -lR on the directory in home where I put the unpacked > .xz, and I own every byte of it. The only thing I don't own in /home/gene is > .. That's root:root as expected. Sorry. I'm totally confused. I don't even understand what you are trying to say here. Cheers -- t
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2024-12-13 11:30 +0100 |
| Message-ID | <JTb5L-gBHq-3@gated-at.bofh.it> |
| In reply to | #275628 |
On 12/13/24 04:59, tomas@tuxteam.de wrote: > On Fri, Dec 13, 2024 at 04:48:09AM -0500, gene heskett wrote: >> On 12/13/24 03:52, tomas@tuxteam.de wrote: >>> On Fri, Dec 13, 2024 at 01:53:55AM -0500, gene heskett wrote: >>> >>> [...] >>> >>>> That was the system config at the original install, and every one of the >>>> subsequent installs, nothing I did with the installer prevented it from >>>> installing orca and brltty. Text only, several variations of graphical have >>>> been tried. >>> Hm. Difficult to tell, then. >>> >>>> Another clue perhaps: where does t-bird try to save a draft copy of a msg >>>> while editing it?, its driving me crazy with failed to write a draft msg >>>> every 5 minutes. >>> I'd venture the strong guess that this is a totally unrelated rabbit >>> hole. In our trade, there are several of them, as you quite certainly >>> know. >>> >>> Cheers >> Wherever it try's, t-b seemto be interpreting the lag as a possible perms >> denial. I did an ls -lR on the directory in home where I put the unpacked >> .xz, and I own every byte of it. The only thing I don't own in /home/gene is >> .. That's root:root as expected. > Sorry. I'm totally confused. I don't even understand what you are trying to > say here. > > Cheers Exploring the possibility of accidentally making some part of the $PATH owned by root. No hits. Cheers, Gene Heskett, CET. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis
[toc] | [prev] | [next] | [standalone]
| From | Greg Wooledge <greg@wooledge.org> |
|---|---|
| Date | 2024-12-13 13:10 +0100 |
| Message-ID | <JTcEx-gCNe-5@gated-at.bofh.it> |
| In reply to | #275627 |
On Fri, Dec 13, 2024 at 04:48:09 -0500, gene heskett wrote: > Wherever it try's, t-b seemto be interpreting the lag as a possible perms > denial. Based on what evidence? What ERROR MESSAGE do you see that leads you to this conclusion?
[toc] | [prev] | [next] | [standalone]
| From | Tom Dial <tddial@comcast.net> |
|---|---|
| Date | 2024-12-14 00:50 +0100 |
| Message-ID | <JTnzX-gN5L-3@gated-at.bofh.it> |
| In reply to | #275627 |
On 12/13/24 02:48, gene heskett wrote: > On 12/13/24 03:52, tomas@tuxteam.de wrote: >> On Fri, Dec 13, 2024 at 01:53:55AM -0500, gene heskett wrote: >> >> [...] >> >>> That was the system config at the original install, and every one of the >>> subsequent installs, nothing I did with the installer prevented it from >>> installing orca and brltty. Text only, several variations of graphical have >>> been tried. >> Hm. Difficult to tell, then. >> >>> Another clue perhaps: where does t-bird try to save a draft copy of a msg >>> while editing it?, its driving me crazy with failed to write a draft msg >>> every 5 minutes. >> I'd venture the strong guess that this is a totally unrelated rabbit >> hole. In our trade, there are several of them, as you quite certainly >> know. >> >> Cheers > Wherever it try's, t-b seemto be interpreting the lag as a possible perms denial. I did an ls -lR on the directory in home where I put the unpacked .xz, and I own every byte of it. The only thing I don't own in /home/gene is .. That's root:root as expected. The correct permissions for your login directory (/home/gene/) are gene:gene, assuming you log in as "gene" and would have been set to that if you created the user "gene" during install. /home should have permissions root:root. I do not know whether that has anything to do with the problems you are having, but correcting it might have some effect and might head off others. With gnome, orca is installed as a dependency. The presumptively correct way to tame it seems to be via the gnome menu item Settings->Accessibility. Mine has every option set to "off" except "Enable Animations," which causes me no grief. If brltty is installed and you don't need it, the proper action is "apt purge brltty," which I have done on occasion. Regards, Tom Dial > > Cheers, Gene Heskett, CET.
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2024-12-14 01:10 +0100 |
| Message-ID | <JTnTj-gNHt-3@gated-at.bofh.it> |
| In reply to | #275672 |
On 12/13/24 18:48, Tom Dial wrote: > > > On 12/13/24 02:48, gene heskett wrote: >> On 12/13/24 03:52, tomas@tuxteam.de wrote: >>> On Fri, Dec 13, 2024 at 01:53:55AM -0500, gene heskett wrote: >>> >>> [...] >>> >>>> That was the system config at the original install, and every one >>>> of the >>>> subsequent installs, nothing I did with the installer prevented it >>>> from >>>> installing orca and brltty. Text only, several variations of >>>> graphical have >>>> been tried. >>> Hm. Difficult to tell, then. >>> >>>> Another clue perhaps: where does t-bird try to save a draft copy of >>>> a msg >>>> while editing it?, its driving me crazy with failed to write a >>>> draft msg >>>> every 5 minutes. >>> I'd venture the strong guess that this is a totally unrelated rabbit >>> hole. In our trade, there are several of them, as you quite certainly >>> know. >>> >>> Cheers >> Wherever it try's, t-b seemto be interpreting the lag as a possible >> perms denial. I did an ls -lR on the directory in home where I put >> the unpacked .xz, and I own every byte of it. The only thing I don't >> own in /home/gene is .. That's root:root as expected. > > The correct permissions for your login directory (/home/gene/) are > gene:gene, assuming you log in as "gene" and would have been set to > that if you created the user "gene" during install. > > /home should have permissions root:root. That is the case. > > I do not know whether that has anything to do with the problems you > are having, but correcting it might have some effect and might head > off others. > > With gnome, orca is installed as a dependency. The presumptively > correct way to tame it seems to be via the gnome menu item > Settings->Accessibility. Mine has every option set to "off" except > "Enable Animations," which causes me no grief. > > If brltty is installed and you don't need it, the proper action is > "apt purge brltty," which I have done on occasion. > > Regards, > Tom Dial > >> >> Cheers, Gene Heskett, CET. > > . Cheers, Gene Heskett, CET. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2024-12-14 01:10 +0100 |
| Message-ID | <JTnTj-gNHt-5@gated-at.bofh.it> |
| In reply to | #275672 |
On 12/13/24 18:23, Tom Dial wrote: > > > On 12/13/24 02:48, gene heskett wrote: >> On 12/13/24 03:52, tomas@tuxteam.de wrote: >>> On Fri, Dec 13, 2024 at 01:53:55AM -0500, gene heskett wrote: >>> >>> [...] >>> >>>> That was the system config at the original install, and every one >>>> of the >>>> subsequent installs, nothing I did with the installer prevented it >>>> from >>>> installing orca and brltty. Text only, several variations of >>>> graphical have >>>> been tried. >>> Hm. Difficult to tell, then. >>> >>>> Another clue perhaps: where does t-bird try to save a draft copy of >>>> a msg >>>> while editing it?, its driving me crazy with failed to write a >>>> draft msg >>>> every 5 minutes. >>> I'd venture the strong guess that this is a totally unrelated rabbit >>> hole. In our trade, there are several of them, as you quite certainly >>> know. >>> >>> Cheers >> Wherever it try's, t-b seemto be interpreting the lag as a possible >> perms denial. I did an ls -lR on the directory in home where I put >> the unpacked .xz, and I own every byte of it. The only thing I don't >> own in /home/gene is .. That's root:root as expected. > > The correct permissions for your login directory (/home/gene/) are > gene:gene, assuming you log in as "gene" and would have been set to > that if you created the user "gene" during install. > > /home should have permissions root:root. > > I do not know whether that has anything to do with the problems you > are having, but correcting it might have some effect and might head > off others. > > With gnome, orca is installed as a dependency. The presumptively > correct way to tame it seems to be via the gnome menu item > Settings->Accessibility. Mine has every option set to "off" except > "Enable Animations," which causes me no grief. My menu has no Accessibility bar under settings. > > If brltty is installed and you don't need it, the proper action is > "apt purge brltty," which I have done on occasion. I've done that to both orca and brltty, the dependency's seem to have been removed now. No change though. > > Regards, > Tom Dial > >> >> Cheers, Gene Heskett, CET. > > . Cheers, Gene Heskett, CET. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis
[toc] | [prev] | [next] | [standalone]
| From | Max Nikulin <manikulin@gmail.com> |
|---|---|
| Date | 2024-12-14 04:30 +0100 |
| Message-ID | <JTr0S-gRpp-5@gated-at.bofh.it> |
| In reply to | #275674 |
On 14/12/2024 07:04, gene heskett wrote:
> I've done that to both orca and brltty, the dependency's seem to have
> been removed now.
What is output of the following command?
dpkg -l orca brltty
Does
dpkg -V
reports anything besides conffiles? Fighting with orca you could remove
files that belong to other packages.
[toc] | [prev] | [next] | [standalone]
Page 2 of 7 — ← Prev page 1 [2] 3 4 5 6 7 Next page →
Back to top | Article view | linux.debian.user
csiph-web