** Visibility changed to: Public
** Description changed:
Binary package hint: unity-2d
In a unity-2d session on the Oneiric i386 20110621 daily-live, unity-2d-
launcher 3.8.8-0ubuntu1 crashed with SIGSEGV in an unspecified function
in libgobject-2.0.so.0. The stack trace here is not ve
Changing from ubiquity to linux, since this bug is a kernel panic, which
sometimes occurs when installing and sometimes not, and which occurs on
both regular and Wubi Ubuntu systems (the latter of which are ubiquity-
free).
Also marking Incomplete for now, pursuant to some requests for
information
*** This bug is a duplicate of bug 691378 ***
https://bugs.launchpad.net/bugs/691378
** This bug has been marked a duplicate of bug 691378
audacious2 crashed with SIGSEGV when quitting
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
** Summary changed:
- audacious2 crashed with SIGSEGV when quitting
+ audacious2 crashed with SIGSEGV when quitting in __lll_lock_wait()
** Description changed:
Binary package hint: audacious
- Audacious2 usually quits with no problems, but occasionally it hangs on
- exit. I am unsure if th
This still occurs on the same machine running brasero 2.32.1-0ubuntu2 on
Natty amd64. The error message is exactly the same. This is with the
same hardware (including the same internal burner) and media type as
before (the DVD+R is from the same spindle). The log of the new burn
attempt is attached
ek@Apok:~$ uname -a
Linux Apok 2.6.38-10-generic #44-Ubuntu SMP Thu Jun 2 21:32:22 UTC 2011 x86_64
x86_64 x86_64 GNU/Linux
** Attachment added: "lspci.natty.txt"
https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/746958/+attachment/2178658/+files/lspci.natty.txt
--
You received this bug
** Attachment added: "lshw.natty.txt"
https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/746958/+attachment/2178659/+files/lshw.natty.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/746958
T
** Attachment added: "lsmod.natty.txt"
https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/746958/+attachment/2178660/+files/lsmod.natty.txt
** Tags added: natty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
In case it's relevant, similar (quite possibly identical) bug 746958
does still occur on Natty.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/700975
Title:
Power calibration area error
To manage no
*** This bug is a duplicate of bug 788710 ***
https://bugs.launchpad.net/bugs/788710
Manual inspection of the original stack trace in this report reveals
that this is the same as bug 788710. (Comparing to the stack trace in
duplicate bug 796497 is most illustrative.)
** This bug has been mark
** 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/801161
Title:
unity-2d-launcher crashed with SIGSEGV in QScriptValue::engine()
To manage notifications about this bug
I'm able to reproduce this bug (with all i386 daily-lives after
20110618, up to the most recent I have tried: 20110623, with unity-2d
/unity-2d-launcher 3.8.8-0ubuntu1 and metacity 1:2.34.0-0ubuntu1), but
only on live CD systems, and only in unity-2d sessions that I did not
manually log in to. That
@RIVIERE Aurélien
Do you have any of the other problems I listed (application icons not
appearing, or appearing and disappearing, or the Unity launcher's contents
scrolling so the topmost icon is invisible)?
"On lightDM, the selected session is Unity but I use the fallback while Unity
doesn't w
** Visibility changed to: Public
** Description changed:
I updated and rebooted an Oneiric i386 system (gnome-control-center
- 1:3.0.2-1ubuntu4, deja-dup 19.2.1-0ubuntu1), and after a short time, I
- was asked if I wanted to configure backup settings. I clicked yes
- (actually I don't remember
@Jakub Grzeszczuk
Does this bug also occur on an Oneiric daily-live
(http://cdimage.ubuntu.com/daily-live/current/)?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/784484
Title:
dramatic kernel pani
It's been a while since Alpha 1 came out, so most current daily-lives
are probably more stable than it was. But if you want to wait until the
next alpha is released, Alpha 2 is expected to be released on July 7th
(https://launchpad.net/ubuntu/+milestone/oneiric-alpha-2).
--
You received this bug
*** This bug is a duplicate of bug 767475 ***
https://bugs.launchpad.net/bugs/767475
** This bug has been marked a duplicate of bug 767475
nothing noticeable occurred computer just stated there was a gpu lockup
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Since this bug has four duplicates, and one of the duplicates (bug
767341) is itself Confirmed, it seems that this bug should be marked
Confirmed as well. Any objections?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
** 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/795309
Title:
gnome-power-manager crashed with SIGABRT in __kernel_vsyscall()
To manage notifications about this bug g
Marking Invalid in libqt-declarative in Arch Linux, since Andrea
Scarpino has deleted the comment on the upstream Qt bug tracker that had
confirmed it for Arch Linux (and searching https://bugs.archlinux.org
doesn't reveal a report separately confirming it).
** Changed in: libqt-declarative (Arch
The stack trace here is very bad, but "#1 0x00c5a7b9 in ?? () from /lib
/ld-linux.so.2" is different from the traces in bug 740878 (where #1 is
in /lib/i386-linux-gnu/libc.so.6) and bug 762318 (where the specific
library is unknown), so I'll keep this as a separate bug for now.
Perhaps "Apport ret
I just reported a crash in gnome-power-manager in Oneiric (bug 795309),
which could possibly be the same as this. While the stack trace here
doesn't contain much information, my stack trace is corrupt, so it only
contains a couple of steps. I know (or at least have good reason to
think) my bug 7953
I have not experienced the crash described here, but I have experienced
a similar crash on login after selecting lightdm over gdm during
yesterday's update (lightdm crashed with SIGSEGV in
g_child_watch_dispatch()), which I reported as bug 795324. That bug is
currently private. (Since it is a crash
** 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/795332
Title:
nautilus crashed with SIGSEGV in
app_chooser_online_get_default_ready_cb()
To manage notifications abo
*** This bug is a duplicate of bug 795332 ***
https://bugs.launchpad.net/bugs/795332
I just reported bug 795332. Comparing the descriptions and stack traces
reveals that it is almost certainly the same bug as this, but with a
much better trace. Therefore, I am marking this as a duplicate of bu
I just filed bug 795332, which is bug 788739 (now a duplicate) with a
much better stack trace. Comparison of bug 795332's trace to the trace
here reveals that they are not the same bug (and thus that this is not
the same bug as bug 788739 either), and that they don't seem likely to
be particularly
** Visibility changed to: Public
** Description changed:
Binary package hint: gnome-power-manager
On an Oneiric i386 system, gnome-power-manager 3.0.2-0ubuntu1 crashed
- with with SIGSEGV in g_cclosure_marshal_VOID__INT() about a minute after
+ with SIGSEGV in g_cclosure_marshal_VOID__INT(
zeitgeist produced some errors not present in Jean-Baptiste Lallement's
log. I don't know whether or not they're relevant to this bug. My log is
attached.
** Attachment added: "Eliah-Kagan-zeitgeist-daemon.log"
https://bugs.launchpad.net/zeitgeist/+bug/793714/+attachment/2
@Robert Ancell
I think 404 (page not found) errors are normal for private bugs to which one
doesn't have access, these days. See bug 434733 in Launchpad itself. I'd like
to keep bug 795324 private until there is good reason to think it doesn't
contain sensitive login information from my machine
** Visibility changed to: Public
** Description changed:
Binary package hint: gnome-settings-daemon
I attempted to shut down an Oneiric i386 system in a unity-2d session
(with gnome-settings-daemon 3.0.2-1ubuntu2) using the indicator-session
menu. All my application windows, desktop ic
gnome-settings-daemon 3.0.2-1ubuntu2 was released on 7 June 2011, the
same day as gnome-user-share 3.0.0-2ubuntu1 (which fixed bug 788714).
Since then, I have not gotten the crash in this bug, but I have gotten a
crash on logout which reminds me of it. I've reported this as bug
795392; there are mo
Changed back to Confirmed based on information from Hans Joachim
Desserud (duplicate bug bug 795596).
** Changed in: gnome-settings-daemon (Ubuntu)
Status: Fix Released => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
** 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/795814
Title:
gnome-power-manager crashed with SIGSEGV in free()
To manage notifications about this bug go to:
https:/
Public bug reported:
Binary package hint: apport
Every time I have installed Oneiric, whether it be from daily-live
images or the Alpha 1 image or derivative (e.g., lubuntu) images, the
installed system has apport disabled (with "enabled=0" in
/etc/default/apport). This continues to be the case w
** Attachment added: "/etc/default/apport"
https://bugs.launchpad.net/bugs/795829/+attachment/2164739/+files/apport
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/795829
Title:
apport disabled by
If you are requesting (further) assistance, rather than attempting to
report a bug, then you should post again in
https://answers.launchpad.net/ubuntu/+source/evolution/+question/160104
rather than creating a bug report. If that is the case, you can close
this bug report by changing its Status from
@Paul Coenraats
You might be able to be of more help than you think. Please read
https://help.ubuntu.com/community/ReportingBugs carefully. That should give you
a sense of how bug reporting in Ubuntu works and what kind of information is
important to provide in bug reports. Then please post here
In my opinion, pppoeconf should not be removed (even in a subsequent
Ubuntu release, which I presume is what you are advocating), because:
(1) pppoeconf is a useful tool for connecting to PPPoE networks on
Ubuntu Server systems and other systems not using NetworkManager.
Removing pppoeconf would m
*** This bug is a duplicate of bug 151539 ***
https://bugs.launchpad.net/bugs/151539
** This bug has been marked a duplicate of bug 151539
No easy way to revert pppoeconf's configuration changes
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
Ubuntu 9.04 Jaunty Jackalope has not been supported since April 2009.
Does this bug still occur with a currently supported release of Ubuntu
like Lucid, Maverick, or Natty? Or, even better, can anyone who
currently experiences this problem test for it on Oneiric (the
development branch)?
If no one
As a correction, Jaunty certainly has been supported after April 2009
(since that's when it was released!)--I meant to say that, since it was
a non-LTS release in April 2009, its support lapsed in October of 2010,
and is thus now unsupported.
--
You received this bug notification because you are
@Dylan McCall
You've marked this as Confirmed in Ubiquity Slideshow--is there any reason this
cannot be changed from New to Confirmed in ubiquity-slideshow-ubuntu in Ubuntu
as well? (The same question goes for bug 794248.)
--
You received this bug notification because you are a member of Ubuntu
** 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/796465
Title:
gnome-settings-daemon crashed with SIGSEGV
To manage notifications about this bug go to:
https://bugs.la
** Description changed:
Binary package hint: gnome-settings-daemon
This crash in gnome-settings-daemon 3.0.2-1ubuntu3 occurred twice
(nearly identical, not very informative stack traces) in succession
after logging in to a recently updated unity-2d session on an Oneiric
i386 system. I
@3vi1
Why do you think this might be the same as bug 788710?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/779878
Title:
gnome-settings-daemon crashed with SIGSEGV
To manage notifications about thi
*** This bug is a duplicate of bug 788710 ***
https://bugs.launchpad.net/bugs/788710
** Visibility changed to: Public
** This bug has been marked a duplicate of bug 788710
gnome-settings-daemon crashed with SIGSEGV in exit()
--
You received this bug notification because you are a member
With gnome-settings-daemon 3.0.2-1ubuntu3 (and possibly earlier
versions, I haven't tried), this bug appears to be reliably producible
by launching a second concurrent instance of gnome-settings-daemon
(i.e., running it when it's already running). I have gotten this to
happen on two separate, simil
** Description changed:
Binary package hint: gnome-settings-daemon
This crash in gnome-settings-daemon 3.0.2-1ubuntu3 occurred twice
(nearly identical, not very informative stack traces) in succession
after logging in to a recently updated unity-2d session on an Oneiric
i386 system. I
For a while (and following an update to a number of packages, a number
of weeks ago) I have no longer experienced this bug on any Oneiric
systems, and no one else ever provided sufficient information to confirm
it (or *any* corroboration at all), I'm closing this bug as Invalid
(rather than Fix Rel
I have successfully produced this crash again with lightdm
0.3.7-0ubuntu2, as requested. I've filed a new report (private duplicate
bug 796521) from that crash. I'm removing the CoreDump.gz attachment in
this bug and marking it public (I've looked over the data in the other
files and it doesn't loo
** Description changed:
Binary package hint: lightdm
On an Oneiric i386 system, I updated a number of packages yesterday
(/var/log/dpkg.log attached compressed as dpkg.log.gz), and was given
the choice between remaining with gdm (2.32.1-0ubuntu5) as my display
manager, or switching to
I had mentioned two bugs in
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/795050/comments/4.
There is now more information about both.
Bug 795324 is now public, and still occurs with lightdm 0.3.7-0ubuntu2
(see
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/795324/comments/5
and b
** Description changed:
Binary package hint: gnome-settings-daemon
This crash in gnome-settings-daemon 3.0.2-1ubuntu3 occurred twice
(nearly identical, not very informative stack traces) in succession
- after logging in to a recently updated unity-2d session on an Oneiric
+ after logging
Public bug reported:
Binary package hint: gsettings-desktop-schemas
On two similar Oneiric i386 systems with gsettings-desktop-schemas
3.0.1-1ubuntu2, the following text appeared in the Terminal while
upgrading libglib2.0-0 from 2.29.6-0ubuntu3 to 2.29.6-0ubuntu4 via "sudo
apt-get upgrade":
Sett
** Attachment added:
"/usr/share/glib-2.0/schemas/org.gnome.desktop.default-applications.gschema.xml"
https://bugs.launchpad.net/bugs/796578/+attachment/2167301/+files/org.gnome.desktop.default-applications.gschema.xml
** Bug watch added: Red Hat Bugzilla #706078
https://bugzilla.redhat.co
** Visibility changed to: Public
** Description changed:
Binary package hint: indicator-datetime
- In an attempt to reproduce bug 789961 on the Oneiric i386 20110614
+ In an attempt to reproduce bug 788801 on the Oneiric i386 20110614
daily-live (same indicator-datetime package version: 0.
I just reported bug 797146, which looks a lot like this and I suspect
should be considered a duplicate, but I'm not sure. Program termination
in bug 797146 occurred in a way I have not previously seen in programs
not being actively debugged.
>From bug 797146's description: "I'm not sure whether or
*** This bug is a duplicate of bug 788801 ***
https://bugs.launchpad.net/bugs/788801
** Visibility changed to: Public
** Description changed:
Binary package hint: indicator-datetime
+
+ This is bug 788801 with a better stack trace. (See below for information
+ about differences near the t
I just posted duplicate bug 797162, which contains a complete stack
trace. (It also specifically supersedes duplicate bug bug 797146, for
whatever that's worth--I filed bug 797162 before I saw that bug 797146
was being definitely considered a duplicate of this bug.)
--
You received this bug notif
** Package changed: software-center (Ubuntu) => seamonkey (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/780236
Title:
Need to use Seamonkey 2.0.14 for Ubuntu 11.04
To manage notifications
With an active Internet connection on the affected machine, please open
a Terminal window and run the command:
apport-collect 797190
That will attach some additional information to this question. After
verifying that it has been attached and that the apport-collected tag
has been added to this bu
(To clarify, the apport-collected tag is added automatically--please do
*not* add it yourself.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/797190
Title:
Ubuntu 11.04 Natty upgrade underclocks and
*** This bug is a duplicate of bug 788710 ***
https://bugs.launchpad.net/bugs/788710
I can see why this is probably bug 788710, as its title is the same as
other duplicate bug 796497 and its trace is semantically similar.
However, this bug's stack trace is *not* the same as bug 796497's. For
e
I have the same entries, except for the gtk-modules directory (so that
directory and its contents aren't what's producing this bug).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/788710
Title:
gnome
@Brendan Donegan
Sorry about that, I should have marked this as affecting linux in Ubuntu before
requesting the apport-collect. Thanks!
** Changed in: linux (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
** 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/797486
Title:
gnome-power-manager crashed with signal 5 in g_object_newv()
To manage notifications about this bug go t
*** This bug is a duplicate of bug 797434 ***
https://bugs.launchpad.net/bugs/797434
** Visibility changed to: Public
** This bug has been marked a duplicate of bug 797434
nm-applet crashed with SIGSEGV in gtk_icon_source_set_pixbuf()
--
You received this bug notification because you ar
I can reproduce this bug (duplicate bug 797494) on a Lubuntu Oneiric
i386 system with the same network-manager-gnome package version. Since
this is in a Lubuntu Desktop session which does not run unity-2d (or any
unity variant, since it is running LXDE), this bug is almost certainly
not related to
** Visibility changed to: Public
** Changed in: network-manager-applet (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/797498
Title:
nm-applet crashed with SI
*** This bug is a duplicate of bug 797498 ***
https://bugs.launchpad.net/bugs/797498
** This bug is no longer a duplicate of bug 797434
nm-applet crashed with SIGSEGV in gtk_icon_source_set_pixbuf()
** This bug has been marked a duplicate of bug 797498
nm-applet crashed with SIGSEGV in g
*** This bug is a duplicate of bug 797498 ***
https://bugs.launchpad.net/bugs/797498
I just filed bug 797498, which is this bug with a complete stack trace.
Ordinarily I would mark it as a duplicate of this bug and link here to
its stack trace, but since no significant work has been done yet i
** Description changed:
Binary package hint: gnome-settings-daemon
This crash in gnome-settings-daemon 3.0.2-1ubuntu3 occurred twice
(nearly identical, not very informative stack traces) in succession
after logging in to a unity-2d session on a recently updated Oneiric
- i386 system. I
** Description changed:
In a 3D Unity session on the Oneiric i386 20110629 daily-live, I opened
the Network control panel in gnome-control-center 1:3.0.2-1ubuntu5 by
using Unity to search for "network" and clicking on the search result
called Network. I configured a network connection with
@alainpannetier
You have misunderstood. Non-administrators cannot create user accounts (nor can
they perform other administrative tasks). Being root is not the same thing as
being an administrator. And the security model you are misunderstanding does
not apply to Linux-based operating systems as
silid has confirmed this in Lucid
(https://answers.launchpad.net/ubuntu/+source/dkms/+question/163792).
Can this be nominated for fixing in Lucid (since it is a serious
stability/usability bug)?
** Tags added: lucid
--
You received this bug notification because you are a member of Ubuntu
Bugs, w
I am unable to reproduce this bug on a Kubuntu Natty i386 system with
qtcreator 2.1.0-0ubuntu2, libkdepim4 4:4.4.10-0ubuntu4, and Qt packages
sourced by
https://launchpad.net/ubuntu/+source/qt4-x11/4:4.7.2-0ubuntu6.2. My
Kubuntu system is affected by bug 752713, so I cannot enter deisgn mode
to att
** Tags added: i386
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/805960
Title:
quickaccess widget not found
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/
With libglib2.0-0-dbg installed, I attempted to retrace with "sudo
apport-retrace -g" followed by the .crash file. This is all I got for
the trace:
Program terminated with signal 5, Trace/breakpoint trap.
#0 0x004d03f9 in g_return_if_fail_warning (
log_domain=0x83de401 "\344=\b\360\263v\a sch
** 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/797712
Title:
gnome-power-manager crashed with signal 5 in g_settings_schema_new()
To manage notifications about this
*** This bug is a duplicate of bug 797712 ***
https://bugs.launchpad.net/bugs/797712
I updated to fix the unrelated nm-applet crash which was interfering
with Apport, and moved the original crash report out of the /var/crash
directory, and this crash (which was apparently happening every time
** Changed in: qt
Status: New => Confirmed
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to qt4-x11 in Ubuntu.
https://bugs.launchpad.net/bugs/791213
Title:
unity-2d-places crashed with SIGSEGV in QMetaObject::metacall()
To manage n
** Also affects: linux via
http://bugzilla.kernel.org/show_bug.cgi?id=31602
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/647043
Title:
Dell Studio 1
Thanks for submitting that information. The "In Progress" status means
that "a developer has taken responsibility to fix the bug and has begun
work" (https://help.launchpad.net/Bugs/Statuses). It does not look like
this is the case yet for this bug, so I'm changing this bug's status
back to "New".
I just took a look at the information you have provided, and while this
bug has been apport-collected, you have not yet provided the other
information. The requested screenshots were previously posted on the web
and linked to in question 160104--for your convenience, I will attach
them. However, on
** Attachment added: "screenshot-showing-smtp-error-message.png"
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/796088/+attachment/2172290/+files/screenshot-showing-smtp-error-message.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
** Attachment added: "screenshot-showing-smtp-server-ping-results.png"
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/796088/+attachment/2172291/+files/screenshot-showing-smtp-server-ping-results.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
Public bug reported:
Binary package hint: xorg
On two machines with significantly different hardware (a VMware
Workstation 7.1.4 build-385536 virtual machine and a Dell Inspiron E1505
laptop) running the Oneiric i386 20110616.1 daily-live (xorg/xserver-
xorg 1:7.6+7ubuntu1, xserver-xorg-input-evd
** Attachment added: "/var/log/Xorg.0.log"
https://bugs.launchpad.net/bugs/798509/+attachment/2172424/+files/Xorg.0.log
** Also affects: xserver-xorg-input-evdev (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
Binary package hint: xorg
On two machines with
*** This bug is a duplicate of bug 793981 ***
https://bugs.launchpad.net/bugs/793981
I cannot access bug 793981 since it's private, so I don't know if it has
a good stack trace (or just good enough for "Apport retracing service"
to have identified this as a duplicate). In case it helps, here's
With today's daily-live (20110617, with ubiquity 2.7.9), this bug is
revealed to be even more interesting. In summary, it appears that this
occurs when ubiquity-dm has not run.
Unlike previous daily-lives for a while, 20110617 has a ubiquity-dm
(graphical Try/Install and language selector menu scr
@Jean-Baptiste Lallement
You had been (so far) unable to reproduce this bug. Given the above
information, if you have not done so already, I recommend trying to produce it
after manually selecting your language and "Try Ubuntu without installing" (or
the equivalent menu item).
--
You received
*** This bug is a duplicate of bug 789207 ***
https://bugs.launchpad.net/bugs/789207
** This bug has been marked a duplicate of bug 789207
X11 crashed after few minutes when evaluating Linaro 11.05 Ubuntu Desktop LEB
--
You received this bug notification because you are a member of Ubuntu
Marking Invalid by reporter's request (bug reports are not deleted, but
Invalid status closes the bug).
** Changed in: xorg-server (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
@Pedro Villavicencio
Since this creates a major usability problem in an important package in Lucid,
can this be nominated for fixing in lucid-updates?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/588
** 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/798722
Title:
gnome-settings-daemon crashed with SIGSEGV
To manage notifications about this bug go to:
https://bugs.la
*** This bug is a duplicate of bug 798722 ***
https://bugs.launchpad.net/bugs/798722
** This bug has been marked a duplicate of bug 798722
gnome-settings-daemon crashed with SIGSEGV
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
Public bug reported:
Binary package hint: ubiquity-slideshow-ubuntu
[This report looks a lot like bug 794248, but it seems to me that they
should not be considered duplicates. If they are considered the same
bug, then perhaps bug 794248 should be the duplicate, since (1) there is
an aspect of thi
** Attachment added: "screenshot_ubiquity-slideshow-ubuntu_Welcome.png"
https://bugs.launchpad.net/bugs/798767/+attachment/2172882/+files/screenshot_ubiquity-slideshow-ubuntu_Welcome.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
There is a similar bug in the binary package ubiquity-slideshow-ubuntu
(on Ubuntu rather than Lubuntu). I'm not sure whether or not that should
be considered the same bug as this. I've reported it separately as bug
798767.
--
You received this bug notification because you are a member of Ubuntu
B
I have found that, once Ubuntu is installed (with Ubiquity), even in the
same login session in which it was installed (after clicking Continue
Testing), pressing 2 or Enter no longer terminates the X server. The
test system was the 20110617 daily-live on the virtual machine.
So I reset the virtual
601 - 700 of 1225 matches
Mail list logo
