In my case, a docker-based firmware build process produces a update
package (owned by root, for some reason), which I upload to a target via
a web-interface.
Sure, I can change the owner of the files but still, this used to work
and it doesn't now.
Let me turn the question around. What is the
Public bug reported:
The chromium snap cannot access files in my $HOME that have a different
owner, even though the files are world-readable.
** Affects: chromium-browser (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of
Public bug reported:
gcc-avr packages for artful and bionic includes the files
/usr/lib/libcc1.* which probably isn't correct (I suspect they should be
in the target specific path, if anywhere) and may conflict with other
gcc packages. It specifically conflicts with the "GNU Arm Embedded
This consistently happens when I use usb-creator. I've tried the lubuntu
17.10 image and the ubuntu 17.10 image, on several USB sticks. Usb-
creator finally reports success, but the resulting USB stick FAILS
verification (both in the installer and manually by comparing md5sums).
** Also affects:
By the way, this was on an up to date 17.10, kernel 4.13.0-17-generic.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1688920
Title:
INFO: task systemd-udevd:326 blocked for more than 120 seconds.
I got the same dmesg output when using Startup Disk Creator to write an
(L)ubuntu ISO image to a USB stick. After a very long time, and three
such messages in the log, the disk creator finally claimed that it was
complete. I'm not confident that the installation medium is actually OK,
will try it
BTW, the long timeout you see on short name lookup failures is most
likely due to LLMNR being on by default. I think this is insane and I
always switch it off in /etc/systemd/resolved.conf .
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Paul Smith, what you describe is information leakage and shouldn't IMHO
work as you say by default.
Consider that I'm connected to a corporate network and have an
(untrusted) VPN active which I only want to use to access resources on
its network (never-default: yes). Then by having the resolver
to->two
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1726124
Title:
DNS domain search paths not updated when VPN started
To manage notifications about this bug go to:
Public bug reported:
The gemspec file is missing from the package, causing packages that
depend on ruby-underscore-rails to fail on install (notably "gitlab").
Manually adding the file from
https://github.com/rweng/underscore-rails/blob/v1.8.2/underscore-rails.gemspec
as
Christopher, I have since upgraded that Dell Precision to 17.04 and
while I still often get the error popup on that computer I cannot
confirm that it is actually Xorg that crashed, because now that I
looked, the crash popup on 17.04 today was about some unrelated software
Reported as Bug 1694331.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1426596
Title:
I get an "error report" popup on log-in
To manage notifications about this bug go to:
Public bug reported:
Sometimes (not very often), Ubuntu shows an error popup immediately
after login (after power-on) that says Xorg has crashed. No other ill
effects have been noticed, everything works normally after that.
The automatic error reporting does not go through because of
This still happens from time to time on a fresh install of 16.10 on a
Dell Precision 5520. So x86_64. Apport says it's unreportable because
the core file is truncated.
** Changed in: xorg (Ubuntu)
Status: Expired => Confirmed
--
You received this bug notification because you are a member
I'm pretty sure that at some point in previous releases, the normal
system Shut down dialog has been shown after clicking "Reboot now..." so
I could choose to shut down instead of reboot. Usually, I defer
rebooting until I anyway want to shut down, so "Shut down" is the normal
choice for me.
--
Public bug reported:
When Software Updater starts, the "Details of updates" section only
covers half the window's height, even though the "Technical description"
section is collapsed. Refer to attached image #1.
If I expand then collapse "Technical description", the "Details of
updates section"
The fix is most definitely in the SF repo:
http://sourceforge.net/p/openocd/code/ci/96549bf0121a7cff08885ddca22ab7a1c362ea24/
You may want to check that you're using the correct URL, SF changed it a few
years back and unfortunately the old one is still available but frozen. The
correct one
Why was this marked invalid? It's an obvious bug which can be reproduced
like in comment #8.
In short, after running empathy -p once, the preference windows opens
every time the empathy windows is raised by executing empathy, even
without the -p.
Interestingly, even when starting using the
Just a thought... Is DAHDI really required for asterisk? I was about to
install asterisk in a linux container, but since it depends on dahdi it
had to pull in all sorts of linux kernel packages which are nonsensical
and probably would fail inside a container.
If it's not required, maybe dahdi
I'm having the same problem here, with current karmic. My logs have
gotten cluttered like this for ages, but it's not until now I realised
what's causing these messages.
I have a Logitech MX500 mouse, with buttons above and below the scroll
wheel to scroll up/down just by holding one of these
** Bug watch added: GNOME Bug Tracker #578837
http://bugzilla.gnome.org/show_bug.cgi?id=578837
** Also affects: fileroller via
http://bugzilla.gnome.org/show_bug.cgi?id=578837
Importance: Unknown
Status: Unknown
--
unintuitive back and forward
Public bug reported:
Binary package hint: file-roller
The back and forward buttons don't work the way they do in other
applications (web browsers, nautilus,...).
Consider an archive with the following directory structure:
/
/a
/a/b
/a/c
After browsing from / to /a to /a/b, you press Back and
** Attachment added: file-roller-2.24.1_history-fix.diff
http://launchpadlibrarian.net/24711317/file-roller-2.24.1_history-fix.diff
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/24711318/Dependencies.txt
** Attachment added: ProcMaps.txt
Oops, maybe should free the element data as well.
** Attachment added: file-roller-2.24.1_history-fix2.diff
http://launchpadlibrarian.net/24728371/file-roller-2.24.1_history-fix2.diff
--
unintuitive back and forward
https://bugs.launchpad.net/bugs/354136
You received this bug notification
I still have this problem in Dapper with klibc-utils 1.1.16-1ubuntu5
--
Machine won't boot because fstype misidentifies ext3 filesystem as minix
https://launchpad.net/bugs/61361
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
25 matches
Mail list logo
