Public bug reported:
Just after a reboot my second screen stop being recognized.
I ran xrandr command and the result was that the hdmi cable was
disconnected, but it wasn't.
I assume it come from the xrandr lib but i'm not sure at all
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: libxra
My initial trouble is now resolved but this message is still displayed into
/var/log/plymouth-debug.log thought, all seems to be fine with fglrx and there
no problem whilt gaming.
I wonder if this message indicate that there is a real trouble or if it just
display a warning for files not found.
phl_plymouth.script script is modified to add lines #169 to 176
169 #-Ajout PHL
---
170 screen_width = Window.GetWidth();
171 screen_height = Window.GetHeight();
172 wallpaper_image = Image("Precise_Pangolin.png");
173 r
** Attachment added: "phl_plymouth.script"
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1208224/+attachment/3762783/+files/phl_plymouth.script
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
https:
Robert,
DefaultPlymouth is my own Plymouth theme built from the official ubuntu-
logo theme and a slightly modified to use the picture
Precise_Pangolin_by_Vlad_Gerasimov.jpg converted to a png file.
/lib/plymouth/themes$ ls -al
total 2488
-rw-r--r-- 1 root root 255 mars 18 23:02 password_fie
** Attachment added: "phl_plymouth"
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1208224/+attachment/3762782/+files/phl_plymouth
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchp
Thanks for your answer Steve.
Sorry, /usr is on the same partition than / :
$ df -k
Sys. de fichiers 1K-blocs Utilisé Disponible Uti% Monté sur
/dev/sda5 96124904 50213412 41028540 56% /
udev197949241979488 1% /dev
t
** Attachment added: "term.log"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-keyboard/+bug/555169/+attachment/1838755/+files/term.log
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-keyboard in ubuntu.
http
Just to inform that the bug disapeared for 2 days.
I just ugraded my ubuntu version and do some cleaning old kernel versions
Please find attached the history and term log files.
** Attachment added: "history.log"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-keyboard/+bug/55516
# Xorg -version
X.Org X Server 1.7.6
Release Date: 2010-03-17
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.24-27-server x86_64 Ubuntu
Current Operating System: Linux phlsys 2.6.32-27-generic #49-Ubuntu SMP Thu Dec
2 00:51:09 UTC 2010 x86_64
Kernel command line: BOOT_IMAGE=/b
For some time I have a keyboard issue at boot. It is relatively close to what
I've read here.
I think this issue appeared after a Lucid Lynx kernel upgrade. Before, it
worked fine.
Till GDM is displayed, the keyboard works well (usb Dell keyboard). I can enter
my login and password.
X11 starts
I uninstalled and reinstalled all X11 xorg packages. It din't fix anything.
Today I deinstalled the xinit package and fglrx then reinstalled xinit and the
ATI package.
To try to debug, I launched xinit via strace and I was able to see that my user
files .Xauthority .Xauthority-c .Xauthority-l wer
I did this test today.
I boot my machine with "normal" mode.
>From an other machine I've been able to do a ssh connection to it.
With a ps -ef I can see that plymouth is still running and x is started
root 437 1 0 17:18 ?00:00:01 /sbin/plymouthd --mode=boot
--attach-to-session
Here some infos that might help too
dmesg | grep fglrx
[ 11.792142] fglrx: module license 'Proprietary. (C) 2002 - ATI Technologies,
Starnberg, GERMANY' taints kernel.
[ 11.852413] [fglrx] Maximum main memory to use for locked dma buffers: 2872
MBytes.
[ 11.852488] [fglrx] vendor: 1002 d
Sorry, I forgot to add the logs
** Attachment added: "Xorg.0.log"
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/645566/+attachment/1626198/+files/Xorg.0.log
--
x server with fglrx driver doesn't start anymore
https://bugs.launchpad.net/bugs/645566
You received this bug notif
** Attachment added: "xorg.conf"
https://bugs.launchpad.net/bugs/645566/+attachment/1624438/+files/xorg.conf
--
x server with fglrx driver doesn't start anymore
https://bugs.launchpad.net/bugs/645566
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed
Public bug reported:
I didn't know what was the fglrx package, so when I bought my new video card, I
first installed Catalyst 10.8 with Lucid Linx and kernel 2.6.32.23 ... it
worked but was a bit buggy (bad 2D display)
When the catalyst 10.9 was out, I installed it. It worked too and it fixed th
** Attachment added: "xorg.conf"
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/642518/+attachment/1609972/+files/xorg.conf
--
package fglrx 2:8.723.1-0ubuntu4 failed to install/upgrade: fglrx kernel module
failed to build
https://bugs.launchpad.net/bugs/642518
You received
** Attachment added: "Xorg.0.log"
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/642518/+attachment/1609971/+files/Xorg.0.log
--
package fglrx 2:8.723.1-0ubuntu4 failed to install/upgrade: fglrx kernel module
failed to build
https://bugs.launchpad.net/bugs/642518
You receive
** Attachment added: "Xorg.0.log"
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/642518/+attachment/1609970/+files/Xorg.0.log
--
package fglrx 2:8.723.1-0ubuntu4 failed to install/upgrade: fglrx kernel module
failed to build
https://bugs.launchpad.net/bugs/642518
You receive
Not for me unfortunately. I have patched the fglrx package as indicated by Luc
Bruninx the reboot.
At startup, the X server hang and doesn't start. (I must electricaly stop the
machine and reboot in rescue mode)
Apparently I had no problem in making and installing packages and the module is
in p
*** This bug is a duplicate of bug 642518 ***
https://bugs.launchpad.net/bugs/642518
I have the same issue. Doing the makefile by hand give the reports.
In my case, I installed the 10.8 catalyst driver before. It didn't cause any
trouble
Due to some display troubles I installed catalyst 10.9
22 matches
Mail list logo
