Re: f24: touchpad "Tap to click" & C. configuration

[Alan Gagne]

Into Fedora 24 "Mouse & Touchpad" panel are missing "Tap to 
click", "Two finger scroll", "Natural scrolling"


On my laptop I have been using the X11 synaptics driver till Fedora24. 
You can get get some info on yours
but tailing the journal log (sudo journalctl -f). When I used the gnome 
control panel to change touchpad settings,
I also had no touchpad setting available. But messages in the journal 
directed me to use libinput rather than synaptics drivers.


I just removed the synaptics drivers and restarted. Touchpad settings 
are now visible in the gnome control panel for mouse and TP.

[dnf remove xorg-x11-drv-synaptics] YMMV

Alan
--
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

F19 raid 1 stuck read only after reboot

[Alan Gagne]

Having an odd problem with my raid 1 array after upgrade to F19.
Upgraded using fedup from 18 to 19. Did not have any problems
with the upgrade itself but since my raid 1 array is stuck read only after
each reboot.

This is a bios intel raid set-up I have been using for a little over 
three years.

So I know it has been quite stable.

The os is installed on the raid 0 array. I use the raid 1 for things I would
rather not lose.

I have to re-write out the partition table using fdisk after each reboot
to get the array to go active.

https://bugzilla.redhat.com/show_bug.cgi?id=985638

 cat /etc/mdadm.conf
# mdadm.conf
MAILADDR root
AUTO +imsm +1.x -all
ARRAY /dev/md/imsm1 metadata=imsm UUID=c740a986:078365cb:f43671d1:e459c34b
ARRAY /dev/md/imsm0 metadata=imsm UUID=a28154cd:08577e7a:8ef68be8:34e15a4b
ARRAY /dev/md/Volume2 container=/dev/md/imsm1 member=0 
UUID=f9dc1dab:feebb78c:b196dcc5:6d6ba98d
ARRAY /dev/md/Volume1_0 container=/dev/md/imsm0 member=0 
UUID=79b75950:70d29fd6:e69a64d6:89b23747



# cat /proc/mdstat
Personalities : [raid0] [raid1]
md124 : active raid1 sdb[1] sdc[0]
  293032960 blocks super external:/md125/0 [2/2] [UU]

md125 : inactive sdb[1](S) sdc[0](S)
  6184 blocks super external:imsm

md126 : active raid0 sdd[1] sde[0]
  156296192 blocks super external:/md127/0 128k chunks

md127 : inactive sde[1](S) sdd[0](S)
  5032 blocks super external:imsm

# fdisk -l /dev/md124

Disk /dev/md124: 300.1 GB, 300065751040 bytes, 586065920 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk label type: dos
Disk identifier: 0x000de834

  Device Boot  Start End  Blocks   Id  System
/dev/md124p12048   419432447   2097152007 HPFS/NTFS/exFAT
/dev/md124p2   419432448   503318527419430407 HPFS/NTFS/exFAT
/dev/md124p3   503318528   58606591941373696   8e  Linux LVM

# fdisk -l /dev/md126

Disk /dev/md126: 160.0 GB, 160047300608 bytes, 312592384 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 131072 bytes / 262144 bytes
Disk label type: dos
Disk identifier: 0x3198d489

  Device Boot  Start End  Blocks   Id  System
/dev/md126p1   *2048   156297215781475847 HPFS/NTFS/exFAT
/dev/md126p2   156297216   157321215  512000   83  Linux
/dev/md126p3   157321216   31259238377635584   8e  Linux LVM


-- 
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: F19 raid 1 stuck read only after reboot

[Alan Gagne]

On Jul 18 11:45, Alan Gagne wrote:
>/  Having an odd problem with my raid 1 array after upgrade to F19.
/>/  Upgraded using fedup from 18 to 19. Did not have any problems
/>/  with the upgrade itself but since my raid 1 array is stuck read only after
/>/  each reboot.
/>/  
/>/  This is a bios intel raid set-up I have been using for a little over

