Re: Fedora17-LXDE / Fedora18-LXDE / Language
On Mon, 11 Feb 2013 11:11:15 +0100 Andreas Assmann wrote: After installing Fedora17-LXDE - be it on a hard disk or a USB-stick - I can easily change the language (e.g. from American English to German) by clicking on Start Administration Language. Obviously, this possibility does not exist any more in Fedora18-LXDE. In any case I cannot find it. Or has it been forgotten? I can't imagine that. Please give me a hint. Thanks in advance for your answer. Do you have system-config-language installed? Martin signature.asc Description: PGP signature -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Fedora17-LXDE / Fedora18-LXDE / Language
On Mon, 11 Feb 2013 17:27:31 +0100 Andreas Assmann wrote: Well, I'm an absolute beginnerin Linux. Where should I see system-config-language: in the start-menu oder in YUM? Thanks for your help. Andrew rpm -q system-config-language (from terminal) should tell you if it's installed. If not su -c 'yum install system-config-language' will install it. When you have it installed try finding it in the menu, under XFCE it's Administration-Language, in LXDE it should be something similar. If it's installed and not in menu, it's a probably a bug somewhere. Martin PS: Looks like this is more of a general support question and would be better to be discussed in fedora-list http://www.redhat.com/mailman/listinfo/fedora-list signature.asc Description: PGP signature -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
[SOLVED] Re: Yum Upgrade -- A couple of issues
Yes, the .xsession-errors (quoted under the message) was it. I feel stupid now. I looked into running services and indeed polkit and upower had failed state. # yum reinstall polkit\* upower # reboot fixed the issue completely. Sorry for the spam. I hope at least that this helps someone, should they encounter the same problem. Thanks, Martin On Thu, 17 Jan 2013 12:44:03 +0100 Martin Sourada wrote: I suspect all these issues have one cause, but I'm not sure what exactly goes wrong. Some probably relevant lines from .xsession-errors: Error creating proxy: Error calling StartServiceByName for org.gtk.Private.UDisks2VolumeMonitor: Timeout was reached (g-io-error-quark, 24) (xfdesktop:1172): GVFS-RemoteVolumeMonitor-WARNING **: remote volume monitor with dbus name org.gtk.Private.UDisks2VolumeMonitor is not supported (polkit-gnome-authentication-agent-1:1241): polkit-gnome-1-WARNING **: Error getting authority: Error initializing authority: Error calling StartServiceByName for org.freedesktop.PolicyKit1: GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Activation of org.freedesktop.PolicyKit1 timed out (xfce4-session:1163): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory. This indicates a bug in someone's code. You must ensure an error is NULL before it's set. The overwriting error message was: Unable to read response from sudo helper: Unknown error xfce4-session: Querying CanRestart failed, Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. (xfce4-session:1163): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory. This indicates a bug in someone's code. You must ensure an error is NULL before it's set. The overwriting error message was: Unable to read response from sudo helper: Unknown error xfce4-session: Querying CanShutdown failed. Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. xfce4-session: Querying suspend failed: Message did not receive a reply (timeout by message bus) DBusException: org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus) Unable to mount card (Error code: 1) ERROR:dbus.proxies:Introspect error on :1.217:/org/freedesktop/UDisks: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. signature.asc Description: PGP signature -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Yum Upgrade -- A couple of issues
Hi all, I upgraded F17 - F18 using the fedora-upgrade method. It had one issue: stopped after doing the upgrade, so I had to do the rest of the steps (rebuild rpmdb, update services, groupupdate minimal installation, etc) by hand, maybe it timed out as I ran the upgrade over night. But so far so good, the real issue comes after reboot: Login related functions terribly slow for no apparent reason. Looks like they're waiting for something until timing out (no HDD nor CPU is being used during the process). Affected are DM start-up (I tried lightdm, kdm), DE start-up (XFCE), XFCE log-out dialog start-up, cannot shut-down, reboot, sleep, hibernate. (Well reboot as root from CLI works...) Pointers to what might be wrong (configuration issue or bug?) welcome. Martin signature.asc Description: PGP signature -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Yum Upgrade -- A couple of issues
On Wed, 16 Jan 2013 11:33:09 + Frank Murphy wrote: On Wed, 16 Jan 2013 12:27:28 +0100 Martin Sourada martin.sour...@gmail.com wrote: Hi all, I upgraded F17 - F18 using the fedora-upgrade method. Do yuo mean you did a yum-upgrade as per Subject, or fedup-cli (fedora-upgrade method) The FedoraUpgrade [1] one, neither direct yum-upgrade nor fedup-cli. Martin [1] https://fedoraproject.org/wiki/Features/FedoraUpgrade signature.asc Description: PGP signature -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Does spinfinity work for anybody
Hi Ian, On Fri, 13 May 2011 00:35:22 -0500 Ian Pilcher wrote: snip Anyone have spinfinity working? Yep. I use spinfinity, I updated earlier today (I'm on F15) and rebooted about half an hour before writing this e-mail. Without issues. plymouth*-0.8.4-0.20110510.2.fc15.i686 systemd*-26-1.fc15.i686 Martin signature.asc Description: PGP signature -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: After most recent update
On Tue, 22 Mar 2011 06:36:15 -0600 Lawrence E Graves wrote: I had the same problems. No background. Everthing works ok just no background. What versions of the following components do you have (if you have them installed)? gnome-desktop3 control-center gsettings-desktop-schemas desktop-backgrounds-gnome I suspect a change in how wallpaper is set between 2.91.91 and 2.91.92 of the first three which however has been propagated only to gsettings-desktop-schemas so far in fedora. Martin signature.asc Description: PGP signature -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F15 ping must run as root?
On Mon, 14 Mar 2011 13:08:17 +0100 Joachim Backes wrote: ls -l /bin/ping -rwxr-xr-x. 1 backes backes 40840 Feb 9 17:00 /bin/ping But chown root.root /bin/ping does not solve the problem, still operation not permitted, even after chmod u+s /bin/ping. There's something weird there indeed. Notice the difference in file-size: $ ls -l /bin/ping -rwxr-xr-x. 1 root root 39344 Feb 9 17:00 /bin/ping $ rpm -q iputils iputils-20101006-7.fc15.i686 FYI, I can ping just fine. With regards, Martin -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
[Rawhide Regression] Intel Seems to Display Lower Colour Depth Than It Should
Hi all, before going off to filling a bug report I thought I'd ask here whether there's a possibility I use some dumb setting instead of it being a driver bug... The issue at hand is that in Rawhide the colours displayed on my integrated screen are displayed differently than on Fedora 14. To be exact, worse. It looks like it uses lower colour depth. I played around with ImageMagick with a screenshot of my desktop and came to a conclusion that the actual displayed depth is ca 6 bits per pixel instead of 8 bits per pixel. So I wonder if I might have messed something up or whether it's a driver bug. From looking into /var/log/Xorg.log it seems the driver is setting 24 bit depth and 32 framebuffer which looks ok to me... xorg-x11-drv-intel-2.14.0-1.fc15.i686 00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03) Anyone seeing similar issue? Thanks, Martin pgpX5JICcdJf6.pgp Description: PGP signature -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
[SOLVED] Re: F14 Branched -- hard freezes
On Tue, 2010-09-21 at 16:02 +0200, Martin Sourada wrote: On Tue, 2010-09-14 at 14:17 +0200, Martin Sourada wrote: On Mon, Sep 13, 2010 at 8:43 AM, Martin Sourada martin.sour...@gmail.com wrote: On Mon, 2010-09-13 at 00:07 +0200, Martin Sourada wrote: On Sun, Sep 12, 2010 at 11:58 PM, Adam Williamson awill...@redhat.com wrote: Check kernel logs and X logs after rebooting, see if there's crash notifications in either. (You'll want to look at /var/log/Xorg.0.log.old rather than Xorg.0.log). What's the gfx card? Thanks, I'll check that out, though I doubt that there'll be anything... I have intel 945. Another interesting thing is, I logged into a different account (which I use to testing/playing around) that currently has gnome-shell (as opposed to composited metacity) and so far after more than an hour no freeze. I'll see if it's still running tomorrow. Ok, that wasn't it. It froze in gnome-shell as well. In the exactly same moment when external USB HDD was waking up (initiated by ls -l on some folder in it). So over night I run full fsck on it. No errors reported, but right now it seems to work (at least I wasn't able to reproduce the freeze in single user mode, I'll see if it appears again in init 5). /var/log/Xorg.0.log* and /var/log/messages show no traces about the freeze. So it appeared again, after several hours of usage (so it's much better than it initially was), this time in gnome-screensaver. The USB drive appeared to be running, so I guess kernel was frozen as well. So, after slowly eliminating possible causes, I came to (uncertain) conclusion that f14 kernel does not like my network card (i.e. unless I missed something, the only time I wasn't able to reproduce this yet is without network cable plugged in). It also seems the freezes have got a lot less frequent (but that might be purely coincidental). Kernel: kernel-2.6.35.4-28.fc14.i686 Network card: 06:01.0 Ethernet controller: Broadcom Corporation BCM4401-B0 100Base-TX (rev 02) Just FYI that I finally updated to a kernel that does not seem to suffer from this (which is sadly in koji only): $ uname -r 2.6.35.6-36.fc14.i686.PAE $ uptime 22:11:38 up 3 days, 4:19, 10 users, load average: 1.40, 1.67, 1.80 Not sure if PAE could play any role in this -- I installed the PAE version just for the heck of it (I don't have that much of memory to be actually in need of the PAE)... Martin signature.asc Description: This is a digitally signed message part -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F14 Branched -- hard freezes
On Tue, 2010-09-14 at 14:17 +0200, Martin Sourada wrote: On Mon, Sep 13, 2010 at 8:43 AM, Martin Sourada martin.sour...@gmail.com wrote: On Mon, 2010-09-13 at 00:07 +0200, Martin Sourada wrote: On Sun, Sep 12, 2010 at 11:58 PM, Adam Williamson awill...@redhat.com wrote: Check kernel logs and X logs after rebooting, see if there's crash notifications in either. (You'll want to look at /var/log/Xorg.0.log.old rather than Xorg.0.log). What's the gfx card? Thanks, I'll check that out, though I doubt that there'll be anything... I have intel 945. Another interesting thing is, I logged into a different account (which I use to testing/playing around) that currently has gnome-shell (as opposed to composited metacity) and so far after more than an hour no freeze. I'll see if it's still running tomorrow. Ok, that wasn't it. It froze in gnome-shell as well. In the exactly same moment when external USB HDD was waking up (initiated by ls -l on some folder in it). So over night I run full fsck on it. No errors reported, but right now it seems to work (at least I wasn't able to reproduce the freeze in single user mode, I'll see if it appears again in init 5). /var/log/Xorg.0.log* and /var/log/messages show no traces about the freeze. So it appeared again, after several hours of usage (so it's much better than it initially was), this time in gnome-screensaver. The USB drive appeared to be running, so I guess kernel was frozen as well. So, after slowly eliminating possible causes, I came to (uncertain) conclusion that f14 kernel does not like my network card (i.e. unless I missed something, the only time I wasn't able to reproduce this yet is without network cable plugged in). It also seems the freezes have got a lot less frequent (but that might be purely coincidental). Kernel: kernel-2.6.35.4-28.fc14.i686 Network card: 06:01.0 Ethernet controller: Broadcom Corporation BCM4401-B0 100Base-TX (rev 02) Martin signature.asc Description: This is a digitally signed message part -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F14 Branched -- hard freezes
On Mon, 2010-09-13 at 00:07 +0200, Martin Sourada wrote: On Sun, Sep 12, 2010 at 11:58 PM, Adam Williamson awill...@redhat.com wrote: Check kernel logs and X logs after rebooting, see if there's crash notifications in either. (You'll want to look at /var/log/Xorg.0.log.old rather than Xorg.0.log). What's the gfx card? Thanks, I'll check that out, though I doubt that there'll be anything... I have intel 945. Another interesting thing is, I logged into a different account (which I use to testing/playing around) that currently has gnome-shell (as opposed to composited metacity) and so far after more than an hour no freeze. I'll see if it's still running tomorrow. Ok, that wasn't it. It froze in gnome-shell as well. In the exactly same moment when external USB HDD was waking up (initiated by ls -l on some folder in it). So over night I run full fsck on it. No errors reported, but right now it seems to work (at least I wasn't able to reproduce the freeze in single user mode, I'll see if it appears again in init 5). /var/log/Xorg.0.log* and /var/log/messages show no traces about the freeze. Martin -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
F14 Branched -- hard freezes
Hi all, I've been encountering a strange issue I have no idea how to handle -- my laptop hard freezes about an half an hour after boot, irrespective of what am I doing (first I was doing something in midori, second I was listening to some song in rhythmbox, third I wasn't even present). Screen freezes, one cannot ping the machine, sound, if any is playing at the time of freeze, plays an infinite loop. Strange thing is, when I was home it didn't froze for 3 straight days. It does not freeze on F12 either. The only difference is that at the place where it freezes I also have external USB HDD, USB keyboard and USB wireless mouse connected and use wired connection instead of wireless. Anyone one having similar issues? Any idea how to debug this? How to produce some usable info in order to fill a bug? Thanks, Martin signature.asc Description: This is a digitally signed message part -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F14 Branched -- hard freezes
On Sun, Sep 12, 2010 at 11:58 PM, Adam Williamson awill...@redhat.comwrote: Check kernel logs and X logs after rebooting, see if there's crash notifications in either. (You'll want to look at /var/log/Xorg.0.log.old rather than Xorg.0.log). What's the gfx card? Thanks, I'll check that out, though I doubt that there'll be anything... I have intel 945. Another interesting thing is, I logged into a different account (which I use to testing/playing around) that currently has gnome-shell (as opposed to composited metacity) and so far after more than an hour no freeze. I'll see if it's still running tomorrow. Martin -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: dbus failure w/ NetworkManager-0.8.1-4git20100817 (x86_64)
On Thu, 2010-08-19 at 13:33 -0700, Steven I Usdansky wrote: Running updated F14-branched w/ LXDE x86_64 desktop. Updated NetworkManager to 0.8.1-4git20100817, but network connection failed upon reboot. Tried calling up nm-applet manually and got the following error (taken from /var/log/messages) Aug 19 14:55:48 Pyrope kernel: init[1]: D-Bus activation failed for NetworkManager-by-dbus.service: Invalid argument Reverting to NetworkManager-0.8.1-1.fc14.x86_64 gets me a working NetworkManager again For me a simple # service NetworkManager restart was enough to get it working again. So there might be some connection to systemd... Martin signature.asc Description: This is a digitally signed message part -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Need updated desktop-backgrounds-compat
On Wed, 2010-08-04 at 11:04 -0700, Steven I Usdansky wrote: ~$ rpm -e --test goddard-backgrounds-single error: Failed dependencies: goddard-backgrounds-single is needed by (installed) desktop-backgrounds-compat-9.0.0-14.noarch ~$ rpm -e --test goddard-backgrounds-single desktop-backgrounds-compat error: Failed dependencies: desktop-backgrounds-compat is needed by (installed) lxdm-0.2.0-4.fc14.x86_64 desktop-backgrounds-compat is needed by (installed) lxde-common-0.5.4-2.fc14.noarch ~$ rpm -q --requires desktop-backgrounds-compat goddard-backgrounds-single Hey, can you try out: http://admin.fedoraproject.org/updates/desktop-backgrounds-9.0.0-15.fc14 Martin signature.asc Description: This is a digitally signed message part -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: GTK 2/3 conflict with gedit and rhythmbox
On Tue, 2010-08-10 at 09:38 -0400, Matthias Clasen wrote: On Tue, 2010-08-10 at 15:32 +0200, Sébastien Wilmet wrote: Hello, gedit and rhythmbox crash on my F-14 x86_64 system: $ gedit Gtk-ERROR **: GTK+ 2.x symbols detected. Using GTK+ 2.x and GTK+ 3 in the same process is not supported aborting... Trace/breakpoint trap (core dumped) $ rhythmbox Gtk-ERROR **: GTK+ 3 symbols detected. Using GTK+ 2.x and GTK+ 3 in the same process is not supported aborting... Trace/breakpoint trap (core dumped) These will get sorted out soon. With the alpha freeze, it has been difficult to get the necessary rebuilds done. Having half of the desktop apps not start *at all* otherwise could perhaps warrant an exception? Or you could perhaps chain-build it (if there's too many deps that need update first) and submit for updates-testing in the meantime. Martin signature.asc Description: This is a digitally signed message part -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Need updated desktop-backgrounds-compat
Hi, On Thu, 2010-08-05 at 19:00 -0400, Ray Strode wrote: Hi, Yes, I know. I've sent a mail to desktop-backgrounds maintainers several days ago notifying them about the move to laughlin-backgrounds, but as usual, no reply. I'm CC-ing Christoph who made all the fixes in past (although he is not maintainer of this package). FWIW, I did the necessary changes for gnome-desktop, libgnome, and gnome-desktop3 in reply to your mail. Thanks :) Chris, can you please update the desktop-backgrounds[-compat] package again? The maintainers seems still unresponsive :-( It needs to change the symlinks basically from goddard to laughlin and change requires from goddard-backgrounds-single to laughlin-backgrounds-single (note that I have still pending commit access to this package). Didn't you ask Chris to do this in your original mail? I thought you said this was an xfce thing? I asked only the maintainers of the desktop-backgrounds package in the original mail, which apparently lead nowhere, so after other people complained, I pinged Chris, who did the change last time (even though he isn't a maintainer of that package), about that. As far as commit access goes, I'm sure davidz would approve you if you pinged him on irc. Ah, thanks for the suggestion, I'll try it :) --Ray Martin signature.asc Description: This is a digitally signed message part -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Need updated desktop-backgrounds-compat
On Thu, 2010-08-05 at 00:45 +0200, Christoph Wickert wrote: Am Donnerstag, den 05.08.2010, 00:17 +0200 schrieb Martin Sourada: On Wed, 2010-08-04 at 23:39 +0200, Christoph Wickert wrote: Am Mittwoch, den 04.08.2010, 22:20 +0200 schrieb Martin Sourada: Chris, can you please update the desktop-backgrounds[-compat] package again? Sure Martin, are there any other changes required? I recall reading something on Planet Fedora about including more wallpapers this time. The extra wallpapers will be included post-alpha, so at this point there is no other change. Ok, I have built the package now. However I noticed that the laughlin-backgrounds package is empty and only it's subpackages contain data. Is that intended or can we just drop the base package? Yes, that's intended. You need only laughlin-backgrounds-single for the d-b-compat. The laughlin-backgrounds package just pulls both -gnome and -kde subpackages. Regards, Martin signature.asc Description: This is a digitally signed message part -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
