This has been driving me to distraction too, as the combination of
privoxy and epiphany-webkit is great. I think I have just stumbled onto
a temporary workaround, which hopefully will help to locate the bug. If
you disable IPv6, it starts correctly.
I put the line:-
net.ipv6.conf.all.disable_ip
@ richardgv #27 - sorry, yes, I have the listen address as
127.0.0.1:8118 in my config too. Before this bug really took hold, that
was the first change necessary top get karmic working on comparison with
Jaunty. Glad those two workarounds work for you too.
--
privoxy not start at boot - karmic
Confusion continues. With no apparent updates, and before I could apply
the IPv6 workaround, one of my machines has started working correctly
again, starting privoxy at startup.
--
privoxy not start at boot - karmic
https://bugs.launchpad.net/bugs/427625
You received this bug notification becaus
I can also confirmn that 0.2.2 does not work on an IBM X31. The boot
process works up to the disk fsck, then simply stops. 0.1.8 works
perfectly. It's a definitive issue, repeatable enough for me to have
wrtten a script to recover using the Live CD after an update.
--
mountall: /proc/filesyst
@Scoot - comment 15
No, as Jonathan says in comment 16, nothing further appears on the screen after
the fsck, in my case of the two partitions I run, has completed. This is with
any version of mountall above 0.1.8
S
--
mountall: /proc/filesystems: No such file or directory
https://bugs.launc
Attached is a photo of the screen at the point at which the boot process
hangs, with "quiet splash" removed from grub2. My systems was re-
installed from scratch a few days ago, and the screen pic was taken
after this morning's update. This is with mountall 0.2.2, in other
words. Standard generi
Public bug reported:
When clicking "Arrange Desktop Icons" in XF Desktop properties, the system
icons, Home. Wastebasket and Removable Devices (I don't use the additional
"Filesystem option) arrange themselves off the screen area to the left rather
than at the top left and visible. A tiny por
SOLVED - A bit bizarre, especially as this is a new installation, and I
even created a new user to test the effect. The problem turned out to
be default keyboard application shortcuts. I removed the two listings
of shortcuts for the display settings manager and the mystery of the
rogue dialog box
Public bug reported:
I suspect this may be a problem with acpid or acpi-scripts. When I
remove or insert the power adaptor, or change screen brightness, the
display settings control box (process "xfce4-display-settings
--minimal") appears. There's np obvious link between these events,.
This is o
Public bug reported:
This resulted:
INFO:softwarecenter.db.pkginfo_impl.aptcache:aptcache.open()
WARNING:softwarecenter.db.update:The file:
'/usr/share/app-install/desktop/sonic-visualiser:x-sonicvisualiser-layer.desktop'
could not be read correctly. The application associated with this file wil
Is anyone able to comment on this issue? I've not been able to find
anything other than an old reference to the same issue, with just one
reply that suggested having a look under /etc/acpi for any pointers, and
no resolution noted. A quick grep of that directory and below shows no
reference to di
Mine:-
/dev/sda3 on / type ext4 (rw,errors=remount-ro,commit=600)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
fusectl on /sys/fs/fuse/connections type fusectl (rw)
none on /sys/kernel/debug type debugfs (rw)
none on /sys/kernel
Latest investigation suggests that if a USB disk is plugged in and
mounted, shutdown fails too. I'll try to do more tests on this, but
again, it would be interesting ti see if others find consistency in
this,
S
--
You received this bug notification because you are a member of Kubuntu
Bugs, whic
@montblanc - sorry about the delay in replying. Yes, that's exactly
right. If I either disable my nfs mount in fstab, meaning it never
mounts the nfs share, or I unmount it before shutting down, then all
works perfectly. The moment my machine has a live nfs mount at shutdown
time, it gets no fur
Yes, I was wondering about what the break point is - someone here had a USB
disk mounted and was experiencing this failure. I've been trying to set check
points in umountnfs.sh to see if I can see what may be causing the problem, but
I fear I soon run out of knowledge. Great the bug has been f
@clint-fewbar #14 - yes, I would say that that is the case. It looks to
my inexpert eye that the -P option is NOT part of the poweroff options
in /usr/lib/xfce4/session/xfsm-shutdown-helper. What bothers me is the
inconsistent nature of using the physical switch to initiate a shut
down. I don't
@Clint Byrum (clint-fewbar) Message 20
I have done as you ask, and I can get consistent failures and successes
which may help. I am running Xubuntu and carried out all these tests
using the shutdown button on the desktop. /etc/default/halt is set to
poweroff.
When shutdown powers off the machi
It's an NFS umount issue.
I've now tried using Natty's umountnfs.sh, but there's no difference, and
I've also tried altering fstab to use an IP address rather than a name. No
difference to the failure.
The immediate shutdown inconsistency is because the NFS mount hasn't yet
happened, triggered b
Yes, I'm sorry if my lack of understanding about the shutdown process
results in false assumptions.
I've added "set -x" to the files mentioned in /etc/init.d
The hang happens, for me, on the nfs umounting. The last four lines
are:-
exec
[ /nfs/home ]
[ no = no ]
fstab-decode umount -f -l /nfs/h
I think this may be an upstream issue. On a whim, I updated a faithful
old Thinkpad running Debian Squeeze to Wheezy, and the same issue occurs
there - when I have an NFS mount, it does not shut down, but when I
unmount it before shutting down, the machine powers off correctly. I
did not go thro
I have a hack that works for me. I should say that I have a very
incomplete understanding of the way the umount* files work with each
other, but I don't think the hack is likely to affect anything else.
I have edited the file /etc/init.t/umountnfs.sh
Somewhere around line 84, alter the following
I wonder if there are other areas of these scripts where perhaps
alternatives are possible, but as the entire sysvinit package has been
flagged as a high importance issue, perhaps it would be better to wait
to see if a proper fix rather than my hack appears. I would suggest you
try clint's sugges
I can confirm the same issue applies to Xubuntu. It's not so easy to
alter /usr/lib/xfce4/session/xfsm-shutdown-helper to include the
settings suggested to KDE.
Also, while the system never seems to power down when choosing the
logout button, there is a slight difference when you use the laptop's
@montblanc - do you have any remote file systems, perhaps samba, mounted? I
think the error occurs in the umountfs script, which, I think (bit may be
wrong) affects all mounted file syystems.
S
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
@montblanc - I thinks that's definitive - there's something wrong with
the umountfs process. I have hashed out my nfs mounts in /etc/fstab the
last couple of days and shutting down is flawless.
@clint-fewbar - does this provide enough info for this to be taken
further? Many thanks for the "set -
25 matches
Mail list logo
