I forgot to link the upstream issue:
https://gitlab.gnome.org/GNOME/mutter/issues/204
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1778566
Title:
[radeon] Screen does not refresh till the mouse
I will report it there. But are you sure that is not a Wayland issue?
That something on the graphics loop can block the whole execution of the
program and be woken up by mouse movement sounds like a deep
architectural problem to me.
The graphics card is rare, it is integrated in a HP ProLiant
I attached the requested output.
** Attachment added: "lspci_k.txt"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1778566/+attachment/5156787/+files/lspci_k.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
When Wayland is activated in GDM, nothing happens when selecting an
account with the keyboard or typing in the password. I have to type,
then wait, then move the mouse around for the characters to appears.
Because I wouldn't believe this report, I made a video of the
Note taht this bug should be fixed in the new upstream:
https://github.com/onli/simdock
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/195295
Title:
'/usr/share/firefox/icons/mozicon128.png': file
Public bug reported:
After upgrading from 12.04 to 14.04, direct rendering was not working.
glxinfo showed these errors:
onli@Fallout:~$ glxinfo
name of display: :0.0
libGL error: dlopen /usr/lib/dri/swrast_dri.so failed
(/usr/lib/dri/swrast_dri.so: cannot open shared object file: No such file
I get a similar error when connection to any AP:
[ 533.763420] WARNING: CPU: 0 PID: 5198 at
/build/buildd/linux-3.13.0/net/wireless/sme.c:924 cfg80211_connect+0x3f9/0x430
[cfg80211]()
[ 533.763424] Modules linked in: michael_mic arc4 ip6table_filter ip6_tables
iptable_filter ip_tables
What about people using no display-manager at all? playmouth should
recognise that the booting process is over, maybe exit on the start of
X?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/774644
Have the same issue on a fresh install of the released lucid (so there
definitely was no configsetting changed or remaining from any beta).
--
Netbook-launcher fonts rendered in wrong colour
https://bugs.launchpad.net/bugs/560598
You received this bug notification because you are a member of
@mac_v: You know how big the german userbase is? I can't imagine you really
want to say that it's not a papercut-issue because it only affects the german
users. Besides, like Jens Böning said, it isn't. As far as I can see, all the
criteria are matched.
1. It's an unintended problem
2. It makes
@Jens Böning: I agree. Tried it via Also affects project.
** Also affects: hundredpapercuts
Importance: Undecided
Status: New
--
Confusing error message when ICQ users have different encodings
https://bugs.launchpad.net/bugs/253452
You received this bug notification because you are a
Empathy is almost unusable with these warnings and the option to change
this is not userfriendly nor even easy to find when you know it exists.
Having to fix a non-usable defaultprogram should not be of low priority.
--
Confusing error message when ICQ users have different encodings
Reopen because Problem still exist in Hardy and Intrepid
** Changed in: amarok (Ubuntu)
Status: Fix Released = Confirmed
--
Amarok's lyric script isn't reliable
https://bugs.launchpad.net/bugs/66265
You received this bug notification because you are a member of Kubuntu
Bugs, which is
Well, relying on one server maybe ain't such a good idea. Same problem occured
at Hardy, the webseite is down for quite some time now. How about changing the
default-script (lyrc is default, isn't it?) to something like Wiki-Lyrics? It's
the nly one working I could discover.
A pity this hasn't
Just wanted to add that this also affects the messenger psi. As this is
not obvious to the user, moving libsox-fmt-all to the depends-section
would be nice - or changing the dependencies of the affected packages
like psi to libsox-fmt-*.
--
Sox (lack of) supported formats in hardy
In intrepid this is solved for me as fglrx isn't offered at all.
--
do not recommend fglrx for cards with good free radeon support
https://bugs.launchpad.net/bugs/226060
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Seems to be fixed in intrepid.
--
icewm default themes not installed
https://bugs.launchpad.net/bugs/196795
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Changed in: icewm (Ubuntu)
Status: New = Confirmed
--
icewm default themes not installed
https://bugs.launchpad.net/bugs/196795
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I can confirm this. Cause of this error, the icons in the window
decorations are broken. A mix of different icons is shown instead.
--
icewm default themes not installed
https://bugs.launchpad.net/bugs/196795
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I can confirm this. On hardy, prboom needs timidity. It should be added
as a dependency.
--
prboom hangs a few second after starting a game
https://bugs.launchpad.net/bugs/139955
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Wanted to add that this is a serious bug (think it's the same, correct
me if not) if you want to use a small windowmanager like icewm, cause
there is no gnome-display-properties. So you have to run xrandr manually
to fix this - not everyone knows this, not every windowmanager likes it.
Using
Well,found it. /usr/lib/libGL.so.1 linked to a backup of the fglrx-
libGL.so.1.2 I once made. Maybe this should be pointed at at the
upgrade...
--
xorg-driver fglrx interferes with r300 dri (undefined symbol:
_glapi_get_dispatch)
https://bugs.launchpad.net/bugs/52695
You received this bug
I don't see the relation? Don't have a laptop-card in my pc :)
Compiz is working fine with the free radeon-drivers, also with hardy. Fglrx in
combination with compiz only produces a white desktop on my system...
--
wrong recommendation for fglrx
https://bugs.launchpad.net/bugs/226060
You
Public bug reported:
After upgrading from gutsy to hardy and rebooting the system, a ballon-popup
told me that I shall enable proprietary drivers cause then my system could be
used more effectively. But on my system I have a radeon 9800 and nothing else
for what jockey provides a proprietary
Is it known which files of fglrx are responsible for this bug? I get
these messages with an Radeon 9800 after the upgrade from Dapper to
Hardy, and I really don't know which files of fglrx shall be left
(deleted everything I found, installed and purged xorg-driver-fglrx and
so on).
--
25 matches
Mail list logo
