PRO [Radeon HD 7750/8740 / R7
250E] . This problem shows up no matter which of the above I'm using,
or Unity.
roger@roger-desktop:~$ uname -a
Linux roger-desktop 4.4.0-124-generic #148-Ubuntu SMP Wed May 2 13:00:18 UTC
2018 x86_64 x86_64 x86_64 GNU/Linux
roger@roger-desktop:~$ free -m
Log in to Ubuntu (i.e. GNOME xorg) > double click
GS5007-GettingStartedWithDraw.odt > click Edit > Track Changes > Compare
Document... > highlight GS4207-GettingStartedWithDraw.odt > click button
Open > in window Manage Changes click button Close > File > Save As... >
in textbox Name
2 of 2 reproduction documents for Bionic.
** Attachment added: "GS4207-GettingStartedWithDraw.odt"
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1537566/+attachment/5147685/+files/GS4207-GettingStartedWithDraw.odt
--
You received this bug notification because you are a member
1 of 2 reproduction documents for Bionic.
** Attachment added: "GS5007-GettingStartedWithDraw.odt"
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1537566/+attachment/5147684/+files/GS5007-GettingStartedWithDraw.odt
--
You received this bug notification because you are a member
** Changed in: xorg (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1772183
Title:
[Microsoft Sculpt Ergonomic Mouse] Booting from
** Attachment removed: "example.zip"
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1094150/+attachment/3469321/+files/example.zip
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
I don't use 14.04, would never install EOL acroread, and issue was only
reproducible against EOL acroread.
** Changed in: apport (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Mike L, to clarify, does this issue happen when using a wired USB mouse?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1772183
Title:
[Microsoft Sculpt Ergonomic Mouse]
** Summary changed:
- [Microsoft Sculpt Ergonomic Mouse] on dual boot systems can scroll multiple
lines at a time.
+ [Microsoft Sculpt Ergonomic Mouse] Booting from Windows to Ubuntu causes
mouse to scroll multiple lines at a time
** Description changed:
- In 16.04 and 18.04, the mouse
** Description changed:
- What was expected to happen is when LibreOffice crashes in Xenial, it
- logs a crash report to file against to errors.ubuntu.com.
+ What is expected to happen is when LibreOffice crashes, a crash report
+ is created in the /var/crash folder.
- What happened instead is
Confirmed in Bionic. What happens in Windows is that it offers to send a
crash report to https://crashreport.libreoffice.org/, where one may then
input the crash ID in to review the stack trace.
** Tags added: bionic
--
You received this bug notification because you are a member of Ubuntu
Touch
Issue also happening in Artful as per:
https://bugs.launchpad.net/bugs/1772425
** Tags added: artful
** Also affects: apport (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
Adding Apport (Ubuntu) in case this is due to Apport not working
correctly, changes would need to happen in LO+Apport, etc.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1771204
** Tags added: regression-release
** Changed in: xorg (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1773744
Title:
Desktop
** Changed in: xorg (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1772542
Title:
after waking from sleep i get text radeon error
Chris Guiver:
1) Going forward, please don't quote snips of logs, as the root cause
issue could have happened well before this, and what you are snipping is
collateral damage. Instead, attach the log in its entirety as you have
done.
2) Regarding #7:
>"New crash reports in /var/crash are
** Tags added: regression-release
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1772542
Title:
after waking from sleep i get text radeon error message then return
login
Thomas Diesenreiter, the next step is to fully commit bisect from 4.13.4
to 4.15.17, in order to identify the last good kernel commit, followed
immediately by the first bad one. This will allow for a more expedited
analysis of the root cause of your issue. Could you please do this
following
** Tags removed: kernel-bug-exists-upstream-4.17.0-041700rc6-generic
** Tags added: kernel-bug-exists-upstream-4.17-rc6
** Tags removed: kernel-bug-exists-upstream
** Tags added: needs-upstream-testing
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
*** This bug is a duplicate of bug 1760849 ***
https://bugs.launchpad.net/bugs/1760849
** Description changed:
- I'm running bionic on a Lenovo X230 laptop.
- It works fine to boot it with either my hdmi monitor or my VGA monitor.
- It also works to attach the VGA monitor after booting and
*** This bug is a duplicate of bug 1760849 ***
https://bugs.launchpad.net/bugs/1760849
Neal McBurnett:
1) Regarding your crash files, please execute the following via a terminal to
have them automatically processed:
ubuntu-bug /var/crash/FILENAME.crash
where FILENAME is the file name of
Mike L:
1) Regarding your comment:
>"removing and reinserting the transciever fixes it until you reboot into
>Windows 10 again."
To clarify, you personally tested with your hardware that after removing
and reinserting, you can reboot Ubuntu as many times as you want and
this will never happen.
** Tags added: latest-bios-f.49
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1772183
Title:
Microsoft Mice on dual boot systems can scroll multiple lines at a
time.
Gary De Maroney, thank you for reporting this and helping make Ubuntu
better.
1) Is this something that started to happen after an update? If so,
which and when precisely?
2) Do you have any actual issues uing the OS?
3) To see if this is already resolved in Ubuntu, could you please test
Sami Pietila:
1) Regarding the crash files, please report these via executing the following
at a terminal:
ubuntu-bug _opt_Gitter_linux64_Gitter.1000.crash
ubuntu-bug _usr_bin_gnome-shell.1000.crash
ubuntu-bug _usr_bin_Xwayland.1000.crash
ubuntu-bug
** Tags added: cosmic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1773744
Title:
Desktop session crash
Status in xorg package in Ubuntu:
Incomplete
Bug description:
** Description changed:
- Hello,
+ In Ubuntu 18.04, after upgrade from 17.10, when I login to Ubuntu
+ desktop via X.org, a wrong display driver is used (llvmpipe). It will
+ cause a horribly poor performance due to software acceleration.
- in Ubuntu 18.04, after upgrade from 17.10, when I
*** This bug is a duplicate of bug 1676547 ***
https://bugs.launchpad.net/bugs/1676547
Hi there,
Anyone found work around solution for the problem mentioned in comment
#39 ??
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
Mike L, thank you for reporting this and helping make Ubuntu better.
1) As per the sticker of the mouse itself (not from the Bug Description,
or the result of a terminal command), could you please provide the full
model?
2) As per the title:
"...on dual boot systems..."
is there some dependency
** Package changed: xorg (Ubuntu) => unity (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1772917
Title:
cannot maximize window
Status in unity package in Ubuntu:
LLAMAs, thank you for reporting this and helping make Ubuntu better.
1) Regarding your Bug Description:
>"Does not start."
What precisely does not start?
2) Is this something that started to happen after an update? If so,
which and when precisely?
3) If you remove the following non-default
Neal McBurnett, thank you for reporting this and helping make Ubuntu
better.
1) As per the sticker of the monitors (not from the Bug Description, or
the result of a terminal command), could you please provide the full
manufacturer and model?
2) Are you using any dongles/adapters to connect to
** Tags added: bios-outdated-2.70 regression-release
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1773850
Title:
No login prompt when booting bionic with both hdmi and vga
Sami Pietila, thank you for reporting this and helping make Ubuntu
better.
1) To clarify, did this issue start after an update? If so, which and
when precisely?
2) Please provide the ouput of the following terminal command (not manually
attach files):
ls -la /var/crash
3) To verify a
*** This bug is a duplicate of bug 1759300 ***
https://bugs.launchpad.net/bugs/1759300
Phill, if you install gnome-tweak-tool and configure GNOME Tweak Tool >
Keyboard & Mouse > Mouse Click Emulation > Area checked then it is a
configuration issue, and in turn, a duplicate.
However, if you
Sending to gnome-shell for review, given monitor does display output
immediately after first configuration via Settings > Devices > Display
(i.e. appears not driver/kernel issue).
** Description changed:
- On Ubuntu 16.04 the login screen and system menu bar, ... is moved to
- the monitor where
Manfred Steiner, in order to finely scope this report on "one issue",
this report will only focus on the first time one boots up with the
external VGA monitor connected (no Beamer), and is at the login screen
(not after login).
Regarding the behavior above, what is reasonable is either, it does
Krishnan Sreenivas:
Regarding using PPAs, PPAs are not supported in Ubuntu. Hence, if a PPA
is used, and it brakes the system, it is out of scope for a bug report.
In regard to the scope of this report, given the history of what changed
and how wasn't documented and provided, you kept making
Manfred Steiner:
1) What is "Beamer"? Is this a program available from the Ubuntu
repositories, a piece of hardware, etc.?
2) To clarify the table in #10, it appears the only part that isn't as
expected is how after configuring the Internal LCD to be off and VGA to
be active, you restart, and at
Manfred Steiner:
1) When the display is set to mirror, at the login screen does it show
up on one monitor or both?
2) When the display is set to mirror, after you login does the system
bar show up on one monitor or both?
--
You received this bug notification because you are a member of Ubuntu
Stefan Helmert, I do not see any visual imperfections in the screenshot
you most recently attached. Could you please advise?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
Manfred Steiner, with only the VGA monitor connected, and the output
sent to both the laptop internal monitor, and external monitor, could
you please provide a screenshot of the Settings > Devices > Display GUI
menu?
--
You received this bug notification because you are a member of Ubuntu
Touch
mustafa, this bug report is being closed due to your last comment
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1773575/comments/5
regarding this being resolved. For future reference you can manage the
status of your own bugs by clicking on the current status in the yellow
line and then
mustafa:
1) Regarding crash files, you would not want to attach them, as they may
contain sensitive information you don't want to reveal publicly.
Instead, one may report them in a privacy respectful way via a terminal:
ubuntu-bug /var/crash/FILENAME.crash
where FILENAME is the name of the
Phill, thank you for reporting this and helping make Ubuntu better.
1) To clarify, how are you attempting to right click, tapping two
fingers on the clickpad, clicking the bottom right area of the clickpad?
2) If you boot into a kernel from 17.10 does right clicking work again?
** Changed in:
** Tags added: latest-bios-c0cn31ww
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1773516
Title:
[Lenovo Yoga 300-11IBY] Right click not working
Status in xorg package in
sathish, thank you for reporting this and helping make Ubuntu better.
1) 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?
If after HWE stack updating this issue is still
Mário Luiz Mendes de Araujo Junior, thank you for taking the time to
report this and helping to make Ubuntu better. Unfortunately, this
report didn't include enough information. You may find it helpful to
read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html
mustafa, thank you for reporting this and helping make Ubuntu better.
1) Regarding your Bug Description:
>"i tried to update the drivers in one way or another..."
This is not enough information. Could you please advise what you did
precisely, in a keyboard click-for-click fashion?
2) Are there
Manfred Steiner:
To advise, this report will only be scoped to one issue. With this in mind, in
this report you have noted the following disparate problems:
1) As per your Bug Description, going from 16.04 to 18.04, where the monitor
the login screen and system bar shows up on changed from
Kevin Dalley, thank you for reporting this and helping make Ubuntu
better. Please advise to all of the following:
1) To clarify, you regarding your self-compiled xserver-xorg-input-
synaptics, is that considered a WORKAROUND to the scope of this report?
If so, could you please provide the steps
Kevin Dalley:
1) To advise, you will not want to manually attach crash reports. This
is due to how they may contain sensitive information you would not want
to release publicly.
2) Regarding those crash reports, in order to process them automatically and in
a privacy respectful way, it is best
Frank Winklmeier, it will help immensely if you use the computer the problem is
reproducible with, and provide necessary debugging logs by filing a new report
with Ubuntu via a terminal:
ubuntu-bug linux
Please feel free to subscribe me to it.
--
You received this bug notification because you
Dieter Meyer, this bug report is being closed due to your last comment
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1770374/comments/3
regarding this being resolved with a reinstall. For future reference you
can manage the status of your own bugs by clicking on the current status
in the
Manfred Steiner, thank you for reporting this and helping make Ubuntu
better.
1) Regarding the VGA monitor, as per the sticker of the monitor itself
(not from the Bug Description, or the result of a terminal command),
could you please provide the full manufacturer and model?
2) Regarding the
Kevin Dalley, thank you for reporting this and helping make Ubuntu
better.
1) Regarding non-default kernel boot parameter i915.i915_enable_rc6=1 is
this required? If you remove it, how does it affect this issue?
2) After you login, are there crash files in the /var/crash folder?
3) To confirm,
** Tags added: bios-outdated-2.48 regression-release
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1773484
Title:
Login screen not moved to used monitor
Status in xorg
sktop 4.4.0-124-generic #148-Ubuntu SMP Wed May 2 13:00:18 UTC
2018 x86_64 x86_64 x86_64 GNU/Linux
roger@roger-desktop:~$ free -m
total used free shared buff/cache available
Mem: 16013 3880 10410 363 1722 11443
Swap: 16348 0 16348
roger@roger-desktop:~$ df -h
Filesystem Size Used Ava
*** This bug is a duplicate of bug 1772386 ***
https://bugs.launchpad.net/bugs/1772386
** This bug has been marked a duplicate of bug 1772386
message - Low Graphics mode - about 2/3 of startups - not all
--
You received this bug notification because you are a member of Ubuntu
Touch
Lonnie Lee Best, this bug report is being closed due to your last
comment
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1771062/comments/4
regarding this being fixed by reinstalling. For future reference you can
manage the status of your own bugs by clicking on the current status in
the
** Tags added: latest-bios-a15 regression-release
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1770306
Title:
X display is black after 18.04 upgrade from 17.10
Status in
Dieter Meyer, thank you for reporting this and helping make Ubuntu
better.
1) Is this something that started to happen after an update? If so,
which and when precisely?
2) Regarding the kernel you are using (4.13.0-37.42-generic 4.13.13) it
appears you are manually booting this or have it
gmc, this bug report is being closed due to your last comment
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1770479/comments/3
regarding this being resolved by a reinstall. For future reference you
can manage the status of your own bugs by clicking on the current status
in the yellow line
Lonnie Lee Best, thank you for reporting this and helping make Ubuntu
better.
1) Is this something that started to happen after an update? If so,
which and when precisely?
2) To clarify, could you please describe how your computer is connected
to monitor (e.g. using a HDMI cord connecting both,
Michal, thank you for reporting this and helping make Ubuntu better.
1) Is this something that started to happen after an update? If so,
which and when precisely?
2) After the freezes, are there any crash files in the /var/crash
folder?
3) How often do the freezes occur?
4) To see if this is
Krishnan Sreenivas:
>"No the windows boot mgr got corrupted"
Regarding strong claims like, "... got corrupted" please post
logs/evidence, advise what caused the corruption, what the configuration
or log file looks like now, and what it should look like precisely to
not be considered corrupted.
Krishnan Sreenivas:
>"The issue was reproducible with only Ubuntu boot,"
To clarify, you completely deleted everything on the drive, only
installed Ubuntu on it (no dual boot) and the problem was reproducible?
--
You received this bug notification because you are a member of Ubuntu
Touch
Krishnan Sreenivas:
To confirm, if you reinstall Ubuntu by completely deleting the entire
drive and only install Ubuntu (no dual boots, manual partitions NTFS,
etc.) is this still reproducible?
If not reproducible, it is advised to keep it this way, and fire up
Windows in a virtual machine if
Krishnan Sreenivas:
To clarify, regarding the drive you installed Ubuntu on, are you either
dual booting with Windows, or manually created an NTFS partition?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
Jörn Heissler, as mentioned previously, apport (which python3-apport is a
dependent of) is used to capture and process program crashes (e.g. xorg and
related packages). For more on apport, please see:
https://wiki.ubuntu.com/Apport
apt-rdepends apport
Reading package lists... Done
Building
Krishnan Sreenivas:
1) The boot log attached notes:
[[0;1;31mFAILED[0m] Failed to mount /media/DATA.
See 'systemctl status media-DATA.mount' for details.
Please execute the following command in a terminal from a failed boot and post
the full results here:
systemctl status media-DATA.mount
--
** Summary changed:
- I get booted into recovery mode every third boot or from sleep when on battery
+ [ASUS R554LA] I get booted into recovery mode every third boot or from sleep
when on battery
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Chris Guiver:
1) Regarding hibernate not working, if you would like to pursue a fix for this,
it is out of scope for this report. However, you may file a new report about it
via a terminal:
ubuntu-bug linux
2) To clarify, did you have issues after sleep/resume in 17.10?
3) In regards to
Thomas Diesenreiter, in order to allow additional upstream mainline kernel
developers to examine the issue, at your earliest convenience, could you please
test the latest mainline kernel available from
http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? Please keep in mind
the following:
Tomáš Klos, to clarify, in Ubuntu 18.04 if you use a Ubuntu (Wayland)
session is the performance as you expected?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1768615
Title:
Krishnan Sreenivas:
Unfortunately, the screenshots provided do not show the root cause of
the problem.
Could you please take a recording via your phone of a failed boot from
start to finish?
Also, you didn't answer question 2).
** Tags added: latest-bios-504
--
You received this bug
** Tags added: bios-outdated-f.65
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1768615
Title:
Intel HD3000 Sandy Bridge - Wrong display driver used by X.org
Status in
Mario Costa:
Your BIOS is outdated as per HP -> https://support.hp.com/us-
en/drivers/selfservice/hp-elitebook-840-g1-notebook-pc/5405360
Also, you didn't respond to question 2).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
** Package changed: xorg (Ubuntu) => gparted (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1772317
Title:
Missing dependency libgtkmm for gparted
Status in
Greg Bouwens, thank you for reporting this and helping make Ubuntu
better. Please advise to all of the following:
1) As per the sticker of the monitor itself (not from the Bug
Description, or the result of a terminal command), could you please
provide the full model number?
2) If you reduce the
** Summary changed:
- don't depend on python3-apport
+ Remove python3-apport as dependency of xserver-xorg
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1773087
Title:
** Tags added: bios-outdated-1.50
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1773009
Title:
Xorg freeze
Status in xorg package in Ubuntu:
New
Bug description:
I am
Jörn Heissler, thank you for reporting this and helping make Ubuntu
better.
1) Regarding not using apport, one may disable it as per:
cat /etc/default/apport
# set this to 0 to disable apport, or to 1 to enable it
# you can temporarily override this with
# sudo service apport start force_start=1
Thomas Diesenreiter, thank you for reporting this and helping make
Ubuntu better. Please advise to all of the following:
1) What release were you using immediately prior to upgrading to 18.04?
2) If you boot into a kernel from the previous working release is this
issue still reproducible?
**
Mario Costa, thank you for reporting this and helping make Ubuntu
better. Please advise to all of the following:
1) Is this something that started to happen after an update? If so,
which and when precisely?
2) To see if this is already resolved in your release, could you please
update your HWE
pawan naresh chandiramani, could you please copy and paste the entire results
of the following terminal command:
sudo apt-get update ; sudo apt-get upgrade
** Changed in: xorg (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Gurjeet, thank you for reporting this and helping make Ubuntu better.
Please advise to all of the following:
1) To clarify, after you get a purple blank screen when putting in
credentials, does it ever get to the desktop environment?
2) Which desktop environments have you tried to log into where
Robin Bitton, thank you for reporting this and helping make Ubuntu
better. Please advise to all of the following:
1) After this occurs, are there crash files in the /var/crash folder?
2) Could you please take a screenshot of the issue and attach
uncompressed to this report?
3) Is this something
Jean Marc trony, thank you for reporting this and helping make Ubuntu
better.
Unfortunately, this report didn't include enough information. You may
find it helpful to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html and
250E] . This problem shows up no matter which of the above I'm using,
or Unity.
roger@roger-desktop:~$ uname -a
Linux roger-desktop 4.4.0-124-generic #148-Ubuntu SMP Wed May 2 13:00:18 UTC
2018 x86_64 x86_64 x86_64 GNU/Linux
roger@roger-desktop:~$ free -m
total used free shared buff/cache a
Chris Guiver, thank you for reporting this and helping make Ubuntu
better. Please respond to all of the following:
1) Is this something that started to happen after an update? If so,
which and when precisely?
2) Regarding your crash files, none of them appear to have been reported, as
the files
** Tags added: bios-outdated-a18
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1772542
Title:
after waking from sleep i get text radeon error message then return
login
Krishnan Sreenivas, thank you for reporting this and helping make Ubuntu
better.
1) Following the instructions from
https://www.asus.com/support/faq/114958 could you please advise to your
model name (not from the Bug Description, or the result of a terminal
command)?
2) Is this problem something
** Package changed: xorg (Ubuntu) => plasma-workspace (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1762978
Title:
ksmserver-logout-greeter crashes on logout
Julian Bieringer-Hinterbuchinger, could you please run the following command
once from a terminal in order to attach additional debugging information:
apport-collect 1766940
** Changed in: xorg (Ubuntu)
Importance: Undecided => Low
** Changed in: xorg (Ubuntu)
Status: Confirmed =>
shyju, the response to 1) didn't answer the question, and you missed
answering question 3).
Could you please provide the missing information?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
Prasanna Kannappan, thank you for reporting this and helping make Ubuntu
better. Please advise to all of the following:
1) Is this something that started to happen after an update? If so,
which one and when precisely?
2) As per nvidia.com the latest proprietary driver compatible with your
card
*** This bug is a duplicate of bug 1769029 ***
https://bugs.launchpad.net/bugs/1769029
** This bug has been marked a duplicate of bug 1769029
Display on Dell 1440x900 is not available
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
gregrwm:
1) To advise, you won't want to manually attach crash files found in
/var/crash, like you did here, and in LP#1770687 and LP#1770250, as they
can contain sensitive information you may not want to share publically.
Also, the cause of all these crash files being generated is because you
201 - 300 of 6428 matches
Mail list logo