Public bug reported:
Symptoms: attaching gdb to any program that uses pthreads will result in
fatal errors like "Cannot find user-level thread for LWP 192701: generic
error"
The upstream bug is
https://sourceware.org/bugzilla/show_bug.cgi?id=27744
It looks like the fix has already been adopted i
It's definitely not (directly) related to either of those - I can't even
get the display to come back on, let alone enter a password at the lock
screen.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/17
Public bug reported:
I'm using a laptop with no external monitors attached (System76 Oryx Pro
2016).
After the screen is locked (either manually or via timeout) and it
blanks/deactivates the screen, the display remains deactivated and my session
is unrecoverable.
(I can still ssh into the machi
Same experience as #40 after installing updates on 16.04 today.
I already have the workaround from #4 applied.
The workaround from #35 appears to still work, thankfully.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
FWIW, my networks were not hidden.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1390709
Title:
Wifi doesn't reconnect after waking from sleep
To manage notifications about this bug go to:
https://
I got this after accidentally starting the bluetooth service while playing
audio via a2dp.
The hackaround from #4 worked for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1490349
Title:
15:10 a
Does it create the symlink for /usr/lib/i386-linux-gnu/libGL.so on a
multiarched amd64 system yet?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1246013
Title:
Would be nice for libgl1-mesa-dev to b
Also affects me on a clean 16.04 installation.
Neither cgmanager nor libpam-cfgs were installed, let alone running.
The workaround from comment #42 works here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
Bug persists with nvidia-361.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1455617
Title:
External HDMI connection fails after upgrade from nvidia-340
To manage notifications about this bug go to:
On Ubuntu 15.10, the proposed rule (KERNEL=="uinput", SUBSYSTEM=="misc",
TAG+="uaccess"), which was preapplied on my system, doesn't fix the
issue (of permissions on /dev/uinput) for me - I still need to either
manually chmod it or add a custom udev rule that sets the mode.
--
You received this b
Still occurs on 15.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1342400
Title:
avahi-daemon constantly reporting "Invalid response packet from host"
To manage notifications about this bug go to
Bug persists with nvidia-355.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1455617
Title:
External HDMI connection fails after upgrade from nvidia-340
To manage notifications about this bug go to:
If I recall, I worked around it by enabling one of the workarounds in the
"OpenGL" section in CCSM.
Difficult to say - it was 2 years ago...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1244225
Titl
FWIW, it looks like the windows drivers at
http://www.killernetworking.com/support/driver-downloads contain patch
and ramp files that look like they should match (at least, the names are
correct). However, the binary format doesn't appear to match the other
patch and ramp files (e.g. the last 8 byt
Ugh, my mistake - I inadvertently tested before rebooting with the new
driver. Bug persists with nvidia-352. :-|
** Changed in: nvidia-graphics-drivers-346 (Ubuntu)
Status: Fix Committed => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
Appears to be fixed in nvidia-352 (xorg-edgers).
** Changed in: nvidia-graphics-drivers-346 (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1455617
Title:
Public bug reported:
The computer in question is a retina macbook pro 10,1.
I have a television that I normally connect to via the builtin HDMI port.
After the upgrade from Ubuntu 14.10 to Ubuntu 15.04 (and thus to the nvidia-346
driver), the television no longer recognizes the connection from th
I have the same symptoms after upgrade from 14.10 to 15.04.
I'm attaching my ubuntu-bug output, but I can file a new bug if this is
adjudged a different issue.
** Attachment added: "apport.network-manager.fmm523w1.apport"
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1390709/
In that case, I have no idea how I'm supposed to remove allowed actions using
this atom.
Reading the specification makes me think that passing a list that doesn't
include _NET_WM_ACTION_RESIZE should cause it to be removed from the list:
'Atoms present in the list indicate allowed actions, atoms
Public bug reported:
According to http://standards.freedesktop.org/wm-spec/latest/ar01s05.html :
Atoms present in the list indicate allowed actions, atoms not present in the
list indicate actions that are not supported for this window. The Window
Manager MUST keep this property updated to reflec
I experienced this problem as well, with 340.24-0ubuntu1~xedgers14.04.1.
Disabling the FXAA setting in nvidia-settings and restarting X worked around it
for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
*** This bug is a duplicate of bug 1246013 ***
https://bugs.launchpad.net/bugs/1246013
Nice find, registering with that one instead.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1317113
Title:
The bug still occurs (and the posted workaround still applies) with
kernel 3.13.0-24.47.
** 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/b
I can confirm that this bug affects me as well with -29, but not with -24.
I tried the 03131102 mainline kernel, but the DKMS step failed for nvidia-337
with that one.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
Public bug reported:
This means that if I want to compile a Gtk+ program for x86 on an amd64
machine, I need to install libgtk2.0-0:i386 and then manually symlink:
libgtk-x11-2.0.so libgdk-x11-2.0.so libatk-1.0.so libgio-2.0.so
libpangoft2-1.0.so libpangocairo-1.0.so libcairo.so libpango-1.0.so
li
Btw, I wasn't able to report this using ubuntu-bug: I get the message
"This is not an official Ubuntu package..."
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1317113
Title:
libgl1-mesa-dev is not
Public bug reported:
This means that if I want to build an x86 program that uses libGL on an
amd64 system, I need to install libgl1-mesa-glx:i386 and then manually
symlink /usr/lib/i386-linux-gnu/libGL.so
$ sudo apt-get install libgl1-mesa-dev:i386
Reading package lists... Done
Building dependenc
Missed comment #9. :-|
The workaround is still required in 14.04, using nvidia-337 from
ppa:xorg-edgers.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1243897
Title:
[MacBookPro10,1] brightness set
Public bug reported:
After installing Ubuntu 13.10 desktop amd64 alongside OSX (using the default
choices along with "Install Ubuntu alongside Mac OSX") on a retina macbook pro,
Ubuntu doesn't appear in the Apple boot menu (the one that appears when holding
Alt/Option at boot).
I worked around
Setting back to "New" - I responded to the feedback.
** Changed in: compiz
Status: Expired => New
** Changed in: unity (Ubuntu)
Status: Expired => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
Re: #7
Yes!
Is this something that's safe to put into a startup script for now, or should I
just run it when I need to?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1243897
Title:
MacBookPro10,1
I'm using nvidia-319.
What is the "correct" driver?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1244225
Title:
Display is unrefreshed/corrupted when opening/closing/switching
windows and tabs
T
I confirm that disabling unity addons in firefox and restarting unity-
panel-service and hud-service greatly reduced their memory usage.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/987060
Title:
m
I was using 310 in 13.04 (and possibly 304 before that; can't remember)
- in that case, the brightness control worked intermittently for each
suspend/resume cycle. The behavior has become consistent in 13.10;
unfortunately, it's consistently the "not responding" case.
I can't even get X to start (
The nvidia driver wrapper doesn't build with that kernel (make.log
attached).
** Attachment added: "DKMS make log for nvidia 319.32-0ubuntu7"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1243897/+attachment/3890088/+files/make.log
** Tags added: kernel-unable-to-test-upstream
** Cha
Public bug reported:
When I switch between windows, or switch between tabs in the same
window, or switch desktops, part or all of the affected windows often
fail to repaint (or repaint and then revert to "stale" content).
Unfocusing/refocusing the affected window usually forces it to repaint
again
Public bug reported:
After upgrade from 13.04 to 13.10, setting the screen brightness has no
effect (either via the hotkeys, "Brightness & Lock" settings, or via
/sys/devices/pnp0/00:07/backlight/gmux_backlight/brightness ).
I'm using nvidia driver 319.32-0ubuntu7.
I've tried Option "RegistryDwor
Issue still exists in 12.04 final, compiz-plugins-main
1:0.9.7.0~bzr19-0ubuntu10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/946609
Title:
Unfolding the desktop cube corrupts desktop
To manage no
It does behave in 11.10, though.
If it's not maintained, why is it in the -main package?
Is there a replacement, or did people go back to letting desktop switches be
dull?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/946609
Title:
Unfolding the desktop cube corrupts desktop
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/
Public bug reported:
Unfolding the desktop cube (Compiz desktop cube plugin, default
keybinding ctrl-alt-down) results in a blank, white unfolded cube, after
which I'm unable to get back to a usable desktop.
Dropping to a virtual console and back appears to work around the issue
once it occurs.
Debugging should just work, provided that you have the gdb debugger
backend (monodevelop-debugger-gdb on ubuntu). Are you able to debug C
programs from MD?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
This is fixed in MD master upstream:
https://github.com/mono/monodevelop/commit/8c5a20147b70094831d3519352bd70ca5149a2c2
--
Monodevelop has unhandled exception when trying to add an XML schema
https://bugs.launchpad.net/bugs/612334
You received this bug notification because you are a member of Ub
43 matches
Mail list logo
