** Attachment added: "Xorg.0.log from experimental machine (running Ubiquity)"
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/798509/+attachment/2173845/+files/EXPERIMENTAL%28RUNNING-UBIQUITY%29_Xorg.0.log
--
You received this bug notification because you are a member of Ubuntu
Bu
** Attachment added: "Xorg.0.log from control machine (not running Ubiquity)"
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/798509/+attachment/2173846/+files/CONTROL%28NOT-RUNNING-UBIQUITY%29_Xorg.0.log
--
You received this bug notification because you are a member of Ubuntu
Bugs
** Attachment added: ".xsession-errors from experimental machine (running
Ubiquity)"
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/798509/+attachment/2173851/+files/EXPERIMENTAL%28RUNNING-UBIQUITY%29_xsession-errors.txt
--
You received this bug notification because you are a mem
** Attachment added: ".xsession-errors from control machine (not running
Ubiquity)"
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/798509/+attachment/2173852/+files/CONTROL%28NOT-RUNNING-UBIQUITY%29_xsession-errors.txt
--
You received this bug notification because you are a membe
** Attachment added: "server-9A8405F3FE0A780485714A4B6DD41909C2CF9F83.xkm from
experimental machine (running Ubiquity)"
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/798509/+attachment/2173853/+files/EXPERIMENTAL%28RUNNING-UBIQUITY%29_server-9A8405F3FE0A780485714A4B6DD41909C2CF9F8
** Attachment added: "server-9A8405F3FE0A780485714A4B6DD41909C2CF9F83.xkm from
control machine (not running Ubiquity)"
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/798509/+attachment/2173854/+files/CONTROL%28NOT-RUNNING-UBIQUITY%29_server-9A8405F3FE0A780485714A4B6DD41909C2CF9F83.
** Attachment added: "server-B20D7FC79C7F597315E3E501AEF10E0D866E8E92.xkm from
experimental machine (running Ubiquity)"
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/798509/+attachment/2173855/+files/EXPERIMENTAL%28RUNNING-UBIQUITY%29_server-B20D7FC79C7F597315E3E501AEF10E0D866E8E9
** Attachment added: "server-B20D7FC79C7F597315E3E501AEF10E0D866E8E92.xkm from
control machine (not running Ubiquity)"
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/798509/+attachment/2173856/+files/CONTROL%28NOT-RUNNING-UBIQUITY%29_server-B20D7FC79C7F597315E3E501AEF10E0D866E8E92.
I just tested with the Oneiric i386 20110617 daily-live (on a VMware
Workstation 7.1.4 build-385536 virtual machine), and now this bug does
occur (and exactly as described in
https://bugs.launchpad.net/ubuntu/+source/indicator-
session/+bug/661250/comments/1). That is, in Oneiric, only Suspend (and
The stack trace here looks kind of like
https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/792999/comments/5
in bug 792999, so perhaps this is the same bug as private bug 793981 (as
is bug 792999). However, a symbolic retrace would probably be necessary,
to be sure.
The stack trace in this bu
*** This bug is a duplicate of bug 797078 ***
https://bugs.launchpad.net/bugs/797078
I just compared the stack trace here to the one at bug 797078, and this
is almost certainly the same bug. (Perhaps bug 792999 / bug 793981 will
also eventually be revealed to be the same as bug 797078.) Since
I just marked bug 792999 a duplicate of this bug, after comparing
https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/792999/comments/5
there to
https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/797078/+attachment/2168109/+files/metacity.gdb
here.
"Apport retracing service" had previousl
*** This bug is a duplicate of bug 797078 ***
https://bugs.launchpad.net/bugs/797078
Comparing the stack trace in
https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/792999/comments/5
to the one in
https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/797078/comments/2
shows that this is
** Tags added: amd64 lucid maverick
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/602048
Title:
metacity crashed with SIGABRT in raise() after login
To manage notifications about this bug go to:
ht
If this still occurs on a fully-updated Maverick, Natty, or Oneiric
system, and you're not able to get a good trace using the above method,
please use sudo apport-retrace -g ...
(https://wiki.ubuntu.com/Apport#Tools) to automatically install all
debug symbol package that are relevant and available
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/799632
Title:
metacity crashed with SIGABRT
To manage notifications about this bug go to:
https://bugs.launchpad.net/u
** Description changed:
Binary package hint: metacity
- On the Oneiric i386 20110619 daily-live, metacity 1:2.34.0-0ubuntu1
- crashed with SIGABRT yielding an apparently corrupt and possibly useless
- stack trace. This occurred shortly after the start of a unity-2d
- session, and also almost
** Package changed: ubuntu => chromium-browser (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/812069
Title:
chromium-browser-l10n armel wrong version
To manage notifications about this bug
This is a problem for chromium-browser generally, not just chromium-
browser-l10n. Since chromium-browser-l10n itself is not architecture-
specific, it is possible to install a newer version of it on armel,
alongside older versions of other chromium-browser binary packages. But
that workaround does
@Robin van Ee
Changing back to Invalid in NULL Project, since a non-Invalid status in NULL
Project is not (ever) meaningful; see https://launchpad.net/null. (Please note
that this has no bearing on the issues being discussed.)
** Changed in: null
Status: New => Invalid
--
You received t
I had incorrectly indicated in that question that this was a bug in
lightdm. I was mistaken. The best way to deal with this is to re-report
it (against unity or unity-2d in Ubuntu). Please see the question for
details. I'm marking this report Invalid. I apologize for my error.
** Changed in: light
I guess I was thinking clearer the first time around. This resembles a
number of problems people have had after updates to unity, compiz, or
video drivers, but on reflection I can see that the necessary elements
to show it wasn't about lightdm were not present. I apologize.
@Mark Nighswonger
Not t
@iLugo
I cannot speak for Martin Pitt, nor for Canonical, but I believe I can explain
why this bug is (and should be) of Medium rather than High importance.
Importance for bugs in Ubuntu is assigned according to the priority in
the Ubuntu project as a whole, and the effect of the bugs on Ubuntu
u
*** This bug is a duplicate of bug 794248 ***
https://bugs.launchpad.net/bugs/794248
** Package changed: ubiquity (Ubuntu) => ubiquity-slideshow-ubuntu
(Ubuntu)
** This bug has been marked a duplicate of bug 794248
ubiquity-slideshow-lubuntu Welcome slide has version 11.04 on Oneiric
--
@Ryan
Are you still experiencing this problem? If not, you can mark this bug as
Invalid (or just leave it Expired). If so, can you provide the information
requested in
https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/775590/comments/11?
--
You received this bug notification because you are
This appears to have been fixed in Oneiric. I just tested with the
Oneiric i386 20110606 daily-live, and after I installed with Ubiquity
and then indicated that I wanted to continue testing, when I checked to
see if Restart... and Shut Down... appeared in the indicator session
menu, they were there
*** This bug is a duplicate of bug 788714 ***
https://bugs.launchpad.net/bugs/788714
** Visibility changed to: Public
** This bug has been marked a duplicate of bug 788714
gnome-user-share crashed with SIGABRT in g_option_context_parse() - needs
porting to GTK3
--
You received this bug
This bug seems pretty well understood, but in case it's helpful, I've
produced a more complete stack trace (showing, among other things, that
the crash occurs in the specific function
do_pre_parse_initialization()), attached in duplicate bug 793707.
--
You received this bug notification because y
Public bug reported:
Binary package hint: openbox
On a Lubuntu Natty amd64 system in a Lubuntu Desktop session with
openbox 3.4.11.2-0ubuntu3, unclosable, blank (light gray), borderless
ghost windows sometimes appear. This seems most often to be triggered by
closing a contextual menu (or sometime
** Attachment added: "lubuntu-rc.xml"
https://bugs.launchpad.net/bugs/793836/+attachment/2158050/+files/lubuntu-rc.xml
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/793836
Title:
openbox occasio
** Attachment added: "Screenshot 1 - a normal desktop, with ghost windows"
https://bugs.launchpad.net/ubuntu/+source/openbox/+bug/793836/+attachment/2158055/+files/screenshot1-normal-desktop.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Attachment added: "Screenshot 2 - a fullscreen application, with ghost
windows in front"
https://bugs.launchpad.net/ubuntu/+source/openbox/+bug/793836/+attachment/2158056/+files/screenshot2-fullscreen-vlc.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, w
** Attachment added: "Screenshot 3 - no openbox, no ghost windows"
https://bugs.launchpad.net/ubuntu/+source/openbox/+bug/793836/+attachment/2158057/+files/screenshot3-openbox-not-running.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Description changed:
Binary package hint: openbox
On a Lubuntu Natty amd64 system in a Lubuntu Desktop session with
- openbox 3.4.11.2-0ubuntu3, unclosable, blank (light gray), borderless
- ghost windows sometimes appear. This seems most often to be triggered by
- closing a contextual me
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/793939
Title:
gnome-power-manager crashed with SIGABRT in g_object_newv()
--
ubuntu-bugs mailing list
ubuntu-bugs@lis
Public bug reported:
Binary package hint: ubiquity-slideshow-ubuntu
On the Lubuntu Oneiric Alpha 1 CD, the slideshow that shows as Ubiquity
is installing the operating system (ubiquity-slideshow-lubuntu 40) has
as the text of its first slide:
Welcome!
Thank you for choosing Lubu
** Attachment added: "screenshot_ubiquity-slideshow-lubuntu_Welcome.png"
https://bugs.launchpad.net/bugs/794248/+attachment/2159871/+files/screenshot_ubiquity-slideshow-lubuntu_Welcome.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
Public bug reported:
Binary package hint: ubiquity-slideshow-ubuntu
On the Lubuntu Oneiric Alpha 1 CD, the slideshow that shows as Ubiquity
is installing the operating system (ubiquity-slideshow-lubuntu 40) shows
the Synaptic Package Manager listing packages with Natty package
versions in the "In
** Attachment added:
"screenshot_ubiquity-slideshow-lubuntu_Install-software.png"
https://bugs.launchpad.net/bugs/794252/+attachment/2159880/+files/screenshot_ubiquity-slideshow-lubuntu_Install-software.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Description changed:
Binary package hint: gnome-power-manager
On an i386 machine, I booted the Lubuntu Oneiric Alpha 1 CD, selected
Try rather than Install, and about 10 seconds after the LXDE desktop
came up, Apport informed me that this crash had occurred. A few seconds
later, I
Added libqt-declarative in Arch Linux, as it was confirmed there by
Andrea Scarpino
(http://bugreports.qt.nokia.com/browse/QTBUG-19736?page=com.atlassian.jira.plugin.system.issuetabpanels
:comment-tabpanel&focusedCommentId=156025#comment-156025). Added Qt
(also without a link, since Launchpad doesn
Public bug reported:
Binary package hint: xserver-xorg-video-intel
On a Sony VAIO VGN-NW13F laptop with a single on-board Intel video chip
and no external monitors running Lubuntu Natty amd64 in a Lubuntu
Desktop session, a GPU lockup was reported by Apport to have occurred.
This did not happen u
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/794861
Title:
[gm45] GPU lockup (EIR: 0x0010 ESR: 0x0011 PGTBL_ER:
0x0001 IPEHR: 0x0100)
To manage notifications about this bug go to:
** Description changed:
Binary package hint: xserver-xorg-video-intel
On a Sony VAIO VGN-NW13F laptop with a single on-board Intel video chip
and no external monitors running Lubuntu Natty amd64 in a Lubuntu
Desktop session, a GPU lockup was reported by Apport to have occurred.
This d
@Didier Roche: Will do.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/791213
Title:
unity-2d-places crashed with SIGSEGV in QMetaObject::metacall()
To manage notifications about this bug go to:
htt
This fix (and released bug fixes in general) is available in the daily
live -- you do not have to wait for the next milestone.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/729394
Title:
partman fai
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/727650
Title:
computer-janitor-gtk crashed with DBusException in call_blocking()
--
ubuntu-bugs mailing list
ubuntu-b
*** This bug is a duplicate of bug 721244 ***
https://bugs.launchpad.net/bugs/721244
I've found that:
(1) Closing the Computer Janitor does not produce this crash, by itself.
(2) Click Cancel when asked for my password (after deselecting a package
in the Computer Janitor) produces this crash
** Tags added: maverick
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/721244
Title:
computer-janitor-gtk crashed with DBusException in call_blocking():
org.freedesktop.DBus.Python.computerjanitord
This bug looks a lot like bug 630625. Even though that bug was filed
slightly before this one, it seems to me that perhaps that bug should be
marked as a duplicate of this one, since this bug provides more
information (as attachments), and the person who filed that bug appears
not to be following i
This bug looks a lot like bug 636056, which provides more information
(in its attachments). Perhaps this should be marked as a duplicate of
that bug (even though that bug was reported slightly later).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
Public bug reported:
Binary package hint: firefox
On a Maverick i386 system with firefox 3.6.15+build1+nobinonly-
0ubuntu0.10.10.1, Firefox's "Warning: Unresponsive script" dialog
wrapped text (i.e. inserted a line break) before a slash in the URL's
path, but did not wrap any subsequent text, per
** Patch added: "screenshot showing dialog box with insufficiently wrapped text"
https://bugs.launchpad.net/bugs/738437/+attachment/1921808/+files/Warning-Unresponsive-script.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
** Patch removed: "screenshot showing dialog box with insufficiently wrapped
text"
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/738437/+attachment/1921808/+files/Warning-Unresponsive-script.png
** Attachment added: "screenshot showing dialog box with insufficiently wrapped
text"
@Sebastien
This bug (or more precisely, whatever bug it duplicates) is now a side issue in
a Launchpad question I've been helping someone with. Can you please indicate
the bug that this duplicates?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
Unfortunately I do not have a URL (even one that does require login)
that reliably produces this problem. It seems to me that it should be
pretty easy to write a script that always stalls, but I don't know
JavaScript, which is why I haven't written, tested with, and attached
such a script.
--
You
Public bug reported:
Binary package hint: ubiquity
I was able to install successfully with Ubiquity 2.5.22 (using the
3/6/2011 daily natty-desktop-i386.iso, MD5SUM
0fa821d25ede844897861acf313fa155). However, with Ubiquity 2.5.23 (using
the 3/8/2011 image, MD5SUM dde1a3000b2e0c2dca242dd17bfb286e)
** Attachment added: "screenshot of hung "Preparing to install Ubuntu" step"
https://bugs.launchpad.net/bugs/732257/+attachment/1897355/+files/Preparing-to-install-Ubuntu.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
Since some of the bugs to which this bug is similar are thought possibly
to involve disk issues, I've attached the output of dmesg. I will
provide additional information that is, by the same reasoning,
potentially relevant, in further comments.
** Attachment added: "dmesg"
https://bugs.launchp
Here's the output of "lspci":
00:00.0 Host bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host bridge
(rev 01)
00:01.0 PCI bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge
(rev 01)
00:07.0 ISA bridge: Intel Corporation 82371AB/EB/MB PIIX4 ISA (rev 08)
00:07.1 IDE interface
Here's the output of "lsusb":
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
In case anyone wants to try to reproduce this bug with VMware
Workstation (or a compatible VMware virtualization product), I would
expect that it would occur with most configurations. But in case it's
more specific, I'm attaching the virtual machine (.vmx) file for this
virtual machine, which descr
*** This bug is a duplicate of bug 731536 ***
https://bugs.launchpad.net/bugs/731536
It turns out that the problem with Ubiquity hanging when I click Forward
in the "Preparing to install Ubuntu" step is a separate bug (present on
today's live CD with ubiquity 2.5.24, in which this bug -- the u
Some additional information: When this hang occurs, I am unable to click
on the Quit button, even though it is not grayed out. However, I can
still click on the X (near the upper-left corner of the window), as
expected. When I do this, Metacity informs me that:
Install is not responding.
You may c
Correction: Clicking Force Quit closes the Ubiquity window and Ubiquity
appears no longer to be running, but the command "ps ax | grep -v grep |
grep ubiquity" produces this output:
6237 pts/0Sl+0:22 gksudo --preserve-env -- /usr/bin/ubiquity --debug
gtk_ui
6240 ?Ss 0:00 /us
Unfortunately, I don't know how to reproduce this crash, and it has not
occurred since I initially reported it. I do have libfm0-dbg installed
and I believe I've had it installed on this machine for some time, but
perhaps it was temporarily uninstalled and then I put it back (I was
switching betwee
@Stephen
This doesn't answer your question about when this bug will be fixed...but have
you considered:
(1) Attempting to install from the Alternate Install CD? (Or does that
exhibit a corresponding problem to this one?)
(2) Attempting to install from an older CD (such as one of the numbered
Alp
** Attachment added: "entries from /var/log/dpkg.log related to the recent
updates"
https://bugs.launchpad.net/bugs/728867/+attachment/1884526/+files/dpkg.log.entries.related.to.2011-03-04.updates.txt
** Visibility changed to: Public
--
You received this bug notification because you are a m
I have just reported bug 728867, which I think may be a duplicate of
this bug, but I am not sure. Bug 728867 looks like it may have a better
stack trace, and I was able to describe what I was doing when it
occurred (though of course that description might not actually be
causally related to the bug
I don't think Bartmann's intent was to report the presence of only a few
icons in the default launcher as a bug. I think the problem he is
experiencing is that he *cannot* click on the applications place icon
and view the rest of his applications. See
https://answers.launchpad.net/ubuntu/+source/un
Public bug reported:
Binary package hint: ubiquity
With a resolution of 800x600, running ubiquity and selecting manual
partitioning results in the manual partitioning step (called "Allocate
drive space") expanding the Ubiquity window below the bottom of the
screen, so that it is very difficult to
** Attachment added: "full-screen screenshot showing the Ubiquity window
extending below the bottom of the screen, without the Forward button visible"
https://bugs.launchpad.net/bugs/729057/+attachment/1885173/+files/Allocate-drive-space.png
--
You received this bug notification because you
Why is the status of this bug Opinion? Typically, Opinion would not be
the status of any bug that produces crashes. Considering the events
surrounding its status becoming Opinion, it seems to me that its status
should instead have been changed to Incomplete. Now that the requested
information has b
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/729065
Title:
gnome-display-properties crashed with SIGSEGV in g_object_set()
--
ubuntu-bugs mailing list
ubuntu-bugs
** Description changed:
Binary package hint: gnome-control-center
While running from today's daily live (i.e. desktop) natty CD (md5sum
5f1c4376fb3c42742627d9f77e83547e), with gnome-control-center
1:2.32.1-0ubuntu5, I opened System > Preferences > Monitors (i.e. gnome-
display-propert
*** This bug is a duplicate of bug 727905 ***
https://bugs.launchpad.net/bugs/727905
** Description changed:
Binary package hint: ubiquity
With a resolution of 800x600, running ubiquity and selecting manual
partitioning results in the manual partitioning step (called "Allocate
driv
Besides on netbooks, I think there are three other likely usage cases
where this bug will manifest itself:
(1) A user may manually use a low resolution even on a computer with a
video card and monitor that support higher resolutions, in order to
cause text to appear larger (i.e. for accessibility)
I have been able to reproduce the crash (even though it does not happen
every time, and seems to happen less than half the time). Also, I have
just realized that the crash occurs not when selecting a resolution from
the drop-down menu, but rather than initially attempting to expand the
drop-down me
Yes, certainly. However, both times I was able to produce the crash were
in the same session, and that when running off the daily live CD. Now
that I've installed Natty, should I go ahead and try to reproduce this
bug on the installed, and then install the package from your PPA *after*
successfully
Clarification: "...should I go ahead and try to reproduce this bug on
the installed Natty system running the non-PPA packages, and then
install the package from your PPA *after* successfully reproducing it?"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
*** This bug is a duplicate of bug 631215 ***
https://bugs.launchpad.net/bugs/631215
** Attachment added: "[probably not relevant] text from terminal
installing/configuring VMware Tools)"
https://bugs.launchpad.net/ubuntu/+source/apt-xapian-index/+bug/729157/+attachment/1885619/+files/te
*** This bug is a duplicate of bug 631215 ***
https://bugs.launchpad.net/bugs/631215
** Attachment added: "[probably irrelevant] /var/log/dpkg.log"
https://bugs.launchpad.net/ubuntu/+source/apt-xapian-index/+bug/729157/+attachment/1885620/+files/dpkg.log
--
You received this bug notific
*** This bug is a duplicate of bug 631215 ***
https://bugs.launchpad.net/bugs/631215
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/729157
Title:
update-apt-xap
I am able to reproduce this bug on a Natty i386 system (duplicate bug
729157). The traceback looks slightly different (it has "db.flush()"
instead of "db.add_document(doc)").
** Tags added: amd64 natty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
I've just noticed that bug 709626, bug 721712, bug 726046, bug 726717,
bug 728323, bug 728504, bug 728693, bug 728816, bug 729157, bug 712754,
bug 713404, bug 713567, bug 713928, bug 713972, bug 714118, bug 714331,
bug 717966, bug 719594, bug 720978, bug 721712, bug 726046, bug 726717,
bug 728323,
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/729230
Title:
gnome-display-properties crashed with SIGSEGV in
invoke_get_all_properties_in_idle_cb()
--
ubuntu-bug
To clarify--this new crash appears to follow exactly the same pattern as
the original crash in bug 729065: I had to perform the operation of
running gnome-control-center and attempting to change the screen
resolution several times before I was able to produce this crash, and I
had thought it was ex
I successfully reproduced the original bug on the installed Natty system
(which was running appmenu-gtk 0.1.95-0ubuntu1, which I presume is the
same version that was running on the daily live CD system that I used to
test and install Natty earlier today). So I then enabled your PPA and
installed th
I'm glad to help in making Natty more stable (and quite pleased by your
very rapid response after I initially reported this bug!). Please let me
know if there's anything else I can do.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
I can reproduce this bug on my Natty i386 system with Indicator Applet
Application Menu 0.4.9 (provided by indicator-applet-appmenu
0.4.9-0ubuntu1). After logging in, the menu bar for the Nautilus desktop
doesn't show; only when another application with a menu is launched does
a menu appear. When t
"Are you in unity or classic desktop? If in classic, do you have the
appmenu applet running?"
This Natty system is a VMware virtual machine without graphics
acceleration, so I believe it's a classic desktop (Xorg is the windowing
server, and I run applications by selecting them from a menu which i
** Attachment added: "what the first login after boot-up looks like"
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/729230/+attachment/1886245/+files/natty-desktop-first-login.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
** Attachment added: "what subsequent login sessions look like"
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/729230/+attachment/1886246/+files/natty-desktop-subsequent-logins.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
"If in classic, do you have the appmenu applet running?"
Sorry, I had meant to answer this, but when I was writing my post, I
forgot to. Yes, indicator-applet-appmenu is running. (It does suffer
from bug 718184, but I doubt that's relevant to this bug.)
--
You received this bug notification beca
Will the newly trimmed-down string necessarily cause the advanced
partitioning page to fit in all language translations?
(By the way, like Jeff, I have now verified that, when manual
partitioning is not performed, each step of installer fits on a screen
with 600 vertical pixels. The reason I had n
Public bug reported:
Binary package hint: gnome-panel
On a Natty i386 system with gnome-panel 1:2.32.1-0ubuntu6, without
graphics acceleration (so it is a classic desktop, even though the
session type in GDM is "Ubuntu Desktop Edition", I logged on, and
received messages indicating that all of th
** Attachment added: "screenshot showing error messages and bottom panel with
only Trash"
https://bugs.launchpad.net/bugs/730581/+attachment/1891410/+files/Screenshot.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
Here's my ~/.xsession-errors file. (I renamed it so that I could see it
in the file upload dialog box.)
The part that seems most relevant is:
** (gnome-panel:5657): WARNING **: Failed to load applet
WnckletFactory::ShowDesktopApplet:
GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such
I've reported bug 730581 which (even more so now that I have examined
and posted my .xsession-errors file) I suspect may be a duplicate of
this bug. What do you think?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
Like in bug 716714, when I clicked Don't Delete in all three windows and
then logged out and back in, I got a similar error, but in a different
panel applet (the Indicator Applet). The message box's contents now are:
The panel encountered a problem while loading
"IndicatorAppletAppmenuFactory::In
701 - 800 of 1225 matches
Mail list logo
