[Desktop-packages] [Bug 1884759] Re: U2f yubikey stopped working in chromium snap
For now I can send udev event instead of replugging:
ls -l /sys/class/hidraw/ | grep :1050: | awk -F/ '{print $NF}' | xargs
-r -L1 -I T udevadm trigger -c add --name-match=T
--
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/1884759
Title:
U2f yubikey stopped working in chromium snap
Status in chromium-browser package in Ubuntu:
New
Bug description:
I was previously using u2f from yubikey in chromium snap, but now it doesn't
work.
No apparmor deny in dmesg (except accessing bluez), u2f slot is conneced.
U2f still works in firefox installed as deb.
# snap connections chromium | grep u2f
u2f-devices chromium:u2f-devices :u2f-devices
manual
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1884759/+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 1884759] Re: U2f yubikey stopped working in chromium snap
Hm, now I updated chrome to 84.0.4147.105 (1260) and can reproduce it reliably by inserting yubikey and then starting chromium with new profile (chromium --user-data-dir=./111). -- 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/1884759 Title: U2f yubikey stopped working in chromium snap Status in chromium-browser package in Ubuntu: New Bug description: I was previously using u2f from yubikey in chromium snap, but now it doesn't work. No apparmor deny in dmesg (except accessing bluez), u2f slot is conneced. U2f still works in firefox installed as deb. # snap connections chromium | grep u2f u2f-devices chromium:u2f-devices :u2f-devices manual To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1884759/+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 1884759] Re: U2f yubikey stopped working in chromium snap
Sorry for long delay. No I can't reproduce it anymore in a way I described before, but it still happens to me. For now certain is that repluging yubikey fixes the problem, reboot doesn't. Upgrading the snap most probably triggering it, need to test it more times. -- 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/1884759 Title: U2f yubikey stopped working in chromium snap Status in chromium-browser package in Ubuntu: New Bug description: I was previously using u2f from yubikey in chromium snap, but now it doesn't work. No apparmor deny in dmesg (except accessing bluez), u2f slot is conneced. U2f still works in firefox installed as deb. # snap connections chromium | grep u2f u2f-devices chromium:u2f-devices :u2f-devices manual To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1884759/+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 1884759] Re: U2f yubikey stopped working in chromium snap
Funny thing. I have Yubikey 5C Nano and it is hard to get out of port. So I plugged spare Yubikey 4 to get dmesg lines and it worked with chromium. Then I replugged my yubikey 5c nano and it worked too. Then I rebooted without unplugging yubikey and it not working in chromium again but works in firefox. -- 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/1884759 Title: U2f yubikey stopped working in chromium snap Status in chromium-browser package in Ubuntu: New Bug description: I was previously using u2f from yubikey in chromium snap, but now it doesn't work. No apparmor deny in dmesg (except accessing bluez), u2f slot is conneced. U2f still works in firefox installed as deb. # snap connections chromium | grep u2f u2f-devices chromium:u2f-devices :u2f-devices manual To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1884759/+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 1884759] Re: U2f yubikey stopped working in chromium snap
name: chromium summary: Chromium web browser, open-source version of Chrome publisher: Canonical* contact: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap license: unset description: | An open-source browser project that aims to build a safer, faster, and more stable way for all Internet users to experience the web. commands: - chromium.chromedriver - chromium snap-id: XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R tracking: latest/stable refresh-date: 12 days ago, at 19:18 MSK installed:84.0.4147.89 (1229) 166MB - -- 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/1884759 Title: U2f yubikey stopped working in chromium snap Status in chromium-browser package in Ubuntu: New Bug description: I was previously using u2f from yubikey in chromium snap, but now it doesn't work. No apparmor deny in dmesg (except accessing bluez), u2f slot is conneced. U2f still works in firefox installed as deb. # snap connections chromium | grep u2f u2f-devices chromium:u2f-devices :u2f-devices manual To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1884759/+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 1884759] Re: U2f yubikey stopped working in chromium snap
Still not working. And right link to test is https://demo.yubico.com /webauthn-technical/registration -- 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/1884759 Title: U2f yubikey stopped working in chromium snap Status in chromium-browser package in Ubuntu: New Bug description: I was previously using u2f from yubikey in chromium snap, but now it doesn't work. No apparmor deny in dmesg (except accessing bluez), u2f slot is conneced. U2f still works in firefox installed as deb. # snap connections chromium | grep u2f u2f-devices chromium:u2f-devices :u2f-devices manual To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1884759/+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 1884759] Re: U2f yubikey stopped working in chromium snap
** Changed in: chromium-browser (Ubuntu) Status: Incomplete => New -- 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/1884759 Title: U2f yubikey stopped working in chromium snap Status in chromium-browser package in Ubuntu: New Bug description: I was previously using u2f from yubikey in chromium snap, but now it doesn't work. No apparmor deny in dmesg (except accessing bluez), u2f slot is conneced. U2f still works in firefox installed as deb. # snap connections chromium | grep u2f u2f-devices chromium:u2f-devices :u2f-devices manual To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1884759/+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 1884759] Re: U2f yubikey stopped working in chromium snap
Log attached. Relevant line probably [92777:92906:0709/115647.054273:ERROR:udev_watcher.cc(96)] Failed to begin udev enumeration. ** Attachment added: "chrom3.log" https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1884759/+attachment/5390970/+files/chrom3.log -- 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/1884759 Title: U2f yubikey stopped working in chromium snap Status in chromium-browser package in Ubuntu: Incomplete Bug description: I was previously using u2f from yubikey in chromium snap, but now it doesn't work. No apparmor deny in dmesg (except accessing bluez), u2f slot is conneced. U2f still works in firefox installed as deb. # snap connections chromium | grep u2f u2f-devices chromium:u2f-devices :u2f-devices manual To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1884759/+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 1884759] Re: U2f yubikey stopped working in chromium snap
Tested firefox snap - u2f works. -- 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/1884759 Title: U2f yubikey stopped working in chromium snap Status in chromium-browser package in Ubuntu: New Bug description: I was previously using u2f from yubikey in chromium snap, but now it doesn't work. No apparmor deny in dmesg (except accessing bluez), u2f slot is conneced. U2f still works in firefox installed as deb. # snap connections chromium | grep u2f u2f-devices chromium:u2f-devices :u2f-devices manual To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1884759/+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 1884759] Re: U2f yubikey stopped working in chromium snap
I use it only for github, no special setup was needed (udev rules are already there for PIV). I logged last time some months ago so I don't know when it stopped working exactly. -- 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/1884759 Title: U2f yubikey stopped working in chromium snap Status in chromium-browser package in Ubuntu: New Bug description: I was previously using u2f from yubikey in chromium snap, but now it doesn't work. No apparmor deny in dmesg (except accessing bluez), u2f slot is conneced. U2f still works in firefox installed as deb. # snap connections chromium | grep u2f u2f-devices chromium:u2f-devices :u2f-devices manual To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1884759/+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 1884759] [NEW] U2f yubikey stopped working in chromium snap
Public bug reported: I was previously using u2f from yubikey in chromium snap, but now it doesn't work. No apparmor deny in dmesg (except accessing bluez), u2f slot is conneced. U2f still works in firefox installed as deb. # snap connections chromium | grep u2f u2f-devices chromium:u2f-devices :u2f-devices manual ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New -- 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/1884759 Title: U2f yubikey stopped working in chromium snap Status in chromium-browser package in Ubuntu: New Bug description: I was previously using u2f from yubikey in chromium snap, but now it doesn't work. No apparmor deny in dmesg (except accessing bluez), u2f slot is conneced. U2f still works in firefox installed as deb. # snap connections chromium | grep u2f u2f-devices chromium:u2f-devices :u2f-devices manual To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1884759/+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 1864901] Re: [snap] suggestion: alert users when the snap has been refreshed while running
tarantula!root# ps axu | grep chr root 561745 0.0 0.0 6436 728 pts/2S+ 15:20 0:00 grep chr tarantula!root# snap refresh chromium error: cannot refresh "chromium": snap "chromium" has running apps (chromium) Had to restart snapd to update chromium snap. -- 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/1864901 Title: [snap] suggestion: alert users when the snap has been refreshed while running Status in chromium-browser package in Ubuntu: Fix Released Bug description: When the chromium snap is being automatically refreshed to a newer revision while the app is running, undefined behaviour might happen, as well as data loss (because the profile folder is versioned). This issue is regularly being reported (see e.g. the duplicates of bug #1616650). Jamie has an interesting suggestion to mitigate this situation, until refresh app awareness becomes default: « […] it would be possible for you to run something in the background that could occasionally see if the current symlink changed, and then alert to restart whenever refresh app awareness lands, it could be converted to see if something is pending, if so, prompt/alert to stop to have updates applied, or something simple idea is to nohup a script in a wrapper before invoking chromium proper iirc, firefox used to have UX built into it letting the user know it needed to be restarted, so there is some precedent for this sort of thing » To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1864901/+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 1864901] Re: [snap] suggestion: alert users when the snap has been refreshed while running
tarantula!root# snap refresh core18 20200427 from Canonical✓ refreshed tarantula!root# snap refresh All snaps up to date. tarantula!root# snap list | grep chromium chromium 81.0.4044.1221119 latest/stable canonical*- tarantula!root# snap info --abs-time chromium name: chromium summary: Chromium web browser, open-source version of Chrome publisher: Canonical✓ store-url: https://snapcraft.io/chromium contact: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap license: unset description: | An open-source browser project that aims to build a safer, faster, and more stable way for all Internet users to experience the web. commands: - chromium.chromedriver - chromium snap-id: XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R tracking: latest/stable refresh-date: 2020-04-25T11:23:52+03:00 channels: latest/stable:81.0.4044.129 2020-04-29T17:25:51Z (1135) 161MB - latest/candidate: 81.0.4044.129 2020-04-28T18:04:52Z (1135) 161MB - latest/beta: 83.0.4103.23 2020-04-25T02:07:58Z (1125) 163MB - latest/edge: 84.0.4128.3 2020-04-29T05:50:21Z (1136) 164MB - installed: 81.0.4044.122 (1119) 161MB - -- 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/1864901 Title: [snap] suggestion: alert users when the snap has been refreshed while running Status in chromium-browser package in Ubuntu: Fix Released Bug description: When the chromium snap is being automatically refreshed to a newer revision while the app is running, undefined behaviour might happen, as well as data loss (because the profile folder is versioned). This issue is regularly being reported (see e.g. the duplicates of bug #1616650). Jamie has an interesting suggestion to mitigate this situation, until refresh app awareness becomes default: « […] it would be possible for you to run something in the background that could occasionally see if the current symlink changed, and then alert to restart whenever refresh app awareness lands, it could be converted to see if something is pending, if so, prompt/alert to stop to have updates applied, or something simple idea is to nohup a script in a wrapper before invoking chromium proper iirc, firefox used to have UX built into it letting the user know it needed to be restarted, so there is some precedent for this sort of thing » To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1864901/+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 1864901] Re: [snap] suggestion: alert users when the snap has been refreshed while running
tarantula!root# snap refresh All snaps up to date. How do I get the "latest" ? -- 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/1864901 Title: [snap] suggestion: alert users when the snap has been refreshed while running Status in chromium-browser package in Ubuntu: Fix Released Bug description: When the chromium snap is being automatically refreshed to a newer revision while the app is running, undefined behaviour might happen, as well as data loss (because the profile folder is versioned). This issue is regularly being reported (see e.g. the duplicates of bug #1616650). Jamie has an interesting suggestion to mitigate this situation, until refresh app awareness becomes default: « […] it would be possible for you to run something in the background that could occasionally see if the current symlink changed, and then alert to restart whenever refresh app awareness lands, it could be converted to see if something is pending, if so, prompt/alert to stop to have updates applied, or something simple idea is to nohup a script in a wrapper before invoking chromium proper iirc, firefox used to have UX built into it letting the user know it needed to be restarted, so there is some precedent for this sort of thing » To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1864901/+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 1864901] Re: [snap] suggestion: alert users when the snap has been refreshed while running
I'm still seeing the problem. tarantula!root# snap refresh All snaps up to date. tarantula!root# snap list | grep chromium chromium 81.0.4044.1221119 latest/stable canonical*- -- 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/1864901 Title: [snap] suggestion: alert users when the snap has been refreshed while running Status in chromium-browser package in Ubuntu: Fix Released Bug description: When the chromium snap is being automatically refreshed to a newer revision while the app is running, undefined behaviour might happen, as well as data loss (because the profile folder is versioned). This issue is regularly being reported (see e.g. the duplicates of bug #1616650). Jamie has an interesting suggestion to mitigate this situation, until refresh app awareness becomes default: « […] it would be possible for you to run something in the background that could occasionally see if the current symlink changed, and then alert to restart whenever refresh app awareness lands, it could be converted to see if something is pending, if so, prompt/alert to stop to have updates applied, or something simple idea is to nohup a script in a wrapper before invoking chromium proper iirc, firefox used to have UX built into it letting the user know it needed to be restarted, so there is some precedent for this sort of thing » To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1864901/+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 1837746] Re: [snap] wrapper script doesn't source ~/.chromium-browser.init
** Changed in: chromium-browser (Ubuntu) Status: Fix Committed => New -- 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/1837746 Title: [snap] wrapper script doesn't source ~/.chromium-browser.init Status in chromium-browser package in Ubuntu: New Bug description: (initially reported here: https://discourse.ubuntu.com/t/call-for- testing-chromium-browser-deb-to-snap-transition/11179/82) The /usr/bin/chromium-browser script in the old deb packages had the following line: test -f ~/.chromium-browser.init && . ~/.chromium-browser.init which allowed users to customize CHROMIUM_FLAGS. This was lost when transitioning to the snap. For compatibility, it should be added back, so that users who rely on this don't observe regressions when transitioning to the snap. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1837746/+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 1837746] Re: [snap] wrapper script doesn't source ~/.chromium-browser.init
I have put CHROMIUM_FLAGS="--force-device-scale-factor=2.0 --new-window" in ~/.chromium-browser.init as I did before. But multiple options is not parsed correctly as it was. I getting error: "[18384:18384:/111220.448169:ERROR:display.cc(55)] Failed to parse the default device scale factor:2 --new-window" -- 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/1837746 Title: [snap] wrapper script doesn't source ~/.chromium-browser.init Status in chromium-browser package in Ubuntu: Fix Committed Bug description: (initially reported here: https://discourse.ubuntu.com/t/call-for- testing-chromium-browser-deb-to-snap-transition/11179/82) The /usr/bin/chromium-browser script in the old deb packages had the following line: test -f ~/.chromium-browser.init && . ~/.chromium-browser.init which allowed users to customize CHROMIUM_FLAGS. This was lost when transitioning to the snap. For compatibility, it should be added back, so that users who rely on this don't observe regressions when transitioning to the snap. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1837746/+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 1837746] Re: [snap] wrapper script doesn't source ~/.chromium-browser.init
snap disconnect chromium:chromium-config snap connect chromium:chromium-config This is resolved my issue -- 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/1837746 Title: [snap] wrapper script doesn't source ~/.chromium-browser.init Status in chromium-browser package in Ubuntu: Fix Committed Bug description: (initially reported here: https://discourse.ubuntu.com/t/call-for- testing-chromium-browser-deb-to-snap-transition/11179/82) The /usr/bin/chromium-browser script in the old deb packages had the following line: test -f ~/.chromium-browser.init && . ~/.chromium-browser.init which allowed users to customize CHROMIUM_FLAGS. This was lost when transitioning to the snap. For compatibility, it should be added back, so that users who rely on this don't observe regressions when transitioning to the snap. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1837746/+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 1837746] Re: [snap] wrapper script doesn't source ~/.chromium-browser.init
# dmesg | grep chromium-browser.init [803454.414690] audit: type=1400 audit(1572333616.781:52868): apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name="/home/baz/.chromium-browser.init" pid=5334 comm="chromium.launch" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000 -- 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/1837746 Title: [snap] wrapper script doesn't source ~/.chromium-browser.init Status in chromium-browser package in Ubuntu: Fix Committed Bug description: (initially reported here: https://discourse.ubuntu.com/t/call-for- testing-chromium-browser-deb-to-snap-transition/11179/82) The /usr/bin/chromium-browser script in the old deb packages had the following line: test -f ~/.chromium-browser.init && . ~/.chromium-browser.init which allowed users to customize CHROMIUM_FLAGS. This was lost when transitioning to the snap. For compatibility, it should be added back, so that users who rely on this don't observe regressions when transitioning to the snap. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1837746/+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 1837746] Re: [snap] wrapper script doesn't source ~/.chromium-browser.init
$ ls -l ~/.chromium-browser.init -rw-r--r-- 1 baz baz 60 мар 16 2018 /home/baz/.chromium-browser.init $ snap connections chromium | grep personal-files personal-fileschromium:chromium-config :personal-files - -- 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/1837746 Title: [snap] wrapper script doesn't source ~/.chromium-browser.init Status in chromium-browser package in Ubuntu: Fix Committed Bug description: (initially reported here: https://discourse.ubuntu.com/t/call-for- testing-chromium-browser-deb-to-snap-transition/11179/82) The /usr/bin/chromium-browser script in the old deb packages had the following line: test -f ~/.chromium-browser.init && . ~/.chromium-browser.init which allowed users to customize CHROMIUM_FLAGS. This was lost when transitioning to the snap. For compatibility, it should be added back, so that users who rely on this don't observe regressions when transitioning to the snap. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1837746/+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 1837746] Re: [snap] wrapper script doesn't source ~/.chromium-browser.init
Chromium snap refuses to start if file exists: $ chromium /snap/chromium/917/bin/chromium.launcher: 78: .: Can't open /home/baz/.chromium-browser.init -- 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/1837746 Title: [snap] wrapper script doesn't source ~/.chromium-browser.init Status in chromium-browser package in Ubuntu: Fix Committed Bug description: (initially reported here: https://discourse.ubuntu.com/t/call-for- testing-chromium-browser-deb-to-snap-transition/11179/82) The /usr/bin/chromium-browser script in the old deb packages had the following line: test -f ~/.chromium-browser.init && . ~/.chromium-browser.init which allowed users to customize CHROMIUM_FLAGS. This was lost when transitioning to the snap. For compatibility, it should be added back, so that users who rely on this don't observe regressions when transitioning to the snap. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1837746/+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 1652253] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1652253/+attachment/4808955/+files/ProcEnviron.txt -- 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/1652253 Title: Xorg crash Status in xorg package in Ubuntu: New Bug description: [ 3122.921] (EE) [ 3122.921] (EE) Backtrace: [ 3122.922] (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4a) [0x559ad2d869fa] [ 3122.922] (EE) 1: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x1bdd69) [0x559ad2d8ad69] [ 3122.922] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7fcac3f5+0x35860) [0x7fcac3f85860] [ 3122.922] (EE) 3: /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 (0x7fcac5085000+0x8cb78) [0x7fcac5111b78] [ 3122.922] (EE) 4: /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 (pixman_image_composite32+0x451) [0x7fcac508ff81] [ 3122.922] (EE) 5: /usr/lib/xorg/modules/libfb.so (fbComposite+0x208) [0x7fcabfac8ff8] [ 3122.922] (EE) 6: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7fcabfef5000+0x15a0a7) [0x7fcac004f0a7] [ 3122.922] (EE) 7: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7fcabfef5000+0x15740a) [0x7fcac004c40a] [ 3122.922] (EE) 8: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x13efc8) [0x559ad2d0bfc8] [ 3122.922] (EE) 9: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x134633) [0x559ad2d01633] [ 3122.922] (EE) 10: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x533bf) [0x559ad2c203bf] [ 3122.922] (EE) 11: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x57413) [0x559ad2c24413] [ 3122.922] (EE) 12: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf1) [0x7fcac3f703f1] [ 3122.922] (EE) 13: /usr/lib/xorg/Xorg (_start+0x2a) [0x559ad2c0e33a] [ 3122.922] (EE) [ 3122.922] (EE) Bus error at address 0x7fcaa65ab400 [ 3122.922] (EE) Fatal server error: [ 3122.922] (EE) Caught signal 7 (Bus error). Server aborting [ 3122.922] (EE) [ 3122.922] (EE) ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11 Uname: Linux 4.8.0-32-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Dec 23 11:53:30 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-11-18 (34 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 16.10 EcryptfsInUse: Yes InstallationDate: Installed on 2016-11-18 (68 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) Package: xorg 1:7.7+13ubuntu4 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11 Tags: yakkety Uname: Linux 4.8.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1652253/+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 1652253] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1652253/+attachment/4808954/+files/JournalErrors.txt -- 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/1652253 Title: Xorg crash Status in xorg package in Ubuntu: New Bug description: [ 3122.921] (EE) [ 3122.921] (EE) Backtrace: [ 3122.922] (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4a) [0x559ad2d869fa] [ 3122.922] (EE) 1: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x1bdd69) [0x559ad2d8ad69] [ 3122.922] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7fcac3f5+0x35860) [0x7fcac3f85860] [ 3122.922] (EE) 3: /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 (0x7fcac5085000+0x8cb78) [0x7fcac5111b78] [ 3122.922] (EE) 4: /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 (pixman_image_composite32+0x451) [0x7fcac508ff81] [ 3122.922] (EE) 5: /usr/lib/xorg/modules/libfb.so (fbComposite+0x208) [0x7fcabfac8ff8] [ 3122.922] (EE) 6: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7fcabfef5000+0x15a0a7) [0x7fcac004f0a7] [ 3122.922] (EE) 7: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7fcabfef5000+0x15740a) [0x7fcac004c40a] [ 3122.922] (EE) 8: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x13efc8) [0x559ad2d0bfc8] [ 3122.922] (EE) 9: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x134633) [0x559ad2d01633] [ 3122.922] (EE) 10: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x533bf) [0x559ad2c203bf] [ 3122.922] (EE) 11: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x57413) [0x559ad2c24413] [ 3122.922] (EE) 12: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf1) [0x7fcac3f703f1] [ 3122.922] (EE) 13: /usr/lib/xorg/Xorg (_start+0x2a) [0x559ad2c0e33a] [ 3122.922] (EE) [ 3122.922] (EE) Bus error at address 0x7fcaa65ab400 [ 3122.922] (EE) Fatal server error: [ 3122.922] (EE) Caught signal 7 (Bus error). Server aborting [ 3122.922] (EE) [ 3122.922] (EE) ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11 Uname: Linux 4.8.0-32-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Dec 23 11:53:30 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-11-18 (34 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 16.10 EcryptfsInUse: Yes InstallationDate: Installed on 2016-11-18 (68 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) Package: xorg 1:7.7+13ubuntu4 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11 Tags: yakkety Uname: Linux 4.8.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1652253/+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 1652253] Re: Xorg crash
apport information ** Tags added: apport-collected ** Description changed: [ 3122.921] (EE) [ 3122.921] (EE) Backtrace: [ 3122.922] (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4a) [0x559ad2d869fa] [ 3122.922] (EE) 1: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x1bdd69) [0x559ad2d8ad69] [ 3122.922] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7fcac3f5+0x35860) [0x7fcac3f85860] [ 3122.922] (EE) 3: /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 (0x7fcac5085000+0x8cb78) [0x7fcac5111b78] [ 3122.922] (EE) 4: /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 (pixman_image_composite32+0x451) [0x7fcac508ff81] [ 3122.922] (EE) 5: /usr/lib/xorg/modules/libfb.so (fbComposite+0x208) [0x7fcabfac8ff8] [ 3122.922] (EE) 6: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7fcabfef5000+0x15a0a7) [0x7fcac004f0a7] [ 3122.922] (EE) 7: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7fcabfef5000+0x15740a) [0x7fcac004c40a] [ 3122.922] (EE) 8: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x13efc8) [0x559ad2d0bfc8] [ 3122.922] (EE) 9: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x134633) [0x559ad2d01633] [ 3122.922] (EE) 10: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x533bf) [0x559ad2c203bf] [ 3122.922] (EE) 11: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x57413) [0x559ad2c24413] [ 3122.922] (EE) 12: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf1) [0x7fcac3f703f1] [ 3122.922] (EE) 13: /usr/lib/xorg/Xorg (_start+0x2a) [0x559ad2c0e33a] [ 3122.922] (EE) [ 3122.922] (EE) Bus error at address 0x7fcaa65ab400 [ 3122.922] (EE) Fatal server error: [ 3122.922] (EE) Caught signal 7 (Bus error). Server aborting [ 3122.922] (EE) [ 3122.922] (EE) ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11 Uname: Linux 4.8.0-32-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Dec 23 11:53:30 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-11-18 (34 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) + --- + ApportVersion: 2.20.3-0ubuntu8.2 + Architecture: amd64 + CurrentDesktop: XFCE + DistroRelease: Ubuntu 16.10 + EcryptfsInUse: Yes + InstallationDate: Installed on 2016-11-18 (68 days ago) + InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) + Package: xorg 1:7.7+13ubuntu4 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11 + Tags: yakkety + Uname: Linux 4.8.0-34-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1652253/+attachment/4808953/+files/Dependencies.txt -- 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/1652253 Title: Xorg crash Status in xorg package in Ubuntu: New Bug description: [ 3122.921] (EE) [ 3122.921] (EE) Backtrace: [ 3122.922] (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4a) [0x559ad2d869fa] [ 3122.922] (EE) 1: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x1bdd69) [0x559ad2d8ad69] [ 3122.922] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7fcac3f5+0x35860) [0x7fcac3f85860] [ 3122.922] (EE) 3: /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 (0x7fcac5085000+0x8cb78) [0x7fcac5111b78] [ 3122.922] (EE) 4: /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 (pixman_image_composite32+0x451) [0x7fcac508ff81] [ 3122.922] (EE) 5: /usr/lib/xorg/modules/libfb.so (fbComposite+0x208) [0x7fcabfac8ff8] [ 3122.922] (EE) 6: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7fcabfef5000+0x15a0a7) [0x7fcac004f0a7] [ 3122.922] (EE) 7: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7fcabfef5000+0x15740a) [0x7fcac004c40a] [ 3122.922] (EE) 8: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x13efc8) [0x559ad2d0bfc8] [ 3122.922] (EE) 9: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x134633) [0x559ad2d01633] [ 3122.922] (EE) 10: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x533bf) [0x559ad2c203bf] [ 3122.922] (EE) 11: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x57413) [0x559ad2c24413] [ 3122.922] (EE) 12: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf1) [0x7fcac3f703f1] [ 3122.922] (EE) 13: /usr/lib/xorg/Xorg (_start+0x2a) [0x559ad2c0e33a] [ 3122.922] (EE) [ 3122.922] (EE) Bus error at address 0x7fcaa65ab400 [ 3122.922] (EE) Fatal server error: [ 3122.922] (EE) Caught signal 7 (Bus error). Server aborting [ 3122.922] (EE) [ 3122.922] (EE) ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11 Uname: Linux 4.8.0-32-gener
[Desktop-packages] [Bug 1652253] [NEW] Xorg crash
Public bug reported: [ 3122.921] (EE) [ 3122.921] (EE) Backtrace: [ 3122.922] (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4a) [0x559ad2d869fa] [ 3122.922] (EE) 1: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x1bdd69) [0x559ad2d8ad69] [ 3122.922] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7fcac3f5+0x35860) [0x7fcac3f85860] [ 3122.922] (EE) 3: /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 (0x7fcac5085000+0x8cb78) [0x7fcac5111b78] [ 3122.922] (EE) 4: /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 (pixman_image_composite32+0x451) [0x7fcac508ff81] [ 3122.922] (EE) 5: /usr/lib/xorg/modules/libfb.so (fbComposite+0x208) [0x7fcabfac8ff8] [ 3122.922] (EE) 6: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7fcabfef5000+0x15a0a7) [0x7fcac004f0a7] [ 3122.922] (EE) 7: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7fcabfef5000+0x15740a) [0x7fcac004c40a] [ 3122.922] (EE) 8: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x13efc8) [0x559ad2d0bfc8] [ 3122.922] (EE) 9: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x134633) [0x559ad2d01633] [ 3122.922] (EE) 10: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x533bf) [0x559ad2c203bf] [ 3122.922] (EE) 11: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x57413) [0x559ad2c24413] [ 3122.922] (EE) 12: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf1) [0x7fcac3f703f1] [ 3122.922] (EE) 13: /usr/lib/xorg/Xorg (_start+0x2a) [0x559ad2c0e33a] [ 3122.922] (EE) [ 3122.922] (EE) Bus error at address 0x7fcaa65ab400 [ 3122.922] (EE) Fatal server error: [ 3122.922] (EE) Caught signal 7 (Bus error). Server aborting [ 3122.922] (EE) [ 3122.922] (EE) ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11 Uname: Linux 4.8.0-32-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Dec 23 11:53:30 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-11-18 (34 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug crash yakkety -- 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/1652253 Title: Xorg crash Status in xorg package in Ubuntu: New Bug description: [ 3122.921] (EE) [ 3122.921] (EE) Backtrace: [ 3122.922] (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4a) [0x559ad2d869fa] [ 3122.922] (EE) 1: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x1bdd69) [0x559ad2d8ad69] [ 3122.922] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7fcac3f5+0x35860) [0x7fcac3f85860] [ 3122.922] (EE) 3: /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 (0x7fcac5085000+0x8cb78) [0x7fcac5111b78] [ 3122.922] (EE) 4: /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 (pixman_image_composite32+0x451) [0x7fcac508ff81] [ 3122.922] (EE) 5: /usr/lib/xorg/modules/libfb.so (fbComposite+0x208) [0x7fcabfac8ff8] [ 3122.922] (EE) 6: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7fcabfef5000+0x15a0a7) [0x7fcac004f0a7] [ 3122.922] (EE) 7: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7fcabfef5000+0x15740a) [0x7fcac004c40a] [ 3122.922] (EE) 8: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x13efc8) [0x559ad2d0bfc8] [ 3122.922] (EE) 9: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x134633) [0x559ad2d01633] [ 3122.922] (EE) 10: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x533bf) [0x559ad2c203bf] [ 3122.922] (EE) 11: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x57413) [0x559ad2c24413] [ 3122.922] (EE) 12: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf1) [0x7fcac3f703f1] [ 3122.922] (EE) 13: /usr/lib/xorg/Xorg (_start+0x2a) [0x559ad2c0e33a] [ 3122.922] (EE) [ 3122.922] (EE) Bus error at address 0x7fcaa65ab400 [ 3122.922] (EE) Fatal server error: [ 3122.922] (EE) Caught signal 7 (Bus error). Server aborting [ 3122.922] (EE) [ 3122.922] (EE) ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11 Uname: Linux 4.8.0-32-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Dec 23 11:53:30 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-11-18 (34 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1652253/+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 1503320] Re: Xorg freeze - general protection fault with fglrx on 4.2 kernel
*** This bug is a duplicate of bug 1493888 *** https://bugs.launchpad.net/bugs/1493888 ** This bug has been marked a duplicate of bug 1493888 FGLRX incompatible with kernel 4.2 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer-updates in Ubuntu. https://bugs.launchpad.net/bugs/1503320 Title: Xorg freeze - general protection fault with fglrx on 4.2 kernel Status in fglrx-installer-updates package in Ubuntu: Confirmed Bug description: X won't start with fglrx or fglrx-updates on Wily. [ 27.388442] fglrx: module license 'Proprietary. (C) 2002 - ATI Technologies, Starnberg, GERMANY' taints kernel. [ 27.388449] Disabling lock debugging due to kernel taint [ 27.416878] fglrx: module verification failed: signature and/or required key missing - tainting kernel [ 27.460461] <6>[fglrx] Maximum main memory to use for locked dma buffers: 3790 MBytes. [ 27.460701] <6>[fglrx] vendor: 1002 device: 679a revision: 0 count: 1 [ 27.461101] <6>[fglrx] ioport: bar 4, base 0xa000, size: 0x100 [ 27.461364] ACPI: PCI Interrupt Link [APC3] enabled at IRQ 18 [ 27.461612] general protection fault: [#1] SMP [ 27.461724] Modules linked in: fglrx(POE+) snd_hda_codec_hdmi snd_hda_intel snd_hda_codec input_leds snd_hda_core amd64_edac_mod(+) edac_core snd_hwdep serio_raw k8temp(+) edac_mce_amd amd_iommu_v2 snd_intel8x0(+) snd_ac97_codec shpchp ac97_bus snd_mpu401_uart snd_pcm i2c_nforce2 ns558 snd_seq_midi snd_seq_midi_event snd_rawmidi 8250_fintek mac_hid snd_seq snd_seq_device snd_timer asus_atk0110 snd gameport soundcore parport_pc ppdev lp parport autofs4 btrfs xor raid6_pq hid_generic usbhid hid pata_acpi forcedeth pata_amd sata_nv floppy [ 27.463451] CPU: 1 PID: 278 Comm: systemd-udevd Tainted: P OE 4.2.0-14-generic #16-Ubuntu [ 27.463494] Hardware name: System manufacturer System Product Name/A8N-E, BIOS ASUS A8N-E ACPI BIOS Revision 1013 04/07/2006 [ 27.463537] task: 8800bfabb200 ti: 88013a0b4000 task.ti: 88013a0b4000 [ 27.463578] RIP: 0010:[] [] firegl_trace+0x61/0x1e0 [fglrx] [ 27.463925] RSP: 0018:88013a0b7aa8 EFLAGS: 00010282 [ 27.463964] RAX: 0001 RBX: 88013a0b7b87 RCX: 12cf [ 27.464006] RDX: c0577430 RSI: c037ac91 RDI: 0004 [ 27.464012] RBP: 0001 R08: R09: c05e04f0 [ 27.464012] R10: 8800b9326000 R11: c0385bf0 R12: 000d [ 27.464012] R13: R14: R15: c05e04f0 [ 27.464012] FS: 7f2db918f8c0() GS:88013fd0() knlGS: [ 27.464012] CS: 0010 DS: ES: CR0: 80050033 [ 27.464012] CR2: 7f2db91ad000 CR3: 00013a0a9000 CR4: 06e0 [ 27.464012] Stack: [ 27.464012] 12cf0092 c0577430 0096 0096 [ 27.464012] 88013a0b7b08 8168e1dc 88013a513400 0004 [ 27.464012] 88013a513400 88013a0b7b96 0286 811cfa83 [ 27.464012] Call Trace: [ 27.464012] [] ? pci_conf1_read+0xbc/0x100 [ 27.464012] [] ? __kmalloc+0xa3/0x250 [ 27.464012] [] ? KCL_MEM_SmallBufferAlloc+0x13/0x20 [fglrx] [ 27.464012] [] ? KCL_STR_Memcpy+0xe/0x10 [fglrx] [ 27.464012] [] ? asyncIOInit+0xa6/0xe0 [fglrx] [ 27.464012] [] ? asyncioSvcInitContext+0x30/0x30 [fglrx] [ 27.464012] [] ? asyncioSvcInstallFn+0x40/0x40 [fglrx] [ 27.464012] [] ? klist_next+0x25/0x100 [ 27.464012] [] ? asyncioSvcRemoveFn+0x80/0x80 [fglrx] [ 27.464012] [] ? KAS_Initialize+0x113/0x1b0 [fglrx] [ 27.464012] [] ? firegl_init+0xe2/0xf0 [fglrx] [ 27.464012] [] ? firegl_find_interrupt_by_sourceid+0x50/0x50 [fglrx] [ 27.464012] [] ? IRQMGR_CallbackWrapper+0x20/0x20 [fglrx] [ 27.464012] [] ? firegl_init_module+0x27e/0x1000 [fglrx] [ 27.464012] [] ? 0xc1012000 [ 27.468510] [] ? do_one_initcall+0xb3/0x200 [ 27.468510] [] ? preempt_schedule_common+0x22/0x40 [ 27.468510] [] ? _cond_resched+0x1c/0x30 [ 27.468510] [] ? kmem_cache_alloc_trace+0x89/0x1f0 [ 27.468510] [] ? do_init_module+0x28/0x1e7 [ 27.468510] [] ? do_init_module+0x60/0x1e7 [ 27.468510] [] ? load_module+0x1676/0x1c10 [ 27.468510] [] ? __symbol_put+0x40/0x40 [ 27.468510] [] ? SyS_finit_module+0x9a/0xc0 [ 27.468510] [] ? entry_SYSCALL_64_fastpath+0x16/0x75 [ 27.468510] Code: df 00 00 00 48 89 54 24 08 89 4c 24 04 ff e6 0f 29 7b f1 0f 29 73 e1 0f 29 6b d1 0f 29 63 c1 0f 29 5b b1 0f 29 53 a1 0f 29 4b 91 <0f> 29 43 81 e8 26 9a fc ff 48 89 c7 e8 5e ae fd ff 44 89 e1 c1 [ 27.469827] RIP [] firegl_trace+0x61/0x1e0 [fglrx] [ 27.469827] RSP [ 27.471417] ---[ end trace 8a2116025344bc47 ]--- ProblemType: Bug DistroRelease: Ubuntu 15.10 Pac
[Desktop-packages] [Bug 1505720] Re: kernel oops in fglrx
A bit info un subject: http://ati.cchtml.com/show_bug.cgi?id=1189 ** Bug watch added: ATi Linux Platform Bugs #1189 http://ati.cchtml.com/show_bug.cgi?id=1189 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1505720 Title: kernel oops in fglrx Status in fglrx-installer package in Ubuntu: Confirmed Bug description: After updating to willy, fglrx oops: Oct 13 16:40:57 alice kernel: <6>[fglrx] Maximum main memory to use for locked dma buffers: 15620 MBytes. Oct 13 16:40:57 alice kernel: <6>[fglrx] vendor: 1002 device: 6740 revision: 0 count: 1 Oct 13 16:40:57 alice kernel: <6>[fglrx] ioport: bar 4, base 0x4000, size: 0x100 Oct 13 16:40:57 alice kernel: general protection fault: [#1] SMP Oct 13 16:40:57 alice kernel: Modules linked in: iwldvm(+) serio_raw mac80211 joydev input_leds snd_hda_codec_idt(+) snd_usb_audio(+) snd_hda_co Oct 13 16:40:57 alice kernel: CPU: 1 PID: 449 Comm: systemd-udevd Tainted: P OE 4.2.0-16-generic #19-Ubuntu Oct 13 16:40:57 alice kernel: Hardware name: Hewlett-Packard HP EliteBook 8560w/1631, BIOS 68SVD Ver. F.60 03/12/2015 Oct 13 16:40:57 alice kernel: task: 8800b943 ti: 8800b9438000 task.ti: 8800b9438000 Oct 13 16:40:57 alice kernel: RIP: 0010:[] [] firegl_trace+0x61/0x1e0 [fglrx] Oct 13 16:40:57 alice kernel: RSP: 0018:8800b943ba78 EFLAGS: 00010282 Oct 13 16:40:57 alice kernel: RAX: 0001 RBX: 8800b943bb57 RCX: 12cf Oct 13 16:40:57 alice kernel: RDX: c0930430 RSI: c0734251 RDI: 0004 Oct 13 16:40:57 alice kernel: RBP: 0001 R08: R09: c09994f0 Oct 13 16:40:57 alice kernel: R10: 880422ea4000 R11: c073f1b0 R12: 000d Oct 13 16:40:57 alice kernel: R13: R14: R15: c09994f0 Oct 13 16:40:57 alice kernel: FS: 7fa3caa628c0() GS:88043dc4() knlGS: Oct 13 16:40:57 alice kernel: CS: 0010 DS: ES: CR0: 80050033 Oct 13 16:40:57 alice kernel: CR2: 7fa3caa8e000 CR3: b942e000 CR4: 000406e0 Oct 13 16:40:57 alice kernel: Stack: Oct 13 16:40:57 alice kernel: 12cf0092 c0930430 0092 0092 Oct 13 16:40:57 alice kernel: 8800b943bad8 816bf58c 8800b943bb4e 88042ad3f400 Oct 13 16:40:57 alice kernel: 8800b943bb5e 0246 811deabd Oct 13 16:40:57 alice kernel: Call Trace: Oct 13 16:40:57 alice kernel: [] ? pci_conf1_read+0xbc/0x100 Oct 13 16:40:57 alice kernel: [] ? __kmalloc+0x1ad/0x250 Oct 13 16:40:57 alice kernel: [] ? KCL_MEM_SmallBufferAlloc+0x13/0x20 [fglrx] Oct 13 16:40:57 alice kernel: [] ? KCL_STR_Memcpy+0xe/0x10 [fglrx] Oct 13 16:40:57 alice kernel: [] ? klist_next+0x25/0x100 Oct 13 16:40:57 alice kernel: [] ? asyncioSvcInitContext+0x30/0x30 [fglrx] Oct 13 16:40:57 alice kernel: [] ? pci_do_find_bus+0x60/0x60 Oct 13 16:40:57 alice kernel: [] ? KAS_Initialize+0x113/0x1b0 [fglrx] Oct 13 16:40:57 alice kernel: [] ? firegl_init+0xe2/0xf0 [fglrx] Oct 13 16:40:57 alice kernel: [] ? firegl_find_interrupt_by_sourceid+0x50/0x50 [fglrx] Oct 13 16:40:57 alice kernel: [] ? IRQMGR_CallbackWrapper+0x20/0x20 [fglrx] Oct 13 16:40:57 alice kernel: [] ? firegl_init_module+0x27e/0x1000 [fglrx] Oct 13 16:40:57 alice kernel: [] ? 0xc13cb000 Oct 13 16:40:57 alice kernel: [] ? do_one_initcall+0xb3/0x200 Oct 13 16:40:57 alice kernel: [] ? __vunmap+0x95/0xf0 Oct 13 16:40:57 alice kernel: [] ? kmem_cache_alloc_trace+0x187/0x1f0 Oct 13 16:40:57 alice kernel: [] ? do_init_module+0x28/0x1e7 Oct 13 16:40:57 alice kernel: [] ? do_init_module+0x60/0x1e7 Oct 13 16:40:57 alice kernel: [] ? load_module+0x1676/0x1c10 Oct 13 16:40:57 alice kernel: [] ? __symbol_put+0x60/0x60 Oct 13 16:40:57 alice kernel: [] ? kernel_read+0x50/0x80 Oct 13 16:40:57 alice kernel: [] ? SyS_finit_module+0xb9/0xf0 Oct 13 16:40:57 alice kernel: [] ? entry_SYSCALL_64_fastpath+0x16/0x75 Oct 13 16:40:57 alice kernel: Code: df 00 00 00 48 89 54 24 08 89 4c 24 04 ff e6 0f 29 7b f1 0f 29 73 e1 0f 29 6b d1 0f 29 63 c1 0f 29 5b b1 0f Oct 13 16:40:57 alice kernel: RIP [] firegl_trace+0x61/0x1e0 [fglrx] Oct 13 16:40:57 alice kernel: RSP Oct 13 16:40:57 alice kernel: ---[ end trace 174522451c72da65 ]--- ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: fglrx 2:15.201-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.19.1-0ubuntu2 Architecture: amd64 Date: Tue Oct 13 16:59:03 2015 ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/b
[Desktop-packages] [Bug 1277894] Re: GExiv2 python wrapper broken
Problem is because overriden GExiv2.py tries to import _glib which
doesn't exists and not even needed.
Quick hack is to remove string "from gi import _glib" from
/usr/lib/python2.7/dist-packages/gi/overrides/GExiv2.py
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gexiv2 in Ubuntu.
https://bugs.launchpad.net/bugs/1277894
Title:
GExiv2 python wrapper broken
Status in “gexiv2” package in Ubuntu:
Confirmed
Bug description:
Ubuntu Trusty Tahr (development branch)
Release: 14.04
gir1.2-gexiv2-0.4: Installed: 0.7.0-1
I can import the Python wrapper, but when initializing a Metadata object, I
get an error:
"TypeError: GObject.__init__() takes exactly 0 arguments (1 given)"
It doesn't work in both python 2.7 and 3.3.
$ python
>>> from gi.repository import GExiv2
>>> GExiv2.Metadata('foo.png')
Traceback (most recent call last):
File "", line 1, in
TypeError: GObject.__init__() takes exactly 0 arguments (1 given)
>>>
$ python3
>>> from gi.repository import GExiv2
>>> GExiv2.Metadata('foo.png')
Traceback (most recent call last):
File "", line 1, in
TypeError: GObject.__init__() takes exactly 0 arguments (1 given)
>>>
p.s. according to: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=697204#32
the Python overrides are not installed?
however, they seem to be:
$ locate GExiv2.py
/usr/lib/python2.7/dist-packages/gi/overrides/GExiv2.py
/usr/lib/python3/dist-packages/gi/overrides/GExiv2.py
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gexiv2/+bug/1277894/+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
