This bug was fixed in the package xserver-xorg-video-amdgpu-hwe-16.04 -
1.4.0-1~16.04.1
---
xserver-xorg-video-amdgpu-hwe-16.04 (1.4.0-1~16.04.1) xenial; urgency=medium
* Backport for hwe-16.04 stack. (LP: #1716203)
-- Timo Aaltonen Wed, 03 Jan 2018 12:26:59 +0200
--
You recei
This bug was fixed in the package vulkan -
1.0.61.1+dfsg1-1ubuntu1~16.04.1
---
vulkan (1.0.61.1+dfsg1-1ubuntu1~16.04.1) xenial; urgency=medium
* Backport to xenial. (LP: #1716203)
-- Timo Aaltonen Wed, 03 Jan 2018 11:07:38 +0200
** Changed in: vulkan (Ubuntu Xenial)
Stat
This bug was fixed in the package xserver-xorg-video-nouveau-hwe-16.04 -
1:1.0.15-2~16.04.1
---
xserver-xorg-video-nouveau-hwe-16.04 (1:1.0.15-2~16.04.1) xenial; urgency=medium
* Backport for hwe-16.04 stack. (LP: #1716203)
-- Timo Aaltonen Wed, 03 Jan 2018 12:27:08 +0200
** Ch
This bug was fixed in the package xserver-xorg-video-ati-hwe-16.04 -
1:7.10.0-1~16.04.1
---
xserver-xorg-video-ati-hwe-16.04 (1:7.10.0-1~16.04.1) xenial; urgency=medium
* Backport for hwe-16.04 stack. (LP: #1716203)
-- Timo Aaltonen Wed, 03 Jan 2018 12:27:00 +0200
** Changed in
Hello!
I'm finding it slow in the boot process using the operating system, before
login.
I reinstalled Ubuntu 16.04 because I changed the video card, added a new
hard drive and organized the files on the hard drives, at the moment are
two hard drives with the same specifications.
In order not to d
Christopher, I tested the daily build of Ubuntu 18.04 from your link and it
does not work - the problem is still there.
What I noticed, the daily build was based on kernel 4.13. I thought 18.04 will
be based on kernel 4.15 (Chris mentioned the problem is solved for him in this
particular kernel
As per Timo's proposition, I'm publishing artful right now and after a
day or two I'll release xenial if no errors are reported for the artful
version. We want to play it safe as this version will be included in
16.04.4.
The libkscreen test suite is completely unreliable so ignoring that
failure.
This bug was fixed in the package mesa - 17.2.8-0ubuntu0~17.10.1
---
mesa (17.2.8-0ubuntu0~17.10.1) artful; urgency=medium
* New upstream bugfix release. (LP: #1741189)
-- Timo Aaltonen Wed, 17 Jan 2018 17:34:54 +0200
** Changed in: mesa (Ubuntu Artful)
Status: Fix Commi
The verification of the Stable Release Update for mesa has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a reg
** Tags added: bionic
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
https://bugs.launchpad.net/bugs/1509997
Title:
1002:6821 Graphical issues when radeon MST enabled
To manage notifications about this bug g
Adrian:
1) Presently, to test 4.15 in http://cdimage.ubuntu.com/daily-
live/current/ you would have to install it (not test a live environment)
and enable the Proposed repository.
An alternative is test the latest upstream kernel (now 4.16-rc1) via
https://wiki.ubuntu.com/Kernel/MainlineBuilds .
Public bug reported:
lsusb
Bus 001 Device 013: ID 056a:037b Wacom Co., Ltd
xsetwacom --list devices
#null output
/usr/bin/libwacom-list-local-devices
#always the same output regardless connected tablet or not
[Device]
Name=Wacom Serial Tablet WACf004
DeviceMatch=serial::;
Class=ISDV4
Widt
Christopher:
I have tried Ubuntu 17.10 with the upstream kernels (4.15.2 and 4.16-rc1) and
both behave similarly:
no kernel parameters: screens chained by MST DisplayPort mirror picture,
visible as a single screen
radeon.mst=1 : screens chained by MST DisplayPort work properly (seen
as separate
** Description changed:
+ uname -r
+ 4.4.0-98-generic
+
+
lsusb
- Bus 001 Device 013: ID 056a:037b Wacom Co., Ltd
+ Bus 001 Device 013: ID 056a:037b Wacom Co., Ltd
xsetwacom --list devices
#null output
/usr/bin/libwacom-list-local-devices
#always the same output regardless connected
Adrian:
>"I have tried Ubuntu 17.10 with the upstream kernels (4.15.2 and
4.16-rc1) and both behave similarly:"
Please attach both your dmesg and xorg logs after reproducing the
graphical glitching on the latest mainline kernel. Without logs,
developers can't do anything.
>"no kernel parameters:
George, thank you for reporting this and helping make Ubuntu better.
1) Regarding the version of the nvidia drivers you attempted to use, it
appears you are using an upstream or 3rd party version. Could you please
mention where you obtained the driver from?
2) Could you please install a supported
jaffar, thank you for reporting this and helping make Ubuntu better.
1) Could you please provide the full computer model as per the sticker
on the computer itself (not the result of a terminal command or from the
Bug Description)?
2) Could you please provide a screenshot of the error when you sta
** Description changed:
- I run Ubuntu 18.04 in Virtualbox 5.2.6 with as host OS; Ubuntu 17.10 with the
propriety Nvidia driver 340 as suggested by Ubuntu.
+ I run Ubuntu 18.04 in Virtualbox 5.2.6 with as host OS; Ubuntu 17.10 with the
propriety Nvidia driver 340 as suggested by Ubuntu.
The s
Public bug reported:
bug
https://bugs.freedesktop.org/show_bug.cgi?id=104382
patch
https://patchwork.freedesktop.org/patch/196090/
** Affects: xorg-server (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu-X,
which
For me the problem is kind of important, since I moved all my work to
specialised Virtual Machines;
a. one for the normal office and web browsing work,
b. one for banking and other financial apps,
c. one to try out new and unknown apps,
d. one to try out Ubuntu 18.04.
The work around I use now
*** This bug is a duplicate of bug 1556418 ***
https://bugs.launchpad.net/bugs/1556418
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1556418, so is being marked as such.
BertN45, given 3D acceleration is a WORKAROUND, Low is in line with its
definition noted in https://wiki.ubuntu.com/Bugs/Importance . To advise,
the potential difficulty in solving a bug has no impact on Importance.
Despite this:
1) What version of VirtualBox are you using on the host?
2) Did th
Great Regan:
The last couple lines from the video until blank screen:
[OK] Started Light Display Manager.
Starting WPA Supplicant...
taking this along with the boot up history didn't confirm the root cause
for me.
Despite this, as per your Bug Description, you noted this problem
started hap
cement_head, thanks for reporting this and helping make Ubuntu better.
To see if this is resolved for your release, could you please update
your HWE stack as per https://wiki.ubuntu.com/Kernel/LTSEnablementStack
and advise to the results?
** Tags added: regression-update
** Changed in: xorg (Ubu
** Package changed: xorg (Ubuntu) => cheese (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1715121
Title:
cheese error message
To manage notifications about this bug go to:
https://bug
Update done. I’ll keep an eye on this and report back if I encounter the
issue again (or do not encounter it for a longer time—being a sporadic
bug, it’s difficult to tell if it’s gone away for good).
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed
woodo, thank you for reporting this and helping make Ubuntu better.
1) Did the touchpad stop working as expected after an update? If so,
which?
2) To see if this is resolved in your release, could you please update
your HWE stack as per https://wiki.ubuntu.com/Kernel/LTSEnablementStack
and advise
Kent Lion, thank you for reporting this and helping make Ubuntu better.
To see if this is already resolved in your release, could you please
update your HWE stack as per
https://wiki.ubuntu.com/Kernel/LTSEnablementStack and advise to the
results?
** Tags added: latest-bios-a11
** Changed in: xor
Petr Qvits, thank you for reporting this and helping make Ubuntu better.
Could you please run the following command once from a terminal by ensuring you
have the package xdiagnose installed, and that you click the Yes button for
attaching additional debugging information:
apport-collect 1713628
Yuriy Vidineev, thank you for reporting this and helping make Ubuntu
better.
To see if this is already resolved in your release, could you please
update your HWE stack as per
https://wiki.ubuntu.com/Kernel/LTSEnablementStack and advise to the
results?
** Tags added: bios-outdated-2.4.2
** Change
Douglas L. Turnbull, thank you for reporting this and helping make
Ubuntu better.
1) Could you please advise how long it takes to bootup in
seconds/minutes?
2) Is this something that started to happen after an update? If so,
which specifically?
3) To see if this is already resolved in your relea
chalosan, thank you for reporting this and helping make Ubuntu better.
Could you please run the following command once from a terminal by ensuring you
have the package xdiagnose installed, and that you click the Yes button for
attaching additional debugging information:
apport-collect 1712416
W
conny, thank you for reporting this and helping make Ubuntu better.
1) Could you please provide a video or screenshot of the error message?
2) To clarify, does it hang indefinitely or for a period of time?
3) To see if this is resolved in your release, could you please update
your HWE stack as p
Ardit Saliasi, thank you for reporting this and helping make Ubuntu
better.
1) After an app crashes, are there crash files in /var/crash?
2) To see if this is resolved in your release, could you please update
your HWE stack as per https://wiki.ubuntu.com/Kernel/LTSEnablementStack
and advise to th
Maketsi, closing as per your comment
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1712005/comments/2
noting this is resolved.
** Tags added: bios-outdated-1.42
** Changed in: xorg (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubu
** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1714282
Title:
Sorry something went wrong GDBus:
To manage notifications about this bug
GRC FAMILY NET, thank you for reporting this and helping make Ubuntu
better.
1) Regarding hardware acceleration being disabled, how do you do this
specifically?
2) If you disable hardware acceleration, is this still reproducible?
3) To see if this is resolved in your release, could you please up
Hi Christopher,
Thanks for your attention!
Like I said in previous comment I don't have this bug anymore after upgrading
to linux 4.13
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1714122
Title
** Tags added: bios-outdated-2101
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1711037
Title:
Screen intermittently flickers
To manage notifications about this bug go to:
https://bugs.launchp
*** This bug is a duplicate of bug 1706070 ***
https://bugs.launchpad.net/bugs/1706070
** This bug has been marked a duplicate of bug 1706070
Xorg crash
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpa
João Gabriel, thank you for reporting this and helping make Ubuntu
better.
1) Could you please provide the full computer model as noted on the sticker of
the computer itself (not from the Bug Description, or the result of a terminal
command)? For example:
HP Pavilion 11-k100 x360 Convertible PC
*** This bug is a duplicate of bug 1706070 ***
https://bugs.launchpad.net/bugs/1706070
** This bug has been marked a duplicate of bug 1706070
Xorg crash
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpa
Anchal Bhargava, thank you for reporting this and helping make Ubuntu
better.
1) What is the full manufacturer and model of your external monitor?
2) How is the monitor connected to the computer HDMI, VGA, etc.?
3) Could you please provide the full computer model as noted on the
sticker of the c
emilram, thank you for reporting this and helping make Ubuntu better.
1) To clarify, is this something that started to happen after an update?
If so, which specifically?
2) When the computer freezes, for how long does it do so and what is the
impact precisely?
3) To see if this is already resolv
Agustin Samman, thank you for reporting this and helping make Ubuntu
better.
1) Did this start to happen after an update? If so, which specifically?
2) To see if this is resolved in your release, could you please update
your HWE stack as per https://wiki.ubuntu.com/Kernel/LTSEnablementStack
and a
farhad ameri, thank you for reporting this and helping make Ubuntu
better.
1) Could you please provide the full computer model as noted on the sticker of
the computer itself (not from the Bug Description, or the result of a terminal
command)? For example:
HP Pavilion dm4-1160eo Entertainment Not
Jerry Quinn, thank you for reporting this and helping make Ubuntu
better.
1) Did this start to happen after an update? If so, which specifically?
2) To see if this is resolved in your release, could you please update
your HWE stack as per https://wiki.ubuntu.com/Kernel/LTSEnablementStack
and advi
Hello Christopher,
I answer in your message.
Best regards,
João Gabriel.
Em seg, 12 de fev de 2018 às 20:21, Christopher M. Penalver <
christopher.m.penal...@gmail.com> escreveu:
> João Gabriel, thank you for reporting this and helping make Ubuntu
> better.
>
> 1) Could you please provide the f
Robert W. King, thank you for reporting this and helping make Ubuntu
better.
1) Could you please advise which after which update specifically this
started to happen?
2) To see if this is resolved in your release, could you please update
your HWE stack as per https://wiki.ubuntu.com/Kernel/LTSEnab
Peke Gandalera, thank you for reporting this and helping make Ubuntu
better.
1) Did this start to happen after an update? If so, which specifically?
2) To see if this is resolved in your release, could you please update
your HWE stack as per https://wiki.ubuntu.com/Kernel/LTSEnablementStack
and a
Yuriy Vidineev, closing as per your comment
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1714122/comments/7
noting this is resolved by updating.
** Changed in: xorg (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu-X,
wh
** Tags added: bios-outdated-f.24
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1706070
Title:
[HP Pavilion x360 - 13-s104br] Xorg crash
To manage notifications about this bug go to:
https://b
João Gabriel, thanks for the response.
To advise, you may monitor the progress towards this issue via a live
environment of http://cdimage.ubuntu.com/daily-live/current/ that won't
disrupt your Windows install. The results of this test will help
determine if this is resolved in Ubuntu already.
**
1. The host is using 5.2.6. I kept the guests at 5.2.4, because 5.2.6
did freeze during login or did enter a login loop dependent on the
distro. I filed a bug report with Oracle and many persons had the same
issue during login. The beta version 5.2.7 did solve the 5.2.6 login
issues.
Today I also
I experienced this problem when doing a *clean installation* of Ubuntu
GNOME 16.04.3. I confirmed that the synaptics driver was in use. apt-
get update; apt-get upgrade did not resolve the problem.
I was able to get the touchpad settings working by uninstalling the
synaptics driver and installin
Well, that didn’t take long: screen just went black again for somewhere
around a second. Let me know if you need further input from me.
BTW: currently working without a dock, with an external screen attached
via DP (which has also experienced the bug before the update)—so the
dock doesn’t make a d
** Description changed:
- I run Ubuntu 18.04 in Virtualbox 5.2.6 with as host OS; Ubuntu 17.10 with the
propriety Nvidia driver 340 as suggested by Ubuntu.
- The screen almost freezes completely as soon as I maximise any window in the
guest OS Ubuntu 18.04. Any mouse click takes 10-60 seconds be
BertN45:
1)
>"I kept the guests at 5.2.4"
To clarify, using a host with 5.2.6, if you use the Oracle guest
additions from version 5.2.4 this problem is not reproducible in Ubuntu
GNOME?
2)
>" I filed a bug report with Oracle"
Did you file a bug report with Oracle regarding the scope of this
rep
** Tags removed: apport bios-outdated-1.42-collected
** Tags added: apport-collected bios-outdated-1.42
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1715749
Title:
Intermittent black screen on
Michael von Glasow:
1) To clarify, did this issue start to happen after an update? If so,
which specifically?
2) Does this issue happen if you don't have any external displays, and
the laptop is not docked?
3) Regarding the internal laptop display going black for a few seconds,
how often does th
Does ANYONE have an ETA on when this is going to be fixed? THIS IS
AFFECTING MY MAIN COMP!
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1338492
Title:
Xorg crashed with SIGABRT in OsAbo
** Bug watch added: freedesktop.org Bugzilla #104382
https://bugs.freedesktop.org/show_bug.cgi?id=104382
** Also affects: xorg-server via
https://bugs.freedesktop.org/show_bug.cgi?id=104382
Importance: Unknown
Status: Unknown
** Summary changed:
- xserver 1.19.6 freezes , please
** Changed in: xorg-server
Status: Unknown => Fix Released
** Changed in: xorg-server
Importance: Unknown => High
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1748926
Title:
[Expired for xserver-xorg-video-nouveau (Ubuntu) because there has been
no activity for 60 days.]
** Changed in: xserver-xorg-video-nouveau (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xor
1)
One month ago I upgraded Virtualbox from 5.2.4 to 5.2.6. While I was upgrading
Vbox Guest Additions in my VMs to 5.2.6, I detected that that 5.2.6 Guest
additions introduced a serious boot/login problem for all my VMs. So as a
work-around I kept all my VMs at Guest Additions 5.2.4. I reporte
65 matches
Mail list logo
