** Bug watch added: Debian Bug tracker #492662
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=492662
** Also affects: debian via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=492662
Importance: Unknown
Status: Unknown
** Bug watch added: Red Hat Bugzilla #485588
https://bu
Public bug reported:
Binary package hint: xorg
I am using the stock Lucid Firefox, with a few extensions including
NoScript. When I click on the NoScript icon in the status bar X crashes
and I am sent back to the gdm login screen.
/var/crash is empty, but in /var/log/gdm/:0.log.1 I found:
Backt
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/48014808/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/48014809/CurrentDmesg.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/48014810/Dependencies.txt
** A
The backtrace above can be seen towards the end of 2 attachments:
http://launchpadlibrarian.net/48014812/GdmLog1.txt
http://launchpadlibrarian.net/48014824/XorgLogOld.txt
--
[Lucid] Clicking on firefox status bar causes segmentation fault in X
https://bugs.launchpad.net/bugs/577155
You received
Done a little more testing, and it is only the NoScript icon that causes
the crash. I can click on other parts of the status bar fine. Blank
parts are fine. I also have icons for the GreaseMonkey and
AutoHideStatusbar extensions, and left or right clicking on them works
as expected.
Also to note t
** Summary changed:
- [Lucid] Clicking on firefox status bar causes segmentation fault in X
+ [Lucid] Clicking on firefox status bar causes segmentation fault in X (using
radeon)
** Package changed: xorg (Ubuntu) => xserver-xorg-video-ati (Ubuntu)
** Tags added: crash
--
[Lucid] Clicking on f
First to note that this is entirely consistent - it happens every time
without fail. Also to say my laptop was stable using karmic, this
problem appears to have started once I upgraded to lucid.
Bit more investigation. I have now installed the debug packages:
xserver-xorg-video-radeon-dbg xserver
Following the instructions at https://wiki.ubuntu.com/X/Backtracing I
ssh'ed in and used gdb to generate the attached gdb log.
Another note, I have looked for /etc/X11/core and there is no such file.
** Attachment added: "gdb-Xorg.txt"
http://launchpadlibrarian.net/48018042/gdb-Xorg.txt
--
[
I've also triggered this by right clicking on a link in firefox (to save
target as ...).
--
[Lucid] Clicking on firefox status bar causes segmentation fault in X (using
radeon)
https://bugs.launchpad.net/bugs/577155
You received this bug notification because you are a member of Ubuntu
Bugs, whic
One thing I was wondering if is this bug is related to encrypted file
systems. My hypothesis would be that the whole of the sqlite db would
need to be re-encrypted after an update and sync, and maybe banshee
1.5.x is rather more keen on doing a sync. Or maybe it is sqlite.
So could other people ex
** Summary changed:
- mountall 0.2.5 and cryptsetup fail to boot when using usplash
+ mountall 0.2.5 and cryptsetup fail to boot when using usplash (encrypted root)
** Description changed:
+ Note that this bug is (now) just for those with an encrypted root. A
+ workaround that seems to work for
*** This bug is a duplicate of bug 408255 ***
https://bugs.launchpad.net/bugs/408255
** Attachment added: "ApportLog.txt"
http://launchpadlibrarian.net/31163662/ApportLog.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/31163663/Dependencies.txt
** Attachment
*** This bug is a duplicate of bug 408255 ***
https://bugs.launchpad.net/bugs/408255
These are the files from /var/crash/
** Attachment added: "memtest86+.0.crash"
http://launchpadlibrarian.net/31163758/memtest86%2B.0.crash
--
During upgrade from jaunty to karmic: package_hook crashed wi
** Attachment added: "_usr_bin_landscape-sysinfo.0.crash"
http://launchpadlibrarian.net/31163863/_usr_bin_landscape-sysinfo.0.crash
--
package_hook crashed with IOError in write()
https://bugs.launchpad.net/bugs/408255
You received this bug notification because you are a member of Ubuntu
Bugs
** Attachment added: "_usr_bin_terminator.1000.crash"
http://launchpadlibrarian.net/31163902/_usr_bin_terminator.1000.crash
--
package_hook crashed with IOError in write()
https://bugs.launchpad.net/bugs/408255
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Attachment added: "_usr_sbin_cupsd.0.crash"
http://launchpadlibrarian.net/31163934/_usr_sbin_cupsd.0.crash
--
package_hook crashed with IOError in write()
https://bugs.launchpad.net/bugs/408255
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
My bug has been marked as a duplicate, so I am going to attach the files
from /var/crash/ to this bug. This bug may also be related to bug
#332350 - or at least the apport part of it. The memtest86+ may also be
related.
$ ll /var/crash
total 376
-rw--- 1 root root 190776 2009-09-01 18:38 memte
** Attachment added: "_usr_share_apport_package_hook.0.crash"
http://launchpadlibrarian.net/31163938/_usr_share_apport_package_hook.0.crash
--
package_hook crashed with IOError in write()
https://bugs.launchpad.net/bugs/408255
You received this bug notification because you are a member of Ubu
** Tags added: ubuntu-boot-experience
--
privoxy not start at boot - karmic
https://bugs.launchpad.net/bugs/427625
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
https://lists.ub
Might be related to bug #426906 - will try the ubuntu-boot ppa
--
suspend (to ram) no longer works - regression in karmic
https://bugs.launchpad.net/bugs/426415
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
On closer reading, it was working for 2.6.31-9 in bug #426906, while it
didn't work for -9 for me. So prob not related. But will try ubuntu-boot
anyway ...
--
suspend (to ram) no longer works - regression in karmic
https://bugs.launchpad.net/bugs/426415
You received this bug notification because
Same problem here - a physical Karmic machine (upgraded from Jaunty).
Audio CDs do mount automatically. DVDs and data CDs do not mount
automatically. However I can mount from the command line and use the
DVDs fine.
It all worked fine under Jaunty. Output of lshw attached.
** Attachment added: "ls
Changing to devicekit-disks as hal is deprecated in Karmic and
devicekit-disks is replacing it.
See https://wiki.ubuntu.com/KarmicKoala/TechnicalOverview#hal
deprecation for notes.
** Package changed: hal (Ubuntu) => devicekit-disks (Ubuntu)
--
cdrom is not mounted (9.10 alpha 5)
https://bugs.l
It might be related to bug #430605 - also automount not happening,
though for different devices.
--
external harddrive (luks encrypted) will not mount automatically
https://bugs.launchpad.net/bugs/428435
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
I should also say that mounting USB media works fine (USB disk, camera
over USB). Is that the same for other people on this bug?
--
cdrom is not mounted (9.10 alpha 5)
https://bugs.launchpad.net/bugs/430605
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
Public bug reported:
Binary package hint: conky
It seems to happen most of the time when logging out. It worked fine in
jaunty.
ProblemType: Bug
Architecture: amd64
Date: Mon Sep 21 13:07:05 2009
DistroRelease: Ubuntu 9.10
Package: conky 1.7.2-0ubuntu1
ProcEnviron:
PATH=(custom, user)
LANG=en_
** Attachment added: ".home.mish..conkyrc.txt"
http://launchpadlibrarian.net/32152599/.home.mish..conkyrc.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/32152600/Dependencies.txt
--
[karmic] conky crashes on logout
https://bugs.launchpad.net/bugs/433966
You rece
Here is the crash report
** Attachment added: "_usr_bin_conky.1000.crash"
http://launchpadlibrarian.net/32152650/_usr_bin_conky.1000.crash
--
[karmic] conky crashes on logout
https://bugs.launchpad.net/bugs/433966
You received this bug notification because you are a member of Ubuntu
Bugs, whi
Just tested this today and it worked fine for me. However bug #430605
was also fixed overnight for me. Can you retest this and report whether
it is still an issue?
--
external harddrive (luks encrypted) will not mount automatically
https://bugs.launchpad.net/bugs/428435
You received this bug noti
I'm happy to report that the problem has been solved by kipi-plugins
0.9.0 - the DNG files are properly generated.
** Changed in: kipi-plugins (Ubuntu)
Status: Incomplete => Fix Released
--
DNGconverter produces invalid DNG files
https://bugs.launchpad.net/bugs/493804
You received this bu
I'm wondering if this is related to
"rc2 currently does not wait for localhost"
from
https://wiki.ubuntu.com/FoundationsTeam/Specs/LucidUpstartServerReview -
which links to a possibly related bug in samba - bug #462169.
--
privoxy not start at boot - karmic
https://bugs.launchpad.net/bugs/42762
** Attachment added: "CRW_4212.dng"
http://launchpadlibrarian.net/36551033/CRW_4212.dng
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/36551034/Dependencies.txt
--
DNGconverter produces invalid DNG files
https://bugs.launchpad.net/bugs/493804
You received this bug n
Public bug reported:
Binary package hint: digikam
When I use DNG converter it produces DNG files which are not valid. The
camera is a Canon EOS 300D producing .CRW format files. When I run
DNGconverter from the command line no errors are reported. Using file it
seems to be OK:
$ file CRW_4212.dn
** Attachment added: "CRW_4212.CRW"
http://launchpadlibrarian.net/36551245/CRW_4212.CRW
--
DNGconverter produces invalid DNG files
https://bugs.launchpad.net/bugs/493804
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Bug watch added: KDE Bug Tracking System #217897
http://bugs.kde.org/show_bug.cgi?id=217897
** Also affects: digikam via
http://bugs.kde.org/show_bug.cgi?id=217897
Importance: Unknown
Status: Unknown
--
DNGconverter produces invalid DNG files
https://bugs.launchpad.net/bugs/49
The command you gave above did not work, I got the error
Usage: apport-gtk
apport-gtk: error: no such option: -p
I had to do:
apport-collect -p linux 426415
Suspend last worked in Jaunty. I'll do the mainline kernel thing soon.
** Tags added: apport-collected
--
suspend (to ram) no longer
I had firefox start to crash today. I've just uninstalled libmoon (and
moonlight-plugin-core and moonlight-plugin-mozilla as they depend on it)
and firefox works fine again. I have an apport report, but it is 156MiB
so I might just upload the report from /var/crash/ instead. Let me know
if you want
** Attachment added: "_usr_lib_firefox-3.6_firefox-bin.1000.crash"
http://launchpadlibrarian.net/40960025/_usr_lib_firefox-3.6_firefox-bin.1000.crash
--
cannot open Firefox when libmoon is installed
https://bugs.launchpad.net/bugs/538796
You received this bug notification because you are a m
Sorry, the command I actually had to do was in fact:
apport-cli -p linux -u 426415
--
suspend (to ram) no longer works - regression in karmic
https://bugs.launchpad.net/bugs/426415
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubu
In my case I upgraded to Lucid a couple of weeks ago and firefox worked
fine until today. I had made no changes to my firefox set up recently. I
use a few different firefox profiles and all the ones I tested were
affected, and they all work fine following the removal of libmoon et al.
The simplest
I have now tested suspend to RAM (or sleep as it now seems to be called)
with the mainline kernel and it still doesn't work. I will try later
with the suspend from text mode and see if there is any output.
$ uname -a
Linux whisper 2.6.34-999-generic #201003151003 SMP Mon Mar 15 10:10:24 UTC 2010
I tried the apport thing again, as it doesn't seem to have actually
attached anything and I got the following output. Any ideas what might
be wrong?
$ apport-collect 426415
hook /usr/share/apport/package-hooks//source_linux-meta.py crashed:
Traceback (most recent call last):
File "/usr/lib/pytho
A crash report to look at - done by running
$ apport-collect 426415
** Attachment added: "_usr_share_apport_apport-gtk.1000.crash"
http://launchpadlibrarian.net/41026485/_usr_share_apport_apport-gtk.1000.crash
--
apport-gtk crashed with --- in _request()
https://bugs.launchpad.net/bugs/5163
I've just reinstalled moonlight-plugin-mozilla (together with libmoon of
course) to check the crash again, but firefox is now happy again. Maybe
there was a bug in one of the lower libraries that caused libmoon to
fail that has since been fixed by one of the updates?
I'll stay subscribed, but unle
@Wayno - the bug you are experiencing is not this bug, but bug #533775
Basically you need to right click on the panel, select Add to Panel and
choose the "Indicator Applet" - then you should have a working typing
break icon. If you have any follow up comments, please add then to bug
#533775.
** S
Public bug reported:
Everyone now and then boot hangs. This probably happens about once a
week, and I boot the computer once or twice a day. When it happens I
hold the power button until it powers down, power up again and it's
fine. When it hangs it shows the message:
(process:311): Glib-WARNING
** Attachment added: "AlsaDevices.txt"
http://launchpadlibrarian.net/49273228/AlsaDevices.txt
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/49273229/BootDmesg.txt
** Attachment added: "CRDA.txt"
http://launchpadlibrarian.net/49273231/CRDA.txt
** Attachment added: "
Public bug reported:
Binary package hint: light-themes
I've just upgraded to Lucid and my typing break icon has disappeared
(well it's been replaced by a red circle with a line through it). It
used to be a slowly increasing vertical bar indicating how long until
the typing break would happen. Oth
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/40413950/Dependencies.txt
--
[ambiance/radiance] No icon for typing break
https://bugs.launchpad.net/bugs/533775
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
On further investigation I found that the problem is the same in all
themes
** Summary changed:
- [ambiance/radiance] No icon for typing break
+ [lucid] No icon for typing break
** Package changed: light-themes (Ubuntu) => gnome-control-center
(Ubuntu)
--
[lucid] No icon for typing break
http
Not quite sure about the last question. The icon I'm talking about lives
in the notification area - I've never seen anything about the typing
monitor appear using the indicator applet.
(As I understand it the notification area is an area in the top panel.
For me it currently contains a Dropbox ico
Screenshot of my panel as requested
** Attachment added: "Screenshot-panel.png"
http://launchpadlibrarian.net/40510807/Screenshot-panel.png
--
No icon for typing break
https://bugs.launchpad.net/bugs/533775
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
Ah yes that did it, thank you. The volume bit has also been added by
that, which I hadn't noticed was missing.
I think I removed it in karmic as it was just the message applet
(envelope icon) and I thought that I was just getting rid of the instant
messaging thing - I don't use any instant messagi
I've made this confirmed as I've provided the information asked for and
tried out the mainline kernel.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
suspend (to ram) no longer works - regression in karmic
https://bugs.launchpad.net/bugs/426415
You received this bug noti
Sorry can't do apport-collect until bug 516381 is fixed. I tried the
work around of doing it several times but that doesn't seem to help.
--
suspend (to ram) no longer works - regression in karmic
https://bugs.launchpad.net/bugs/426415
You received this bug notification because you are a member o
apport information
** Description changed:
Previous to karmic, suspend to ram worked fine on my desktop. When I
tried it earlier today, the machine froze. Ctrl-Alt-F1 did nothing.
Suspend to RAM worked fine on hardy, intrepid and jaunty - although
sometimes the option would be hidden.
apport information
** Attachment added: "Card0.Amixer.values.txt"
http://launchpadlibrarian.net/41534465/Card0.Amixer.values.txt
--
suspend (to ram) no longer works - regression in karmic
https://bugs.launchpad.net/bugs/426415
You received this bug notification because you are a member of Ubu
apport information
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/41534426/BootDmesg.txt
--
suspend (to ram) no longer works - regression in karmic
https://bugs.launchpad.net/bugs/426415
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
apport information
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/41534468/CurrentDmesg.txt
--
suspend (to ram) no longer works - regression in karmic
https://bugs.launchpad.net/bugs/426415
You received this bug notification because you are a member of Ubuntu
Bugs, whic
apport information
** Attachment added: "Card0.Codecs.codec.2.txt"
http://launchpadlibrarian.net/41534467/Card0.Codecs.codec.2.txt
--
suspend (to ram) no longer works - regression in karmic
https://bugs.launchpad.net/bugs/426415
You received this bug notification because you are a member of U
apport information
** Attachment added: "IwConfig.txt"
http://launchpadlibrarian.net/41534471/IwConfig.txt
--
suspend (to ram) no longer works - regression in karmic
https://bugs.launchpad.net/bugs/426415
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
apport information
** Attachment added: "Lspci.txt"
http://launchpadlibrarian.net/41534475/Lspci.txt
--
suspend (to ram) no longer works - regression in karmic
https://bugs.launchpad.net/bugs/426415
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
apport information
** Attachment added: "Lsusb.txt"
http://launchpadlibrarian.net/41534476/Lsusb.txt
--
suspend (to ram) no longer works - regression in karmic
https://bugs.launchpad.net/bugs/426415
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
apport information
** Attachment added: "PciMultimedia.txt"
http://launchpadlibrarian.net/41534477/PciMultimedia.txt
--
suspend (to ram) no longer works - regression in karmic
https://bugs.launchpad.net/bugs/426415
You received this bug notification because you are a member of Ubuntu
Bugs, wh
apport information
** Attachment added: "ProcModules.txt"
http://launchpadlibrarian.net/41534481/ProcModules.txt
--
suspend (to ram) no longer works - regression in karmic
https://bugs.launchpad.net/bugs/426415
You received this bug notification because you are a member of Ubuntu
Bugs, which
apport information
** Attachment added: "ProcCpuinfo.txt"
http://launchpadlibrarian.net/41534479/ProcCpuinfo.txt
--
suspend (to ram) no longer works - regression in karmic
https://bugs.launchpad.net/bugs/426415
You received this bug notification because you are a member of Ubuntu
Bugs, which
apport information
** Attachment added: "UdevLog.txt"
http://launchpadlibrarian.net/41534531/UdevLog.txt
--
suspend (to ram) no longer works - regression in karmic
https://bugs.launchpad.net/bugs/426415
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
apport information
** Attachment added: "ProcInterrupts.txt"
http://launchpadlibrarian.net/41534480/ProcInterrupts.txt
--
suspend (to ram) no longer works - regression in karmic
https://bugs.launchpad.net/bugs/426415
You received this bug notification because you are a member of Ubuntu
Bugs,
apport information
** Attachment added: "UdevDb.txt"
http://launchpadlibrarian.net/41534482/UdevDb.txt
--
suspend (to ram) no longer works - regression in karmic
https://bugs.launchpad.net/bugs/426415
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
Public bug reported:
Previous to karmic, suspend to ram worked fine on my desktop. When I
tried it earlier today, the machine froze. Ctrl-Alt-F1 did nothing.
Suspend to RAM worked fine on hardy, intrepid and jaunty - although
sometimes the option would be hidden. But whenever the option was there
** Attachment added: "output of lshw"
http://launchpadlibrarian.net/31504594/lshw.txt
** Attachment added: "AlsaDevices.txt"
http://launchpadlibrarian.net/31504595/AlsaDevices.txt
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/31504596/BootDmesg.txt
** Attachment ad
I will do some testing later to see if it is a consistent problem.
--
suspend (to ram) no longer works - regression in karmic
https://bugs.launchpad.net/bugs/426415
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
** Attachment added: "susres.2009-09-08_20:42:21.048269.crash"
http://launchpadlibrarian.net/31506467/susres.2009-09-08_20%3A42%3A21.048269.crash
** Tags added: resume suspend
--
suspend (to ram) no longer works - regression in karmic
https://bugs.launchpad.net/bugs/426415
You received this
Seems pretty consistent in fact. I do seem to get one or two seconds of
still being able to move the mouse around before it freezes up.
I'm attaching a couple of susres.xyz.crash files from /var/crash/
** Attachment added: "crash file 1"
http://launchpadlibrarian.net/31506426/susres.2009-09-0
I've done a few more tests and the behaviour remains consistent. I tried
booting without my usb wireless card to see if that made a difference,
but it seemed the same.
I followed the instructions for suspend from text mode (doing sudo pm-
suspend at the text console - ie Ctrl-Alt-F1) and no output
Tried again with the new kernel - 2.6.31-10-generic - and suspend is
still broken - no change in behaviour.
--
suspend (to ram) no longer works - regression in karmic
https://bugs.launchpad.net/bugs/426415
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
My system is also failing to boot. With 0.2.0~boot1 I had lots of
messages about various non disk filesystems (proc, sys ...) being read
only. I had a root prompt and was able to remount the root file system
as rw, at which point booting continued.
I then upgraded the mountall package to 0.2.0~boo
Here is mountall.log after installing ~boot4 but before reboot.
** Attachment added: "mountall_boot4_before.log"
http://launchpadlibrarian.net/33356804/mountall_boot4_before.log
--
System doesn't boot
https://bugs.launchpad.net/bugs/440896
You received this bug notification because you are a
Here is mountall.log after installing ~boot4 and rebooting (after the
long hang during boot).
** Attachment added: "mountall_boot4_after.log"
http://launchpadlibrarian.net/33356854/mountall_boot4_after.log
--
System doesn't boot
https://bugs.launchpad.net/bugs/440896
You received this bug not
This may well be a different bug to the original reported, but I added
it here from a different computer because I didn't think my main
computer was going to work, so I wouldn't be able to run ubuntu-bug on
the computer with the bug.
Let me know if I should start a new bug for my problems.
--
Sy
There was no output to say that it was checking the filesystem - there
usually is. But it is possible. It has happened on two consecutive
boots, though admittedly the first time I thought it was completely hung
so I switched it off. So it could have been due to do a check and then
restarted it the
Did a reboot and there was no delay this time.
Also checked the last filesystem check time (using tune2fs -l ) and it
appears there was a check during the boot that took ages. I guess this
may have been triggered by whatever went wrong when I used the
0.2.0~boot1 version of mountall.
So I guess
Does the hard drive activity continue? It could be a detailed fsck
happening with no output on screen, as in bug #446596 or it may be
related to bug #443080. My experience is related in bug #440896 .
I had a similar problem, and the fsck took about 10 minutes before boot
continued - if it is doing
Done more testing, and it's not just generating a big list view that
causes slowness. (New Items AND Downloaded AND All Podcasts) is normally
around 10-20 items. If in that I mark an item as old, it still takes 5
seconds of 100% cpu to do that.
--
Banshee uses too much CPU
https://bugs.launchpad.
** Bug watch added: GNOME Bug Tracker #601305
https://bugzilla.gnome.org/show_bug.cgi?id=601305
** Also affects: banshee via
https://bugzilla.gnome.org/show_bug.cgi?id=601305
Importance: Unknown
Status: Unknown
--
Banshee uses too much CPU
https://bugs.launchpad.net/bugs/396268
Y
@geostar1024
Have you tried just waiting? When mountall says it is waiting, stuff may
continue to happen in the background. Basically, if your disk activity light
stays on, then I would not press Escape, but just wait and see if booting
continues anyway.
Only if the disk activity light goes off a
philinux: thanks for your input, but I think your issue is a separate
issue - please file a separate bug for it.
This bug was about when you click install, and then you get asked for
your password twice just for clicking install. That no longer happens.
However, I think this bug may have been onl
The Private folder suggests it might be ecryptfs-utils - using the
encrypted home folders as developed by Dustin Kirkland. These should not
be set up until log in.
whoop: what type of encryption are you using?
--
boot hangs during forced fsck
https://bugs.launchpad.net/bugs/443080
You received t
The link you give is for the ecryptfs-utils type of encryption. Mountall
shouldn't be trying to mount it.
Could you put here the contents of:
/etc/crypttab (if present)
/etc/fstab
/etc/mtab
Also could you run
$ aptitude search cryptsetup
and give the output (the letter at the start will show w
It appears mountall is trying to mount a private directory that is
managed by ecryptfs-utils. The password is the users login password, so
it should not be mounted at boot, but only when the user logs in.
So this is a bug in mountall trying to mount something it shouldn't.
See the bottom line of
OK - I've updated the title and subscribed Dustin Kirkland (who looks
after ecryptfs). I guess the status should be triaged, but I don't seem
to have permission to change that.
I'm also bewildered as to why you are being asked for a password for
/dev/sda5 - have you tried just closing that window
This is still broken with 2.6.31-13-generic
$ show linux-image-2.6.31-13-generic
...
Version: 2.6.31-13.45
When I tried going to tty1 and doing pm-suspend, all I got was
$ sudo pm-suspend
* Reloading Postfix configuration
Then nothing - Ctrl-Alt-F2 , Ctrl-Alt-Del ... nothing.
When doing it fro
Dustin, not sure exactly, though comments #48 and #49 might be of some
use. At any rate, mountall appears to expect that you won't ask for a
password. But I'm no expert, just reading between the lines, so ...
I've resubscribed Scott James Remnant, who is responsible for mountall,
and hope that he
I can confirm this in karmic - on opening, cpu goes through the roof for
a while. Any interaction seems to take ages - even without playing
music. (I mostly use it for managing podcasts).
** Changed in: banshee (Ubuntu)
Status: New => Confirmed
--
Banshee uses too much CPU
https://bugs.la
It seems it is not related to bug #426906 - that seems fixed while I am
not. Here is a crash report with 2.6.31-10-generic and using the ubuntu-
boot repository.
** Attachment added: "susres.2009-09-17_17:43:36.689977.crash"
http://launchpadlibrarian.net/31975747/susres.2009-09-17_17%3A43%3A36
Public bug reported:
Binary package hint: mountall
I have a system with an encrypted root (well encrypted LVM with root,
home and swap volumes). Since upgrading to mountall 0.2.5 I have only
managed to boot once.
When I boot I get usplash appearing and asking me for the passphrase. I
enter it, a
There doesn't appear to be anything useful in /var/log/ or from dmesg.
Though I can access tty1 I can't scroll back through the output.
Will try another reboot without splash and see if that is a consistent
way of actually being able to boot.
--
mountall 0.2.5 does not start recovery console aft
Several reboots later and I only get this problem when I use usplash.
Interestingly, I don't get any messages about waiting while the password
prompt is 'open', even if I leave the machine alone for several minutes
without typing anything at the password prompt, whether with or without
usplash. It
** Summary changed:
- mountall 0.2.5 does not start recovery console after timeout
+ mountall 0.2.5 and cryptsetup fail to boot when using usplash
--
mountall 0.2.5 and cryptsetup fail to boot when using usplash
https://bugs.launchpad.net/bugs/456274
You received this bug notification because yo
I only see the timeout warning after entering the correct passphrase, so
I press Escape after cryptsetup has finished.
I tried waiting several minutes at the cryptsetup prompt in usplash, and
I saw no warning from mountall. I've also entered the passphrase
incorrectly, and there is still no warnin
1 - 100 of 147 matches
Mail list logo