/>/  three years.
/>/  So I know it has been quite stable.
/>/  
/>/  The os is installed on the raid 0 array. I use the raid 1 for things I would

/>/  rather not lose.
/>/  
/>/  I have to re-write out the partition table using fdisk after each reboot

/>/  to get the array to go active.
/
Is that the journal option problem, maybe?  See the last three entries
fromhttp://forums.fedoraforum.org/archive/index.php/t-287286.html

I encountered the same problem when upgrading one of my machines from
F18 to F19.  No idea why it worked before.


Thanks for the information. Unfortunately it is not the same issue.

Alan
-- 
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: F19 raid 1 stuck read only after reboot

[Alan Gagne]

>/  # cat /proc/mdstat
/>/  Personalities : [raid0] [raid1]
/>/  md124 : active raid1 sdb[1] sdc[0]
/>/293032960 blocks super external:/md125/0 [2/2] [UU]
/>/
/>/  md125 : inactive sdb[1](S) sdc[0](S)
/>/6184 blocks super external:imsm
/>/
/>/  md126 : active raid0 sdd[1] sde[0]
/>/156296192 blocks super external:/md127/0 128k chunks
/>/
/>/  md127 : inactive sde[1](S) sdd[0](S)
/>/5032 blocks super external:imsm
/
Super something on external devices which are inactive?

They are all internal drives. That is the normal good state
for the arrays. After a reboot md124 would show auto-read-only
instead of active. When in that state I cannot mount the filesystem.


I think I would try to make it so that the mdtools figure out what the
arrays consist of automatically.  IIRC it is not necessary, maybe not
even advisable, to specify explicitly in mdadm.conf what the arrays are
made of because there is information stored on the disks that allow to
build them automatically.

The mdadm.conf was built when F18 was installed.
Running mdadm --detail --scan returns the same info as what is in the
conf file. I checked that already to make sure there was not any 
differences.


Is md124 a RAID-1 on top of a RAID-0?

Two separate arrays.

Thanks
Alan
-- 
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: F19 raid 1 stuck read only after reboot

[Alan Gagne]

>>/  >/  # cat /proc/mdstat
/>>/  />/  Personalities : [raid0] [raid1]
/>>/  />/  md124 : active raid1 sdb[1] sdc[0]
/>>/  />/293032960 blocks super external:/md125/0 [2/2] [UU]
/>>/  />/
/>>/  />/  md125 : inactive sdb[1](S) sdc[0](S)
/>>/  />/6184 blocks super external:imsm
/>>/  />/
/>>/  />/  md126 : active raid0 sdd[1] sde[0]
/>>/  />/156296192 blocks super external:/md127/0 128k chunks
/>>/  />/
/>>/  />/  md127 : inactive sde[1](S) sdd[0](S)
/>>/  />/5032 blocks super external:imsm
/>>/  /
/>>/  Super something on external devices which are inactive?
/>/  They are all internal drives. That is the normal good state
/>/  for the arrays. After a reboot md124 would show auto-read-only
/>/  instead of active. When in that state I cannot mount the filesystem.
/
You mean the whole array md124 goes read-only?

Yes, the entire array.

Or are the partitions on
it mounted ro?

Unable to mount any partitions when the array is in auto-read-ony state.

  Why do you need to rewrite the partition tables?
Well that the jist of this post. F19 fails to detect something needed 
for the array
to work properly. Rewriting the partition table just gets things working 
again.


How do you know when any of the physical disks go bad?

Hopefully smart will pick-up id there is a disk problem.
So far it reports no errors for either disk member of the array.

Thanks
Alan
-- 
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: F19 raid 1 stuck read only after reboot

[Alan Gagne]

