desktop-packages team mailing list archive

[Vindicator <1516531@xxxxxxxxxxxxxxxxxx>]

I must say I'm glad you did respond as it means you take it seriously.

While you take it as a personal attack, it was merely a description of what I have seen and experienced.
Attacking is something I associate with name-calling with nothing backing it up.
A performance-review from a boss that describes problems with an employee's results is not something I would consider an attack.

I know 1st-tier phone support where the person I'm speaking with has no idea regarding the issue and is reading from a script that is not applicable to the issue, when all that is needed is to advance me to someone who would be able to provide deeper support (test a patch).
It's the kind of support that would be equal to "reboot your computer 3 times" when Excel is selecting multiple cells with a single click. It would be more appropriate to see if the mouse button has bounce, but even then it could still be a software bug.
That is the impression I get when I'm asked to test a newer kernel or OS to see if it would fix the issue.
It was never said "why" it was thought it would fix the issue (eg, reference a pull-request that addresses an issue that might be remotely applicable to the current issue).
I can see the value of 1st-tier in order to filter out "newbs" for the developers when a configuration/setting change is all that is needed, but as much as the tier can be helpful for the developers (and newbs), they can also be headaches for those with issues that need deeper triage.

"... why one is asked... documented, both in those comments..."
I must be missing those comments you are referencing that provides the "why".
My "why" questions:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1516531/comments/29  "What is it about Xenial..."
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1465862/comments/11  "...wondering what this 'testing' is supposed to be doing..."
Other's bug's that ask for a test with an upgrade, but no "why" given:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1523108/comments/4
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1506914/comments/4 "Can someone please explain what..."

With the wiki, I think you are probably referencing "Please do not complain because someone sent what one perceives to be a automated or "canned" response."
I also see this issue as "Please check to see if you(r) problem is a regression." so I'd say bisecting should be done rather than about testing upstream. But I know by saying just that goes against "Please avoid arguing with triagers and developers".

For me, testing a newer kernel is less complicated than testing a whole new OS that is only in the early testing stages when I'm dealing with a "production" (day-to-day use) computer.
It would involve:
1) backing things up and hoping that backup worked.
2) upgrading (in my case, I always start with a fresh install)
3) restore, which never goes well with an encrypted home. something I have to do from live-cd.
4) installing programs, which also means building some from scratch like kodi which also means building the addons.
Even if I got there after hours (day(s)?) of work, the testing OS may not fix the issue and may also have other unusable problems.

Note how I actually do the footwork that I consider reasonable. I'll do
research before submitting a report. I do research to back up my
comments. This isn't off-the-cuff stuff that I am doing.

Also I WON'T be marking this report as "Invalid" as it's VERY valid considering how it affected Kodi and Chrome (haven't tested totem or games in fullscreen).
But YOU may mark it as incomplete since I am unlikely to test xenial, especially since the break happened in 15.10 (worked in 15.04).
I may put xenial on a VM to get a feel for it's current state, but based on my experience with UX bugs in 15.04 and 15.10, if I'm going to have to clean house on my system, I'd just as soon avoid 16.04 (not even alpha yet) and see if other dists come through the pipeline clean(er/ly).
I'll have to back up my data anyway, so I may just do an in-place upgrade to xenial and if it fails with fullscreen or some other notable bug, I'll go ahead an move on to a different dist.

I may look at Arch since the documentation I've seen online, when searching for system-stuff, has been better than Ubuntu. Ubuntu does have plenty of documentation, but they are all over the place with multiple versions that are about the same exact thing.
Again, I wouldn't call that an attack, but merely pointing out a problem. I'd provide links to examples, but this comment is already getting long-winded and this paragraph doesn't relate specifically to the "help" issue (though it is about docs which was mentioned in your last comment).

I won't be offended or hurt if you want to reference these comments as what to (do/not do).
If I'm in the wrong, so be it. I currently don't see it. I'm trying to do good by submitting a bug and providing good data and in turn I'm only asked to test an upstream (unstable/pre-alpha) OS on my personal system with no basis provided on why it is thought it might work.

similar/side note: this reminds me of an article I've seen on
reddit/slashdot referencing sjw vs linus.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1516531

Title:
  Fullscreen Freeze.

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Related?:
  http://askubuntu.com/questions/692405/ubuntu-15-10-unity-freezes-after-escaping-full-screen-video
  https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1509622

  I've been having cases of unusual screen behavior, particularly when Kodi 16 is being used (maybe it's just a Kodi thing).
  There have been times before when coming out of fullscreen video using either Chrome or Kodi would drop me to a console screen with no input.
  I think I would be able to kill the gnome session in tty1.

  Now, after a bios upgrade as well as the latest display manager and kernel update, Kodi has frozen in fullscreen a couple of times and yet audio will still play from Kodi.
  I created the bug report in tty1.

  I've also been noticing that if I pause a Kodi video, other non-Kodi applications may not update their window content.
  For example, I may be in a webpage in Chrome and I try to mousewheel scroll, yet not see the scrolling effect. Or I will click on a different tab and the window doesn't show the switch. BUT, if I continue playing the Kodi video, Chrome will update it's screen, and if I switch back to the tab I scrolled, the scroll will have already occurred.

  I will say that I have at least not had a fullscreen GUI crash me out
  to console.

  Another peculiarity is when booting Ubuntu, I used to be able to press ESC to view the kernel/system booting output, but now it just shows a black screen with a cursor.
  The downside to that in 15.04 was I'd lose my mouse cursor when the GUI login screen came up.

  Let me know what other output you'd like (or whatever test you'd like me to try) "when" it happens again.
  --- 
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroRelease: Ubuntu 15.10
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Generation Core Processor Family Integrated Graphics Controller [8086:041e] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: ASRock Incorporation Device [1849:041e]
  InstallationDate: Installed on 2015-10-28 (26 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: xorg 1:7.7+7ubuntu4
  PackageArchitecture: amd64
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-19-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro noprompt quiet splash elevator=cfq vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Tags:  wily ubuntu compiz-0.9
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.2.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 07/27/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.80
  dmi.board.name: H97M-ITX/ac
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.80:bd07/27/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH97M-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3
  xserver.bootTime: Mon Nov 23 21:36:32 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id                               47908 
   vendor                                     BBY
  xserver.version: 2:1.17.2-1ubuntu9.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1516531/+subscriptions