[Desktop-packages] [Bug 1892584] Re: wine game 'rune classic' hungs the OS on exit

2020-09-25 Thread Alexey Kuznetsov
I've tested ubuntu kernel 5.4.0-26-generic + debian packages (full os
install). It works fine. I can conclude this not kernel issue but
X-server or amd drivers.

Debian packages which works:

ii  x11-xserver-utils7.7+8   
amd64X server utilities
ii  xserver-common   2:1.20.4-1+deb10u1  
all  common files used by various X servers
ii  xserver-xephyr   2:1.20.4-1+deb10u1  
amd64nested X server
ii  xserver-xorg 1:7.7+19
amd64X.Org X server
ii  xserver-xorg-core2:1.20.4-1+deb10u1  
amd64Xorg X server - core server
ii  xserver-xorg-input-all   1:7.7+19
amd64X.Org X server -- input driver metapackage
ii  xserver-xorg-input-libinput  0.28.2-2
amd64X.Org X server -- libinput input driver
ii  xserver-xorg-input-wacom 0.34.99.1-1 
amd64X.Org X server -- Wacom input driver
ii  xserver-xorg-legacy  2:1.20.4-1+deb10u1  
amd64setuid root Xorg server wrapper
ii  xserver-xorg-video-all   1:7.7+19
amd64X.Org X server -- output driver metapackage
ii  xserver-xorg-video-amdgpu18.1.99+git20190207-1   
amd64X.Org X server -- AMDGPU display driver
ii  xserver-xorg-video-ati   1:19.0.1-1  
amd64X.Org X server -- AMD/ATI display driver wrapper
ii  xserver-xorg-video-fbdev 1:0.5.0-1   
amd64X.Org X server -- fbdev display driver
ii  xserver-xorg-video-intel 2:2.99.917+git20180925-2
amd64X.Org X server -- Intel i8xx, i9xx display driver
ii  xserver-xorg-video-nouveau   1:1.0.16-1  
amd64X.Org X server -- Nouveau display driver
ii  xserver-xorg-video-qxl   0.1.5-2+b1  
amd64X.Org X server -- QXL display driver
ii  xserver-xorg-video-radeon1:19.0.1-1  
amd64X.Org X server -- AMD/ATI Radeon display driver
ii  xserver-xorg-video-vesa  1:2.4.0-1   
amd64X.Org X server -- VESA display driver
ii  xserver-xorg-video-vmware1:13.3.0-2  
amd64X.Org X server -- VMware display driver

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

Title:
  wine game 'rune classic' hungs the OS on exit

Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New

Bug description:
  Hello!

  Rune Classic hungs OS on exit (music plays, but X or keyboard caps
  lock not responding), Debian 10 works fine.

  https://www.gog.com/game/rune_classic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg-video-amdgpu 19.1.0-1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Aug 22 19:03:42 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 6.1.10: added
   wireguard, 1.0.20200611: added
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c2) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Picasso [1043:1b11]
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX431DA_UM431DA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=/dev/mapper/vg0-root ro
  SourcePackage: xserver-xorg-video-amdgpu
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/11/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX431DA.301
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX431DA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX431DA.301:bd09/11/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX431DA_UM431DA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX431DA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX431DA_UM431DA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  

[Desktop-packages] [Bug 1892584] [NEW] wine game 'rune classic' hungs the OS on exit

2020-08-22 Thread Alexey Kuznetsov
Public bug reported:

Hello!

Rune Classic hungs OS on exit (music plays, but X or keyboard caps lock
not responding), Debian 10 works fine.

https://www.gog.com/game/rune_classic

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xserver-xorg-video-amdgpu 19.1.0-1
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Aug 22 19:03:42 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 6.1.10: added
 wireguard, 1.0.20200611: added
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c2) (prog-if 
00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Picasso [1043:1b11]
MachineType: ASUSTeK COMPUTER INC. ZenBook UX431DA_UM431DA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=/dev/mapper/vg0-root ro
SourcePackage: xserver-xorg-video-amdgpu
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/11/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX431DA.301
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX431DA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No  Asset  Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX431DA.301:bd09/11/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX431DA_UM431DA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX431DA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: ZenBook
dmi.product.name: ZenBook UX431DA_UM431DA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

** Affects: xserver-xorg-video-amdgpu (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal ubuntu

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

Title:
  wine game 'rune classic' hungs the OS on exit

Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New

Bug description:
  Hello!

  Rune Classic hungs OS on exit (music plays, but X or keyboard caps
  lock not responding), Debian 10 works fine.

  https://www.gog.com/game/rune_classic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg-video-amdgpu 19.1.0-1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Aug 22 19:03:42 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 6.1.10: added
   wireguard, 1.0.20200611: added
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c2) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Picasso [1043:1b11]
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX431DA_UM431DA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=/dev/mapper/vg0-root ro
  SourcePackage: xserver-xorg-video-amdgpu
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/11/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX431DA.301
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX431DA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX431DA.301:bd09/11/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX431DA_UM431DA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX431DA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX431DA_UM431DA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 

[Desktop-packages] [Bug 1776873] Re: Whitelisted allowedURLschemes breaks some desktop apps

2020-04-16 Thread Alexey Kuznetsov
I just found the issue second ago. It is related to SNAP_REEXEC
behavior. The idea is to run snap from snap_core installed from snap. If
you have system snap installed it will be reexec'd from snap core. To
disable it you need to change the source.

Just run this before compilation and you will be ok:

sed -i 's/!osutil.GetenvBool(reExecKey, true)/true/'
snapd-*/cmd/cmd_linux.go

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

Title:
  Whitelisted allowedURLschemes breaks some desktop apps

Status in snapd:
  Triaged
Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  
https://github.com/snapcore/snapd/blob/7952972d4897e085030b288e44dc98b824f6723a/userd/launcher.go#L55

  snapd has a hard-coded list of allowed URL schemes. Currently that is
  limited to "http", "https", "mailto", "snap".

  We have a number of applications in the store which are trying to use
  protocol handlers outside this scope and break when that's not
  possible.

  e.g.

  Telegram Desktop: tg:/
  Github Desktop: git:/
  IRCCloud Desktop: irc:/

  These are the ones I know of, others may also be affected. Can we
  please at least expand the list to those that we know of, and perhaps
  research other popular protocol handlers?

  Ideally we wouldn't have a whitelist, because this delays our ability
  to land new applications with as-yet unknown url schemes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1776873/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1776873] Re: Whitelisted allowedURLschemes breaks some desktop apps