>>/  >>/  >/  # cat /proc/mdstat
/>>/  />>/  />/  Personalities : [raid0] [raid1]
/>>/  />>/  />/  md124 : active raid1 sdb[1] sdc[0]
/>>/  />>/  />/293032960 blocks super external:/md125/0 [2/2] [UU]
/>>/  />>/  />/
/>>/  />>/  />/  md125 : inactive sdb[1](S) sdc[0](S)
/>>/  />>/  />/6184 blocks super external:imsm
/>>/  />>/  />/
/>>/  />>/  />/  md126 : active raid0 sdd[1] sde[0]
/>>/  />>/  />/156296192 blocks super external:/md127/0 128k chunks
/>>/  />>/  />/
/>>/  />>/  />/  md127 : inactive sde[1](S) sdd[0](S)
/>>/  />>/  />/5032 blocks super external:imsm
/>>/  />>/  /
/>>/  />>/  Super something on external devices which are inactive?
/>>/  />/  They are all internal drives. That is the normal good state
/>>/  />/  for the arrays. After a reboot md124 would show auto-read-only
/>>/  />/  instead of active. When in that state I cannot mount the filesystem.
/>>/  /
/>>/  You mean the whole array md124 goes read-only?
/>/  Yes, the entire array.
/>>/  Or are the partitions on
/>>/  it mounted ro?
/>/  Unable to mount any partitions when the array is in auto-read-ony state.
/
That's what I'd expect because when you mount them, changes would be
made, even if only the mount counter is updated.  I'm not sure if that
counter is updated when you mount a partition read only --- you could
try to do that.

Have to try that next tine I reboot.


>>/Why do you need to rewrite the partition tables?
/>/  Well that the jist of this post. F19 fails to detect something needed
/>/  for the array
/>/  to work properly. Rewriting the partition table just gets things
/>/  working again.
/
IIUC, rewriting the partition tables in your case means that you are
writing to the RAID volumes created by the on-board fakeraid while
software RAID is using them.  Besides that I won't do such a thing, it
seems as if this somehow makes these volumes writeable and then somehow
the software reconfigures itself and the software raid becomes writable.

Perhaps there is some sort of timing problem.  You could look at the
services files that are involved with bringing up the RAID and see if
you can add or change waiting times.

>>/  How do you know when any of the physical disks go bad?
/>/  Hopefully smart will pick-up id there is a disk problem.
/>/  So far it reports no errors for either disk member of the array.
/
"SMART is not a reliable warning system for impending failure

Maybe not, but when I had one of these drives going bad about a year ago.
It did a great job of warning that I had an impending drive failure.
The relocated sector count would jump in small blocks over time.

The intel storage manager I use under Windows currently does not
have any warnings about the drives.

The bios screen that displays array health when the system comes up
shows both arrays as healthy.

Smart,Intel and the bios  were all in agreement when I had a failing 
disk in the past.



detection."[1]

I wouldn't rely on SMART to decide whether a disk has failed or not.  A
disk either works correctly or it doesn't (letting connection problems
aside).  When it doesn't, just replace it.  SMART is rather irrelevant
for that.

You seem to be using these disks for a couple years, and it is possible
that there is some failure.  It may be a coincidence that a failure is
discovered after you performed the upgrade, and it is also possible that
there already was a failure before you upgraded which is now detected
and simply wasn't detected before.

Do you see any messages in /var/log/messages that could be relevant?
Since you're using the on-board fakeraid, I'm not sure what you would
see and if you'd see anything at all.  Maybe the BIOS tells you or has
an option to test the disks for failures.

These are the only messages that seem relevant from journalctl -xb

Jul 19 07:35:26 knucklehead..com kernel: device-mapper: table: 
253:4: linear: dm-linear: Device lookup failed
Jul 19 07:35:26 knucklehead..com kernel: device-mapper: ioctl: error 
adding target to table




Do you have good backups?

Yes 



[1]:http://www.tomshardware.com/reviews/ssd-reliability-failure-rate,2923-9.html


Alan

-- 
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: F19 raid 1 stuck read only after reboot

[Alan Gagne]

>>/  "SMART is not a reliable warning system for impending failure
/>/  Maybe not, but when I had one of these drives going bad about a year ago.
/>/  It did a great job of warning that I had an impending drive failure.
/>/  The relocated sector count would jump in small blocks over time.
/
Interesting, did you get a warning message?


