** Changed in: linux (Ubuntu Vivid)
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/1371233
Title:
USB 3.0 connection is unreliable + xHCI xhci_drop_endpoint
Same problem, fresh 14.10 Desktop install on custom built PC (GA-Z77X-
UD5H) : mdadm.conf looks good, mdadm --assemble --scan works perfectly
when booted, but raid drive lost upon reboot.
Commented that line out and it now works...
--
You received this bug notification because you are a member
@iacobs many thanks for streching Oleksij's work into a working dkms
module (I think there might be a newer version of the code in the MMC
ML?), I can confirm it works under 14.10.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
WIth the release of 14.10, compiz-plugin-extras are not packaged anymore
and fallback to the static window switcher (recommended everywhere when
this issue is mentionned) is not easily feasible anymore. Users are
bound to the default unity switcher's painful time delay.
This switcher behavior is
(In reply to comment #38)
(In reply to comment #37)
We've merged a number of patches that might affect this since the last
comments. Please try recent drm-intel-nightly branch and report back.
Thanks.
No blank screen issues in my UX302LA either at boot, or when mode setting or
when
Created attachment 97254
kernel 20140411 dmesg w/ drm.debug=0xe
Hello,
so far it works on the UX302LG, i've attached the dmesg with
drm.debug=0xe enabled, I see the screen flashing black after grub but it
works thereafter.
--
You received this bug notification because you are a member of
No updates since last reply in the freedesktop bugzilla :
https://bugs.freedesktop.org/show_bug.cgi?id=73567 from 02-24-2014, if
you have something more to add to the bugreport, please do.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Hello Oleksij,
thanks a lot for the hard work on getting a driver for that reader.
I did get a reply from Alcor, it was along the lines of It should be
compatible with Linux, but we do not support 3rd parties, ask your OEM (Asus,
in this case) for a driver..
Asus previously answered (for the
I notice that the bug hasn't been updated in a while, a patch that fixes the
issue exists and can be integrated in the same way as bug 71049 (quirk-based
bpp clamping bypass).
Can this patch be reviewed integrated so that we can consider the issue fixed
with this laptop and move on ?
--
You
I can confirm screen-resolution-extra 0.17.1 fixes the issue and that
I'm now able to switch back to the Intel GPU. There is still some issue
with nvidia wake from suspend that crashes X but this is reported as Bug
1220865.
--
You received this bug notification because you are a member of Ubuntu
Oleksij I tried writing to them but didn't get much of an answer, maybe you'll
be more lucky this time (or the more that ask, things might change).
Otherwise you're right, there's pretty much only opening the .sys in IDA that'd
be left...
--
You received this bug notification because you are a
*** This bug is a duplicate of bug 1268771 ***
https://bugs.launchpad.net/bugs/1268771
Alberto,
I confirm this is indeed duplicate of bug #1268771 and got resolved by
following suggested actions. I can now confirm that I have bug #1274733
and I'm unable to switch to Intel Power Savings Mode
(In reply to comment #32)
Created attachment 93205 [details] [review]
Patch adding quirk to avoid bpp clamping
Since we know that ignoring bpp clamping actually works (tehownt can
confirm), can intel consider a quirk based patch for this laptop model as in
this patch?
Thanks.
I can
I have to refute this:
trying to modset or suspend using intel-drm-nightly from 2014-01-26 doesn't
work with my machine (UX302LG).
Though I have screen from boot using the intel-drm-nightly kernels, for me the
issue still is present whatever the branch.
--
You received this bug notification
(In reply to comment #30)
(In reply to comment #29)
Did you try the newer kernels without that, wrt this bug?
Yes, 2014-01-28 drm-intel-next 3.13.0-5 (Ubuntu) both fail.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Created attachment 92927
dmesg of 2014-01-28 drm-intel-nightly on ux302LG with drm.debug=0xe
Tried with 2014-01-28 nightly and didn't work (screen on boot, blank on resume
from suspend).
Output from dmesg with drm.debug=0xe added.
As for including the patch from comment #15 , I'm unfortunately
(In reply to comment #28)
(In reply to comment #27)
Tried with 2014-01-28 nightly and didn't work (screen on boot, blank on
resume from suspend).
Output from dmesg with drm.debug=0xe added.
Why acpi_osi= in kernel cmdline?
Fixes a couple of other issues : Airplane mode key and Screen
Problem existsts in 12.04.0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1270676
Title:
SD Card Reader broken on UX302LG
To manage notifications about this bug go to:
Hello, problem exists in 13.10 and 12.04.3 tested w/ live CD version.
Also, lspci.out attachment got removed but please note that lspci.txt
has less info since it ran unprivileged.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Tested 3.13 from http://kernel.ubuntu.com/~kernel-
ppa/mainline/v3.13-trusty/ had to boot in recovery mode/root console
because of Bug #1265544 device still shows as Unassigned class [ff00]:
Device 1aea:6601 and SD Cards do not work.
** Changed in: linux (Ubuntu)
Status: Incomplete =
apport information
** Tags added: apport-collected trusty
** Description changed:
SD card reader is dysfunctional in UX302LG laptop.
USB readers work without problem.
Nothing happens when pluggin SD/mSD/SDHC/mSDHC cards in the reader (might as
well use a piece of wood).
Nothing
apport information
** Attachment added: BootDmesg.txt
https://bugs.launchpad.net/bugs/1270676/+attachment/3954047/+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/1270676
apport information
** Attachment added: AudioDevicesInUse.txt
https://bugs.launchpad.net/bugs/1270676/+attachment/3954046/+files/AudioDevicesInUse.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: CurrentDmesg.txt
https://bugs.launchpad.net/bugs/1270676/+attachment/3954049/+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/1270676
apport information
** Attachment added: ProcEnviron.txt
https://bugs.launchpad.net/bugs/1270676/+attachment/3954054/+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/1270676
apport information
** Attachment added: AlsaInfo.txt
https://bugs.launchpad.net/bugs/1270676/+attachment/3954045/+files/AlsaInfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1270676
Title:
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.launchpad.net/bugs/1270676/+attachment/3954055/+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/1270676/+attachment/3954048/+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/1270676
Title:
SD Card
apport information
** Attachment added: ProcModules.txt
https://bugs.launchpad.net/bugs/1270676/+attachment/3954056/+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/1270676
apport information
** Attachment added: RfKill.txt
https://bugs.launchpad.net/bugs/1270676/+attachment/3954058/+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/1270676
Title:
SD
apport information
** Attachment added: UdevDb.txt
https://bugs.launchpad.net/bugs/1270676/+attachment/3954059/+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/1270676
Title:
SD
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.launchpad.net/bugs/1270676/+attachment/3954053/+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/1270676
apport information
** Attachment added: Lsusb.txt
https://bugs.launchpad.net/bugs/1270676/+attachment/3954052/+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/1270676
Title:
SD
apport information
** Attachment added: IwConfig.txt
https://bugs.launchpad.net/bugs/1270676/+attachment/3954050/+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/1270676
Title:
apport information
** Attachment added: Lspci.txt
https://bugs.launchpad.net/bugs/1270676/+attachment/3954051/+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/1270676
Title:
SD
apport information
** Attachment added: PulseList.txt
https://bugs.launchpad.net/bugs/1270676/+attachment/3954057/+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/1270676
apport information
** Attachment added: UdevLog.txt
https://bugs.launchpad.net/bugs/1270676/+attachment/3954060/+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/1270676
Title:
apport information
** Attachment added: WifiSyslog.txt
https://bugs.launchpad.net/bugs/1270676/+attachment/3954061/+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/1270676
WORKAROUND:
Using
acpi_osi=
at boot parameter with NO value set, fixes the key and screen brightness is
able to be controlled correctly by it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1270663
WORKAROUND:
Using
acpi_osi=
at boot parameter with NO value set, also fixes the Wifi key (and others, see
Bug #1270663).
Still the same caveat though.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: acpi
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1270663
Title:
Brightness hotkey broken on UX302LG
To manage notifications about
** Also affects: acpi
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1270676
Title:
SD Card Reader broken on UX302LG
To manage notifications about this
** Also affects: acpi
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1270661
Title:
Wifi hotkey / LED (acpi) broken on UX302LG
To manage notifications
FWIW Asus has so far refused to provide any help, saying that they do
not support Linux. Getting a new UEFI to fix this is not looking
good...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1265544
Public bug reported:
Wifi hotekey (including LED lighting on/off) is broken on UX302LG with
default acpi settings.
*SOME* of the other hotkeys work :
- keyboard dim
- sound control
- touchpad toggle.
- sleep hotkey
not tested : external display hotkey.
Screen dim key does not work (probably
** Attachment added: dmesg.acpi_not_win2012
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331-updates/+bug/1270661/+attachment/3952388/+files/dmesg.acpi_not_win2012
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
See dmesg/kern.log output from Bug #1270661 or Bug #1265544.
** Package changed: nvidia-graphics-drivers-331-updates (Ubuntu) =
ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1270663
Title:
Public bug reported:
Brightness control key is broken on UX302LG laptop.
Other hotkeys work (as per Bug #1270661) .
Soft control works and is able to dim screen brightness.
- Key does not output anything using xev.
- Nothing shows up using acpi_listen when pressing the key.
Tried
** Package changed: nvidia-graphics-drivers-331-updates (Ubuntu) =
ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1270661
Title:
Wifi hotkey / LED (acpi) broken on UX302LG
To manage
Public bug reported:
SD card reader is dysfunctional in UX302LG laptop.
USB readers work without problem.
Nothing happens when pluggin SD/mSD/SDHC/mSDHC cards in the reader (might as
well use a piece of wood).
Nothing is listed in lsusb -v that could be the reader.
Nohting is listed in lspci
** Attachment added: lsusb.out
https://bugs.launchpad.net/ubuntu/+bug/1270676/+attachment/3952428/+files/lsusb.out
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1270676
Title:
SD Card Reader
(In reply to comment #5)
BTW, kernel 3.13rc8 must be working.
I just tried 3.13-rc8 from http://kernel.ubuntu.com/~kernel-
ppa/mainline/v3.13-rc8-trusty/ and it is NOT working : blank screen on
boot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
(In reply to comment #8)
(In reply to comment #6)
(In reply to comment #5)
BTW, kernel 3.13rc8 must be working.
I just tried 3.13-rc8 from
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.13-rc8-trusty/ and it is
NOT working : blank screen on boot.
Are you the original reporter
Created attachment 92047
dmesg of 3.13-rc8 on ux302lg with drm.debug=0xe
As requested, dmesg with debug activated using ux302LG and 3.13-rc8
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1265544
(In reply to comment #10)
(In reply to comment #9)
I'm not the original reporter of the bug, I have an identical machine :
UX302LG w/ the same issue: I'm the reporter of
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1265544 that helped/led
to this bugreport.
Thanks for verifying
Alberto: Thanks a lot, I will do the same, hopefully, the more, the merrier.
If you have any special details that you included that were not part of your
previous post, could you please send them by mail ?
Joseph: What are next steps for an eventual fix in 14.04 ?
--
You received this bug
Thanks a lot Alberto, this indeed could be it, I wonder what blocked this
upstream, maybe because it's a manufacturer issue that only can get patched
using a big fat ugly hack instead of having correct VBT...
I now understand better the use of the CSM/Non-CSM test since some laptop
apparently
Public bug reported:
Installing nvidia-331 or nvidia-331-updates (nvidia-current does not
support GPU from kern.log message), X fails to start / driver fails to
load properly.
Nouveau works OK with the haswell GPU upstream patch targetted there
** Attachment added: Xorg.failsafe.log
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331-updates/+bug/1268184/+attachment/3946375/+files/Xorg.failsafe.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: Xorg.0.log
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331-updates/+bug/1268184/+attachment/3946374/+files/Xorg.0.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: kern.log
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331-updates/+bug/1268184/+attachment/3946376/+files/kern.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The bug exists when only using nvida-331 and nouveau is blacklisted. Therefore
I would expect the nvidia card to be the default and only card visible but it
does not start.
It only starts if hd4000 is present (either because nvida-331 not installed or
with bumblebee that manages both).
I tried the config in bug #1267442 and since by forcing the nvidia card
to be the one used at lightdm it triggers an X failsafe display, I think
it might confirm the issue with nvidia-331 and the laptop.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I don't know what you did, I don't think we have the same configuration
or that the problems even relate (different computer, different GPU,
etc).
If you want to reverse your installation just either boot 'recovery' and
remove the packages that are in conflict (or try the standard boot with
The problem exists w/ bumblebee, w/o bumblebee, using primus, using
virtualgl and is exactly the same behaviour with the aforementionned log
messages.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hello,
problem is still present in the build 3.13.0-031300rc3.201401101125
representing commit 9b33600d52fab54df1aa82ea0d70c113060c293a : black
screen on boot.
Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hello,
thanks for the help.
The test kernel fixes the bla[cn]k screen on boot problem.
The test kernel does not fix the bla[cn]k screen when waking from
sleep problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hello,
there is still a as soon as the screen is getting dimmed, then it
doesn't light up on wake issue, in the kernel up to commit c26fe8e.
That issue is present in the nightly drm-intel-next build though that I
originally reported the bug with (2013-12-18), so it might not get fixed
by
The behaviour is exactly the same though (black screen w/ backlight on)
and from the comments on the drm-intel-next commits it would seem like
it's somewhat related eventhough it does not happen at the same time.
My very wild (and uninformed) guess would be that the code that fixed
the issue at
Thanks,
the problem is present in the latest build
3.13.0-031300rc3-generic_3.13.0-031300rc3.201401091408 representing
commit 1f2d45319922cdcf1f2a6f1f32f3afb206fdaaf7 : black screen on boot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Hello,
problem still present for
3.13.0-031300rc3-generic_3.13.0-031300rc3.201401072105 representing
commit e9cb81a22841908b1c075156b409a538d09c8466.
Thanks for the help !
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hello and thanks for the help.
IT WORKS.
I have display for the kernel 3.13.0-031300rc3-generic #201401081512
built against commit c26fe8e5eb34c18aa9ab60fcf4c3150663a52306
I will test the display dim/sleep issue and report.
Messages about driver/module error still present in Xorg.log (same as
Screen going dim still has a wake up issue.
Also, there is some discussions on the intel-gfx ML about a commit that
should have been pushed with c26fe8e5eb34c18aa9ab60fcf4c3150663a52306
but got squashed.
https://www.mail-archive.com/intel-
g...@lists.freedesktop.org/msg30489.html
So when
Just to confirm, problem still exists in 3.13.0-031300rc3 representing
commit c461562e84d180fb691af57f93a42bd9cc7eb69c.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1265544
Title:
8086:0a16
Hello,
thanks for the hard work, problem is still present in
3.13.0-031300rc2-generic_3.13.0-031300rc2.201401071301 representing commit
2a0a016addedd7a7ac489f10c89db503fadb334e
Onto the next !
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Thank you.
Problem still present for 3.12.0-031200 representing commit
ad071acb53110c8efd26ff1e5b5d57449b43833b.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1265544
Title:
8086:0a16 [UX302LG]
Using 3.2.54 under trusty, problem exist at boot, though terminal
console switched to automatically.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1265544
Title:
8086:0a16 [UX302LG] black screen on
Laptop is UEFI only, cannot boot/install 12.04.1 since apparently UEFI support
arrived in 12.04.2.
Also, there's no DVD drive in the laptop and I tried making a USB stick but
12.04.2+ images aren't recognized in the UEFI.
--
You received this bug notification because you are a member of Ubuntu
Finally found the Enable CSM option of the laptop that allowed to boot from
pre-UEFI devices.
I was able to test 12.04.1 and 12.04.3 in Live mode only (didn't
install/replace my trusty install) both using the 3.2.0.29 kernel and display
was _working fine_.
Do you still require Quantal testing ?
No, I cannot boot successfully using the 14.04 with Enable CSM option. For
reference CSM is only a pre-UEFI compatibility option in the UEFI :
http://wiki.phoenix.com/wiki/index.php/Compatibility_Support_Module and as
such, it has no apparent link to the display issue the laptop has.
Do you
The fix has been narrowed down to 16 commits from drm-intel-next on
2013-12-11. I might look into bisection sice it seem to be the only
solution to find the problematic commit, but it's a fairly important
ammount of work so I don't know when I'll do.
--
You received this bug notification because
Thanks for the help guys, if I'm provided with kernels for commits to
test I will make sure to report what works or not.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1265544
Title:
8086:0a16
I have the exact same issue with the laptop...
Tried the mainline kernel at http://kernel.ubuntu.com/~kernel-
ppa/mainline/v3.13-rc6-trusty/ but the behaviour was the same as with
3.12 : black screen on boot.
Had to revert to 3.13 drm-intel-next and it worked OK except when screen
is dimmed the
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1265544 submitted.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1263015
Title:
8086:0a16 [ASUS Zenbook UX302LG] Black screen on boot
To manage
Public bug reported:
Same description/workaround as
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1263015
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.12.0-7-generic 3.12.0-7.15
ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4
Uname: Linux 3.12.0-7-generic
Bug present in v3.13-rc6 from http://kernel.ubuntu.com/~kernel-
ppa/mainline/v3.13-rc6-trusty/ (cannot use Ubuntu-bug w/ that kernel
though).
** Tags removed: needs-upstream-testing
** Tags added: kernel-bug-exists-upstream kernel-bug-exists-upstream-v3.13-rc6
--
You received this bug
Christopher, no I don't.
Plus, it's important to note, the drm-intel-nightly doesn't _fix_ the issue,
it's merely a slight workaround allowing the system to boot, as mentionned in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1263015 as soon as the
screen goes blank, the system is lost
After further investigation drm-intel-nightlies up to 2013-12-11 work
but 2013-12-10 does _not_ work.
Hence issue/correcting commit has been made on 2013-12-11, but which of
the 16 ones, that I don't know.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
You might be able to WORKAROUND the dimming+freeze issue by disabling
screen dim in System Settings (which may have it's own systemd
WORKAROUND to get these to take). I'll let you comment further to this.
Yes, this was the easiest workaround but it forbids screen going down.
So issue is
I now use wicd instead of gnome-network-manager: I prefer the configuration
options and files offered by wicd and find the GUI way more user-friendly
and functionnal.
Since I am not planning on going back to gnome-network-manager soon, you'd
rather have someone else test this.
--tehownt.
On Wed
There are 2 outcomes to this bug:
1) Deny apt-get/aptitude the right to create the new menu.lst file and
thus have an unconfigured package forever.
2) Authorize apt-get/aptitude to create the menu.lst file and thus
configure the package correctly, then delete the file and manually
adjust
Public bug reported:
Binary package hint: linux-image-2.6.31-15-generic
Ubuntu 9.10 default installation uses Grub 2.0 which is configured using
the /boot/grub/menu.cfg but new kernel installation tries to find and
modify /boot/grub/menu.lst and thus fails.
ProblemType: Package
Architecture:
** Attachment added: AptOrdering.txt
http://launchpadlibrarian.net/35993226/AptOrdering.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/35993227/Dependencies.txt
** Attachment added: Dmesg.txt
http://launchpadlibrarian.net/35993228/Dmesg.txt
** Attachment
I totally agree, the only icon that makes sense is the Online one.
There should be a way to change those icons manually, so that they match the
user-decided theme. Is there a way to do that ?
--
User Switcher Applet (FUSA) icons do not match Pidgin
https://bugs.launchpad.net/bugs/294547
You
The same noticed with Intel 4965.
--
Network Manager Fails to Recover from Monitor Mode / Kismet / rfmon
https://bugs.launchpad.net/bugs/292230
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I think I found a workaround, I copied login.keyring to 'default' and
'default.keyring' not knowing which one the nm-applet was looking for.
Then rebooted, and instead of the usual Authentication Required By Wireless
Network window I got the Keyring access needed message windows on which I
had
96 matches
Mail list logo
