[Desktop-packages] [Bug 1954980] Re: [snap] Chromium showing Japanese fonts incorrectly

[wdoekes]

Today it was experimental.refresh-app-awareness expiry time. It claimed
it had waited long enough and did the refresh anyway without consulting
me.

Immediately my fonts broke. And, as usual, the red dot in the Ubuntu
Dock (the "running applications indicator") next to the Chromium icon
disappeared: a click on that icon will now open a _new_ Chromium instead
of revealing the running one. (Another poor side effect from this snap
auto-refresh thing.)

Olivier: do you happen to know where I can find this expiry-awareness
timer and raise it to a million days?

-- 
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/1954980

Title:
  [snap] Chromium showing Japanese fonts incorrectly

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  It simply shows square rectangles for all Japanese characters this
  occurred after a recent update (earlier this week), a restart fixed it
  the first time but now it has reverted, probably after another update.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  ProcVersionSignature: Ubuntu 5.4.0-91.102-generic 5.4.151
  Uname: Linux 5.4.0-91-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec 16 11:54:12 2021
  InstallationDate: Installed on 2019-02-08 (1041 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Snap: chromium 96.0.4664.110 (latest/stable)
  SnapSource: ubuntu/+source/chromium-browser
  UpgradeStatus: Upgraded to focal on 2021-12-01 (14 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1954980/+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 1954980] Re: [snap] Chromium showing Japanese fonts incorrectly

[wdoekes]

Okay. That experimental.refresh-app-awareness did not fix it.

This morning (16 March), while switching tabs, the font "change"
occurred visibly again. Apparently I'm not looking at a fresh Chromium.
Yet still there is _something_ that messed up the fonts.

Here's some system info:

 $ snap list --all chromium 
 Name  VersionRev   Tracking   Publisher   Notes
 chromium  98.0.4758.91868  latest/stable  canonical✓  disabled
 chromium  96.0.4664.110  1854  latest/stable  canonical✓  disabled
 chromium  98.0.4758.54   1873  latest/stable  canonical✓  disabled
 chromium  97.0.4692.99   1878  latest/stable  canonical✓  disabled
 chromium  98.0.4758.80   1895  latest/stable  canonical✓  disabled
 chromium  98.0.4758.80   1899  latest/stable  canonical✓  disabled
 chromium  98.0.4758.102  1912  latest/stable  canonical✓  disabled
 chromium  99.0.4844.51   1926  latest/stable  canonical✓  -

Running processes and start-time:

 $ ps -ho lstart,command -p $(pgrep -f chromium | tr '\n' , | sed -e
's/,$//') | awk '{print $2 " " $3 " " $6 " " $7}' | uniq -c

  1 Feb 11 /snap/chromium/1899/usr/lib/chromium-browser/chrome 
--password-store
  3 Feb 11 /snap/chromium/1899/usr/lib/chromium-browser/chrome --type=zygote
  1 Mar 7  /snap/chromium/1926/usr/lib/chromium-browser/chrome 
--password-store
  3 Mar 7  /snap/chromium/1926/usr/lib/chromium-browser/chrome --type=zygote
  1 Mar 7  /snap/chromium/1926/usr/lib/chromium-browser/chrome 
--type=gpu-process
  2 Mar 7  /snap/chromium/1926/usr/lib/chromium-browser/chrome 
--type=utility
  4 Mar 7  /snap/chromium/1926/usr/lib/chromium-browser/chrome 
--type=renderer
  1 Mar 8  /snap/chromium/1926/usr/lib/chromium-browser/chrome 
--type=utility
  1 Mar 8  /snap/chromium/1926/usr/lib/chromium-browser/chrome 
--type=renderer
  1 Mar 9  /snap/chromium/1926/usr/lib/chromium-browser/chrome 
--type=renderer
  1 Mar 14 /snap/chromium/1926/usr/lib/chromium-browser/chrome 
--type=renderer
 34 Mar 15 /snap/chromium/1926/usr/lib/chromium-browser/chrome 
--type=renderer
  1 Mar 15 /snap/chromium/1926/usr/lib/chromium-browser/chrome 
--type=utility
  2 Mar 15 /snap/chromium/1926/usr/lib/chromium-browser/chrome 
--type=renderer

So, apparently there _are_ two chromiums running at the same time. Not
sure why, but that might explain conflicts. The old one was branched off
a --password-store parent.

Looking at the age in the fontconfig dir:

 $ ls /var/snap/chromium/common/fontconfig/ -ltr
 total 1700
 -rw-r--r-- 1 root root151 mrt  2 15:39 fonts.conf
 -rw-r--r-- 1 root root408 mrt  2 15:39 
34e0e5ac-5c62-4453-a219-f92185a510d1-le64.cache-7
 ...
 -rw-r--r-- 1 root root104 mrt  2 15:39 
34e3ea57-0766-47d7-ac34-3152aff3ab1c-le64.cache-7
 -rw-r--r-- 1 root root152 mrt  2 15:39 
2bdf00a0-773f-43e6-bc52-f8023b64a749-le64.cache-7

So, all files are from the same date and not recently changed or
something.

Steps I did now:

- $ sudo rm /var/snap/chromium/common/fontconfig/*

- fonts were still bad

- stopping chromium (alt-4)

- observe how the old chromium is still running:

  $ ps -ho lstart,command -p $(pgrep -f chromium | tr '\n' , | sed -e 's/,$//') 
| awk '{print $2 " " $3 " " $6 " " $7}' | uniq -c
  
  1 Feb 11 /snap/chromium/1899/usr/lib/chromium-browser/chrome 
--password-store
  3 Feb 11 /snap/chromium/1899/usr/lib/chromium-browser/chrome --type=zygote

- start chromium again
 
- fonts are good again

I'm killing off the old chromium/1899 now:

 $ kill 965195  965392  965393  965395

 (Where the parent 965195 refuses to die without SIGKILL.)


Restarted chromium again, for good measure.

 $ ps -ho lstart,command -p $(pgrep -f chromium | tr '\n' , | sed -e 's/,$//') 
| awk '{print $2 " " $3 " " $6 " " $7}' | uniq -c
  1 Mar 16 /snap/chromium/1926/usr/lib/chromium-browser/chrome 
--password-store
  3 Mar 16 /snap/chromium/1926/usr/lib/chromium-browser/chrome --type=zygote
  1 Mar 16 /snap/chromium/1926/usr/lib/chromium-browser/chrome 
--type=gpu-process
  2 Mar 16 /snap/chromium/1926/usr/lib/chromium-browser/chrome 
--type=utility
  9 Mar 16 /snap/chromium/1926/usr/lib/chromium-browser/chrome 
--type=renderer

Observe that the fontconfig directory is empty at this point (even
though chromium has started twice after purging it).

Now wait for the issue to reappear...

-- 
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/1954980

Title:
  [snap] Chromium showing Japanese fonts incorrectly

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  It simply shows square rectangles for all Japanese characters this
  occurred after a recent update (earlier this week), a restart fixed it
  the first time but now it has reverted, probably after another update.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  ProcVersionSignature: Ubuntu 

[Desktop-packages] [Bug 1954980] Re: [snap] Chromium showing Japanese fonts incorrectly

[wdoekes]

I suspect OP suffers from this:

www.osso.nl/blog/chromium-snap-wrong-fonts

Clearing out the font cache `rm /var/snap/chromium/common/fontconfig/*`
and restarting chromium is the only thing that reliably works for me.

I think "Refresh App Awareness" might be a workable workaround, as
Chromium tends to update when I least want it. Enabling that now.

-- 
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/1954980

Title:
  [snap] Chromium showing Japanese fonts incorrectly

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  It simply shows square rectangles for all Japanese characters this
  occurred after a recent update (earlier this week), a restart fixed it
  the first time but now it has reverted, probably after another update.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  ProcVersionSignature: Ubuntu 5.4.0-91.102-generic 5.4.151
  Uname: Linux 5.4.0-91-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec 16 11:54:12 2021
  InstallationDate: Installed on 2019-02-08 (1041 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Snap: chromium 96.0.4664.110 (latest/stable)
  SnapSource: ubuntu/+source/chromium-browser
  UpgradeStatus: Upgraded to focal on 2021-12-01 (14 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1954980/+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 1956888] Re: [upstream] regression: drag'n'drop broken

[wdoekes]

Confirmed with 98.0.4758.54:

- the pasting of content in an unrelated X window is _fixed_;

- the sorting is _fixed_;

- the moving of Tabs is _fixed_.

Thanks!

-- 
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/1956888

Title:
  [upstream] regression: drag'n'drop broken

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 21.10
  Chromium is installed via snap.
  chromium97.0.4692.711864   latest/stable

  Since a few days (weeks ?) I can't anymore drag and drop my bookmarks in the 
bookmarks view (control + shift + O) nor directly in the bookmarks bar. 
  Bookmarks folders have the same problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1956888/+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 1956838] Re: drag and drop broken chromium snap

[wdoekes]

Personally, I think it's a waste of space to setup timeshift just
because Ubuntu snapcraft cannot keep more than two versions alive... I
think there is something wrong in the snap ecosystem if we cannot choose
between more than two versions which are both broken.

My two cents.

-- 
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/1956838

Title:
  drag and drop broken chromium snap

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  With the latest Chromium refresh on 2020-01-07 to version 97.0.4692.71
  Chromium will not drag and drop selected text onto any any application
  including Chromium.  In a virtual machine, I was able to revert the
  Chromium snap to version 96.0.4664.110 and drag and drop works.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1956838/+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 1956838] Re: drag and drop broken chromium snap

[wdoekes]

See also https://bugs.launchpad.net/ubuntu/+source/chromium-
browser/+bug/1956888/comments/10 for downgrading instructions and
possible upstream bug.

-- 
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/1956838

Title:
  drag and drop broken chromium snap

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  With the latest Chromium refresh on 2020-01-07 to version 97.0.4692.71
  Chromium will not drag and drop selected text onto any any application
  including Chromium.  In a virtual machine, I was able to revert the
  Chromium snap to version 96.0.4664.110 and drag and drop works.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1956838/+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 1956888] Re: can't manually sort bookmarks anymore

[wdoekes]

I think the relevant bug report is:
https://bugs.chromium.org/p/chromium/issues/detail?id=1279532

It causes havoc with Tab moving, and broken sortable lists (like the
bookmarks), and with pasting stuff to the wrong (X11) window. (See my
previous comment.)


Downgrading to a previous version (1854) should be a matter of:

# snap list chromium --all

# snap revert chromium --revision 1854


Maybe allow more historic snap packages than 2 in the future:

# snap set system refresh.retain=4


And if you've lost the 1854 snap for amd64, I have it here:
https://junk.devs.nu/2022/bugs/chromium_96.0.4664.110_snap_1854_amd64.snap

sha512sum
c636cd18798f0bb98138ec6aafa85b1ae460f415dfca5973d38cc3a70f0eb2b02629eaedf2b10acb561267bcdf73eb7f575c431d0ef56b5f350da855956c50b1

# snap install ./chromium_96.0.4664.110_snap_1854_amd64.snap --dangerous

(I think --dangerous is needed, but possibly not if you already had 1854
running before.)

-- 
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/1956888

Title:
  can't manually sort bookmarks anymore

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 21.10
  Chromium is installed via snap.
  chromium97.0.4692.711864   latest/stable

  Since a few days (weeks ?) I can't anymore drag and drop my bookmarks in the 
bookmarks view (control + shift + O) nor directly in the bookmarks bar. 
  Bookmarks folders have the same problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1956888/+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 1956888] Re: can't manually sort bookmarks anymore

[wdoekes]

Is this related to https://bugs.launchpad.net/ubuntu/+source/chromium-
browser/+bug/1956838/comments/4 perhaps?

That bug reared its head for me when I was using a drag-drop widget in a
website.

If it is, it is even uglier than you think.


> As a workaround, it's too bad we can't restore a bugfree version of chromium.

I've been pulling my hair out trying to find/download a working 1854
version, but that one got dropped when I tried beta/edge. Not a happy
camper.

-- 
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/1956888

Title:
  can't manually sort bookmarks anymore

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 21.10
  Chromium is installed via snap.
  chromium97.0.4692.711864   latest/stable

  Since a few days (weeks ?) I can't anymore drag and drop my bookmarks in the 
bookmarks view (control + shift + O) nor directly in the bookmarks bar. 
  Bookmarks folders have the same problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1956888/+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 1956838] Re: drag and drop broken chromium snap

[wdoekes]

I'm really unhappy with this, because it appears to paste text into the
window below it:

https://junk.devs.nu/2022/bugs/chromium_98.0.4758.9_snap_pastes_in_gedit.mp4
"""This is a video with two gedit windows side by side, and this bug report on 
top. When dragging and dropping text INSIDE the browser, it gets copied to a 
different windows BEHIND it."""

https://junk.devs.nu/2022/bugs/chromium_97.0.4692.71_snap_pastes_in_shell.mp4
"""This is a similar video, this time pasting text in a shell, back when I did 
not know that the mouse position of release was relevant. Unintentionally 
pasting text into a shell is not cool."""

Observed with chromium 97.0.4692.71 and 98.0.4758.9 on Ubuntu Focal.
I could not revert to the older version 1854 because snap had already removed 
it.

Walter Doekes
OSSO B.V.


P.S. This commit looks related:

commit  0d6d861a1f39380238f4163f1325f5802792d4d5
author  Joel HockeyWed Nov 17 20:27:34 2021
committer   Chromium LUCI CQ 
Wed Nov 
17 20:27:34 2021

[Merge to M97] Ignore X DragWidget when doing drag-drop image
Chrome has only recently supported image drag-drop between tabs,
and this has revealed a bug in the X drag-drop code.
When doing the drop drop, a DragWidget (semi-transparent version of
image being dragged) is created.  Since this image is under the cursor,
it was incorrectly chosen when XDragDropClient::ProcessMouseMove()
calls XTopmostWindowFinder::FindWindowAt().
The fix is to allow finder to take a set of windows to ignore, similar
to what is already done for FindLocalProcessWindowAt(). The
X11TopmostWindowFinder constructor now takes the ignore-set which
applies to both Find* functions.

Because, if it ignores its own window, then the dropped text may land in
a window below it.

-- 
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/1956838

Title:
  drag and drop broken chromium snap

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  With the latest Chromium refresh on 2020-01-07 to version 97.0.4692.71
  Chromium will not drag and drop selected text onto any any application
  including Chromium.  In a virtual machine, I was able to revert the
  Chromium snap to version 96.0.4664.110 and drag and drop works.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1956838/+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 1818987] Re: broken symlink to changelog.Debian.gz in chromium-browser

[wdoekes]

Hi Oliver, thanks for checking.

That's not what I meant though:

> chromium-codecs-ffmpeg are actual files

Yes, they are. So I *do* have *a* changelog.

But the chromium-browser files are not real files, and they point to the
wrong files, making it harder to find the chromium-browser changelog.

I wrote:

```
$ ls -l /usr/share/doc/chromium-browser/changelog.Debian.gz
lrwxrwxrwx 1 root root 51 feb 25 15:56
  /usr/share/doc/chromium-browser/changelog.Debian.gz
  -> ../chromium-codecs-ffmpeg-extra/changelog.Debian.gz
```

Checked again today with the newest 73.0.3683.75-0ubuntu0.18.04.1:

```
$ ls -l /usr/share/doc/chromium-browser/changelog.Debian.gz -l
lrwxrwxrwx 1 root root 51 mrt 12 21:59
  /usr/share/doc/chromium-browser/changelog.Debian.gz
  -> ../chromium-codecs-ffmpeg-extra/changelog.Debian.gz
```

It's not my system, it's really the .deb file:

```
$ dpkg-deb -c chromium-browser_73.0.3683.75-0ubuntu0.18.04.1_amd64.deb |
grep changelog
lrwxrwxrwx root/root 0 2019-03-12 21:59
  ./usr/share/doc/chromium-browser/changelog.Debian.gz ->
  ../chromium-codecs-ffmpeg-extra/changelog.Debian.gz
```

In my system, I don't have chromium-codecs-ffmpeg-extra (only without
"-extra"), so the links are dead.

Regards,
Walter

** 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/1818987

Title:
  broken symlink to changelog.Debian.gz in chromium-browser

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Related to https://bugs.launchpad.net/ubuntu/+source/cdbs/+bug/194574,
  which has to do with saving space, for some reason, the chromium-
  browser has its changelog symlinked to an optional package.

  Version: 72.0.3626.119-0ubuntu0.18

  Right now, I have chromium-codecs-ffmpeg installed, but the changelog
  links to documentation in chromium-codecs-ffmpeg-extra.

  ```
  $ dpkg -L chromium-browser | grep changelog.Debian
  /usr/share/doc/chromium-browser/changelog.Debian.gz

  $ dpkg -l | grep chromium-
  ii chromium-browser 72.0.3626.119-0ubuntu0.18.04.1 amd64 Chromium web 
browser, open-source version of Chrome
  ii chromium-codecs-ffmpeg 72.0.3626.119-0ubuntu0.18.04.1 amd64 Free ffmpeg 
codecs for the Chromium Browser

  $ ls -l /usr/share/doc/chromium-browser/changelog.Debian.gz
  lrwxrwxrwx 1 root root 51 feb 25 15:56 
/usr/share/doc/chromium-browser/changelog.Debian.gz -> 
../chromium-codecs-ffmpeg-extra/changelog.Debian.gz

  $ ls -l ../chromium-codecs-ffmpeg-extra/changelog.Debian.gz
  ls: cannot access '../chromium-codecs-ffmpeg-extra/changelog.Debian.gz': No 
such file or directory
  ```

  I don't think saving 2k warrants breaking sane access to the changelog:
  ```
  $ ls -l /usr/share/doc/chromium-browser/
  total 1108
  lrwxrwxrwx 1 root root 51 feb 25 15:56 changelog.Debian.gz -> 
../chromium-codecs-ffmpeg-extra/changelog.Debian.gz
  -rw-r--r-- 1 root root 1126239 okt 25 2017 copyright
  -rw-r--r-- 1 root root 2512 okt 25 2017 copyright.problems.gz
  -rw-r--r-- 1 root root 2975 okt 25 2017 README.source

  $ ls -l /usr/share/doc/chromium-codecs-ffmpeg/
  total 1104
  -rw-r--r-- 1 root root 2263 feb 25 15:56 changelog.Debian.gz
  -rw-r--r-- 1 root root 1126239 okt 25 2017 copyright
  ```

  That copyright file takes up actual space but is not symlinked, 
:thinking_face:
  ```
  $ md5sum /usr/share/doc/chromium-{browser,codecs-ffmpeg}/copyright
  983091d3a4c4e207f2146a911a7f7387 /usr/share/doc/chromium-browser/copyright
  983091d3a4c4e207f2146a911a7f7387 
/usr/share/doc/chromium-codecs-ffmpeg/copyright
  ```

  If anything, I would guess that the symlink should be the other way
  around:

  - chromium-codecs-ffmpeg/changelog.Debian.gz symlinked to 
../chromium-browser/changelog.Debian.gz
  - chromium-codecs-ffmpeg-extra/changelog.Debian.gz symlinked to 
../chromium-browser/changelog.Debian.gz

  (And optionally that copyright file as well.)

  Cheers,
  Walter Doekes
  OSSO B.V.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1818987/+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 1818987] [NEW] broken symlink to changelog.Debian.gz in chromium-browser

[wdoekes]

Public bug reported:

Related to https://bugs.launchpad.net/ubuntu/+source/cdbs/+bug/194574,
which has to do with saving space, for some reason, the chromium-browser
has its changelog symlinked to an optional package.

Version: 72.0.3626.119-0ubuntu0.18

Right now, I have chromium-codecs-ffmpeg installed, but the changelog
links to documentation in chromium-codecs-ffmpeg-extra.

```
$ dpkg -L chromium-browser | grep changelog.Debian
/usr/share/doc/chromium-browser/changelog.Debian.gz

$ dpkg -l | grep chromium-
ii chromium-browser 72.0.3626.119-0ubuntu0.18.04.1 amd64 Chromium web browser, 
open-source version of Chrome
ii chromium-codecs-ffmpeg 72.0.3626.119-0ubuntu0.18.04.1 amd64 Free ffmpeg 
codecs for the Chromium Browser

$ ls -l /usr/share/doc/chromium-browser/changelog.Debian.gz
lrwxrwxrwx 1 root root 51 feb 25 15:56 
/usr/share/doc/chromium-browser/changelog.Debian.gz -> 
../chromium-codecs-ffmpeg-extra/changelog.Debian.gz

$ ls -l ../chromium-codecs-ffmpeg-extra/changelog.Debian.gz
ls: cannot access '../chromium-codecs-ffmpeg-extra/changelog.Debian.gz': No 
such file or directory
```

I don't think saving 2k warrants breaking sane access to the changelog:
```
$ ls -l /usr/share/doc/chromium-browser/
total 1108
lrwxrwxrwx 1 root root 51 feb 25 15:56 changelog.Debian.gz -> 
../chromium-codecs-ffmpeg-extra/changelog.Debian.gz
-rw-r--r-- 1 root root 1126239 okt 25 2017 copyright
-rw-r--r-- 1 root root 2512 okt 25 2017 copyright.problems.gz
-rw-r--r-- 1 root root 2975 okt 25 2017 README.source

$ ls -l /usr/share/doc/chromium-codecs-ffmpeg/
total 1104
-rw-r--r-- 1 root root 2263 feb 25 15:56 changelog.Debian.gz
-rw-r--r-- 1 root root 1126239 okt 25 2017 copyright
```

That copyright file takes up actual space but is not symlinked, :thinking_face:
```
$ md5sum /usr/share/doc/chromium-{browser,codecs-ffmpeg}/copyright
983091d3a4c4e207f2146a911a7f7387 /usr/share/doc/chromium-browser/copyright
983091d3a4c4e207f2146a911a7f7387 /usr/share/doc/chromium-codecs-ffmpeg/copyright
```

If anything, I would guess that the symlink should be the other way
around:

- chromium-codecs-ffmpeg/changelog.Debian.gz symlinked to 
../chromium-browser/changelog.Debian.gz
- chromium-codecs-ffmpeg-extra/changelog.Debian.gz symlinked to 
../chromium-browser/changelog.Debian.gz

(And optionally that copyright file as well.)

Cheers,
Walter Doekes
OSSO B.V.

** Affects: chromium-browser (Ubuntu)
 Importance: Undecided
 Status: New

** Package changed: cdbs (Ubuntu) => chromium-browser (Ubuntu)

-- 
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/1818987

Title:
  broken symlink to changelog.Debian.gz in chromium-browser

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Related to https://bugs.launchpad.net/ubuntu/+source/cdbs/+bug/194574,
  which has to do with saving space, for some reason, the chromium-
  browser has its changelog symlinked to an optional package.

  Version: 72.0.3626.119-0ubuntu0.18

  Right now, I have chromium-codecs-ffmpeg installed, but the changelog
  links to documentation in chromium-codecs-ffmpeg-extra.

  ```
  $ dpkg -L chromium-browser | grep changelog.Debian
  /usr/share/doc/chromium-browser/changelog.Debian.gz

  $ dpkg -l | grep chromium-
  ii chromium-browser 72.0.3626.119-0ubuntu0.18.04.1 amd64 Chromium web 
browser, open-source version of Chrome
  ii chromium-codecs-ffmpeg 72.0.3626.119-0ubuntu0.18.04.1 amd64 Free ffmpeg 
codecs for the Chromium Browser

  $ ls -l /usr/share/doc/chromium-browser/changelog.Debian.gz
  lrwxrwxrwx 1 root root 51 feb 25 15:56 
/usr/share/doc/chromium-browser/changelog.Debian.gz -> 
../chromium-codecs-ffmpeg-extra/changelog.Debian.gz

  $ ls -l ../chromium-codecs-ffmpeg-extra/changelog.Debian.gz
  ls: cannot access '../chromium-codecs-ffmpeg-extra/changelog.Debian.gz': No 
such file or directory
  ```

  I don't think saving 2k warrants breaking sane access to the changelog:
  ```
  $ ls -l /usr/share/doc/chromium-browser/
  total 1108
  lrwxrwxrwx 1 root root 51 feb 25 15:56 changelog.Debian.gz -> 
../chromium-codecs-ffmpeg-extra/changelog.Debian.gz
  -rw-r--r-- 1 root root 1126239 okt 25 2017 copyright
  -rw-r--r-- 1 root root 2512 okt 25 2017 copyright.problems.gz
  -rw-r--r-- 1 root root 2975 okt 25 2017 README.source

  $ ls -l /usr/share/doc/chromium-codecs-ffmpeg/
  total 1104
  -rw-r--r-- 1 root root 2263 feb 25 15:56 changelog.Debian.gz
  -rw-r--r-- 1 root root 1126239 okt 25 2017 copyright
  ```

  That copyright file takes up actual space but is not symlinked, 
:thinking_face:
  ```
  $ md5sum /usr/share/doc/chromium-{browser,codecs-ffmpeg}/copyright
  983091d3a4c4e207f2146a911a7f7387 /usr/share/doc/chromium-browser/copyright
  983091d3a4c4e207f2146a911a7f7387 
/usr/share/doc/chromium-codecs-ffmpeg/copyright
  ```

  If anything, I would guess that the symlink should be the other way
  around:

  - 

[Desktop-packages] [Bug 1724557] Re: gnome-shell crashed with SIGSEGV in meta_logical_monitor_get_scale()

[wdoekes]

For the record, now that I've moved from Artful 17.10 to Bionic 18.04,
this bug is not affecting me anymore, but now bug #1724439 is.

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

Title:
  gnome-shell crashed with SIGSEGV in meta_logical_monitor_get_scale()

Status in Mutter:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Released

Bug description:
  Hi all, 
  Originally I was reporting bug 1717170, about session crash after monitor 
disconnect/switch-off/input change on desktop PC and the bug was fixed 
according to bug tracker. But now, after gnome-shell and mutter update, the 
crash goes worse. Now it is not just session kick-out but complete crash. Same 
events can be used to reproduce the crash. This time also crash files was 
created.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 18 13:52:07 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2017-09-11 (37 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170906)
  ProcCmdline: /usr/bin/gnome-shell
  SegvAnalysis:
   Segfault happened at: 0x7f475acbac30 :   
movss  0x38(%rdi),%xmm0
   PC (0x7f475acbac30) ok
   source "0x38(%rdi)" (0x0038) not located in a known VMA region (needed 
readable region)!
   destination "%xmm0" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   meta_logical_monitor_get_scale () from 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   meta_window_wayland_get_geometry_scale () from 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   meta_surface_actor_wayland_get_scale () from 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   meta_surface_actor_wayland_sync_state () from 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
  Title: gnome-shell crashed with SIGSEGV in meta_logical_monitor_get_scale()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1724557/+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 1724439] Re: gnome-shell crashed with SIGSEGV in meta_window_get_monitor() from ffi_call_unix64() from ffi_call() from gjs_invoke_c_function() from function_call()

[wdoekes]

I just upgraded to Ubuntu 18.04 with libmutter 3.28.0-2 and ran into
this; monitor poweroff/poweron yields a crash of gnome-shell. The good
news is that the applications are not killed like they were in 17.10
(with wayland?). But waiting for the ubuntu-bug crash file to get
generated isn't a good use of my time either.

For me, applying the following patch works:

  https://bug788834.bugzilla-
attachments.gnome.org/attachment.cgi?id=361331

Patched binaries are here:

  https://downloads.osso.nl/libmutter-3.28.0-ubuntu-
bionic/mutter_3.28.0-2osso1/

Cheers,
Walter Doekes
OSSO B.V.

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

Title:
  gnome-shell crashed with SIGSEGV in meta_window_get_monitor() from
  ffi_call_unix64() from ffi_call() from gjs_invoke_c_function() from
  function_call()

Status in Mutter:
  In Progress
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gnome-shell source package in Bionic:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/3e662975e4b7e6829b9d68d1c2b06f429e44c854

  ---

  left virtual box to update win10 came back and got error message

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 17 23:37:32 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2017-04-18 (182 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7feb2ed42d94 :mov
0x18(%rax),%eax
   PC (0x7feb2ed42d94) ok
   source "0x18(%rax)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   meta_window_get_monitor () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ?? () from /usr/lib/libgjs.so.0
   ?? () from /usr/lib/libgjs.so.0
  Title: gnome-shell crashed with SIGSEGV in meta_window_get_monitor()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1724439/+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 1748323] Re: /usr/lib/chromium-browser/chromium-browser:5:AsLocatedEvent:DispatchMouseEvent:DispatchEvent:non:DispatchEvent

[wdoekes]

Hi Olivier,

I'm sorry, I must've missed your reply. Apparently I did not auto-
subscribe to the bug-updates.

It crashed again today with 64.0.3282.167-0ubuntu0.17.10.1, so I went
here, saw your response and tried to reproduce: before upgrading it
crashed as expected, but with the latest version from your link
(65.0.3325.88-0ubuntu0.17.10.1) it did NOT crash.

So, that looks good :)

(One minor nit: my failed attempts at reproducing somehow broke the
scrolling in this Tab. The vertical slider works, but the mouse wheel
just stopped working, both for the entire window and for this textarea
where I'm typing this. In other Tabs the scroll-wheel works fine. And
attempting to reproduce this new bug in other Tabs failed thusfar.)


Cheers,
Walter

-- 
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/1748323

Title:
  /usr/lib/chromium-browser/chromium-
  browser:5:AsLocatedEvent:DispatchMouseEvent:DispatchEvent:non:DispatchEvent

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
chromium-browser.  This problem was most recently seen with package version 
64.0.3282.140-0ubuntu0.17.10.1, the problem page at 
https://errors.ubuntu.com/problem/2ba87566e823966fa28f4720cc19be87bdb35b98 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1748323/+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 1748323] Re: /usr/lib/chromium-browser/chromium-browser:5:AsLocatedEvent:DispatchMouseEvent:DispatchEvent:non:DispatchEvent

[wdoekes]

I've seen a crash with that exact backtrace on Artful just now.

Both on 64.0.3282.140-0ubuntu0.17.10.1 and on
64.0.3282.167-0ubuntu0.17.10.1.

For 140 I did not get a full backtrace because I could not locate the
dbgsym at the time. For 167 the backtrace ends in AsLocatedEvent() <-
DispatchMouseEvent() <- DispatchEvent() <- ...

Reproducing was as simple as:

- open a website where you can scroll
- set mouse scroll-wheel to keep scrolling (I have a button to disable friction)
- scroll
- right click on the webpage
- at that point, the context menu opens and the browser crashes

Many in the office can reproduce (also on Ubuntu 16.04), except for that
one guy who uses Xorg (not Wayland) on 17.10.

Cheers,
Walter

P.S. Bug report filed as https://errors.ubuntu.com/oops/7446be7c-
16f5-11e8-bbf2-fa163ebeb28a -- I think. I cannot view them myself.

-- 
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/1748323

Title:
  /usr/lib/chromium-browser/chromium-
  browser:5:AsLocatedEvent:DispatchMouseEvent:DispatchEvent:non:DispatchEvent

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
chromium-browser.  This problem was most recently seen with package version 
64.0.3282.140-0ubuntu0.17.10.1, the problem page at 
https://errors.ubuntu.com/problem/2ba87566e823966fa28f4720cc19be87bdb35b98 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1748323/+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 1724557] Re: gnome-shell crashed with SIGSEGV in meta_logical_monitor_get_scale()

[wdoekes]

@3v1n0: I suspect that this changeset -- which should be in 3.26.3 -- does the 
same:
https://gitlab.gnome.org/GNOME/mutter/commit/71b4ef5940d16f7d3cb7dca5c224784315803492

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

Title:
  gnome-shell crashed with SIGSEGV in meta_logical_monitor_get_scale()

Status in Mutter:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Committed

Bug description:
  Hi all, 
  Originally I was reporting bug 1717170, about session crash after monitor 
disconnect/switch-off/input change on desktop PC and the bug was fixed 
according to bug tracker. But now, after gnome-shell and mutter update, the 
crash goes worse. Now it is not just session kick-out but complete crash. Same 
events can be used to reproduce the crash. This time also crash files was 
created.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 18 13:52:07 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2017-09-11 (37 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170906)
  ProcCmdline: /usr/bin/gnome-shell
  SegvAnalysis:
   Segfault happened at: 0x7f475acbac30 :   
movss  0x38(%rdi),%xmm0
   PC (0x7f475acbac30) ok
   source "0x38(%rdi)" (0x0038) not located in a known VMA region (needed 
readable region)!
   destination "%xmm0" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   meta_logical_monitor_get_scale () from 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   meta_window_wayland_get_geometry_scale () from 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   meta_surface_actor_wayland_get_scale () from 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   meta_surface_actor_wayland_sync_state () from 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
  Title: gnome-shell crashed with SIGSEGV in meta_logical_monitor_get_scale()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1724557/+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 1726352] Re: gnome-shell crashed with SIGSEGV in meta_window_move_resize_request()

[wdoekes]

By the way, upstream appears to have a fix for this too:
https://gitlab.gnome.org/GNOME/mutter/commit/71b4ef5940d16f7d3cb7dca5c224784315803492

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

Title:
  gnome-shell crashed with SIGSEGV in meta_window_move_resize_request()

Status in Mutter:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/53c0d16d8db1d08fe8ae663d632981c54b476052

  ---

  Ordinary bug report in 17.10

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 23 13:08:15 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   b'org.gnome.shell' b'enabled-extensions' b"['hidetop...@mathieu.bidon.ca', 
'ubuntu-appindicat...@ubuntu.com', 'ubuntu-d...@ubuntu.com']"
   b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Terminal.desktop', 
'org.gnome.Nautilus.desktop', 'google-chrome.desktop', 
'jetbrains-rubymine.desktop', 'jetbrains-webstorm.desktop', 
'jetbrains-studio.desktop', 'keepass2.desktop', 'spotify.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
  InstallationDate: Installed on 2017-10-19 (3 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: /usr/bin/gnome-shell
  SegvAnalysis:
   Segfault happened at: 0x7f8d82fc8c5c:mov0x18(%rax),%esi
   PC (0x7f8d82fc8c5c) ok
   source "0x18(%rax)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%esi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   meta_window_x11_configure_request () at 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-shell crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lp lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1726352/+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 1726352] Re: gnome-shell crashed with SIGSEGV in meta_window_move_resize_request()

[wdoekes]

Perhaps this helps?
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1724557/comments/29
->
https://downloads.osso.nl/libmutter-3.26.2-ubuntu-artful/libmutter_3.26.2-0ubuntu0.1osso1/

Cheers,
Walter Doekes
OSSO B.V.

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

Title:
  gnome-shell crashed with SIGSEGV in meta_window_move_resize_request()

Status in Mutter:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/53c0d16d8db1d08fe8ae663d632981c54b476052

  ---

  Ordinary bug report in 17.10

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 23 13:08:15 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   b'org.gnome.shell' b'enabled-extensions' b"['hidetop...@mathieu.bidon.ca', 
'ubuntu-appindicat...@ubuntu.com', 'ubuntu-d...@ubuntu.com']"
   b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Terminal.desktop', 
'org.gnome.Nautilus.desktop', 'google-chrome.desktop', 
'jetbrains-rubymine.desktop', 'jetbrains-webstorm.desktop', 
'jetbrains-studio.desktop', 'keepass2.desktop', 'spotify.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
  InstallationDate: Installed on 2017-10-19 (3 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: /usr/bin/gnome-shell
  SegvAnalysis:
   Segfault happened at: 0x7f8d82fc8c5c:mov0x18(%rax),%esi
   PC (0x7f8d82fc8c5c) ok
   source "0x18(%rax)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%esi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   meta_window_x11_configure_request () at 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-shell crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lp lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1726352/+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 1724557] Re: gnome-shell crashed with SIGSEGV in meta_logical_monitor_get_scale()

[wdoekes]

In my case, applying just [3] wasn't enough.
[1] https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1724557
[2] https://bugzilla.gnome.org/show_bug.cgi?id=788764
[3] https://bug788764.bugzilla-attachments.gnome.org/attachment.cgi?id=361654

I also had to apply [6] to fix [5]:
[4] https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1726352
[5] https://bugzilla.gnome.org/show_bug.cgi?id=790207 (possibly?)
[6]
--- a/src/x11/window-x11.c
+++ b/src/x11/window-x11.c
@@ -1973,6 +1973,9 @@ meta_window_move_resize_request (MetaWindow *window,
   gboolean in_grab_op;
   MetaMoveResizeFlags flags;
 
+  if (!window->monitor)
+return;
+
   /* We ignore configure requests while the user is moving/resizing
* the window, since these represent the app sucking and fighting
* the user, most likely due to a bug in the app (e.g. pfaedit


I created builds for Artful here, which appear to work:
https://downloads.osso.nl/libmutter-3.26.2-ubuntu-artful/libmutter_3.26.2-0ubuntu0.1osso1/

The only added patch is:
https://downloads.osso.nl/libmutter-3.26.2-ubuntu-artful/libmutter_3.26.2-0ubuntu0.1osso1/handle_resizing_when_headless.patch

Cheers,
Walter Doekes
OSSO B.V.


** Bug watch added: GNOME Bug Tracker #790207
   https://bugzilla.gnome.org/show_bug.cgi?id=790207

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

Title:
  gnome-shell crashed with SIGSEGV in meta_logical_monitor_get_scale()

Status in Mutter:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Committed

Bug description:
  Hi all, 
  Originally I was reporting bug 1717170, about session crash after monitor 
disconnect/switch-off/input change on desktop PC and the bug was fixed 
according to bug tracker. But now, after gnome-shell and mutter update, the 
crash goes worse. Now it is not just session kick-out but complete crash. Same 
events can be used to reproduce the crash. This time also crash files was 
created.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 18 13:52:07 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2017-09-11 (37 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170906)
  ProcCmdline: /usr/bin/gnome-shell
  SegvAnalysis:
   Segfault happened at: 0x7f475acbac30 :   
movss  0x38(%rdi),%xmm0
   PC (0x7f475acbac30) ok
   source "0x38(%rdi)" (0x0038) not located in a known VMA region (needed 
readable region)!
   destination "%xmm0" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   meta_logical_monitor_get_scale () from 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   meta_window_wayland_get_geometry_scale () from 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   meta_surface_actor_wayland_get_scale () from 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   meta_surface_actor_wayland_sync_state () from 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
  Title: gnome-shell crashed with SIGSEGV in meta_logical_monitor_get_scale()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1724557/+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 1729028] Re: gnome-shell crashes when monitor sleeps or is turned off

[wdoekes]

Stack trace looks like https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/1724557 here too. Guessing this is a duplicate.

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

Title:
  gnome-shell crashes when monitor sleeps or is turned off

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Gnome shell crashes reliably and only after a period of inactivity
  (15+ minutes). I have not seen it crash while using the desktop - even
  for hours at a time. I suspect it has something to do with locking the
  screen or turning off the monitor. However even after attempting to
  disable both lockscreen and blank screen it still happens.

  After a crash dmesg shows [ 3726.608957] gnome-shell[2666]: segfault
  at 38 ip 7fc6a7330c30 sp 7fff0d12fe78 error 4 in
  libmutter-1.so.0.0.0[7fc6a72de000+141000]

  When the crash happens it goes back to the login screen. Logging in
  works fine.

  It happens pretty reliably but will sometimes successfully lock and
  blank the screen. I would say it happens 90% of the time I leave the
  computer alone for awhile.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 31 11:34:11 2017
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 
'google-chrome.desktop', 'firefox.desktop', 'code.desktop', 
'org.gnome.Terminal.desktop', 'libreoffice-writer.desktop', 
'libreoffice-calc.desktop', 'libreoffice-impress.desktop', 
'org.gnome.Software.desktop', 'gnome-control-center.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'clock-format' b"'12h'"
   b'org.gnome.desktop.interface' b'text-scaling-factor' b'1.25'
  InstallationDate: Installed on 2017-07-18 (105 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-10-18 (12 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1729028/+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 1729028] Re: gnome-shell crashes when monitor sleeps or is turned off

[wdoekes]

Yes. Also experiencing these crashes since I switched from Zesty to
Artful yesterday. A lock-screen reproduces the crash, as does turning
the monitor off.

I have a UWQHD (3440×1440) resolution, if that matters, on my Dell
monitor. I'll try to gather some more debug info.

This is highly annoying, as all my open windows are destroyed as soon as
a leave my workstation (cannot leave it running without locked screen
obviously).


** Changed in: gnome-shell (Ubuntu)
   Status: Expired => Confirmed

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

Title:
  gnome-shell crashes when monitor sleeps or is turned off

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Gnome shell crashes reliably and only after a period of inactivity
  (15+ minutes). I have not seen it crash while using the desktop - even
  for hours at a time. I suspect it has something to do with locking the
  screen or turning off the monitor. However even after attempting to
  disable both lockscreen and blank screen it still happens.

  After a crash dmesg shows [ 3726.608957] gnome-shell[2666]: segfault
  at 38 ip 7fc6a7330c30 sp 7fff0d12fe78 error 4 in
  libmutter-1.so.0.0.0[7fc6a72de000+141000]

  When the crash happens it goes back to the login screen. Logging in
  works fine.

  It happens pretty reliably but will sometimes successfully lock and
  blank the screen. I would say it happens 90% of the time I leave the
  computer alone for awhile.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 31 11:34:11 2017
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 
'google-chrome.desktop', 'firefox.desktop', 'code.desktop', 
'org.gnome.Terminal.desktop', 'libreoffice-writer.desktop', 
'libreoffice-calc.desktop', 'libreoffice-impress.desktop', 
'org.gnome.Software.desktop', 'gnome-control-center.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'clock-format' b"'12h'"
   b'org.gnome.desktop.interface' b'text-scaling-factor' b'1.25'
  InstallationDate: Installed on 2017-07-18 (105 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-10-18 (12 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1729028/+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 1734791] Re: gnome-keyring doesn't start gnome-keyring-ssh services

[wdoekes]

I have the same problem, but with gpg-agent, which also reverse-depends
on graphical-session-pre.target.

Also upgraded from 17.04 (clean install) to 17.10.

I'm not sure where when the --user graphical-session-pre.target is
supposed to get started (and by whom), but it appears it never does. If
I (re)start it manually, the gpg-agent does start, but then I have to
log out and in again to get the SSH_AGENT and related env to work.

I tried a quick fix where I started the --user graphical-session-
pre.target from a /usr/local/bin/gnome-session wrapper, but that was
still too late (the envvars did not appear).

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

Title:
  gnome-keyring doesn't start gnome-keyring-ssh services

Status in gnome-keyring package in Ubuntu:
  Confirmed

Bug description:
  Looking at the gnome-keyring packages in 17.10, I see the following
  files, which should be auto-starting the gnome-keyring ssh agent
  service:

  /usr/lib/systemd/user/gnome-keyring-ssh.service
  
/usr/lib/systemd/user/graphical-session-pre.target.wants/gnome-keyring-ssh.service

  As well, I seem to have a file in ~/.config/autostart/gnome-keyring-
  ssh.desktop which should also start gnome-keyring-daemon with the
  --components=ssh option.

  However, in my actual GNOME session on Wayland, gnome-keyring-daemon
  is running with the following options:

  "/usr/bin/gnome-keyring-daemon --daemonize --login"

  and there are no SSH-AGENT related env vars set, and common ssh
  commands like ssh-add do not work.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-keyring 3.20.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Nov 27 16:56:40 2017
  InstallationDate: Installed on 2016-07-08 (507 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: gnome-keyring
  UpgradeStatus: Upgraded to artful on 2017-10-19 (39 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1734791/+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 1710789] Re: chromium does not open downloaded files

[wdoekes]

Yeap, that fixes things. Thanks!

-- 
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/1710789

Title:
  chromium does not open downloaded files

Status in chromium-browser package in Ubuntu:
  In Progress

Bug description:
  I have up to date Ubuntu 17.04. Recently, Chromium stoped to open
  downloaded files.

  If i download and open doc file from chromium, in command line i see
  the following message:

  /usr/lib/libreoffice/program/soffice.bin: relocation error:
  /usr/lib/x86_64-linux-gnu/libgdk-3.so.0: symbol
  mir_display_config_release, version MIR_CLIENT_0.21 not defined in
  file libmirclient.so.9 with link time reference

  If i download pdf file i see the same message with evince instead of
  libreoffice.

  It looks like more general problem, but I still can open files from
  these two applications or using xdg-open.

  I tried to work with new chromium profile, but i get the same message
  no matter what and files cannot be opened.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1710789/+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 1641380] Re: chromium-browser: ERR_CERTIFICATE_TRANSPARENCY_REQUIRED for Symantec certs

[wdoekes]

s/the broken Xenial version is lower/the fixed Xenial version is lower/

(sorry)

-- 
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/1641380

Title:
  chromium-browser: ERR_CERTIFICATE_TRANSPARENCY_REQUIRED for Symantec
  certs

Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  Chromium browser in xenial no longer trusts Symantec issued
  certificates. See [1].

  1. https://bugs.chromium.org/p/chromium/issues/detail?id=664177

  Ubuntu release: 16.04
  chromium-browser: 53.0.2785.143-0ubuntu0.16.04.1.1254

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1641380/+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 1641380] Re: chromium-browser: ERR_CERTIFICATE_TRANSPARENCY_REQUIRED for Symantec certs

[wdoekes]

Okay, that didn't take long. My slack windows started to "Aw snap!"
within another 10 minutes.

Both the Xenial [*1] version and the version from Haw Loeung (hloeung)
[*2] work fine though. Where the second is better because the broken
Xenial version is lower and would be auto-replaced with the broken
Yakkety build until a fixed version is uploaded.

Answering w2vy's (tom-moulton) question: a fixed version will likely be
still higher and auto-update over these manually installed files. In
short: no manual uninstall will have to be performed.

[*1]
http://nl.archive.ubuntu.com/ubuntu/pool/universe/c/chromium-browser/chromium-browser_53.0.2785.143-0ubuntu0.16.04.1.1257_amd64.deb
http://nl.archive.ubuntu.com/ubuntu/pool/universe/c/chromium-browser/chromium-browser-l10n_53.0.2785.143-0ubuntu0.16.04.1.1257_all.deb
http://nl.archive.ubuntu.com/ubuntu/pool/universe/c/chromium-browser/chromium-codecs-ffmpeg-extra_53.0.2785.143-0ubuntu0.16.04.1.1257_amd64.deb

[*2] from: 
https://launchpad.net/~canonical-chromium-builds/+archive/ubuntu/stage/+sourcepub/7137607/+listing-archive-extra
https://launchpad.net/~canonical-chromium-builds/+archive/ubuntu/stage/+files/chromium-browser_53.0.2785.143-0ubuntu2.16.10.1323_amd64.deb
https://launchpad.net/~canonical-chromium-builds/+archive/ubuntu/stage/+files/chromium-browser-l10n_53.0.2785.143-0ubuntu2.16.10.1323_all.deb
https://launchpad.net/~canonical-chromium-builds/+archive/ubuntu/stage/+files/chromium-codecs-ffmpeg-extra_53.0.2785.143-0ubuntu2.16.10.1323_amd64.deb

Answering Eloquence's (eloquence) question:
- find the broken packages on your system:
  $ dpkg -l | grep chromium
- select and download the replacements from here:
  
https://launchpad.net/~canonical-chromium-builds/+archive/ubuntu/stage/+sourcepub/7137607/+listing-archive-extra
  (pay attention to your architecture (arm vs amd64))
- install the downloaded files:
  $ sudo dpkg -i THE_DOWNLOADED_FILES...


P.S. I'm a bit puzzled that the fix for Xenial didn't get into Yakkety 
immediately. Now I ran into this issue on two separate occasions.

-- 
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/1641380

Title:
  chromium-browser: ERR_CERTIFICATE_TRANSPARENCY_REQUIRED for Symantec
  certs

Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  Chromium browser in xenial no longer trusts Symantec issued
  certificates. See [1].

  1. https://bugs.chromium.org/p/chromium/issues/detail?id=664177

  Ubuntu release: 16.04
  chromium-browser: 53.0.2785.143-0ubuntu0.16.04.1.1254

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1641380/+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 1641380] Re: chromium-browser: ERR_CERTIFICATE_TRANSPARENCY_REQUIRED for Symantec certs

[wdoekes]

54.0.2840.100-0ubuntu0.16.10.1326 from 'ppa:canonical-chromium-
builds/stage' (on Yakkety) hasn't crashed yet. (Running for 10 minutes
now.) Beats having to switch to FF for some pages.

-- 
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/1641380

Title:
  chromium-browser: ERR_CERTIFICATE_TRANSPARENCY_REQUIRED for Symantec
  certs

Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  Chromium browser in xenial no longer trusts Symantec issued
  certificates. See [1].

  1. https://bugs.chromium.org/p/chromium/issues/detail?id=664177

  Ubuntu release: 16.04
  chromium-browser: 53.0.2785.143-0ubuntu0.16.04.1.1254

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1641380/+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 1309145] Re: Chromium 34+ ignores ComposeKey (with xim GTK_IM_MODULE)

[wdoekes]

Confirmed. No strange behaviour with 38.0.2125.111. Only expected and
working behaviour.

Good.

-- 
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/1309145

Title:
  Chromium 34+ ignores ComposeKey (with xim GTK_IM_MODULE)

Status in Chromium Browser:
  Unknown
Status in “chromium-browser” package in Ubuntu:
  Incomplete

Bug description:
  When entering the key combination
  AltGr + [  a
  in any text input field or address bar, it does not translate to ä (a umlaut) 
anymore. This worked in the pre-aura Chromium 33.

  ---
  Ubuntu 14.04

  UK International Keyboard

  $ echo $GTK_IM_MODULE
  xim

  Chromium  34.0.1847.116 (Developer Build 260972) Ubuntu 14.04 aura
  OSLinux
  Blink 537.36 (@170605)
  JavaScriptV8 3.24.35.22
  Flash 13.0.0.182
  User AgentMozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like 
Gecko) Ubuntu Chromium/34.0.1847.116 Chrome/34.0.1847.116 Safari/537.36
  Command Line   /usr/lib/chromium-browser/chromium-browser 
--ppapi-flash-path=/usr/lib/pepflashplugin-installer/libpepflashplayer.so 
--ppapi-flash-version=13.0.0.182 --enable-pinch --flag-switches-begin 
--enable-experimental-extension-apis --flag-switches-end

  (See also https://code.google.com/p/chromium/issues/detail?id=351230)

To manage notifications about this bug go to:
https://bugs.launchpad.net/chromium-browser/+bug/1309145/+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 1031718] Re: Obscure error messages caused by ubuntu patch

[wdoekes]

So. Apparently this has been fixed somewhere along the road to Ubuntu
14.04.

The patch is commented out in the debian/patches/series file in version 
1.3.0-0ubuntu2.
However, the debian/changelog doesn't tell me when that happened (or when it 
was added, for that matter).

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

Title:
  Obscure error messages caused by ubuntu patch

Status in “libjpeg-turbo” package in Ubuntu:
  Confirmed

Bug description:
  Environment:
  Description:Ubuntu 12.04 LTS
  Release:12.04
  libjpeg-turbo8  1.1.90+svn733-0ubuntu4.1

  Ubuntu's own patch (FixLibraryStartup.patch) causes obscure Error
  opening file for reading: Permission denied error messages.

  The patch adds some auxv related stuff to the library init that
  attempt to read /proc/self/auxv. If it fails the above error is
  printed usually ending up to application's log that's using the
  library. Looking at the log it's completely unclear where that error
  came from and what file was it trying to read.

  The /proc/self/auxv has 0400 permissions and is owned by the user who
  started the process. If the process drops privileges and setuid()'s to
  another user, the file is no longer readable.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libjpeg-turbo/+bug/1031718/+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 1309145] Re: Chromium 34 and 36 ignores ComposeKey (with xim GTK_IM_MODULE)

[wdoekes]

Nope. Not fixed there either. I get exactly this:
https://code.google.com/p/chromium/issues/detail?id=351230#c64
(the gdk_window_set_user_time called on non-toplevel error)

-- 
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/1309145

Title:
  Chromium 34 and 36 ignores ComposeKey (with xim GTK_IM_MODULE)

Status in Chromium Browser:
  Unknown
Status in “chromium-browser” package in Ubuntu:
  Incomplete

Bug description:
  When entering the key combination
  AltGr + [  a
  in any text input field or address bar, it does not translate to ä (a umlaut) 
anymore. This worked in the pre-aura Chromium 33.

  ---
  Ubuntu 14.04

  UK International Keyboard

  $ echo $GTK_IM_MODULE
  xim

  Chromium  34.0.1847.116 (Developer Build 260972) Ubuntu 14.04 aura
  OSLinux
  Blink 537.36 (@170605)
  JavaScriptV8 3.24.35.22
  Flash 13.0.0.182
  User AgentMozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like 
Gecko) Ubuntu Chromium/34.0.1847.116 Chrome/34.0.1847.116 Safari/537.36
  Command Line   /usr/lib/chromium-browser/chromium-browser 
--ppapi-flash-path=/usr/lib/pepflashplugin-installer/libpepflashplayer.so 
--ppapi-flash-version=13.0.0.182 --enable-pinch --flag-switches-begin 
--enable-experimental-extension-apis --flag-switches-end

  (See also https://code.google.com/p/chromium/issues/detail?id=351230)

To manage notifications about this bug go to:
https://bugs.launchpad.net/chromium-browser/+bug/1309145/+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 1309145] Re: Chromium 34 and 36 ignores ComposeKey (with xim GTK_IM_MODULE)

[wdoekes]

Funny, but that gives me completely different broken behaviour.

im-config writes to ~/.xinputrc:

  # im-config(8) generated on Thu, 07 Aug 2014 08:26:49 +0200
  run_im xim
  # im-config signiture: 89512b7941127eeda7d3e3ac5703f05e  -

And then I indeed get the same environment variables as you. (en_US)

In other applications the input works like expected, regular compose and my
extra combinations. In chromium, the following happens:
- in the address bar, regular compose works, but my extra combinations *don't*
- as soon as I press enter in the address bar, the compose key stops working
  altogether: both keys of the combination get discarded
- however, after the third attempt at reproducing, the regular compose stopped
  working: chromium now consistently silently eats all compose characters, even
  at startup.

That last behavioural change sounded like a local config issue, but removing
~/.config/chromium did not resolve anything. 

Also, switching the compose key from right-alt to right-ctrl does what you'd 
expect:
- in all applications the compose key is changed
- in chromium, the composed keys -- now with right-ctrl -- are eaten

-- 
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/1309145

Title:
  Chromium 34 and 36 ignores ComposeKey (with xim GTK_IM_MODULE)

Status in Chromium Browser:
  Unknown
Status in “chromium-browser” package in Ubuntu:
  Incomplete

Bug description:
  When entering the key combination
  AltGr + [  a
  in any text input field or address bar, it does not translate to ä (a umlaut) 
anymore. This worked in the pre-aura Chromium 33.

  ---
  Ubuntu 14.04

  UK International Keyboard

  $ echo $GTK_IM_MODULE
  xim

  Chromium  34.0.1847.116 (Developer Build 260972) Ubuntu 14.04 aura
  OSLinux
  Blink 537.36 (@170605)
  JavaScriptV8 3.24.35.22
  Flash 13.0.0.182
  User AgentMozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like 
Gecko) Ubuntu Chromium/34.0.1847.116 Chrome/34.0.1847.116 Safari/537.36
  Command Line   /usr/lib/chromium-browser/chromium-browser 
--ppapi-flash-path=/usr/lib/pepflashplugin-installer/libpepflashplayer.so 
--ppapi-flash-version=13.0.0.182 --enable-pinch --flag-switches-begin 
--enable-experimental-extension-apis --flag-switches-end

  (See also https://code.google.com/p/chromium/issues/detail?id=351230)

To manage notifications about this bug go to:
https://bugs.launchpad.net/chromium-browser/+bug/1309145/+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 1309145] Re: Chromium 34 and 36 ignores ComposeKey (with xim GTK_IM_MODULE)

[wdoekes]

** Summary changed:

- Chromium 34 ignores ComposeKey
+ Chromium 34 and 36 ignores ComposeKey (with xim GTK_IM_MODULE)

-- 
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/1309145

Title:
  Chromium 34 and 36 ignores ComposeKey (with xim GTK_IM_MODULE)

Status in Chromium Browser:
  Unknown
Status in “chromium-browser” package in Ubuntu:
  Incomplete

Bug description:
  When entering the key combination
  AltGr + [  a
  in any text input field or address bar, it does not translate to ä (a umlaut) 
anymore. This worked in the pre-aura Chromium 33.

  ---
  Ubuntu 14.04

  UK International Keyboard

  $ echo $GTK_IM_MODULE
  xim

  Chromium  34.0.1847.116 (Developer Build 260972) Ubuntu 14.04 aura
  OSLinux
  Blink 537.36 (@170605)
  JavaScriptV8 3.24.35.22
  Flash 13.0.0.182
  User AgentMozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like 
Gecko) Ubuntu Chromium/34.0.1847.116 Chrome/34.0.1847.116 Safari/537.36
  Command Line   /usr/lib/chromium-browser/chromium-browser 
--ppapi-flash-path=/usr/lib/pepflashplugin-installer/libpepflashplayer.so 
--ppapi-flash-version=13.0.0.182 --enable-pinch --flag-switches-begin 
--enable-experimental-extension-apis --flag-switches-end

  (See also https://code.google.com/p/chromium/issues/detail?id=351230)

To manage notifications about this bug go to:
https://bugs.launchpad.net/chromium-browser/+bug/1309145/+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 1309145] Re: Chromium 34 and 36 ignores ComposeKey (with xim GTK_IM_MODULE)

[wdoekes]

I can refute it. Over here is it *not* fixed with:

  Version 36.0.1985.125 Ubuntu 14.04 (283153)

I did a full restart, to be on the safe side.

My config:

  $ tail -n1 .profile 
  export GTK_IM_MODULE=xim # Compose key stuffs

  $ cat .XCompose 
  include %L   # import the default Compose file for your locale
  Multi_key slash question: ⸮ U2E2E # REVERSED QUESTION 
MARK (IRONY PUNCTUATION)
  # and add GTK_IM_MODULE=xim to ~/.profile

No composition works anywhere within chromium.
If I remove the GTK_IM_MODULE export and restart the X session, things work
like expected again.

-- 
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/1309145

Title:
  Chromium 34 and 36 ignores ComposeKey (with xim GTK_IM_MODULE)

Status in Chromium Browser:
  Unknown
Status in “chromium-browser” package in Ubuntu:
  Incomplete

Bug description:
  When entering the key combination
  AltGr + [  a
  in any text input field or address bar, it does not translate to ä (a umlaut) 
anymore. This worked in the pre-aura Chromium 33.

  ---
  Ubuntu 14.04

  UK International Keyboard

  $ echo $GTK_IM_MODULE
  xim

  Chromium  34.0.1847.116 (Developer Build 260972) Ubuntu 14.04 aura
  OSLinux
  Blink 537.36 (@170605)
  JavaScriptV8 3.24.35.22
  Flash 13.0.0.182
  User AgentMozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like 
Gecko) Ubuntu Chromium/34.0.1847.116 Chrome/34.0.1847.116 Safari/537.36
  Command Line   /usr/lib/chromium-browser/chromium-browser 
--ppapi-flash-path=/usr/lib/pepflashplugin-installer/libpepflashplayer.so 
--ppapi-flash-version=13.0.0.182 --enable-pinch --flag-switches-begin 
--enable-experimental-extension-apis --flag-switches-end

  (See also https://code.google.com/p/chromium/issues/detail?id=351230)

To manage notifications about this bug go to:
https://bugs.launchpad.net/chromium-browser/+bug/1309145/+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 1309145] Re: Chromium 34 ignores ComposeKey

[wdoekes]

Confirming: I switched to xim input method yesterday (for custom compose
combinations), and today I noticed that indeed the compose key does not
work in Chromium.

http://code.google.com/p/chromium/issues/detail?id=351230

Browser: Version 34.0.1847.116 Ubuntu 14.04 aura (260972) 
[34.0.1847.116-0ubuntu2]
OS: Trusty

-- 
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/1309145

Title:
  Chromium 34 ignores ComposeKey

Status in Chromium Browser:
  Unknown
Status in “chromium-browser” package in Ubuntu:
  Incomplete

Bug description:
  When entering the key combination
  AltGr + [  a
  in any text input field or address bar, it does not translate to ä (a umlaut) 
anymore. This worked in the pre-aura Chromium 33.

  ---
  Ubuntu 14.04

  UK International Keyboard

  $ echo $GTK_IM_MODULE
  xim

  Chromium  34.0.1847.116 (Developer Build 260972) Ubuntu 14.04 aura
  OSLinux
  Blink 537.36 (@170605)
  JavaScriptV8 3.24.35.22
  Flash 13.0.0.182
  User AgentMozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like 
Gecko) Ubuntu Chromium/34.0.1847.116 Chrome/34.0.1847.116 Safari/537.36
  Command Line   /usr/lib/chromium-browser/chromium-browser 
--ppapi-flash-path=/usr/lib/pepflashplugin-installer/libpepflashplayer.so 
--ppapi-flash-version=13.0.0.182 --enable-pinch --flag-switches-begin 
--enable-experimental-extension-apis --flag-switches-end

  (See also https://code.google.com/p/chromium/issues/detail?id=351230)

To manage notifications about this bug go to:
https://bugs.launchpad.net/chromium-browser/+bug/1309145/+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 1230172] Re: gnome-calculator menu unreachable when global menu is off

[wdoekes]

Thanks for that detailed explanation Michael.

I'm not sure why the other apps didn't pose any problems without the
indicator-appmenu. But it's all moot now.

The desktops have been upgraded to 14.04. Let's focus on the problems of
the future!

Closing. (If I have the power to do so.)

** Changed in: gnome-calculator (Ubuntu)
   Status: New = Invalid

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

Title:
  gnome-calculator menu unreachable when global menu is off

Status in “gnome-calculator” package in Ubuntu:
  Invalid

Bug description:
  The Ubuntu's new Enhanced Menu project[1] aims to add the option of
  choosing whether you want the Global menu or not.

  Due to a faulty upgrade, my Ubuntu 13.04 desktop turned out to be
  missing the indicator-appmenu (and dependencies). And without those,
  there was no global menu.

  That wasn't a problem for me, until I found out that I couldn't put
  the gnome-calculator back into PROGRAMMING mode because it had no menu
  to do so [2].

  I tried to hack around a bit in the code, but I didn't get very far.
  See patch attempt in [2].

  Kind regards,
  Walter Doekes
  OSSO B.V.

  [1] https://bugs.launchpad.net/unity/+bug/682788
  [2] http://wjd.nu/notes/2013#gnome-calculator-missing-menu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1230172/+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 1230172] Re: gnome-calculator menu unreachable when global menu is off

[wdoekes]

Did you see the workaround on my site? Using dconf-editor to switch the
mode?

(And hit the this bug affects me to increase its visibility.)

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

Title:
  gnome-calculator menu unreachable when global menu is off

Status in “gnome-calculator” package in Ubuntu:
  New

Bug description:
  The Ubuntu's new Enhanced Menu project[1] aims to add the option of
  choosing whether you want the Global menu or not.

  Due to a faulty upgrade, my Ubuntu 13.04 desktop turned out to be
  missing the indicator-appmenu (and dependencies). And without those,
  there was no global menu.

  That wasn't a problem for me, until I found out that I couldn't put
  the gnome-calculator back into PROGRAMMING mode because it had no menu
  to do so [2].

  I tried to hack around a bit in the code, but I didn't get very far.
  See patch attempt in [2].

  Kind regards,
  Walter Doekes
  OSSO B.V.

  [1] https://bugs.launchpad.net/unity/+bug/682788
  [2] http://wjd.nu/notes/2013#gnome-calculator-missing-menu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1230172/+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 1230172] [NEW] gnome-calculator menu unreachable when global menu is off

[wdoekes]

Public bug reported:

The Ubuntu's new Enhanced Menu project[1] aims to add the option of
choosing whether you want the Global menu or not.

Due to a faulty upgrade, my Ubuntu 13.04 desktop turned out to be
missing the indicator-appmenu (and dependencies). And without those,
there was no global menu.

That wasn't a problem for me, until I found out that I couldn't put the
gnome-calculator back into PROGRAMMING mode because it had no menu to do
so [2].

I tried to hack around a bit in the code, but I didn't get very far. See
patch attempt in [2].

Kind regards,
Walter Doekes
OSSO B.V.

[1] https://bugs.launchpad.net/unity/+bug/682788
[2] http://wjd.nu/notes/2013#gnome-calculator-missing-menu

** Affects: gnome-calculator (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  gnome-calculator menu unreachable when global menu is off

Status in “gnome-calculator” package in Ubuntu:
  New

Bug description:
  The Ubuntu's new Enhanced Menu project[1] aims to add the option of
  choosing whether you want the Global menu or not.

  Due to a faulty upgrade, my Ubuntu 13.04 desktop turned out to be
  missing the indicator-appmenu (and dependencies). And without those,
  there was no global menu.

  That wasn't a problem for me, until I found out that I couldn't put
  the gnome-calculator back into PROGRAMMING mode because it had no menu
  to do so [2].

  I tried to hack around a bit in the code, but I didn't get very far.
  See patch attempt in [2].

  Kind regards,
  Walter Doekes
  OSSO B.V.

  [1] https://bugs.launchpad.net/unity/+bug/682788
  [2] http://wjd.nu/notes/2013#gnome-calculator-missing-menu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1230172/+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