2020-04-16 Thread Alexey Kuznetsov
Seems like a new linux virus preventing me from running compiled snap.
Not the right place to report but who knows? When I recompile the snap
package and changed "help" output to "refresh !!! and remove snaps" and
unpack the content of resulting file into 123/. I reinstall the system
package and result md5 sum look like this:

axet@axet-laptop:~/local$ md5sum 123/usr/bin/snap /usr/bin/snap
f6639f5060dcd23506082f6ff0699f72  123/usr/bin/snap
f6639f5060dcd23506082f6ff0699f72  /usr/bin/snap
axet@axet-laptop:~/local$ 

When I run the package from ./123/usr/bin/snap I got my "!!! and remove
snaps" but when I ran the same file (same md5) from /usr/bin/snap I got
the old output.

axet@axet-laptop:~/local$ ./123/usr/bin/snap
The snap command lets you install, configure, refresh !!! and remove snaps.
Snaps are packages that work across many different Linux distributions,
enabling secure delivery and operation of the latest apps and utilities.

...

axet@axet-laptop:~/local$ /usr/bin/snap
The snap command lets you install, configure, refresh and remove snaps.
Snaps are packages that work across many different Linux distributions,
enabling secure delivery and operation of the latest apps and utilities.

...

Even when I copy my /usr/bin/snap into 11 file and run it from
another location I still getting my new "!!! and remove" string. Seems
like somthing (bug or virus) load old snap package when I run it from
/usr/bin/snap location and when I read the same file I get my actual
file system data. Not sure what kind of virus, trojan or system nvme,
encryption or kernel bug I have... Maybe anyone knows?

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

Title:
  Whitelisted allowedURLschemes breaks some desktop apps

Status in snapd:
  Triaged
Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  
https://github.com/snapcore/snapd/blob/7952972d4897e085030b288e44dc98b824f6723a/userd/launcher.go#L55

  snapd has a hard-coded list of allowed URL schemes. Currently that is
  limited to "http", "https", "mailto", "snap".

  We have a number of applications in the store which are trying to use
  protocol handlers outside this scope and break when that's not
  possible.

  e.g.

  Telegram Desktop: tg:/
  Github Desktop: git:/
  IRCCloud Desktop: irc:/

  These are the ones I know of, others may also be affected. Can we
  please at least expand the list to those that we know of, and perhaps
  research other popular protocol handlers?

  Ideally we wouldn't have a whitelist, because this delays our ability
  to land new applications with as-yet unknown url schemes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1776873/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1776873] Re: Whitelisted allowedURLschemes breaks some desktop apps

2020-04-16 Thread Alexey Kuznetsov
For some reason I unable to rebuild snapd following #29 instruction. All
goes fine, but in the end xdg-open wont work. I've checked
/var/log/syslog and it full of:

chromium_chromium.desktop[1674]: user-open error: Supplied URL scheme
"magnet" is not allowed

What is interesting, when I'm changing the source code of launcher.go I
also changed the line with error text to "Supplied !!! URL scheme"...
but in syslog error line still appears the same with out "!!!" this
conclude changes never goes into the /usr/bin/snap binary file.

I tried to remove ~/.cache/go-build /tmp/go-build turn off wifi, but
still resulting package still produce old version of error text. I have
no idea how to rebuild package correctly, following #28 not working.

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

Title:
  Whitelisted allowedURLschemes breaks some desktop apps

Status in snapd:
  Triaged
Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  
https://github.com/snapcore/snapd/blob/7952972d4897e085030b288e44dc98b824f6723a/userd/launcher.go#L55

  snapd has a hard-coded list of allowed URL schemes. Currently that is
  limited to "http", "https", "mailto", "snap".

  We have a number of applications in the store which are trying to use
  protocol handlers outside this scope and break when that's not
  possible.

  e.g.

  Telegram Desktop: tg:/
  Github Desktop: git:/
  IRCCloud Desktop: irc:/

  These are the ones I know of, others may also be affected. Can we
  please at least expand the list to those that we know of, and perhaps
  research other popular protocol handlers?

  Ideally we wouldn't have a whitelist, because this delays our ability
  to land new applications with as-yet unknown url schemes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1776873/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp