Seems some people here are using the DisplayLink driver offered by the
company for USB3-based DL-devices. I ran into this bug using the udl
driver, since I'm using a DL-device based on one of the older USB2
DisplayLink chipsets. Confirmed the problem in Mint 20.1 and Ubuntu
20.04.2. In Ubuntu, I
This problem persists on the same system with all the latest updates. I
did however notice that in the "hardware" part of the GUI there is no
longer a "2.1" option, so defaulting to analogue stereo output.
I tried connecting an external speaker ("headphone") and it sounded as
it should.
--
You
Public bug reported:
It seems the 2.0 speakers get mapped to Speaker and the subwoofer is
mapped to HEADPHONES, not LFE. I confirmed this by raising the volume
for "headphones" in alsamixer and getting the base to play along.
However, there seems to be no workaround in Ubuntu just using the
** Also affects: firefox (Ubuntu)
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/1650381
Title:
Slow scrolling in Firefox and slow Youtube-playback with
I discovered that both scrolling and Youtube-playback (HTML5) works just
fine in Chromium, both in Ubuntu 16.10 and Mint 18.1 (which is built on
16.04). So perhaps this is a Firefox bug?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I scrapped the two 6715s I had and can no longer test them.
/ Carl
Den 20 dec 2016 18:25 skrev "Christopher M. Penalver" <
christopher.m.penal...@gmail.com>:
> Carl Englund, please see
> https://community.ubuntu.com/contribute/support/irc/ .
>
> In addition to the b
** Summary changed:
- Slow scrolling in Firefox and slow Youtube-playback with Radeon RV
+ Slow scrolling in Firefox and slow Youtube-playback with Radeon RV730
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
I first discovered this problem in Mint 18.1 Cinnamon (64-bit) and Mint
18 XFCE (64-bit). I enabled Glamor (and thus, it seemed DRI3) and tried
turning off smooth scrolling and/or hardware support in Firefox, but to
no great avail. Interestingly, scrolling worked nice and
I could use some help, but nobody answered. Is there some IRC channel I
should turn to instead?
https://ubuntuforums.org/showthread.php?t=2338146
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1611536
Tested 4.8-rc8, problem remains
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1611536
Title:
Fan on full speed without noapic or nolapic on HP 6715s
To manage notifications about this bug go to:
I made a mistake, 4.4.0-34 does not boot with normal fan speed without
noapic. Instead, it seems the change/break appears between 4.2.3 and
4.2.4. I will try to bisect there. Here is the updated list:
4.1.0: fan ok, 32-bit FADT
4.1.1: fan ok, 32-bit FADT
4.1.2: fan ok, 32-bit FADT
4.1.3: fan ok,
I have done some testing of different kernels from the mainline
repository, omitting the noapic parameter to see if they start and how
the fan behaves. This is the result. Kernels using 64-bit FADT cause the
machine to malfunction, as per:
Tested 4.8.0 rc2, problem persists.
** Attachment added: "480rc2.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1611536/+attachment/4725156/+files/480rc2.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Tags added: kernel-bug-exists-upstream
--
You
Reported separate bug for noapic nolapic here:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1611536
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1590154
Title:
System slow unless using
Public bug reported:
Without adding noapic or nolapic to boot parameters the fan will run on
full speed, the system is sluggish (can almost see windows redrawing on
screen). On some kernel versions tested, rebooting also fails.
The parameter(s) were not required in Trusty. I also tested some
I can confirm 4.8.0 rc1 works great with noapic/nolapic and
"acpi_force_32bit_fadt_addr". Without the last parameter it uses 64-bit
FADT adress and the problem occurs.
Interestingly, mainline kernels 4.3.6, 4.2.8 and 4.1.29 seem not to
honor the parameter and use 64-bit adress no matter what.
--
I did some further testing and it seems I have found a culprit and a
solution. In older kernel versions (3.19.8 and 4.0.9 worked flawlessly
without extra boot parameters) I get something like this when booting:
ACPI BIOS Warning (bug): 32/64X address mismatch in
FADT/Pm2ControlBlock:
I did get the system to boot in 4.4.0-34 without noapic and nolapic -
but the fan was running on full (separate issue?). However, the system
seemed even slower than when booting WITH said parameters.
4.8 rc1 failed to boot without noapic nolapic, however fan was also on
full.
--
You received
Problem remains in 4.8 rc1.
** Tags removed: kernel-bug-exists-upstream-4.7-rc2
** Tags added: kernel-bug-exists-upstream-4.8-rc1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1590154
Title:
Did a part of the command fall off? I changed the last part to "bios-
release-date". Here is the output:
68YTT Ver. F.20
12/01/2011
The last kernel version that worked fine is in my Trusty install on a
separate partition, kernel 3.19.0-59. There, the boot parameter
"acpi_force_32bit_fadt_addr"
I found a smart way to upgrade the BIOS, so now it's up to date, F.20. I
tested 4.4.0 and 4.7-rc2 again but I'm afraid the results were the same
:-(
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Yes! 4.7-rc2 booted (with noapic and nolapic) but the slowness-problem
still remains there, tested with the disk utility again.
I tried to boot without noapic and nolapic but the computer seemed
really slow and the graphical environment never came up. I was able to
switch to console and reboot
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Tags added: kernel-bug-exists-upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1590154
Title:
System slow unless using
** Attachment added: "Fail to boot, readable output"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1590154/+attachment/4679853/+files/readable.JPG
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Tested kernel mentioned in #3:
With noapic, nolapic:
Fails to boot, with readable output
Without noapic, nolapic:
Fails to boot, with unreadable output (but supposedly the same content?)
** Attachment added: "Unreadable, screenshot"
Public bug reported:
I tested this installing the Disks tool and running a read-only
benchmark. The transfer rate is very slow (2-3 MB/s) unless I'm moving
the cursor, then it jumps up.
As I understand this could have something to do with triggering/handling
interrupts. In this context it might
I added the "proposed" source and from there installed kernel 3.19.0-46
(using Synaptic). Booted with acpi_force_32bit_fadt_addr and system
froze.
I get the feeling this kernel wasn't the one I was supposed to be
testing with. Could it be because I am on Trusty? Is the proposed kernel
released to
Issue started after fresh install, no knowledge of earlier kernels.
Laptop is currently broken and unavailable for testing, it suddently
died in the middle of normal usage. Ruled out memory and reseted BIOS.
Unsure of reason for malfunction but suspecting solderings. Will perhaps
try baking in
Public bug reported:
After install and updates this laptop still becomes VERY hot. I
installed indicator-sensors to get a handle on the temperature and it's
hovering at about 80C without much load at all.
I managed to work around this by adding "radeon.runpm=0" to boot options
and adding to
My post to the developers:
http://marc.info/?l=linux-acpi=145186512903943=2
Reply:
http://marc.info/?l=linux-acpi=145191133113281=2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1529381
Title:
Bug submitted to bugzilla.kernel.org as per developer instructions:
https://bugzilla.kernel.org/show_bug.cgi?id=110451
** Bug watch added: Linux Kernel Bug Tracker #110451
http://bugzilla.kernel.org/show_bug.cgi?id=110451
--
You received this bug notification because you are a member of
I got it! If I didn't mess it up but I don't think so.
Side question: do you have to do "fakeroot debian/rules clean" for every
step when bisecting? The guide was a bit unclear on that. I was just
thinking the compile process might be quicker if I didn't do clean in
between..
Done. 4.4.0-040400rc7 tested:
- Message about loading initrd image or somesuch.
- Screen goes black.
- Fan goes to full speed.
- HD light lit for about 15 seconds or so, then goes dark.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi! Bisecting stuff is new to me - I'm not sure I did it the right way,
but..
..I tested precompiled kernel commits found via a link in the Kernel
bisection guide. My results are:
3.19.0-26.27 doesn't boot
3.19.0-25.26 boots normally
** Changed in: linux (Ubuntu)
Status: Incomplete =>
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1529381/+attachment/4540776/+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/1529381
Title:
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1529381/+attachment/4540782/+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/1529381
apport information
** Tags added: apport-collected
** Description changed:
To reproduce (on this hardware)
1) Install 14.04.3 LTS (Ubuntu or XUbuntu)
2) Install updates
3) Reboot
The kernel used after update is 3.19.0-42. Booting with the kernel that
came with the install
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1529381/+attachment/4540781/+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/1529381
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1529381/+attachment/4540785/+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/1529381
apport information
** Attachment added: "BootDmesg.txt"
https://bugs.launchpad.net/bugs/1529381/+attachment/4540775/+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/1529381
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1529381/+attachment/4540777/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1529381/+attachment/4540779/+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/1529381
Title:
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1529381/+attachment/4540780/+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/1529381
Title:
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1529381/+attachment/4540783/+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: "UdevLog.txt"
https://bugs.launchpad.net/bugs/1529381/+attachment/4540787/+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/1529381
Title:
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1529381/+attachment/4540784/+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/1529381
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1529381/+attachment/4540786/+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/1529381
Title:
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1529381/+attachment/4540778/+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/1529381
Testing 4.4-rc6 had the difference in result that after the fan went on
max speed (unlike when booting on 3.19.0-25) and hdd was working - after
a while the blue XUbuntu screen with the spinning wheel came up. After
that the screen went black again and hdd stopped.
4.3.3 was same result but
Tested 3.19.0-23 just to make sure..and yes, it works. Everything I've
tested after 3.19.0-25 doesn't.
** Tags added: kernel-bug-exists-upstream-3.19.0-26 kernel-bug-exists-
upstream-3.19.0-42 kernel-bug-exists-upstream-4.2.0-22
** Tags added: kernel-bug-exists-upstream-4.3.2
--
You received
What should I do to complete the bug report?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1529381
Title:
Updating 14.04.3 to latest updates renders system unbootable
To manage notifications about
Public bug reported:
To reproduce (on this hardware)
1) Install 14.04.3 LTS (Ubuntu or XUbuntu)
2) Install updates
3) Reboot
The kernel used after update is 3.19.0-42. Booting with the kernel that
came with the install image (3.19.0-25) works fine.
This computer is a HP Compaq 6715s. I have
I did some testing using different kernels:
3.19.0-26, no boot.
- ACPI PCC error on screen, disappears after a few seconds
- Black screen, normal fan, no HDD activity
- Ctrl+alt+del doesn't work
3.19.0-42
- ACPI PCC error on screen, disappears after a longer time
- HDD works longer before
Haven't had time to experiment for a while. However, I just upgraded to
Wily 15.10 (with updates) and the machine froze just as before. Will
report when I have again tried the latest mainline kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
#5 didn't solve, still has to reload wl now and then returning from
suspend.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1466994
Title:
bcmwl stops working after resume from suspend
To manage
I had the same problem solved with the same change (128M - 256M) on
15.04 amd64 running on a laptop. Should I open a separate bug?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1359980
Title:
Installing 6.30.223.248+bdcom-0ubuntu3 (from Wily) seems to solve the
problem 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/1466994
Title:
bcmwl stops working after resume from suspend
To
Getting kernel panic every third or fourth resume.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1466994
Title:
bcmwl stops working after resume from suspend
To manage notifications about this bug
Bug occurred again, does seem to exist even after reinstalling driver.
** Changed in: bcmwl (Ubuntu)
Status: Invalid = New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1466994
Title:
bcmwl
** Description changed:
After 10 min or so, or an hour. The freeze happened also when using the
performance (max freq) governor.
-
- WORKAROUND: Lock the CPU freq to something.
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: linux-image-3.19.0-18-generic 3.19.0-18.18
The sysrq+alt+1 and sysrq+alt+t had no effect. No sign of anything in
kern.log or kern.log.1 after reboot. SSH doesn't work either.
** Attachment added: Photo of screen
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1458569/+attachment/4417979/+files/DSC04561.JPG
--
You received this
Other times the screen just freezes without becoming white. There is
however a very quick flicker of white it the lower part of the screen
before this happens.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Problems seems to be solved after removing and reinstalling driver!
** Changed in: bcmwl (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1466994
Title:
bcmwl
Public bug reported:
Should this be reported against kernel instead?
The driver worked fine in 14.10. Since 15.04 module needs to be reloaded
after suspend for wlan to work again.
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu2
I just had a freeze using rc8 BUT it happened when I was also using the
performance governor - that is, no CPU cycling going on.
** Tags removed: kernel-bug-exists-upstream-4.1-rc6
** Tags added: kernel-bug-exists-upstream-4.1-rc8
** Description changed:
After 10 min or so, or an hour.
-
** Description changed:
After 10 min or so, or an hour.
Workaround seems to be locking the CPU freq to something. I'm guessing
there might be a bug in the powernow-k8 driver that exhibits itself in
- systems with the XPRESS 200M CPU chipset.
+ systems with the XPRESS 200M GPU chipset.
Tested! System still freezes as before.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1458569
Title:
System freezes randomly
To manage notifications about this bug go to:
Have been trying vmlinuz-4.1.0-040100rc5-generic for about a week, using
the laptop for maybe 2h a day, mostly just running Facebook. I was
starting to hope but it froze again today. I was hammering ctrl+alt+f2
in hope of a console just after that, and to my surprise it switched
(but not
Will continue to test with the powersave governor. For some reason just
setting the frequency and userspace governor doesn't seem to work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1458569
Title:
Moved card to other 14.04/386 machine and have been unable to reproduce.
Suspect hardware compatibility problems or overheating.
** Changed in: xserver-xorg-video-nouveau-lts-utopic (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Problem remains on 15.04 amd64 with latest updates
** Package changed: xserver-xorg-video-ati-lts-utopic (Ubuntu) =
xserver-xorg-video-ati (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
I'm not sure if this should instead be tagged on linux/kernel or not.
Blacklisting the nouveau module keeps system going, otherwise it crashes
after a short while of usage.
At some point I was lucky and managed to switch to console before the
system froze completely (seems
Public bug reported:
I think software-properties should be tagged in this since it offers to
install nvidia-173 (but fails to do so). One of these two packages
should be changed so that the driver is installed or so it isn't
offered.
Terminal output:
root@sempron:~# LANG=EN apt-get install
Forgot the command output: root@emmas:~# sudo dmidecode -s bios-version
sudo dmidecode -s bios-release-date
68DTT Ver. F.13
09/08/2008
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1458569
Title:
Thanks for the tip! I had forgotten about updating the BIOS because it
was such a hassle, but I finally got it done.
Unfortunately, the problem remains. I got a whitescreen today after
about 20-30 minutes of usage.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
This happened to me today on XUbuntu 15.04 final with updates. It seems
to stay on hogging as much as CPU as it can get its hands on (nice 10
apparently) and using about as much memory as stated earlier here. It
just keeps on hogging, making me wonder if something's gone wrong.
I probably can
Public bug reported:
After 10 min or so, or an hour.
Workaround seems to be locking the CPU freq to something. I'm guessing
there might be a bug in the powernow-k8 driver that exhibits itself in
systems with the XPRESS 200M CPU chipset.
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package:
I currently don't have access to the same laptop anymore, as I seem to
have found a workaround by locking the CPU frequency and gave the
computer back to its owner.
However, I do have another laptop with the same GPU which has the same
symptoms. Should I open a new bug and post the information
Seems more and more to me like a kernel bug affecting a specific
combination of hardware (my two laptops with the same ATI GPU + AMD
processors)..or perhaps, a hardware bug that needs a workaround. Sad to
see it looks like this one has been around for 7+ years already :-(
I'm working on fixing
Possibly related? Sounds pretty similar
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.15/+bug/46470
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1444680
Title:
System freezes
** No longer affects: linux-2.6 (Ubuntu)
** Also affects: linux-lts-utopic (Ubuntu)
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/1444680
Title:
System
Tried 15.04 but it eventually ended up in a freeze white screen. Saw
some old posts about the Cool n Quiet-setting in BIOS being the problem.
Will try that before I try the old LTS 12.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
Looks similar to https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-
video-ati/+bug/655200
Booting to recovery mode (using the vesa driver) gives image albeit
slower and incorrect resolution.
diskdoc@p4:~$ lsb_release -rd
Description:Ubuntu 14.04.2 LTS
Release:
I tried booting up from the 15.04 install DVD but problem remains there
as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1451054
Title:
Radeon driver + DVI + Syncmaster 225bw = black screen
Installing and using Wine 1.7.41-staging under PlayOnLinux (still in
Ubuntu 14.10) seems to resolve this problem for me. As this is not the
default Wine in Ubuntu, I guess this is still a bug..
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Maybe my bug is related? https://bugs.launchpad.net/ubuntu/+source
/xserver-xorg-video-ati-lts-utopic/+bug/1444680
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1364502
Title:
XUBUNTU 14.04 keeps
Possibly related?
https://bugs.launchpad.net/ubuntu/+bug/1364502
http://www.computerhope.com/forum/index.php?topic=144174.0
I will also mention that I tried to SSH in but to no avail. It's really
frozen.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
Have two machines with same chip (Radeon XPRESS 200M), this one running
XUbuntu 14.04 (with Utopic driver) and other one running Mint 17.1 XFCE
(apparently with LTS driver). Both exhibit same random freezing.
When frozen, fans spin more and more (CPU on 100%, generating
Bug fixed after I today received update duplicity-0.6.23-1ubuntu4.1
** Changed in: duplicity (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1322571
Tried Mesa 10.1.3 from Proposed but the problem remains.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1322589
Title:
Screen flickers when running game Sins of a Solar Empire
To manage
Tried with
Option SwapbuffersWait off
(using radeon) just for the heck of it, made no difference.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1322589
Title:
Screen flickers when running game
Public bug reported:
Running Trusty/14.04 with updates (duplicity 0.6.23-1ubuntu4) and
getting this when I try to backup. Seems like a new bug since the sort
of similar bugs have been marked fixed released.
Traceback (most recent call last):
File /usr/bin/duplicity, line 1494, in module
Public bug reported:
Problem appeared after update from Ubuntu 13.10 to 14.04. Game worked
fine in Saucy with both radeon and fglrx. Now in Trusty only works with
fglrx. Using radeon driver gives heavy flickering (about 0,5s intervals)
when running the game (through PlayOnLinux/WINE). I expect
Tried running with Intel IGP instead of radeon - no flickering!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1322589
Title:
Screen flickers when running game Sins of a Solar Empire
To manage
I have duplicity 0.6.23-1ubuntu4, having this problem:
Traceback (most recent call last):
File /usr/bin/duplicity, line 1494, in module
with_tempdir(main)
File /usr/bin/duplicity, line 1488, in with_tempdir
fn()
File /usr/bin/duplicity, line 1337, in main
do_backup(action)
I'm suffering from this too, after upgrading from 13.10. I use my Radeon
with the open source driver.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1314871
Title:
Ubuntu 14.04 random screen freeze
Public bug reported:
Get following error when trying to log on SSO: cannot convert float NaN
to integer.
Tried to downgrade python-software-properties as per
https://bugs.launchpad.net/ubuntu/+source/pycurl/+bug/1063350 but it
didn't help. I guess the problem is some code somewhere is compiled
** Tags added: kernel-bug-exists-upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1215441
Title:
Screen blank or shaking if boot without nomodeset
To manage notifications about this bug go
** Attachment added: This is dmesg booting 3.2.0-52 withOUT nomodeset
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1215441/+attachment/3782498/+files/dmesg.without-nomodeset
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: X.org.log booting 3.2.0-29 withOUT nomodeset
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1215441/+attachment/3782501/+files/Xorg.0.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
1 - 100 of 191 matches
Mail list logo
