*** This bug is a duplicate of bug 830276 ***
https://bugs.launchpad.net/bugs/830276
Public bug reported:
This crash happened while I was running the update manager, during which
it popped up several times.
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: xserver-xorg-video-intel
*** This bug is a duplicate of bug 830276 ***
https://bugs.launchpad.net/bugs/830276
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/840784
Title:
[i915gm] False GPU
*** This bug is a duplicate of bug 830276 ***
https://bugs.launchpad.net/bugs/830276
Thank you for taking the time to report this crash and helping to make
Ubuntu better. This particular crash has already been reported and is a
duplicate of bug #830276, so is being marked as such. Please
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/830276
Title:
[i915gm] GPU lockup EIR:
Public bug reported:
Just after the system started
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: xserver-xorg-video-intel 2:2.15.901-1ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-9.15-generic 3.0.3
Uname: Linux 3.0.0-9-generic i686
Architecture: i386
BootLog:
fsck z pakietu util-linux
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/840811
Title:
[i945gm] False GPU lockup EIR: 0x0010 PGTBL_ER: 0x0101
To manage notifications about this bug go to:
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/840811
Title:
[i945gm] False GPU lockup EIR: 0x0010 PGTBL_ER: 0x0101
To manage
*** This bug is a duplicate of bug 576648 ***
https://bugs.launchpad.net/bugs/576648
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 576648, so it is being marked as such. Please look
*** This bug is a duplicate of bug 576648 ***
https://bugs.launchpad.net/bugs/576648
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 576648, so it is being marked as such. Please look
Public bug reported:
(The only nearly relevant choice I could find in apport was xorg, so I'm
sorry if this is incorrect.)
I'm running Oneiric Beta1 fully updated. I've noticed my laptops
cooling fan is permanently running, and that the temperature of my
graphics card reaches 86 degrees C
** Attachment added: Screenshot.png
https://bugs.launchpad.net/bugs/840828/+attachment/2351675/+files/Screenshot.png
** Description changed:
(The only nearly relevant choice I could find in apport was xorg, so I'm
sorry if this is incorrect.)
I'm running Oneiric Beta1 fully updated.
I don't see the headers for the kernel in use in the DpkgLog.txt of the
original reporter. This means that the module was never built because he
didn't install the required headers.
As for danizmax, the module was built and installed correctly:
nvidia-current, 280.13, 3.0.0-8-generic-pae, i686:
Public bug reported:
I am testing the next release of Ubuntu and I found out that the
touchpad is no longer working.
I checked the Fn button and the touchpad is not disabled from hardware.
Also left and right touchpad buttons are not working.
I am able to use the same touchpad on Maverick.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
https://bugs.launchpad.net/bugs/840857
Title:
Touchpad no longer working on Oneiric on Dell N3010
To manage notifications about this bug go to:
Forgot to mention:
During the installation process, i had been asked which manager to use.
I'd chosen lightdm. That left me with an unusable system, because the
xserver went into an infinite loop.
Only if i switch to use gdm (dpkg-reconfigure lightdm), xserver starts.
--
You received this bug
** Tags added: unmetdeps
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-dummy in Ubuntu.
https://bugs.launchpad.net/bugs/834136
Title:
Depends on a package that doesn't exists
To manage notifications about this bug go to:
I delete the /etc/X11/xorg.conf file with 'Option Emulate3Buttons' and
started gpointing-device-settings again, enabled middle mouse emulation and set
timeout to short.
After this, the middle click emulation is working again.
No need to edit any xorg.conf files.
Cheers
--
You received this
** Tags added: kubuntu
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/691170
Title:
KDE Screen Locker crashes whenever I open up my laptop screen, or
whenever my screen comes back
You have been subscribed to a public bug:
While testing Ubuntu Oneiric Beta 1 (iso:
http://releases.ubuntu.com/11.04/ubuntu-11.04-desktop-amd64.iso) on my HP-G62
laptop, when changing screen resolution in 800x600 or 1024x768 the screen goes
black, have to wait it reverts back to 1366x768 on
Thank you for taking the time to report this bug and helping to make Ubuntu
better.
From what you written, it looks like a Xorg problem.
I changed bug status, to affects Xorg, not Linux.
Running again:
apport-collect 840865
should send Xorg logs, that will be useful in debugging.
** Package
Not true! modprobe nvidia says the driver does not exist...
Also on the followinf link you can see that my graphic card GTS 250 is
supported by this driver:
http://www.nvidia.com/object/linux-display-ia32-280.13-driver.html
None of official nvidia drivers work for me at the moment, only open
It looks like there is a problem with gnome settings.
The touchpad is working in the Login windows, but stops working after
the gnome session is started.
I looked at mouse and touchpad settings and touchpad is enabled.
** Package changed: xserver-xorg-input-synaptics (Ubuntu) = gnome-
*** This bug is a duplicate of bug 828684 ***
https://bugs.launchpad.net/bugs/828684
Public bug reported:
It occurred after screen had been locked.
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: xserver-xorg-video-intel 2:2.15.901-1ubuntu2
ProcVersionSignature: Ubuntu
*** This bug is a duplicate of bug 828684 ***
https://bugs.launchpad.net/bugs/828684
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/840926
Title:
It occurred after
*** This bug is a duplicate of bug 828684 ***
https://bugs.launchpad.net/bugs/828684
Thank you for taking the time to report this crash and helping to make
Ubuntu better. This particular crash has already been reported and is a
duplicate of bug #820110, so is being marked as such. Please
Yep Mathieu, I'd mark it as duplicate of this bug.
Same here, Nvidia GTS250 with Nvidia 280.13 drivers. Attached
screenshot of corruption.
** Attachment added: Screen corruption on Nvidia card
I have the same setup as #5. The described workaround fixed the problem.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/833841
Title:
libgl1-mesa-glx alternative link
To manage notifications
Apport retracing service marks Bug #840926 (Chipset: i915gm) as dupe of
Bug #820110, which again is a dupe of this one where the description
says Chipset: i965gm, instead as dupe of Bug #830276 where it says
Chipset: i915gm.
--
You received this bug notification because you are a member of
** Tags added: corruption
** Tags added: black-screen
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
https://bugs.launchpad.net/bugs/840140
Title:
Graphical corruption then black screen using an ATI Radeon
Hello Amit,
Thanks for feedback and sorry for late response, somehow I didn't see the mail.
I checked, kernel, udev and synaptics driver but all clear.
Moving to 'gnome-settings-daemon'
Best Wishes
** Package changed: xserver-xorg-input-synaptics (Ubuntu) = gnome-
settings-daemon (Ubuntu)
--
Public bug reported:
When I type something in an xterm window, the text that I type have some
artifacts, making it almost impossible to read. If I switch focus to
some other window, the text looks normal, and when switching focus back
to the xterm window the text still looks normal. It's only
** Attachment added: xterm-problem.png
https://bugs.launchpad.net/bugs/841103/+attachment/2353304/+files/xterm-problem.png
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xterm in Ubuntu.
https://bugs.launchpad.net/bugs/841103
Title:
Text
On Sun, 4 Sep 2011, Björn Tillenius wrote:
Public bug reported:
When I type something in an xterm window, the text that I type have some
artifacts, making it almost impossible to read. If I switch focus to
some other window, the text looks normal, and when switching focus back
to the xterm
Public bug reported:
Every time I use the Session menu to switch to the guest account and then log
back out into my main user account either through the session menu again or the
main login screen, screen corruption occurs.
Only the unity dash and right-click menus are drawn above the screen
** Attachment added: ScreenCorruption2.png
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/841164/+attachment/2353645/+files/ScreenCorruption2.png
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
** Attachment added: ScreenCorruption1.png
https://bugs.launchpad.net/bugs/841164/+attachment/2353617/+files/ScreenCorruption1.png
--
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/841164
Title:
*** This bug is a duplicate of bug 810221 ***
https://bugs.launchpad.net/bugs/810221
I updated my sons computer to oneiric from natty yesterday so that he
could do some alpha testing and ran into the same problem (i.e. it was
using nouveau after the upgrade, but was working fine with nvidia-
Looks like Chris may have been right after all and I was wrong.
See this comment in the original freedesktop bug:
https://bugs.freedesktop.org/show_bug.cgi?id=33592#c15
I'm not in front of the buggy system right now so I can't completely
verify, but when I remotely ssh to it, I can see
Seems to be a problem with inputattach on my machine at least (upgrade from a
nicely tuned natty install)
If I log in to a rescue window, sudo killall -1 inputattach, then ctrl-D, X
restarts with a working touchscreen.
Will try removing the udev rule containing the inputattach line, see if that
Oh, thanks a lot! I can confirm that killing inputattach also solves the
problem for me and the touchscreen works after an X restart!
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xf86-input-wacom in Ubuntu.
Public bug reported:
I don't know any details about...
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: xserver-xorg-video-intel 2:2.15.901-1ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-9.15-generic 3.0.3
Uname: Linux 3.0.0-9-generic i686
Architecture: i386
Chipset: i945gme
CompizPlugins:
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/841258
Title:
[i945gme] False GPU lockup EIR: 0x0010 PGTBL_ER: 0x0103
To
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/841258
Title:
[i945gme] False GPU lockup EIR: 0x0010 PGTBL_ER: 0x0103
To manage notifications about this bug go to:
and yes, it looks like for the solution to survive a reboot is just comment out
the (only) line of
/lib/udev/rules.d/40-inputattach.rules ...
#SUBSYSTEM==tty, KERNEL==ttyS[0-9]*, ATTRS{id}==FUJ02e5|WACf00c,
ACTION==add|change, RUN+=/lib/udev/inputattach --daemon --baud 19200
--w8001 /dev/%k
--
** Summary changed:
- Text has artifacts when typing something
+ Text has artifacts when typing something in terminal
** Package changed: xterm (Ubuntu) = compiz (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xterm in Ubuntu.
Public bug reported:
Here the xorg log of the crash that occurs randomly
[ 717.403]
X.Org X Server 1.10.1
Release Date: 2011-04-15
[ 717.403] X Protocol Version 11, Revision 0
[ 717.403] Build Operating System: Linux 2.6.24-28-server x86_64 Ubuntu
[ 717.404] Current Operating System:
--
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/841321
Title:
Xorg failing randomly
To manage notifications about this bug go to:
Today it has happened again. A couple of tabs were open in FireFox.
After opening a new URL the session has been terminated.
gdm-simple-slave[4255]: WARNING: Unable to load file '/etc/gdm/custom.conf': No
such file or directory
acpid: client connected from 4259[0:0]
acpid: 1 client rule loaded
Public bug reported:
In oneiric (at time of writing) fglrx is successfully built and
installed in kernel (3.0.0-9) but xorg fails to start... getting to
console (sometimes system simply stuck on boot) an lsmod return both
radeon and fglrx modules active in the kernel... when starting (building
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/841326
Title:
xorg not starting with fglrx
To manage notifications about this bug go to:
Public bug reported:
Note: although I'm reporting this bug on a natty system, I have
confirmed it is present in Oneiric, and I'm basing my report on the
files in oneiric.
The diff between /usr/share/X11/locale/en_US.UTF-8/Compose in Debian's
libx11-data 1.4.4-1 and Ubuntu's libx11-data
--
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/841330
Title:
Ubuntu patch to Compose doesn't achieve intended result
To manage notifications about this bug go to:
Totem video player is the same. With dual head, it freeze for 5 to 10
seconds while starting. VLC don't freeze. TeamViewer use wine, so it
freeze, too.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
** Changed in: xserver-xorg-input-synaptics (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
https://bugs.launchpad.net/bugs/830755
Title:
cursor delay
To manage
Actually, looking carefully, only one of the patched shortcuts is
overridden:
+Multi_key less equal : ⇐ U21D0 # LEFT DOUBLE ARROW
The shortcut for RIGHT DOUBLE ARROW uses equal greater whereas that
for GREATER-THAN OR EQUAL TO uses greater equal. However, the
shortcut for RIGHT DOUBLE ARROW does
--
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/841352
Title:
no cursor in login screen
To manage notifications about this bug go to:
Public bug reported:
Without a cursor in the password box, I cannot tell if it has focus. If
it does not have focus, it would be unsafe to type a password. It seems
to always have focus, but it really needs a cursor so it is clear.
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: xorg
Reassigned to the unity-greeter package, and Confirming.
** Package changed: xorg (Ubuntu) = unity-greeter (Ubuntu)
** Changed in: unity-greeter (Ubuntu)
Status: New = Confirmed
** Changed in: unity-greeter (Ubuntu)
Importance: Undecided = Low
--
You received this bug notification
After looking even more carefully, I found that the reason that the
shortcut for RIGHT DOUBLE ARROW didn't work was because I wasn't using
XIM, but the default gtk input method.
Hence, this bug boils down to simply the shortcut for LEFT DOUBLE ARROW
which Ubuntu helpfully patches in does not work
** Bug watch added: freedesktop.org Bugzilla #39282
http://bugs.freedesktop.org/show_bug.cgi?id=39282
** Also affects: xserver-xorg-driver-ati via
http://bugs.freedesktop.org/show_bug.cgi?id=39282
Importance: Unknown
Status: Unknown
--
You received this bug notification because
Public bug reported:
/usr/share/X11/locale/en_US.UTF-8/Compose contains the line:
Multi_key S S : ẞ Ssharp # LATIN CAPITAL
LETTER SHARP S
Unfortunately, this doesn't work, as the system doesn't seem to
recognise the symbolic name Ssharp. Replacing it with the unicode code
(Note: although I'm reporting from a natty system, this bug is present
in oneiric.)
--
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/841371
Title:
Shortcut for Ssharp doesn't work
To manage
--
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/841371
Title:
Shortcut for Ssharp doesn't work
To manage notifications about this bug go to:
This bug still affects me in Ubuntu 11.10 (Oneiric). The first time
plugged in it works. All times after that, the device is not registered.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xf86-input-wacom in Ubuntu.
This bug still affects me in Ubuntu 11.10 (Oneiric). The first time
plugged in it works. All times after that, the device is not registered.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xf86-input-wacom in Ubuntu.
Public bug reported:
I dont know anything else
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: xserver-xorg-video-intel 2:2.15.901-1ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-9.15-generic 3.0.3
Uname: Linux 3.0.0-9-generic i686
Architecture: i386
BootLog:
fsck from util-linux 2.19.1
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/841382
Title:
[i915gm] False GPU lockup EIR: 0x0010 PGTBL_ER: 0x0100
render.IPEHR: 0x0100
To manage
*** This bug is a duplicate of bug 647802 ***
https://bugs.launchpad.net/bugs/647802
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/841388
Title:
*** This bug is a duplicate of bug 647802 ***
https://bugs.launchpad.net/bugs/647802
Thank you for taking the time to report this crash and helping to make
Ubuntu better. This particular crash has already been reported and is a
duplicate of bug #647802, so is being marked as such. Please
I believe this has regressed in Natty. I've been consistently able to
reproduce this behavior on my Lenovo X61s.
00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960
Integrated Graphics Controller (primary) (rev 0c)
ii xserver-xorg 1:7.6+4ubuntu3.1
** Changed in: xf86-input-wacom (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xf86-input-wacom in Ubuntu.
https://bugs.launchpad.net/bugs/730877
Title:
ctl-460: cursor gets stuck
To manage
Just not to be out of my English writing skill I wrote them too -
sending them link to this site. But I would be not surprised if they did
not write back. I bet they receive stuff like this in thousands every
day. Not to mention, ignoring this bug will force users to buy new
graphic cards - more
Tried with Ubuntu Oneiric beta and the corruption is still there.
The versions in beta are:
xserver-xorg-video-intel 2:2.15.901-1ubuntu2
linux-headers-generic 3.0.0.9.10
I attach the picture of the corruption, which seems to be of the same
pattern as before.
** Attachment added:
Christian: The hypothesis of memory running low causing the problems
seems to cohere with the symptoms, because for me too, the corruption
appears when lots of applications have been opened for one user or many
users logged in at the same time.
--
You received this bug notification because you
(and for reference, this was working in Lucid, so I believe it regressed
at some point between Lucid and Natty.)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/275285
Title:
You have been subscribed to a public bug:
My touchpad doesn't respond at all, and my keyboard doesn't respond until I
press the menu-key, I've tried to do clean installs of Ubuntu again on my
laptop, but even during the setup, it wouldn't work. It just started happening
recently - it used to
Does this issue occur in other non-Linux OS's such as Windows or when
you attempt to access your BIOS?
Can you please also load the Oneiric LiveCD and run from terminal:
apport-collect 840704
** Package changed: ubuntu = xorg (Ubuntu)
--
You received this bug notification because you are a
How do I access bios?
On Sep 4, 2011 5:01 PM, Timothy Mayoh timothy.ma...@gmail.com wrote:
Does this issue occur in other non-Linux OS's such as Windows or when
you attempt to access your BIOS?
Can you please also load the Oneiric LiveCD and run from terminal:
apport-collect 840704
**
Hi Tim,
No I cannot even access my bios from the main boot menu. It's not
reading my keyboard at all. This didn't seem to start happening until
recently. Weirdly enough it will still read my keyboard but only when I
pressed the menu button like you saw.
--
You received this bug notification
Do you think it's my keyboard or some big in the system? Because for
some reason it will read my keystrokes but only after I press the menu
key on ubuntu. It doesn't read my keystrokes when in in bios or any
other menu.
--
You received this bug notification because you are a member of Ubuntu-X,
Ok, this is almost certainly a problem caused by faulty hardware, as
this problem does not seem to affect other computers of the same model
from research I have done, and it should be possible for you to access
the BIOS with the internal keyboard on any working laptop.
It also appears that your
Ah thank you for the answer Tim
On Sep 4, 2011 7:00 PM, Timothy Mayoh timothy.ma...@gmail.com wrote:
Ok, this is almost certainly a problem caused by faulty hardware, as
this problem does not seem to affect other computers of the same model
from research I have done, and it should be possible
** Changed in: mesa (Ubuntu Oneiric)
Assignee: (unassigned) = Chris Halse Rogers (raof)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/840679
Title:
conflicting types in GLES2/gl2.h and
*** This bug is a duplicate of bug 647802 ***
https://bugs.launchpad.net/bugs/647802
Thank you for taking the time to report this crash and helping to make
Ubuntu better. This particular crash has already been reported and is a
duplicate of bug #647802, so is being marked as such. Please
** Tags added: arm-porting-queue
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/840679
Title:
conflicting types in GLES2/gl2.h and GL/glext.h
To manage notifications about this bug go to:
[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]
** Changed in: xorg (Ubuntu)
Status: Incomplete = Expired
--
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/780424
I'm a bit surprised that Qt includes both GL/gl.h and GLES2/gl2.h in the
same file. I wouldn't expect that to work; there's a large overlap in
symbols.
This clearly isn't built in the desktop Qt builds as there isn't
anything ARM specific there. I think this is actually a Qt bug, either
in the
Oh, hah!
It's not directly a Qt problem. However, switching the Qt backend from
desktop GL to GL ES in 4:4.7.3-4ubuntu1 is an ABI break, and since it's
exposed in the Qt headers it's an API break, too.
I'm not sure how the Qt maintainers want to deal with this, but I don't
think there's
88 matches
Mail list logo
