This also prevents OpenOffice from being able to access many webdav
servers who filter on the user agent string to determine allowable
webdav clients.
I tested this against a webdav server using OOo Writer v3.1.1 and the
user agent string delivered by OOo was blank and the server refused to
allow
** Tags removed: fixed-in-debian fixed-upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/706764
Title:
dphys-swapfile sets incorrect swap size
--
ubuntu-bugs mailing list
Hi Alex,
I tried to run the fix you show for development snapshot on my machine but it
says this:
The program 'dc' is currently not installed. You can install it by typing:
apt-get install dc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
My machine is just a basic Ubuntu 10.04 LTS Lucid server.
It does have the 'bc' calculator installed but not 'dc'.
'dc' being RPN is also quite obtuse to understand being stack based
which might the code difficult to maintain.
'expr' can be a pain to use with all the quoting needed but I see
When I look at upstream 20061020-3:
MEMSIZE=`head -1 /proc/meminfo | awk '{ print $2 }'`
looks like it still might be high by a factor of 1024 since MEMSIZE is in
megabytes and meminfo is in kilobytes.
That is why my patch adjusted for the difference:
MEMSIZE=$(($(cat /proc/meminfo | awk
Public bug reported:
Binary package hint: dphys-swapfile
In Ubuntu 10.04 LTS Lucid.
Package: dphys-swapfile does not set the proper swap file size. It
currently looks at /proc/kcore to determine the memory size and in my
machine this file is 0 bytes.
Attaching patch.
** Affects:
** Patch added: dphys-swapfile.patch
https://bugs.launchpad.net/bugs/706764/+attachment/1804396/+files/dphys-swapfile.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/706764
Title:
Scott,
I just tested a recent Maverick AMI and it does indeed correctly set the
hostname to the newly assigned internal domain name after a stop/start
sequence. So no need to open any other bugs on that score.
+ uname -n
ip-10-117-39-235
+ hostname -s
ip-10-117-39-235
+ hostname -d
cloud-init does a lot of things. I guess what I'm looking for is
whether cloud-init could be made to emit events as it works such that
other upstart jobs can listen for those events and then use them to
trigger their startup as opposed to waiting for the entire cloud-init
process to complete.
Scott,
I just tested a recent Maverick AMI and it does indeed correctly set the
hostname to the newly assigned internal domain name after a stop/start
sequence. So no need to open any other bugs on that score.
+ uname -n
ip-10-117-39-235
+ hostname -s
ip-10-117-39-235
+ hostname -d
cloud-init does a lot of things. I guess what I'm looking for is
whether cloud-init could be made to emit events as it works such that
other upstart jobs can listen for those events and then use them to
trigger their startup as opposed to waiting for the entire cloud-init
process to complete.
This fix is needed for Lucid as well.
I have a clustered filesystem that fails because of this bug. It relies
upon the hostname value always being set correctly.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in ubuntu.
As the ec2 meta-data, local-hostname, returns the long form of hostname,
I would also propose that an enhancement that a new ec2 meta-data attribute be
added:
local-shortname
that would return the short version of hostname such as is returned from
'hostname -s' on a properly configured
When hostname is properly working on a system all of the following
commands should work as expected:
#uname -n
#hostname -a
#hostname -s
#hostname -d
#hostname -f
#hostname
Source: http://www.debianadmin.com/change-hostname-or-server-name-of-a
-linux-machine.html
--
You received this bug
Running the following commands appears to correctly set all the forms of
hostname on my Lucid ec2 instance:
echo $(curl -s http://169.254.169.254/latest/meta-data/local-hostname)
| sed 's:\..*$::' /etc/hostname
/sbin/sysctl -w kernel.hostname=$(curl -s http://169.254.169.254/latest
Now since my cluster filesystem starts real early in the bootup (S20) I
need the hostname to be set correctly even earlier.
So that would probably require some upstart job to run at S10.
So now I need to see how cloud-init is doing this and if it is early in
the bootup.
--
You received this
This fix is needed for Lucid as well.
I have a clustered filesystem that fails because of this bug. It relies
upon the hostname value always being set correctly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
As the ec2 meta-data, local-hostname, returns the long form of hostname,
I would also propose that an enhancement that a new ec2 meta-data attribute be
added:
local-shortname
that would return the short version of hostname such as is returned from
'hostname -s' on a properly configured
When hostname is properly working on a system all of the following
commands should work as expected:
#uname -n
#hostname -a
#hostname -s
#hostname -d
#hostname -f
#hostname
Source: http://www.debianadmin.com/change-hostname-or-server-name-of-a
-linux-machine.html
--
You received this bug
Running the following commands appears to correctly set all the forms of
hostname on my Lucid ec2 instance:
echo $(curl -s http://169.254.169.254/latest/meta-data/local-hostname)
| sed 's:\..*$::' /etc/hostname
/sbin/sysctl -w kernel.hostname=$(curl -s http://169.254.169.254/latest
Now since my cluster filesystem starts real early in the bootup (S20) I
need the hostname to be set correctly even earlier.
So that would probably require some upstart job to run at S10.
So now I need to see how cloud-init is doing this and if it is early in
the bootup.
--
You received this
Opened a kernel bug about this problem:
https://bugzilla.kernel.org/show_bug.cgi?id=26702
.
** Bug watch added: Linux Kernel Bug Tracker #26702
http://bugzilla.kernel.org/show_bug.cgi?id=26702
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
1. The problem was fixed when I went through the 3mb/second channel.
That's probably because it was a different controller or the hardware at
least differed sufficiently enought so as to not exhibit the problem.
2. I had to re-install the OS completely due to data corruption
caused by the READ
I've got this same DRDY ERR occurring on one of my machines, and once it
started it continues to show this error.
I did a drive test on the drives and no errors were found. So this is
definitely something with the kernel.
--
You received this bug notification because you are a member of Ubuntu
I'm seeing this same error with Lucid x86_64 and kernel 2.6.32-21.
My drive is a Hitachi 500GB SATA.
Once this error starts I get hung task timeouts and the systems starts
freezing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
It also generates filesystem errors such that I have to run fsck on the
next boot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/550559
Title:
hdd problems, failed command: READ FPDMA QUEUED
--
And I just checked and my south bridge is an AMD SB750 with 6 SATA. I'm
using AHCI mode.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/550559
Title:
hdd problems, failed command: READ FPDMA QUEUED
I just went and upgraded to kernel 2.6.37-12-server from kernel-ppa
and after rebooting into it I'm still see the same READ FPDMA QUEUED errors I
was before.
Both drives in the machine check out fine according to the drive tests.
I've noticed a little unexplained freezing up and releasing
Cabling is fine.
I just tried to run 'sudo apt-get update' and it is telling me that I
need to run 'dpkg --configure -a'. When I do that it tries to
reconfigure the new kernel package again. So the read errors must have
prevented the configure from completing.
But the read errors will not let
Tried adding libata.force=noncq to 2.6.37-12-server kernel boot line and
the errors are changed to READ DMA EXT.
This particular machine has a Gigabtye M/B.
Some details:
# lspci
00:00.0 Host bridge: Advanced Micro Devices [AMD] RS780 Host Bridge
00:01.0 PCI bridge: Advanced Micro Devices [AMD]
This removal of XDMCP affects us as well.
Why is the LTS release (Lucid) marked as Won't Fix?
This is a critical piece of functionality that has been removed from
Ubuntu without any advance notice or warning.
Please fix this for the LTS release (Lucid).
--
No option to log in remotely via
Milan, excuse me, but closing this report is ridiculous.
It is NOT at all a feature request. This is clearly a bug, a bad bug,
and it needs fixed.
A lot of research and symptoms are detailed in this report that will be
useful for those trying to fix this issue.
And the problem needs to be
*** This bug is a duplicate of bug 221363 ***
https://bugs.launchpad.net/bugs/221363
As the reporter, it seemed as if you were trying to push aside this bug.
I'm glad to hear that is not the case. Thank you.
I have no problem with it being marked as a duplicate of a true bug that
is for
I logged out the user and started a new session:
I went to try accessing Users and Groups from the menu and got the same
behavior as before. Only the Password button for the current user
worked, nothing else.
$ ps
PID TTY TIME CMD
12237 pts/300:00:00 bash
12284 pts/300:00:00
$ ps
PID TTY TIME CMD
12237 pts/300:00:00 bash
19027 pts/300:00:00 ps
$ pkcheck --action-id org.freedesktop.systemtoolsbackends.set
--allow-user-interaction --process 12237
Not authorized.
$ pkcheck --action-id com.ubuntu.systemservice.setproxy
--allow-user-interaction
I am remote logged into the machine using vnc/ssh/nx and this behavior
is extremely undesirable.
Nobody would expect this type of behavior.
I have remote logged into machines for years like this and never saw
this type of behavior.
--
PolicyKit authentication always fails
*** This bug is a duplicate of bug 295405 ***
https://bugs.launchpad.net/bugs/295405
I reinstalled 'dbus' and this cleared the error but I'm seeing strange
behavior.
Logged in as a regular user.
Time and Date: all greyed out and you are not authorized..., no
prompt to enter root
I reinstalled 'dbus' and this cleared the error but I'm seeing strange
behavior.
Logged in as a regular user.
Time and Date: all greyed out and you are not authorized..., no prompt
to enter root password.
Users and Groups: can only change Password for current user, the other
Change buttons do
*** This bug is a duplicate of bug 295405 ***
https://bugs.launchpad.net/bugs/295405
I wouldn't say it's completely different. Just maybe that the
permissions aspect of the bug has been solved but there are still other
related errors showing.
Without sudo:
$ users-admin
(users-admin:18974):
*** This bug is a duplicate of bug 295405 ***
https://bugs.launchpad.net/bugs/295405
I do not have the time at the moment to create another fresh install of
Lucid using ubuntu-server followed by ubuntu-desktop.
I've been reading the wiki entry about PolicyKit. But there is nothing
that says
*** This bug is a duplicate of bug 295405 ***
https://bugs.launchpad.net/bugs/295405
# ps -ef | grep polkitd
root 2552 1 0 15:33 ?00:00:00 /usr/lib/policykit-1/polkitd
# killall polkitd
# ps -ef | grep polkitd
#
# sudo /usr/lib/policykit-1/polkitd
[1] 32132
# Registering
*** This bug is a duplicate of bug 295405 ***
https://bugs.launchpad.net/bugs/295405
The user does not have a password. All users are keyed access.
# ck-list-sessions
Session20:
unix-user = '1001'
realname = 'David Reno'
seat = 'Seat18'
session-type = ''
*** This bug is a duplicate of bug 295405 ***
https://bugs.launchpad.net/bugs/295405
Created a user 'test' with a password:
$ sudo adduser test
Adding user `test' ...
Adding new group `test' (1002) ...
Adding new user `test' (1002) with group `test' ...
Creating home directory `/home/test'
*** This bug is a duplicate of bug 295405 ***
https://bugs.launchpad.net/bugs/295405
And here is Session 26:
Session26:
unix-user = '1002'
realname = 'TEST USER'
seat = 'Seat1'
session-type = ''
active = FALSE
x11-display = ''
# cat /etc/polkit-1/localauthority.conf.d/51-ubuntu-admin.conf
[Configuration]
AdminIdentities=unix-group:admin
The users were not members of 'admin' group. I added them and reran the
tests. Still got the exact same results. It didn't seem to make any
difference.
$ ps
PID TTY TIME
It did not seem to matter that the launcher was group as 'messagebus'.
It still generated the error even after I changed the group.
In my case it was a fresh install of Ubuntu Lucid server and followed by
an install of ubuntu-desktop. Those were the main packages.
--
Fails to run
*** This bug is a duplicate of bug 295405 ***
https://bugs.launchpad.net/bugs/295405
$ jockey-gtk
Traceback (most recent call last):
File /usr/bin/jockey-gtk, line 417, in module
sys.exit(u.run())
File /usr/lib/python2.6/dist-packages/jockey/ui.py, line 428, in run
*** This bug is a duplicate of bug 295405 ***
https://bugs.launchpad.net/bugs/295405
Scroll just a little bit. You have my strace here in comment #5
https://bugs.launchpad.net/ubuntu/+source/system-tools-
backends/+bug/598909/comments/5
--
Failed to execute program
*** This bug is a duplicate of bug 295405 ***
https://bugs.launchpad.net/bugs/295405
Also, look back and you'll see that I've reinstalled all the requested
packages. It didn't change anything.
--
Failed to execute program /lib/dbus-1.0/dbus-daemon-launch-helper: Success
Ok, here is some more info:
# ls -l /lib/dbus-1.0/dbus-daemon-launch-helper
-rwsr-xr-- 1 root avahi 47520 2010-03-30 18:43
/lib/dbus-1.0/dbus-daemon-launch-helper
# cat /etc/group | grep -e 108 -e avahi
messagebus:x:108:
avahi-autoipd:x:111:
avahi:x:112:
# cat /etc/passwd | grep -e messagebus
If I change the UID for messagebus it will be the same id as haldaemon
so I don't think I should do this.
Really I can see nothing wrong with the ids. There are no duplicated
id's.
--
Failed to execute program /lib/dbus-1.0/dbus-daemon-launch-helper: Success
*** This bug is a duplicate of bug 295405 ***
https://bugs.launchpad.net/bugs/295405
This is NOT the same problem! This is not a duplicate bug. The other
cases were about duplicated GID's.
# grep messagebus /etc/passwd
messagebus:x:102:108::/var/run/dbus:/bin/false
# grep 108 /etc/group
Seriously, a user cannot be expected to get into a terminal and go
searching their entire system trying to fix up GIDs that were
incorrectly set by some package. That isn't even a possible general
workaround.
This bug is a SHOWSTOPPER for Ubuntu Lucid. The majority of users are
not going to
Ok, if you think this is not related I'll be glad to open a new bug. I
do think this is the same underlying problem though.
Also:
# apt-show-versions liboobs
liboobs not installed (even not available)
There is no such package.
--
users-admin (System-Administration-Users and Groups) overwrites
Public bug reported:
Binary package hint: system-tools-backends
I am running lucid with system-tools-backends at 2.9.4 and am seeing errors
trying to run any of:
Time and Date
Users and Groups
example:
$ users-admin
(users-admin:12353): Liboobs-WARNING **: There was an unknown error
The UID for user 'messagebus' is already 102. Not sure what you are
asking there.
# apt-cache policy liboobs-1-4
liboobs-1-4:
Installed: 2.30.0-0ubuntu1
Candidate: 2.30.0-0ubuntu1
Version table:
*** 2.30.0-0ubuntu1 0
500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu/ lucid/main
What I got out of the other bugs comment was that it needs to be checked
that there is not two groups using same ids. I don't see that as the
case here.
--
Failed to execute program /lib/dbus-1.0/dbus-daemon-launch-helper: Success
https://bugs.launchpad.net/bugs/598909
You received this bug
57 matches
Mail list logo
