Re: System hang under F16
by Jackson Byers
> I have no idea if it is related, but twice with F16
> I've had Gnome completely lock up.
> The mouse pointer would move,
> but otherwise the screen was completely unresponsive,
> not even any of the keyboard hot
> keys would work (Alt-F*, ctrl-alt-del, etc).
FWIW, I am seeing exactly same response on F14
complete lock up, pointer moves.
I was not able to ssh in from my wife's iMac (normally, I can)
this version of F14 was from a fresh install, hardisk install from the iso.
I have another version of F14 (preupgrade from F12) which I am using now,
that is not experiencing this lock up
Jack
12 years, 6 months
Gnome Shell periodically locks up hard in F16
by Deron Meranda
Since upgrading to Fedora 16, I have experienced several periodic hard
lock-ups of the Gnome Shell session. I never experienced such
behaviour in F15. I am wondering if anybody else is seeing something
similar or may have advice, or can suggest a better way for me to
gather useful debugging information should it happen again.
I'm running with this version (including shell extensions):
gnome-shell-3.2.1-2.fc16.x86_64
gnome-shell-extension-apps-menu-3.2.0-1.fc16.noarch
gnome-shell-extension-common-3.2.0-1.fc16.noarch
gnome-shell-extension-drive-menu-3.2.0-1.fc16.noarch
gnome-shell-extension-mediaplayers-0-0.1.git259f96e.fc16.noarch
gnome-shell-extension-places-menu-3.2.0-1.fc16.noarch
gnome-shell-extension-systemMonitor-3.2.0-1.fc16.noarch
Often these lock-ups occur when I'm opening or closing windows in
quick succession. However the last lock-up happened as I flung the
pointer into the upper-left corner to bring up the Gnome Shell
activities bar. Gnome hung almost instantly, and the screen output was
frozen-in-time just as the little animated circular "ripple" that
happens when you hit an edge got about 15-to-20 pixels away from the
corner position.
The general symptoms are that all user interaction with the display
ceases to work. The mouse pointer will still move, but nothing can be
clicked on. Keyboard entry completely stops working too; which
includes any of the hot keys such as the "windows" keys, alt-F?,
ctl-alt-backspace, etc. I think running applications may still able to
draw to the screen, as I saw firefox refresh some icons while it was
in a locked up state. But Gnome itself appears quite dead.
The operating system as a whole though is still working. I can login
using ssh from another machine, and kill off the hung user's gnome
session processes. Afterwards I log in again to a new session and
everything works fine.
I didn't see anything in my syslog, except at the point when I killed
the session processes, such as...
Nov 18 23:53:03 beryl pulseaudio[2563]: module-gconf.c: Unable to read
or parse data from client.
Nov 18 23:53:03 beryl gnome-session[2509]: WARNING: Detected that
screensaver has left the bus
Nov 18 23:53:03 beryl gnome-session[2509]: GConf-WARNING: Got
Disconnected from DBus.#012
Nov 18 23:53:03 beryl gnome-session[2509]: WARNING: Application
'gnome-settings-daemon.desktop' killed by signal
Nov 18 23:53:03 beryl gnome-session[2509]: WARNING: Application
'gnome-shell.desktop' killed by signal
Nov 18 23:53:33 beryl systemd-logind[1256]: Removed session 2.
Nov 18 23:53:35 beryl systemd-logind[1256]: New session 39 of user gdm.
Nov 18 23:53:35 beryl systemd-logind[1256]: Linked /tmp/.X11-unix/X0
to /run/user/gdm/X11/display.
...
The ~/.xsession-errors file is harder to decipher, mainly because it
lacks any timestamps at all and is generally quite cluttered. I am
seeing a ton of errors like:
([object _private_Clutter_Timeline],434)@/usr/share/gnome-shell/js/ui/tweener.js:220
"'
JS ERROR: !!! message = '"global.current_event_time is not a function"'
JS ERROR: !!! Exception was: TypeError:
global.current_event_time is not a function
JS ERROR: !!! lineNumber = '292'
JS ERROR: !!! fileName = '"/usr/share/gnome-shell/js/ui/keyboard.js"'
But I see those even when Gnome is not locked up. I think this may be
an unrelated upstream bug,
http://mail.gnome.org/archives/commits-list/2011-November/msg01202.html
And I also caught an exception in seapplet, which is strange because I
did not see any AVC error show up in syslog. The stack trace follows:
*** glibc detected *** /usr/bin/seapplet: double free or corruption
(out): 0x000000000265d290 ***
======= Backtrace: =========
/lib64/libc.so.6[0x368be7c606]
/lib64/libglib-2.0.so.0(g_free+0x23)[0x368ba4b793]
/usr/lib64/libgtk-x11-2.0.so.0[0x369df6ad19]
/usr/lib64/libgtk-x11-2.0.so.0[0x369dfc62f2]
/lib64/libgobject-2.0.so.0(g_closure_invoke+0x154)[0x368f60ea24]
/lib64/libgobject-2.0.so.0[0x368f620527]
/lib64/libgobject-2.0.so.0(g_signal_emit_valist+0x851)[0x368f62a141]
/lib64/libgobject-2.0.so.0(g_signal_emit+0x82)[0x368f62a2e2]
/lib64/libgobject-2.0.so.0[0x368f611a47]
/lib64/libgobject-2.0.so.0(g_object_notify+0x500)[0x368f613a80]
/usr/lib64/libgtk-x11-2.0.so.0[0x369dfc9723]
/usr/lib64/libgtk-x11-2.0.so.0(gtk_main_do_event+0x3f5)[0x369df4cb05]
/usr/lib64/libgdk-x11-2.0.so.0[0x369ca6209c]
/lib64/libglib-2.0.so.0(g_main_context_dispatch+0x1dd)[0x368ba44a7d]
/lib64/libglib-2.0.so.0[0x368ba45278]
/lib64/libglib-2.0.so.0(g_main_loop_run+0x175)[0x368ba457c5]
/usr/lib64/libgtk-x11-2.0.so.0(gtk_main+0xa7)[0x369df4b9c7]
/usr/bin/seapplet[0x4021c6]
/lib64/libc.so.6(__libc_start_main+0xed)[0x368be2169d]
/usr/bin/seapplet[0x402779]
======= Memory map: ========
....hundreds of lines omitted here...
Otherwise, I don't have much else to report at this point. Any help to
figure this out would be appreciated. Thanks.
--
Deron Meranda
http://deron.meranda.us/
12 years, 6 months
iptables systemd services fail
by Michael Schwendt
Fedora 16 x86_64 plus updates-testing
Some time ago systemd has started with reporting that both the iptables4
and iptables6 services fail at boot time. For example:
| Starting IPv4 firewall with iptables...
| Starting IPv4 firewall with iptables failed, see 'systemctl status iptables.service' for details.
|
# systemctl status iptables.service
#iptables.service - IPv4 firewall with iptables
Loaded: loaded (/lib/systemd/system/iptables.service; enabled)
Active: failed since Thu, 17 Nov 2011 18:19:23 +0100; 2min 31s ago
Process: 1003 ExecStart=/usr/libexec/iptables.init start (code=exited, status=1/FAILURE)
CGroup: name=systemd:/system/iptables.service
Once logged in, I can start it manually without problems. SELinux is not
the culprit. The services fail also when running permissive mode. It seems
as if it's another race between systemd services.
Anyone has seen this, too?
--
Fedora release 16 (Verne) - Linux 3.1.1-2.fc16.x86_64
loadavg: 1.36 0.44 0.15
12 years, 6 months
SystemD Resolved
by Fedora User
After all my kvetching, it turns out that systemd is really pretty easy
to administer. SOME techs have a tendency to write documentation that
is rather esoteric. I think that I likened the 49 man pages for systemd
to Talmudic study.
This could use a graphical application to create the necessary links. I
was lost because of being accustomed to SysV for more than a decade. My
concern is that a new user migrating from windows would be equally
lost. This could also use a SIMPLE guide for end users who would
ordinarily manage just the multi-user and graphical target.wants.
12 years, 6 months
Gnome Shell periodically locks up hard in F16
by Deron Meranda
(Oops, I originally sent this to the wrong list address ... sorry if
anybody sees duplicates)
Since upgrading to Fedora 16, I have experienced several periodic hard
lock-ups of the Gnome Shell session. I never experienced such
behaviour in F15. I am wondering if anybody else is seeing something
similar or may have advice, or can suggest a better way for me to
gather useful debugging information should it happen again.
I'm running with this version (including shell extensions):
gnome-shell-3.2.1-2.fc16.x86_64
gnome-shell-extension-apps-menu-3.2.0-1.fc16.noarch
gnome-shell-extension-common-3.2.0-1.fc16.noarch
gnome-shell-extension-drive-menu-3.2.0-1.fc16.noarch
gnome-shell-extension-mediaplayers-0-0.1.git259f96e.fc16.noarch
gnome-shell-extension-places-menu-3.2.0-1.fc16.noarch
gnome-shell-extension-systemMonitor-3.2.0-1.fc16.noarch
Often these lock-ups occur when I'm opening or closing windows in
quick succession. However the last lock-up happened as I flung the
pointer into the upper-left corner to bring up the Gnome Shell
activities bar. Gnome hung almost instantly, and the screen output was
frozen-in-time just as the little animated circular "ripple" that
happens when you hit an edge got about 15-to-20 pixels away from the
corner position.
The general symptoms are that all user interaction with the display
ceases to work. The mouse pointer will still move, but nothing can be
clicked on. Keyboard entry completely stops working too; which
includes any of the hot keys such as the "windows" keys, alt-F?,
ctl-alt-backspace, etc. I think running applications may still able to
draw to the screen, as I saw firefox refresh some icons while it was
in a locked up state. But Gnome itself appears quite dead.
The operating system as a whole though is still working. I can login
using ssh from another machine, and kill off the hung user's gnome
session processes. Afterwards I log in again to a new session and
everything works fine.
I didn't see anything in my syslog, except at the point when I killed
the session processes, such as...
Nov 18 23:53:03 beryl pulseaudio[2563]: module-gconf.c: Unable to read
or parse data from client.
Nov 18 23:53:03 beryl gnome-session[2509]: WARNING: Detected that
screensaver has left the bus
Nov 18 23:53:03 beryl gnome-session[2509]: GConf-WARNING: Got
Disconnected from DBus.#012
Nov 18 23:53:03 beryl gnome-session[2509]: WARNING: Application
'gnome-settings-daemon.desktop' killed by signal
Nov 18 23:53:03 beryl gnome-session[2509]: WARNING: Application
'gnome-shell.desktop' killed by signal
Nov 18 23:53:33 beryl systemd-logind[1256]: Removed session 2.
Nov 18 23:53:35 beryl systemd-logind[1256]: New session 39 of user gdm.
Nov 18 23:53:35 beryl systemd-logind[1256]: Linked /tmp/.X11-unix/X0
to /run/user/gdm/X11/display.
...
The ~/.xsession-errors file is harder to decipher, mainly because it
lacks any timestamps at all and is generally quite cluttered. I am
seeing a ton of errors like:
([object _private_Clutter_Timeline],434)@/usr/share/gnome-shell/js/ui/tweener.js:220
"'
JS ERROR: !!! message = '"global.current_event_time is not a function"'
JS ERROR: !!! Exception was: TypeError:
global.current_event_time is not a function
JS ERROR: !!! lineNumber = '292'
JS ERROR: !!! fileName = '"/usr/share/gnome-shell/js/ui/keyboard.js"'
But I see those even when Gnome is not locked up. I think this may be
an unrelated upstream bug,
http://mail.gnome.org/archives/commits-list/2011-November/msg01202.html
And I also caught an exception in seapplet, which is strange because I
did not see any AVC error show up in syslog. The stack trace follows:
*** glibc detected *** /usr/bin/seapplet: double free or corruption
(out): 0x000000000265d290 ***
======= Backtrace: =========
/lib64/libc.so.6[0x368be7c606]
/lib64/libglib-2.0.so.0(g_free+0x23)[0x368ba4b793]
/usr/lib64/libgtk-x11-2.0.so.0[0x369df6ad19]
/usr/lib64/libgtk-x11-2.0.so.0[0x369dfc62f2]
/lib64/libgobject-2.0.so.0(g_closure_invoke+0x154)[0x368f60ea24]
/lib64/libgobject-2.0.so.0[0x368f620527]
/lib64/libgobject-2.0.so.0(g_signal_emit_valist+0x851)[0x368f62a141]
/lib64/libgobject-2.0.so.0(g_signal_emit+0x82)[0x368f62a2e2]
/lib64/libgobject-2.0.so.0[0x368f611a47]
/lib64/libgobject-2.0.so.0(g_object_notify+0x500)[0x368f613a80]
/usr/lib64/libgtk-x11-2.0.so.0[0x369dfc9723]
/usr/lib64/libgtk-x11-2.0.so.0(gtk_main_do_event+0x3f5)[0x369df4cb05]
/usr/lib64/libgdk-x11-2.0.so.0[0x369ca6209c]
/lib64/libglib-2.0.so.0(g_main_context_dispatch+0x1dd)[0x368ba44a7d]
/lib64/libglib-2.0.so.0[0x368ba45278]
/lib64/libglib-2.0.so.0(g_main_loop_run+0x175)[0x368ba457c5]
/usr/lib64/libgtk-x11-2.0.so.0(gtk_main+0xa7)[0x369df4b9c7]
/usr/bin/seapplet[0x4021c6]
/lib64/libc.so.6(__libc_start_main+0xed)[0x368be2169d]
/usr/bin/seapplet[0x402779]
======= Memory map: ========
....hundreds of lines omitted here...
Otherwise, I don't have much else to report at this point. Any help to
figure this out would be appreciated. Thanks.
--
Deron Meranda
http://deron.meranda.us/
12 years, 6 months
mozilla-https-everywhere causes Firefox to freeze up regularly
by Andre Robatino
I tried this addon a few weeks ago in F15, uninstalled it after experiencing
frequent Firefox freezeups, then tried again with F16. The same thing still
happens with mozilla-https-everywhere-1.1-1.fc16.noarch. There are currently no
bugs reported against it. Is anyone else seeing this?
12 years, 6 months
build gcc-4.4 on F15/16?
by Neal Becker
I'm trying to install cuda sdk. It needs gcc<=4.4.
I grabbed gcc-4.4.6
gcc fails to link:
gcc -g -fkeep-inline-functions -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-
prototypes -Wmissing-prototypes -Wcast-qual -Wold-style-definition -Wc++-compat
-Wmissing-format-attribute -pedantic -Wno-long-long -Wno-variadic-macros -Wno-
overlength-strings -fno-common -DHAVE_CONFIG_H -o cc1-dummy c-lang.o stub-
objc.o attribs.o c-errors.o c-lex.o c-pragma.o c-decl.o c-typeck.o c-convert.o
c-aux-info.o c-common.o c-opts.o c-format.o c-semantics.o c-ppoutput.o c-
cppbuiltin.o c-objc-common.o c-dump.o c-pch.o c-parser.o i386-c.o c-gimplify.o
tree-mudflap.o c-pretty-print.o c-omp.o dummy-checksum.o main.o tree-browser.o
libbackend.a ../libcpp/libcpp.a ../libdecnumber/libdecnumber.a
../libcpp/libcpp.a ../libiberty/libiberty.a ../libdecnumber/libdecnumber.a -
L/lib -lcloog -lmpfr -lppl -lgmpxx -lgmp
/usr/bin/ld: libbackend.a(graphite.o): undefined reference to symbol
'ppl_finalize'
/usr/bin/ld: note: 'ppl_finalize' is defined in DSO /usr/lib64/libppl_c.so.4 so
try adding it to the linker command line
/usr/lib64/libppl_c.so.4: could not read symbols: Invalid operation
collect2: ld returned 1 exit status
OK, let's add -lppl_c:
[nbecker@nbecker6 gcc]$ gcc -g -fkeep-inline-functions -DIN_GCC -W -Wall -
Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wcast-qual -Wold-style-
definition -Wc++-compat -Wmissing-format-attribute -pedantic -Wno-long-long -
Wno-variadic-macros -Wno-overlength-strings -fno-common -DHAVE_CONFIG_H -o
cc1-dummy c-lang.o stub-objc.o attribs.o c-errors.o c-lex.o c-pragma.o c-decl.o
c-typeck.o c-convert.o c-aux-info.o c-common.o c-opts.o c-format.o c-semantics.o
c-ppoutput.o c-cppbuiltin.o c-objc-common.o c-dump.o c-pch.o c-parser.o i386-c.o
c-gimplify.o tree-mudflap.o c-pretty-print.o c-omp.o dummy-checksum.o main.o
tree-browser.o libbackend.a ../libcpp/libcpp.a ../libdecnumber/libdecnumber.a
../libcpp/libcpp.a ../libiberty/libiberty.a ../libdecnumber/libdecnumber.a -
L/lib -lcloog -lmpfr -lppl_c -lgmpxx -lgmp
/usr/lib/gcc/x86_64-redhat-linux/4.6.1/../../../../lib64/libppl_c.so: undefined
reference to
`std::__detail::_List_node_base::swap(std::__detail::_List_node_base&,
std::__detail::_List_node_base&)@GLIBCXX_3.4.15'
/usr/lib/gcc/x86_64-redhat-linux/4.6.1/../../../../lib64/libppl_c.so: undefined
reference to
`std::__detail::_List_node_base::_M_transfer(std::__detail::_List_node_base*,
std::__detail::_List_node_base*)@GLIBCXX_3.4.15'
/usr/lib/gcc/x86_64-redhat-linux/4.6.1/../../../../lib64/libppl_c.so: undefined
reference to `std::__detail::_List_node_base::_M_unhook()@GLIBCXX_3.4.15'
/usr/lib/gcc/x86_64-redhat-linux/4.6.1/../../../../lib64/libppl_c.so: undefined
reference to
`std::__detail::_List_node_base::_M_hook(std::__detail::_List_node_base*)@GLIBCXX_3.4.15'
/usr/lib/gcc/x86_64-redhat-linux/4.6.1/../../../../lib64/libppl_c.so: undefined
reference to `std::ctype<char>::_M_widen_init() const(a)GLIBCXX_3.4.11'
collect2: ld returned 1 exit status
Now what's that about? glibcxx_3.4.15?
12 years, 6 months
Swap space not enabled at boot in F16
by Deron Meranda
For some reason my swap device is not being enabled (swapon) at boot.
It seems that the new systemd swap.target is not doing its thing as I
would expect.
After booting, I can manually run "systemctl start swap.target" and it
works, with my device then showing up in /proc/swaps.
My swap device is a LUKS-encrypted LVM logical volume, and I don't see
anything wrong with any of its setup or configuration. Nor has
anything changed that I know of since F15.
Since swap.target is a built-in special systemd unit, is there
anything I need to do to make it work at boot?
--
Deron Meranda
http://deron.meranda.us/
12 years, 6 months
[SOLVED] Re: firefox taking foreground
by g
*OOOPPPSSS*
On 11/16/2011 06:24 PM, goodwin wrote:
> On 11/16/2011 09:04 AM, g wrote:
<>
my apoligies.
i used 'nicknames' for my emails.
i use 'fe' for "fedora" and 'ff' for "firefox".
other post to fedora tsl was in error. seems i used 'fe'
instead of 'ff'.
--
peace out.
tc.hago,
g
.
*please reply "plain text" only. "html text" are deleted*
****
in a free world without fences, who needs gates.
**
help microsoft stamp out piracy - give linux to a friend today.
**
to mess up a linux box, you need to work at it.
to mess up an ms windows box, you just need to *look* at it.
**
The installation instructions stated to install Windows 2000 or better.
So I installed Linux.
**
learn linux:
'Rute User's Tutorial and Exposition' http://rute.2038bug.com/index.html
'The Linux Documentation Project' http://www.tldp.org/
'LDP HOWTO-index' http://www.tldp.org/HOWTO/HOWTO-INDEX/index.html
'HowtoForge' http://howtoforge.com/
****
12 years, 6 months