I did a bisect as asked in the upstream issue I reported at
https://github.com/vim/vim/issues/5237 and I think that
https://github.com/vim/vim/commit/cd142e3369db163a511dbe9907bcd138829c
is the offending commit.
** Summary changed:
- vim-gtk can no longer save to GVFS SFTP mounts in 18.04
+ v
All autopkgtests for the newly accepted mesa (19.2.1-1ubuntu1~18.04.1) for
bionic have finished running.
The following regressions have been reported in tests triggered by the package:
firefox/70.0.1+build1-0ubuntu0.18.04.1 (armhf)
pymol/1.8.4.0+dfsg-1build1 (armhf)
Please visit the excuses pag
Sorry, I misremembered my results from yesterday. I just checked again.
The permissions are in fact different: the Nautilus-created files are
644 (because my "New Text Document.txt" template in ~/Templates is 644),
while files created with e.g. touch are 664.
Since both allow me, the owning user,
The permissions and ownership are the same. It seems to persist across
ejecting and remounting the SSH mount. I can see if it persists across a
reboot or magically spreads from one SSH mount to a different mount (via
a different hostname/ip for the same machine), but I suspect it won't.
November 1
** Changed in: glib
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1852844
Title:
Nautilus/Files UI requires sudo access to unmount a disk th
Public bug reported:
i was upgrading my windows 10 from 14 to 16 using sudo do-release-
upgrade, which failed about an hour into the process
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: resolvconf 1.78ubuntu7
Uname: Linux 3.4.0+ x86_64
ApportVersion: 2.20.1-0ubuntu2.21
Architecture:
** Changed in: upower
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upower in Ubuntu.
https://bugs.launchpad.net/bugs/1852911
Title:
CriticalPowerAction=Suspend should be supported
Status in
Same problem here, cannot print using shared printer on the network. It
says waiting for authentication. That s annoying.
Is there a workaround? Would installing a prior version of smbclient do
the trick?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded pack
By the way the actual discussion seems to be this one:
https://gitlab.freedesktop.org/upower/upower/issues/59
And this is the unmerged PR with the simple patch:
https://gitlab.freedesktop.org/upower/upower/merge_requests/11
** Bug watch added: gitlab.freedesktop.org/upower/upower/issues #59
Upstream seems to be ignoring the user's wishes. Would Ubuntu be willing
to take the patch?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upower in Ubuntu.
https://bugs.launchpad.net/bugs/1852911
Title:
CriticalPowerActio
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs
Thank you for your bug report, the previous comment seems to suggest
it's a kernel issue?
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launch
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.n
In the appendix, an image of the screen in which the PC's crotch hangs.
I hope, this might be helpfull.
Thank you
On 16.11.19 22:48, Sebastien Bacher wrote:
> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. Unfortunately, we cannot work on this bug because y
Thank you for your bug report. Does it only happen directly after
creating the file or is it still an issue for those files after e.G a
reboot?
Could you see if there is anything different in permission/ownership
between the files created by nautilus and from the commandline?
** Changed in: nauti
Thanks
** Package changed: nautilus (Ubuntu) => glib2.0 (Ubuntu)
** Changed in: glib2.0 (Ubuntu)
Status: New => Triaged
** Also affects: glib via
https://gitlab.gnome.org/GNOME/glib/issues/1942
Importance: Unknown
Status: Unknown
--
You received this bug notification becaus
Thank you for your bug report, it has been reported upstream as well on
https://gitlab.freedesktop.org/upower/upower/issues/23
Which got that reply
'Suspend still uses significant amounts of power, and if you run out of
power and do a hard powerdown when suspended bad things can happen.'
** Bug
So it works under GNOME/the default Ubuntu session but is only an issue
under xubuntu? Did you try the xfce remix from those other
distributions? Is IBUS maybe active on some distributions and not
others?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packag
Thanks, closing
** Changed in: xorg (Ubuntu)
Importance: Undecided => Low
** Changed in: xorg (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launch
You have been subscribed to a public bug:
An external disk device is declared in '/etc/fstab' with 'auto,nofail,users'
options:
UUID=aa083302-...-b66c0715eaf1 /media/ushakov/TOSHIBA_SYSTEM ext4
nodev,nosuid,auto,nofail,users 0 2
It is then successfully mounted automatically upon being connected
Hello Timo, or anyone else affected,
Accepted mesa into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/19.2.1-1ubuntu1~18.04.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://
Installed snapd from proposed, rebooted, and /snap/bin is now in path of
systemd-run unit
Nov 18 18:25:26 well-monkey env[298]:
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin
# dpkg-query -W snapd
snapd 2.42.1+18.04
Prior to reboot it was not in PATH of a systemd-r
Hello Timo, or anyone else affected,
Accepted libclc into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/libclc/0.2.0+git20190827-1~ubuntu18.04.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package.
@hui.wang
Reply to #30
ahh...bad news...
Reploy to #31
uname -a
Linux lilian-dev 5.0.0-37-generic #41+redmiv3 SMP Mon Nov 18 13:48:44 UTC 2019
x86_64 x86_64 x86_64 GNU/Linux
working with this V3 Kernel, with external mic. (thank you!)
--
You received this bug notification because you are a me
After mentioning that I cannot reproduce the problem on Fedora and
Manjaro, they replied that this is probably the Ubuntu-specific bug and
promptly closed the bug. Note that the status from Bug Watcher updater
is incorrect.
--
You received this bug notification because you are a member of Ubuntu
** Changed in: gtk
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1848865
Title:
Spurious "key_press_event" when focus on entry widget u
So let us try to fix the problem on external mic. when you have time,
please install the v3 kernel, then plug headset to test the external
mic.
thx.
https://people.canonical.com/~hwang4/redmi/v3
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, whic
This bug has actually been fixed. At least in Bionic we now have:
* xinit:
Recommends: ... gnome-terminal | xterm | x-session-manager | x-window-manager
| x-terminal-emulator
* xorg:
Depends: ... gnome-terminal | xterm | x-terminal-emulator, xinput
--
You received this bug notification beca
Sorry, mail got lost. Here's a fix:
https://github.com/lxc/lxc/pull/3187
** Changed in: lxc (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpa
Christian: Discussed this bug with stgraber last week. Sounds like
/dev/network_latency is just an arbitrary device picked for a test case,
and since it's been removed upstream a different device should be used.
He said you could get this fixed.
** Changed in: lxc (Ubuntu)
Importance: Undecided
After latest Ubuntu updates mouse seems to work properly without having
to execute
$ sudo hcitool lecup --handle 3585 --latency 0 --min 6 --max 8
Versions in my system:
$ uname -a
... 5.0.0-36-generic #39~18.04.1-Ubuntu SMP Tue Nov 12 11:09:50 UTC 2019 x86_64
x86_64 x86_64 GNU/Linux
$ apt-cac
** Attachment added: "/var/crash/_lib_systemd_systemd.0.crash"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1852903/+attachment/5306190/+files/_lib_systemd_systemd.0.crash
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscr
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3-defaults in
Ubuntu.
https://bugs.launchpad.net/bugs/1841072
Title:
test_reflection.CallbackEqualityTest.test_different_instance_callbacks
fails
** Patch added: "py38.patch"
https://bugs.launchpad.net/ubuntu/+source/python-oslo.utils/+bug/1841072/+attachment/5306166/+files/py38.patch
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3-defaults in
Ubuntu.
https:
I think actually strict can be dropped.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3-defaults in
Ubuntu.
https://bugs.launchpad.net/bugs/1841072
Title:
test_reflection.CallbackEqualityTest.test_different_instance
Ah I know why your internal mic doens't work, it is a new HW design, the
internal mic is connected to PCH instead of codec, so it needs sof
driver and firmware/tplg/ucm to work. But so far, we don't have them for
Xiaomi.
We only have some files which are specific to some dell machines and
lenovo m
According to #4, the internal mic connects to PCH, so it needs the sof
driver and firmware/tplg/ucm to work. So far, we don't have those files.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bug
Please find the attached dumpfile
** Attachment added: "RtHDDump.txt"
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1852922/+attachment/5306147/+files/RtHDDump.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
38 matches
Mail list logo