Yes, Root got an email on the first occurrence and then after each re-boot.
Also there was something in logwatch email.

  I had to remove udisksd2
because it kept polling SMART information from a disk that should be
asleep and not kept awake all the time.  I was wondering what the SMART
information is polled for.

>/  The intel storage manager I use under Windows currently does not
/>/  have any warnings about the drives.
/>/
/>/  The bios screen that displays array health when the system comes up
/>/  shows both arrays as healthy.
/>/
/>/  Smart,Intel and the bios  were all in agreement when I had a failing
/>/  disk in the past.
/
Then I guess we can assume that the disks have not failed.

>>/  Do you see any messages in /var/log/messages that could be relevant?
/>/  These are the only messages that seem relevant from journalctl -xb
/>/
/>/  Jul 19 07:35:26 knucklehead..com kernel: device-mapper: table:
/>/  253:4: linear: dm-linear: Device lookup failed
/>/  Jul 19 07:35:26 knucklehead..com kernel: device-mapper: ioctl:
/>/  error adding target to table
/
It seems likely that this is what causes your problem.  When you google
for the error message, there are a lot of reports about it.  You could
look into them and try to figure out how to solve the issue --- someone
said old meta information caused it, someone else said removing a
package that provides dmraid fixed it for them ...
Yea, I have been looking at those. I was hoping that between here and 
filing a bug

I would get the best answer.

Thanks
Alan
-- 
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: F19 raid 1 stuck read only after reboot

[Alan Gagne]

>>/  />/  Jul 19 07:35:26 knucklehead..com kernel: device-mapper: table:
/>>/  />/  253:4: linear: dm-linear: Device lookup failed
/>>/  />/  Jul 19 07:35:26 knucklehead..com kernel: device-mapper: ioctl:
/>>/  />/  error adding target to table
/>>/  /
/>>/  It seems likely that this is what causes your problem.  When you google
/>>/  for the error message, there are a lot of reports about it.  You could
/>>/  look into them and try to figure out how to solve the issue --- someone
/>>/  said old meta information caused it, someone else said removing a
/>>/  package that provides dmraid fixed it for them ...
/>/  Yea, I have been looking at those. I was hoping that between here and
/>/  filing a bug
/>/  I would get the best answer.
/
The dmraid package seems to be installed by default.  I'd try to remove
it.

Tried it. No Joy !
Back to Google .

Thanks
Alan
-- 
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: F19 raid 1 stuck read only after reboot

[Alan Gagne]

Alan Gagne https://admin.fedoraproject.org/mailman/listinfo/users>> writes:

>>/  >>/  />/  Jul 19 07:35:26 knucklehead..com kernel: device-mapper: 
table:
/>>/  />>/  />/  253:4: linear: dm-linear: Device lookup failed
/>>/  />>/  />/  Jul 19 07:35:26 knucklehead..com kernel: device-mapper: 
ioctl:
/>>/  />>/  />/  error adding target to table
/>>/  />>/  /
/>>/  />>/  It seems likely that this is what causes your problem.  When you 
google
/>>/  />>/  for the error message, there are a lot of reports about it.  You 
could
/>>/  />>/  look into them and try to figure out how to solve the issue --- 
someone
/>>/  />>/  said old meta information caused it, someone else said removing a
/>>/  />>/  package that provides dmraid fixed it for them ...
/>>/  />/  Yea, I have been looking at those. I was hoping that between here and
/>>/  />/  filing a bug
/>>/  />/  I would get the best answer.
/>>/  /
/>>/  The dmraid package seems to be installed by default.  I'd try to remove
/>>/  it.
/>/  Tried it. No Joy !
/>/  Back to Google .
/
At this point, I'd make a bug report on the mdadm or the kernel package
about it if there isn't one yet.

I opened a bug report before posting to the list.
https://bugzilla.redhat.com/show_bug.cgi?id=985638


  Other than that, besides google, I'd
