On Mon, Sep 08, 2008 at 11:51:59AM +0200, Alexander Sack wrote:
> On Mon, Sep 08, 2008 at 10:44:49AM +0100, Matthew Garrett wrote:
> > The thread was discussing the removal of network-admin - doesn't that
> > modify /etc/network/interfaces?
>
> Yes it does that atm. But if network-admin is still
On Mon, Sep 08, 2008 at 10:44:49AM +0100, Matthew Garrett wrote:
> On Mon, Sep 08, 2008 at 11:31:07AM +0200, Alexander Sack wrote:
> > On Mon, Sep 08, 2008 at 12:26:50AM +0100, Matthew Garrett wrote:
> > > To be fair to NM, this is a Debian/Ubuntu integration issue. System-wide
> > > configuration
On Mon, Sep 08, 2008 at 11:31:07AM +0200, Alexander Sack wrote:
> On Mon, Sep 08, 2008 at 12:26:50AM +0100, Matthew Garrett wrote:
> > To be fair to NM, this is a Debian/Ubuntu integration issue. System-wide
> > configuration is present but requires a system-specific backend.
> >
>
> NetworkMana
On Mon, Sep 08, 2008 at 12:26:50AM +0100, Matthew Garrett wrote:
> On Sun, Sep 07, 2008 at 10:27:10PM +0300, Peteris Krisjanis wrote:
>
> > Btw, I haven't seen that system wide configuration on OpenSUSE and
> > Fedora. I would like to see it in action. So far I am very nervous
> > about ditching n
On Sun, Sep 07, 2008 at 10:27:10PM +0300, Peteris Krisjanis wrote:
> Btw, I haven't seen that system wide configuration on OpenSUSE and
> Fedora. I would like to see it in action. So far I am very nervous
> about ditching network-admin, because no matter how it was stuck in
> development, or it la
to find
the network and to get a DHCP lease...why even bother with the GUI? I'm
not saying NM is perfect, of course; it still rejects all WEP keys if
you use an Intel wireless card (yes, bugs are filed, driver is being
blamed), but at least it can handle DHCP and s
2008/9/7 Wouter Stomp <[EMAIL PROTECTED]>:
> On Fri, Sep 5, 2008 at 7:49 PM, Jordan Mantha <[EMAIL PROTECTED]> wrote:
>> On Fri, Sep 5, 2008 at 9:24 AM, Peteris Krisjanis <[EMAIL PROTECTED]> wrote:
>>> Btw, a slight offtopic from this message, but does it mean that there
>>> will be no network-admi
On Fri, Sep 5, 2008 at 7:49 PM, Jordan Mantha <[EMAIL PROTECTED]> wrote:
> On Fri, Sep 5, 2008 at 9:24 AM, Peteris Krisjanis <[EMAIL PROTECTED]> wrote:
>> Btw, a slight offtopic from this message, but does it mean that there
>> will be no network-admin from g-s-t in Ibex?
>>
>> Would be very sad if
In terms of actual volume of patches against upstream, and excluding SVN
updates, the diff from the base Debian 4.2.3-2 version and Ubuntu 8.04's
4.2.3-2ubuntu7 is about 40 KB.
> If so, what is it meant to change?
Matthias (CCed) should be able to give more information on any
://bugzilla.gnome.org/show_bug.cgi?id=548114
I'm concerned that gnome seem to be pushing through beta 1, beta 2 and
onwards without resolving these bugs.
--
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/ma
On Fri, Sep 5, 2008 at 9:24 AM, Peteris Krisjanis <[EMAIL PROTECTED]> wrote:
> Btw, a slight offtopic from this message, but does it mean that there
> will be no network-admin from g-s-t in Ibex?
>
> Would be very sad if that happened.
It won't be installed by default. However, it is still in the
Btw, a slight offtopic from this message, but does it mean that there
will be no network-admin from g-s-t in Ibex?
Would be very sad if that happened.
Peter.
2008/9/5 Thomas Novin <[EMAIL PROTECTED]>:
> Hello
>
> I recall reading something about if you file bugs on NM 0.7 you
Hello
I recall reading something about if you file bugs on NM 0.7 you should
prefix the summary with NM 0.7. Is that correct?
I have created 6 bugs for NM 0.7 but they are all untouched.
NM 0.7 Regression from 0.6.6 using VPNC plugin
https://bugs.launchpad.net/ubuntu/+source/network-manager
On Tue, Sep 02, 2008 at 10:41:49PM -0400, Richard M. Stallman wrote:
> In terms of actual volume of patches against upstream, and excluding SVN
> updates, the diff from the base Debian 4.2.3-2 version and Ubuntu 8.04's
> 4.2.3-2ubuntu7 is about 40 KB.
>
> > If so, what is it meant
Incomplete, the sub-status then
becomes "Incomplete w/ response" and the expiration timer is reset.
One can only wonder why there is a timer on the Incomplete with response
bugs at all. The bug is clearly not waiting for any more information
(assuming the reporter has done what w
On Mon, 2008-09-01 at 23:32 +0200, Wouter Stomp wrote:
> Bugs that are marked incomplete and subsequently get a reply from the
> original reporter often stay in the incomplete status. This means they
> automatically get closed even though the needed info was provided. I
> think it wou
Olá James e a todos.
On Tuesday 02 September 2008 10:28:50 James Westby wrote:
> I have seen this feature in a list of the launchpad teams possible plans for
> LP 3.0, so it may be something that happens soon.
I guess Bugs should work as Answers does.
Once the OP replies, it changes the
On Sun, Aug 17, 2008 at 06:32:41PM -0400, Richard M. Stallman wrote:
> Are the statements below true?
> Is the Ubuntu patch really 5 MB?
It is, although bear in mind that that includes a large volume of
packaging infrastructure; 1.3 MB of files in the Ubuntu patch have
nothing to do with patching
On Mon, Sep 01, 2008 at 11:32:20PM +0200, Wouter Stomp wrote:
> Hello,
>
> Bugs that are marked incomplete and subsequently get a reply from the
> original reporter often stay in the incomplete status. This means they
> automatically get closed even though the needed info was prov
On Mon, 2008-09-01 at 23:32 +0200, Wouter Stomp wrote:
> Hello,
>
> Bugs that are marked incomplete and subsequently get a reply from the
> original reporter often stay in the incomplete status. This means they
> automatically get closed even though the needed info was provide
On Tue, Sep 02, 2008 at 08:04:43AM +0100, Chris Coulson wrote:
> Unfortunately, some triagers do just close bugs when they are marked ready
> to expire, without actually checking whether the reporter provided the
> requested information. I have re-opened one such report recently, a
2008/9/2 Bryce Harrington <[EMAIL PROTECTED]>
> On Tue, Sep 02, 2008 at 01:54:21AM +0200, Wouter Stomp wrote:
> > On Mon, Sep 1, 2008 at 11:44 PM, Bryce Harrington <[EMAIL PROTECTED]>
> wrote:
> > > First, afaik automatic-expiration is not enabled for Ubuntu
On Tue, Sep 02, 2008 at 01:54:21AM +0200, Wouter Stomp wrote:
> On Mon, Sep 1, 2008 at 11:44 PM, Bryce Harrington <[EMAIL PROTECTED]> wrote:
> > First, afaik automatic-expiration is not enabled for Ubuntu. It tracks
> > when bugs will expire but doesn't close
On Mon, Sep 1, 2008 at 11:44 PM, Bryce Harrington <[EMAIL PROTECTED]> wrote:
> First, afaik automatic-expiration is not enabled for Ubuntu. It tracks
> when bugs will expire but doesn't close them without human action.
>
Ok, so what does expiring mean then?
> So... I thi
On Mon, Sep 01, 2008 at 11:32:20PM +0200, Wouter Stomp wrote:
> Hello,
>
> Bugs that are marked incomplete and subsequently get a reply from the
> original reporter often stay in the incomplete status. This means they
> automatically get closed even though the needed info was prov
Hello,
Bugs that are marked incomplete and subsequently get a reply from the
original reporter often stay in the incomplete status. This means they
automatically get closed even though the needed info was provided. I
think it would be a good idea to automatically change the status to
new once a
Olá Brian e a todos.
On Friday 22 August 2008 14:31:08 Brian Curtis wrote:
> My idea is to have launchpad send out an e-mail to the bug creators of bugs
> relating to packages that were recently updated asking them to check with
> the update (provide instructions on how to update) to see
I haven't been following along very closely, but I have an idea on something
that might help out with bug management (assuming this hasn't been talked
about).
I went through and marked a bunch of bugs as incomplete yesterday because it
seems that pidgin was updated and their pro
where the retracers fail and we
>>> dont have any testcase. You want those to stay open as well?
>> But what do we do with these then? They are still bugs, and with some
>> crashes we never seem to get a backtrace with symbols.
>>
>> Currently we just close them
2008/8/21 Christopher James Halse Rogers <[EMAIL PROTECTED]>:
> In what way is this different to the current Apport infrastructure? My
> understanding is that the client sends in the crashdump and the apport
> retracers on launchpad replay it on a system with the debugging symbols
> installed.
>
>
On Thu, 2008-08-21 at 15:26 +0200, Krzysztof Lichota wrote:
> 2008/8/20 Null Ack <[EMAIL PROTECTED]>:
> > I'm not convinced that the strategy of asking users to install
> > specialised debugging packages is the right way to go. I see a very
> > low hit rate with this working in practice.
>
> It is
2008/8/20 Null Ack <[EMAIL PROTECTED]>:
> I'm not convinced that the strategy of asking users to install
> specialised debugging packages is the right way to go. I see a very
> low hit rate with this working in practice.
It is not surprising. Asking people to install multi-megabyte packages
and re
On Thu, 2008-08-21 at 15:17 +1000, Null Ack wrote:
> 3. Ubuntu makes the leading step in showing their commitment to
> quality by requiring that all upstream projects run the security test
> static test tool before it will be accepted into the repos. Tools are
> bit to make this pretty easy for ups
ainly that is 'a' purpose, but not the only one.
> Understanding the state of a package or distro is another purpose.
>
> By marking incomplete backtrace crash bugs invalid we lose
> information both about circumstances of crashes and frequency.
> A bug with 50 dupes and one good b
with a symbol-equipped equivalent as well. Having a
> debug version of a package among standard packages hurts only neglible and
> most users won't even notice.
>
> Voi-la, next crash time Apport will come along with a backtrace.
>
Markus I particularly like your suggestion here
On Wed, Aug 20, 2008 at 10:20:38AM -0400, Paul Smith wrote:
> Also, it seems to me that if you tell someone their bug is "invalid"
> that doesn't inspire them to come back with more information or send
> more bugs in the future. On the other hand, if you mark the bug as
as well?
>
>But what do we do with these then? They are still bugs, and with some
>crashes we never seem to get a backtrace with symbols.
>
>Currently we just close them and hope they go away..
Personally, I think closing them after some period if similar crashes stop
coming is reaso
do we do with these then? They are still bugs, and with some
> crashes we never seem to get a backtrace with symbols.
>
> Currently we just close them and hope they go away..
if its not possible to get a backtrace, nor is there any hint on how
to reproduce, we can only hope that we have m
2008/8/20 Alexander Sack <[EMAIL PROTECTED]>:
> But there are also many crash reports where the retracers fail and we
> dont have any testcase. You want those to stay open as well?
But what do we do with these then? They are still bugs, and with some
crashes we never seem to get a ba
On Wed, Aug 20, 2008 at 04:06:56PM +0200, Markus Hitter wrote:
>
> So yes, please stop this marking-as-invalid-mania.
>
I think the real problem here is that we open new bugs for every crash
in the first place. Having a separate crash database from where
developers can pick individua
On Wed, Aug 20, 2008 at 04:42:42PM +0200, Markus Hitter wrote:
>
> Am 20.08.2008 um 11:42 schrieb Null Ack:
>
> > I'm not convinced that the strategy of asking users to install
> > specialised debugging packages is the right way to go. I see a very
> > low hit rate with this working in practice.
ith thinking about how this detracts from
> >quality and what to do about it. These are real bugs, some of them are
> >in production, that are not being fixed.
>
> I think this is important. It seems to me that marking bugs invalid
> because they don't have enough informat
Scott Kitterman wrote:
> By marking incomplete backtrace crash bugs invalid we lose information both
> about circumstances of crashes and frequency. A bug with 50 dupes and one
> good backtrace is different than one with no dupes. Reading the dictionary
> definition of 'invali
On Wednesday 20 August 2008 11:00, Matthew Paul Thomas wrote:
> Scott Kitterman wrote on 20/08/08 15:34:
> > On Wednesday 20 August 2008 10:31, Matthew Paul Thomas wrote:
> >...
> >
> >>> So, if there is no suitable bug state existing already we need a new
> &g
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Scott Kitterman wrote on 20/08/08 15:34:
>
> On Wednesday 20 August 2008 10:31, Matthew Paul Thomas wrote:
>...
>>> So, if there is no suitable bug state existing already we need a new
>>> state for these kinds of bugs. We
Am 20.08.2008 um 11:42 schrieb Null Ack:
> I'm not convinced that the strategy of asking users to install
> specialised debugging packages is the right way to go. I see a very
> low hit rate with this working in practice.
How about getting this even more automated? Apport would have three
butt
On Wednesday 20 August 2008 10:31, Matthew Paul Thomas wrote:
> Paul Smith wrote on 20/08/08 15:20:
> >...
> > On the other hand I do think it's worthwhile to somehow mark bugs which
> > are not sufficiently documented as to be reproducible/fixable.
> >...
> >
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Paul Smith wrote on 20/08/08 15:20:
>...
> On the other hand I do think it's worthwhile to somehow mark bugs which
> are not sufficiently documented as to be reproducible/fixable.
>...
> So, if there is no suitable bug state existi
On Wed, 2008-08-20 at 16:06 +0200, Markus Hitter wrote:
> please stop this marking-as-invalid-mania.
+1. It's a bad idea to hide problems, even ones that cannot be
replicated.
On the other hand I do think it's worthwhile to somehow mark bugs which
are not sufficiently docume
Am 20.08.2008 um 13:39 schrieb Scott Kitterman:
> Modulo stupid sysadmin tricks that can put a system in an
> unsupportable
> state, crashes are always bugs and should not be casually thrown away.
Isn't this a discussion coming up every 6 months or so? From the last
tim
e through and I ended up
>at an invalid existing bug from 2007 because the user had not
>submitted debugging symbols. This has happened to me before and my
>mind has been busy since with thinking about how this detracts from
>quality and what to do about it. These are real bugs, some of
. This has happened to me before and my
mind has been busy since with thinking about how this detracts from
quality and what to do about it. These are real bugs, some of them are
in production, that are not being fixed.
I'm not convinced that the strategy of asking users to install
specia
On Mon, Aug 18, 2008 at 6:45 PM, Paul Smith <[EMAIL PROTECTED]> wrote:
> On Mon, 2008-08-18 at 18:18 -0400, Andrew wrote:
>> > Are the statements below true?
>> > Is the Ubuntu patch really 5 MB?
>> > If so, what is it meant to change?
>>
>> The diff of the current gcc in Intrepid ,as found here [
On Mon, 2008-08-18 at 18:18 -0400, Andrew wrote:
> > Are the statements below true?
> > Is the Ubuntu patch really 5 MB?
> > If so, what is it meant to change?
>
> The diff of the current gcc in Intrepid ,as found here [1], seems to
> only be 672 KB
>
> gcc-4.2.3's [2] seems to be 1.1 MB
You're
On Mon, Aug 18, 2008 at 3:18 PM, Andrew <[EMAIL PROTECTED]> wrote:
>> Are the statements below true?
>> Is the Ubuntu patch really 5 MB?
>> If so, what is it meant to change?
>
> The diff of the current gcc in Intrepid ,as found here [1], seems to
> only be 672 KB
>
> gcc-4.2.3's [2] seems to be 1
> Are the statements below true?
> Is the Ubuntu patch really 5 MB?
> If so, what is it meant to change?
The diff of the current gcc in Intrepid ,as found here [1], seems to
only be 672 KB
gcc-4.2.3's [2] seems to be 1.1 MB
[1]
http://archive.ubuntu.com/ubuntu/pool/main/g/gcc-4.3/gcc-4.3_4.3.1
Are the statements below true?
Is the Ubuntu patch really 5 MB?
If so, what is it meant to change?
From: John Regehr <[EMAIL PROTECTED]>
...the default C
compiler for Ubuntu [GNU/]Linux 8.04 is a patched gcc-4.2.3 which (on x86)
miscompiles this rather simple function:
int func_1 (void)
{
Olá Martin e a todos.
On Tuesday 03 June 2008 11:05:37 Martin Pitt wrote:
> Do we need to make this page more obvious? Anything that I can change on that
> page to make it more useful for testers?
>
> Thanks,
> Martin
Maybe place that link, or some short version of it, on Update-Manager, when
Matthew Garrett wrote:
> On Mon, Jan 14, 2008 at 11:10:49AM -0800, Matt Price wrote:
>
>> sudo pm-suspend
>
> Right, so it sounds more like the issue here is that we're passing
> quirks that are breaking your system. For reference, the quirks that are
> used by default on Ubuntu are currently:
Lars Wirzenius schrieb:
> https://wiki.ubuntu.com/UnderstandingSuspend might of some help to some
> people.
Thanks, that's a great start, which could be improved by documenting the
changes made in hardy (that would improve debugging feedback before the
relase). The next time I'll have troube with
On to, 2008-01-17 at 11:59 +0100, Paulus Esterhazy wrote:
> It would be *very* helpful if a developer who really knows this stuff
> could write a document on the Wiki detailing how this process works for
> hardy. To users, suspend problems are opaque, because there often are no
> logs readily avail
rocess. can someone point me to a location where the
> process is described? or suggest best practice for finding bugs of this
> nature (in which resume is impossible, so messages e.g. from dmesg
> or /var/log/messages don't get captured?
It would be *very* helpful if a devel
Matt Price said the following on 01/15/2008 10:08 PM:
>> Now this is fine for my dell with nvidia driver, but I hope it works for
>> others too.
>>
> didn't catch this, what model is your dell? mine is latitude d820, if
> you're the same maybe we've identified a laptop-specific bug.
I have an E1
On Tue, 2008-01-15 at 21:18 -0500, Paul S wrote:
> Paul S said the following on 01/15/2008 07:18 PM:
> > Matt Price said the following on 01/15/2008 05:35 PM:
> ok, now I get it .. since these are based on not being false, they are
> set. and "sudo lshal | grep quirk" shows that they are not se
Paul S said the following on 01/15/2008 07:18 PM:
> Matt Price said the following on 01/15/2008 05:35 PM:
>> take a look
>> at /usr/share/hal/scripts/linux/hal-syspem-power-suspend-linux & related
>> scripts -- the $QUIRK variable is built up in these scripts
>> progressively; all you would need to
> If I suspend my laptop, I'll lose my mouse pointer. The mouse action
> is still there, but no mouse pointer, so I cant see what I'm
> clicking.
In a side note, my notebook, an Asus G1 suspends and hibernates nicely
with hardy.
[]s
Adilson.
--
Ubuntu-devel-discuss mailing list
Ubuntu-devel-di
On Tue, 2008-01-15 at 19:18 -0500, Paul S wrote:
> Matt Price said the following on 01/15/2008 05:35 PM:
> > paul, how did you find out that the suspend button initiates quirks in
> > the order you describe?
>
> I edited /usr/share/hal/scripts/linux/hal-syspem-power-suspend-linux and
> added a
Matt Price said the following on 01/15/2008 05:35 PM:
> paul, how did you find out that the suspend button initiates quirks in
> the order you describe?
I edited /usr/share/hal/scripts/linux/hal-syspem-power-suspend-linux and
added a line to log the value of $QUIRKS when it was called, as follo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Monday 14 January 2008 19:10:49 Matt Price wrote:
> hmmm... fooling around, i find that i can suspend pretty reliably from the
> command line
> sudo pm-suspend
>
> but that the gnome-power-manager dialog reliably fails to resume; this
> despiteth
Matthew Garrett said the following on 01/15/2008 06:02 PM:
> Though, having said that, I have found various issues - I've just
> uploaded a new pm-utils. It'd be nice to know if it worked for you.
>
OK, I'm updating daily, so when it hits the repos I'll get it, unless
you have an advance copy
Matthew Garrett said the following on 01/15/2008 05:42 PM:
> I can't see how this can happen - the same environment variables are set
> in both cases independent of the ordering. Is this repeatable?
>
Yes, many times.
--
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
M
On Tue, 2008-01-15 at 23:02 +, Matthew Garrett wrote:
> Though, having said that, I have found various issues - I've just
> uploaded a new pm-utils. It'd be nice to know if it worked for you.
>
i'll give it a try myself soon as it hits the archive.
matt
> --
> Matthew Garrett | [EMAIL P
Though, having said that, I have found various issues - I've just
uploaded a new pm-utils. It'd be nice to know if it worked for you.
--
Matthew Garrett | [EMAIL PROTECTED]
--
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at:
https://li
I can't see how this can happen - the same environment variables are set
in both cases independent of the ordering. Is this repeatable?
--
Matthew Garrett | [EMAIL PROTECTED]
--
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at:
https://
On Tue, 2008-01-15 at 16:30 -0500, Paul S wrote:
> Matthew Garrett said the following on 01/15/2008 01:59 PM:
> > On Tue, Jan 15, 2008 at 09:30:13AM -0500, Paul S wrote:
> >
> >> This is not good. I had a kernel update so had to reboot anyway. Now
> >> I find that even Fn-Esc does not work.
Matthew Garrett said the following on 01/15/2008 01:59 PM:
> On Tue, Jan 15, 2008 at 09:30:13AM -0500, Paul S wrote:
>
>> This is not good. I had a kernel update so had to reboot anyway. Now
>> I find that even Fn-Esc does not work. The only way to suspend is by
>> konsole with "sudo pm-susp
On Tue, Jan 15, 2008 at 09:30:13AM -0500, Paul S wrote:
> This is not good. I had a kernel update so had to reboot anyway. Now
> I find that even Fn-Esc does not work. The only way to suspend is by
> konsole with "sudo pm-suspend" and it still works ok. The
> kde-power-manager menu "suspen
Matthew Garrett said the following on 01/15/2008 09:00 AM:
> acpid needs restarting, so rebooting is the easiest way to do that. If
> Fn+Esc no longer works, there's some sort of KDE issue.
This is not good. I had a kernel update so had to reboot anyway. Now
I find that even Fn-Esc does not w
On Tue, Jan 15, 2008 at 08:25:38AM -0500, Paul S wrote:
> but same result .. /var/log/pm-suspend.log does not change, suspend /
> resume work only from laptop Fn-Esc, not kde-power-manager menu or usb
> keyboard sleep button and no "logger" message in /var/log/messages.
>
> Do I need to reboot
Matthew Garrett said the following on 01/15/2008 07:12 AM:
> On Mon, Jan 14, 2008 at 09:17:29PM -0500, Paul S wrote:
>
>> Since kde-power-manager won't work and my usb keyboard sleep button
>> doesn't work, I tried the Fn-Esc key combo on the laptop, which is the
>> suspend key combo. The lapto
On Mon, Jan 14, 2008 at 09:17:29PM -0500, Paul S wrote:
> Since kde-power-manager won't work and my usb keyboard sleep button
> doesn't work, I tried the Fn-Esc key combo on the laptop, which is the
> suspend key combo. The laptop suspended and resumed fine. Now, when I
> look at /var/log/mes
On Mon, 2008-01-14 at 23:42 +, Matthew Garrett wrote:
> On Mon, Jan 14, 2008 at 11:10:49AM -0800, Matt Price wrote:
>
> > sudo pm-suspend
>
> Right, so it sounds more like the issue here is that we're passing
> quirks that are breaking your system. For reference, the quirks that are
> used
Paul S said the following on 01/14/2008 08:17 PM:
> Still no idea why kde-power-manager can't start a suspend
Here's an idea .. maybe some of the old acpi-support suspend is still
active. I just tried adding a logger line to
/usr/lib/hal/scripts/linux/hal-system-power-suspend-linux to print
Matthew Garrett said the following on 01/14/2008 06:42 PM:
> On Mon, Jan 14, 2008 at 11:10:49AM -0800, Matt Price wrote:
>
>> sudo pm-suspend
>
> Right, so it sounds more like the issue here is that we're passing
> quirks that are breaking your system. For reference, the quirks that are
> used
On Mon, Jan 14, 2008 at 11:10:49AM -0800, Matt Price wrote:
> sudo pm-suspend
Right, so it sounds more like the issue here is that we're passing
quirks that are breaking your system. For reference, the quirks that are
used by default on Ubuntu are currently:
--quirk-dpms-on
--quirk-vbestate-re
On Mon, Jan 14, 2008 at 10:30:33AM -0800, Matt Price wrote:
> ... i suppose if the resume worked properly the reverse steps would be
> present too?
You'd hope so :) How exactly is the resume failing, and which graphics
drivers are you using?
> ah, this is my bad -- it seems an old script i h
Matt Price said the following on 01/14/2008 02:10 PM:
> hmmm... fooling around, i find that i can suspend pretty reliably from
> the command line
>
> sudo pm-suspend
>
> but that the gnome-power-manager dialog reliably fails to resume; this
> despitethe fact that it seemsto be using pm-suspend,
On Mon, 2008-01-14 at 10:30 -0800, Matt Price wrote:
> On Mon, 2008-01-14 at 15:23 +, Matthew Garrett wrote:
> > On Sun, Jan 13, 2008 at 10:51:48PM -0800, Matt Price wrote:
> >
>
> > > i alsoseem to have an odd problem -- if i choose 'suspend' from the
> > > gnome 'quit' menu, then resume fa
think still works best if it's called by
> > the hibernate script.
>
> If it's triggered by writing disk to /sys/power/state (which I believe
> it is, nowadays) then pm-hibernate will trigger it happily. Please don't
> use the hibernate script - any cases wher
On Mon, 2008-01-14 at 16:41 +, Matthew Garrett wrote:
> Filing bugs is ok, but if you think an issue is generic then
> feel free to bring it up here.
Is suspend/hibernate with laptops using the new proprietary ATi driver
(fglrx) in Hardy expected to work now, or is is still normal t
t us to feedback on this list or start bugs?
Now is a fine time to provide feedback - there shouldn't be any major
changes. Filing bugs is ok, but if you think an issue is generic then
feel free to bring it up here.
--
Matthew Garrett | [EMAIL PROTECTED]
--
Ubuntu-devel-discuss mailing l
ll as the ubuntu lead?
Is it too early to start feedback on this stuff now, or should we
continue? Do you want us to feedback on this list or start bugs?
regards,
Paul
--
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
ed by writing disk to /sys/power/state (which I believe
it is, nowadays) then pm-hibernate will trigger it happily. Please don't
use the hibernate script - any cases where it works and pm-utils doesn't
are bugs that need fixing.
> i alsoseem to have an odd problem -- if i choose '
ck down
> > this bug but i'm not entirely sure what the current chain of events is
> > in the suspend process. can someone point me to a location where the
> > process is described? or suggest best practice for finding bugs of this
> > nature (in which resume is impossible,
ain, how to track down
> this bug but i'm not entirely sure what the current chain of events is
> in the suspend process. can someone point me to a location where the
> process is described? or suggest best practice for finding bugs of this
> nature (in which resume is impossible,
the
process is described? or suggest best practice for finding bugs of this
nature (in which resume is impossible, so messages e.g. from dmesg
or /var/log/messages don't get captured?
thanks,
matt
--
Matt Price
[EMAIL PROTECTED]
--
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discu
On Thursday 10 January 2008 14:49:07 Sarah Hobbs wrote:
> Doesn't apply for universe, where there are a lot of uploads going on.
Thanks.
> (and did you really need to quote the *entire* mail for a 2 line response?)
The original email was sent to the announce list. since I was sending this
repl
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
(``-_-´´) -- Fernando wrote:
> Its the end of the 9th of January, and there are still many updates coming
> for hardy.
> Aint the "soft" freeze working?
>
>
Doesn't apply for universe, where there are a lot of uploads going on.
(and did you really
ading packages between Tuesday and Thursday which don't bring us closer
> to releasing the alpha, so that these days can be used for settling the
> archive and fixing any remaining showstoppers.
>
> The list of bugs targeted for alpha-3 can be found in a couple of different
> places
plete.
>
> I find it interesting that you call other ways to look at bug
> statuses 'odd', while not considering that maybe your intepretation
> sounds odd to me (and probably to others as well).
I have written a Launchpad news entry that clarifies the semantics of
bug statuse
101 - 200 of 246 matches
Mail list logo
