[opensuse] Need to file a bug report - but to who?
Need advice on an issue regarding an oddity with Google Chrome, (Their package) running on my Opensuse machine with Xorg 7.6_1.16.1-356.2 from Opensuse Repositories. Obviously when anyone has such a bug report its a total corner case. My hardware, my video card, my distro, my version of X on My version of Chrome with My desktop environment. How can anybody be expected to run down such a bug, when even specifying ALL the particulars takes 5 paragraphs and TLDR kicks in around three? Problem is Jaggies (paint bugs) when running Chrome (Version 38.0.2125.111 (64-bit) from Their repository. Jaggies appear when resizing browser the window. \ But that is the ONLY program on this machine that shows the error. Firefox, Kong, Dolphin, etc all work just fine. But chrome jaggies, Bling On or Bling Off. See the movie, showing same page with firefox an chrome:
https://drive.google.com/open?id=0B9qMkpbh7Y2LT19Gekl2N2hGUUk&authuser=0
How would you guys write this up? (Already filed bug report with Google, but they are Google, so..... Would you but report this to Opensuse Bugzilla? Xorg? -- Explain again the part about rm -rf / -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 01/11/2014 21:58, John Andersen a écrit :
How would you guys write this up? (Already filed bug report with Google, but they are Google, so.....
did you try chromium to see if the bug is also there? I think it shares part of the code jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* John Andersen <jsamyth@gmail.com> [11-01-14 16:59]:
Need advice on an issue regarding an oddity with Google Chrome, (Their package) running on my Opensuse machine with Xorg 7.6_1.16.1-356.2 from Opensuse Repositories.
Probably out-a-luck if you are using giggle's package and are not satisfied with reporting there, *unless* you can identify a particular openSUSE factor which is responsible. I do not see the condition you report using the chromium package graciously provided by Raymond Wooninck, <tittiatcoke@gmail.com>. ps: he provides *frequent* updates -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/01/2014 02:23 PM, Patrick Shanahan wrote:
* John Andersen <jsamyth@gmail.com> [11-01-14 16:59]:
Need advice on an issue regarding an oddity with Google Chrome, (Their package) running on my Opensuse machine with Xorg 7.6_1.16.1-356.2 from Opensuse Repositories.
Probably out-a-luck if you are using giggle's package and are not satisfied with reporting there, *unless* you can identify a particular openSUSE factor which is responsible. I do not see the condition you report using the chromium package graciously provided by Raymond Wooninck, <tittiatcoke@gmail.com>.
ps: he provides *frequent* updates
Can that co-exist with chrome? -- Explain again the part about rm -rf / -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* John Andersen <jsamyth@gmail.com> [11-01-14 18:20]:
On 11/01/2014 02:23 PM, Patrick Shanahan wrote:
* John Andersen <jsamyth@gmail.com> [11-01-14 16:59]:
Need advice on an issue regarding an oddity with Google Chrome, (Their package) running on my Opensuse machine with Xorg 7.6_1.16.1-356.2 from Opensuse Repositories.
Probably out-a-luck if you are using giggle's package and are not satisfied with reporting there, *unless* you can identify a particular openSUSE factor which is responsible. I do not see the condition you report using the chromium package graciously provided by Raymond Wooninck, <tittiatcoke@gmail.com>.
ps: he provides *frequent* updates
Can that co-exist with chrome?
I believe so as I believe chrome installs into /opt but since both are rpms, uninstalling both and reinstalling the desired one would be simple. Surely chrome does not remove preferences and history stored in the <user> directory. But you could protect against that. I am satisfied with chomium enough to not really be interested in trying chrome. :^) -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/01/2014 03:25 PM, Patrick Shanahan wrote:
* John Andersen <jsamyth@gmail.com> [11-01-14 18:20]:
On 11/01/2014 02:23 PM, Patrick Shanahan wrote:
* John Andersen <jsamyth@gmail.com> [11-01-14 16:59]:
Need advice on an issue regarding an oddity with Google Chrome, (Their package) running on my Opensuse machine with Xorg 7.6_1.16.1-356.2 from Opensuse Repositories.
Probably out-a-luck if you are using giggle's package and are not satisfied with reporting there, *unless* you can identify a particular openSUSE factor which is responsible. I do not see the condition you report using the chromium package graciously provided by Raymond Wooninck, <tittiatcoke@gmail.com>.
ps: he provides *frequent* updates
Can that co-exist with chrome?
I believe so as I believe chrome installs into /opt but since both are rpms, uninstalling both and reinstalling the desired one would be simple. Surely chrome does not remove preferences and history stored in the <user> directory. But you could protect against that.
I am satisfied with chomium enough to not really be interested in trying chrome. :^)
Exact same issue in chromium. Version 37.0.2062.94 (290621) (64-bit) -- Explain again the part about rm -rf / -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* John Andersen <jsamyth@gmail.com> [11-01-14 18:36]: [...]
Exact same issue in chromium. Version 37.0.2062.94 (290621) (64-bit)
Then advise tittiatcoke@gmail.com and perhaps file a bug report and have a very close look at your video parameters/display... gud luk, -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/01/2014 03:38 PM, Patrick Shanahan wrote:
* John Andersen <jsamyth@gmail.com> [11-01-14 18:36]: [...]
Exact same issue in chromium. Version 37.0.2062.94 (290621) (64-bit)
Then advise tittiatcoke@gmail.com and perhaps file a bug report and have a very close look at your video parameters/display...
gud luk,
Yeah, the video parameters are stock, its the community radeon driver for the x1400 cards from AMd. This is relatively new issue, and Again, Chromium/Chrome is absolutely the only thing that behaves this way. Not sure its worth anyone's time to try to track this down, as it is monentary and fleeting, and corrects itself when you stop resizing the browser window. I suspect the problem is in xorg, and unless someone happens to have an older inspiron 9400 laying around they may never see this. I just find it odd that no matter how busy the machine is, nothing else generates these display corruptions. -- Explain again the part about rm -rf / -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (3)
-
jdd -
John Andersen -
Patrick Shanahan