try to find whatever configuration files there might be involved in
getting the RAID up and try to see if there is something that could be
adjusted.


find /etc -type f -print0 | xargs -0 grep device-mapper
/etc/lvm/lvm.conf


I get lvm.conf and a couple of selinux files (selinux is disabled).




Do you still get the same error message?

Yes, same error messages with dmraid removed.

Thanks
Alan
-- 
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: VirtualBox wont run -

[Alan Gagne]

On 30/07/13 12:41, Steven Stern wrote:
>/  If you're using the repo from virtualbox.org*, type
/>/
/>/  sudo /sbin/service vboxdrv setup
/>/
/>/  It will use DKMS to remove the virtual box drivers, recompile them for
/>/  the new kernel, and install them into the active kernel modules.
/>/
/>/  * This may apply to the Fedora repos but I'm not sure. I'm using the one
/>/  from virtualbox.org.Seehttps://www.virtualbox.org/wiki/Linux_Downloads  
https://www.virtualbox.org/wiki/Linux_Downloads>
/>/  and scroll down to RPM-based Linux distributions
/>/
/>/
/
This is a yum install but I will look into that.

Bob



If you have DKMS installed it will automatically update the modules when 
a new kernel

in installed. Works great for me.

From the doc referenced above.

*Note:*Users of Fedora/Mandriva might want to install the*dkms*package 
(not available on openSUSE) to ensure that the VirtualBox host kernel 
modules (/vboxdrv/,/vboxnetflt/and/vboxnetadp/) are properly updated if 
the linux kernel version changes during the next kernel update.


Alan
-- 
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: VirtualBox wont run -

[Alan Gagne]

[root at box10    
bobg]# ll /etc/sysconfig/modules/VirtualBox.modules
ls: cannot access /etc/sysconfig/modules/VirtualBox.modules: No such
file or directory

The directory contains only one file, nothing for virtualbox.

[root at box10    
bobg]# ll /etc/sysconfig/modules/
total 4
-rwxr-xr-x. 1 root root 96 Jul 23 11:36 bluez-uinput.modules

So it will just have to wait for the updates to come through.

Bob


VirtualBox in not dependent on kernel version at install time.
The modules are built for whatever kernel you are currently running.

You might try to yum remove VirtualBox and then yum install.
Since you have dkms installed. It should register the modules with dkms so
with future kernel updates the modules will get compiled.

Currently the VirtualBox version is the same from either 
rpmfusion-free-updates or virtualbox repos.


[root@knucklehead ~]# yum info Virtual*
Loaded plugins: langpacks, refresh-packagekit
Installed Packages
Name: VirtualBox-4.2
Arch: x86_64
Version : 4.2.16_86992_fedora18
Release : 1
Size: 143 M
Repo: installed
From repo   : virtualbox
Summary : Oracle VM VirtualBox
URL : http://www.virtualbox.org/
License : GPLv2
Description : VirtualBox is a powerful PC virtualization solution allowing
: you to run a wide range of PC operating systems on your Linux
: system. This includes Windows, Linux, FreeBSD, DOS, OpenBSD
: and others. VirtualBox comes with a broad feature set and
: excellent performance, making it the premier virtualization
: software solution on the market.

Available Packages
Name: VirtualBox
Arch: x86_64
Version : 4.2.16
Release : 1.fc19
Size: 26 M
Repo: rpmfusion-free-updates/19/x86_64
Summary : A general-purpose full virtualizer for PC hardware
URL : http://www.virtualbox.org/wiki/VirtualBox
License : GPLv2 or (GPLv2 and CDDL)
Description : A general-purpose full virtualizer and emulator for 32-bit and
: 64-bit x86 based PC-compatible machines.

Alan
-- 
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: VirtualBox wont run -

[Alan Gagne]

Am 31.07.2013 16:45, schrieb Bob Goodwin ~ Zuni:
>/  I awoke around 03:00 and tried whatever new suggestions had come in at that 
time as well as rebooting, all to no
/>/  avail.
/>/  
/>/  However, systemctl setup  vboxdrv.service still does not run:
/>/  
/>/  [root at box10    bobg]# /sbin/service vboxdrv setup

