Also confirm -34 solves issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1603719
Title:
[regression] NFS client: access problems after updating to kernel
4.4.0-31-generic
To manage
Same problem. Reverted to 4.4.0-28. Didn't try mainline as -28 was
sufficient.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1603719
Title:
NFS client: access problems after updating to kernel
Same problem, same package version, xenial release amd64 squid pinger
SIGSEGV.
squid3 upgraded to squid as part of the xenial upgrade.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1572715
Title:
Public bug reported:
$ grep user /etc/passwd
user:x:1000:1000:user,,,:/home/user:/bin/bash
useri:x:1000:1000:useri,,,:/export/home/user:/bin/bash
$
These two accounts are collapsed into just useri when presented via lightdm.
Ordering in /etc/passwd doesn't change things.
ProblemType: Bug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/885449
Title:
accountsservice is collapsing multiple distinct accounts into one when
uid is same
To manage notifications about this bug go to:
** Description changed:
$ grep user /etc/passwd
- user:x:1000:1000:user,,,:/home/user:/bin/bash
- useri:x:1000:1000:useri,,,:/export/home/user:/bin/bash
+ scott:x:1000:1000:scott,,,:/home/scott:/bin/bash
+ scotti:x:1000:1000:scotti,,,:/export/home/scott:/bin/bash
$
- These two accounts are
Public bug reported:
$ ls -ld /var/log/lightdm
drwxr-xr-x 2 root root 4096 2011-10-28 21:19 /var/log/lightdm
$
probably should be chmod 1770; chgrp lightdm; like /var/log/gdm
current permissions preclude creation of
/var/log/lightdm/x-0-greeter.log when lightdm runs the greeter as can be
seen
** Description changed:
$ ls -ld /var/log/lightdm
drwxr-xr-x 2 root root 4096 2011-10-28 21:19 /var/log/lightdm
- $
+ $
probably should be chmod 1770; chgrp lightdm; like /var/log/gdm
- current permissions preclude creation of /var/log/lightdm/x-0-greeter.log
when lightdm runs the
Linux server 2.6.35-24-server #42-Ubuntu SMP Thu Dec 2 03:58:11 UTC 2010 x86_64
GNU/Linux
Ubuntu 10.10
Welcome to the Ubuntu Server!
* Documentation: http://www.ubuntu.com/server/doc
New release 'natty' available.
Run 'do-release-upgrade' to upgrade to it.
You have new mail.
Last login: Tue
You have to look at the created hierarchy and ensure there isn't a main
/debian-installer directory. If there is, then such a section was added
to natty-updates and the test was invalid. You can use the multiverse
directory structure as a guide.
--
You received this bug notification because
The problem with the test Brian is that karmic has a main/debian-
installer section and the problem occurs when main/debian-installer
doesn't exist.
The problem usually manifests itself in new dists, in the -updates,
-proposed, and -backports trees, and maybe even security.
If you want to test
Public bug reported:
Binary package hint: linux-image-2.6.35-25-server
XEN/XVM 3.4 virtual guest running maverick.
When running linux-image-2.6.35-24-server, system halts ok.
When running linux-image-2.6.35-25-server, system hangs after printing System
halted.
When running
# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 10.10
Release:10.10
Codename: maverick
# apt-cache policy linux-image-2.6.35-25-server
linux-image-2.6.35-25-server:
Installed: 2.6.35-25.43
Candidate: 2.6.35-25.43
Version table:
***
** Attachment added: uname-a.log
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/706749/+attachment/1804390/+files/uname-a.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/706749
Title:
** Attachment added: version.log
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/706749/+attachment/1804391/+files/version.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/706749
Title:
** Attachment added: dmesg.log
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/706749/+attachment/1804392/+files/dmesg.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/706749
Title:
lspci is empty, as is /proc/bus/pci/devices
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/706749
Title:
virtual guest fails to halt/shutdown fully
--
ubuntu-bugs mailing list
but this is also the case on 2.6.35-24, which works ok
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/706749
Title:
virtual guest fails to halt/shutdown fully
--
ubuntu-bugs mailing list
again.
--
Scott Merrilees
On Thu, Jan 13, 2011 at 09:14, Jeremy Foshee 673...@bugs.launchpad.net wrote:
Hi Scott,
This bug was reported a while ago and there hasn't been any activity in it
recently. We were wondering if this is still an issue? Can you try with the
latest development release
Public bug reported:
Binary package hint: linux-image-2.6.35-22-virtual
I upgraded a XEN VM from lucid to maverick.
Before the upgrade, then VM was able to mount NFS files systems from the
server.
After the upgrade mount_nfs4 was failing with ENXIO.
As can be seen below, linux-image-virtual
Public bug reported:
Binary package hint: bash
$ cat /etc/issue
Ubuntu 10.04.1 LTS \n \l
$ echo $BASH_VERSION
4.1.5(1)-release
$ sleep 5 pid=$!
$ sleep 5 pid=$!; echo $pid
bash: !: event not found
$ sleep 5 pid=$! ; echo $pid
3434
$ (sleep 5 pid=$!; echo $pid)
bash: !: event not found
$
Last night I build another minimal server, and it had the same plymouth
bug.
This morning I applied the current setup of updates, and the plymoth bug
disappeared on both servers.
aptitude reinstall console-setup works ok too, so I can't see the
original bug either anymore.
--
console-setup
If try to remove console-setup, and accept the default to install
console-setup-mini, I get this:
# pstree -ap 17906
aptitude,17906 purge console-setup
├─dpkg,18150 --status-fd 32 --configure console-setup-mini
│ └─frontend,18151 -w /usr/share/debconf/frontend...
│
# ps -ef|grep setup
root 26759 18404 0 10:11 pts/300:00:00 aptitude reinstall
console-setup-mini
root 26959 26759 0 10:11 pts/200:00:00 /usr/bin/dpkg --status-fd 32
--configure console-setup-mini
root 26960 26959 0 10:11 pts/200:00:00 /usr/bin/perl -w
I had done an aptitude upgrade before then reboot which did some
plymouth updates.
After the reboot, I has able to complete an aptitude reinstall cosnole-
setup-mini without killing plymouth like I have been.
So I then did an aptitude install console-setup, and it successfully
reinstalled
Public bug reported:
Binary package hint: console-setup
System is Xen/xVM domU amd64 lucid, minimal build, no X11.
# lsb_release -rd
Description:Ubuntu lucid (development branch)
Release:10.04
# apt-cache policy console-setup
console-setup:
Installed: 1.34ubuntu14
Candidate:
Tried to apport-cli -u however bug 561421 precludes this action.
--
console-setup installation hangs
https://bugs.launchpad.net/bugs/564360
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
This may be a bug in the lauchpad openid login page html, as it only
presents a button for continue while it presents a link for cancel,
and w3m renders the cancel link as a link, but the continue button
is just rendered as inactive text.
--
bug reporting issues, cannot log in Lanchpad in
Further, it seems that xen-netfront.ko at least needs to be in the initrd, as
this may be needed to download the udeb.
If the udeb is on disk, then xen-blkfront.ko would be needed in initrd.
--
Include Xen Modules in 64bit install initrd
https://bugs.launchpad.net/bugs/531883
You received this
Both karmic and lucid initrds are affected.
--
Include Xen Modules in 64bit install initrd
https://bugs.launchpad.net/bugs/531883
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
Seems like debmirror has an undocumented --skip-installer option vis:
# skip debian-installer for each dist in --skip-installer=foo,...
if ($section =~ /debian-installer/) {
my $skipped = 0;
foreach my $skipped_release (@skip_installer) {
if ($dist eq
I rebuild the mini.iso initrd including xen-blkfront.ko and xen-
netfront.ko and rebuild the maps and was able to use this to do an
install, however it would be better if they were included by default.
--
Include Xen Modules in 64bit install initrd
https://bugs.launchpad.net/bugs/531883
You
Similar problem in karmic lucid kernels with a 2 Port NEC USB 2.0
PCcard on an IBM Thinkpad T23.
Same problem irrespective of the combination of values of the values of the
following yenta_socket parameters:
parm: disable_clkrun:If PC card doesn't function properly, please try
this
Interestingly, it seems that pccard slot 1 produces the above errors,
however pccard slot 0 works.
BIOS PCI Interrupt automatic vs manual doesn't seem to have any
appreciable effect.
Slot 0 maps PCI devices 03:00.[012]
Slot 1 maps PCI devices 07:00.[012]
03:00.0 USB Controller: NEC
AplayDevices:
List of PLAYBACK Hardware Devices
card 0: I82801CAICH3 [Intel 82801CA-ICH3], device 0: Intel ICH [Intel
82801CA-ICH3]
Subdevices: 1/1
Subdevice #0: subdevice #0
Architecture: i386
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp',
'/dev/snd/by-path',
** Attachment added: AlsaDevices.txt
http://launchpadlibrarian.net/39264229/AlsaDevices.txt
--
jaunty-regression: Verizon (qualcomm) PC5750 PCMCIA card isn't recognized after
upgrade to JJ from HH
https://bugs.launchpad.net/bugs/397242
You received this bug notification because you are a
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/39264235/BootDmesg.txt
--
jaunty-regression: Verizon (qualcomm) PC5750 PCMCIA card isn't recognized after
upgrade to JJ from HH
https://bugs.launchpad.net/bugs/397242
You received this bug notification because you are a
** Attachment added: ArecordDevices.txt
http://launchpadlibrarian.net/39264230/ArecordDevices.txt
--
jaunty-regression: Verizon (qualcomm) PC5750 PCMCIA card isn't recognized after
upgrade to JJ from HH
https://bugs.launchpad.net/bugs/397242
You received this bug notification because you
** Attachment added: Card0.Amixer.values.txt
http://launchpadlibrarian.net/39264236/Card0.Amixer.values.txt
--
jaunty-regression: Verizon (qualcomm) PC5750 PCMCIA card isn't recognized after
upgrade to JJ from HH
https://bugs.launchpad.net/bugs/397242
You received this bug notification
** Attachment added: Card0.Codecs.codec97.0.ac97.0.0.txt
http://launchpadlibrarian.net/39264239/Card0.Codecs.codec97.0.ac97.0.0.txt
--
jaunty-regression: Verizon (qualcomm) PC5750 PCMCIA card isn't recognized after
upgrade to JJ from HH
https://bugs.launchpad.net/bugs/397242
You received
** Attachment added: Card0.Codecs.codec97.0.ac97.0.0.regs.txt
http://launchpadlibrarian.net/39264241/Card0.Codecs.codec97.0.ac97.0.0.regs.txt
--
jaunty-regression: Verizon (qualcomm) PC5750 PCMCIA card isn't recognized after
upgrade to JJ from HH
https://bugs.launchpad.net/bugs/397242
You
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/39264246/CurrentDmesg.txt
--
jaunty-regression: Verizon (qualcomm) PC5750 PCMCIA card isn't recognized after
upgrade to JJ from HH
https://bugs.launchpad.net/bugs/397242
You received this bug notification because you are a
** Attachment added: Lspci.txt
http://launchpadlibrarian.net/39264251/Lspci.txt
--
jaunty-regression: Verizon (qualcomm) PC5750 PCMCIA card isn't recognized after
upgrade to JJ from HH
https://bugs.launchpad.net/bugs/397242
You received this bug notification because you are a member of
** Attachment added: Lsusb.txt
http://launchpadlibrarian.net/39264257/Lsusb.txt
--
jaunty-regression: Verizon (qualcomm) PC5750 PCMCIA card isn't recognized after
upgrade to JJ from HH
https://bugs.launchpad.net/bugs/397242
You received this bug notification because you are a member of
** Attachment added: PciMultimedia.txt
http://launchpadlibrarian.net/39264258/PciMultimedia.txt
--
jaunty-regression: Verizon (qualcomm) PC5750 PCMCIA card isn't recognized after
upgrade to JJ from HH
https://bugs.launchpad.net/bugs/397242
You received this bug notification because you are
** Attachment added: ProcCpuinfo.txt
http://launchpadlibrarian.net/39264259/ProcCpuinfo.txt
--
jaunty-regression: Verizon (qualcomm) PC5750 PCMCIA card isn't recognized after
upgrade to JJ from HH
https://bugs.launchpad.net/bugs/397242
You received this bug notification because you are a
** Attachment added: ProcInterrupts.txt
http://launchpadlibrarian.net/39264260/ProcInterrupts.txt
--
jaunty-regression: Verizon (qualcomm) PC5750 PCMCIA card isn't recognized after
upgrade to JJ from HH
https://bugs.launchpad.net/bugs/397242
You received this bug notification because you
** Attachment added: ProcModules.txt
http://launchpadlibrarian.net/39264262/ProcModules.txt
--
jaunty-regression: Verizon (qualcomm) PC5750 PCMCIA card isn't recognized after
upgrade to JJ from HH
https://bugs.launchpad.net/bugs/397242
You received this bug notification because you are a
** Attachment added: UdevDb.txt
http://launchpadlibrarian.net/39264265/UdevDb.txt
--
jaunty-regression: Verizon (qualcomm) PC5750 PCMCIA card isn't recognized after
upgrade to JJ from HH
https://bugs.launchpad.net/bugs/397242
You received this bug notification because you are a member of
** Attachment added: UdevLog.txt
http://launchpadlibrarian.net/39264267/UdevLog.txt
--
jaunty-regression: Verizon (qualcomm) PC5750 PCMCIA card isn't recognized after
upgrade to JJ from HH
https://bugs.launchpad.net/bugs/397242
You received this bug notification because you are a member of
** Attachment added: WifiSyslog.gz
http://launchpadlibrarian.net/39264269/WifiSyslog.gz
** Changed in: linux (Ubuntu)
Status: Incomplete = New
** Tags added: apport-collected
--
jaunty-regression: Verizon (qualcomm) PC5750 PCMCIA card isn't recognized after
upgrade to JJ from HH
I have a further issue with this since I upgraded from jaunty to karmic.
I now see my zfs zpool component partitions in this list. This makes no
sense.
Paritions that are part of md lvm volumes aren't presented, neither
should zpool components.
If I click on a zfs partition then it tries to
Just upgraded, jaunty to karmic, and started getting this email:
*** glibc detected *** /usr/lib/sysstat/sadc: double free or corruption
(!prev): 0x014ed4d0 ***
# apt-cache policy sysstat
sysstat:
Installed: 9.0.3-2ubuntu1
Candidate: 9.0.3-2ubuntu1
Version table:
***
Just upgraded, jaunty to karmic, and started getting this email:
*** glibc detected *** /usr/lib/sysstat/sadc: double free or corruption
(!prev): 0x014ed4d0 ***
# apt-cache policy sysstat
sysstat:
Installed: 9.0.3-2ubuntu1
Candidate: 9.0.3-2ubuntu1
Version table:
***
Since cd / find . -depth -print|cpio -pdmu0 is my standard partition
replication command, this bug has just caused me enough grief to have
rebuild a system, rather than just the disk to disk copy that I intended
to move the root file system around.
--
cpio 2.9 drops directory permissions and
So this bug is still present in karmic.
--
cpio 2.9 drops directory permissions and ownership
https://bugs.launchpad.net/bugs/214942
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
If Settings/Appearance/Paint Engine is Qt, then Graphite doesn't work.
If Settings/Appearance/Paint Engine is OpenGL, then Graphite does work.
--
graphite theme watch-recordings screen status icons fail to update
https://bugs.launchpad.net/bugs/501076
You received this bug notification because
dpkg -i mythbuntu-repos.deb.
Selected ppa 0.22.
aptitude update upgrade.
Changed frontend back to Graphite theme.
Watched Recordings page still doesn't update status icons.
So Graphite is definitely still broken.
$ apt-cache policy mythtv-theme-graphite
mythtv-theme-graphite:
Installed:
I pulled the diffs from svn, and applied them to my test Gr2 theme. No
Change, apart from fixing the things they fixed per the diffs.
I went into recordings-ui.xml, and for all imagetypes where name =~ m/off$/, I
changed alpha from 55 to 0.
When I move around the recordings page, I can now just
Public bug reported:
# lsb_release -rd
Description:Ubuntu 9.10
Release:9.10
# apt-cache policy mythtv-theme-graphite
mythtv-theme-graphite:
Installed: 1:0.22.0~zrc1-0ubuntu2
Candidate: 1:0.22.0~zrc1-0ubuntu2
Version table:
*** 1:0.22.0~zrc1-0ubuntu2 0
500
manually, especially as I have to negotiate
a transparent proxy and local debmirror redirection?
--
Scott Merrilees
On Tue, Dec 29, 2009 at 05:08, Mario Limonciello supe...@ubuntu.com wrote:
Hi Scott:
Thanks for the report. It looks like there has actually been some
activity upstream
between recorded shows, I was
able to see some slight brightness change on some parts of some icons,
so I'm wondering if it is a theme issue, or a graphics card issue,
although since it happened initially on two totally different
machines, I leaning away from a hardware issue.
--
Scott Merrilees
I too am getting the problem what I can get an autologin to happen first
time, but not subsequent times.
I previously had a custom.conf setup in 9.04 and had updated
custome.conf.9.10 in an attempt to fix.
# cat custom.conf.9.04
[daemon]
AutomaticLoginEnable=true
AutomaticLogin=mythtv
Also, if I didn't add the 'exit' to the end of the .gnomerc then after I
terminated mythtv, a normal gnome desktop would start up.
--
gdm ignores timed/auto login on all but first greeter run
https://bugs.launchpad.net/bugs/463314
You received this bug notification because you are a member of
I, like Malcolm, also have this issue building my debmirror for karmic.
Debmirror box is running jaunty, debmirror version 20070123ubuntu3.
--
missing main/debian-installer in repo causes debmirror to fail
https://bugs.launchpad.net/bugs/34376
You received this bug notification because you are a
With a latest patched karmic, if I copy a dsa key in as .ssh/identity,
then try to ssh to another host, then I get a gui request box asking for
they passphrase, and I then get connected to the host. So it seems like
it works for me.
--
gnome-keyring-daemon returns Agent admitted failure to sign
You don't need to restart apache, just the move is sufficient. Thanks.
--
Cannot use both zlib.output_compression and output_handler together!!
https://bugs.launchpad.net/bugs/329053
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5
You don't need to restart apache, just the move is sufficient. Thanks.
--
Cannot use both zlib.output_compression and output_handler together!!
https://bugs.launchpad.net/bugs/329053
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
68 matches
Mail list logo
