Public bug reported:
1. When opening a text document (with standard text editor) or a pdf with "Pdf
viewer" and clicking on the "menu" icon at the top right of the window, the
menu shows up correctly.
2.If I resize the window making it shorter than the menu itself, I would expect
the menu to
Same problem here with Ubuntu 20.04. I have an Asus ZenBook Flip S
(UX370UA). I tried two kernels: 5.6.11 and 5.4.2
--
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/1576844
Title:
I have a similar problem using qemu-kvm in kubuntu 14.04.1, while running
linux-mint 17.1 or elementary os 0.3 beta 1 in the virtual machine.
In the case of linux mint, the desktop is more or less ok, but some objects are
corrupted.
If you look at the first attached screenshot you will see three
** Attachment added: qemu_elementary_dekstop.png
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1080674/+attachment/4291236/+files/qemu_elementary_dekstop.png
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-cirrus in
** Attachment added: qemu_mint_dekstop.png
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1080674/+attachment/4291235/+files/qemu_mint_dekstop.png
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-cirrus in Ubuntu.
*** This bug is a duplicate of bug 288502 ***
https://bugs.launchpad.net/bugs/288502
To me it happened the reverse.
1) I installed Ubuntu.
2) I installed KDE
3) After this. Both in ubuntu desktop and in kde desktop I could NOT use the
mouse properly (the pointer only would appear in the
** Attachment added: Xorg.0.log
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1321667/+attachment/4117443/+files/Xorg.0.log
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
Public bug reported:
The SynPS/2 Synaptics TouchPad of Lifebook Fujitsu A544 in Xubuntu 14.04
stops working after a while (at the end I have only the left and right click).
After installing Xubuntu the TouchPad was not revealed, so
I have used the workaround of changing the GRUB_CMDLINE_LINUX
Yes.
** Changed in: xserver-xorg-input-evdev (Ubuntu)
Status: Incomplete = New
--
xinput clients receive input even when the window manager is getting mouse input
https://bugs.launchpad.net/bugs/82110
You received this bug notification because you are a member of Ubuntu-X,
which is
When I reported this bug first, I didn't know very well how bug worked.
Therefore I didn't forward upstream myself. That's the only sane thing
that can be done to such a bug - it's 2 years old. So someone please
report upstream.
I will instead unsubscribe, because of Bug #405350 and my decision
Dear Bryce,
the problem still occurs in Lucid, but only for mouse scroll events.
This can be easily verified by opening xournal, enabling Options-Use
xinput and then, over its main window, press Win+mousewheel to use
compiz. If the scrollbar in xournal is visible (that is, if the document
/can/
I also have this problem on Fedora 13 (kernel 2.6.33). I have put the
kernel 2.6.34 on Fedora 13 (taken by the repository of Fedora 14) and I
don't have this problem anymore. Now, I can set the resolution of
1024x768 + 85 hz.
Also with OpenSuse 11.3 (kernel 2.6.34 rc8) I don't have problems.
I
Xorg.4.log
** Attachment added: Xorg.4.log
http://launchpadlibrarian.net/45184354/Xorg.4.log
--
1024x768 85Hz display resolution leads to Signal Out of Range
https://bugs.launchpad.net/bugs/559066
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
Xorg.5.log
** Attachment added: Xorg.5.log
http://launchpadlibrarian.net/45184375/Xorg.5.log
--
1024x768 85Hz display resolution leads to Signal Out of Range
https://bugs.launchpad.net/bugs/559066
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
** Attachment added: Xorg.2.log
http://launchpadlibrarian.net/45184303/Xorg.2.log
--
1024x768 85Hz display resolution leads to Signal Out of Range
https://bugs.launchpad.net/bugs/559066
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
Xorg.2.log
** Attachment added: Xorg.2.log
http://launchpadlibrarian.net/45184308/Xorg.2.log
--
1024x768 85Hz display resolution leads to Signal Out of Range
https://bugs.launchpad.net/bugs/559066
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
Xorg.3.log
** Attachment added: Xorg.3.log
http://launchpadlibrarian.net/45184326/Xorg.3.log
--
1024x768 85Hz display resolution leads to Signal Out of Range
https://bugs.launchpad.net/bugs/559066
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
** Changed in: xorg-server (Ubuntu)
Status: Incomplete = New
--
display resolution
https://bugs.launchpad.net/bugs/559066
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in ubuntu.
___
In attached, output of lspci -vvnn.
** Attachment added: output of lspci -vvnn
http://launchpadlibrarian.net/43894445/lspci-vvnn.txt
--
display resolution
https://bugs.launchpad.net/bugs/559066
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
Xorg.0.log
** Attachment added: Xorg.0.log
http://launchpadlibrarian.net/43894677/Xorg.0.log
--
display resolution
https://bugs.launchpad.net/bugs/559066
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in ubuntu.
In attachment, Xorg.0.log.old
** Attachment added: Xorg.0.log.old
http://launchpadlibrarian.net/43894813/Xorg.0.log.old
--
display resolution
https://bugs.launchpad.net/bugs/559066
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in
In Attachment, Xorg.1.log
** Attachment added: Xorg.1.log
http://launchpadlibrarian.net/43894846/Xorg.1.log
--
display resolution
https://bugs.launchpad.net/bugs/559066
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in ubuntu.
I ran the command: apport-collect 559066
This is the output: Package xorg-server not installed and no hook available,
ignoring
--
display resolution
https://bugs.launchpad.net/bugs/559066
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server
** Changed in: xorg-server (Ubuntu)
Status: Incomplete = New
** Changed in: xorg-server (Ubuntu)
Status: New = Incomplete
--
display resolution
https://bugs.launchpad.net/bugs/559066
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
To the benefit of all the users experiencing this regression, booting
with the vga cable attached makes everything work fine. Typical of intel
minor league drivers.
--
Got black screen when set to dual monitor mode
https://bugs.launchpad.net/bugs/441112
You received this bug notification because
For those who have the black screen problem with i945gm (e.g. eeepc
1005ha) try to boot with the vga cable attached. This works perfectly on
my system (I use compiz on extended monitor setup).
--
[i945GM] dual screen not working with virtual resolution enabled: just a blank
screen with a mouse
Even better: it suffices to plug the cable, log out and then log in, and
xrandr no longer causes deadlock. Instead, just switching to a text mode
console and back does not help. Someone should try with kernel mode
switch disabled and report, preferably upstream.
--
Got black screen when set to
Same for me, could some developer double check if the bug may have
returned by mistake? E.g. a patch omitted in an upgrade?
--
Source rename clobbered local changes (so tapping not working in Karmic)
https://bugs.launchpad.net/bugs/378391
You received this bug notification because you are a
Bryce, I have been told on some ubuntu development IRC channel that the
upstream fix is going to reach karmic. Please check this, and if you
still need the requested information or more don't hesitate to ask.
** Changed in: mesa (Ubuntu)
Status: Incomplete = New
--
mesa xdemo/glxcontexts
Public bug reported:
I am currently encountering this bug in karmic
http://bugs.freedesktop.org/show_bug.cgi?id=22428
It's fixed upstream but since it's an high priority bug (compiz
completely unusable on intel video cards) and I don't know the path that
the upstream fix follows, I open this
** Bug watch added: freedesktop.org Bugzilla #22428
https://bugs.freedesktop.org/show_bug.cgi?id=22428
** Also affects: mesa via
https://bugs.freedesktop.org/show_bug.cgi?id=22428
Importance: Unknown
Status: Unknown
--
mesa xdemo/glxcontexts run aborted with assertion error
I have this bug on jaunty why was this marked as invalid?
--
[RS690M X1200] screen randomly blanks for short times
https://bugs.launchpad.net/bugs/310864
You received this bug notification because you are a member of Ubuntu-X,
which is the registrant for xserver-xorg-driver-ati.
Will reply in two weeks properly, because I will not be at office very
soon and the machine is there. I use a digital monitor with a high
resolution connected via vga. Not so frequently (can be once per hour)
the monitor goes black and comes back after some seconds.
--
[RS690M X1200] screen
. Ubuntu never endorsed using old
releases; instead, fixes for non-LTS and non current releases are
usually not done unless they are security fixes. In other words, using
past releases is unsupported and not adviced by ubuntu. What you are
describing above is debian.
Vincenzo
--
[i965] X freezes
Il giorno gio, 04/06/2009 alle 19.59 +, reini ha scritto:
I'd like to point out that I tried the old (i.e. intrepid) driver
version (don't remember where I found it - it was somewhere in the
ubuntu wiki AFAIR). It didn't change the freezing problem at all
(made it worse if
Il giorno gio, 04/06/2009 alle 21.01 +, José Tomás Atria ha scritto:
IMHO, please stop with all the discussion about what should have been
done, or if linux is ready for the desktop and whatnot.
We have a stable release that is recommended as stable to users. ALL
users.
this stable
improving it.
Vincenzo
--
[i965] X freezes starting on April 3rd
https://bugs.launchpad.net/bugs/359392
You received this bug notification because you are a member of Ubuntu-X,
which is the registrant for xf86-video-intel.
___
Mailing list: https
Il giorno gio, 04/06/2009 alle 20.00 +0200, Vincenzo Ciancia ha scritto:
In this case, putting the old driver back in the distribution and
starting to chose the right driver based on user's feedback until the
too many intel issues are solved, would be mandatory.
@Bryce, it's easy to put
Il giorno gio, 21/05/2009 alle 16.03 +, zwaldowski ha scritto:
On odd note, though: my now-standard test of looking at the Wikimedia
picture above was passed, but Firefox blacks out the image as soon as
it
finishes downloading. I'm going to wget it right now and see if the
system can
Il giorno ven, 22/05/2009 alle 02.01 +, mlissner ha scritto:
So is it safe to say that if the singapore picture (above) doesn't
freeze our system when we have compiz on, that we don't have this bug?
That's my reading of it, but I haven't read all 500 comments.
No I don't think it is safe
I have a machine affected by this bug, but also another laptop showing
exactly the same form of sudden deadlocks, using an ATI radeon. Now the
point is that this is a centrino laptop, and the chipset is the same of
the other laptop. May this be not a bug in the video driver but
somewhere else
41 matches
Mail list logo