/>/  Redirecting to /bin/systemctl setup  vboxdrv.service
/>/  Unknown operation 'setup'.
/>/  
/>/  Thanks to all for the help. That help is invaluable to many of us and is what keeps people coming back to Fedora!

/
/etc/init.d/vboxdrv setup

you *must not* use systemctl or service which is a wrapper for systemctl
the times where a service can have whatever actions are gone with systemd

Not entirely true with regards to using service. This is on my F19 box.
[root@dw-agagne ~]# uname -r
3.10.3-300.fc19.x86_64


[dw-agagne ~]# service vboxdrv
Usage: /etc/init.d/vboxdrv 
{start|stop|stop_vms|restart|force-reload|status|setup}

[dw-agagne ~]# service vboxdrv setup
Stopping VirtualBox kernel modules [  OK  ]
Uninstalling old VirtualBox DKMS kernel modulesError! There are no 
instances of module: vboxhost

4.2.16 located in the DKMS tree.
Error! There are no instances of module: vboxhost
4.2.16 located in the DKMS tree.
   [  OK  ]
Trying to register the VirtualBox kernel modules using DKMS[  OK  ]
Starting VirtualBox kernel modules [  OK  ]

[dw-agagne ~]# service vboxdrv status
VirtualBox kernel modules (vboxdrv, vboxnetflt, vboxnetadp, vboxpci) are 
loaded.


Where Bob has a problem with vboxdrv is that it does not exist.
It appears he has gotten virtualbox from the rpmfusion repo.

vboxdrv comes with what is packaged from the virtualbox.org repo.

[dw-agagne ~]# yum repolist
Loaded plugins: langpacks, refresh-packagekit
repo id  repo 
name status
adobe-linux-i386 Adobe Systems 
Incorporated17
adobe-linux-x86_64   Adobe Systems 
Incorporated 2
fedora/19/x86_64 Fedora 19 - 
x86_6436,253

google-chrome google-chrome  3
rpmfusion-free/19/x86_64 RPM Fusion for Fedora 19 - 
Free  462
rpmfusion-free-updates/19/x86_64 RPM Fusion for Fedora 19 - Free 
- Updates 96
rpmfusion-nonfree/19/x86_64  RPM Fusion for Fedora 19 - 
Nonfree   219
rpmfusion-nonfree-updates/19/x86_64  RPM Fusion for Fedora 19 - 
Nonfree - Updates  90
updates/19/x86_64Fedora 19 - x86_64 - 
Updates   9,730

virtualbox/19/x86_64

[dw-agagne ~]# yum provides "*/vboxdrv"

VirtualBox-4.2-4.2.8_83876_fedora18-1.x86_64 : Oracle VM VirtualBox
Repo: virtualbox
Matched from:
Filename: /etc/rc.d/init.d/vboxdrv
Filename: /usr/share/virtualbox/src/vboxhost/vboxdrv


Alan
-- 
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: Turning off SELINUX

[Alan Gagne]

As for the tinfoil hat, it needs two layers --- the inside layer needs
to be orientend shiny-side in, which would prevent the NSA from spying
on your brain waves. But the outside layer needs to be oriented
shiny-side out, to prevent the NSA from feeding your brain with
undesired signals. The two layers need to be well insulated against
each other --- it's obvious that a short-circuit between them will
leave you completely vulnerable...


I prefer kevlar in the insulated layer. Also my hat is more of a full 
helmet.

Like to make it slightly more difficult in the event they decide my
process needs to be terminated.

:-)

Alan
-- 
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: Fedora 18 - from minimal to desktop system

[Alan Gagne]

Is it possible to first do minimal Fedora 18 installation and then using
one or two commands (yum ??) install every package that is included in
GNOME desktop installation done by Anaconda? Maybe it's more question
about the name of meta-package that will pull all needed dependencies. I
can't find the right package name.


