[Bug 1974446] [NEW] sngrep in Jammy segfaults in del_panel (fixed upstream)
Public bug reported: When pressing ESC after going into a trace, I got this: ``` (gdb) bt #0 0x77bf470b in del_panel () from /lib/x86_64-linux-gnu/libpanelw.so.6 #1 0x5556ab18 in ui_destroy (ui=0x555856a0 ) at curses/ui_panel.c:64 #2 ui_default_handle_key (ui=ui@entry=0x555856a0 , key=key@entry=27) at curses/ui_manager.c:292 #3 0xfdd6 in ui_wait_for_input () at curses/ui_manager.c:248 #4 main (argc=, argv=0x7fffe5c8) at ./src/main.c:435 ``` Looks very much like this bug: https://github.com/irontec/sngrep/issues/389 https://github.com/irontec/sngrep/commit/7ed9942c859bab13222d86b4d0fdd370c94664a3 # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.04 LTS Release:22.04 Codename: jammy # dpkg -l sngrep | grep ^ii ii sngrep 1.4.10-1 amd64Ncurses SIP Messages flow viewer sngrep 1.5.0 has been released a month ago. I think it would be nice if the Ubuntu version got bumped: https://github.com/irontec/sngrep/releases/tag/v1.5.0 Cheers, Walter Doekes OSSO B.V. ** Affects: sngrep (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1974446 Title: sngrep in Jammy segfaults in del_panel (fixed upstream) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sngrep/+bug/1974446/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1641236] Re: Confined processes inside container cannot fully access host pty device passed in by lxc exec
Ahyes, that fixes things on Ubuntu/Jammy as well: mkdir -p /etc/apparmor.d/disable # (did not exist, over here) ln -s /etc/apparmor.d/usr.bin.tcpdump /etc/apparmor.d/disable # (note, no sbin, but bin) apparmor_parser -R /etc/apparmor.d # (this is indeed needed, instead of an apparmor restart) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1641236 Title: Confined processes inside container cannot fully access host pty device passed in by lxc exec To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1641236/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1954980] Re: [snap] Chromium showing Japanese fonts incorrectly
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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1954980 Title: [snap] Chromium showing Japanese fonts incorrectly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1954980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964622] Re: MariaDB limits to 1000 parameters
https://jira.mariadb.org/browse/MDEV-27937 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964622 Title: MariaDB limits to 1000 parameters To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mariadb-10.3/+bug/1964622/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964622] Re: MariaDB limits to 1000 parameters
That is a likely culprit, as there are changes there after 10.3.32: $ git tag --contains a65d01a4cf04c744f9355bec186430540ce6ba08 | grep 10.3 -F mariadb-10.3.34 mariadb-10.3.33 commit a65d01a4cf04c744f9355bec186430540ce6ba08 Author: Dmitry Shulga Date: Wed Oct 20 19:24:31 2021 +0700 MDEV-23182: Server crashes in Item::fix_fields_if_needed / table_value_constr::prepare upon 2nd execution of PS Repeating execution of a query containing the clause IN with string literals in environment where the server variable in_predicate_conversion_threshold is set results in server abnormal termination in case the query is run as a Prepared Statement and conversion of charsets for string values in the query are required. The reason for server abnormal termination is that instances of the class Item_string created on transforming the IN clause into subquery were created on runtime memory root that is deallocated on finishing execution of Prepared statement. On the other hand, references to Items placed on deallocated memory root still exist in objects of the class table_value_constr. Subsequent running of the same prepared statement leads to dereferencing of pointers to already deallocated memory that could lead to undefined behaviour. To fix the issue the values being pushed into a values list for TVC are created by cloning their original items. This way the cloned items are allocate on the PS memroot and as consequences no dangling pointer does more exist. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964622 Title: MariaDB limits to 1000 parameters To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mariadb-10.3/+bug/1964622/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1954980] Re: [snap] Chromium showing Japanese fonts incorrectly
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1954980
Title:
[snap] Chromium showing Japanese fonts incorrectly
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1954980/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1954980] Re: [snap] Chromium showing Japanese fonts incorrectly
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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1954980 Title: [snap] Chromium showing Japanese fonts incorrectly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1954980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 331136] Re: [needs-packaging] GtkRadiant
This is nice and old :) Here's a starting point, if others are still interested: https://github.com/wdoekes/gtkradiant-deb/tree/v1.6.6-0wjd0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/331136 Title: [needs-packaging] GtkRadiant To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/331136/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956888] Re: [upstream] regression: drag'n'drop broken
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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956888 Title: [upstream] regression: drag'n'drop broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1956888/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956838] Re: drag and drop broken chromium snap
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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956838 Title: drag and drop broken chromium snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1956838/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956838] Re: drag and drop broken chromium snap
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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956838 Title: drag and drop broken chromium snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1956838/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956888] Re: can't manually sort bookmarks anymore
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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956888 Title: can't manually sort bookmarks anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1956888/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956888] Re: can't manually sort bookmarks anymore
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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956888 Title: can't manually sort bookmarks anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1956888/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956838] Re: drag and drop broken chromium snap
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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956838 Title: drag and drop broken chromium snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1956838/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949104] Re: netplan try is broken
Fix 0.103-0ubuntu5~20.04.3 appears to work on Focal. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949104 Title: netplan try is broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1949104/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768777] Re: libnvpair1linux doc contents have busted symlinks
Also affects Ubuntu/Focal: # readlink /usr/share/doc/zfs-zed/changelog.Debian.gz ../libnvpair1linux/changelog.Debian.gz # readlink /usr/share/doc/zfsutils-linux/changelog.Debian.gz ../libnvpair1linux/changelog.Debian.gz # readlink /usr/share/doc/zfsutils-linux/../libnvpair1linux/changelog.Debian.gz ../libnvpair1linux/changelog.Debian.gz So.. no changelog then. # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.2 LTS Release:20.04 Codename: focal # apt-cache policy zfsutils-linux zfsutils-linux: Installed: 0.8.3-1ubuntu12.12 Candidate: 0.8.3-1ubuntu12.12 Version table: *** 0.8.3-1ubuntu12.12 500 This is also an upgraded system. I tried removing a stale 'rc' zfs-doc (0.7.5-1ubuntu16.4), and then --reinstall'ing zfsutil-linux and libnvpair1linux, but I still have no docs, only broken symlinks. Any ideas? Cheers, Walter -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768777 Title: libnvpair1linux doc contents have busted symlinks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1768777/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768777] Re: libnvpair1linux doc contents have busted symlinks
Ok. I stand corrected. I reinstall of libnvpair1linux _did_ fix it. (After removing zfs-doc.) # apt-get install --reinstall libnvpair1linux # ls -l /usr/share/doc/libnvpair1linux/ total 76 -rw-r--r-- 1 root root 1615 jul 12 16:36 changelog.Debian.gz Move along.. nothing to see here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768777 Title: libnvpair1linux doc contents have busted symlinks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1768777/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934992] Re: rsync 3.2.x in Groovy depends on broken libxxhash 0.7.x
> ...so if a user has built against libxxhash for such > a use case that is supported by upstream, your proposal > for changing Focal would break them. *shrug* I'd rather have my build break now than succeed and get harder to debug issues with failing cross device communication. Well, I've done my part. Let me know if there's something I can do. I'll consider this closed on my end :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934992 Title: rsync 3.2.x in Groovy depends on broken libxxhash 0.7.x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xxhash/+bug/1934992/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934992] Re: rsync 3.2.x in Groovy depends on broken libxxhash 0.7.x
** Description changed: + **NOTE: This ticket has been moved/altered. Original problem referred to + rsync behaviour with libxxhash0. New subject is the changed ABI of + libxxhash0.** + + Original-Subject: rsync 3.2.x in Groovy depends on broken libxxhash + 0.7.x + + Actual problem: libxxhash0 in Focal exposes 128-bit xxhash (xxh128) + symbols which behave differently on versions of libxxhash0 in Groovy and + above. + + In xxhash 0.7.x there is this notice: + + https://github.com/Cyan4973/xxHash/blob/173e50be0509c6fb6c1bb74d95049ef61d7fdced/xxhash.h#L465-L476 + + > The XXH3 algorithm is still in development. + > The results it produces may still change in future versions. + > + > Results produced by v0.7.x are not comparable with results + > from v0.7.y. However, the API is completely stable, and it + > can safely be used for ephemeral data (local sessions). + > + > Avoid storing values in long-term storage until the + > algorithm is finalized. XXH3's return values will be + > officially finalized upon reaching v0.8.0. + + Unfortunately these ended up as usable symbols in xxhash 0.7.x in + Debian: + + > XXH128@Base 0.7.0 + (etc..) + + This means that those linking against libxxhash0 would get a binary + dependency on 0.7.0. But behaviour of xxh128 differs between 0.7 and + 0.8. So if you're linking against xxh128 from 0.8.x, it should binary- + depend on >=0.8 and not >=0.7. (And if possible, you should not use + xxh128 at all in 0.7.x.) + + The following Debian changeset fixes this for newer libxxhash0 builds: + + https://github.com/norbusan/debian- + xxhash/commit/b51053c86952dd13573b08344101172c88de847f + + > debian/libxxhash0.symbols + > - XXH128@Base 0.7.0 + > + XXH128@Base 0.8.0 + + But, this is not fully resolved until: + + - that Debian change lands in libxxhash0 in Ubuntu; + - packages linking against libxxhash0 (e.g. rsync) are rebuilt against this newer package, so the Depends is bumped to >=0.8; + - xxh128 in libxxhash0 in Focal is clearly marked as ephemeral (or removed altogether; this applies to xxh128 symbols libxxhash0 and an `xxh128sum` binary in the xxhash package) + + Cheers, + Walter Doekes + OSSO B.V. + + + ---vvv--- Original ticket below ---vvv--- + + **Problem** - $ rsync root@focal-system:/etc/.pwd.lock . - ERROR: .pwd.lock failed verification -- update discarded. - rsync error: some files/attrs were not transferred (see previous errors) - (code 23) at main.c(1816) [generator=3.2.3] + $ rsync root@focal-system:/etc/.pwd.lock . + ERROR: .pwd.lock failed verification -- update discarded. + rsync error: some files/attrs were not transferred + (see previous errors) + (code 23) at main.c(1816) [generator=3.2.3] - - $ rsync root@focal-system:/etc/.pwd.lock . --debug=all - opening connection using: ssh -l root focal-system rsync --server --sender \ - -e.LsfxCIvu . /etc/.pwd.lock (10 args) - (Client) Protocol versions: remote=31, negotiated=31 - Client negotiated checksum: xxh128 - ... - + $ rsync root@focal-system:/etc/.pwd.lock . --debug=all + opening connection using: ssh -l root focal-system rsync \ + --server --sender \ + -e.LsfxCIvu . /etc/.pwd.lock (10 args) + (Client) Protocol versions: remote=31, negotiated=31 + Client negotiated checksum: xxh128 + ... **Cause** - focal-system# dpkg -l | grep -E 'libxxhash|rsync' - ii libxxhash0:amd64 0.7.3-1 amd64 - ii rsync 3.2.3-2ubuntu1 amd64 - + focal-system# dpkg -l | grep -E 'libxxhash|rsync' + ii libxxhash0:amd64 0.7.3-1 amd64 + ii rsync 3.2.3-2ubuntu1 amd64 **Why this affects only us and not more people?** On Ubuntu/Focal, there is no rsync 3.2.3, only 3.1.3-8. But because we need the lz4 compression support we've fetched a newer rsync (from Groovy). However: the rsync 3.2.3 depends on libxxhash0 0.7.1+, while in fact it needs 0.8+. + **Details** - **Details** - - On a Ubuntu/Focal system we have installed a rsync 3.2.3 package from Ubuntu/Groovy because we need the lz4 compression support. - + On a Ubuntu/Focal system we have installed a rsync 3.2.3 package from + Ubuntu/Groovy because we need the lz4 compression support. focal-system# apt-cache show rsync Package: rsync ... Version: 3.2.3-2ubuntu1 Depends: lsb-base, libacl1 (>= 2.2.23), libc6 (>= 2.15), - liblz4-1 (>= 0.0~r130), libpopt0 (>= 1.14), libssl1.1 (>= 1.1.0), - libxxhash0 (>= 0.7.1), libzstd1 (>= 1.3.8), zlib1g (>= 1:1.1.4) + liblz4-1 (>= 0.0~r130), libpopt0 (>= 1.14), libssl1.1 (>= 1.1.0), + libxxhash0 (>= 0.7.1), libzstd1 (>= 1.3.8), zlib1g (>= 1:1.1.4) ... - Alongside this we had libxxhash0 0.7.3-1 from Focal: focal-system# apt-cache policy libxxhash0 libxxhash0: - Installed: 0.7.3-1 - Candidate: 0.7.3-1 - Version table: - *** 0.7.3-1 500 - 500 http://ARCHIVE/ubuntu focal/universe amd64 Packages - 100 /var/lib/dpkg/status -
[Bug 1934992] Re: rsync 3.2.x in Groovy depends on broken libxxhash 0.7.x
Thanks, Robie, for the excellent response. > Actually I'm not sure it's a symbol versioning issue now. Maybe this example can persuade you that there is a problem between (lib)xxhash in Focal and in Groovy: focal$ xxh128sum <(echo -n) 07fd4e968e916ae11f17545bce1061f1 /dev/fd/63 groovy$ xxh128sum <(echo -n) 99aa06d3014798d86001c324468d497f /dev/fd/63 > I suggest you find the fix and send it to wherever > the problem originates in our ecosystem (maybe Debian? > Or perhaps xxhash upstream?). Unless a supported > use case is presented, I think it's unlikely that > we'll carry a patch for this in Ubuntu. I think I can safely say now that the problem originates in the Debian package: if the symbols file is altered as I have done here [1] the problem goes away: [1] https://github.com/norbusan/debian-xxhash/issues/3 ``` --- a/debian/libxxhash0.symbols +++ b/debian/libxxhash0.symbols @@ -1,9 +1,9 @@ libxxhash.so.0 libxxhash0 #MINVER# - XXH128@Base 0.7.0 - XXH128_canonicalFromHash@Base 0.7.1 + XXH128@Base 0.8.0 + XXH128_canonicalFromHash@Base 0.8.0 ... ``` A rebuild of rsync against a libxxhash0 with the above symbol changes will properly Depend on 0.8.0+. I am just not intimately familiar with the rules for these symbol files, so I'm not 100% sure if the above changes are "legal". Can you shed some light on this? > I'd appreciate a fix at the origin of the problem, > and that would go into a subsequent Ubuntu release Well. If we get the symbols file updated so it says 0.8.0, then subsequent updates from Debian would trickle into Ubuntu. Then any _new_ builds (of for example rsync) against the updated libxxhash library package would get the dependencies fixed. That does leave the problem of libxxhash 0.7.x on Ubuntu/Focal: - it has a broken xxh128sum binary - it exposes access to old/invalid xxh128 functions leading to possible future problems when people start upgrading their libxxhash0 To remedy that, I would suggest a rebuild of xxhash + libxxhash0 on Focal where all xxh128 symbols/functionality is removed/blacklisted. I could do some quilting that simply `#if 0`'s the relevant code. Is this something that would be accepted? ** Bug watch added: github.com/norbusan/debian-xxhash/issues #3 https://github.com/norbusan/debian-xxhash/issues/3 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934992 Title: rsync 3.2.x in Groovy depends on broken libxxhash 0.7.x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xxhash/+bug/1934992/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934992] Re: rsync 3.2.x in Groovy depends on broken libxxhash 0.7.x
How about this case: - I make a hypothetical package that depends on libxxhash < 0.8 because I want the "broken/old" xxh128 support; - I have libxxhash 0.7.3 (that came with Focal); - I have rsync 3.1.x (that came with Focal); - Now I release-upgrade my system from Focal to Groovy; - I get all kinds of new packages, including rsync 3.2.3; - Dependency resolution fixes that I _don't_ get libxxhash 0.8 _because_ I have: - (a) my hypothetical package pinned and it depends on libxxhash<0.8; - (b) rsync that depends on libxxhash>=0.7.1. - The dependencies are all still satisfied and I get to keep libxxhash=0.7.3. In this new situation I have completed the upgrade to Groovy. As long as my hypothetical package that depends on libxxhash <0.8 exists, Ubuntu will not upgrade libxxhash. And then I'm in the same situation as I am now: root@groovy-rsync:~# apt-mark hold hypothetical-pkg hypothetical-pkg set on hold. root@groovy-rsync:~# apt-cache show hypothetical-pkg | grep ^Depe Depends: libxxhash0 (<= 0.8) root@groovy-rsync:~# apt-get install rsync Reading package lists... Done Building dependency tree Reading state information... Done Suggested packages: openssh-server The following NEW packages will be installed: rsync root@groovy-rsync:~# dpkg -l | grep -E 'rsync|libxxhash' hi hypothetical-pkg 1.0 ii libxxhash0:amd64 0.7.3-1 ii rsync3.2.3-2ubuntu1 root@groovy-rsync:~# apt-get dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages have been kept back: libxxhash0 0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded. This may not be the commonest of cases. But this would be an impossible situation if rsync_3.2.3 simply depended on 0.8+ instead of on 0.7.1+. (An impossible situation is good in this case, because you have to choose between either hypothetical-pkg or rsync.) So, I still feel that this is a bug in the rsync control file in Groovy. Not a bug in the rsync source. (Ok, in fact, I think it's ultimately a bug in soname-version/symbol handling of libxxhash. But that's not where the problem manifests itself.) I'll leave it as is if you still feel it should be closed. But at least it has some visibility/presence on the internet so others are helped if they also run into this issue. Cheers :) Walter ** Changed in: rsync (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934992 Title: rsync 3.2.x in Groovy depends on broken libxxhash 0.7.x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1934992/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934992] Re: rsync 3.2.x in Groovy depends on broken libxxhash 0.7.x
Hi Wayne! Thanks for commenting. > It's only the 128-bit hash that depends on 0.8.0. > The 0.7 version works fine with rsync, giving it > the 64-bit and 32-bit hashes. Yes. Except it seems that if you switch the libxxhash0 from 0.8 to 0.7, you get different behaviour. rsync doesn't check what kind of xxh128 is produced, so we end up with a mismatch. Steps to reproduce: wget -q https://launchpad.net/ubuntu/+archive/primary/+files/rsync_3.2.3-2ubuntu1_amd64.deb wget -q https://launchpad.net/ubuntu/+archive/primary/+files/libxxhash0_0.7.3-1_amd64.deb wget -q https://launchpad.net/ubuntu/+archive/primary/+files/libxxhash0_0.8.0-1ubuntu1.20.10.1_amd64.deb focal-node-1: sudo dpkg -i libxxhash0_0.7.3-1_amd64.deb \ rsync_3.2.3-2ubuntu1_amd64.deb touch empty-file.txt echo A > non-empty-file.txt focal-node-2: sudo dpkg -i rsync_3.2.3-2ubuntu1_amd64.deb \ libxxhash0_0.8.0-1ubuntu1.20.10.1_amd64.deb rsync -v --debug=nstr \ focal-node-1:*empty-file.txt \ . Result: Client negotiated checksum: xxh128 empty-file.txt WARNING: empty-file.txt failed verification -- update discarded (will try again). non-empty-file.txt WARNING: non-empty-file.txt failed verification -- update discarded (will try again). empty-file.txt ERROR: empty-file.txt failed verification -- update discarded. non-empty-file.txt ERROR: non-empty-file.txt failed verification -- update discarded. sent 104 bytes received 255 bytes 239.33 bytes/sec total size is 2 speedup is 0.01 rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1816) [generator=3.2.3] focal-node-2: $ ls *empty* ls: cannot access '*empty*': No such file or directory I don't mind if I don't get xxh128 and get some poorer hash. But I _do_ mind if I get a hash that produces different results. If I install libxxhash0 0.7.3 on both: things work. If I install libxxhash0 0.8.x on both: things work. But when there is a mismatch, things break. And uselessly too. I ended up syncing lots of GBs multiple times because our job kept retrying. I hope that clarifies the situation. Walter P.S. Alternative solutions could be: - not exporting xxh128 functions from libxxhash0 0.7.3 (but it might be a bit late for that); - checking that xxh128 produces sane values in rsync before choosing that option. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934992 Title: rsync 3.2.x in Groovy depends on broken libxxhash 0.7.x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1934992/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934992] [NEW] rsync 3.2.x in Groovy depends on broken libxxhash 0.7.x
Public bug reported:
**Problem**
$ rsync root@focal-system:/etc/.pwd.lock .
ERROR: .pwd.lock failed verification -- update discarded.
rsync error: some files/attrs were not transferred (see previous errors)
(code 23) at main.c(1816) [generator=3.2.3]
$ rsync root@focal-system:/etc/.pwd.lock . --debug=all
opening connection using: ssh -l root focal-system rsync --server --sender \
-e.LsfxCIvu . /etc/.pwd.lock (10 args)
(Client) Protocol versions: remote=31, negotiated=31
Client negotiated checksum: xxh128
...
**Cause**
focal-system# dpkg -l | grep -E 'libxxhash|rsync'
ii libxxhash0:amd64 0.7.3-1 amd64
ii rsync 3.2.3-2ubuntu1 amd64
**Why this affects only us and not more people?**
On Ubuntu/Focal, there is no rsync 3.2.3, only 3.1.3-8. But because we
need the lz4 compression support we've fetched a newer rsync (from
Groovy).
However: the rsync 3.2.3 depends on libxxhash0 0.7.1+, while in fact it
needs 0.8+.
**Details**
On a Ubuntu/Focal system we have installed a rsync 3.2.3 package from
Ubuntu/Groovy because we need the lz4 compression support.
focal-system# apt-cache show rsync
Package: rsync
...
Version: 3.2.3-2ubuntu1
Depends: lsb-base, libacl1 (>= 2.2.23), libc6 (>= 2.15),
liblz4-1 (>= 0.0~r130), libpopt0 (>= 1.14), libssl1.1 (>= 1.1.0),
libxxhash0 (>= 0.7.1), libzstd1 (>= 1.3.8), zlib1g (>= 1:1.1.4)
...
Alongside this we had libxxhash0 0.7.3-1 from Focal:
focal-system# apt-cache policy libxxhash0
libxxhash0:
Installed: 0.7.3-1
Candidate: 0.7.3-1
Version table:
*** 0.7.3-1 500
500 http://ARCHIVE/ubuntu focal/universe amd64 Packages
100 /var/lib/dpkg/status
According to the dependencies, this should work. But the combination does not,
as this quote from the rsync maintainer would tell you:
https://github.com/WayneD/rsync/issues/122#issuecomment-737690913
> Yeah, Cyan4973 could have told you that the 128-bit xxhash only
> just stabilized in its 0.8.0 release, so anything older than
> that isn't compatible.
**The fix**
As the maintainer points out, version 0.7 is not stable (= broken for
our intents and purposes) and thus not fit for use with rsync 3.2.
I would argue that it's a good idea to bump the dependency of rsync
3.2.3 on Groovy to libxxhash0>=0.8
After all, in Groovy there is a libxxhash0 0.8.0-1ubuntu1.20.10.1, so
that would not be a problem. And it would fix issues for those mixing
and matching packages.
Thanks!
Walter Doekes
OSSO B.V.
(*) possible patch:
$ diff -pu debian/control{.orig,}
--- debian/control.orig 2021-07-08 09:56:57.646861644 +0200
+++ debian/control 2021-07-08 09:57:38.499029903 +0200
@@ -8,7 +8,7 @@ Build-Depends: debhelper-compat (= 13),
libacl1-dev,
libpopt-dev,
liblz4-dev,
- libxxhash-dev,
+ libxxhash-dev (>= 0.8),
libzstd-dev,
zlib1g-dev,
libssl-dev
** Affects: rsync (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1934992
Title:
rsync 3.2.x in Groovy depends on broken libxxhash 0.7.x
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1934992/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898177] [NEW] (focal update-grub) 10_linux_zfs: causes lots of warnings (invalid version number, bpool does not exist)
Public bug reported:
On our upgrade Focal system (which had ZFS-on-root _before_ this was an
installer option in Ubuntu) we're seeing these non-fatal warnings when
running update-grub:
```
# update-grub
Sourcing file `/etc/default/grub'
Sourcing file `/etc/default/grub.d/init-select.cfg'
Generating grub configuration file ...
cannot open 'bpool/BOOT/ubuntu': dataset does not exist
Found linux image: vmlinuz-5.4.0-48-generic in rpool/ROOT/ubuntu
Found initrd image: initrd.img-5.4.0-48-generic in rpool/ROOT/ubuntu
Found linux image: vmlinuz-4.15.0-118-generic in rpool/ROOT/ubuntu
Found initrd image: initrd.img-4.15.0-118-generic in rpool/ROOT/ubuntu
(start loop)
cannot open 'bpool/BOOT/ubuntu@2019-12-06-zabbix-3.4': dataset does not exist
dpkg: warning: version '12-06-zabbix-3.4/boot/vmlinuz-4.4.0-170-generic' has
bad syntax: invalid character in version number
dpkg: warning: version '12-06-zabbix-3.4/boot/vmlinuz-4.4.0-151-generic' has
bad syntax: invalid character in version number
Found linux image: vmlinuz-4.4.0-170-generic in
rpool/ROOT/ubuntu@2019-12-06-zabbix-3.4
Found initrd image: initrd.img-4.4.0-170-generic in
rpool/ROOT/ubuntu@2019-12-06-zabbix-3.4
Found linux image: vmlinuz-4.4.0-151-generic in
rpool/ROOT/ubuntu@2019-12-06-zabbix-3.4
Found initrd image: initrd.img-4.4.0-151-generic in
rpool/ROOT/ubuntu@2019-12-06-zabbix-3.4
(repeat loop for a number of times)
Adding boot menu entry for UEFI Firmware Settings
done
```
There are two problems here:
- checking of files on 'bpool', even though I only have an 'rpool'
zpool; having that error appear for all snapshots is awkward
- the invalid character in version number (caused by the
version_find_latest not coping with full path names)
First error:
```
$ update-grub 2>&1 | grep 'does not'
cannot open 'bpool/BOOT/ubuntu': dataset does not exist
cannot open 'bpool/BOOT/ubuntu@2019-12-06-zabbix-3.4': dataset does not exist
cannot open 'bpool/BOOT/ubuntu@2019-12-06-zabbix-4.4': dataset does not exist
cannot open 'bpool/BOOT/ubuntu@save-2020-02-14-a': dataset does not exist
cannot open 'bpool/BOOT/ubuntu@2020-09-30-pre-focal': dataset does not exist
cannot open 'bpool/BOOT/ubuntu@planb-20201002T0500Z': dataset does not exist
cannot open 'bpool/BOOT/ubuntu@planb-20201002T0600Z': dataset does not exist
cannot open 'bpool/BOOT/ubuntu@planb-20201002T0700Z': dataset does not exist
cannot open 'bpool/BOOT/ubuntu': dataset does not exist
cannot open 'bpool/BOOT/ubuntu@2019-12-06-zabbix-3.4': dataset does not exist
cannot open 'bpool/BOOT/ubuntu@2019-12-06-zabbix-4.4': dataset does not exist
cannot open 'bpool/BOOT/ubuntu@save-2020-02-14-a': dataset does not exist
cannot open 'bpool/BOOT/ubuntu@2020-09-30-pre-focal': dataset does not exist
cannot open 'bpool/BOOT/ubuntu@planb-20201002T0500Z': dataset does not exist
cannot open 'bpool/BOOT/ubuntu@planb-20201002T0600Z': dataset does not exist
cannot open 'bpool/BOOT/ubuntu@planb-20201002T0700Z': dataset does not exist
```
This is really confusing if you haven't set up a bpool zpool at all.
Simple fix:
```
--- a/grub.d/10_linux_zfs
+++ b/grub.d/10_linux_zfs
@@ -369,6 +369,7 @@ is_secure_boot_enabled() {
get_dataset_info() {
local dataset="$1"
local mntdir="$2"
+local has_bpool="$3"
local base_dataset="${dataset}"
local etc_dir="${mntdir}/etc"
@@ -405,7 +406,10 @@ get_dataset_info() {
mountpoint -q "${mntdir}/etc" && umount "${mntdir}/etc" || true
# read available kernels from /boot
-boot_dir="$(try_default_layout_bpool "${dataset}" "${mntdir}")"
+local boot_dir=
+if [ $has_bpool -eq 1 ]; then
+boot_dir="$(try_default_layout_bpool "${dataset}" "${mntdir}")"
+fi
if [ -z "${boot_dir}" ]; then
boot_dir=$(get_system_directory "${dataset}" "boot" "false"
"${mntdir}" "${etc_dir}")
fi
@@ -534,14 +538,15 @@ get_dataset_info() {
bootlist() {
local mntdir="$1"
local boot_list=""
+local has_bpool=$(zpool list -Honame bpool >/dev/null 2>&1 && echo 1 ||
echo 0)
for dataset in $(get_root_datasets); do
# get information from current root dataset
-boot_list="${boot_list}$(get_dataset_info ${dataset} ${mntdir})\n"
+boot_list="${boot_list}$(get_dataset_info ${dataset} ${mntdir}
${has_bpool})\n"
# get information from snapshots of this root dataset
for snapshot_dataset in $(zfs list -H -o name -t snapshot
"${dataset}"); do
-boot_list="${boot_list}$(get_dataset_info ${snapshot_dataset}
${mntdir})\n"
+boot_list="${boot_list}$(get_dataset_info ${snapshot_dataset}
${mntdir} ${has_bpool})\n"
done
done
echo "${boot_list}"
```
Now it will skip trying the bpool if no such pool exists.
The second error is:
```
# update-grub 2>&1 | grep 'invalid character'
dpkg: warning: version '12-06-zabbix-3.4/boot/vmlinuz-4.4.0-170-generic' has
bad syntax: invalid character in version number
dpkg: warning: version '12-06-zabbix-3.4/boot/vmlinuz-
[Bug 1894855] [NEW] MariaDB 10.3.22-MariaDB-1ubuntu1 on Focal has subquery optimizer bug
Public bug reported: The Focal-shipped MariaDB 10.3.22 is affected by: https://jira.mariadb.org/browse/MDEV-21614 It is fixed in 10.3.23, and it was apparently not broken in 10.3.21. It's a nasty optimizer bug that makes certain expressions like this wrongly return no results: SELECT y FROM y WHERE y.id IN (SELECT y.id FROM y WHERE ...) The release notes say: https://mariadb.com/kb/en/mariadb-10323-release-notes/ "Optimizer, Wrong query results with optimizer_switch="split_materialized=on" (MDEV-21614)" Tracking the problem down to this was rather time consuming. I wish for others to make better use of their time, and I hope a fix gets included into Focal soon. A temporary workaround is to set SET optimizer_switch="split_materialized=off"; Cheers, Walter Doekes OSSO B.V. ** Affects: mariadb-10.3 (Ubuntu) Importance: Undecided Status: New ** Tags: focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1894855 Title: MariaDB 10.3.22-MariaDB-1ubuntu1 on Focal has subquery optimizer bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mariadb-10.3/+bug/1894855/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1808957] Re: Dell XPS 13 (9370) defaults to s2idle sleep/suspend instead of deep, NVMe drains lots of power under s2idle
[~ozdror] / [~andraz313]: > but cant apply the fix mentioned same write error You cannot sudo echo to a file. The opener of the file is still regular- user. Try either: sudo sh -c 'echo deep > /sys/power/mem_sleep' Or: echo deep | sudo tee /sys/power/mem_sleep >/dev/null (P.S. Looks like I'm affected too with XPS13 on Focal. Draining at 0.3W in s2idle. This did not appear to be an issue with Bionic.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1808957 Title: Dell XPS 13 (9370) defaults to s2idle sleep/suspend instead of deep, NVMe drains lots of power under s2idle To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808957/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803309] Re: xmlindent Assertion `strlen(yytext) == 1' failed
Here, a combined patch against the debian/ dir. ** Patch added: "xmlindent-combined-fix-for-1803309.patch" https://bugs.launchpad.net/ubuntu/+source/xmlindent/+bug/1803309/+attachment/5323384/+files/xmlindent-combined-fix-for-1803309.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803309 Title: xmlindent Assertion `strlen(yytext) == 1' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xmlindent/+bug/1803309/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803309] Re: xmlindent Assertion `strlen(yytext) == 1' failed
** Patch added: "yywrap-to-mark-eof.patch (better fix to 857796)" https://bugs.launchpad.net/ubuntu/+source/xmlindent/+bug/1803309/+attachment/5323381/+files/yywrap-to-mark-eof.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803309 Title: xmlindent Assertion `strlen(yytext) == 1' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xmlindent/+bug/1803309/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803309] Re: xmlindent Assertion `strlen(yytext) == 1' failed
Actually, there are two bugs here: - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823315 - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857796 They've both been fixed in Debian version 0.2.17-5. I suggest Ubuntu to adopt the load of them. And ideally a better version of the 857796 fix. - makefile.patch (updated 865758; needs a minor tweak to the rules file as well) - clean-exit-on-error.patch (823315) - yywrap-to-mark-eof.patch (better vesion of 857796, this one copes with embedded NULs) - makefile2.patch (might as well fix the makefile to properly rebuild) Patches incoming. Cheers! Walter Doekes OSSO B.V. ** Bug watch added: Debian Bug tracker #823315 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823315 ** Bug watch added: Debian Bug tracker #857796 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857796 ** Patch added: "makefile.patch (updated from debian 865758)" https://bugs.launchpad.net/ubuntu/+source/xmlindent/+bug/1803309/+attachment/5323379/+files/makefile.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803309 Title: xmlindent Assertion `strlen(yytext) == 1' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xmlindent/+bug/1803309/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803309] Re: xmlindent Assertion `strlen(yytext) == 1' failed
** Patch added: "clean-exit-on-error.patch (823315)" https://bugs.launchpad.net/ubuntu/+source/xmlindent/+bug/1803309/+attachment/5323380/+files/clean-exit-on-error.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803309 Title: xmlindent Assertion `strlen(yytext) == 1' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xmlindent/+bug/1803309/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803309] Re: xmlindent Assertion `strlen(yytext) == 1' failed
** Patch added: "makefile2.patch" https://bugs.launchpad.net/ubuntu/+source/xmlindent/+bug/1803309/+attachment/5323382/+files/makefile2.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803309 Title: xmlindent Assertion `strlen(yytext) == 1' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xmlindent/+bug/1803309/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771559] Re: error while loading icon with pyscss 1.3.5
And for cross-reference, the ticket by ~chrisren on Kronuz/pyScss: https://github.com/Kronuz/pyScss/issues/375 ** Bug watch added: github.com/Kronuz/pyScss/issues #375 https://github.com/Kronuz/pyScss/issues/375 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1771559 Title: error while loading icon with pyscss 1.3.5 To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1771559/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771559] Re: error while loading icon with pyscss 1.3.5
$ pip freeze | grep pyScss
pyScss==1.3.4
$ python -m scss --style compact
xstatic/pkg/mdi/data/scss/materialdesignicons.scss 2>&1 | uniq -c | head -n 10
1650 ERROR: Function not found: function-exists:1
1 @font-face { font-family: 'Material Design Icons'; src:
url('../fonts/materialdesignicons-webfont.eot?v=1.6.50'); src:
url('../fonts/materialdesignicons-webfont.eot?#iefix&v=1.6.50')
format('embedded-opentype'),
url('../fonts/materialdesignicons-webfont.woff2?v=1.6.50') format('woff2'),
url('../fonts/materialdesignicons-webfont.woff?v=1.6.50') format('woff'),
url('../fonts/materialdesignicons-webfont.ttf?v=1.6.50') format('truetype'),
url('../fonts/materialdesignicons-webfont.svg?v=1.6.50#materialdesigniconsregular')
format('svg'); font-weight: normal; font-style: normal; }
1 .mdi { display: inline-block; font: normal normal normal 24px / 1
'Material Design Icons'; font-size: inherit; text-rendering: auto;
-webkit-font-smoothing: antialiased; -moz-osx-font-smoothing: grayscale;
transform: translate(0, 0); }
1 .mdi-access-point:before { content: "\F002"; }
1
1 .mdi-access-point-network:before { content: "\F003"; }
1
1 .mdi-account:before { content: "\F004"; }
1
1 .mdi-account-alert:before { content: "\F005"; }
$ pip freeze | grep pyScss
pyScss==1.3.5
$ python -m scss --style compact
xstatic/pkg/mdi/data/scss/materialdesignicons.scss 2>&1 | uniq -c | head -n 10
1 @font-face { font-family: 'Material Design Icons'; src:
url('../fonts/materialdesignicons-webfont.eot?v=1.6.50'); src:
url('../fonts/materialdesignicons-webfont.eot?#iefix&v=1.6.50')
format('embedded-opentype'),
url('../fonts/materialdesignicons-webfont.woff2?v=1.6.50') format('woff2'),
url('../fonts/materialdesignicons-webfont.woff?v=1.6.50') format('woff'),
url('../fonts/materialdesignicons-webfont.ttf?v=1.6.50') format('truetype'),
url('../fonts/materialdesignicons-webfont.svg?v=1.6.50#materialdesigniconsregular')
format('svg'); font-weight: normal; font-style: normal; }
1
1 .mdi { display: inline-block; font: normal normal normal 24px / 1
'Material Design Icons'; font-size: inherit; text-rendering: auto;
-webkit-font-smoothing: antialiased; -moz-osx-font-smoothing: grayscale;
transform: translate(0, 0); }
1
1 .mdi-access-point:before { content: "xF002"; }
1
1 .mdi-access-point-network:before { content: "xF003"; }
1
1 .mdi-account:before { content: "xF004"; }
1
So yes. \F004 is right, and xF004 is wrong. But those 1650 errors are
wrong too.
It looks strange to me that pyScss takes the path of the existing
function when it doesn't exist. (1.3.4 said 'function-exist' doesn't
exists, and then took that path, see patch below).
This may also have been a fix that would work for 1.3.4 and 1.3.5:
$ diff -pu xstatic/pkg/mdi/data/scss/_functions.scss{.orig,}
--- xstatic/pkg/mdi/data/scss/_functions.scss.orig 2019-10-29
16:27:09.640420707 +0100
+++ xstatic/pkg/mdi/data/scss/_functions.scss 2019-10-29 16:27:24.256440797
+0100
@@ -1,14 +1,5 @@
@function char($character-code) {
-@if function-exists("selector-append") {
-@return unquote("\"\\#{$character-code}\"");
-}
-
-@if "\\#{'x'}" == "\\x" {
-@return str-slice("\x", 1, 1) + $character-code;
-}
-@else {
-@return #{"\"\\"}#{$character-code + "\""};
-}
+@return unquote("\"\\#{$character-code}\"");
}
@function mdi($name) {
I cannot speak for the validity of the scss/sass syntax and whether or not the
undefined function should've been run. Not my cup of tea.
Walter Doekes
OSSO B.V.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1771559
Title:
error while loading icon with pyscss 1.3.5
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1771559/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849178] Re: upgrading linux-image package to 4.15.0-66.75 breaks Ceph network file system clients
Related to https://lkml.org/lkml/2019/10/3/862 ? (That rervert is _not_ in ubuntu linux 4.15.0-66.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849178 Title: upgrading linux-image package to 4.15.0-66.75 breaks Ceph network file system clients To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849178/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818987] Re: broken symlink to changelog.Debian.gz in chromium-browser
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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818987 Title: broken symlink to changelog.Debian.gz in chromium-browser To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1818987/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 194574] Re: can cause broken symlinks in /usr/share/doc
(Not sure whose responsibility this is. I did not find the problematic packaging code directly. Also filed as #1818987 under chromium-browser.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/194574 Title: can cause broken symlinks in /usr/share/doc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cdbs/+bug/194574/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818987] [NEW] broken symlink to changelog.Debian.gz in chromium-browser
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818987
Title:
broken symlink to changelog.Debian.gz in chromium-browser
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1818987/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 194574] Re: can cause broken symlinks in /usr/share/doc
Right now I have the former installed, also boom.
```
$ 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
amd64Chromium web browser, open-source version of Chrome
ii chromium-codecs-ffmpeg 72.0.3626.119-0ubuntu0.18.04.1
amd64Free 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 root2512 okt 25 2017 copyright.problems.gz
-rw-r--r-- 1 root root2975 okt 25 2017 README.source
$ ls -l /usr/share/doc/chromium-codecs-ffmpeg/
total 1104
-rw-r--r-- 1 root root2263 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
```
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/194574
Title:
can cause broken symlinks in /usr/share/doc
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cdbs/+bug/194574/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1724557] Re: gnome-shell crashed with SIGSEGV in meta_logical_monitor_get_scale()
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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1724557 Title: gnome-shell crashed with SIGSEGV in meta_logical_monitor_get_scale() To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1724557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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()
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 Ubuntu Bugs, which is subscribed to 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() To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1724439/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1748323] Re: /usr/lib/chromium-browser/chromium-browser:5:AsLocatedEvent:DispatchMouseEvent:DispatchEvent:non:DispatchEvent
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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1748323 Title: /usr/lib/chromium-browser/chromium- browser:5:AsLocatedEvent:DispatchMouseEvent:DispatchEvent:non:DispatchEvent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1748323/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1748323] Re: /usr/lib/chromium-browser/chromium-browser:5:AsLocatedEvent:DispatchMouseEvent:DispatchEvent:non:DispatchEvent
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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1748323 Title: /usr/lib/chromium-browser/chromium- browser:5:AsLocatedEvent:DispatchMouseEvent:DispatchEvent:non:DispatchEvent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1748323/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1724557] Re: gnome-shell crashed with SIGSEGV in meta_logical_monitor_get_scale()
@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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1724557 Title: gnome-shell crashed with SIGSEGV in meta_logical_monitor_get_scale() To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1724557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726352] Re: gnome-shell crashed with SIGSEGV in meta_window_move_resize_request()
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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726352 Title: gnome-shell crashed with SIGSEGV in meta_window_move_resize_request() To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1726352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726352] Re: gnome-shell crashed with SIGSEGV in meta_window_move_resize_request()
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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726352 Title: gnome-shell crashed with SIGSEGV in meta_window_move_resize_request() To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1726352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1724557] Re: gnome-shell crashed with SIGSEGV in meta_logical_monitor_get_scale()
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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1724557 Title: gnome-shell crashed with SIGSEGV in meta_logical_monitor_get_scale() To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1724557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1729028] Re: gnome-shell crashes when monitor sleeps or is turned off
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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1729028 Title: gnome-shell crashes when monitor sleeps or is turned off To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1729028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1715146] Re: Not Suspending When Lid is Closed Causing Heat Issue
BIOS Setup: Settings -> System Configuration -> Thunderbolt(tm) Adapter Configuration: [x] Enable Thunderbolt(tm) Technology Support [ ] Enable Thunderbolt(tm) Adapter Boot Support [ ] Enable Thunderbolt(tm) Adapter Pre-boot Modules (x) Security level - User Authorization I have/had no devices attached to the Thunderbolt/USB-C socket. But like I said, I ran the command quickly after reboot. Perhaps it enumerated right after boot but went away after a while of disuse? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1715146 Title: Not Suspending When Lid is Closed Causing Heat Issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715146/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1715146] Re: Not Suspending When Lid is Closed Causing Heat Issue
Ok, rebooted and verified that Thunderbolt was enabled. Both pm-suspend and lid-closing now works as intended. Dec 25 23:35:41 walter-tretton kernel: [ 53.790125] Suspended for 135.895 seconds LGTM :okay_hand: -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1715146 Title: Not Suspending When Lid is Closed Causing Heat Issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715146/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1715146] Re: Not Suspending When Lid is Closed Causing Heat Issue
Ah.. $ gcc -I /usr/include/efivar 1.c -lsmbios_c In file included from /usr/include/smbios_c/config/get_config.h:36:0, from /usr/include/smbios_c/compat.h:27, from /usr/include/smbios_c/smi.h:22, from 1.c:22: /usr/include/smbios_c/config/compiler/gcc.h:31:7: warning: #warning "Unknown compiler version - please run the configure tests and report the results" [-Wcpp] # warning "Unknown compiler version - please run the configure tests and report the results" ^~~ $ ./a.out This application forces TBT controller to flashing mode on Dell systems Call with an argument of '1' to force flashing mode Call with an argument of '0' to return to normal mode $ ./a.out 1 failed to build buffer Failed to force device to 1 (ret -1) $ sudo ./a.out 1 Turned device to 1 $ fwupdmgr install eac3961ba9bd466f6e34d9276c27d524395d7c3c-NN1TN_NVM21.00.cab Decompressing… [- ] Restarting device… [] Okay. Let me try again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1715146 Title: Not Suspending When Lid is Closed Causing Heat Issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715146/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1715146] Re: Not Suspending When Lid is Closed Causing Heat Issue
No, because it won't install. I tried "fwupdmgr install eac3961ba9bd466f6e34d9276c27d524395d7c3c- NN1TN_NVM21.00.cab", but I got: could not find thunderbolt device at /sys/devices/pci:00/:00:1c.0/:01:00.0/:02:00.0/:03:00.0/domain0/0-0 So I rebooted with Thunderbolt enabled. That gave me: Decompressing… [- ] could not validate firmware: Error reading from file: Input/output error. See https://github.com/hughsie/fwupd/wiki/Thunderbolt:-Validation-failed-or-unknown-device for more information. But a second call gave me the same error as before the reboot (i.e. as before re-enabling Thunderbolt). Enabling test fwupd remote through lvfs-testing.conf gave me the same results after refresh+update, so I guess I typed the right commands. Just after reboot, probably around the time of the first fwupdmgr call, I got this in the dmesg. Could be related: [ma dec 25 23:04:04 2017] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ma dec 25 23:04:04 2017] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) [ma dec 25 23:04:04 2017] pcieport :00:1c.0: device [8086:9d10] error status/mask=0001/2000 [ma dec 25 23:04:04 2017] pcieport :00:1c.0:[ 0] Receiver Error (First) [ma dec 25 23:04:04 2017] xhci_hcd :39:00.0: remove, state 1 [ma dec 25 23:04:04 2017] usb usb4: USB disconnect, device number 1 [ma dec 25 23:04:04 2017] xhci_hcd :39:00.0: USB bus 4 deregistered [ma dec 25 23:04:04 2017] xhci_hcd :39:00.0: xHCI host controller not responding, assume dead [ma dec 25 23:04:04 2017] xhci_hcd :39:00.0: remove, state 1 [ma dec 25 23:04:04 2017] usb usb3: USB disconnect, device number 1 [ma dec 25 23:04:04 2017] xhci_hcd :39:00.0: Host halt failed, -19 [ma dec 25 23:04:04 2017] xhci_hcd :39:00.0: Host not accessible, reset failed. [ma dec 25 23:04:04 2017] xhci_hcd :39:00.0: USB bus 3 deregistered [ma dec 25 23:04:04 2017] thunderbolt :03:00.0: stopping RX ring 0 [ma dec 25 23:04:04 2017] thunderbolt :03:00.0: disabling interrupt at register 0x38200 bit 12 (0x -> 0xefff) [ma dec 25 23:04:04 2017] thunderbolt :03:00.0: stopping TX ring 0 [ma dec 25 23:04:04 2017] thunderbolt :03:00.0: disabling interrupt at register 0x38200 bit 0 (0x -> 0xfffe) [ma dec 25 23:04:04 2017] thunderbolt :03:00.0: control channel stopped [ma dec 25 23:04:04 2017] thunderbolt :03:00.0: freeing RX ring 0 [ma dec 25 23:04:04 2017] thunderbolt :03:00.0: freeing TX ring 0 [ma dec 25 23:04:04 2017] thunderbolt :03:00.0: shutdown [ma dec 25 23:04:04 2017] pci_bus :03: busn_res: [bus 03] is released [ma dec 25 23:04:04 2017] pci_bus :04: busn_res: [bus 04-38] is released [ma dec 25 23:04:04 2017] pci_bus :39: busn_res: [bus 39] is released [ma dec 25 23:04:04 2017] pci_bus :02: busn_res: [bus 02-39] is released Although the dmesg starts about 30s earlier with a bunch of other messages (mainly pci and some thunderbolt, usb and acpi). Possibly the first call took that long. ... [ma dec 25 23:03:37 2017] thunderbolt :03:00.0: NHI initialized, starting thunderbolt ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1715146 Title: Not Suspending When Lid is Closed Causing Heat Issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715146/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1715146] Re: Not Suspending When Lid is Closed Causing Heat Issue
(And indeed, no suspend, it was waking/sleeping during the entire 1.5h it was "suspended" just now. $ dmesg | grep 'PM.*Preparing system for sleep' | wc -l 115) Hi Mario, do you mean this? $ fwupdmgr get-devices Intel AMT (unprovisioned) DeviceID: /dev/mei Guid: 2800f812-b7b4-2d4b-aca8-46e0ff65814c Plugin: amt Flags:internal|registered Version: 11.8.50 VersionBootloader:11.8.50 Created: 2017-12-25 Unifying Receiver DeviceID: /sys/devices/pci:00/:00:14.0/usb1/1-1 Guid: 77d843f7-682c-57e8-8e29-584f5b4f52a1 Guid: cc4cbfa9-bf9d-540b-b92b-172ce31013c1 Plugin: unifying Flags:updatable|supported|registered DeviceVendor: Logitech DeviceVendorId: USB:0x046D Version: RQR24.05_B0029 VersionBootloader:BOT03.00_B0006 Created: 2017-12-25 XPS13 9360 Thunderbolt Controller DeviceID: d203-0091-7508-22f9-f2e58a90981c Guid: dfd51125-338f-56ff-b721-fa3bea8e534e Plugin: thunderbolt Flags:internal|updatable|registered DeviceVendor: Dell DeviceVendorId: TBT:0x00D4 Version: 18.5 Created: 2017-12-25 XPS 13 9360 System Firmware DeviceID: UEFI-5ffdbc0d-f340-441c-a803-8439c8c0ae10-dev0 Guid: 5ffdbc0d-f340-441c-a803-8439c8c0ae10 Plugin: uefi Flags: internal|updatable|require-ac|supported|registered|needs-reboot Version: 0.2.4.2 VersionLowest:0.2.4.2 Created: 2017-12-25 Integrated Webcam HD DeviceID: usb:00:05 Guid: 87c78d19-a3ed-5778-9b69-8eb701529940 Guid: ea5dc553-c861-59a3-885c-caf80c2dea78 Plugin: usb Flags:registered DeviceVendorId: USB:0x0BDA Version: 99.24 Created: 2017-12-25 USB Receiver DeviceID: usb:00:01 Guid: 77d843f7-682c-57e8-8e29-584f5b4f52a1 Guid: a00c69e9-62ec-56f5-bab4-177f3424793c Plugin: usb Flags:registered DeviceVendorId: USB:0x046D Version: 36.5 Created: 2017-12-25 Unknown Device DeviceID: ro__sys_devices_pci_00__00_02_0 Guid: a2721130-d6d5-51aa-a710-0323525ca469 Plugin: udev Flags:internal|registered DeviceVendor: Intel Corporation DeviceVendorId: PCI:0x8086 Created: 2017-12-25 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1715146 Title: Not Suspending When Lid is Closed Causing Heat Issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715146/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1715146] Re: Not Suspending When Lid is Closed Causing Heat Issue
Additional info: - if I use pm-suspend, it just refuses to suspend (after 20secs wait) [ma dec 25 18:33:49 2017] PM: Preparing system for sleep (mem) ... [ma dec 25 18:33:49 2017] thunderbolt :03:00.0: Ignoring mailbox command error (-110) in icm_suspend [ma dec 25 18:33:49 2017] PM: Some devices failed to suspend, or early wake event detected [ma dec 25 18:33:49 2017] i2c i2c-7: Unbalanced pm_runtime_enable! ... [ma dec 25 18:34:10 2017] PM: Finishing wakeup. [ma dec 25 18:34:10 2017] OOM killer enabled. [ma dec 25 18:34:10 2017] Restarting tasks ... done. - if I close the lid, it does some kind of suspend with a black screen and it sometimes requires some efforts to get logged in again (ctrl-alt-del to get a login prompt again) [ma dec 25 18:36:36 2017] PM: Preparing system for sleep (mem) ... [ma dec 25 18:36:37 2017] PM: Some devices failed to suspend, or early wake event detected ... [ma dec 25 18:36:57 2017] PM: Preparing system for sleep (freeze) ... [ma dec 25 18:36:58 2017] PM: Some devices failed to suspend, or early wake event detected ... [ma dec 25 18:37:19 2017] PM: Preparing system for sleep (mem) ... [ma dec 25 18:37:20 2017] PM: Some devices failed to suspend, or early wake event detected ... [ma dec 25 18:37:41 2017] PM: Preparing system for sleep (freeze) ... [ma dec 25 18:37:42 2017] PM: Some devices failed to suspend, or early wake event detected ... During that time, logind says: Dec 25 18:36:35 walter-tretton systemd-logind[891]: Lid closed. Dec 25 18:36:35 walter-tretton systemd-logind[891]: Suspending... Dec 25 18:36:35 walter-tretton dbus[881]: [system] Rejected send message, 2 matched rules; type="error", sender=":1.5" (uid=0 pid=891 comm="/lib/systemd/systemd-logind ") interface="(unset)" member="(unset)" error name="org.freedesktop.DBus.Error.UnknownMethod" requested_reply="0" destination=":1.72" (uid=1000 pid=1466 comm="/usr/bin/gnome-shell ") Dec 25 18:37:19 walter-tretton systemd-logind[891]: Operation 'sleep' finished. Dec 25 18:37:19 walter-tretton systemd-logind[891]: Suspending... Dec 25 18:38:03 walter-tretton systemd-logind[891]: Lid opened. I'm not really satisfied that between 18:37:19 and 18:38:03 it was actually suspended. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1715146 Title: Not Suspending When Lid is Closed Causing Heat Issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715146/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1715146] Re: Not Suspending When Lid is Closed Causing Heat Issue
Hi there, I upgraded to Ubuntu Artful the other day, and today I updated the Dell BIOS (using the GUI tools). Out of curiosity, I went back to check this: re-*enabling* Thunderbolt in the BIOS *still* *breaks* *suspend*. Again "Some devices failed to suspend, or early wake event detected". dmidecode: > BIOS Information > Vendor: Dell Inc. > Version: 2.4.2 > Release Date: 11/21/2017 > ... > System Information > Manufacturer: Dell Inc. > Product Name: XPS 13 9360 uname -a: > Linux walter-tretton 4.13.0-21-generic #24-Ubuntu SMP > Mon Dec 18 17:29:16 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux Cheers, Walter -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1715146 Title: Not Suspending When Lid is Closed Causing Heat Issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715146/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1734791] Re: gnome-keyring doesn't start gnome-keyring-ssh services
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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1734791 Title: gnome-keyring doesn't start gnome-keyring-ssh services To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1734791/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1715146] Re: Not Suspending When Lid is Closed Causing Heat Issue
Disabling Thunderbolt support in the BIOS (F2 during boot) worked for me. Suspend works. Don't know when/if I'll need the Thunderbolt. This works for now. Thanks! Can I provide any additional info to help you debug/fix this properly? Cheers, Walter Before disabling Thunderbolt: [ 4694.667622] wlp58s0: deauthenticating from xx:xx:xx:xx:xx:xx by local choice (Reason: 3=DEAUTH_LEAVING) [ 4694.679878] IPv6: ADDRCONF(NETDEV_UP): wlp58s0: link is not ready [ 4696.418854] PM: Syncing filesystems ... done. [ 4696.426577] PM: Preparing system for sleep (mem) [ 4696.426825] Freezing user space processes ... (elapsed 0.001 seconds) done. [ 4696.428577] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 4696.429797] PM: Suspending system (mem) [ 4696.429831] Suspending console(s) (use no_console_suspend to debug) [ 4696.645611] xhci_hcd :39:00.0: WARN: xHC CMD_RUN timeout [ 4696.645628] suspend_common(): xhci_pci_suspend+0x0/0xd0 returns -110 [ 4696.645632] pci_pm_suspend(): hcd_pci_suspend+0x0/0x30 returns -110 [ 4696.645636] dpm_run_callback(): pci_pm_suspend+0x0/0x150 returns -110 [ 4696.645642] PM: Device :39:00.0 failed to suspend async: error -110 [ 4696.645836] PM: Some devices failed to suspend, or early wake event detected [ 4696.653802] PM: resume of devices complete after 7.960 msecs [ 4696.654412] PM: Finishing wakeup. [ 4696.654413] Restarting tasks ... done. [ 4696.713358] PM: Syncing filesystems ... done. [ 4696.724043] PM: Preparing system for sleep (freeze) [ 4696.724263] Freezing user space processes ... (elapsed 0.001 seconds) done. [ 4696.726226] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 4696.727480] PM: Suspending system (freeze) [ 4696.727481] Suspending console(s) (use no_console_suspend to debug) [ 4696.727681] xhci_hcd :39:00.0: WARN: xHC CMD_RUN timeout [ 4696.727685] suspend_common(): xhci_pci_suspend+0x0/0xd0 returns -110 [ 4696.727687] pci_pm_suspend(): hcd_pci_suspend+0x0/0x30 returns -110 [ 4696.727688] dpm_run_callback(): pci_pm_suspend+0x0/0x150 returns -110 [ 4696.727690] PM: Device :39:00.0 failed to suspend async: error -110 [ 4696.727901] PM: Some devices failed to suspend, or early wake event detected [ 4696.735295] PM: resume of devices complete after 7.392 msecs [ 4696.735495] PM: Finishing wakeup. After disabling Thunderbolt: [ 467.806774] wlp58s0: deauthenticating from xx:xx:xx:xx:xx:xx by local choice (Reason: 3=DEAUTH_LEAVING) [ 467.819709] IPv6: ADDRCONF(NETDEV_UP): wlp58s0: link is not ready [ 469.526719] PM: Syncing filesystems ... done. [ 469.536851] PM: Preparing system for sleep (mem) [ 469.537149] Freezing user space processes ... (elapsed 0.001 seconds) done. [ 469.538896] Freezing remaining freezable tasks ... (elapsed 0.000 seconds) done. [ 469.539665] PM: Suspending system (mem) [ 469.539701] Suspending console(s) (use no_console_suspend to debug) [ 469.759779] ACPI : EC: event blocked [ 470.973736] PM: suspend of devices complete after 1217.757 msecs [ 470.995596] PM: late suspend of devices complete after 21.855 msecs [ 470.996271] ACPI : EC: interrupt blocked [ 470.999072] xhci_hcd :00:14.0: System wakeup enabled by ACPI [ 471.035732] PM: noirq suspend of devices complete after 40.130 msecs [ 471.036567] ACPI: Preparing to enter system sleep state S3 [ 471.043286] ACPI : EC: EC stopped [ 471.043288] PM: Saving platform NVS memory [ 471.043385] Disabling non-boot CPUs ... [ 471.046076] smpboot: CPU 1 is now offline [ 471.073211] Broke affinity for irq 123 [ 471.073217] Broke affinity for irq 124 [ 471.073229] Broke affinity for irq 126 [ 471.073284] Broke affinity for irq 286 [ 471.074352] smpboot: CPU 2 is now offline [ 471.096769] Broke affinity for irq 1 [ 471.096776] Broke affinity for irq 8 [ 471.096781] Broke affinity for irq 9 [ 471.096785] Broke affinity for irq 12 [ 471.096789] Broke affinity for irq 14 [ 471.096793] Broke affinity for irq 16 [ 471.096798] Broke affinity for irq 17 [ 471.096806] Broke affinity for irq 51 [ 471.096815] Broke affinity for irq 122 [ 471.096820] Broke affinity for irq 123 [ 471.096823] Broke affinity for irq 124 [ 471.096827] Broke affinity for irq 125 [ 471.096832] Broke affinity for irq 126 [ 471.096871] Broke affinity for irq 281 [ 471.096875] Broke affinity for irq 286 [ 471.097940] smpboot: CPU 3 is now offline [ 471.111695] ACPI: Low-level resume complete [ 471.111808] ACPI : EC: EC started [ 471.111809] PM: Restoring platform NVS memory [ 471.112606] Suspended for 16.485 seconds [ 471.113987] Enabling non-boot CPUs ... [ 471.123998] x86: Booting SMP configuration: [ 471.123998] smpboot: Booting Node 0 Processor 1 APIC 0x2 [ 471.124625] cache: parent cpu1 should not be sleeping [ 471.124746] microcode: sig=0x806e9, pf=0x40, revision=0x4e [ 471.125660] CPU1 is up [ 471.136138] smpboot: Booting Node 0 Processor 2 APIC 0x1 [ 471.137181] cache: parent cpu2 should not be sleeping [ 471.
[Bug 1710789] Re: chromium does not open downloaded files
Yeap, that fixes things. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1710789 Title: chromium does not open downloaded files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1710789/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1664481] Re: incorrect postinstall script
I see it has been fixed in later versions (e.g. on Zesty): uwsgi-2.0.14+20170111/debian$ grep BINARY_IS_UWSGI_ALTERNATIVE= -A3 uwsgi-plugin-__PLUGIN__.postinst.in* uwsgi-plugin-__PLUGIN__.postinst.in.pri: BINARY_IS_UWSGI_ALTERNATIVE="$(\ uwsgi-plugin-__PLUGIN__.postinst.in.pri-update-alternatives --list uwsgi 2>/dev/null \ uwsgi-plugin-__PLUGIN__.postinst.in.pri-| grep -c '/uwsgi_@@plugin_alternatives_stem@@$' || true \ uwsgi-plugin-__PLUGIN__.postinst.in.pri- )" -- uwsgi-plugin-__PLUGIN__.postinst.in.pri-py: BINARY_IS_UWSGI_ALTERNATIVE="$(\ uwsgi-plugin-__PLUGIN__.postinst.in.pri-py-update-alternatives --list uwsgi 2>/dev/null \ uwsgi-plugin-__PLUGIN__.postinst.in.pri-py-| grep -c '/uwsgi_@@plugin_alternatives_stem@@$' || true \ uwsgi-plugin-__PLUGIN__.postinst.in.pri-py- )" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1664481 Title: incorrect postinstall script To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/uwsgi/+bug/1664481/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1664481] Re: incorrect postinstall script
That should be `; true` or ` || true`, but not ` | true`. Reproduced on Xenial machine where I first installed uwsgi and then uwsgi-plugin-python3 2.0.12-5ubuntu3. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1664481 Title: incorrect postinstall script To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/uwsgi/+bug/1664481/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1691741] Re: Execute NX-protected page - 4.4.0-78-generic - kernel panic
Uptime is now 13 days. I think we can close this one as "fixed by 4.4.0-79-generic". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1691741 Title: Execute NX-protected page - 4.4.0-78-generic - kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1691741/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1691741] Re: Execute NX-protected page - 4.4.0-78-generic - kernel panic
Update: running 4.4.0-79-generic on the original machine with issues for 24hrs (normal workload) without kernel panics thusfar. *Crosses fingers* -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1691741 Title: Execute NX-protected page - 4.4.0-78-generic - kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1691741/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1691741] Re: Execute NX-protected page - 4.4.0-78-generic - kernel panic
The docker1-tcn machine with vanilla kernel 4.4.70 is still up. And on another (abmfn-staging) machine with 4.4.0-78 I've seen the crash. According to dmesg output in the console, btrfs and other fs modules were loaded. Probably due to an update-grub call. After restart, I ensured that those modules were not loaded. No crashes have happened there since. In all cases, the machines were running on a proxmox cluster, with "Linux 4.4.24-1-pve" (pve-kernel-4.4.24-1-pve 4.4.24-72) on the host OS. With KVM version pve-qemu-kvm 2.7.0-8. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1691741 Title: Execute NX-protected page - 4.4.0-78-generic - kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1691741/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1691741] Re: Execute NX-protected page - 4.4.0-78-generic - kernel panic
Okay. So we've been running 4.4.70 now for 22 hours and counting on docker1-tcn. /var/crash# uptime 09:45:30 up 22:25, 1 user, load average: 0,01, 0,02, 0,00 /var/crash# uname -a Linux ossoio-docker1-tcn 4.4.70-040470-generic #201705251131 SMP Thu May 25 15:34:16 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux /var/crash# ls -l total 36 drwxr-xr-x 2 root root 4096 mei 29 18:19 201705291818 drwxr-xr-x 2 root root 4096 mei 29 18:37 201705291836 drwxr-xr-x 2 root root 4096 mei 29 23:53 201705292352 drwxr-xr-x 2 root root 4096 mei 30 08:00 201705300759 drwxr-xr-x 2 root root 4096 mei 30 09:49 201705300948 drwxr-xr-x 2 root root 4096 mei 30 10:58 201705301057 -rw-r--r-- 1 root root0 mei 30 11:31 201705301119-START-vanilla-kernel-with-overlay2-instead-of-aufs -rw-r--r-- 1 root root0 mei 31 09:16 201705310915-22hrs-uptime-still-no-crash Previously we had crashes at least every 8 hours. This looks promising. But, for this machine to work, I had to switch the dockerd storage from aufs from overlay2, because the vanilla kernel doesn't include aufs. This change isn't a problem, but it makes this result less reliable: is the problem with the Ubuntu-specific modules? Or with something that has been fixed between kernel 4.4.61 and 4.4.70? My best guess is still something with a (filesystem module?) change that went into 4.4.0-78 that did not get (fully) applied to the Ubuntu-specific modules. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1691741 Title: Execute NX-protected page - 4.4.0-78-generic - kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1691741/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1691741] Re: Execute NX-protected page - 4.4.0-78-generic - kernel panic
Okay. On a different machine with different load, we've now got the same problem: KERNEL: /usr/lib/debug/boot/vmlinux-4.4.0-78-generic DUMPFILE: dump.201705300948 [PARTIAL DUMP] CPUS: 4 DATE: Tue May 30 09:48:05 2017 UPTIME: 01:47:38 LOAD AVERAGE: 0.05, 0.06, 0.04 TASKS: 292 NODENAME: ossoio-docker1-tcn RELEASE: 4.4.0-78-generic VERSION: #99-Ubuntu SMP Thu Apr 27 15:29:09 UTC 2017 MACHINE: x86_64 (2199 Mhz) MEMORY: 4 GB PANIC: "BUG: unable to handle kernel paging request at 88013a404000" PID: 0 COMMAND: "swapper/3" TASK: 88013abf1980 (1 of 4) [THREAD_INFO: 88013a40] CPU: 3 STATE: TASK_RUNNING (PANIC) #9 [88013a403e20] async_page_fault at 81842be8 #10 [88013a403e38] tick_nohz_idle_exit at 810ff75e #11 [88013a403ed8] cpu_startup_entry at 810c4736 #12 [88013a403f30] start_secondary at 810517c4 Differences: - this machine does not use zfs, the other one does - this machine runs docker instances, the other one mainly mysqld - this machines has x2apic enabled according to dmesg (no idea what that is) Similarities: - both are KVM guests (same KVM cluster, different nodes) - the two KVM nodes have the same hardware, same kernel and same KVM host software - 4 cpus, 2200MHz, flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx lm constant_tsc nopl xtopology pni cx16 x2apic hypervisor lahf_lm - 512MB swap Modules loaded: - both: 8250_fintek autofs4 drm drm_kms_helper fb_sys_fops floppy i2c_piix4 input_leds mac_hid parport parport_pc pata_acpi ppdev psmouse serio_raw shpchp syscopyarea sysfillrect sysimgblt ttm - this: aufs bridge br_netfilter ip6table_filter ip6_tables iptable_filter iptable_nat ip_tables ipt_MASQUERADE llc nf_conntrack nf_conntrack_ipv4 nf_conntrack_netlink nf_defrag_ipv4 nf_nat nf_nat_ipv4 nf_nat_masquerade_ipv4 nfnetlink stp veth xfrm_algo xfrm_user x_tables xt_addrtype xt_conntrack xt_nat xt_tcpudp - other: spl(O) zavl(PO) zcommon(PO) zfs(PO) znvpair(PO) zunicode(PO) We should be able to run this node on the vanilla kernel and see how that goes. Will report back in a bit. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1691741 Title: Execute NX-protected page - 4.4.0-78-generic - kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1691741/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1691741] Re: Execute NX-protected page - 4.4.0-78-generic - kernel panic
So, I tried to revert the backing_dev_info changes and dpkg-built an updated kernel. But that didn't work out. Either because it isn't the cause, or because I reverted too much or too little. After several hours of normal-load uptime, a removal of the mysql data dir quickly caused a panic. I did not get a dmesg+dump unfortunately, but I'd guess the same problem still existed. Attaching for reference: revert-backing_dev_info-changes-of-77-78-DID-NOT-WORK.patch ^-- did not help ** Patch added: "revert-backing_dev_info-changes-of-77-78-DID-NOT-WORK.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1691741/+attachment/4882561/+files/revert-backing_dev_info-changes-of-77-78-DID-NOT-WORK.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1691741 Title: Execute NX-protected page - 4.4.0-78-generic - kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1691741/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1691741] Re: Execute NX-protected page - 4.4.0-78-generic - kernel panic
I could be on a wild goose chase here.
But one of the prominent changes between 77 and 78 is the
backing_dev_info element of the queue turning into a pointer.
Part of the "bdi" changes in this bit:
++ * UbuntuKVM guest crashed while running I/O stress test with Ubuntu kernel
++4.4.0-47-generic (LP: #1659111)
I believe from here: https://patchwork.kernel.org/patch/9547199/
For example this:
--- a/drivers/block/drbd/drbd_main.c
+++ b/drivers/block/drbd/drbd_main.c
@@ -2462,7 +2462,7 @@ static int drbd_congested(void *congested_data, int
bdi_bits)
if (get_ldev(device)) {
q = bdev_get_queue(device->ldev->backing_bdev);
- r = bdi_congested(&q->backing_dev_info, bdi_bits);
+ r = bdi_congested(q->backing_dev_info, bdi_bits);
put_ldev(device);
if (r)
reason = 'b';
But if I check the Ubuntu-specific code, that change does not seem to be
done everywhere:
$ zcat linux_4.4.0-78.99.diff.gz | grep bdi_congested.*backing_dev -B2 |
tail -n8
struct request_queue *q = bdev_get_queue(rdev->bdev);
- ret |= bdi_congested(&q->backing_dev_info, bits);
+ ret |= bdi_congested(q->backing_dev_info, bits);
--
+ struct request_queue *q = bdev_get_queue(rs->dev[p].dev->bdev);
+
+ r |= bdi_congested(&q->backing_dev_info, bdi_bits);
Extracting only the "new" files, I find it here indeed:
$ mkdir foo; cd foo
$ patch -tp1 < ../linux_4.4.0-78.99.diff.gz
$ find . -name '*.c' | xargs grep -B2 bdi_congested.*backing_dev_info
./ubuntu/dm-raid4-5/dm-raid4-5.c- struct request_queue *q =
bdev_get_queue(rs->dev[p].dev->bdev);
./ubuntu/dm-raid4-5/dm-raid4-5.c-
./ubuntu/dm-raid4-5/dm-raid4-5.c: r |=
bdi_congested(&q->backing_dev_info, bdi_bits);
This is just an example of course, I believe there could be more "bdi" changes
like that one that haven't been made.
Correct me if I'm wrong though. I've never done any kernel dev, so I
could be way off base here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1691741
Title:
Execute NX-protected page - 4.4.0-78-generic - kernel panic
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1691741/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1691741] Re: Execute NX-protected page - 4.4.0-78-generic - kernel panic
Crash info appears the same: KERNEL: /usr/lib/debug/boot/vmlinux-4.4.0-78-generic DUMPFILE: dump.201705191443 [PARTIAL DUMP] CPUS: 4 DATE: Fri May 19 14:43:31 2017 UPTIME: 00:43:02 LOAD AVERAGE: 2.53, 1.81, 2.56 TASKS: 544 NODENAME: RELEASE: 4.4.0-78-generic VERSION: #99-Ubuntu SMP Thu Apr 27 15:29:09 UTC 2017 MACHINE: x86_64 (2199 Mhz) MEMORY: 16 GB PANIC: "BUG: unable to handle kernel paging request at 88042d684000" PID: 0 COMMAND: "swapper/1" TASK: 88042d678000 (1 of 4) [THREAD_INFO: 88042d68] CPU: 1 STATE: TASK_RUNNING (PANIC) bt: #9 [88042d683e20] async_page_fault at 81842be8 #10 [88042d683e38] tick_nohz_idle_exit at 810ff75e #11 [88042d683ed8] cpu_startup_entry at 810c4736 #12 [88042d683f30] start_secondary at 810517c4 bt -f: #9 [88042d683e20] async_page_fault at 81842be8 88042d683e28: 88042d68 88042d683e38: 810ff75e #10 [88042d683e38] tick_nohz_idle_exit at 810ff75e 88042d683e40: 88042d683ed0 81f38d40 88042d683e50: 0259403d7830 2800 88042d683e60: 00010008b4dc 88042d683e70: 0014 0001 88042d683e80: 0001 88042d683e90: 0083 0083 88042d683ea0: 88042d684000 88042d683eb0: 0010 00010082 88042d683ec0: 88042d683ed0 0018 88042d683ed0: 88042d683f28 810c4736 #11 [88042d683ed8] cpu_startup_entry at 810c4736 88042d683ee0: 88042d68 88042d684000 88042d683ef0: 7072184c56e60054 ada92d752b7bcf68 88042d683f00: 88042d683f10: 88042d683f20: 88042d683f48 88042d683f30: 810517c4 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1691741 Title: Execute NX-protected page - 4.4.0-78-generic - kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1691741/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1691741] Re: Execute NX-protected page - 4.4.0-78-generic - kernel panic
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1691741 Title: Execute NX-protected page - 4.4.0-78-generic - kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1691741/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1691741] Re: Execute NX-protected page - 4.4.0-78-generic - kernel panic
Well. That did not go so well: there were no ZFS modules in the builds. We've tried all of: * http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.19.8-vivid/linux- image-3.19.8-031908-generic_3.19.8-031908.201505110938_amd64.deb * http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4.68/linux- image-4.4.68-040468-generic_4.4.68-040468.201705140831_amd64.deb * 4.4.0-78-generic with ZFS modules disabled. But because there was no ZFS, our setup wasn't the same. We tried: - 15 minutes of file copying/removing with sync => no panic Then we tried the 78-kernel with ZFS to reproduce the previous days panic: - file copying on the ZFS disk => no panic - 15 minutes of stress(1) testing with `stress -m 1 -c 1 -i 1 -d 1` => no panic - repeat of yesterdays tasks => *instant* *panic* The tasks were in this case: - removing the mysql data dir - aborting the rm, because mysqld (maria) was still running - stopping mysqld, did not work - resuming removal of data dir - mkdir of data dir (took rather long) - kill -9 on mysqld - kernel panic within 2s Previously the panic would occur when we were transferring a complete mysql dataset of 100G-500G over tcp to xbstream (receive). We cannot test any further on this system without working ZFS support, since the environment seems to be different enough for the panic not to happen. Is there any way you could provide the ZFS modules for the stock kernel? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1691741 Title: Execute NX-protected page - 4.4.0-78-generic - kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1691741/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1691741] Re: Execute NX-protected page - 4.4.0-78-generic - kernel panic
> Does the panic stop happening if you boot back into -77? Yes. It's now running fine for more thant 3 hours now on -77. Observe that we have upgraded more than one machine to -78, and only one machine has trouble. > Would it be possible for you to test the latest upstream stable kernel? Ah, you have debianized builds for upstream kernels. I'm sure we can try that tomorrow. Thanks for your questions/feedback. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1691741 Title: Execute NX-protected page - 4.4.0-78-generic - kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1691741/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1691741] Re: Execute NX-protected page - 4.4.0-78-generic - kernel panic
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1691741 Title: Execute NX-protected page - 4.4.0-78-generic - kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1691741/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1350782] Re: Upstart does not reopen /var/log/upstart/* logfiles upon log rotation
A google search turned up this as the most likely candidate for my
logrotate+gzip issues.
I'm going to try this for a workaround:
/var/log/upstart/*.log {
daily
missingok
rotate 7
compress
notifempty
nocreate
# Added by wjd 2017-03 for launchpad bug #1350782
delaycompress
sharedscripts
postrotate
lsof | awk '/ \/var\/log\/upstart\/.*\.log.+/{print $9}' | sed
-e 's#.*/##;s#\..*##' | xargs -IX service X restart >/dev/null
endscript
}
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1350782
Title:
Upstart does not reopen /var/log/upstart/* logfiles upon log rotation
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1350782/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1646538] Re: pdns-recursor 4.0.0~alpha2-2 fails on FORMERR response to EDNS query
It works. $ apt-cache policy pdns-recursor pdns-recursor: Installed: 4.0.0~alpha2-2 Candidate: 4.0.0~alpha2-2ubuntu0.1 Version table: 4.0.0~alpha2-2ubuntu0.1 500 500 http://archive.ubuntu.com/ubuntu xenial-proposed/universe amd64 Packages 4.0.0~alpha2-2osso1 500 500 http://ppa.osso.nl/ubuntu xenial/osso amd64 Packages *** 4.0.0~alpha2-2 500 500 http://apt.osso.nl/ubuntu xenial/universe amd64 Packages 100 /var/lib/dpkg/status $ dig A umcg-nl.mail.protection.outlook.com. @127.0.0.1 +edns +dnssec ... ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 19210 $ sudo apt-get install pdns-recursor $ apt-cache policy pdns-recursor pdns-recursor: Installed: 4.0.0~alpha2-2ubuntu0.1 Candidate: 4.0.0~alpha2-2ubuntu0.1 Version table: *** 4.0.0~alpha2-2ubuntu0.1 500 500 http://archive.ubuntu.com/ubuntu xenial-proposed/universe amd64 Packages 100 /var/lib/dpkg/status 4.0.0~alpha2-2osso1 500 500 http://ppa.osso.nl/ubuntu xenial/osso amd64 Packages 4.0.0~alpha2-2 500 500 http://apt.osso.nl/ubuntu xenial/universe amd64 Packages $ dig A umcg-nl.mail.protection.outlook.com. @127.0.0.1 +edns +dnssec ... ;; ANSWER SECTION: umcg-nl.mail.protection.outlook.com. 10 IN A213.199.154.23 umcg-nl.mail.protection.outlook.com. 10 IN A213.199.154.87 ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1646538 Title: pdns-recursor 4.0.0~alpha2-2 fails on FORMERR response to EDNS query To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pdns-recursor/+bug/1646538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1641380] Re: chromium-browser: ERR_CERTIFICATE_TRANSPARENCY_REQUIRED for Symantec certs
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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1641380 Title: chromium-browser: ERR_CERTIFICATE_TRANSPARENCY_REQUIRED for Symantec certs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1641380/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1641380] Re: chromium-browser: ERR_CERTIFICATE_TRANSPARENCY_REQUIRED for Symantec certs
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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1641380 Title: chromium-browser: ERR_CERTIFICATE_TRANSPARENCY_REQUIRED for Symantec certs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1641380/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1641380] Re: chromium-browser: ERR_CERTIFICATE_TRANSPARENCY_REQUIRED for Symantec certs
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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1641380 Title: chromium-browser: ERR_CERTIFICATE_TRANSPARENCY_REQUIRED for Symantec certs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1641380/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1646538] Re: pdns-recursor 4.0.0~alpha2-2 fails on FORMERR response to EDNS query
The patch is present in rec-4.0.0-beta1, so if Yakkety runs >=4.0.0 (not alpha), we should be good. But sure: $ grep VERSION /etc/os-release VERSION="16.10 (Yakkety Yak)" VERSION_ID="16.10" VERSION_CODENAME=yakkety $ dpkg -l pdns-recursor | grep ^ii ii pdns-recursor 4.0.1-1build2 amd64PowerDNS Recursor $ sudo netstat -apnAinet | grep 53.*pdns tcp0 0 127.0.0.1:530.0.0.0:* LISTEN 18159/pdns_recursor udp0 0 127.0.0.1:530.0.0.0:* 18159/pdns_recursor $ dig A umcg-nl.mail.protection.outlook.com. @127.0.0.1 +edns +dnssec +short 213.199.154.23 213.199.154.87 Confirmed. It's fixed in Yakkety. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1646538 Title: pdns-recursor 4.0.0~alpha2-2 fails on FORMERR response to EDNS query To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pdns-recursor/+bug/1646538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1646538] [NEW] pdns-recursor 4.0.0~alpha2-2 fails on FORMERR response to EDNS query
Public bug reported: The pdns-recursor in Xenial returns this: $ dig A umcg-nl.mail.protection.outlook.com. @127.0.0.1 +edns +dnssec ... ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 57895 While it should return this: ... umcg-nl.mail.protection.outlook.com. 10 IN A213.199.154.87 umcg-nl.mail.protection.outlook.com. 10 IN A213.199.154.23 Because the relevant NS returns FORMERR (it doesn't support EDNS): $ dig A umcg-nl.mail.protection.outlook.com. \ @ns1-proddns.glbdns.o365filtering.com. +edns +dnssec ... ;; ->>HEADER<<- opcode: QUERY, status: FORMERR, id: 1004 ... ;; WARNING: EDNS query returned status FORMERR - retry with '+nodnssec +noedns' This has been fixed in later versions of pdns, specifically here: https://github.com/PowerDNS/pdns/commit/9d534f2a12defc44d2a79291bf34b82e5ee28121 After applying that patch onto 4.0.0~alpha2-2, pdns-recursor behaves as expected and returns the correct A records. This bug manifested itself in our case through Postfix not being able to send mail to Office 365 domains. When postfix tried to enable optional DNSSEC validation -- which it did because of a builtin default -- the A record lookups would start to fail, and this failure would be cached for non-EDNS lookups as well. See original discussion here: http://postfix.1071664.n5.nabble.com/EDNS-DANE-trouble-with-Microsoft-mail-protection-outlook-com-td87331.html#a87353 "EDNS / DANE trouble with Microsoft mail.protection.outlook.com." Attached, the patch that appears to fix the problem. IMHO, Xenial (being an LTS) needs to get this fixed. Either by updating from 4.0.0 to something more recent, or by applying this patch. Cheers, Walter Doekes OSSO B.V. ** Affects: pdns-recursor (Ubuntu) Importance: Undecided Status: New ** Tags: patch ** Patch added: "9d534f2a12defc44d2a79291bf34b82e5ee28121.patch" https://bugs.launchpad.net/bugs/1646538/+attachment/4785809/+files/9d534f2a12defc44d2a79291bf34b82e5ee28121.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1646538 Title: pdns-recursor 4.0.0~alpha2-2 fails on FORMERR response to EDNS query To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pdns-recursor/+bug/1646538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1542586] Re: AttributeError: 'NoneType' object has no attribute 'dumps'
I happens every now and then as far as I can tell (xenial here, but seen with earlier OSes): Cron test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.weekly ) ``` /etc/cron.weekly/apt-xapian-index: Exception ignored in: > Traceback (most recent call last): File "/usr/lib/python3/dist-packages/axi/indexer.py", line 306, in __del__ AttributeError: 'NoneType' object has no attribute 'unlink' ``` -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1542586 Title: AttributeError: 'NoneType' object has no attribute 'dumps' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/synaptic/+bug/1542586/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1613183] Re: gui do-release-upgrade 14.04->16.04 stopped (because of no ubuntu-minimal mirror?)
Thanks for you reply. Looks like it indeed. The only confusing bit left was the apparent "crashing" of the release- upgrade dialog, causing the startup of apport and this bug report in the first place. A dialog with "we cannot properly convert your sources.list, please fix it manually" and no crash would've been better IMHO. But I don't care enough to reopen this ticket. Thanks again! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1613183 Title: gui do-release-upgrade 14.04->16.04 stopped (because of no ubuntu- minimal mirror?) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1613183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1613634] [NEW] python-pisa calls PIL tostring instead of tobytes in xenial
Public bug reported: Versions: python-pil:amd64 3.1.2-0ubuntu1 python-pisa3.0.32-3 Exception: File "...", line 172, in to_pdf context = CreatePDF(src=source, dest=destination, default_css=DEFAULT_CSS) File "/usr/lib/python2.7/dist-packages/sx/pisa3/pisa_document.py", line 161, in pisaDocument doc.build(c.story) ... File "/usr/lib/python2.7/dist-packages/reportlab/pdfbase/pdfdoc.py", line 2190, in loadImageFromSRC raw = im.getRGBData() File "/usr/lib/python2.7/dist-packages/sx/pisa3/pisa_reportlab.py", line 319, in getRGBData self._data = im.tostring() File "/usr/lib/python2.7/dist-packages/PIL/Image.py", line 695, in tostring "Please call tobytes() instead.") Exception: tostring() has been removed. Please call tobytes() instead. Fix: - replace the tostring call with tobytes See the attached patch. Cheers, Walter Doekes OSSO B.V. ** Affects: pisa (Ubuntu) Importance: Undecided Status: New ** Patch added: "0005-tostring-2-tobytes.patch" https://bugs.launchpad.net/bugs/1613634/+attachment/4721766/+files/0005-tostring-2-tobytes.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1613634 Title: python-pisa calls PIL tostring instead of tobytes in xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pisa/+bug/1613634/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1613183] Re: gui do-release-upgrade 14.04->16.04 stopped (because of no ubuntu-minimal mirror?)
** Attachment added: "VarLogDistupgradeMainlog.txt" https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1613183/+attachment/4721073/+files/VarLogDistupgradeMainlog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1613183 Title: gui do-release-upgrade 14.04->16.04 stopped (because of no ubuntu- minimal mirror?) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1613183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1613183] [NEW] gui do-release-upgrade 14.04->16.04 stopped (because of no ubuntu-minimal mirror?)
Public bug reported: The GUI warned that ubuntu-minimal could not be located. The console version showed this: """ After updating your package information, the essential package 'ubuntu-minimal' could not be located. This may be because you have no official mirrors listed in your software sources, or because of excessive load on the mirror you are using. See /etc/apt/sources.list for the current list of configured software sources. In the case of an overloaded mirror, you may want to try the upgrade again later. Restoring original system state Aborting """ This could possibly be caused by me using a custom APT mirror (apt- cacher-ng). Replacing all of `MY_MIRROR` with `nl.archive.ubuntu.com` in sources.list seems to do the trick. The console do-release-upgrade now continues (and later aborts on disk space issues with /boot, but that was easily fixed as well). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ubuntu-release-upgrader-core 1:0.220.8 ProcVersionSignature: Ubuntu 3.13.0-88.135-generic 3.13.11-ckt39 Uname: Linux 3.13.0-88-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 CrashDB: ubuntu Date: Mon Aug 15 08:29:28 2016 InstallationDate: Installed on 2014-04-29 (838 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to trusty on 2016-08-15 (0 days ago) VarLogDistupgradeAptlog: Log time: 2016-08-15 08:29:01.398250 Log time: 2016-08-15 08:29:13.357910 Log time: 2016-08-15 08:29:22.426505 Log time: 2016-08-15 08:29:34.568601 VarLogDistupgradeTermlog: ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade trusty ** Attachment removed: "VarLogDistupgradeAptclonesystemstate.tar.gz" https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1613183/+attachment/4721070/+files/VarLogDistupgradeAptclonesystemstate.tar.gz ** Attachment removed: "VarLogDistupgradeMainlog.txt" https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1613183/+attachment/4721072/+files/VarLogDistupgradeMainlog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1613183 Title: gui do-release-upgrade 14.04->16.04 stopped (because of no ubuntu- minimal mirror?) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1613183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1465959] Re: In phones with two SIMs, if you don't unlock SIM1, the message for unlocking SIM2 says "SIM1"
I think so. I did a single attempt at reproducing it recently, I didn't succeed. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1465959 Title: In phones with two SIMs, if you don't unlock SIM1, the message for unlocking SIM2 says "SIM1" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1465959/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 889250] Re: compiz crashes when using static switcher
void
StaticSwitchScreen::getWindowPosition (unsigned int index,
int *x,
int *y)
{
int row, column;
if (index >= windows.size ())
return;
column = (int)index % xCount;
row= (int)index / xCount;
*x = column * previewWidth + (column + 1) * previewBorder;
*x += getRowXOffset (row);
*y = row * previewHeight + (row + 1) * previewBorder;
}
That's two places for divbyzero in a row; both if xCount is zero. It looks like
it's initialized to 0 and then has lots of opportunity to be zero later on.
However, compiling the thing is apparently not as easy as typing `cmake .`.
Crosses thumbs that I get away with not fixing this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/889250
Title:
compiz crashes when using static switcher
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/compiz-plugins-main/+bug/889250/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 889250] Re: compiz crashes when using static switcher
Also on Ubuntu 14.04. This has never happened to me before, as fas as I'm aware, and now twice in a row: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 14.04.2 LTS Release:14.04 Codename: trusty Versions: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 compiz-plugins 1:0.9.11.3+14.04.20150313-0ubuntu1 gnome-session 3.9.90-0ubuntu12.1 Log: Oct 20 09:31:57 walter-laptop kernel: [ 3194.670620] traps: compiz[2844] trap divide error ip:7fa42242f8de sp:7ffe62e4e6 f0 error:0 in libstaticswitcher.so[7fa422422000+2] Oct 20 09:32:05 walter-laptop gnome-session[2708]: WARNING: Application 'compiz.desktop' killed by signal 8 Oct 20 09:32:05 walter-laptop gnome-session[2708]: WARNING: App 'compiz.desktop' respawning too quickly Oct 20 09:32:05 walter-laptop gnome-session[2708]: CRITICAL: We failed, but the fail whale is dead. Sorry Oct 20 09:50:20 walter-laptop kernel: [ 4297.934327] traps: compiz[6100] trap divide error ip:7f60420008de sp:7ffd526a9ad0 error:0 in libstaticswitcher.so[7f6041ff3000+2] Oct 20 09:50:20 walter-laptop gnome-session[5931]: WARNING: Application 'compiz.desktop' killed by signal 8 Oct 20 09:50:20 walter-laptop gnome-session[5931]: WARNING: App 'compiz.desktop' respawning too quickly Oct 20 09:50:20 walter-laptop gnome-session[5931]: CRITICAL: We failed, but the fail whale is dead. Sorry # # 7fa42242f8de−7fa422422000 = d8de # addr2line -Cfe /usr/lib/compiz/libstaticswitcher.so 0xd8de StaticSwitchScreen::getWindowPosition(unsigned int, int*, int*) ??:? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/889250 Title: compiz crashes when using static switcher To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz-plugins-main/+bug/889250/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1426307] Re: location is inaccurate
I've never had GPS location work without the HERE functions enabled. As soon as I disable it (I have to restart for a change to take effect) I get *no* location info whatsoever. (I have waited for weeks to get a GPS lock, to no avail.) The SensorsStatus tool tells me (when HERE is enabled) that I only have Horizontal accuracy, and that drifts between 8m and 250m. Location: Netherlands SIMs/network: dual sim and lots of wifi around Version: latest Ubuntu 15.04 r24 (20150713) on the Aquaris BQ 4.5 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1426307 Title: location is inaccurate To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1426307/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1442105] Re: GPS not working on my BQ Ubuntu Touch
Same here. I had the "Using GPS only" since I bought the phone and GPS
never worked. Days/weeks of uptime should be enough to get a GPS lock,
right?
Now I enabled the GPS/Wifi/mobile-network ("HERE"), rebooted, and like
you said, within 30 seconds, the SensorsStatus tool started reporting
GPS info. Yay.
Running latest 15.04 r24 atm (updated 7 july).
This does look like a bug which should be fixed; you shouldn't have to enable
privacy-sensitive modes to get the GPS to work.
I'll go back and try what happens when I disable the "HERE" location detection
again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1442105
Title:
GPS not working on my BQ Ubuntu Touch
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-location/+bug/1442105/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1447499] Re: "Rotation locked" icon in notification top bar icon is counter intuitive
The released new icon solves this problem indeed. I'm not fond of the new gsm-signal and wifi indicators though, but that's another matter ;) Thanks for the fix! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1447499 Title: "Rotation locked" icon in notification top bar icon is counter intuitive To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-display/+bug/1447499/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1447499] Re: "Rotation locked" icon in notification top bar icon is counter intuitive
> My proposal is to have two icons: > orientation-lock.svg [standing + flat phone + X] > and > orientation-unlock.svg [standing + flat phone + move-arrow] > > What do you think about that? Awesome! Right now the latter image [standing + flat phone + move-arrow] is used for the lock case; so that would invert its meaning. But don't think users will mind the switch. Thanks for picking this up so quickly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1447499 Title: "Rotation locked" icon in notification top bar icon is counter intuitive To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-display/+bug/1447499/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1447502] Re: "GPS/location" icon in notification top bar is out of sync with settings
No idea; I only noticed this when initially using the phone. If you think it's fixed in the next version, I'll believe you. I'll reopen if it happens again. Thanks! ** Changed in: indicator-location (Ubuntu) Status: New => Fix Released ** Changed in: indicator-location (Ubuntu RTM) Status: New => Fix Released ** Changed in: unity8 (Ubuntu) Status: Opinion => Fix Released ** Changed in: unity8 (Ubuntu RTM) Status: Opinion => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1447502 Title: "GPS/location" icon in notification top bar is out of sync with settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-location/+bug/1447502/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1447479] Re: SIM Pin1 and Pin2 headings get mixed up sometimes
100% reproducible: - boot with dual sim, - when it says sim 1: press X (to cancel) - then it says sim 1, but it wants sim 2 code - enter sim 2 code - at this point, only sim 2 is activated, - authenticate, go to network, unlock sim 1, now it says "sim 2" but wants sim 1 code -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1447479 Title: SIM Pin1 and Pin2 headings get mixed up sometimes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1447479/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1452161] Re: Leaving flight mode, unlocking on dual SIM: header PIN's title prompt does not match with the SIM's number
*** This bug is a duplicate of bug 1447479 *** https://bugs.launchpad.net/bugs/1447479 ** This bug has been marked a duplicate of bug 1447479 SIM Pin1 and Pin2 headings get mixed up sometimes -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1452161 Title: Leaving flight mode, unlocking on dual SIM: header PIN's title prompt does not match with the SIM's number To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1452161/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1447502] [NEW] "GPS/location" icon in notification top bar is out of sync with settings
Public bug reported: On the Aquaris E4.5 (ubuntu 14.10 r21, Utopic Unicorn dev, armhf 20150410-232623), I've noticed the following: - even though I've disabled GPS and "Location detection", the crosshair icon is always on. - after playing around with *enabling* the GPS and waiting a bit, the icon *disappeared*. and then I found that the icon does stay away when disabling it again. perhaps GPS was on the whole time after all? Further info: - this icon had been on since I got the phone (and restarted at least two times) - I've disabled GPS almost the first thing I did Cheers, Walter ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1447502 Title: "GPS/location" icon in notification top bar is out of sync with settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1447502/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1447499] [NEW] "Rotation locked" icon in notification top bar icon is counter intuitive
Public bug reported: On the Aquaris E4.5 (ubuntu 14.10 r21, Utopic Unicorn dev, armhf 20150410-232623), I've noticed the following: - the "Rotation locked" icon appears as "phone which can be rotated", which is illogical to me. If the rotation is locked, then I'd expect the icon to cross out the rotated phone. Perhaps simply adding a diagonal through the icon would make it better? Thanks, Walter severity=veryverylow ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1447499 Title: "Rotation locked" icon in notification top bar icon is counter intuitive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1447499/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1447482] Re: Notification area is readable/editable while in screen-lock mode
*** This bug is a duplicate of bug 1358340 *** https://bugs.launchpad.net/bugs/1358340 Oops. Hadn't found those. Sorry. Disabling both the "Launcher" and "Notifications and quick settings" suits my needs. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1447482 Title: Notification area is readable/editable while in screen-lock mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1447482/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1426400] Re: Time zone selection is really weird
Agreed. I tried Europe first, before I searched for Amsterdam. And when selecting that, I saw that it had properly converted that to the appropriate "Europe/Amsterdam". If we're configuring time, it should IMO not ask for location, but for a timezone, which is Europe/Amsterdam. I don't want to tell my phone where I live, I only want it to switch to/from daylight savings correctly, nothing else. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1426400 Title: Time zone selection is really weird To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1426400/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1447482] [NEW] Notification area is readable/editable while in screen-lock mode
Public bug reported: On the Aquaris E4.5 (ubuntu 14.10 r21, Utopic Unicorn dev, armhf 20150410-232623), I've noticed the following: even though the phone is supposed to be locked, one can: - read incoming messages from the notification (top swipe) area, - change on/off state of bluetooth, gps, wifi, brightness Expected: when not logged in, one should not be able to see more than: - number of notifications (possibly type), but not content - the time, battery life, gps, mobile, bluetooth and wifi *state*, but not be able to switch them on/off Cheers, Walter ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Tags: security ** Tags added: security -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1447482 Title: Notification area is readable/editable while in screen-lock mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1447482/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1447479] [NEW] SIM Pin1 and Pin2 headings get mixed up sometimes
Public bug reported: On the Aquaris E4.5 (ubuntu 14.10 r21, Utopic Unicorn dev, armhf 20150410-232623), I've had the following issue: - both SIMs are inserted, I'm asked to unlock one SIM, and the text above says SIM2 while in fact it wanted the pin code for SIM1 (and vice versa): notably, the counter for the amount of failed attempts was for the correct sim -- which I know, because I didn't have the right code for one of the SIMs the first time I noticed this. - I've also had the problem that the right passphrase didn't unlock (bug #1426876) but returned to the network/mobile screen where I could click un "unlock" a second time, after which it worked For codes that can only be wrongly entered three times, these mixups are rather severe. Cheers, Walter ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1447479 Title: SIM Pin1 and Pin2 headings get mixed up sometimes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1447479/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1387207] Re: [greeter] strange persistent "Enter SIM1 PIN" dialog on Greeter
** Summary changed: - [greeter] strange persistant "Enter SIM1 PIN" dialog on Greeter + [greeter] strange persistent "Enter SIM1 PIN" dialog on Greeter -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1387207 Title: [greeter] strange persistent "Enter SIM1 PIN" dialog on Greeter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1387207/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
