Re: OT: RGB mechanical keyboard
Some keyboard reviews, from across the pond: https://www.theregister.com/2020/04/30/how_good_are_cheap_mechanical_keyboards/ ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: What was that?
> However, neither the keyboard or mouse were functioning.
> I unplugged the wireless dongles for both of them and
> plugged them back in, and now the mouse works, but the
> keyboard still doesn't work.
I've been seeing stuff like this in the syslog from recent kernels:
Sep 30 08:59:34 dorotea kernel: usb 1-3: new full-speed USB device
number 3 using xhci_hcd
Sep 30 08:59:34 dorotea kernel: usb 1-3: New USB device found,
idVendor=046d, idProduct=c52b, bcdDevice=12.09
Sep 30 08:59:34 dorotea kernel: usb 1-3: New USB device strings:
Mfr=1, Product=2, SerialNumber=0
Sep 30 08:59:34 dorotea kernel: usb 1-3: Product: USB Receiver
Sep 30 08:59:34 dorotea kernel: usb 1-3: Manufacturer: Logitech
Sep 30 08:59:34 dorotea kernel: input: Logitech USB Receiver as
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/0003:046D:C52B.0001/input/input18
Sep 30 08:59:34 dorotea kernel: hid-generic 0003:046D:C52B.0001:
input,hidraw0: USB HID v1.11 Keyboard [Logitech USB Receiver] on
usb-:00:14.0-3/input0
Sep 30 08:59:34 dorotea kernel: input: Logitech USB Receiver Mouse as
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.1/0003:046D:C52B.0002/input/input19
Sep 30 08:59:34 dorotea kernel: input: Logitech USB Receiver Consumer
Control as
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.1/0003:046D:C52B.0002/input/input20
Sep 30 08:59:34 dorotea kernel: input: Logitech USB Receiver System
Control as
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.1/0003:046D:C52B.0002/input/input21
Sep 30 08:59:34 dorotea kernel: hid-generic 0003:046D:C52B.0002:
input,hiddev96,hidraw1: USB HID v1.11 Mouse [Logitech USB Receiver] on
usb-:00:14.0-3/input1
Sep 30 08:59:34 dorotea kernel: hid-generic 0003:046D:C52B.0003:
hiddev97,hidraw2: USB HID v1.11 Device [Logitech USB Receiver] on
usb-:00:14.0-3/input2
Sep 30 08:59:34 dorotea kernel: usb 1-3: USB disconnect, device number 3
Sep 30 08:59:34 dorotea mtp-probe[1544]: checking bus 1, device 3:
"/sys/devices/pci:00/:00:14.0/usb1/1-3"
Sep 30 08:59:39 dorotea kernel: usb 1-3: new full-speed USB device
number 4 using xhci_hcd
Sep 30 08:59:39 dorotea kernel: usb 1-3: New USB device found,
idVendor=046d, idProduct=c52b, bcdDevice=12.09
Sep 30 08:59:39 dorotea kernel: usb 1-3: New USB device strings:
Mfr=1, Product=2, SerialNumber=0
Sep 30 08:59:39 dorotea kernel: usb 1-3: Product: USB Receiver
Sep 30 08:59:39 dorotea kernel: usb 1-3: Manufacturer: Logitech
The device is recognized, then something called mtp-probe comes along
and blows it out of the water. The cycle repeats until either
mtp-probe gives up and lets the device work, or the device itself
gives up:
Sep 30 09:00:10 dorotea kernel: usb 1-3: Device not responding to setup address.
A workaround (found on the interwebs) is to add a udev rule in, say,
/etc/udev/rules.d/99-mtp-no-probe.rules:
ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c52b", ENV{MTP_NO_PROBE}="1"
Now there are messages like this:
Oct 2 10:18:09 dorotea mtp-probe[973]: checking bus 1, device 3:
"/sys/devices/pci:00/:00:14.0/usb1/1-5"
Oct 2 10:18:09 dorotea mtp-probe[973]: bus: 1, device: 3 was not an MTP device
But so far nothing bad has happened.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: Network dies on laptop lid closure
My (F24) laptop's lid behavior, configured in the MATE control center, is to blank the display and leave everything else alone. The machine can overheat with the display running and the lid closed. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: post-mortem: f24 boot fails; need help.
Some years ago I had an IBM ThinkPad that one day failed to boot, and every subsystem diagnostic that ran at power-up (keyboard, memory, disk controller, ...) reported a problem. On a whim I put in a new clock battery and everything was fine. Now any time a machine suddenly goes flakey, the clock battery is the first thing that gets replaced. On Fri, May 26, 2017 at 21:22:17 +0930,Tim wrote: > On Thu, 2017-05-25 at 12:47 -0700, Rick Stevens wrote: > > Otherwise, with a weak battery the BIOS will usually revert to default > > settings which are generally considered conservative and "safe". > > I'm not so sure that's the case. In many PCs, the BIOS clock, BIOS > memory, and perhaps other BIOS hardware, are powered solely by the > battery (even when the computer is running off mains power). So, with > failing power you could have all manner of random things happen. > ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: Odd behaviour for GREP
Sorry, should be "directory is searchable bur not readable". On Mon, Oct 3, 2016 at 9:48 AM, Tom Killian wrote: > People, >> >> On F25 x86_64 as user "fedora" with default environment I get: >> >> grep Cock application.html.erb >> >>Provider for the National Disability Insurance Trial Site in Kwinana/ >> Cockburn >> >> grep Cock * >> >>grep: *: No such file or directory > > > This behaviour generally means that the file is in a directory that is > readable but not searchable. But root does not have that restriction and > can expand the pattern. > ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: Odd behaviour for GREP
> > People, > > On F25 x86_64 as user "fedora" with default environment I get: > > grep Cock application.html.erb > >Provider for the National Disability Insurance Trial Site in Kwinana/ > Cockburn > > grep Cock * > >grep: *: No such file or directory This behaviour generally means that the file is in a directory that is readable but not searchable. But root does not have that restriction and can expand the pattern. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: looking for a BASH tool
Once upon a time, SternData said: > Years ago, I used a tool called CED and PCED on DOS systems. I could > type in "abc" and press an up-arrow and it would walk back through my > stack of DOS commands showing only those with "abc" in them. > > There's *got* to be a similar tool for bash, but my google-fu is weak today. In addition to keyboard shortcuts... history | grep abc | less If what you're looking for came from a different, now closed, terminal window, try grep $HISTFILE abc | less -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: keyboard with a numeric keypad which does not work in Fedora
> > It's an Apple keyboard, maybe six years old but I don't ever recall > seeing an Apple keyboard with numlock because there was never such a > thing as navigation by keypad on Macs. Maybe run xev and see what keystrokes it's actually sending. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: http://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Photo app's -
> On Mon, 2016-04-11 at 12:09 -0400, Bob Goodwin wrote: > > On 04/11/16 11:48, Patrick O'Callaghan > > wrote: > > > > > > On Mon, 2016-04-11 at 11:43 -0400, Bob Goodwin wrote: > > > > > > > > I just installed simple-mtpfs and gat > > > > the following: > > > > > > > > [root@Box10 bobg]# simple-mtpfs -l > > > > No raw devices found. > > > Try turning it off and on again (seriously :-) > > > > > > poc > > . > > > > Tried that along with reinserting the > > usb cable several times, all to no avail. > > > > A bit of googling provides: > > > > "unfortunately, Nikon S3100 doesn't have > > RAW file support." > > That's related to the kind of images the camera produces (i.e. they are > compressed, probably with JPEG, and without the option of turning off > the compression). It has nothing to do with the connection issue as > such. > > > Anyway this has been interesting and I > > thank you for the helpful suggestions. > > Sorry it didn't work out. > > poc You can probably read the media directly with an SDcard-to-USB adapter. Some laptops even have an SDcard slot built in. Tom -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: http://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: MATE on dual screen, put a panel on secondary screen?
> Date: Fri, 6 Mar 2015 19:06:42 -0500 > From: Fred Smith > To: users@lists.fedoraproject.org > Subject: > Message-ID: <20150307000642.ga25...@fcshome.stoneham.ma.us> > Content-Type: text/plain; charset=us-ascii > > hi all! > > Experimenting with dual screens on F20 using MATE. Video card is Nvidia 9800GT > using Nvidia drivers from rpmfusion: > > kmod-nvidia.x86_64 1:331.113-1.fc20.5 @rpmfusion-nonfree-updates > > So, I've got it configured, using the nvidia X-Server Settings tool and it > works nicely sofar. > > But I'd kinda like trying it with a set of panels on the second screen much > like (if not identical to) those on the main screen. > > But so far I've not figured out how to add a panel to the second screen. > The context menu (right-click on a panel) for "new panel" offers no options, > it just sticks it on the first screen. I can't drag it, it just seems to > want to sit there. > > Can someone advise me if thereis a way to do what I want? some arcane > incantation on the commandline, perhaps? > > thanks! > -- > Fred Smith -- fre...@fcshome.stoneham.ma.us - > "And he will be called Wonderful Counselor, Mighty God, Everlasting Father, > Prince of Peace. Of the increase of his government there will be no end. He > will reign on David's throne and over his kingdom, establishing and upholding > it with justice and righteousness from that time on and forever." > --- Isaiah 9:7 (niv) -- The (non-intuitive) solution is to make a new panel on the first screen, then use alt-click to drag it to the second screen where you can set its orientation and content to taste. If someone knows how to script this, that would be nice. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: fedup - the good and the bad
On Tue, 9 Jul 2013 20:46:58 +0200, wrote: >> What I want to know is, what does fedup do if, as in my case, Gnome isn't >> installed? > > Don't know that. Sorry. > Frédéric I fedup'd (18->19) a system with only mate installed and it worked perfectly. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Check your /etc/default/grub, if you use raid 1.
On Sun, Jul 29, 2012 at 10:02 AM, Sam Varshavchik wrote: > To: For users of Fedora Core releases > Subject: Check your /etc/default/grub, if you use raid 1. > Message-ID: > Content-Type: text/plain; charset="utf-8"; Format="flowed"; > DelSp="yes" > > There's a long standing combination of two bugs: the list of rd.md.uuid boot > parameters generated by anaconda for /etc/default/grub may not include the > raid uuid of non-stock partitions like /home; and although the ramfs > initscript autodiscovers all raid volumes present, sometimes (not always, > I'll estimate 5% of the time) if a uuid is not enumerated in the boot > parameters, one of the drives in the raid 1 volume may not get assembled at > boot. > > There's probably a third bug in here: mdmonitor should've mailed me when an > array came up degraded at boot (I suspect that because mdmonitor gets > started so early in the boot process, not all the moving pieces are there > for mail delivery to happen). Eventually, you'll boot again with both drives > in the array somehow, except they'll be out of sync, resulting in massive > corruption. If you're lucky, you'll boot just with the other drive, and > discover that your filesystem's contents are weeks/months out of date, and > maybe you'll be lucky enough to figure out what happen, and switch back to > the other drive and resync. But, not everyone's so lucky. > > This first started happening in F16. It took me a while to figure out the > cause for an occasionally raid assembly failure at boot. Fixed it, and > forgot about it. Well, looks like the F17 anaconda brought back the broken > /etc/default/grub, which found its way into my grub.cfg, and I just lost a > full day, cleaning up this mess. > > So, if you use raid 1 and upgraded to F17, you may need to fix this before > it's too late: put back the missing uuid into /etc/default/grub, and into > every entry in grub.cfg > > Pissed. Thanks for the explanation and fix/workaround, Sam. This happened to me as well. I ran fsck on the two mirrors independently and was able to recover most of the data from the lost+found's. But I had been brooding over the root cause until now. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Random kernel update breakage
On Tue, 24 Aug 2010 22:29:54 -0400 Sam Varshavchik wrote: > >Every once in a while, something breaks when a kernel update gets installed. >It doesn't happen every time, I'd say that once in every thirty or so kernel >updates, grub fails to come up after a subsequent reboot. > >This is just a minor annoyance -- I'd have to boot the install CD in rescue >mode, let it mount Fedora on /mnt/sysimage, chroot to it, and execute >/sbin/grub-install -- but I'm wondering if anyone else is seeing this. I have seen this quite often following the first kernel update after a Fedora version update. I.e., the machine boots fine after the version update, but needs re-grubbing after 'yum update'. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: What's up with bash shell and spaces in filenames?
>[a...@agena ~]$ cd /media/My* >bash: cd: /media/My: No such file or directory this suggests that there may be a space at the *beginning* of the filename. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: chainloader +1, again
>Snipped from that shell: >device (hd0,0) /dev/sdb >grub> root (hd0,1) >root (hd0,1) > Filesystem type unknown, partition type 0x82 >grub> setup (hd0,1) >setup (hd0,1) i think you're close. 'device' refers to the whole drive, and grub counts partitions from 0 (partition type 0x82 is a swap partition, /dev/sdb2). so you probably want: device (hd0) /dev/sdb root (hd0,0) setup (hd0) # write mbr of device, not partition! on the other hand, if you got here via 'chainloader' from /dev/sda, the bios (and therefore grub) likely thinks that /dev/sdb is drive 1, so that 'hd1' may be what you need instead of 'hd0'. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