Try yum grouplist to see the packaged groups.
I think you want to install GNOME Desktop.

Alan
-- 
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: Transferring files to/from Android phone

[Alan Gagne]

This topic has been discussed several times before. With the recent
update to KDE 4.10.1, Fedora (KDE) seems to be able to do this:
Now, from Dolphin I can browse my phone as an "MTP-device", the internal
memory as well as the SD-card.


Works as well on Gnome Desktop.

Alan
-- 
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:presto

[Alan Gagne]

starting fc18 presto-plugin has disappeared
I would like to get yum out of this mode.
Can't find a conf switch or trick to do that in man or google.
Is this another choice removed from "Linux,the world of choice"?
Or can I get a hint from here?


Try install presto yum plugin.

yum install yum-presto

[dw-agagne ~]# yum info yum-pesto
Loaded plugins: langpacks, presto, refresh-packagekit
Error: No matching Packages to list
[root@dw-agagne ~]# yum info yum-presto
Loaded plugins: langpacks, presto, refresh-packagekit
Installed Packages
Name: yum-presto
Arch: noarch
Version : 0.9.0
Release : 1.fc18
Size: 66 k
Repo: installed
From repo   : fedora
Summary : Presto plugin for yum
URL : http://www.lesbg.com/jdieter/presto/
License : GPLv2+
Description : Yum-presto is a plugin for yum that looks for deltarpms 
rather than rpms
: whenever they are available.  This has the potential of 
saving a lot of

: bandwidth when downloading updates.
:
: A Deltarpm is the difference between two rpms.  If you 
already have foo-1.0
: installed and foo-1.1 is available, yum-presto will 
download the deltarpm
: for foo-1.0 => 1.1 rather than the full foo-1.1 rpm, and 
then build the full
: foo-1.1 package from your installed foo-1.0 and the 
downloaded deltarpm.


Alan
-- 
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:presto

[Alan Gagne]

NoGo : yum-presto has been obsoleted.


Don't know what to tell you.
I have two F18 boxes that are both using the presto plugin for yum.

Linux dw-agagne 3.8.5-201.fc18.x86_64 #1 SMP Thu Mar 28 21:01:19 UTC 
2013 x86_64 x86_64 x86_64 GNU/Linux


Alan
-- 
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:getting back from a black screen

[Alan Gagne]

On 04/08/2013 12:31 PM, Reindl Harald wrote:
>/
/>/  [harry at srv-rhsoft  
:~]$ lspci | grep -i 
graphic
/
AHA!  Two ways to do it.  How Unix!


And let's add a twist to find out your drivers.

[dw-agagne ~]# lspci | grep VGA
01:00.0 VGA compatible controller: NVIDIA Corporation Device 1251 (rev a1)

then using the bus:slot.func returned from previous command.

dw-agagne ~]# lspci -s 01:00.0 -k
01:00.0 VGA compatible controller: NVIDIA Corporation Device 1251 (rev a1)
Subsystem: ASUSTeK Computer Inc. Device 204a
Kernel driver in use: nouveau

Alan

-- 
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:Disability relief

[Alan Gagne]

I do always set that, yes, as soon as I find it, and it does
help; but I have yet to find it in Gnome 3 or xfce4. Anybody know where
it lurks?


I have not read this entire thread so maybe I am too late to the game.
If you are still looking at how to turn on the bulls-eye around the 
mouse pointer

in gnome 3 it comes with gnome tweak tool.

Alan
-- 
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:Disability relief

[Alan Gagne]

>/   I do always set that, yes, as soon as I find it, and it does
/>/  help; but I have yet to find it in Gnome 3 or xfce4. Anybody know where
/>/  it lurks?
/
I have not read this entire thread so maybe I am too late to the game.
If you are still looking at how to turn on the bulls-eye around the
mouse pointer
in gnome 3 it comes with gnome tweak tool.

Alternatively just use gsettings to turn on in gnome.

