As Jullian Gafar (jullian-gafar) wrote on 2015-08-20:
I'm also having this issue with F11 or any application that goes
fullscreen in Unity.
--
System Software / Hardware Information
Hardware:
Processor: Intel Core i3-3110M @ 2.40GHz (4 Cores), Motherboard: LEN
Public bug reported:
I was working on bug #1541082 which was reporting "blotchy" graphics
images on my PowerMac3,1 with Rage ATI Pro 128 card . . . and got the
suggestion to try to add the "r128" driver, which I did. After that the
display went black. After fiddling around with it, I removed the
On Fri, Jul 29, 2016 at 11:20 AM, Fritz Hudnut
wrote:
> But, I was thinking this morning I have some notes about the display
> "modes" where I have used something like "1024 x 768@60-32" . . .
> something like that, and ***that*** did make a difference on my iBook to
> get the display to work pro
** Description changed:
~ % cat /var/log/xdm.log
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
resize called 1920 1200
Fri Apr 22 06:40:03 2016 xdm info (pid 1185): sourcing /etc/X11/xdm/Xsetup
Fri Apr 22 06:40:13 2016 xdm info (pid 1185): sourcing /etc/X11/xdm/Xstar
** Branch linked: lp:~dandrader/qtubuntu/content-hub-clipboard
** Changed in: qtubuntu (Ubuntu)
Status: Triaged => In Progress
** Changed in: qtubuntu (Ubuntu)
Assignee: (unassigned) => Daniel d'Andrada (dandrader)
** Tags removed: xmir
** No longer affects: xorg-server (Ubuntu)
**
Yes, that is correct.
On Fri, Jul 29, 2016 at 7:41 PM, Christopher M. Penalver <
christopher.m.penal...@gmail.com> wrote:
> rohshall, to confirm, you are stating that when using nvidia-358 from
> the Ubuntu repositories (not PPA, third party installs, etc.) doesn't
> crash at all?
>
> --
> You re
rohshall, to confirm, you are stating that when using nvidia-358 from
the Ubuntu repositories (not PPA, third party installs, etc.) doesn't
crash at all?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/b
Public bug reported:
I installed AMD fglrx through AMD's website and upon reboot could not
get to my desktop or TTY anymore. I tried to blindly uninstall
everything and went back to X.Org open-source drivers. The bug was
encountered.
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: fglrx
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-304 in Ubuntu.
https://bugs.launchpad.net/bugs/1607856
Title:
nvidia-304 304.131-0ubuntu3: nvidia-304 kernel module failed to build
Sorry, I meant nvidia-358 and not nvidia-258
On Fri, Jul 29, 2016 at 7:01 PM, Salil Wadnerkar
wrote:
> nvidia-258, available in the ubuntu repository, worked mostly. I don't
> remember what didn't work. However, I can vouch for nvidia-367, which is
> avalable through ppa ppa:graphics-drivers/ppa
** Information type changed from Private Security to Public
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-304 in Ubuntu.
https://bugs.launchpad.net/bugs/1607856
Title:
nvidia-304 304.131-0ubuntu3: nvidia-304 kernel mo
nvidia-258, available in the ubuntu repository, worked mostly. I don't
remember what didn't work. However, I can vouch for nvidia-367, which is
avalable through ppa ppa:graphics-drivers/ppa. It worked without any issues.
On Fri, Jul 29, 2016 at 6:17 PM, Christopher M. Penalver <
christopher.m.pena
** Changed in: xserver-xorg-video-r128 (Debian)
Status: Unknown => Confirmed
--
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/1607891
Title:
X doesn't start with r128 driver (PowerMac 3,1)
On Fri, Jul 29, 2016 at 10:24 AM, ernsteiswuerfel
wrote:
> Added the upstream bug to this tracker. Then I realized that strictly
> speaking this bug "X doesn't start with r128 driver (ATI RAGE)
> [powerpc]" has a different meaning from this one here "blotchy
> graphics". I think it's best to crea
rohshall, to clarify, if you use the nvidia proprietary drivers provided
by the Ubuntu repositories as per
https://help.ubuntu.com/community/BinaryDriverHowto/Nvidia does this
problem a WORKAROUND?
** Tags removed: bios-outdated-2902
** Tags added: latest-bios-2902
** Changed in: xorg (Ubuntu)
For the sake of correctness I added a new bug:
https://bugs.launchpad.net/xorg-server/+bug/1607891
If you like just add the relevant data with "apport-collect" to this bug
after "r128" failed.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg
Public bug reported:
X seems to start, but only produces a black display. Happens on a
PowerMac 3,1 with Rage 128 PRO AGP 4x grapics card. Driver used:
xserver-xorg-video-r128
** Affects: xorg-server
Importance: Unknown
Status: Unknown
** Affects: xorg (Ubuntu)
Importance: Und
$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
2902
03/31/2016
On Fri, Jul 29, 2016 at 4:46 PM, Christopher M. Penalver <
christopher.m.penal...@gmail.com> wrote:
> rohshall, as previously requested, please provide the output of the
> following terminal command:
> sudo d
Added the upstream bug to this tracker. Then I realized that strictly
speaking this bug "X doesn't start with r128 driver (ATI RAGE)
[powerpc]" has a different meaning from this one here "blotchy
graphics". I think it's best to create a new Ubuntu Xorg bug and add the
upstream info there.
Sorry fo
Jeramy Rutley, this bug report is being closed due to your last comment
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1574425/comments/4
regarding you no longer have the hardware. For future reference you can
manage the status of your own bugs by clicking on the current status in
the yellow l
** No longer affects: xorg-server
** No longer affects: debian
--
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/1541082
Title:
[PowerMac3,1] Blotchy GUI graphics for images
To manage notificatio
It took me a while to find this bug report. For the convenience of
others, I thought I would share references to this bug on the internet.
Perhaps a friendly user could post on all these forums links to this
bug. :)
User descriptions and reports of this bug:
https://askubuntu.com/questions/759
Oliver, regarding this report, please post directly here (not send
personal emails). This allows others to contribute towards this.
Despite this, to see if this is a regression, if you test earlier
versions of the nvidia driver in your present install as per
https://help.ubuntu.com/community/Binar
** Also affects: xorg-server via
https://bugs.freedesktop.org/show_bug.cgi?id=94916
Importance: Unknown
Status: Unknown
** Bug watch added: Debian Bug tracker #820233
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820233
** Also affects: debian via
http://bugs.debian.org/cgi-
rohshall, as previously requested, please provide the output of the following
terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.la
I updated the BIOS and still the same result.
I also tried using ppa ppa:oibaf/graphics-drivers
.
But, still the same.
Finally, I switched to nvidia-367 drivers and it works without crashing
(though not everything works -
gdm does not work with nvidia drivers - only xdm
)
.
Anyway, I don't li
On Wed, Jul 27, 2016 at 4:19 PM, ernsteiswuerfel
wrote:
> It would be a good idea to let the
> upstream devs know that. xorg/driver/xf86-video-r128 is actively
> maintained and still receives patches (last one 8 days ago). You could
> file a bug against upstream:
> https://bugs.freedesktop.org/bu
Public bug reported:
Occasionally my screen gets black. The machine is still alive, can login
via ssh.
journalctl -k -b-2 | grep drm
Jul 26 10:22:34 kernel: [drm] Initialized drm 1.1.0 20060810
Jul 26 10:22:34 kernel: [drm] Memory usable by graphics device = 2048M
Jul 26 10:22:34 kernel: fb:
** Also affects: shim (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
** Changed in: xorg (Ubuntu)
Status: Confirmed => Invalid
** Changed in: shim (Ubuntu)
Importance: Undecided => Critical
** Changed in: shim (Ub
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gsettings-ubuntu-touch-schemas (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.laun
Please:
1. Report to (http://tinyurl.com/zmzneso).
2. Paste the new report link here.
3. Set this bug status back to "confirmed".
Thank you.
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Confirmed => Incomplete
** Also affects: xserver-xorg-video-intel
Importance: Undecided
@ Amish Naidu
This is the correct place to report. Thanks for doing so.
** Changed in: xserver-xorg-video-intel (Ubuntu)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
ht
** Branch linked: lp:~vanvugt/qtubuntu/correct-scroll-speed
--
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/1607240
Title:
Unity8 default mouse wheel speed is 7.0 (it should be 1.0)
To ma
I've added the xenial enablement stack and will report back if the crash
occurs.
Here's my updated kernel and Xorg version info:
➜ ~ Xorg -version
X.Org X Server 1.18.3
Release Date: 2016-04-04
X Protocol Version 11, Revision 0
Build Operating System: Linux 3.13.0-91-generic x86_64 Ubuntu
Curre
gsettings-ubuntu-touch-schemas has the default values
** Also affects: gsettings-ubuntu-touch-schemas (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launch
** Changed in: qtubuntu
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
** Changed in: qtubuntu (Ubuntu)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
** Changed in: qtubuntu
Importance: Undecided => High
** Changed in: qtubuntu (Ubuntu)
Importance: Undecided => High
*
** Also affects: qtubuntu (Ubuntu)
Importance: Undecided
Status: New
** Also affects: qtubuntu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.ne
It seems also just switching displays makes the kernel upset, please see
attached dmesg output. Also, please consider making
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1568573 a
duplicate, as it seems to involve the same cases and error messages.
** Attachment added: "dmesg-switch-displa
This bug was fixed in the package xorg-server - 2:1.18.4-1ubuntu4
---
xorg-server (2:1.18.4-1ubuntu4) yakkety; urgency=medium
* debian/patches/xmir.patch:
- Fix button/menu focus failures (LP: #1590553)
- Implement XWMHints properly
- Add smooth touchpad scroll support (
This bug was fixed in the package xorg-server - 2:1.18.4-1ubuntu4
---
xorg-server (2:1.18.4-1ubuntu4) yakkety; urgency=medium
* debian/patches/xmir.patch:
- Fix button/menu focus failures (LP: #1590553)
- Implement XWMHints properly
- Add smooth touchpad scroll support (
Thanks for the info.
So it turns out that the problem is that the modesetting driver is
pruning these modelines because it thinks their vertical refresh is
greater than the max vrefresh.
The function in question is
hw/xfree86/drivers/modesetting/drmmode_display.c#add_gtf_modes(), and it
is calcul
41 matches
Mail list logo
