Looking good on 18.04.1 LTS Desktop. I have installed the patch from
comment #23 and the network icon now appears consistently on both the
status bar and the status menu.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
According to https://gitlab.gnome.org/GNOME/gnome-shell/issues/140 this
is fixed in Gnome Shell 3.30.1 & 3.28.4. Any chance of getting 3.28.4
(or the fix) in 18.04 LTS desktop?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I have an 18.04.2 desktop installation running grub2 2.02-2ubuntu8.12,
which is still pausing for 30 seconds at the grub menu on every boot.
The system is UEFI and running secure boot, with nVidia binary drivers
if that matters? The disk is an NVMe drive with two partitions. The
first is
*** This bug is a duplicate of bug 1741934 ***
https://bugs.launchpad.net/bugs/1741934
** This bug has been marked a duplicate of bug 1741934
Kernel trace with xenial 4.4 (4.4.0-108.131, Candidate kernels for PTI fix)
--
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 1741934 ***
https://bugs.launchpad.net/bugs/1741934
** This bug has been marked a duplicate of bug 1741934
Kernel trace with xenial 4.4 (4.4.0-108.131, Candidate kernels for PTI fix)
--
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 1741934 ***
https://bugs.launchpad.net/bugs/1741934
** This bug has been marked a duplicate of bug 1741934
Kernel trace with xenial 4.4 (4.4.0-108.131, Candidate kernels for PTI fix)
--
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 1741934 ***
https://bugs.launchpad.net/bugs/1741934
** This bug is no longer a duplicate of bug 1742330
Can't reboot, shutdown or suspend with 4.4.0-108
** This bug has been marked a duplicate of bug 1741934
Kernel trace with xenial 4.4
*** This bug is a duplicate of bug 1741934 ***
https://bugs.launchpad.net/bugs/1741934
** This bug is no longer a duplicate of bug 1742323
Meltdown Update Kernel doesnt boot
** This bug has been marked a duplicate of bug 1741934
Kernel trace with xenial 4.4 (4.4.0-108.131, Candidate
*** This bug is a duplicate of bug 1741934 ***
https://bugs.launchpad.net/bugs/1741934
** This bug is no longer a duplicate of bug 1742323
Meltdown Update Kernel doesnt boot
** This bug has been marked a duplicate of bug 1741934
Kernel trace with xenial 4.4 (4.4.0-108.131, Candidate
Having read through the Debian notes it appears unlikely that 2.40 will
ever compile and work against the newer OCaml library in 16.04 LTS.
However, 2.48 does fine. There was some question about whether this
would work in 14.04 LTS. I have carried out a test using a 14.04 LTS
server and a 16.04
It appears this was fixed with the patch
https://attachments.samba.org/attachment.cgi?id=9882 in Samba bug 10524
(https://bugzilla.samba.org/show_bug.cgi?id=10524) against their 4.1
code base. Is there any chance in getting this applied to the 14.04 LTS
Samba release or the Utopic release
It appears this was fixed with the patch
https://attachments.samba.org/attachment.cgi?id=9882 in Samba bug 10524
(https://bugzilla.samba.org/show_bug.cgi?id=10524) against their 4.1
code base. Is there any chance in getting this applied to the 14.04 LTS
Samba release or the Utopic release
I've given up with my solution in #9 as it did not work. I'm still
using 14.04 LTS systems and now employ the following fix instead:
service isc-dhcp-server stop
setfacl -dm u:dhcpd:rwx /var/lib/dhcp
setfacl -m u:dhcpd:rwx /var/lib/dhcp
service isc-dhcp-server start
Note: For this to work you
Is there any chance of a backport to 14.04 LTS for this patch?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1281588
Title:
Disk standby timer is broken
To manage notifications about this bug go
Rather annoyingly, this still seems to be present in 14.04 LTS after all
these years! The following seems to fix it (at least until the isc-
dhcp-server package gets updated):
- Stop the DHCP server (service isc-dhcp-server stop)
- chown -R dhcpd:dhcpd /var/lib/dhcp
- Edit
In case it assists when this bug gets triaged, I've repeated my build
today with Samba 2:4.1.6+dfsg-1 from Jessie and this bug is also not
present in the 4.1.6 release, which includes security fixes over 4.1.5.
--
You received this bug notification because you are a member of Ubuntu
Server Team,
In case it assists when this bug gets triaged, I've repeated my build
today with Samba 2:4.1.6+dfsg-1 from Jessie and this bug is also not
present in the 4.1.6 release, which includes security fixes over 4.1.5.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
As this bug stops an other application using the Kerberos details stored
in the Samba directory, it is quite a show-stopper for the Trusty
release. Is there anything I can tag this bug with or anyone I should
notify in an attempt to get 4.1.5 pulled from Jessie for the Trusty
release?
--
You
As this bug stops an other application using the Kerberos details stored
in the Samba directory, it is quite a show-stopper for the Trusty
release. Is there anything I can tag this bug with or anyone I should
notify in an attempt to get 4.1.5 pulled from Jessie for the Trusty
release?
--
You
Public bug reported:
To reproduce this bug, carry out the following:
Install a fresh Trust Tahr 14.04 AMD64 development build in a (KVM)
virtual machine as a basic server.
Install the samba (2:4.1.3+dfsg-2ubuntu3) and bind9 packages.
Provision an Active Directory Domain with the following
I've just upgraded Samba to 2:4.1.5+dfsg-1 from the Debian Jessie
repository. This also forced the following updates:
2014-03-10 17:13:00 upgrade python-samba:amd64 2:4.1.3+dfsg-2ubuntu3
2:4.1.5+dfsg-1
2014-03-10 17:13:00 upgrade samba-dsdb-modules:amd64 2:4.1.3+dfsg-2ubuntu3
2:4.1.5+dfsg-1
Public bug reported:
To reproduce this bug, carry out the following:
Install a fresh Trust Tahr 14.04 AMD64 development build in a (KVM)
virtual machine as a basic server.
Install the samba (2:4.1.3+dfsg-2ubuntu3) and bind9 packages.
Provision an Active Directory Domain with the following
I've just upgraded Samba to 2:4.1.5+dfsg-1 from the Debian Jessie
repository. This also forced the following updates:
2014-03-10 17:13:00 upgrade python-samba:amd64 2:4.1.3+dfsg-2ubuntu3
2:4.1.5+dfsg-1
2014-03-10 17:13:00 upgrade samba-dsdb-modules:amd64 2:4.1.3+dfsg-2ubuntu3
2:4.1.5+dfsg-1
apport information
** Attachment added: CurrentDmesg.txt
https://bugs.launchpad.net/bugs/936190/+attachment/3786226/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/936190
apport information
** Attachment added: ProcEnviron.txt
https://bugs.launchpad.net/bugs/936190/+attachment/3786229/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/936190
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.launchpad.net/bugs/936190/+attachment/3786228/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/936190
apport information
** Attachment added: UdevLog.txt
https://bugs.launchpad.net/bugs/936190/+attachment/3786234/+files/UdevLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/936190
Title:
As requested the test was re-run in the latest Saucy daily. The results
are attached above. The issue still exists if a mass storage USB device
is connected to the nForce 590 USB controller. If only HID devices are
attached then they all power off correctly at shutdown.
--
You received this
apport information
** Attachment added: UdevDb.txt
https://bugs.launchpad.net/bugs/936190/+attachment/3786233/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/936190
Title:
apport information
** Attachment added: PulseList.txt
https://bugs.launchpad.net/bugs/936190/+attachment/3786232/+files/PulseList.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/936190
Title:
apport information
** Tags added: apport-collected saucy
** Description changed:
Following on from bug #787590, it appears that with the release of the
3.0.0-16 kernel a regression has occurred and the problem is present
again. I thought the patch had been adopted into the mainstream
apport information
** Attachment added: Lspci.txt
https://bugs.launchpad.net/bugs/936190/+attachment/3786227/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/936190
Title:
nForce
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.launchpad.net/bugs/936190/+attachment/3786230/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: CRDA.txt
https://bugs.launchpad.net/bugs/936190/+attachment/3786225/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/936190
Title:
nForce
apport information
** Attachment added: WifiSyslog.txt
https://bugs.launchpad.net/bugs/936190/+attachment/3786235/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/936190
apport information
** Attachment added: ProcModules.txt
https://bugs.launchpad.net/bugs/936190/+attachment/3786231/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/936190
apport information
** Attachment added: BootDmesg.txt
https://bugs.launchpad.net/bugs/936190/+attachment/3786224/+files/BootDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/936190
Title:
Further information has come to light today. I'm now running 3.2.0-29
(PAE) on the same platform. This does not exhibit the USB controller
power shut-down bug unless as mass storage device is connected.
My USB memory card reader or a USB stick left connected to the
motherboard at kernel
All was well in Precise (12.04 LTS) for a while. Up to and including
3.2.0-23 correctly powered off the USB controller at shutdown. Now from
-24 (including -25) the bug has appeared.
Should I file another bug for Precise or update this one in some way now
the problem is present here too? I'm
Just experienced the same issue using the daily build of 12.04 LTS (32
bit) released today. Seemed to occur while doing a background data
update for the Basingstoke, England weather from Yahoo.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Also still present in this morning's update:
Linux custard 3.0.0-17-generic #30-Ubuntu SMP Thu Mar 8 17:34:21 UTC
2012 i686 athlon i386 GNU/Linux
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/936190
Just to let you know that this regression is also present on the latest
security release of the kernel this morning:
Linux custard 3.0.0-16-generic #29-Ubuntu SMP Tue Feb 14 12:49:42 UTC
2012 i686 athlon i386 GNU/Linux
--
You received this bug notification because you are a member of Ubuntu
The last kernel running on this machine was:
Linux custard 3.0.0-15-generic #26-Ubuntu SMP Fri Jan 20 15:59:53 UTC
2012 i686 athlon i386 GNU/Linux
When shutdown this previous kernel correctly powers down the USB ports.
So, it looks like the quirk for the 590 chipset is still needed. Is
there
Public bug reported:
Following on from bug #787590, it appears that with the release of the
3.0.0-16 kernel a regression has occurred and the problem is present
again. I thought the patch had been adopted into the mainstream kernel
but for some reason it does not appear to have made it into the
** Bug watch added: Linux Kernel Bug Tracker #35032
http://bugzilla.kernel.org/show_bug.cgi?id=35032
** Also affects: linux via
http://bugzilla.kernel.org/show_bug.cgi?id=35032
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of
OK, I spoke too early in my last post. The machine was working fine all
day Thursday with the official 3.0.0-13-generic kernel. Then when I
booted it on Friday morning, lightdm displayed fine but the UI froze
logging into any account with a background bitmap and mouse cursor.
Unity did not
Having upgraded to the 3.0.0-13-generic #22-Ubuntu kernel (without the
RS690M patch) after the security release a couple of days ago, I realise
that there is really no improvement on my HP Compaq 6715b whether I run
Alex's patch or not. The graphics are very lagged in both Unity 3D and
2D.
For
No, as far as I can see from the code modifications AMD made in the
patches this will only fix the RS690M. In terms of installing my test
kernel, I have a vanilla Oneiric i386 desktop installation and then ran
dpkg -i on each of the three .deb files I created in turn. After a
reboot things
Patches in https://bugs.freedesktop.org/show_bug.cgi?id=37679 (posts 81
and 82) by Alex Deucher. Please report back how you get on as I'm keen
to get Canonical to adopt this into the Oneiric kernel as it is a bad
regression.
--
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 755791 ***
https://bugs.launchpad.net/bugs/755791
** This bug has been marked a duplicate of bug 755791
[RS690M] No 3d acceleration in Radeon X1200 with new Gallium r300 / 3d
drivers in 11.04
--
You received this bug notification because you are a
The performance of my HP Compaq 6715b with an RS690M has regressed so
badly in Oneiric that I've been forced into action. Based on the work
done in Bug #874784 and the patches provided by Alex Deucher in
https://bugs.freedesktop.org/show_bug.cgi?id=37679 I have built my first
kernel. It builds
Generic headers for the above kernel
** Attachment added: linux-headers-3.0.0-13_3.0.0-13.22_all.deb
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/755791/+attachment/2585692/+files/linux-headers-3.0.0-13_3.0.0-13.22_all.deb
--
You received this bug notification
i386 headers for above kernel
** Attachment added: linux-headers-3.0.0-13-generic_3.0.0-13.22_i386.deb
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/755791/+attachment/2585702/+files/linux-headers-3.0.0-13-generic_3.0.0-13.22_i386.deb
** Tags added: kernel-graphics
I can confirm I have tested the X-Swat PPA on an AMD Radeon X1200 in an
HP Compaq 6715b and it does not fix the problem. With the PPA glxgears
still struggles to make 13 FPS and the whole Unity interface lags
terribly. Please see my comment above
(https://bugs.launchpad.net/ubuntu/+source/linux-
Could you clarify how updating nVidia dirvers solved a performance
problem with an AMD Radion X1200 card? I am suffering the same issue
with Oneiric on an Compaq 6715b laptop with the same graphics card.
Natty Unity 3D flew. Even typing this report in Launchpad is causing a
substantial lag in
Kernel bug with the IRQ handling in the Radeon driver. See
https://bugs.freedesktop.org/show_bug.cgi?id=37679 for the two patches
that fix this.
** Bug watch added: freedesktop.org Bugzilla #37679
http://bugs.freedesktop.org/show_bug.cgi?id=37679
** Package changed: unity (Ubuntu) =
** Tags added: kernel-graphics
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/874784
Title:
Unity 3D too slow (Oneiric)
To manage notifications about this bug go to:
A year has passed since this packaging issue was solved in the Debian
repositories. How can we go about getting it included in the 10.04 LTS?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openldap in Ubuntu.
A year has passed since this packaging issue was solved in the Debian
repositories. How can we go about getting it included in the 10.04 LTS?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/82853
Tested and also working correctly on today's 2.6.38-11.48 proposed
kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/787590
Title:
USB power not turned off using nForce 590 SLI chipset
To
Thanks Julian. Following the instructions at
https://wiki.ubuntu.com/Testing/EnableProposed I have upgraded to kernel
2.6.38-11.47, which correctly shuts the power down to USB devices at
shutdown.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Sadly today's security update for the kernel (2.6.38-10.46) has knocked
out this patch and the problem is back. Is there any chance you could
build another image based on this kernel? If not, do you have a diff I
can apply to the kernel package and I'll have a go at building one in my
PPA?
--
Thanks, that's certainly a work-around. It does mean that the latest
set of security patches won't be in the running kernel then. Does the
fact that a kernel has just been released mean the new proposed one
including this patch will be built in the next day or so?
--
You received this bug
Thanks for letting me know. Is there a way I can see when it is
proposed to test it there or will you update the bug when it gets
included?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/787590
Sorry for the delay, I have been away from my nForce 590 based machine
for the last few days. I have now tested your kernel and it fixes this
regression with no side-effects that I could see. USB devices are
correctly powered off when the system shuts down.
Does this mean we will see this in an
Thanks, that's excellent news and fully explains why I am not suffering
difficulties with the Natty kernel. What do I need to do to get that
patch included in the Natty kernel to fix this regression?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
* not = now in the previous post. Sorry for this confusing typo!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/787590
Title:
USB power not turned off using nForce 590 SLI chipset
--
ubuntu-bugs
** Bug watch added: Linux Kernel Bug Tracker #35032
http://bugzilla.kernel.org/show_bug.cgi?id=35032
** Also affects: linux via
http://bugzilla.kernel.org/show_bug.cgi?id=35032
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of
Thanks, that's good news. As a humble user (with a fair degree of
hardware and development knowledge) I am not on personal terms with any
members of the kernel team. I am guessing their group is subscribed to
this bug? If so, could anyone assist me in getting this patch moved
into pre-stable
Public bug reported:
I have a Gigabyte GA-M59SLI-S5 motherboard with BIOS F9c upon which I am
now running Natty (11.04). Devices like the keyboard (Microsoft Comfort
Curve) and mouse (Microsoft Wheel Mouse Optical) connected to the USB
bus are no longer powered off at shutdown.
No hardware
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/787590
Title:
USB power not turned off using nForce 590 SLI chipset
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Having dug a little deeper I have found the following kernel patch:
http://www.spinics.net/lists/linux-usb/msg35958.html
Can anyone walk me through finding out if it was included in 2.6 kernel
releases up until Natty? If so, I will then need to work out why it was
removed for Natty and if it
Tested and confirmed working on an Acer Aspire Revo 3610 from the
proposed repository with kernel 2.6.38-9.43.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/662288
Title:
rt3090: freeze on module
Appears to be fixed upstream in http://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=611704. Can someone pull it over to the Ubuntu
repositories?
** Bug watch added: Debian Bug tracker #611704
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=611704
** Also affects: simplepie (Debian) via
*** This bug is a duplicate of bug 777394 ***
https://bugs.launchpad.net/bugs/777394
Appears to be fixed upstream in http://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=611704. Can someone pull it over to the Ubuntu
repositories?
** Bug watch added: Debian Bug tracker #611704
As a temporary work-around, try the following:
wget
http://ftp.debian.org/debian/pool/main/s/simplepie/libphp-simplepie_1.2-3_all.deb
sudo dpkg -i libphp-simplepie_1.2-3_all.deb
sudo apt-get install dokuwiki (assuming this is the package that requires
simplepie in your installation)
All
From Maverick (10.10) Desktop 32-bit with a GeForce 7300GT (which
doesn't support VDPAU) I get the following visiting www.youtube.com and
clicking on the first video link displayed:
$ chromium-browser
[3034:3077:1088577600:ERROR:chrome/browser/sync/engine/all_status.cc(114)]
Unrecognized Syncer
** Attachment added: cupsd.conf
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/494141/+attachment/1764561/+files/cupsd.conf
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
Sorry for the two posts, I couldn't work out how to attach more than one
file to a comment! cupsd.conf and smb.conf as requested. IP addresses
and domain names have been changed as per RFC1166 and RFC2606
respectively to protect privacy.
** Attachment added: smb.conf
** Attachment added: cupsd.conf
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/494141/+attachment/1764561/+files/cupsd.conf
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/494141
Title:
Sorry for the two posts, I couldn't work out how to attach more than one
file to a comment! cupsd.conf and smb.conf as requested. IP addresses
and domain names have been changed as per RFC1166 and RFC2606
respectively to protect privacy.
** Attachment added: smb.conf
*** This bug is a duplicate of bug 650525 ***
https://bugs.launchpad.net/bugs/650525
Can be fixed by running:
sudo apt-get install ubuntu-extras-keyring
As far as I can tell it was only omitted from the 10.10 RC builds. The
release versions seem fine in my limited experience so far.
--
Confirmed as still being an issue on a fresh installation of Maverick
(10.10) RC AM64 server.
--
dhcp3-server launches before upstart brings all interface, thus failing to start
https://bugs.launchpad.net/bugs/580319
You received this bug notification because you are a member of Ubuntu
Server
As another proposed workaround, I have found that editing /etc/init/rc-
sysinit.conf to change the line:
start on filesystem and net-device-up IFACE=lo
to:
start on filesystem and net-device-up IFACE=br0
also appears to produce the desired result by delaying running of legacy
*** This bug is a duplicate of bug 580319 ***
https://bugs.launchpad.net/bugs/580319
** This bug has been marked a duplicate of bug 580319
dhcp3-server launches before upstart brings all interface, thus failing to
start
* You can subscribe to bug 580319 by following this link:
Confirmed as still being an issue on a fresh installation of Maverick
(10.10) RC AM64 server.
--
dhcp3-server launches before upstart brings all interface, thus failing to start
https://bugs.launchpad.net/bugs/580319
You received this bug notification because you are a member of Ubuntu
Bugs,
As another proposed workaround, I have found that editing /etc/init/rc-
sysinit.conf to change the line:
start on filesystem and net-device-up IFACE=lo
to:
start on filesystem and net-device-up IFACE=br0
also appears to produce the desired result by delaying running of legacy
*** This bug is a duplicate of bug 580319 ***
https://bugs.launchpad.net/bugs/580319
** This bug has been marked a duplicate of bug 580319
dhcp3-server launches before upstart brings all interface, thus failing to
start
* You can subscribe to bug 580319 by following this link:
It might be worth some further consideration if Chromium becomes the
default browser in Maverick (10.10). However, you guessed correctly as
here is the output of a ping:
gu...@custard:~$ ping www.google.com
ping: icmp open socket: Permission denied
--
chromium-browser can't open when the guest
I have also noticed this issue in guest sessions on the Lucid 32-bit
Desktop installation. When attempting to run Chromium from a terminal
the following output is given:
gu...@custard:~$ chromium-browser
Failed to move to new PID namespace: Operation not permitted
The only workaround I have
I've just pulled the zaptel package from the repositories in Jaunty and
received 1:1.4.11~dfsg-3ubuntu1. This refuses to build because of the
issue reported in this bug on the current 2.6.28-17-server kernel.
After applying the patch from http://svn.debian.org/viewsvn/*checkout
Hi Yannick,
I've installed Ekiga 3.2.6~ppa~jaunty1 from your PPA as requested and
re-tested. There's still no indication anywhere of voice mail. I'm
still not sure where I should see it in the 3.2 code stream but it's not
on the status bar (next to the signal strength indicator), in the call
** Attachment added: SIP trace of MWI on Intrepid and Jaunty
http://launchpadlibrarian.net/34253496/SIP.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/34253497/Dependencies.txt
** Attachment added: ProcMaps.txt
Public bug reported:
Binary package hint: ekiga
When using Ekiga 2.0.12 from Intrepid with Asterisk, an extension with
new voice mail waiting shows a count of the messages waiting in the
status bar at the bottom of the window. However when upgraded to Ekiga
3.2.0 on Jaunty there is no longer
Public bug reported:
Binary package hint: ubuntu-mid-default-settings
After a clean Ubuntu MID installation from the Karmic netboot image no
errors are generated but the GUI fails to start upon reboot.
The script /etc/init.d/ubuntu-mid-default-settings calls the Upstart
start, stop and status
@Loïc: Thanks for letting me know the status of the MID build. I
wonder whether it should be removed from the list of options on the
netboot image if it isn't supported in Karmic, perhaps?
I'm not sure whether the xfce4-panel removal is an issue or not. As you
say the
I've tested the new 1.144 package by a complete rebuild of the test
machine from the netboot image. As before, the installation succeeds
without error. However after the initial Ubuntu splash it again drops
to a text login prompt. Logging in I find that the ubuntu-mid package
is not installed
Netboot issue confirmed fixed in
http://archive.ubuntu.com/ubuntu/dists/karmic/main/installer-i386/current/images/netboot/netboot.tar.gz
version 20081029ubuntu70 dated 17th October, 2009. The network card
used for the test was an embedded Intel Corporation 82557/8/9/0/1
Ethernet Pro 100 (rev 09).
Public bug reported:
I've recently built an Ubuntu MID machine from the Karmic netboot image
(http://archive.ubuntu.com/ubuntu/dists/karmic/main/installer-i386/current/images/netboot/netboot.tar.gz)
version 20081029ubuntu70. Although the installation appears to complete
successfully upon reboot
Just to check, as my original bug (#445522) was for the Karmic netboot
image, that the changes made here will get rolled into that for release
too?
--
e100_request_firmware fails with Karmic alternate cd (20091014.2).
https://bugs.launchpad.net/bugs/451872
You received this bug notification
1 - 100 of 118 matches
Mail list logo
