> That model=imac24 doesn't work for me on jaunty with my nvidia-based
mac mini. Any other hint?
Same thing for me. Did you ever solve this? I've done everything
I could find including making sure channels aren't muted, and even
going through Part A of http://ubuntuforums.org/showthread.php?t=78
read jack, good idea. I get sound out of of the rear jack (analog), with
either "model=mbp3" or "model=imac24", no difference. Still no sound from the
built-in
speaker. I can't try digital/optical, as I don't have anything to connect it
to.
I'm now running alsa from https://launchpad.net/~th
Public bug reported:
Binary package hint: likewise-open
After upgrading from ubuntu 9.10 to 10.04 the computer takes forever to
LOGIN... Attention, not to boot, just the login part.
Checking the Likewise GUI AD Settings
STATUS: Joined
with correct computer name and domain (imported from 9.10)
I
** Attachment added: "likewise_log_error"
http://launchpadlibrarian.net/47782180/likewise_log_error
** Description changed:
Binary package hint: likewise-open
this launchpad sucks big time... slow and always in read only
mode... so I spend half an hour writing a bug and everythin
As per above, bug was "Incomplete" by mistake. Please put it back to
Triaged or whatever state is more appropriate.
** Changed in: pulseaudio (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
h
Joseph - that one exibits the behavior described here - so I guess we'd
mark it as git bisect bad
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1094800
Title:
Toshiba z930 fails to resume after seco
Joseph, feels kind'a silly for me to have you building kernels for me to
test, so I went ahead and did the bisect myself to save you that time.
Making a quick summary of this behavior
Kernel <= 3.3 : System is able to successfully resume multiple times.
Everything works.
3.4-RC1 : System reboo
Hum, joseph, did you see my last comment? I can absolutely test this
one, but is it still relevant? Won't we get to the same results I got?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1094800
Title:
I did the bisect to when this started happening. So here the deal:
SYMPTOMS:
3.x -> 3.3.8: All working!
3.4-rc1: rebooted automatically while resuming from suspension
3.4-rc2 -> 3.8-rc2: behavior described in this report
* Change on 3.3 that caused the system to reboot while trying to resume
Public bug reported:
I've been using a Twinview (nvidia) setup on kubuntu 11.04 with an
external Dell U2410 monitor for a long while without any problems.
Something changed recently though (don't know if it was an update), as
for today, all I get is a blank screen on the external monitor, no
curs
> for a short second I can move the cursor to the external monitor and
see e.g. the password dialog box there
What I mean is that I can move the cursor to the external monitor, and
_see it_ too. But only for a second. I goes away quickly.
--
You received this bug notification because you are a
I installed gdm and made it the default in hopes that it'd be a kde
specific problem, and rebooted, but I still got the same problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/847691
Title:
blan
Ah! A suspend to RAM and resume fixed it. (Docked, but that may not
have been necessary.) It looks like some stale state somewhere
associated with suspending. It is possible that my laptop powered down
while in the suspended state just before the problem appearing (I'm not
certain).
Any idea w
I came here due to trying to install dgen causing trouble. See:
https://bugs.launchpad.net/ubuntu/+source/dgen/+bug/1016944
>From the description, the fix sounds simple. Is there anything blocking
it?
Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
I find it hard to find that firefox is causing this - but for the ones
that think it's the cause, can you please go to Preferences -> Advanced
-> General Tab and disable / enable hardware acceleration to see if that
could be the cause?
In this thread there seems to be different things at stake. O
For what it's worth, there's a suggestion in this thread that worked for
me:
Setting in grub.conf: i915.i915_enable_rc6=0 i915.i915_enable_fbc=0
(instead of =1 on both) just made my computer come back from "windows
mode"
--
You received this bug notification because you are a member of Ubuntu
B
Hey Joseph - Indeed, still exists.
I did a "manual bisect" using the kernels from
http://kernel.ubuntu.com/~kernel-ppa/mainline/ and it started happening in
v3.4-quantal . In v3.3.8-quantal/ still worked
** Tags added: kernel-bug-exists-upstream
** Changed in: linux (Ubuntu)
Status: I
Rich, can you try kernel 3.3.8? Worked for me, as I was only able to
reproduce this post 3.4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1088721
Title:
[Toshiba Portege Z935-P390] Fn key and susp
Forgot to tell - also tested in 3.8-rc2 and the bug is still present
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1094800
Title:
Hello Joseph.
I'm assuming 3.3 final is 3.3.8 - I do confirm the bug does not exist in
3.3.8 (and as far as my tests went, didn't happen in any previous
kernels I tested). Let me know if you want more tests on 3.3 series.
The bug, as I reported it, happens in 3.4-rc2. In 3.4-rc1 the system is
abl
Just a note:
"I'll start a bisect between v3.4-rc1 and v3.4-rc2."
There seem to be a bug in v3.4-rc1, since it didn't even resume from suspend.
In summary:
3.x -> 3.3.8: All working!
3.4-rc1: rebooted automatically while resuming from suspension
3.4-rc2 -> 3.8-rc2: behavior described in this r
This bug report is about failing to resume from *second* suspension,
where I just get with a blank display.
In 3.4-rc1 reboots while trying to resume from *first* suspend.
My very naive interpretation is that something regarding suspension
changed for 3.4-rc1, wasn't working properly and was chan
still happens for me on 3.8-rc1-raring
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1088721
Title:
Fn key and suspend resume fa
** Attachment added: "Syslog of 3.3.8 since sleep request (everything working
fine)"
https://bugs.launchpad.net/ubuntu/+bug/1094800/+attachment/3471130/+files/successfulResume-3.3.8-GOOD.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
After resuming from first supend, brightness keys don't work, power key
doesn't show logout menu, and if I try to suspend a second time I'm
unable to recover from suspension (blank screen)
Seems similar to
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1088721
This is
apport information
** Tags added: apport-collected quantal
** Description changed:
After resuming from first supend, brightness keys don't work, power key
doesn't show logout menu, and if I try to suspend a second time I'm
unable to recover from suspension (blank screen)
Seems similar
apport information
** Attachment added: "BootDmesg.txt"
https://bugs.launchpad.net/bugs/1094800/+attachment/3471132/+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/1094800
Titl
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1094800/+attachment/3471135/+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/1094800
Title:
Tosh
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1094800/+attachment/3471136/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1094800
Title:
Tosh
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1094800/+attachment/3471137/+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/1094800
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1094800/+attachment/3471138/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/109
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1094800/+attachment/3471139/+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/1094800
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1094800/+attachment/3471140/+files/RfKill.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1094800
Title:
To
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1094800/+attachment/3471141/+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/1094800
Title:
To
apport information
** Attachment added: "UdevLog.txt"
https://bugs.launchpad.net/bugs/1094800/+attachment/3471142/+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/1094800
Title:
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1094800/+attachment/3471143/+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/1094800
Ti
last apport-collect was done on official Linux arpeggio
3.5.0-21-generic, where problem also appears
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1094800
Title:
Toshiba z930 fails to resume after s
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1094800/+attachment/3471133/+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/1094800
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1094800/+attachment/3471134/+files/IwConfig.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1094800
Title:
Added package (linux)
** Package changed: ubuntu => linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1094800
Title:
Toshiba z930 fails to resume after second suspend on kernel >=3.4
To
I also see this - it worked last week
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1190160
Title:
Can't sign in: window goes blank
To manage notifications about this bug go to:
https://bugs.launch
Z930-12T
Kernel 3.11.0-031100rc4-generic fixed this problem!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1094800
Title:
Toshiba z930 fails to resume after second suspend on kernel >=3.4
To manag
$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
Version 6.40
10/01/2012
But like I said, 3.11 fixes this (also see
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1088721)
Didn't have the chance to upgrade to 6.70 yet (no windows here,
upgrading bios is always a PI
So do we need to put the status back to "Triaged" to raise awareness of
the issue? I'm guessing the "Incomplete" status is making it so the
people that should look at it aren't even looking...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
44 matches
Mail list logo
