BUMP.. I have the same issues with my yahoo based email accounts,
Started around the same time as the others. The email accounts do work
in Thunderbird.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
The host is amd64 and the target is i386.
After Colin Watson post on debian-l...@lists.debian.org
Once only:
$ mkdir -p auto
$ ln -sf /usr/share/livecd-rootfs/live-build/auto/* auto/
Each time:
$ export PROJECT=xubuntu SUITE=oneiric ARCH=i386
Public bug reported:
After Colin Watson post on debian-l...@lists.debian.org
Once only:
$ mkdir -p auto
$ ln -sf /usr/share/livecd-rootfs/live-build/auto/* auto/
+ my patch (Bug #893589)
Each time:
$ export PROJECT=xubuntu SUITE=oneiric ARCH=i386
I tried to manually install in the chroot/
apt-get install humanity-icon-theme
also fails with
Unpacking humanity-icon-theme (from .../humanity-icon-theme_0.5.3.11_all.deb)
...
dpkg: error processing
/var/cache/apt/archives/humanity-icon-theme_0.5.3.11_all.deb (--unpack):
unable to install
The fs is btrfs and other packages install fine.
Ph.L.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/893594
Title:
lb build stops at humanity-icon-theme
To manage notifications about this bug go
Here is my udev based live-device recognition system. Diff from 10.10
release
--1
EXTLINUX config :
kernel ../casper/vmlinuz1
append initrd=../casper/initramfs-USB-UDEV boot=casper
I think you arre speaking about uuid= , don't you ?
Could you remove reference to live-media-path in man casper. It's a lot of
waste time trying this feature which will never work ?
Thanks.
By the way, because of this bug I had to use my own method, more general
that the new uuid= because any
I have this same bug with latest bcmwl-kernel-source
5.100.82.38+bdcom-0ubuntu3 on natty (Ubuntu 11.04)
2.6.38-8-generic #42-Ubuntu SMP Mon Apr 11 03:31:50 UTC 2011 i686 i686 i386
GNU/Linux.
I did a dpkg-reconfigure bcmwl-kernel-source to be sure it's not a build
issue. I still have
eth%d:
Public bug reported:
Binary package hint: casper
From Changelog:
casper (1.77+debian-1) unstable; urgency=low
+
+ ..
+ * Added boot parameter live-media=device to force trying to boot from
+a specified device.
From man casper (casper_1.246_i386.deb)
{live-media|bootfrom}=DEVICE
Felix, please reconsider making v-o-dkms and v-o-guest-dkms conflict
with each other: I second that wish.
For me it's also a must have: single image used either as host or guest.
Of course, not both roles are played at the same time by an instance of
the OS !
So, i'd like both dkms kernel
Public bug reported:
Binary package hint: casper
Ubuntu 9.10 casper 1.206 uses grep -E which is misuse under BusyBox
v1.13.3 (Ubuntu 1:1.13.3-1ubuntu7).
Under BusyBox the correct syntax is egrep
egrep -r 'grep -.?E ' *
casper:if /lib/udev/path_id ${sysfs_path} | grep -E -q
LOCAL DAY calculation for 1250AM.
The message header:
-
From: Edwin McGuire mcguiresm...@..
Subject:Software Installation Pains
Date: Wed, 5 Aug 2009 10:50:38 -0600 (Thu, 00:50 PHT)
The DISPLAY (on my monitor) of same:
Aug 06, 1250 AM
It's not a bug.
** Changed in: casper (Ubuntu)
Status: Incomplete = Invalid
--
/etc/init.d/casper:do_stop() misuses casper-snapshot --resync-string=
https://bugs.launchpad.net/bugs/384064
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
You are absolutely right, and I was absolutely wrong filing a bug. Sorry
for the inconvenience. Changed status to invalid.
--
/etc/init.d/casper:do_stop() misuses casper-snapshot --resync-string=
https://bugs.launchpad.net/bugs/384064
You received this bug notification because you are a member
You are right,the snapshot doesn't expand to other filesystems, and I was
wrong in my description. Sorry !
However mount points like /cdrom and /media/LABEL are under /cow and are saved
in the snapshot, but that does no harm b/c the directories /cow/cdrom and
/cow/media/LABEL have no content.
Each time I do a /home snapshot, I have this error message:
cpio: ./ubuntu/.gvfs: Cannot stat: Permission denied
Like as I said in bug 384070 , the directory /cow/home/ubuntu/.gvfs does
exist, is void, and ls /cow/home/ubuntu/.gvfs works fine, but ls
/home/ubuntu/.gvfs gives the error message.
I closed the bug because I didn't reproduce it. I cannot believe I
totally invented it, perhaps was it under a different environment (
persistent/nopersistent, with or without home-rw ). Anyway, if I come
accros again, I'd file another bug, ... after twice checking !
--
Fixing bug 384066 fixed this issue as according to casper - 1.178 changelog,
the first field of *SNAP entries in casper.conf is relative
to /cow, not /root so it is /cow/home that is snapshoted and not /home as
in my tempory workaround.
** Changed in: casper (Ubuntu)
Status:
It's not a bug, because every file/directory searched by casper MUST be
at the root of the filesystem, never inside a directory, be it the
/casper directory, so put your snapshot at the root of any ( ext2 | vfat
) filesystem, not inside the /casper directory which is ONLY for R/O
filesystem,
Public bug reported:
Binary package hint: casper
Ubuntu 9.04 Part 1 of 8
For having snaphot resync work at halt/reboot time I had to workaround 8
bugs. Here they are:
-1- As startup-time, just before exiting, casper should copy
/etc/casper.conf file because the last lines may have been
Part 2 of 8
At reboot/halt time /etc/casper.conf:do_stop() misuse casper-snapshot
command with '--resync-string=${HOMESNAP}'. The = is to be removed.
Patch
---
--- /rofs/etc/init.d/casper 2009-04-18 05:24:22.0 +
+++ /etc/init.d/casper 2009-06-03
Part 3 of 8
'casper-snapshot --resync-string:Defaults()' wrongly sets COW from
$snap_mount value remembered by initrd/casper:try_snap() line:
echo export ${snap_type}SNAP=${snap_mount}:${snapdev}:${snapfile}
/etc/casper.conf # for resync on reboot/halt
--
Snapshot resync is broken. Proposed
Part 4 of 8
'casper-snapshot --resync-string:Defaults()' wrongly sets DEST from
$snapfile value remembered by initrd/casper:try_snap() in
/etc/casper.conf.
--
Snapshot resync is broken. Proposed FIXs.
https://bugs.launchpad.net/bugs/383984
You received this bug notification because you are a
Part 5 of 8
casper-snapshot:Do_snapshot() doesn't limit snapshot to only one
Filesystem which is mandatory for /cow.
FIX:
for TYPE=cpio: add -xdev option to find command
for other TYPEs, does the problem exist ?
--
Snapshot resync is broken. Proposed FIXs.
Part 6 of 8
casper-snapshot:Do_snapshot() excludes files matching the pattern
'*.wh.*', so files are not persistently deleted.
FIX: use this pattern instead: '.wh..wh*'
--
Snapshot resync is broken. Proposed FIXs.
https://bugs.launchpad.net/bugs/383984
You received this bug notification
Part 7 of 8
Perhaps a gnome bug. Anyway it's a minor bug as it only triggers a
warning.
casper-snapshot:Do_snapshot():cpio: ./ubuntu/.gvfs: Cannot stat: refuse
permission
Workaround: find -prune
Here is the patch for part 3 to 7
diff -Naur
Part 8 of 8
At halt/reboot time there is no automatic snapshot, b/c the symlink is
S89casper
FIX: rename it K89casper in /etc/rc{0,6}.d
Workaround (merge with workaround bug#1)
---
#!/bin/sh
# This file: /custom-installation/hooks/casper-bottom.sh
# Usage: have this
I was wrong, on 9.04, *-sn.cpio.gz are broken.
At startup time casper:try_snap() does cpio -i -u -d which fails as
for initrd/bin/cpio only -i is allowed.
Workaround:
!/bin/sh
# This file: /custom-installation/hooks/casper-premount.sh
# Usage: have this file by
Yes, I will.
--
Snapshot resync is broken. Proposed FIXs.
https://bugs.launchpad.net/bugs/383984
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
Public bug reported:
Binary package hint: casper
Ubuntu 9.04
(casper|home)-sn.cpio.gz do not work because casper:try_snap() does
cpio -i -u -d which fails as for initrd/bin/cpio only -i is allowed.
Removing -u -d solves the issue.
** Affects: casper (Ubuntu)
Importance: Undecided
Public bug reported:
Binary package hint: casper
After using a snapshot casper remember in at the end of /etc/casper.conf
for resync at halt/reboot time. But this changes are lost b/c the file
is not copied.
FIX:
in casper, after line
cp casper.log ${rootmnt}/var/log/
add this line
cp
Public bug reported:
Binary package hint: casper
At reboot/halt time /etc/init.d/casper stop:do_stop() misuses casper-
snapshot command with --resync-string=${HOMESNAP} option . The = is to
be removed (cf man casper-snapshot).
** Affects: casper (Ubuntu)
Importance: Undecided
Public bug reported:
Binary package hint: casper
casper-snapshot --resync-string:Defaults()' wrongly sets COW from
$snap_mount value remembered by initrd/casper:try_snap() line:
echo export ${snap_type}SNAP=${snap_mount}:${snapdev}:${snapfile}
/etc/casper.conf # for resync on reboot/halt
for
Public bug reported:
Binary package hint: casper
casper-snapshot --resync-string:Defaults() wrongly sets DEST from
$snapfile value remembered by initrd/casper:try_snap() in
/etc/casper.conf: prefixing with mount point is lacking.
Adding DEST=${MOUNTP}/${DEST} solves the issue.
** Affects:
Public bug reported:
Binary package hint: casper
ROOTSNAP must be limited to the /cow filesystem.
For TYPE=cpio, adding -xdev option to find command solves the issue.
Without this fix, the snapshot would include the whole uncompressed R/O
filesystems + all mounted partitions
** Affects:
Public bug reported:
Binary package hint: casper
casper-snapshot:Do_snapshot() doesn't limit snapshot to only one
Filesystem which is mandatory for /cow.
For TYPE=cpio, add -xdev option to find command solves the issue.
Without this fix the ROOTSNAP is huge as it contents all the filesystem,
Public bug reported:
Binary package hint: casper
casper-snapshot:Do_snapshot() wrongly excludes files matching the
pattern '*.wh.*', so files are not persistently deleted.
Using this pattern '.wh..wh*' fixes the issue.
** Affects: casper (Ubuntu)
Importance: Undecided
Status: New
Public bug reported:
Binary package hint: casper
Probably a gnome bug a ~/.gvfs appears often as broken.
Anyway it's a minor issue as it only triggers a warning.
Adding option -path '*.gvfs.*' -prune to find command works around this
issue.
** Affects: casper (Ubuntu)
Importance:
Public bug reported:
Binary package hint: casper
At halt/reboot time there is no automatic snapshot, b/c the symlink is
S89casper and /etc/init.d/casper start does nothing, it is
/etc/init.d/casper stop that does the resync.
In /etc/rc{0,6}.d, renaming S89casper to K89casper fixes the issue.
Done.
Can I close this bug report ?
Have I to break down my patch which fixes several issue in several patches
solving only one issue at a time ?
I reported *one* bug b/c, from the user's point of view, it is one problem,
even if from the developper view it needs several fixes.
Further more;
*** This bug is a duplicate of bug 384070 ***
https://bugs.launchpad.net/bugs/384070
** This bug has been marked a duplicate of bug 384070
casper-snapshot:Do_snapshot() doesn't limit snapshot to only one Filesystem
--
casper-snapshot:Do_snapshot() doesn't limit snapshot to only one
Public bug reported:
Binary package hint: evolution
In Evolution to get all msgs with same subject, I use the little SEARCH window.
I get the text from the displayed msg. (COPY)
I paste it in the little SEARCH window (PASTE)
I used to do it that way.
It no longer works.
I use
Ubuntu
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/21262292/Dependencies.txt
** Attachment added: ProcMaps.txt
http://launchpadlibrarian.net/21262293/ProcMaps.txt
** Attachment added: ProcStatus.txt
http://launchpadlibrarian.net/21262294/ProcStatus.txt
--
cannot COPY
here is the screenshot
** Attachment added: 090116-bug-rprt
http://launchpadlibrarian.net/21263059/090116-bug-rprt
--
cannot COPY from SUBJ and PASTE in SEARCH
https://bugs.launchpad.net/bugs/317845
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
Binary package hint: gnome-screensaver
Screensavers are solution to a problem that totally disappeared 15 years
ago, where displays itself became able to white-out.
Nowadays, power saving is a big concern, and suspend-to-ram is a big
solution.
Screensavers which eat huge
** Attachment added:
_usr_lib_gnome-screensaver_gnome-screensaver-dialog.1000.crash
http://launchpadlibrarian.net/18816447/_usr_lib_gnome-screensaver_gnome-screensaver-dialog.1000.crash
--
screensavers are totally useless but can be harmful
https://bugs.launchpad.net/bugs/288078
You
46 matches
Mail list logo
