I think this is a dupe of bug 1274947.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1382190
Title:
LXCs assigned IPs by MAAS DHCP lack DNS PTR entries
To manage notifications about
I don't think #3 is that bad actually; remember that's how we used to do
it before static IP days so it's tried and tested (although admittedly
the DNS was in place by the time commissioning ended).
#2 is also good, but you have to calculate which lines to generate based
on the netmask.
I'd go
On Thursday 23 Oct 2014 15:40:51 you wrote:
Andres and I have discussed this further, and he pointed out that the
LXCs can take a *long* time to start. That would be sufficient time for
us to parse the leases file and update the DNS with a PTR for the new
node (option #3).
I've tested this
I am interested as to how you got into the situation of needing to enter
IP information for your cluster interface. When a cluster controller
registers itself on the region, it transmits these details automatically
so that you don't need to configure them.
** Changed in: maas
Status:
** Changed in: maas
Status: Fix Committed = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1382266
Title:
maas-proxy fails to start on freshly installed MAAS
To manage
Adding an ubuntu task as I think this will mostly happen in the
packaging.
** Also affects: maas (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
** Also affects: maas (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1382774
Title:
Postgresql installation for MAAS fails on
This is a packaging issue; it detects the IP to configure for
DEFAULT_MAAS_URL and then pops up a message about using dpkg-reconfigure
if it's wrong.
It could do better, is a blanket ignoring of wlan0 appropriate? Or
maybe ignore it only if eth* is present.
** Also affects: maas (Ubuntu)
** Changed in: maas (Ubuntu)
Status: Confirmed = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1377964
Title:
maas-proxy logrotate permission denied
To manage
On Thursday 06 Nov 2014 11:22:56 you wrote:
Could packaging detect whether the cluster and region are on the same
machine and if so use lo?
Kind of - if you're installing the all-in-one meta maas package it *could*,
however it still needs an IP address, and it doesn't matter if it's the lo or
** Changed in: maas
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas-enlist in Ubuntu.
https://bugs.launchpad.net/bugs/1081660
Title:
If maas-enlist fails to reach a DNS server, the
** Changed in: maas
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1087183
Title:
MaaS cloud-init configuration specifies
** Changed in: maas
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1382266
Title:
maas-proxy fails to start on freshly installed MAAS
To
** Changed in: maas
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1382190
Title:
LXCs assigned IPs by MAAS DHCP lack DNS PTR entries
To
** Changed in: maas
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-django in Ubuntu.
https://bugs.launchpad.net/bugs/1365130
Title:
django-admin prints spurious messages to stdout,
** Changed in: maas
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1350103
Title:
No support for armhf/keystone architecture
To manage
** Changed in: maas
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1337437
Title:
[SRU] maas needs utopic support
To manage notifications
** Changed in: maas
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openipmi in Ubuntu.
https://bugs.launchpad.net/bugs/1321885
Title:
IPMI detection and automatic setting fail in ubuntu
** Changed in: maas
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1379144
Title:
maas-proxy package won't install when upgrading from
** Changed in: maas
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to curtin in Ubuntu.
https://bugs.launchpad.net/bugs/1378910
Title:
Call the install log 'install log' rather than 'curtin
** Changed in: maas
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to freeipmi in Ubuntu.
https://bugs.launchpad.net/bugs/1364617
Title:
ipmipower returns a zero exit status when password
** Changed in: maas
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1367455
Title:
MAC address for node's IPMI is reversed looked up to
** Changed in: maas
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1373580
Title:
[SRU] Glen m700 cartridge list as ARM64/generic after
Packaging bug.
** Also affects: maas (Ubuntu)
Importance: Undecided
Status: New
** Changed in: maas
Status: New = Triaged
** Changed in: maas
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Not a bug in Soyuz (any more) as the Gutsy partner (commercial) archive
is now present. Michael is still investigating update-manager for any
issues.
** Changed in: soyuz
Status: Incomplete = Fix Released
--
Error during update Gutsy Gibbon 7.10 because of missing commercial repository
Thanks for the detailed instructions.
The culprit appears to be yenta_socket!
--
Powertop reports huge number of wakeups under gutsy and drains battery
https://bugs.launchpad.net/bugs/145377
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
Does it make difference to have the modules loaded in boot time or
after?
Not for me.
Does it make difference if you unload them later?
If I unload yenta_socket the wakeups stays high.
Does it happen every time?
Yes.
Thanks, HTH!
J.
--
Powertop reports huge number of wakeups under gutsy
Well I can't re-create this now either :/
The only difference is that I am using 1.9rc1-1 now as that is what I upgraded
to just now to test this out. However, I know I was not the only one with the
issue yesterday, so it might be some particular data that triggers the bug
rather than all
Public bug reported:
Binary package hint: bzr
I tried 1.9rc1 from the bzr-beta-ppa and when pushing a branch to
Launchpad it will stall after 1/4 done and promptly eats RAM like
there's no tomorrow - I killed it when it got to 800 meg.
Downgrading to 1.8-1 works ok.
** Affects: bzr (Ubuntu)
** Also affects: bzr
Importance: Undecided
Status: New
** Changed in: bzr (Ubuntu)
Status: New = Invalid
--
1.9rc1 can't push to Launchpad
https://bugs.launchpad.net/bugs/293679
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
On Tuesday 04 November 2008 22:43:48 Andrew Bennetts wrote:
You are pushing via bzr+ssh, I assume?
Yep, sorry I should have mentioned that.
Did you get a backtrace in ~/.bzr.log when you killed it?
Yes:
Using saved push location: lp:~julian-edwards/launchpad/api_copy_packages
BTW, I'll carry on using 1.9rc1-1 and let you know as soon as the problem
happens again, if it does.
--
1.9rc1 can't push to Launchpad
https://bugs.launchpad.net/bugs/293679
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I am happy to re-confirm this, it happened to me this morning when I was
fighting to get Kubuntu on Intrepid to start up :)
** Changed in: xorg (Ubuntu)
Status: Incomplete = New
--
higher resolutions aren't recognized for external monitors after hotplugging
but after X start (Virtual is
Public bug reported:
Binary package hint: kdebase
From powertop:
20.3% ( 83.3) knotify4 : schedule_timeout (process_timeout)
17.6% ( 72.4) interrupt : [EMAIL PROTECTED]::00:02.0
14.8% ( 60.7) kwin : schedule_timeout (process_timeout)
10.3% ( 42.3)
I don't understand why you've marked this invalid. Is the presence of
desktop effects supposed to excuse the high number of wake-ups? That's
not a valid reason.
Regarding your driver, is it nvidia, configured with on-demand
interrupts? Intel doesn't have that luxury AFAIK.
--
powertop shows
On Tuesday 14 October 2008 12:44:32 Harald Sitter wrote:
Ok, let me put it this way. Do you really expect that playing Quake is
not going to raise the wakeup time? Desktop effects are basically the
same, just less wakeupish.
If it's sat there doing nothing, I don't expect it to keep re-drawing
Public bug reported:
Binary package hint: kdebase
This is a regression from KDE3 on Hardy. When restoring a session after
login, only one konsole window is restored, no matter how many I had
open in the saved session.
It also does not remember opened tabs in each window.
** Affects: kdebase
Confirming, this just bit me.
Since this is the default config for out-the-box Intrepid, this should
either be higher priority, or change the shipped config.
** Changed in: pinentry-qt4 (Ubuntu)
Status: New = Confirmed
--
[intrepid] Wrong passphrase message when correct one is entered -
Ok so I turned on show paint and show fps
First observation: If I change the screen's refresh rate, I see the
corresponding change in both the fps shown by kwin *and* the
wakeups/second.
Second observation: If I don't touch the mouse and have a static screen,
nothing is apparently getting
As requested:
http://www.alsa-
project.org/db/?f=ed4e480a831edbff00627848577a39cc6917c95b
** Changed in: linux (Ubuntu)
Status: Incomplete = New
--
Headset volume control doesn't change headset volume
https://bugs.launchpad.net/bugs/201391
You received this bug notification because you
Public bug reported:
Binary package hint: kdepim
Kmail bombs on startup with this error:
[EMAIL PROTECTED]:~$ kmail
ASSERT: s-parsed == false in file
/build/buildd/kde4libs-4.1.2/kdecore/kernel/kcmdlineargs.cpp, line 524
It was working fine until I updated my packages on Sunday 12th October.
Public bug reported:
Binary package hint: kdepim
On current Intrepid with KDE4 I get this:
[EMAIL PROTECTED]:~$ knotes
knotes(16517): Communication problem with knotes , it probably crashed.
Error message was: org.freedesktop.DBus.Error.NoReply : Did not receive a
reply. Possible causes
Something is seriously boogered:
[EMAIL PROTECTED]:~$ ps -fe|grep scim-panel-gtk|wc -l
121
After killing all those instances, knotes and kontact popped up.
--
knotes and kontact fail to start
https://bugs.launchpad.net/bugs/282666
You received this bug notification because you are a member of
Also happens for me, Dell D630 laptop (64 bit) with Intel GMA 965. I
just upgraded from Kubuntu Hardy to Intrepid so I've no idea if this is
KDE4 related.
It looks like DPMS is kicking in briefly. The laptop's screen stays on
while this happens.
I made it stable by using xrandr to a lower
These miraculously started working some time this week so I can't
directly test this any more.
However, I found another program that won't start, both before and after
removing scim. Here's the paste from my konsole:
$ gvim
/usr/bin/scim
long pause, nothing happens
Hit ctrl-c and:
^CICE
Colin
Sorry for the delay in replying - I've tried pwr_irqs_off=1 and it
doesn't help I'm afraid :(
--
Powertop reports huge number of wakeups and drains battery
https://bugs.launchpad.net/bugs/145377
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Bizarrely, this problem has now gone away for me. I've kept an eye on
powertop for the 2 days since it went and not once have I seen it
heading over 1000 wakeups per second unless I am doing something
intensive. There must have been an update that fixed it, but who knows
what given the huge
Also happens on Dell D630 using iwl3945.
--
wireless networking disappears in Hardy Heron Beta after waking up from suspend
or hiberante
https://bugs.launchpad.net/bugs/211135
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Unfortunately, this problem has started happening for me again :(
When I get some time, I'll try and unload some kernel modules and see if
I can pinpoint which is causing the problem.
exactt: the yenta_socket blacklisting fix only works on Gutsy.
--
Powertop reports huge number of wakeups and
acpi=noirq is working well for me (Dell D630 as in the second bug
comment)
Does this have any knock-on effects?
--
Powertop reports huge number of wakeups and drains battery
https://bugs.launchpad.net/bugs/145377
You received this bug notification because you are a member of Ubuntu
Bugs, which
Colin
Thanks very much for all the info. I had a look into my BIOS version,
saw that it was A01 and A08 is available. I excitedly upgraded but it's
not fixed this problem :(
I know absolutely nothing about DSDT so I am going to leave the
acpi=noirq on my menu.lst for now, I need my laptop
Hi there Colin
Jean-Baptiste is right, and I feel quite strongly that Won't Fix is an
inappropriate result to this bug. To quote a cliche, expecting my
granny to hack menu.lst or download a BIOS update or fix the DSDT is a
non-starter. The kernel should work properly on this particular type of
I just discovered that adding acpi=noirq has a rather unfortunate
consequence.
When resuming from suspend, my USB ports no longer work.
acpi=noirq can't really be considered a viable work around.
Cheers
J
--
Powertop reports huge number of wakeups and drains battery
Public bug reported:
Using the bzr team PPA to install bzrtools 1.3 on Hardy, I get this:
Preparing to replace bzrtools 1.2.0-1ubuntu3 (using
.../bzrtools_1.3.0-1~bazaar1~hardy1_all.deb) ...
Traceback (most recent call last):
File /usr/bin/pycentral, line 1813, in module
main()
File
I added acpi=noirq and removed quiet to watch the console during boot
and so far, three hours later, it's not gone into crazy mode. This has
happened before though where it didn't go wrong for a while, so I will
keep an eye on it.
[EMAIL PROTECTED]:~# dmesg|grep command
[0.00] Kernel
Colin, that was an interesting read on bug 177895.
I think that in those comments there are two separate issues:
1. People complaining about kernel IPI : Rescheduling interrupts
2. Some people noticing the larger interrupt count caused by the issue on this
bug report (possibly yenta_socket).
** Attachment added: top.log
http://launchpadlibrarian.net/13327735/top.log
--
Powertop reports huge number of wakeups and drains battery
https://bugs.launchpad.net/bugs/145377
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Attachment added: vmstat.log
http://launchpadlibrarian.net/13327739/vmstat.log
--
Powertop reports huge number of wakeups and drains battery
https://bugs.launchpad.net/bugs/145377
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Colin
acpi=noirq removed the problems but exactt above says he still had the
problem! Weird - the only difference in what we did was that I removed
quiet - I can't believe that would make any difference but I've seen
weirder things happen :)
I'll do some more experiments shortly and let you
I should add - kicking off means when it's actively backing-up
--
Keep is blocking some KDE apps when running
https://bugs.launchpad.net/bugs/208374
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Public bug reported:
Binary package hint: keep
On an up-to-date Hardy (although it happens on Gutsy too) when Keep
kicks off, it's totally blocking at least Konqueror and Kontact/Kmail -
they are not even repainting on the screen. When Keep finishes, they
spring back into life.
** Affects:
I had to add softcarrier=1 to my lirc_serial module options to get my
serial transmitter to work. Does this fix enable that by default, or do
we need another debconf option?
--
lirc_serial loads but does not work (Gutsy 7.10 + Hardy 8.04)
https://bugs.launchpad.net/bugs/182530
You received this
Sound works on my Latitude D630, but the volume control is still non-
linear. It starts very, very quiet until you get to about 70% and then
it SUDDENLY GETS VERY LOUD!
--
[gutsy] no sound on Dell Latitude D630/D830/Precision M4300/Vostro
1500/1700/Apple Aluminium iMac/Acer TM6292 pci id
Blacklisting yenta_socket and pcmcia does not fix this problem, it
merely averts it temporarily until some event happens that causes the
bad state again.
Is there any news on this? There's a kernel freeze in 10 days and I
would hate for this to be still a bug when Hardy is released (more the
the
Fix was cherry picked.
** Changed in: soyuz
Status: Fix Committed = Fix Released
--
PPA packages fail to upload but build successfully
https://bugs.launchpad.net/bugs/192713
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
The same problem is in Hardy (which I upgraded to last night as it
happens), I will open a new bug.
** Also affects: linux-source-2.6.24 (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- Powertop reports huge number of wakeups under gutsy and drains battery
+ Powertop
Output for powertop --dump on Hardy attached.
** Attachment added: powertop.log
http://launchpadlibrarian.net/12497558/powertop.log
--
Powertop reports huge number of wakeups and drains battery
https://bugs.launchpad.net/bugs/145377
You received this bug notification because you are a member
Hardy dmesg
** Attachment added: dmesg.log
http://launchpadlibrarian.net/12497566/dmesg.log
--
Powertop reports huge number of wakeups and drains battery
https://bugs.launchpad.net/bugs/145377
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Hardy -lspci vvnn
** Attachment added: lspci-vvnn.log
http://launchpadlibrarian.net/12497571/lspci-vvnn.log
--
Powertop reports huge number of wakeups and drains battery
https://bugs.launchpad.net/bugs/145377
You received this bug notification because you are a member of Ubuntu
Bugs, which
I can confidently say it's not yenta_socket again as I still have it
blacklisted.
So, here's the vmstat:
** Attachment added: vmstat.log
http://launchpadlibrarian.net/12502496/vmstat.log
--
Powertop reports huge number of wakeups and drains battery
https://bugs.launchpad.net/bugs/145377
You
and the top
** Attachment added: top.log
http://launchpadlibrarian.net/12502499/top.log
** Changed in: linux (Ubuntu)
Status: Incomplete = New
--
Powertop reports huge number of wakeups and drains battery
https://bugs.launchpad.net/bugs/145377
You received this bug notification
Attached.
It seems to be an order of magnitude out compared to what powertop is
saying for total wakeups.
I think it's the kernel doing it, not a process, like the yenta_socket
problem for Gutsy, and powertop does not list kernel events.
** Attachment added: timer_stats.log
Fixed in RF 5849 for Soyuz. The code now uses the backported python-apt
fix.
The problem was originally worked around in production by increasing the
ulimit for files but we'll probably cherry pick this anyway.
** Changed in: soyuz
Status: In Progress = Fix Committed
--
PPA packages
Public bug reported:
I use Kubuntu Hardy and have a Plantronics USB headset that has its own
volume and mute controls.
When using its volume controls, they affect the master volume only and
have no effect on the headset volume. I can only alter the headset
volume by going into kmix and
I'm pretty sure powertop is correct (doesn't it use the CPU itself to
get the stats?). The reason being that the temperature sensors rise by
about 10-15 degrees and my battery life is shot to bits :)
Can you reproduce it at all?
This line from powertop also piqued my interest:
57.0% (403.1)
Unfortunately the sched_mc_power_savings change makes no difference :(
I noticed that immediately after booting, the wakeups look normal
(around 100/sec). It's only after I Ieave Skype running with a call on
my (USB) headset that it makes these wake-ups go skyrocketing (even
after I shut down
This is actually an important issue for laptops, because it frequently
wakes up the hard disk, increasing power consumption and contributing to
the load cycle issue.
I would like my HD to spin down for longer than 15 seconds. :)
--
dellWirelessCtl needed for Dell machines
** Changed in: linux-source-2.6.22 (Ubuntu)
Status: Incomplete = Confirmed
--
Powertop reports huge number of wakeups under gutsy and drains battery
https://bugs.launchpad.net/bugs/145377
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact
Public bug reported:
Binary package hint: python-apt
After calling debExtractArchive(deb_file, tmpdir), my current directory
is changed to tmpdir.
Please leave my current directory alone. Bad apt_inst! No cookies!
** Affects: python-apt (Ubuntu)
Importance: Undecided
Status:
Public bug reported:
Binary package hint: python-apt
import apt_inst
def Callback(What,Name,Link,Mode,UID,GID,Size,MTime,Major,Minor):
print %s '%s','%s',%u,%u,%u,%u,%u,%u,%u % (
What,Name,Link,Mode,UID,GID,Size, MTime, Major, Minor)
Colin, finally I tried booting with noapic. The problem appears to go
away (as with acpi=noirq) and it doesn't freeze the machine with
excessive USB activity (like acpi=noirq).
I'll try suspending and resuming next and see how that goes.
I did another interrupt diff, see attached.
**
IRQ diff with no boot params and 20k wakeups/sec
** Attachment added: irq_delta_normal.log
http://launchpadlibrarian.net/14501723/irq_delta_normal.log
--
Powertop reports huge number of wakeups and drains battery
https://bugs.launchpad.net/bugs/145377
You received this bug notification
Hello again Colin
My happiness with noapic has waned, because I am now getting hard
lockups requiring a power cycle. It seems to happen when I am using
Skype and waggle my USB mouse around, so I guess it's causing a lot of
interrupts and overwhelming something.
Are we any closer to a *real* fix
It also blew away my custom /etc/modprobe.d/lirc-serial.
It's totally unacceptable for a package update to unconditionally re-
write customised configuration.
--
Update disables lircd.conf (i.e. the remote control) without appropriate notice
https://bugs.launchpad.net/bugs/239938
You received
Hi Colin - noapic seems to not break suspend/resume so I'm quite happy
again :-)
--
Powertop reports huge number of wakeups and drains battery
https://bugs.launchpad.net/bugs/145377
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Changed in: soyuz
Target: 1.99 = None
--
Hardy release files contain invalid SHA256 signatures.
https://bugs.launchpad.net/bugs/243630
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I don't know if the BT hardware is the same, but on my Latitude D630 I
just booted up Vista (I kept it in a small partition in case of such
emergencies!) and updated Dell's BT driver - it resets the firmware back
to a version that works in Linux.
--
Bluetooth not discovered on Dell Inspiron 9400
The backports module does not fix sound on my D630. I am having to
compile alsa 1.0.15rc1 to get sound (which works flawlessly, including
suspend and hibernate).
00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio
Controller (rev 02)
--
[gutsy] no sound on Dell Latitude
Since the C0 residency is 50% plus whatever process wake-ups I can see,
I would hazard a guess that the kernel has woken up one of the cores in
my dual core CPU and not let it sleep again.
--
Powertop reports huge number of wakeups under gutsy and drains battery
Having upgraded to Gutsy, the problem still exists. It looks like it
thinks the screen is 4:3 and not 16:9.
--
Video playback is horizontally stretched for GMA965 (X3100)
https://bugs.launchpad.net/bugs/132633
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
I've been playing around with powertop on gutsy and something weird is
happening after a random amount of uptime that makes the number of
wakeups go from ~100 to ~6000 per second and C0 residency ~50%. If I
kill the dd that's reading /proc/kmsg the wakeups go back to ~100
The machine is a Dell Latitude D630. (Centrino Duo T7300, Santa Rosa
chipset)
** Attachment added: lspci.txt
http://launchpadlibrarian.net/9517733/lspci.txt
--
Powertop reports huge number of wakeups under gutsy and drains battery
https://bugs.launchpad.net/bugs/145377
You received this bug
** Attachment added: dmesg.txt
http://launchpadlibrarian.net/9517740/dmesg.txt
--
Powertop reports huge number of wakeups under gutsy and drains battery
https://bugs.launchpad.net/bugs/145377
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact
It should probably go fix-committed when the package is accepted and
fix-released when finally published.
--
Bugs set to Fix Released by changelog-closes-bugs before fixed version is
published
https://bugs.launchpad.net/bugs/151925
You received this bug notification because you are a member of
Public bug reported:
Binary package hint: xserver-xorg-video-intel
I am using Kubuntu Feisty but with a backported Gutsy driver
(2.1.0-1ubuntu1) because the Feisty-shipped one is unusable on my Dell
D630.
Playing any videos in any player (kaffeine, mplayer etc) results in the
video being
Public bug reported:
Binary package hint: xmltv
The xmltv version for hardy is too old and the UK grabber is failing
because of the recent listings data format change.
Can the latest version be released to -updates please? I've installed
the current intrepid xmltv instead and it works fine.
** Changed in: soyuz
Importance: Undecided = Low
Status: New = Triaged
** Tags added: feature
--
PPA could have option to auto-add to sources
https://bugs.launchpad.net/bugs/326295
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
Binary package hint: kdepim
After I upgraded to Kubuntu Jaunty, kmail will start itself
automatically at the start of a session. It also keeps restarting
itself after I exit it. Killing the process fares no better - it
restarts! It's definitely not in the autostart config
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
Headset volume control doesn't change headset volume
https://bugs.launchpad.net/bugs/201391
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Assigning as advised by Rick
** Changed in: linux (Ubuntu)
Assignee: (unassigned) = Ubuntu Foundations Team (ubuntu-foundations)
--
Headset volume control doesn't change headset volume
https://bugs.launchpad.net/bugs/201391
You received this bug notification because you are a member of
601 - 700 of 1689 matches
Mail list logo
