We're closing this bug since it is has been some time with no response from the
original reporter. However, if the issue still exists please feel free to
reopen with the requested information. Also, if you could, please test against
the latest development version of Ubuntu, since this
Hi TJ, thanks for all the analysis work. Can you test to see if this
issue was still afflicting lucid (and/or maverick). If it is, is libx11
still the right package or should it be filed against a different
package?
** Changed in: libxcb (Ubuntu)
Status: Confirmed = Incomplete
--
two
** Tags added: intrepid
--
two xscreens - gnome panel crashes
https://bugs.launchpad.net/bugs/278261
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I believe I've managed to identify the issue here. It is dependent on my
having correctly navigated the register variable identification. Gdb is
supposed to report which register the variable is stored in using info
address dpy but this reports Symbol dpy is a variable with multiple
locations -
Having just patched glib to fix bug #290935 dual screen all panels end
up on one screen at startup I'm using dual screens again and hit this
bug whilst using compiz cube and nvidia drivers.
Metacity /apps/metacity/general/compositing_manager = false.
Running gnome-panel from within gdb shows
I neglected to install the libgtk ebug symbols for the previous back-
trace. Here's a summary of the key parts that I'm focusing on:
#19 0x7fd66d49a588 in gdk_window_x11_set_cursor (window=0x148f960,
cursor=0x0)
at /build/buildd/gtk+2.0-2.16.1/gdk/x11/gdkwindow-x11.c:2912
#20
Looking at the libx11-dev package source code I see that the 'Display'
value is optimized out into a register variable, which is a pain since
that is likely key to the bug and doesn't show up in gdb output.
libx11/src/DefCursor.c:
int
XDefineCursor (
register Display *dpy,
Window w,
** Changed in: libxcb (Ubuntu)
Status: Incomplete = Confirmed
--
two xscreens - gnome panel crashes
https://bugs.launchpad.net/bugs/278261
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I still experience this problem in Ubuntu Jausty as well as Intrepid.
The Gnome fix didn't help for me, since it still occurs on Jausty with
Gnome 2.26
The program 'gnome-panel' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid
I just experienced this error. If I enable compiz and use the second
screen I get a box with only error when I click on a gnome-panel icon on
my second desktop. If I kill gnome-panel, disable compiz
(effects=none) and try again it still crashes, logging off and on after
disabling compiz my
I tried the fix mentioned by Nico-S (in comment #33), and it works.
Thanks!
--
two xscreens - gnome panel crashes
https://bugs.launchpad.net/bugs/278261
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Same problem, attached xsession-errors
kernel: 2.6.27-4-generic
Ubuntu: Intrepid(8.10)
Gnome: 2.24.1
nvidia-drivers: 180.22
gnome-panel: Panel 2.24.1
** Attachment added: xsession-errors
http://launchpadlibrarian.net/21899983/xsession-errors
--
two xscreens - gnome panel crashes
I also get this:
The program 'gnome-panel' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.
(Details: serial 12030 error_code 8 request_code 1 minor_code 0)
(Note to programmers: normally, X errors are
note: it only occurs when I add a application launcher to the gnome
panel on the 2nd X screen and click/start that launcher. This seems to
happen with any application I try to launch from the gnome-panel
launchers on the 2nd X screen
--
two xscreens - gnome panel crashes
When I start a new gnome-panel myself (on the 2nd X screen) the problem
seems solved.
As reported above, when the gnome-panel crashed, a error popup (without text)
is displayed on the 1st X screen.
When I killall -9 gnome-panel, it restarts by itself, and still crashes with
the reported
I also experience this issue with gnome-panel and 2 X screens, in
combination with nvidia 177 drivers, running Ubuntu Intrepid.
I attached the output of lspci -vvnn
** Attachment added: lspci -vvnn
http://launchpadlibrarian.net/21711003/lspci.txt
--
two xscreens - gnome panel crashes
When doing the above, the problem moves to the 1st X screen. If gnome-
panel is started from the 2nd X screen, using launchers from the 1st X
screen causes the crash. The other way around, if gnome-panel is started
from the 1st X screen, using launchers from the 2nd X screen causes the
crash.
--
Hi,
I resolved the problem on my computer. It was an interaction with
metacity, linked to the /apps/metacity/general/compositing_manager key.
If it is true then some visuals effects are done without compiz, but it
has to be set to false to remove my problems.
The question is : where is the bug ?
another 'weird' behaviour: if I add a application launcher to my desktop
on the 2nd X screen, and I double click that launcher on the 2nd X
screen desktop, the application appears on the 1st X screen.
Only starting applications from the applications menu on the 2nd X
screen seems to work
I don't seem to have that key in my gconf and still experience the issue
--
two xscreens - gnome panel crashes
https://bugs.launchpad.net/bugs/278261
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[This is an automated message]
Hi tdomhan,
Please attach the output of `lspci -vvnn` too.
** Changed in: libxcb (Ubuntu)
Status: New = Incomplete
--
two xscreens - gnome panel crashes
https://bugs.launchpad.net/bugs/278261
You received this bug notification because you are a member
I'm not sure if this will help, but I'm experiencing something eerily
similar. I'm on Hardy using Gnome. I have two screens. I'm working on
a Qt 4.5 app. When I launch the app on the first screen, things at first
seem ok. However, if I move the window (even a couple pixels), then
Gnome tries
By the way, this ONLY happens when I move the main window (derived from
QMainWindow). It does not happen if I move the Open File dialog or
other popup dialog.
--
two xscreens - gnome panel crashes
https://bugs.launchpad.net/bugs/278261
You received this bug notification because you are a member
Please disregard my last two comments. This was a bug on my part.
--
two xscreens - gnome panel crashes
https://bugs.launchpad.net/bugs/278261
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Here is my ~/xsession-errors trace :
(gnome-panel:6538): Gtk-WARNING **: gtk_widget_size_allocate(): attempt
to allocate widget with width -9 and height 24
(gnome-panel:6538): Gdk-WARNING **:
/build/buildd/gtk+2.0-2.14.4/gdk/x11/gdkdrawable-x11.c:878 drawable is not a
pixmap or window
The
kernel: 2.6.27-9-generic
Ubuntu: Intrepid(8.10)
nvidia-drivers: 177.8
Gnome:
gnome-panel: 1:2.24.1-0ubuntu2.1
ProblemType: Bug
Architecture: x86_64 (Intel(R) Core(TM)2 Duo CPU T8300)
DistroRelease: Ubuntu 8.10
NonfreeKernelModules: nvidia
Hi,
First of all, thanks to all ubunutu
I ran into this same problem on 2 machines I updated today.
I also ran into the 177 vs 173 problem. Downgrading to 173 fixed the second
screen desktop.
I run independent screens like most people writing here.
When I use an application launcher in the gnome panel to launch something the
Hi guys I am in the same boat.. running Ibex using nvidia 177 and tried
173 drivers.. any progress been made yet?
--
two xscreens - gnome panel crashes
https://bugs.launchpad.net/bugs/278261
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
As Sebastien said the the crash is one in libxcb, rejecting the gnome-
panel task.
** Changed in: gnome-panel (Ubuntu)
Status: Confirmed = Invalid
--
two xscreens - gnome panel crashes
https://bugs.launchpad.net/bugs/278261
You received this bug notification because you are a member of
** Changed in: gnome-panel (Ubuntu)
Status: New = Confirmed
--
two xscreens - gnome panel crashes
https://bugs.launchpad.net/bugs/278261
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Your latest comment indicate that it hangs could you lease try to obtain
a backtrace of the hang http://wiki.ubuntu.com/DebuggingProgramCrash and
attach the file to the bug report. This will greatly help us in tracking
down your problem.
** Changed in: gnome-panel (Ubuntu)
Status:
Ok, I am stuck with a silly problem, please forgive me because this the
first time I attempt to debug.
From the instruction given here:
http://wiki.ubuntu.com/DebuggingProgramCrash
Which points to here:
https://wiki.ubuntu.com/Backtrace
I followed the instructions in section Already running
Ok, I saw these in the .xsession-errors:
ICEDTEAPLUGIN_DEBUG = (null)
The program 'gnome-panel' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.
(Details: serial 22028 error_code 8 request_code 1 minor_code
the crash seems to be a libxcb one
** Changed in: libxcb (Ubuntu)
Sourcepackagename: gnome-panel = libxcb
Assignee: Ubuntu Desktop Bugs (desktop-bugs) = (unassigned)
Status: Incomplete = New
** Changed in: libxcb (Ubuntu)
Importance: Medium = Low
** Changed in: libxcb (Ubuntu)
I followed the instructions of Pedro Villavicencio and I attach the
debug's output. I hope this will be useful, by confirming that it is an
libxcb issue.
** Attachment added: gdb-gnome-panel.txt
http://launchpadlibrarian.net/19653631/gdb-gnome-panel.txt
--
two xscreens - gnome panel crashes
I also attach the error from the file .xsession-errors
** Attachment added: gnome-panel_xsession-errors.txt
http://launchpadlibrarian.net/19653833/gnome-panel_xsession-errors.txt
--
two xscreens - gnome panel crashes
https://bugs.launchpad.net/bugs/278261
You received this bug notification
** Changed in: gnome-panel (Ubuntu)
Status: Invalid = Confirmed
--
two xscreens - gnome panel crashes
https://bugs.launchpad.net/bugs/278261
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I downgraded to the 173 nvidia drivers as suggested by revgazza and the
desktop is fully shown on external monitor. However, the gnome-panel's
100% consuming bug still remains.
--
two xscreens - gnome panel crashes
https://bugs.launchpad.net/bugs/278261
You received this bug notification because
I changed to nvidia 173 driver, gnome-panel problem still occurs.
--
two xscreens - gnome panel crashes
https://bugs.launchpad.net/bugs/278261
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Happens for me with or without Compiz activated.
Also Nautilus refuses to open windows on Screen 1 (they always open on Screen 0)
Beginning to regret having upgraded to Intrepid. This is seriously affecting my
productivity.
--
two xscreens - gnome panel crashes
botticchio, your problem happened for me using the 177 nvidia-drivers.
Using the 173 drivers fixes the problem
--
two xscreens - gnome panel crashes
https://bugs.launchpad.net/bugs/278261
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I am seeing the same problem as reported by user chewearn. However, it
only seems to happen when I have compiz activated.
kernel: 2.6.27-7-generic
Ubuntu: Intrepid(8.10)
Gnome: 2.24.1
nvidia-drivers: 177
gnome-panel: 1:2.24.1-0ubuntu2
compiz: 1:0.7.8-0ubuntu4.1
In addition, I don't know if it is
I am seeing the same problem.
kernel: 2.6.27-7-generic x86_64
Ubuntu: Intrepid(8.10)
Gnome: 2.24.1
nvidia-drivers: 177
gnome-panel: 1:2.24.1-0ubuntu2
Two monitors, separate X screens.
If I click on a panel application launcher on screen 2, gnome-panel stop
responding and consumed 100% CPU. An
the problem is that crashes is the wrong word, it just doesn't respond anymore.
a error window is shown, though this is not being filled with any
information(so a empty window with error as the title)
/var/crash is therefore empty.
though this bug seems to not be there on every bootup. I can't
Thank you for taking the time to report this bug and helping to make Ubuntu
better. However, your crash report is either missing or challenging to deal
with as a '.crash' file. Please follow these instructions to have apport report
a new bug about your crash that can be dealt with by the
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/18222465/Dependencies.txt
--
two xscreens - gnome panel crashes
https://bugs.launchpad.net/bugs/278261
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
furthermore I got 3 gnome-panel processes, that are the top 3 CPU
consuming processes, being 80% all the time
--
two xscreens - gnome panel crashes
https://bugs.launchpad.net/bugs/278261
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
after this bug occurs I got another gnome-panel process
the 3 CPU consuming processes were active even though the bug described wasn't
produced yet btw.
A killall gnome-panel results in a normal gnome-panel process that
uses nearly no CPU, and the bug described above is not there anymore.
48 matches
Mail list logo
