How long should this process of phasing in updates take? update-manager
tells me I'm up to date on 20.04, but:
$ apt list --upgradable | wc -l
WARNING: apt does not have a stable CLI interface. Use with caution in
scripts.
49
It looks like I get all the focal-security updates through update-
It's too late now, but there's a typo in the changelog: "shitfs".
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876645
Title:
Unable to handle kernel pointer dereference in virtual kernel address
Upstream fix is most likely https://gitlab.gnome.org/GNOME/gnome-
shell/merge_requests/763
I have installed gnome-shell{,-common}
3.34.1+git20191024-1ubuntu1~19.10.1 from eoan-proposed and verified that
the "opening activities" delay goes down from ~4 seconds in
3.34.1-1ubuntu1 to <1 second in
I see this in journalctl at approx. the time of this "giving up after 5
attempts", I also use sftp: (where XXX is my user name)
Okt 25 17:51:09 XXX kernel: gvfsd-sftp[10782]: segfault at 55b30002 ip
7f0a424e63ae sp 7fffe1c32c00 error 4 in
libc-2.30.so[7f0a4246e000+178000]
Okt 25
Eric, I believe your mirror is lagging behind ab it?
I just installed 4.15.0-24-generic from -proposed and it fixes the issue for me
(tested 2 suspend cycles – previously it would fail 100% of the time).
** Tags removed: verification-failed-bionic
** Tags added: verification-done-bionic
--
You
Confirming this is still an issue for me after updating my bionic
installation to linux-image-4.15.0-23-generic 4.15.0-23.25, while
https://people.canonical.com/~khfeng/lp1752772-r8169-intx/ worked fine
in recent weeks.
--
You received this bug notification because you are a member of Ubuntu
I'm pretty sure this is a duplicate of #1752772 , right? Like Kai-Heng
Feng mentioned above. If so, please mark as duplicate.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1759644
Title:
[18.04]
>From http://kernel.ubuntu.com/~kernel-ppa/mainline/:
works: v4.17-rc1, v4.17-rc3, v4.17-rc4 (-rc2 not tested, but I assume it
works)
fails: v4.16.7
build for 4.16.8 failed, so I was unable to test that one.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
I forgot this yesterday: I accidentally compiled git master HEAD of that
repo first. It worked fine, so something fixed this bug between v4.16.5
and 46dc111dfe47. If required I can try to bisect, but it will take a
while, my CPU is almost 10 years old (takes 1+ hour to compile the
kernel). I guess
I cloned git://git.launchpad.net/~ubuntu-kernel-
test/ubuntu/+source/linux/+git/mainline-crack and checked out tag
v4.16.5, applied the 6 patches listed at the top of
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16.5/ and the one debug
patch at https://lkml.org/lkml/2018/4/3/136.
journalctl
Related/Duplicate(?):
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752772
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1760073
Title:
No network from suspend resume
To manage
I have added a link to the upstream kernel.org bugzilla, I believe it's
the same bug.
** Bug watch added: Linux Kernel Bug Tracker #198973
https://bugzilla.kernel.org/show_bug.cgi?id=198973
** Also affects: linux via
https://bugzilla.kernel.org/show_bug.cgi?id=198973
Importance: Unknown
Since updating to bionic, I notice the same symptoms (network not
working after suspend).
I'm adding this comment to note that this makes my network come up again, I'll
try to add this as a post-suspend script as described above:
$ sudo modprobe -r r8169
$ sudo modprobe r8169
(Suggested in
Using artful, I updated these packages (everything that used to have version
"17.2.2-0ubuntu1" on my system) to version "17.2.4-0ubuntu1~17.10.1" from
-proposed:
libegl1-mesa:amd64 libgbm1:amd64 libgl1-mesa-dev:amd64 libgl1-mesa-dri:amd64
libgl1-mesa-dri:i386 libgl1-mesa-glx:amd64
Ubuntu 16.10 -> 17.04 upgrade fails because of this, presumably if
"systemctl disable mysql" was used earlier. Is that an unsupported
configuration? I enabled/started mysql when the first modal error
message dialog was displayed and it eventually re-tried the mysql
upgrade (which succeeded with a
Flash not working is less of a show stopper than half of the internet
not working because of trust issues. (Who needs flash anyway? I use it
maybe once a month, but now I can't do my christmas shopping in Chromium
because amazon doesn't work no matter what.) So if you can't get flash
to work, I'd
Thanks Joseph!
I now believe I'm seeing two different issues in 4.8 that are not in 4.4 and
slow down my boot, which is very confusing.
- #1: High number of kworkers (fixed in 4.8 using the two patches and bisected
by Doug Smythies already)
- #2: Unknown other issue. I've noticed that when
Concerning the "bootspeed" tag, the NM issue would be less noticable if
"rc-local.service" was removed from "After=" in plymouth-quit.service.
That way, my boot-to-graphical-login is a few seconds faster because
plymouth is only visible for a very very short time instead of waiting
up to 8 seconds
My boot time comparison: (Wall clock time from GRUB to lightdm ready for login)
4.4: 12.28s
4.8.0-26 + Patches (Joseph's kernel): 21.78s
4.8.0-22 (Yakkety): 25.06s
This is with NetworkManager-wait-online.service enabled, which seems to
take ~8s in my case.
The attached file has systemd-analyze
Thanks Joseph! I'm seeing the same effect described by Martin.
Boot+lightdm+loading Unity 7 is not as fast as it used to be in 16.04.
I need to compare timings (4.8 patched vs 4.8 vs 4.4) tomorrow to make
sure, but I also feel like it's a little faster now with the patches
applied.
The number of
My problem is probably the same that Doug Smythies described in bug
1626564 . I used the "echo workqueue:workqueue_queue_work >
/sys/kernel/debug/tracing/set_event" method and had about 1000 work
items enqueued by "memcg_kmem_cache_create_func" all at pretty much the
same time, which correlates
Well, I guess the other patch is required as well for SLUB (not only SLAB as I
assumed at first):
https://patchwork.kernel.org/patch/9361853/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1626436
This is what I get right after boot and login into Unity 7 (executed in Gnome
Terminal):
$ ps aux | grep kworker | wc -l
1004
Kernel is 4.8.0-22-generic. After a few minutes, only 21 kworkers remain. Load
after 4 minutes is not excessive (1244 sleeping processes), forgot to check
load right
Same here, downgrading to 4.4 from Xenial improved the situation (boot
still feels a little slower than Xenial though, maybe because of the
NetworkManager bug). I use a 7 years old desktop computer based on a
Gigabyte motherboard and AMD Phenom II X4 955 CPU, So it's not Thinkpad-
related.
(From
Public bug reported:
Error displayed during GUI-based upgrade from 14.04 to 16.04.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: printer-driver-gutenprint 5.2.11-1
ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
Uname: Linux 4.4.0-36-generic x86_64
ApportVersion:
I also get this when running sudo unity8-lxc-setup --rebuild:
> Starting the container
> Not able to connect to the network.
When trying to log into the unity8 lxc session afterwards, I get this in
unity-system-compositor.log (probably expected?):
0
130
lxc_container: cgmanager.c:
I should probably add that I'm still on Trusty, kernel 4.2, and an older
mesa/Xorg stack.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1477720
Title:
Unity8 won't install properly
To manage
Hi,
I'm just wondering if WebGL is still disabled in 14.04, even though we
are on chromium 44 now? I wanted to enable WebGL just to see if I could
watch 360° Youtube vids then, and now noticed that it no longer works at
all, apparently due to this Ubuntu change.
I realize that lots of crashes
Since 3.16.7-ckt11 appears to be affected by the ext4+raid0+trim
corruption bug [1], it might be better not to update to -ckt11.
[1] https://bugzilla.kernel.org/show_bug.cgi?id=98501
** Bug watch added: Linux Kernel Bug Tracker #98501
http://bugzilla.kernel.org/show_bug.cgi?id=98501
--
You
This kernel (3.19.7), as well as the SRU-proposed 3.19.8, is also
affected by the ext+raid0+trim chunksize not a power of 2
patch-regression that causes severe data loss. So I certainly don't
want this patch to land on my trusty system with -lts-vivid kernel. :)
Can you check the device log output on the devices page and paste the
contents?
Here's the log after a minute or so (protocol fault at the bottom = I
disconnected the device to copy the log):
http://paste.ubuntu.com/11242404/
I didn't think of checking the log earlier. Probably the first thing
Ah, if the log steadily grows and is never truncated, that might have
caused the increasing CPU usage for rendering the log, and increasing
memory usage as well. I still wonder why the spawning of new processes
fails after some time though.
--
You received this bug notification because you are a
While this happened all the time in the last few days, I now did
something that apparently made it stop (temporarily?).
Maybe deleting the device from the Devices view in Ubuntu SDK? It re-
appeared quickly, but maybe that stopped it. Maybe it's important that
the same device (Nexus 4) has been
Public bug reported:
I'm using qtcreator-plugin-ubuntu
3.1.1+15.10.20150508-0ubuntu1i~0trusty1 from the Trusty PPA.
I'm currently porting my Ubuntu App to Android, so I have my android
phone connected to my computer using USB.
A few days ago I noticed that qtcreator started using a complete CPU
Well, sorry for the long post. %) I think I found the bug.
Anyway, is it possible that…
http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/wily/qtcreator-plugin-ubuntu/wily/view/head:/src/ubuntu/ubuntudevice.cpp
In line 209 or 216, the condition is true because my device is not an
Ubuntu
Thanks for your important questions, Zoltan!
What CPU and how much memory do you have on that device?
It's an old AMD Phenom II X4 955 BE. Still, qt creator usually needs
much less than one full core when just editing code files and generally
works quite well. I have 8GB of memory.
Were you
A full stacktrace could help with finding the error, the message posted
does not tell me what's wrong.
The crash could be related to a broken media file that kills minidlna,
you can test that by setting the media directory to some empty location
on your hard drive. Minidlna code quality has
This bug appears to be fixed now in the PPA, thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1448521
Title:
sudo unity8-lxc-setup fails on 15.04
To manage notifications about this bug go to:
minidlna-1.1.4+dfsg-1 that was imported from Debian to Ubuntu Vivid is
supposed to have a fix for this.
** Changed in: minidlna (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I think this should fix itself when /usr/share/distro-info/ubuntu.csv is
updated to contain the w series. The error occurs in lots of ubuntu-
related tools when there is no known development release. See LP Bug
#1068390 for example.
Nevertheless, unity8-lxc-setup should be fixed to handle that
As I stated above, this should be fixed in recent minidlna releases, so
I close this bug now. If this still happens on Ubuntu 14.04 (Trusty) or
newer releases, please reopen the bug report.
** Changed in: minidlna (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug
It might be interesting to know if this happens when minidlna is linked
against ffmpeg instead of libav. Some people say that libav has more
bugs (some even say it's broken), so maybe this is one of those bugs.
It should be possible to remove libav and install ffmpeg on newer Ubuntu
releases, then
I think this was fixed in minidlna 1.0.22 by this commit:
http://sourceforge.net/p/minidlna/git/ci/c599ed3a9fe79f69c2a229d5f6f1d30534a65bfb/
So let me close this as Fix Released. If anyone has this crash in
Trusty or newer Ubuntu releases, please reopen. :) Ubuntu 12.04
(precise) has an old,
It seems like the attached logs don't tell us why the post-install
script returned an error.
This error might occur if you manually remove the minidlna user or
minidlna group while having minidlna installed on your system.
There could be other problems that cause an exit status 2.
Since this
The report says that this works in Precise (12.04). Which versions are
affected by this bug? Is this still an issue in Vivid? In Trusty, the
comma delimiter seems to work. At least minidlna doesn't crash. (I don't
get any logs and the -d flag crashes, so I can't check for the error
message.)
--
It seems like the attached logs don't tell us why the post-install
script returned an error.
This error might occur if you manually remove the minidlna user or
minidlna group while having minidlna installed on your system.
There could be other problems that cause an exit status 2.
Since this
According to http://sourceforge.net/p/minidlna/bugs/212/ , this should
work since minidlna 1.1.2. So any trusty, utopic or vivid users should
be fine.
Can anyone confirm so we can close this as fix released?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Is this still an issue? I'm not very experienced with upstart. The error
message almost sounds like the minidlnad binary is missing. Can you
check if /usr/bin/minidlnad exists? Maybe your file system was full /
corrupted when minidlna was upgraded the last time? Have you tried
sudo apt-get
I (probably) fixed this by removing the extra space in front of with
in line 293. sudo apt-get -f install then worked without a flaw.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1439158
Title:
Public bug reported:
This error started to appear yesterday whenever I do apt-get things.
$ LANG=C sudo apt-get install unity8-lxc
Reading package lists... Done
Building dependency tree
Reading state information... Done
unity8-lxc is already the newest version.
0 upgraded, 0 newly
Lorenzo, have you tried the PPA referenced by Iain Lane (#35)? I'd love
to test that, but I'm still on trusty and the debs don't work. Let me
try to build the package locally.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Sorry, the unity-control-center package was not taken from the PPA, but
from the bzr branch linked in this bug report. Not sure if these
packages use the same code.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I've built (on trusty) and installed the unity-control-center package
from the PPA, and unity-settings-daemon from utopic, and now I have a
mouse pointer speed option in the settings. That setting was missing
when I used the original trusty packages.
Now another problem is that the mouse cursor
Since you want to mark this bug as Won't fix, can you point me to some
docs for music-hub? I can only find some info about
QtMultimedia.MediaPlayer related to music-hub, but that QML API is
apparently missing the functionality described in this bug report.
I'm already using
This is still an issue, and very confusing. I assume that most
developers who need external dependenices for the click package run into
this and wonder why the linker complains about not finding the library.
I guess most developers find it more convenient to add build rules that
copy prebuilt
Public bug reported:
I think the bug title and the logs attached by ubuntu-bug explain my
issue:
mtp-server fails to start on emulator image 105 (devel-proposed i386)
because there is no /dev/mtp_usb device. After the process quits, it is
instantly respawned, just to fail again. The emulator is
I guess this is no surprise to anyone involved in ubuntu emulator
development, but for completeness sake: This is printed in the
Application Output tab in ubuntu-sdk when launching an app that
targets the 14.10 click target in the current devel-proposed emulator
image. It is supposed to use the
I tried this again now, and after installing libgl1-mesa-dev-lts-utopic
I was able to re-install qt5-default and qtbase5-dev, and then ubuntu-
sdk.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I have now verified that building the goldfish kernel from git with the
upstream commit cherry-picked, and then booting that kernel in the
emulator, solves my issue with libupnp.
** Summary changed:
- kernel null pointer dereference after setsockopt(…IP_ADD_MEMBERSHIP…)
+ [fixed-upstream] kernel
I think the goldfish kernel is not maintained in the android source
package, but in this separate linux-goldfish package, so it's time to
move this bug again.
** Package changed: android (Ubuntu) = linux-goldfish (Ubuntu)
** Summary changed:
- goldfish kernel panic after
I have some more details about the kernel panic.
In net/ipv4/igmp.c, line 320, ip_route_output_ports() is called with socket
(aka sk) = NULL.
In include/net/route.h, line 150, that NULL socket pointer is passed on to
sock_i_uid(), so sock_i_uid(NULL) is called.
That sock_i_uid() call is not in
There's actually a fix upstream, :
https://android.googlesource.com/kernel/goldfish/+/0836a0c191f580ed69254e0b287cdce58481e978
I hope there are plans to rebase to a recent goldfish kernel some time.
:)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Okay, so it's not actually the emulator. The guest system (goldfish?)
simply kernel panics, see the attachment.
I guess the android source package is still correct though.
** Attachment added: goldfish-kernel-panic.log
Public bug reported:
This might be a bug in one of the products the ubuntu emulator is based
on, or maybe it's a configuration issue. I don't know so I report this
here.
I'm trying to use libupnp in the Ubuntu emulator (My app was compiled
using a 15.04 framework / i386 kit chroot created
Turns out that goget-ubuntu-touch is not the correct source package for
this bug, since the emulator runtime is in the android package.
** Package changed: goget-ubuntu-touch (Ubuntu) = android (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Is there any way to preserve wine, libsdl-*-dev and qt5 when installing
the hardware enablement bits on 14.04 (with -proposed disabled)?
I tried the suggested apt command lines, but none of them seemed to
install the new mesa/xorg stack and preserve wine/qt5/libsdl at the same
time. See the
Thanks, Maarten. I just noticed my comment was missing the apt command
that I used.
I now use
LANG=C sudo apt install --install-recommends libgles2-mesa-lts-utopic
libglapi-mesa-lts-utopic linux-generic-lts-utopic xserver-xorg-lts-
utopic libgl1-mesa-dri-lts-utopic
I was still able to reproduce this using Version
39.0.2171.65-0ubuntu0.14.04.1.1064 (hope we can get an update soon btw
:D), but it appears to be much more difficult now. It no longer happens
when I type at my normal typing speed. Maybe that's because the omnibar
suggestions apparently load pretty
This is fixed now, as far as I can tell. Thanks. :-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1396224
Title:
unity-system-compositor fails to launch / terminates with signal 15
To manage
This is probably either a network connectivity issue or related to
censorship / nation-wide firewall in china, as you mention.
So you'd need to fix your internet connection or ask your government to
allow access to the google chrome download (not sure if there's a place
where you can ask for
** Changed in: chromium-browser (Ubuntu)
Status: Confirmed = 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/1386455
Title:
Chromium 37 has 159 known security issues
To manage
Debian status is inaccurate, it is actually something like Invalid /
Wontfix, not Fix Released.
I do think this is a valid bug. The proper solution probably is:
Release an updated pepperflashplugin-nonfree package every time Google
updates the flash plugin. The package should contain a checksum
Someone recently confirmed this, but I haven't experienced the bug in
recent weeks. Possibly since updating to 37?
Does this still affect anyone? If not, I'll close the bug in a few days.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
*** This bug is a security vulnerability ***
Public security bug reported:
Chromium 38 (released 3 weeks ago) fixes at least $52k worth of security issues:
http://googlechromereleases.blogspot.de/2014/10/stable-channel-update.html
So 159 chromium security fixes (with 113 relatively minor) are
I was about to go insane re-creating and updating chroots and using all kinds
of pbuilderrc options. Nothing seemed to help. Then I found this bug report and
applied this patch to my local pbuilder-dist copy:
http://bazaar.launchpad.net/~p8n/ubuntu-dev-tools/othermirror_fixes/revision/1421
This is fixed, right? I just got updated to 37 through update-manager. Thanks a
lot, Chad :-)
I'm not closing it because it's not my bug, but I guess it can be closed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
To clarify:
- So in Debian, all the packages in testing are now built against libav11
AFAICT.
I actually meant:
The packages that are both in sid and in testing were successfully rebuilt
against libav11. However, they are still in sid and waiting to migrate. :-)
--
You received this bug
So in Debian, all the packages in testing are now built against libav11 AFAICT.
I (as a user) hope we can still get libav11 for Utopic.
In case this helps with your decision, these are the packages in sid
which are not built against libav11 (yet?):
- bino (unrelated to libav, some gettext
Chromium is not in main, i.e. it's officially unsupported by
Canonical. Formally, only approved Ubuntu community members (MOTUs)
support chromium in Ubuntu, while Canonical does not guarantee any
support at all.
That's the formal aspect at least. In practice, it seems like a
Canonical employee,
This is unrelated to docker, it's a bug in a minidlna patch that was
added for Debian to possibly allow using logrotate for minidlna.
However, according to a Debian bug report, the log-reopen on signal does
not actually work due to a mistake in the patch, since the log-reopen
function is not
Yes, that's the commit and Katsuhiko TAKAHASHI's comment.
I haven't contacted Benoît regarding this issue, as I haven't received a
response to my mail from last year about updating the package from
1.0.24 to 1.1.x. He is either Missing In Action, or he's too busy to
reply to minidlna mails (or
Michael Gilbert of Debian apparently carries some patches for chromium
that supposedly get rid of SSE2 instructions in the Debian chromium
package (at least in experimental?). User opera posted a link to the
corresponding bug report in Debian. I'm not sure what the status of this
is or if Ubuntu
Well, I didn't push the update. I'm just a user. But if Ubuntu didn't
push newer chromium releases to stable, there'd be a ton of security
flaws by the time even the next STS Ubuntu release is published 6 months
later.
And that would basically mean that any user who cares at least a little
bit
I'll repeat it again: What you are describing works for me, and it works
for Saikrishna.
1) Go to http://www.spiegel.de
2) Observe the location bar shows just www.spiegel.de
3) Copy that text by starting to click somewhere to the right of
www.spiegel.de, then move the cursor to the left until
Frederick, there was no chromium 35 in Ubuntu if I remember correctly,
so you are probably talking about Chromium 34 (that was the current
version in Ubuntu until a few weeks ago when it was upgraded to 36).
Chromium 35 has stopped supporting non-SSE2 Linux systems because,
according to Google,
37.0.2062.94 has 50 more security fixes:
http://googlechromereleases.blogspot.de/2014/08/stable-channel-
update_26.html
CVE-2014-3176, CVE-2014-3177 (critical, sandbox breakage)
CVE-2014-3168
CVE-2014-3169
CVE-2014-3170
CVE-2014-3171
CVE-2014-3172
CVE-2014-3173
CVE-2014-3174
CVE-2014-3175
There is no way (or at least no way that does not involve forking
chromium and quite a lot of coding work) to get chromium to work with
Adobe Flash and have no security issues at the same time. Ubuntu decided
to prefer breaking flash over having precise users exposed to a growing
number of
I'm sorry, you don't have option 3). Only after upgrading to Trusty.
Pepperflash is not available in Precise.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1359615
Title:
[precise] critical: flash
** Summary changed:
- Security fixes from 36.0.1985.143
+ Security fixes from 36.0.1985.143 and 37.0.2062.94
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1360505
Title:
Security fixes from
The http:// is prepended when using either the select text - middle
click clipboard or the ctrl-c/ctrl-v clipboard. At least for me.
So I'd say this is not a bug, unless the reporter confirms there is some
way to copy/paste the almost complete URL without http://. In fact, this
new feature only
Public bug reported:
I hope this wasn't reported already, but couldn't find any recent
reports.
This is a relatively new bug, I don't think it was in v34.
I often move the cursor to the address bar using F6 and instantly start
typing my URL / search term afterwards. F6 leads to a quite
Not sure if that's related or maybe expected behaviour, the strace
contains \35\0\0\0org.freedesktop.UPower.Devic… strings which seem to
indicate that something in system settings repeatedly calls the upower
dbus API. If these dbus calls are not expected (for example to refresh
battery info
FYI, stable Chromium 36.0.1985.125 is now out for Linux, containing 26
security fixes for two more CVEs.
** Summary changed:
- Update Chromium to = 35.0.1916.153 (including security fixes)
+ Update Chromium to = 36.0.1985.125 (including security fixes)
** CVE added:
I finally managed to fix my configuration.
In dconf, I had com/canonical/unity/lenses/disabled-scopes set to
['files-local.scope']. Resetting this to the default [] value and
restarting unity fixed my files lense. FINALLY, YAY! :-)
I *really* wonder how that value sneaked in there. I don't
** Changed in: unity-lens-files
Status: Confirmed = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/856949
Title:
file lens does not display any files
To manage notifications about
A debian user confirmed this is fixed in 1.1.2. So this bug only affects
saucy and precise. :-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1053173
Title:
minidlna crashes on boot when no active
Are there any issues preventing chromium from being updated to a version
without known security vulnerabilities? Even debian has v35 in stable-
security since June 15, and Arch Linux (unsurprisingly) since June 11,
and the vulnerabilites are public since June 10.
Since most other distributions
- is this Bug not in minidlna itself ? Why requires minidlna IP
address to be set (why do not allow to BIND to ANY address)?
I think this is because minidlna does not only listen on some interface
port number, it also needs to send out SSDP packets (multicast) on
relevant network interfaces.
In Ubuntu Trusty I did this to fix the issue (seems like the new version uses
gstreamer 1.0 instead of 0.10):
rm ~/.cache/gstreamer-1.0/registry.x86_64.bin
The file name might be a little different if you're not on x86_64.
--
You received this bug notification because you are a member of
Thanks Doug for your extensive plugin review. Maybe we should continue
this in a new grilo-plugins bug (I noticed we can report bugs at
https://bugs.launchpad.net/ubuntu/+source/grilo-plugins , is that a bad
idea?).
One of them might be an actual totem bug though: jamendo works in
rhythmbox (at
1 - 100 of 144 matches
Mail list logo
