Hello,
after upgrading a mini-itx machine (VIA CLE266 chipset) from ubuntu 7.10 to
8.04 the machine began to freezing at boot time.
Before freezing, for a instant, the screen becomes green, then the display
shuts down (out of sync error).
I figured out that it was the VIA framebuffer driver
** Summary changed:
- HP t5000 - vt8623fb - memory size detection failed
+ Add vt8623fb to blacklisted framebuffer drivers
** Description changed:
-
- I have HP t5000 thin client. Everything works on Edubuntu 7.10 Classroom
Server.
+ I have HP t5000 thin client. Everything works on Edubuntu
Public bug reported:
With an NVidia GeForce 8600M GT I'm experiencing huge performance issues
with every opengl program.
- Compiz effects are terribly slowly and they move jerkly
- Some opengl app is completely broken, for instance meshlab (
http://meshlab.sourceforge.net/ ) or the QtOpenGL
** Attachment added: 3dmodelviewer.png
http://launchpadlibrarian.net/15995659/3dmodelviewer.png
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/15995660/Dependencies.txt
--
opengl performance issues and rendering bugs with a GeForce 8600M GT
Just did it. I installed the latest nvidia drivers with the envyng-gtk
interface, but the issues are still the same.
--
opengl performance issues and rendering bugs with a GeForce 8600M GT
https://bugs.launchpad.net/bugs/248149
You received this bug notification because you are a member of
This is just horrible.
Please raise the severity to critical, since this is a major
malfunction.
And please blame the translation teams or whatever causes this bug to depend on
the localization.
Why the heck there's no It's used by 5 pieces of installed software in
Italian?
HOW is it possible
Public bug reported:
Start any application using QDockWidgets (f.i. the stock mainwindow
demos that come with Qt), and dock/undock dockwidgets. Frequently the
whole panel disappears, forcing a killall unity-2d-panel to get it back.
Description:Ubuntu 12.04.3 LTS
Release:12.04
This is still open for Ubuntu 16.04, by the way (confirmed on a GTX
970).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1313539
Title:
[DisplayPort] monitor shows black screen and "no input signal"
Public bug reported:
I have two monitors (in the logs: DP-2, DP-4) and one beamer (HDMI-0)
connected to this computer via a GTX 970.
Since this computer is used as a presentation device, I want to
configure the beamer output to mirror one of the two monitors, so that
the presenter can see what's
Public bug reported:
This is mirroring Debian bug #808086 https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=808086
Compiling any source file that includes with clang 3.8 and
-std=c++11 -stdlib=libc++ results in a compile error.
While this is a minor bug in Debian (as it doesn't ship 3.8 yet),
Guys, this is a serious bug. (In Debian it would be called "important").
Could you please just upgrade to wget 1.18, or at least backport
http://git.savannah.gnu.org/cgit/wget.git/commit/?id=7099f4899880eaefc2c40a3dc7693ab4174a819b
so that wget stops being unusable for ordinary usage?
--
You
Something else I noticed when doing a 14.04->16.04 upgrade: the damn
indicator-appmenu package was missing! Installing that brought in the
unity-gtk module, which solved the issue for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
After installing certain updates (kernel, system libraries, etc.), the
"The computer needs to restart" dialog appears periodically, prompting
the user to restart the system.
That dialog eats a constant 8-10% of CPU time. That's the issue. (Yes,
update-manager is niced to 10,
Hi Brian,
do you know some way to get a good backtrace for your purpose? Note that
this is 100% reproducible, just run update manager, and even if it tells
you that the system is up to date, switch window focus to somewhere else
to trigger the 8-10% CPU usage.
A quick gdb -p PID and bt doesn't
Public bug reported:
The scenario is this:
* Multiple windows of the same application are opened
* Some of them are fullscreen
* The user clicks the application icon in the side tray, starting the window
switcher for it (so that the user can select a certain window)
This last step actually
Qt-based testcase is attached.
Instructions:
* Unpack, qmake, make
* Run the application at least twice, making at least one fullscreened
* Trigger the window switcher by clicking on the Unity's sidebar
The fullscreened one will print a wrong resize event. E.g.:
Resized to QResizeEvent(2880,
Public bug reported:
In Ubuntu 16.04.2, after upgrading nvidia-375 to
375.66-0ubuntu0.16.04.1, bumblebee stopped working. Attempting to launch
anything with primusrun results in errors.
Upstream bug report seems to be pointing at a flaw in
/usr/lib/nvidia-375-prime/ld.so.conf , that's why I'm
Yes. It's likely caused by some broken code calling update() in a loop
or something like that. Yet, we're looking at a 30-40% aggregated
between the app, X and compiz.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
In that case, X usage goes down, and of course compiz isn't there any
more, but the dialog is still eating CPU. I don't know anything about
GTK nor python, so I don't really know how to track this down, otherwise
I would've already done that...
--
You received this bug notification because you
Seems to be working just fine here, thank you very much!
Verification steps:
1. Get a C++11 source file that #includes :
#include
int main() {
std::string s{"foobar"};
}
2. compile it with clang++ -stdlib=libc++ -std=c++11
3. if it compiles (which now it does) the bug is fixed.
--
You
This is still valid, by the way.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1700672
Title:
bumblebee / primusrun does not work with NVIDIA 375.66
To manage notifications about this bug go to:
Hello,
Xenial is still affected by this AFAICS. And yes, I'd like it to be
fixed there.
17.04/17.10 shouldn't be affected, as they're using libc++ 3.9.1 which
has fixed the corresponding bug in Debian. (No idea about ~ubuntu-
sponsors, to be honest...).
--
You received this bug notification
Added the SRU info, added ~ubuntu-bug-control.
** Description changed:
This is mirroring Debian bug #808086 https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=808086
Compiling any source file that includes with clang 3.8 and
-std=c++11 -stdlib=libc++ results in a compile error.
Could also someone set the severity to High? As per:
"Renders essential features or functionality of the application or
dependencies broken or ineffective "
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi,
Unfortunately I'm still on 16.04, waiting for 18.04.1 to upgrade, so I
can't test the proposed right now...
Thanks for all the effort at fixing this annoyance!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Launching any application in the Nvidia Linux Graphics Debugger does not
work with the Ubuntu packaged drivers, but it works by manually
installing the Nvidia upstream drivers (same version). A packaging issue
is the likely issue of this.
Steps to reproduce:
1) install
Actually, sorry, I misread the dates on the changelog. hplip has never
been upgraded since March 2016, not 2017. So, yes, it's been 2 years
without any update for new printers.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Could this bug please be reopened, against 16.04? This is not fixed
there.
hplip used to have regular updates in 16.04 as part of SRU, in order to
support new printers that become available on the market, but for some
reason this stopped ~1 year ago. It would be *really* great to get again
Still an issue with 384.90. In Xorg8.log I see
[272208.772] (II) Loading /usr/lib/nvidia-384/xorg/libglx.so
[272208.773] (EE) Failed to load /usr/lib/nvidia-384/xorg/libglx.so:
libnvidia-tls.so.384.90: cannot open shared object file: No such file or
directory
[272208.773] (II) UnloadModule:
I've just faced this bug, which made the 18.04 to 20.04 upgrade fail. It
seems that, after upgrading, DKMS tries to build LTTNG modules for the
18.04 kernel (4.15), which doesn't work.
A possible workaround is to remove this package before the upgrade, and
reinstall it afterwards.
--
You
(Sorry, I meant, WHILE upgrading. The upgrade leaves the 18.04 kernel
installed, and also installs the 20.04 kernel. DKMS then tries to build
LTTNG modules for both kernels, failing.)
Could it be possible to please mention this bug on
https://wiki.ubuntu.com/FocalFossa/ReleaseNotes ?
--
You
Public bug reported:
Hi,
Valgrind shipped with focal does not support the sched_getattr and
sched_setattr syscalls, resulting in output like
--1234-- WARNING: unhandled amd64-linux syscall: 315
--1234-- You may be able to write your own handler.
--1234-- Read the file
Is this a duplicate of #1863434 ?
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1863434
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1836934
Title:
eoan boot hides grub menu
To manage
I have just upgraded from 18.04 to 20.04.2. 18.04 did not have this
problem and simply showed G
I'm affected by this bug as well. I have a Lenovo W550s; after the BIOS
checks (which just show the Lenovo logo), GRUB does not appear (but the
Lenovo logo is still visible). However, GRUB is there,
Might be a duplicated of 1836934 .
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1836934
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1863434
Title:
20.04 grub menu not visible
To manage
Public bug reported:
Description:Ubuntu 20.04.3 LTS
Release:20.04
thunderbird:
Installed: 1:91.5.0+build1-0ubuntu0.20.04.1
Candidate: 1:91.5.0+build1-0ubuntu0.20.04.1
After the upgrade to Thunderbird 91, the dark theme settings are not
honored in several places:
* when reading
36 matches
Mail list logo
