** Changed in: xorg-server
Status: Confirmed => Unknown
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-geode in Ubuntu.
https://bugs.launchpad.net/bugs/873942
Title:
xf86-video-geode: driver initialization fails on
Thanks for the patch.
This does a fair job of avoiding an explicit crash whenever DDC is
unavailable.
When that happens, restricting available modes to those that AMD
considers safe i.e. Panel-friendly modes, is indeed a promising
strategy.
However, that strategy doesn't guarantee that the
Created attachment 121450
Improved fix
You're right. The panel resolution would usually be too big for an
external display. This new patch picks the largest mode mentioned in
xorg.conf if anything is there. Otherwise it uses those three modes with
a preference for 800x600.
--
You received this
-- GitLab Migration Automatic Message --
This bug has been migrated to freedesktop.org's GitLab instance and has
been closed from further activity.
You can subscribe and participate further through the new bug through
this link to our GitLab instance:
Created attachment 120261
Possible fix
A bit lower brow than the proposal to always get DDC working.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-geode in Ubuntu.
https://bugs.launchpad.net/bugs/873942
Title:
I have two still widely used US-made POS machines with this Geode LX chip.
At least one of them actually makes use of the multiplexed DDC/UART2 gpio line
for the serial connected touchscreen. If/when the KMS driver gets included in
the kernel, can we have a way to use both DDC control and UART2?
** Description changed:
lsb_release :
Description: Ubuntu 18.04.1 LTS
Release: 18.04
What you expected to happen ?
Boot successfully.
What happened instead ?
After selecting Ubuntu in the grub menu, I am greeted with a black screen
that flashes text and the computer
Public bug reported:
lsb_release :
Description:Ubuntu 18.04.1 LTS
Release:18.04
What you expected to happen ?
Boot successfully.
What happened instead ?
After selecting Ubuntu in the grub menu, I am greeted with a black screen that
flashes text and the computer reboots. This keeps
** Changed in: xinit
Status: In Progress => Unknown
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xinit in Ubuntu.
https://bugs.launchpad.net/bugs/199486
Title:
ConsoleKit integration
To manage notifications about this bug go to:
-- GitLab Migration Automatic Message --
This bug has been migrated to freedesktop.org's GitLab instance and has
been closed from further activity.
You can subscribe and participate further through the new bug through
this link to our GitLab instance:
Sergey Menshikov, it is most helpful if you use the computer the problem is
reproducible with, and file 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 are a member of Ubuntu-X,
which is
I repeated the process, now it seems to work correctly. Here is the bug:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1786638
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
** Attachment added: "Stacktrace.txt"
https://bugs.launchpad.net/bugs/1786634/+attachment/5174236/+files/Stacktrace.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
** Attachment added: "ThreadStacktrace.txt"
https://bugs.launchpad.net/bugs/1786634/+attachment/5174237/+files/ThreadStacktrace.txt
** Attachment removed: "CoreDump.gz"
https://bugs.launchpad.net/bugs/1786634/+attachment/5174208/+files/CoreDump.gz
** Changed in: nvidia-graphics-drivers
StacktraceTop:
pixman_rasterize_edges (image=image@entry=0x55bbb91b0190,
l=l@entry=0x7ffc13cfefa0, r=r@entry=0x7ffc13cfefd0, t=t@entry=2185,
b=b@entry=718711) at ../../pixman/pixman-edge.c:376
pixman_rasterize_trapezoid (image=image@entry=0x55bbb91b0190,
trap=trap@entry=0x55bbb90977c8,
Public bug reported:
When close the lid (suspend) then resume the system killed the current
session (as it was logged out) and a greeting screen for log in appears
and when log in, the system locked the session and asked for password to
unlock.
I use Ubuntu 18.04, nvidia-390.
ProblemType: Crash
My workaround is to enable GuC firmware loading and boot without the
dock attached.
Kernel 4.15.0.30 Ubuntu 18.04.1 Xorg/Gnome Lenovo 4th gen X1 20FBxxx
Skylake i7 Intel built-in video
Looks like this is some kind of race condition related to DisplayPort
Multi-Stream mode (DP-MST). This is why
> > 3. If step 2 also failed then apply the workaround from bug
> > 994921, reboot, reproduce the crash, and retry step 1.
>
> I applied the fix and I will try as soon as possible.
I applied the fix, rebooted, reproduced the crash, repeated step 1,
here is the id of the bug:
fokedFromTheLife:
1)
>"so when i install ubuntu the touchpad don't work i go to
>http://pclub.in/2017/01/06/Linux-on-Asus-ROG.html and that' worked"
To clarify, you are stating that by default, the touchpad doesn't work
at all. However, after using the non-default kernel parameters, and
so
when i install ubuntu
the touchpad don't work
i go to http://pclub.in/2017/01/06/Linux-on-Asus-ROG.html
and that' worked
after an update my touchpad stopped again
after deleting that kernel parameters that's not okay
thanks
--
You received this bug notification because you are a member
Launchpad has imported 5 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=94916.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
fokedFromTheLife, thank you for reporting this and helping make Ubuntu
better. Please answer all of the following:
1) Regarding your Bug Description comment:
>"after a while..."
1a) Could you please define specifically how long a while is? Seconds, minutes,
hours, etc.?
1b) Could you please
** Changed in: xlibs
Status: Confirmed => Unknown
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libx11 in Ubuntu.
https://bugs.launchpad.net/bugs/1062534
Title:
Thread unsafe access to internal linked list, breaks Origin games in
Appended two patches from Alessandro Pignotti originally posted on the
Ubuntu Bugzilla. They may or may not still be valid.
According to Alessandro's words, "They should be considered hacks to
make the problem more clear."
Trying to attract some attention to this bug because I face it on a
-- GitLab Migration Automatic Message --
This bug has been migrated to freedesktop.org's GitLab instance and has
been closed from further activity.
You can subscribe and participate further through the new bug through
this link to our GitLab instance:
Created attachment 130585
A hack to remove an optimization that is thread unsafe
Originally posted here:
https://bugs.launchpad.net/ubuntu/+source/libx11/+bug/1062534 by
Alessandro Pignotti
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libx11
Created attachment 130584
A hack to improve the thread safety of the libX11 localization
Originally posted here:
https://bugs.launchpad.net/ubuntu/+source/libx11/+bug/1062534 by
Alessandro Pignotti
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed
Launchpad has imported 2 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=104715.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
28 matches
Mail list logo
