system-config-display crashes (F12)
When I try to run system-config-display as root I get the following Traceback (most recent call last): File "/usr/share/system-config-display/xconf.py", line 378, in dialog = xConfigDialog.XConfigDialog(hardware_state, xconfig, videocard.VideoCardInfo()) File "/usr/share/system-config-display/xConfigDialog.py", line 640, in __init__ if len(self.xconfig.layout[0].adjacencies) > 1: IndexError: index out-of-bounds The background is that this morning when I came to my desktop machine I didn't get a password screen from the screensaver, so I rebooted. It booted fine and I got a login screen and it accepted my login but I didn't get a proper gnome desktop. All I got was a blue background (the standard one) and the possibility to right click -> cŕeate a new folder -> open up the file-browser -> find gnome-terminal and so I could start applications in X but I had no desktop, i.e. no panels or menus and so forth. I thought perhaps installing nvidia drivers from rpm fusion instead would help. That was a non-starter, I didn't even get X. So I erased those packages. At that point I also thought of disconnecting my second monitor that had been blank all morning, and that did the trick of getting back my desktop, but at that point the resolution of my screen had dropped to 800x600 and now I don't seem to have any means to set it back Any advice? Markus -- users mailing list users@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: system-config-display crashes (F12)
Thanks for the input. I managed after much fiddling to get the display back on track. But there is still something strange going on. Each morning now when I get to the computer the left monitor is dead, i.e. it doesn't seem to have a data signal. The only way to bring it back is to power down the computer and physically disconnect and reconnect the dvi cable from the graphics card. After that everything works again until next morning. There isn't anything of interest in /var/log/messages I have a nVidia NV43GL [Quadro FX 550] card. Both monitors connect to this card with dvi I using the nouveau driver Any thoughs? Markus 2010/1/15 Tomas Hajek : > Hi Markus, > I had a similar problem and what I had to do was just mv the > /etc/X11/xorg.conf file out of the way (I think system-config-display > might be failing on trying to parse your exising xorg.conf file.) I had this > problem with my ATI card but it might work for you too. > -Tomas > Müslüm Ejder wrote: >> Hi Markus, >> i had 2 Displays connected on 2 devices >> 1 Nvidia on Board >> 1 Nvidia on AGP >> >> if u have two Videocards you must go into your PC-BIOS and specify the >> Videocard where your Primary Display Connected as your Primary one. >> >> but most people using only 1 Videocard for two Displays. if this is true >> for you then chek if your nvidia driver is installed properly. >> >> to check it open a terminal and : >> lsmod | grep nvidia >> if the output like the following line, the driver is installed and works >> and you dont need to install the driver again. >> nvidia 10311864 26 >> >> if the output is nothing the driver is not installed or not for the >> kernel u have. Then you need to install it with following steps: >> >> Download the latest driver from >> http://www.nvidia.co.uk/Download/index.aspx?lang=en-uk >> change to runlevel 3 - open a terminal and type : >> su -C 'init 3' >> login as root >> yum install gcc kernel-headers (installer needs the headers and gcc >> to auto compile the driver for your kernel) >> now change to folder where u downloaded your nvidia driver is locatet >> Type "sh NVIDIA-Linux-x86_64-169.12.pkg1.run" >> follow the steps from installer to install or reinstall the driver. >> >> Now or when your driver was properly installed you must config your >> screen, for a basic configuration use nvidia-xconfig in terminal as >> root. >> now u can go back into runlevel 5 as root with: >> init 5 >> log in in your desktop and open a terminal >> now type su -C 'nvidia-settings' >> and Configure your Desktop >> when you have multiple displays and use it as one big desktop >> (stretched) you cannot enable desktop effects etc. only when u have >> multiple desktops and displays. >> >> - hope will help you - >> >> Am Donnerstag, den 14.01.2010, 10:02 +0100 schrieb Markus Lindholm: >>> When I try to run system-config-display as root I get the following >>> >>> Traceback (most recent call last): >>> File "/usr/share/system-config-display/xconf.py", line 378, in >>> dialog = xConfigDialog.XConfigDialog(hardware_state, xconfig, >>> videocard.VideoCardInfo()) >>> File "/usr/share/system-config-display/xConfigDialog.py", line 640, >>> in __init__ >>> if len(self.xconfig.layout[0].adjacencies) > 1: >>> IndexError: index out-of-bounds >>> >>> The background is that this morning when I came to my desktop machine >>> I didn't get a password screen from the screensaver, so I rebooted. It >>> booted fine and I got a login screen and it accepted my login but I >>> didn't get a proper gnome desktop. All I got was a blue background >>> (the standard one) and the possibility to right click -> cŕeate a new >>> folder -> open up the file-browser -> find gnome-terminal and so I >>> could start applications in X but I had no desktop, i.e. no panels or >>> menus and so forth. >>> >>> I thought perhaps installing nvidia drivers from rpm fusion instead >>> would help. That was a non-starter, I didn't even get X. So I erased >>> those packages. >>> >>> At that point I also thought of disconnecting my second monitor that >>> had been blank all morning, and that did the trick of getting back my >>> desktop, but at that point the resolution of my screen had dropped to >>> 800x600 and now I don't seem to have any means to s
Re: SELinux RPM scriptlet issue cleanup
I got also hit by this nfs-utils/selinux-policy issue.
Tried to do a yum reinstall \* but it didn't go through. It gave the following
--> Finished Dependency Resolution
Error: Package: 32:bind-libs-9.9.4-8.fc20.i686 (fedora)
Requires: bind-license = 32:9.9.4-8.fc20
Installed: 32:bind-license-9.9.4-11.P2.fc20.noarch (@updates)
bind-license = 32:9.9.4-11.P2.fc20
Available: 32:bind-license-9.9.4-8.fc20.noarch (fedora)
bind-license = 32:9.9.4-8.fc20
You could try using --skip-broken to work around the problem
** Found 5 pre-existing rpmdb problem(s), 'yum check' output follows:
32:bind-9.9.4-8.fc20.x86_64 has missing requires of bind-libs = ('32',
'9.9.4', '8.fc20')
firefox-26.0-5.fc20.x86_64 is a duplicate with firefox-26.0-3.fc20.x86_64
firewalld-0.3.9.2-1.fc20.noarch is a duplicate with
firewalld-0.3.9-1.fc20.noarch
selinux-policy-targeted-3.12.1-116.fc20.noarch has missing requires of
selinux-policy = ('0', '3.12.1', '116.fc20')
yum-3.4.3-130.fc20.noarch is a duplicate with yum-3.4.3-129.fc20.noarch
I then tried with --skip-broken but got
--> Finished Dependency Resolution
Error: Multilib version problems found. This often means that the root
cause is something else and multilib version checking is just
pointing out that there is a problem. Eg.:
1. You have an upgrade for firefox which is missing some
dependency that another package requires. Yum is trying to
solve this by installing an older version of firefox of the
different architecture. If you exclude the bad architecture
yum will tell you what the root cause is (which package
requires what). You can try redoing the upgrade with
--exclude firefox.otherarch ... this should give you an error
message showing the root cause of the problem.
2. You have multiple architectures of firefox installed, but
yum can only see an upgrade for one of those architectures.
If you don't want/need both architectures anymore then you
can remove the one with the missing update and everything
will work.
3. You have duplicate versions of firefox installed already.
You can use "yum check" to get yum show these errors.
...you can also use --setopt=protected_multilib=false to remove
this checking, however this is almost never the correct thing to
do as something else is very likely to go wrong (often causing
much more problems).
Protected multilib versions: firefox-26.0-5.fc20.x86_64 !=
firefox-26.0-3.fc20.x86_64
What to do?
/Markus
On 18 January 2014 05:33, Rahul Sundaram wrote:
> Hi
>
>
> On Fri, Jan 17, 2014 at 11:28 PM, Ian Pilcher wrote:
>>
>> On 01/17/2014 11:46 AM, Suvayu Ali wrote:
>> > You should reinstall all the packages that had a scriptlet failure but
>> > were able to install. I had the same issue, in my case however I was
>> > trying to install a few new packages. So I simply did yum history undo,
>> > and repeated the original command.
>>
>> Not really realistic with a distro-sync, I'm afraid.
>
>
> Depends on how far you are willing to go
>
> sudo yum reinstall \*
>
> Rahul
>
>
>
> --
> 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
>
--
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
Kernel panic during boot - what now?
Hi I've run into a nasty problem with kernel panic during boot. I did a fresh installation of F18 last Wednesday and it was a smooth experience, but then yesterday I did a 'yum update' that ended up causing a kernel panic (there wasn't much more happening on the machine at that time) and after that the boot process always terminates in a kernel panic almost immediately after the password for disc encryption has been given. It gives exit code 0x7F00. I've got two kernel versions to choose from, 3.6.10-4 and 3.7.2.-201, same result with both. What now, how can I repair the system? /Markus -- 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: Kernel panic during boot - what now?
On 22 January 2013 01:22, Sam Varshavchik wrote: > Reindl Harald writes: > >> some years ago you had the possibility to boot from >> install DVD in rescue mode and "chroot /sysimage" >> but these days all this extended options seems to >> go away or perfectly hidden > > > I'm pretty sure that the F18 install image has a boot option for rescue mode > that'll automount everything and give you a shell. > I could always remove the SSD from the crashed system and mount it on a different machine. But any ideas what to do then? Replacing systemd with an earlier version? And what could have been the reason for the kernel panic in the first place? An unfortunate race condition during 'yum update' that I just happened to run into? Some unfortunate combination of services and configuration? /Markus -- 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
Accessing disk from F19 in F21
Hi I just updated a computer from Fedora 19 to 21. I did it by adding a second SSD to the computer on which I installed F21. The problem is now that I can't access the files from the old SSD. They seem to be overshadowed as the volume group has the same name as the new installation. Any way to get access to the old disk in this new setting? /Markus -- 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: Accessing disk from F19 in F21
This is what I see in the log when I attach the disk kernel: sd 7:0:0:0: [sdb] Attached SCSI disk lvm[2859]: device-mapper: create ioctl on fedora-swap failed: Device or resource busy lvm[2859]: device-mapper: create ioctl on fedora-home failed: Device or resource busy lvm[2859]: device-mapper: create ioctl on fedora-root failed: Device or resource busy lvm[2859]: 0 logical volume(s) in volume group "fedora" now active lvm[2859]: fedora: autoactivation failed. kernel: EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null) kernel: SELinux: initialized (dev sdb1, type ext4), uses xattr udisksd[1680]: Mounted /dev/sdb1 at /run/media/mli/e746019e-de05-40e6-9883-daf16e8c929a on behalf of uid 1000 /dev/sdb1 is the old boot partition On 18 December 2014 at 14:47, Markus Lindholm wrote: > Hi > > I just updated a computer from Fedora 19 to 21. I did it by adding a > second SSD to the computer on which I installed F21. The problem is > now that I can't access the files from the old SSD. They seem to be > overshadowed as the volume group has the same name as the new > installation. > > Any way to get access to the old disk in this new setting? > > /Markus -- 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: Accessing disk from F19 in F21
On 18 December 2014 at 15:50, Roger Heflin wrote: > vgrename can rename using a uuid to know who to rename, so rename it > to something that does not conflict. Thanks, vgrename solved the conflict. /Markus -- 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: Accessing disk from F19 in F21
On 18 December 2014 at 18:52, Chris Murphy wrote: > On Thu, Dec 18, 2014 at 6:47 AM, Markus Lindholm > wrote: >> Hi >> >> I just updated a computer from Fedora 19 to 21. I did it by adding a >> second SSD to the computer on which I installed F21. The problem is >> now that I can't access the files from the old SSD. They seem to be >> overshadowed as the volume group has the same name as the new >> installation. > > Odd. The Fedora 21 installer should have avoided using the same VG > name as before. I just tried this with Fedora 20 and 21. Both default > to VG name "fedora" but Fedora 21's installer knows to add numbers if > "fedora" already exists. This is what I end up with: Ah, I physically disconnected the old disk during installation of F21, as it is identical in size with the new one. Just to make sure I wouldn't mix the two during installation. /Markus -- 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
Evolution not working with automatic login?
Hi I have a box with F18 on which I use automatic login and I just noticed that Evolution doesn't work any more. It just hangs. If I logout and back in again, then Evolution comes back to life. And same thing if I switch of automatic login. I have a recollection that previously Evolution asked for keyring password when it was started. Now it doesn't do that any more. Am I the only one with this problem? /Markus -- 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: Evolution not working with automatic login?
On 9 March 2013 19:07, Reindl Harald wrote: > > > Am 09.03.2013 18:58, schrieb Markus Lindholm: >> I have a box with F18 on which I use automatic login and I just >> noticed that Evolution doesn't work any more. It just hangs. If I >> logout and back in again, then Evolution comes back to life. And same >> thing if I switch of automatic login. I have a recollection that >> previously Evolution asked for keyring password when it was started. >> Now it doesn't do that any more. >> >> Am I the only one with this problem? > > most likely because virtually nobody has open his > machine so blindly these days That I would call a less than helpful response. /Markus -- 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
