This bug affects my Lubuntu 17.10 (64-bit) system, which has version
5.26.0-8ubuntu1 of the perl and perl-doc packages. I noticed the bug
immediately upon checking for it after Zanna (https://launchpad.net
/~rose-anna-bleasdale / https://askubuntu.com/users/527764/zanna)
reported experiencing it in
For affected people looking for a workaround--this procedure might work,
as it is for the same or a very similar problem:
http://punygeek.blogspot.com/2012/10/ubuntu-1204-how-to-solve-disk-drive-for.html
http://askubuntu.com/a/342002/22949
--
You received this bug notification because you are a
Any of us may close the report by changing its status from New to
Invalid. But I think there may be value to this report: as I mentioned
on AU (http://askubuntu.com/questions/439801/man-command-does-not-work-
with-yelp?noredirect=1#comment574556_439839), I'm not sure why the
"legacy" behavior canno
Public bug reported:
On a Saucy i386 system, Apport informed me Chromium had crashed. Flash
had crashed recently, so this may be a common Flash crash. But I'm not
sure yet, so I'm submitting this bug report. Unfortunately I don't have
much information beyond what's provided in the Apport-attached
*** This bug is a duplicate of bug 1705870 ***
https://bugs.launchpad.net/bugs/1705870
Public bug reported:
I don't know if this should be considered a bug in systemd or apport.
systemd-udevd appears to crash with this bug on each boot. This is a
fully updated Xubuntu Artful amd64 system (in
*** This bug is a duplicate of bug 1705870 ***
https://bugs.launchpad.net/bugs/1705870
** Attachment removed: "the output of dmesg"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1707792/+attachment/4924803/+files/dmesg.txt
--
You received this bug notification because you are a
I've experienced this bug, also in a virtual machine (though with VMware
rather than QEMU). See bug 1707792 for details.
These bugs have a lot in common with bug 1433320, though that is
considered fixed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
*** This bug is a duplicate of bug 1705870 ***
https://bugs.launchpad.net/bugs/1705870
** Description changed:
I don't know if this should be considered a bug in systemd or apport.
systemd-udevd appears to crash with this bug on each boot. This is a
fully updated Xubuntu Artful amd64
*** This bug is a duplicate of bug 1605307 ***
https://bugs.launchpad.net/bugs/1605307
Public bug reported:
Apport told me systemd-resolved crashed when I logged in to my fully
updated Xubuntu Artful amd64 system. This is the same virtual machine
for which I reported bug 1707792 earlier today
*** This bug is a duplicate of bug 1539995 ***
https://bugs.launchpad.net/bugs/1539995
Public bug reported:
On an Xubuntu Artful amd64 system with linux-generic 4.11.0.12.12,
libgtk-3-0 3.22.17-0ubuntu1, and apport-gtk 2.20.6-0ubuntu4, I viewed
the details on a kernel crash report prepared by
*** This bug is a duplicate of bug 1539995 ***
https://bugs.launchpad.net/bugs/1539995
This bug report is for the bug in apport or GTK+, *not* for the kernel
bug (if any) that triggered it. However, in case the kernel oops that
triggered the apport-gtk instance that crashed is relevant, here's
This apparently has not gone away; I got it on Artful. There are some
details in duplicate bug 1707854.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1539995
Title:
apport-gtk crashed with SIGSEGV i
As indicated in the original bug report, the system on which the bug
occurred was Natty, which *is* a currently supported version of Ubuntu.
Since I have no idea what triggered the problem, and it has not happened
since, even when copying files of similar size and under similar
circumstances, it s
I reported this bug after it happening on a Maverick system (as detailed
in the original bug report). Maverick is still supported, through the
end of this month. So I'm unsure what you mean when you ask if I can
reproduce this on a supported release.
In any case, I probably cannot reproduce it at
*** This bug is a duplicate of bug 908737 ***
https://bugs.launchpad.net/bugs/908737
** 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/933088
Title:
pcmanfm crashe
Looking more closely, my stack trace in this bug report doesn't look so
good either. I've installed the debug symbols and just experienced this
same crash again. The stack trace still doesn't look very good...but
nothing seems to have been done with this bug report so far, so I'm
going to mark this
** 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/691378
Title:
audacious2 crashed with SIGSEGV when quitting
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Correction: "with *might have better information" --> "which *might*
have better information"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/690432
Title:
audacious2 crashed with SIGSEGV when quittin
@Evan Martin: As you recommended, I tried viewing the page on several
different browsers.
Now that I have looked closely, and compared different browsers'
rendering side-by-side and with the same screen resolution and color
depth, I think this issue is a little more complicated than I made it
out
** Visibility changed to: Public
** Tags added: i386 natty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/691814
Title:
gdb crashed with SIGSEGV in response to strace command with no arguments
--
There's a bug report on the upstream tracker that is *possibly* the same bug as
this:
http://sourceware.org/bugzilla/show_bug.cgi?id=12271
I've inquired about the details. I'm unsure whether that bug occurs only
when strace is run with no arguments (in which case this is probably the
same bug), o
The original reporter (calimeroteknik at free dot fr, who filed the
upstream bug report) has verified that this is the same bug.
** Also affects: gdb via
http://sourceware.org/bugzilla/show_bug.cgi?id=12271
Importance: Unknown
Status: Unknown
** Changed in: gdb (Ubuntu)
Status
Public bug reported:
Binary package hint: filezilla
I use the desktop environment LXDE (provided by lubuntu-desktop 1.207)
on a Maverick amd64 system. A few days ago, lxpanel (package version
0.5.6-0ubuntu2) crashed and automatically restarted. After that,
Filezilla (package version 3.3.3-1ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/691905
Title:
filezilla notification area icon does not survive lxpanel restart
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://list
That upstream bug report has been found to be a duplicate of another upstream
bug report:
http://sourceware.org/bugzilla/show_bug.cgi?id=12217
That bug was fixed in the upstream source last month, so I guess we just
need a new downstream update for gdb in Ubuntu.
** Bug watch added: Sourceware.o
The old external bug watch (for Sourceware.org Bugzilla #12271) turned
out to be an upstream duplicate -- this is the original bug report.
** Changed in: gdb
Remote watch: Sourceware.org Bugzilla #12271 => Sourceware.org Bugzilla #12217
--
You received this bug notification because you are a me
Sorry about the confusion -- I mean that sourceware-bugs #12217 is the
original bug report, not that this Launchpad report came first.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/691814
Title:
gdb
Public bug reported:
Binary package hint: nvidia-common
On Natty i386, the dpkg --configure step fails in upgrading nvidia-
common to version 0.2.25, producing this output while attempting to
upgrade with "sudo apt-get upgrade":
Setting up nvidia-common (0.2.25) ...
Traceback (most recent call l
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/692065
Title:
package nvidia-common 0.2.25 failed to install/upgrade: subprocess installed
post-installation script returned error exit status 1
--
*** This bug is a duplicate of bug 692022 ***
https://bugs.launchpad.net/bugs/692022
** This bug has been marked a duplicate of bug 692022
bug in nvidia-common (0.2.25)
* You can subscribe to bug 692022 by following this link:
https://bugs.launchpad.net/ubuntu/+source/nvidia-common/+bug/6
** Tags added: amd64 apport-package i386 natty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/692022
Title:
bug in nvidia-common (0.2.25)
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
ht
I've checked to see if this has already been fixed in the Natty git
sources (lp:ubuntu/gdb) -- it has not. But the latest upstream cvs
sources compile on Natty and produce the desired behavior. (For example,
running gdb with no arguments and immediately running the strace command
with no arguments
I've installed pcmanfm-dbg and libfm0-dbg. Unfortunately, I have no idea
what triggers this bug, so I cannot deliberately reproduce it...but
perhaps it will occur again. If I do succeed in reproducing it, should I
file a new bug report, or post here?
--
You received this bug notification because
*** This bug is a duplicate of bug 685168 ***
https://bugs.launchpad.net/bugs/685168
It turns out my stack trace is worse than the stack trace in the
original bug report. I'm marking this as a duplicate.
** This bug has been marked a duplicate of bug 685168
polkit-gnome-authentication-agen
*** This bug is a duplicate of bug 685168 ***
https://bugs.launchpad.net/bugs/685168
** 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/692397
Title:
polkit-gnome-a
Should I file another bug report for the bug that I think this crash
relates to (where left-clicking the Volume Control lxpanel applet fails
to bring up the volume slider)? That problem occurs relatively often,
whereas this crash occurred only once.
--
You received this bug notification because y
Public bug reported:
Binary package hint: lxpanel
On a Maverick amd64 system, LXPanel (package version 0.5.6-0ubuntu2)'s
Volume Control panel applet sometimes stops responding to single-clicks.
The expected and usual behavior of a single left-click on the Volume
Control icon in the LXPanel is to
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/692546
Title:
lxpanel Volume Control applet fails to raise volume slider when clicked
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https:
I have filed a separate bug report (Bug 692546) for the issue where
clicking the Volume Control icon doesn't raise the volume slider. That
report is clearer and more detailed than this report with respect to
that issue. It also contains new information about the issue that I
discovered since making
I still don't have a perfect stacktrace, but for the past week I've run
audacious exclusively in gdb, and I now have a gdb session transcript
for a session where the bug occurred. It shows some information about
the I/O errors that occurred immediately prior to the crash, and gdb was
able to genera
** Attachment added: "examples.desktop"
https://bugs.launchpad.net/bugs/692712/+attachment/1771767/+files/examples.desktop
** 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.ne
Curiously, the same actions that produced this crash have now produced a
similar-seeming crash...but the segfault is in on_launch_error() instead
of fm_launch_files(). As it appears to be a different crash, I've
reluctantly submitted a new bug report for it (Bug 692712).
--
You received this bug
** 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/637588
Title:
audacious2 crashed with SIGSEGV
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.
*** 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 can subscribe to bug 691378 by following this link:
https://bugs.launchpad.net/ubuntu/+source/auda
*** 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 can subscribe to bug 691378 by following this link:
https://bugs.launchpad.net/ubuntu/+source/auda
Note that, contrary to what I said in the original bug report, I do not
think this bug is possibly a duplicate of Bug 640732 or Bug 650531. The
stack trace information that is available does not make it look like
those bugs. I believe that this is in fact a new bug.
--
You received this bug notif
Public bug reported:
Binary package hint: xorg
I run Ubuntu 11.04 Natty Narwhal inside a VMware Workstation 7.1.2
build-301548 virtual machine. The guest machine is 32-bit and has a
single processor (though for some reason it's running the SMP kernel).
In case it's important, the host machine (ru
** Attachment added: "/var/log/Xorg.0.log (full log produced by running startx
as limited user "ek")"
https://bugs.launchpad.net/bugs/676759/+attachment/1736690/+files/Xorg.0.log
--
X11 (xorg) fails to start in natty on vmware
https://bugs.launchpad.net/bugs/676759
You received this bug noti
This is no surprise...but I am able to get xorg to work by removing the
package xserver-xorg-video-vmware (Ubuntu's video driver for VMware
guests). It seems that the problem may be specific to the package
xserver-xorg-video-vmware. Of course, with the generic driver X11 is
extremely slow.
(Unfort
Works for me!
--
X fails to start in vmware/kvm and with various UMS drivers on 2.6.37-5
https://bugs.launchpad.net/bugs/676759
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
htt
Public bug reported:
Binary package hint: pcmanfm
When you double-click on a file to execute in pcmanfm, this will only
succeed if there are no spaces in its absolute path. Spaces in the
filename or in any directories in the file's full path are not escaped
-- consequently, double-clicking on a f
** Description changed:
Binary package hint: pcmanfm
When you double-click on a file to execute in pcmanfm, this will only
succeed if there are no spaces in its absolute path. Spaces in the
filename or in any directories in the file's full path are not escaped
-- consequently, double
I can confirm this in Maverick amd64, Maverick i386, and Natty i386. All
use lsof package version 4.81.dfsg.1-1build1.
** Tags added: i386 natty
** Changed in: lsof (Ubuntu)
Status: New => Confirmed
** Tags added: lucid
--
You received this bug notification because you are a member of U
Here's a better, but not perfect, backtrace from gdb. Complete gdb
session log attached.
#0 __lll_lock_wait ()
at ../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:137
#1 0x75447849 in _L_lock_953 () from /lib/libpthread.so.0
#2 0x7544766b in __pthread_mutex_lock (mutex=
** Visibility changed to: Public
** Description changed:
Binary package hint: policykit-1-gnome
I believe this bug is a duplicate of Bug 694032. However, I am filing a
new bug report, because my stack trace looks better (though not
perfect).
- Shortly after booting Natty and starti
*** This bug is a duplicate of bug 694032 ***
https://bugs.launchpad.net/bugs/694032
Well, my stack appears corrupt, so I doubt this stack trace will add
much of value. I'm marking this as a duplicate of Bug 694032.
** This bug has been marked a duplicate of bug 694032
polkit-gnome-authent
I am able to reproduce this bug on a Natty i386 system. It came up after
I updated (via 'sudo apt-get update', 'sudo apt-get upgrade'), rather
than immediately after logging in. But I updated very soon after logging
in, and I cannot be sure that it had anything to do with this bug.
(I originally r
Possibly relevant information from my now-duplicate-marked bug report:
"This bug might be related to Bug 685168, which I have been experiencing
from time to time lately on this machine (as duplicate bug 692397). When
I saw the Apport icon, I had assumed it was that bug again. However, in
that bug,
Public bug reported:
Binary package hint: gnome-panel
In an Ubuntu Classic Desktop session on a Natty i386 system with gnome-
panel package version 1:2.32.1-0ubuntu4, right-clicking in most places
on the panel and clicking Help fails, raising a message box with the
title "Error" and the message:
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/695260
Title:
gnome-panel help cannot be displayed
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo
** Attachment added: "image of the error message box for everything except the
trash can"
https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/695260/+attachment/1778695/+files/error-message-box-for-everything-but-trash-can.png
--
You received this bug notification because you are a m
** Attachment added: "image of the error message box, for the trash can only"
https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/695260/+attachment/1778696/+files/error-message-box-for-trash-can-only.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, w
** Description changed:
Binary package hint: gnome-panel
In an Ubuntu Classic Desktop session on a Natty i386 system with gnome-
panel package version 1:2.32.1-0ubuntu4, right-clicking in most places
on the panel and clicking Help fails, raising a message box with the
title "Error" an
Well, this is odd. Even though right-clicking on the GNOME Panel and
clicking Help fails to bring up the "Using the Panels" help topic,
running this command (which is the same command that gnome-panel
executes to achieve this effect, at least on Maverick) is successful:
gnome-help ghelp:user-guide
I no longer experience this problem on my i386 Lubuntu Natty Alpha 1
system. Yelp now launches successfully (and runs smoothly). Presumably,
some update (to something) fixed it.
My system is now running yelp 2.30.2-0ubuntu1 (a later version than when
I last tested it). Furthermore, I now *do* have
I am experiencing this bug as well (yelp package version
2.30.1-0ubuntu1), on an Lubuntu Maverick amd64 system. This system was
created by installing the lubuntu-desktop package on an existing Xubuntu
Maverick amd64 system (so xubuntu-desktop is installed too), which was
itself upgraded from Xubunt
This bug appears similar to Bug 644025, except that in that bug, yelp
loads (but displays "invalid" characters), and then crashes when the
home button is clicked. (Inspection of the stack traces reveals the
possible similarity.)
This bug (and that one) also appear similar to the old bug 375986. Th
This bug appears similar to Bug 433504, except in that bug, yelp does
not load at all. Inspection of the stack traces reveals the possible
similarity.
This bug (and that one) also appear similar to the old bug 375986. That
bug is filed against the package rarian, which provides
/usr/lib/librarian.
There are two new bugs that appear similar to this one -- Bug 433504
(recently resurrected) and Bug 644025. Inspection of their stack traces
reveals the apparent similarity. I don't think they're duplicates of
this...but in case they are, or the similarity is otherwise useful to
fixing them, I'm po
Public bug reported:
Binary package hint: lxsession
lxsession-logout allows multiple instances in the same lxsession, while
instead, it should probably only be possible to run it once at a time.
(Within the same lxsession, I mean. A global prohibition on multiple
instances of lxsession-logout wou
** Tags added: amd64 natty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/695378
Title:
lxsession-logout allows multiple instances in the same lxsession
--
ubuntu-bugs mailing list
ubuntu-bugs@lis
I just set up a Natty i386 command line system (using the Natty Alpha 1
i386 Alternate Install CD -- it's an option when you press F4 in the
boot menu). Using aptitude, I updated the system, and then installed
yelp (and its dependencies). I made lists of packages installed before
and after the inst
** Attachment added: "package list on Natty command-line system before
installing yelp"
https://bugs.launchpad.net/ubuntu/+source/yelp/+bug/673588/+attachment/1779011/+files/installed-packages-before-installing-yelp.txt
--
You received this bug notification because you are a member of Ubunt
** Attachment added: "package list on Natty command-line system after
installing yelp"
https://bugs.launchpad.net/ubuntu/+source/yelp/+bug/673588/+attachment/1779012/+files/installed-packages-after-installing-yelp.txt
--
You received this bug notification because you are a member of Ubuntu
** Attachment added: "diff showing only yelp and packages installed with it (on
command-line system)"
https://bugs.launchpad.net/ubuntu/+source/yelp/+bug/673588/+attachment/1779013/+files/diff-showing-only-packages-installed-with-yelp.txt
--
You received this bug notification because you ar
Public bug reported:
Binary package hint: yelp
Currently, clicking a link on the Yelp main page to a help topic that is
missing due to the appropriate -docs package (e.g. ubuntu-docs) brings
up a message box with a confusing and technical error message, like:
Unable to load page
The requested UR
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/695511
Title:
yelp should specify which Ubuntu packages provide missing help topics
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://
Public bug reported:
Binary package hint: debian-installer
Installing a command-line system from the Natty Alpha 1 i386 alternate
install CD, all "windows" have nice-looking borders, except the one
showing the progress of "Installing the base system". That one looks
ugly. A screenshot is attached
** Attachment added: "screenshot of "window" with ugly border"
https://bugs.launchpad.net/bugs/695521/+attachment/1779273/+files/installing-the-base-system.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
** Attachment added: "screenshot of "window" with pretty border, for comparison"
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/695521/+attachment/1779274/+files/set-up-users-and-passwords.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, whi
** Description changed:
Binary package hint: yelp
Currently, clicking a link on the Yelp main page to a help topic that is
- missing due to the appropriate -docs package (e.g. ubuntu-docs) brings
- up a message box with a confusing and technical error message, like:
+ missing due to the app
Additional info:
This was with the default (US/English) locale.
I have tried, and failed, to reproduce this bug by installing a command-
line system with the Maverick i386 alternate install CD.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
Binary package hint: grub2
The following line in /etc/grub.d/10_linux is present in Natty but not
Maverick:
GRUB_CMDLINE_EXTRA="$GRUB_CMDLINE_EXTRA vt.handoff=7"
That creates seamless transition to the graphical login screen.
Specifically, it makes the 7th virtual terminal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/695658
Title:
grub2 configuration has vt.handoff=7 even when X11 is not installed
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://li
** Description changed:
Binary package hint: grub2
The following line in /etc/grub.d/10_linux is present in Natty but not
Maverick:
GRUB_CMDLINE_EXTRA="$GRUB_CMDLINE_EXTRA vt.handoff=7"
That creates seamless transition to the graphical login screen.
Specifically, it makes the
I performed a fresh reinstallation and captured 5 minutes of video.
(It's a VMware virtual machine, so that's easy to do.) "Installing the
base system" starts at 2:28, and for most of the progress of that step,
the border looks pretty. It becomes ugly during the installation of
console-setup (3:44)
Correction to that last comment: The border becomes uglified during the
configuration of console-setup, not during its installation.
Also, I am able to reproduce this bug when installing Natty Server (from
the Alpha 1 Server Install CD).
--
You received this bug notification because you are a me
I am able to reproduce this bug (and the workaround) on Natty Server
(installed from the Alpha 1 Server Install CD). Since Ubuntu Server is
configured by default to write status information to tty7, it looks a
little different -- you see a "shadow" of whatever text is written
there.
Arguably the u
** Attachment added: "blank purple screen seen after a natty non-server
command-line system boots up"
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/695658/+attachment/1779636/+files/natty-non-server-command-line-system-blank-purple-tty7.png
--
You received this bug notification becau
** Attachment added: "purple screen with unreadable black text, seen after a
natty server system boots up"
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/695658/+attachment/1779637/+files/natty-server-purple-tty7-with-blank-black-shadow-of-status-messages.png
--
You received this bug
** Attachment added: "same text, now readable after switching to another tty
and back"
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/695658/+attachment/1779638/+files/natty-server-tty7-after-switching-from-another-tty.png
--
You received this bug notification because you are a member
I have found that I only experience this bug when I run yelp with no
arguments. If I run yelp with arguments (e.g. "yelp ghelp:user-guide"),
this crash does not occur. Perhaps this bug is related to yelp's attempt
to render the yelp main page (which might explain the similar crash
documented in Bug
@K. Deniz Ogut: Do you also experience this problem only when running
yelp with no arguments? (One way of running it with no arguments is
System > Help and Support in a standard Ubuntu desktop session.)
Or do you also experience it when you run help with arguments? (One way
of running it with argu
I am able to reproduce this on a Maverick amd64 system running a 2.2 GHz
Intel Core 2 Duo processor (by running the command "yelp ghelp:user-
guide" -- I cannot try running yelp with no arguments, since this system
is affected by Bug 433504). The CPU spikes to 100% for at least 4
seconds.
** Tags
I am also able to reproduce it on a Natty i386 system (also with the
command "yelp ghelp:user-guide"). That system is a VMware Workstation
virtual machine with the 2.2 GHz Intel Core 2 Duo machine (running
Maverick amd64) as the host system. The Natty guest system runs yelp
2.30.2-0ubuntu1. The VMw
Public bug reported:
Binary package hint: yelp
On a Maverick amd64 system with yelp 2.30.1-0ubuntu1, ubuntu-docs
10.10.5, and gnome-user-guide 2.30.0+git20100403ubuntu2, I ran "yelp
ghelp:user-guide". This system is affected by Bug 409706, but I waited
several seconds until the CPU spike was over
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/695929
Title:
yelp takes a long time to load About This Document in the Desktop User Guide
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
h
** 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/695932
Title:
polkit-gnome-authentication-agent-1 crashed with SIGSEGV in
g_data_set_internal()
--
ubuntu-bugs mail
I am able to reproduce this bug on a Maverick i386 system with yelp
2.30.1-0ubuntu1. It seems that xref: links cannot be opened in new
windows, though other links can. An xref: link is a link to part of the
current document. The bug is probably due to yelp trying to open the
xref: link with respect
*** This bug is a duplicate of bug 694032 ***
https://bugs.launchpad.net/bugs/694032
Oops, I meant Bug 694032 in the description, not Bug 694023. I've edited
the description (and I'm also commenting, for the benefit of anyone
who's already read the description).
Anyway, I'm marking this as a
1 - 100 of 1225 matches
Mail list logo