check current setting:
gsettings get org.gnome.settings-daemon.peripherals.mouse locate-pointer

Turn on locate-pointer:
gsettings set org.gnome.settings-daemon.peripherals.mouse locate-pointer 
true


Alan
-- 
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: F17 losing settings

[Alan Gagne]

Where/How do I tell Fedora (Gnome 3) once and for all to show
hidden files? Unless I command otherwise, I always want to see them; but
the file manager seems to ignore the fact that I have that option checked.


[agagne@dw-agagne ~]$ gsettings set org.gnome.nautilus.preferences 
show-hidden-files true
[agagne@dw-agagne ~]$ gsettings get org.gnome.nautilus.preferences 
show-hidden-files

true

Alan
-- 
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:Fedora 18

[Alan Gagne]

I think my Fedora 18 uses nautilus for file management, but it may be
nemo, I've never taken any notice.

I'm wondering if I can set a default somewhere so that when opening ruby
.rb and .erb  rails files in my Rails development directory it will
default to using Geany instead of GEdit.
Is there somewhere to set these default please
I have looked in .config/geany  /nautilus  /nemo  and .local with no luck.



Try right click on the file you want to open with geany in nautilus.
Go to properties then open with tab. Add your preferred app as the default.

Alan
--
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: fedup upgrade to 18 broke my touchpad on DELL Vostro

[Alan Gagne]

I still haven't managed to get my touchpad workin although my USB mouse is
working fine.

One thing I don't have with the mouse that I did have with the touchpad was
pressing both buttons to emulate the middle button and getting a "paste"
action.

My mouse does actually have a middle button (a pressable scroll wheel) but
pressing this doesn't give me the effect I want either.

Any suggestions?



Check what you have set currently.

gsettings get org.gnome.settings-daemon.peripherals.mouse 
middle-button-enabled


If this returns false then you can turn this on.

gsettings set org.gnome.settings-daemon.peripherals.mouse 
middle-button-enabled true


Alan

-- 
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: fedup upgrade to 18 broke my touchpad on DELL Vostro

[Alan Gagne]

>/  Check what you have set currently.
/>/
/>/  gsettings get org.gnome.settings-daemon.peripherals.mouse
/>/  middle-button-enabled
/>/
/>/  If this returns false then you can turn this on.
/>/
/>/  gsettings set org.gnome.settings-daemon.peripherals.mouse
/>/  middle-button-enabled true
/>/
/>/  Alan
/
Thanks for this Alan, do you know what the KDE equiv of this?
Sorry for the dumb question but I've already googled for things like this.

Also, I've run the Scientific Linux Live DVD and my touchpad works fine. It's
a drastic solution swapping distributions, but so far I haven't found an
alternative


Try to use xinput for both mouse and touchpad.

 xinput list
# xinput list_props "$device_name_or_number"
xinput list-props 10
Turn on three button emulation.
xinput set-prop 10 "Evdev Middle Button Emulation" 1


Alan
-- 
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: fedup upgrade to 18 broke my touchpad on DELL Vostro

[Alan Gagne]

On Tuesday 18 June 2013 16:18:14 Alan Gagne wrote:
>/  Try to use xinput for both mouse and touchpad.
/>/
/>/xinput list
/>/  # xinput list_props "$device_name_or_number"
/>/  xinput list-props 10
/>/  Turn on three button emulation.
/>/  xinput set-prop 10 "Evdev Middle Button Emulation" 1
/>/
/>/
/>/  Alan
/
The problem with the touchpad is that it's seen as a PS/2 device which from
Google is an old problem that seems to have re-appeared.

I've run

"xinput set-prop 14 "Evdev Middle Button Emulation" 1

and it's got the Left+Right mouse button click to work on my USB mouse.

How do I go about making this permenant?


I haven't used KDE for quite a long time so YMMV.

Create a script with the xinput set command and make it executable.
Test to make sure it works.
Then Goto System Settings > Startup and Shutdown > Autostart, then click 
Add Program, enter:

your script.

Alan
-- 
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