bbswitch is a module for Optimus laptops, not desktops (except an odd,
single all-in-one). The i7-3770 is a desktop processor, so bbswitch will
not work here.
** Changed in: bbswitch (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of
It seems that you have no kernel headers installed for that version.
When installing the kernels from Ubuntu Mainline Kernel PPA, be sure to
install the linux-headers- package too.
** Changed in: bbswitch (Ubuntu)
Status: New = Invalid
--
You received this bug notification because
(In reply to comment #23)
[..]
I know it is a DIFFERENT BUG from this one, but I still wanted to ask if
after kernel 3.14 OpenGL 3.1 works for anyone. And is there any other way of
testing if it actually works other than in kwin?
Please open a new bug, I can confirm that KWin
The problem disappeared with:
KDE 4.13.0
Linux v3.15-rc1-356-gebfc45e
Mesa 10.1.1
Not sure which of the three is responsible though.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1299499
I think you got your versions reversed. On this laptop, kdebase-
workspace 4.11.8 (includes KWin) and kdebase-runtime 4.13.0 are
installed.
Perhaps you can try with a newer kernel?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in
Indeed, I forgot to consider that possibility because Arch normally does not
patch that much:
https://projects.archlinux.org/svntogit/packages.git/tree/trunk/workaround-for-robustness-and-reset-with-intel.patch?h=packages/mesa
--
You received this bug notification because you are a member of
Public bug reported:
When NetworkManager is configured to assign a link-local IPv4 address to an
interface, it ends up with a global scope. This happens in two cases:
- Configure method=link-local
- Configure method=manual, addresses1=169.254.x.x;16:0.0.0.0
$ ip link show dev iface # for
ILK is indeed affected. I (OP) forgot to mention my hardware. Some more
details:
CPU: i5-460M (Ironlake GPU)
libdrm: 2.4.52-1
libdrm master contains only some fixes for Freedreno, a FreeBSD platform
fix and a change in the test suite. I believe that updating libdrm in
Ubuntu won't help in this
Looks like the issue entered in 331.20-0ubuntu7. From the changelog[1]:
+nvidia-graphics-drivers-331 (331.20-0ubuntu7) trusty; urgency=low
+
+ * debian/rules, debian/templates/control.in,
+debian/templates/nvidia-graphics-drivers.dirs.in,
+
This chip was supported long time ago, I cannot remember which exact
version.
** Changed in: xserver-xorg-video-nouveau (Ubuntu)
Status: Incomplete = Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
(In reply to comment #12)
Using upower 0.9.23-2 on Debian, I still have this issue:
[..]
The battery level is wrong and sometimes fluctuate (between 1%; 20% and 55%).
Currently the battery is almost full (thanks to the LEDs on the mouse) and
the battery level only indicates 20%.
The
Thanks for merging. Martin, note that the battery percentage may still
show as 0% if a device was unavailable when UPower starts, but in that
case the state is unknown. Applications should check the state before
using percentage.
--
You received this bug notification because you are a member of
Heads-up: I noticed that the K800 reports 0% while charging (0 means
unknown level). I think this is unfixable in UPower and that
applications should not warn when a device is charging and the
percentage is 0.
This also messes up history, if you expected a nice history with a
climbing percentage,
(In reply to comment #114)
Yes, it is xf86-video-intel. I am running it with the current version of
Debian/sid + this patch now (2.20.14-1 + the patch)
Is it a standalone patch or does it depend on the former DRM patch? Anyway, I
have tested it with 3.7.1 + i915.i915_enable_rc6=1 and it still
(In reply to comment #116)
the rc6 needs to be disabled *in*any*case*, that is known by now.
And it is a standalone patch of xf86-video-intel. Did you recompile it?
With rc6 disabled I cannot trigger the bug. Yes, I recompiled and restarted X.
[reply to comment 111]
I tried to apply
, KWin uses OpenGL compositing
- Kernel: 3.7.1 (config
https://raw.github.com/Lekensteyn/aur/master/linux-custom/config + watchdog
patch)
- SSD: Intel 320 80G (/boot + LUKS-encrypted filesystem)
- CPU: i5-460M
- RAM: 8G
My rc6-enabled hang could be triggered by copying a Linux source from
the SSD
(In reply to comment #118)
[/usr/src/git-kernel/linux-2.6] grep -rn drm_mm_hole_node_end
Binary file drivers/gpu/drm/drm.ko matches
...
I saw that, but I have a symbol with a __ prefix.
Looking at the comments, there are two versions of that patch. comment
105 and comment 111 (v3). I guess you
[reply to comment 107]
I haven't tried it yet, do you still want me to test it?
[reply to comment 108]
I cannot apply it on top of 3.7.1. What base do you want me to test it on?
[reply to comment 109]
Do I need to apply this to xf86-video-intel? If yes, which version/commit?
[reply to comment
i915.i915_enable_rc6=0 unables me to trigger the bug. With the patch
applied on top of 3.7-rc7, the bug is still not exposed (as expected).
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
With http://cgit.freedesktop.org/~ickle/linux-2.6/commit/?h=bug55984,
the situation does not change, i.e. still lockup message and vanishing
3D capailities.
(this bug is still marked NEEDINFO, do you need more details?)
--
You received this bug notification because you are a member of Desktop
I don't remember having this issue in Precise, I guess it can be closed.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/786229
Title:
NetworkManager fails to connect to
For those affected and do not use a solution like Bumblebee
(https://github.com/Bumblebee-Project/Bumblebee), please run:
update-alternatives --force --set i386-linux-gnu_gl_conf
/usr/lib/i386-linux-gnu/mesa/ld.so.conf
If you're running a 64-bit system, run:
update-alternatives --force
** Bug watch added: GNOME Bug Tracker #661635
https://bugzilla.gnome.org/show_bug.cgi?id=661635
** Also affects: gconf via
https://bugzilla.gnome.org/show_bug.cgi?id=661635
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of
23 matches
Mail list logo
