Public bug reported:
surface go 2, 4425Y,8+128,and a 256GB sandisk tf card. i have win 10 on
ssd.so i install it on she tf card. and it goes wrong
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity 20.04.15.17
ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22
Uname:
@3v1n0 I tried but can't yet confirm if the original reboot persistence
bug is still happening, because it seems every time I test it an
additional layer of problems occurs.
Parallels Desktop 13 still doesn't officially support Ubuntu 18.04.
Ubuntu installs okay, but post-installation the VM
I also noticed that the first monitors.xml I attached is version 1 of
the file spec, while the monitors.xml files created after I changed the
scale in Settings are version 2.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "Settings_Details_About.png"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1720465/+attachment/5013916/+files/Settings_Details_About.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "Monitor config after changing scale to 200%"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1720465/+attachment/5013914/+files/monitors.xml_scale-changed-to-200-percent
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I created a new 17.10 VM in Parallels 13 and didn't update any packages
post-installation, so I can still access the scale controls in Settings.
I'm attaching copies of ~/.config/monitors.xml before changing any
settings, immediately after changing Settings > Devices > Displays >
Scale to 200%,
** Attachment added: "Monitor config after reboot"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1720465/+attachment/5013915/+files/monitors.xml_after-reboot
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I confirm #6. First, as I have to do every time I boot into my Ubuntu
17.10 VM under Parallels 13, I went to Settings > Devices > Displays and
changed my scaling to 200% so I can actually read text. Then I performed
some outstanding Ubuntu software updates and rebooted when prompted.
When I logged
Yes, same problem using the final 17.10 release ISO freshly installed as
a guest OS under Parallels Desktop 13 on a MacBook Pro host. The default
session it logs me into uses X.org instead of Wayland for some reason.
My host machine's native resolution is 2880x1800 (but it's detected by
Artful as
@zyga Excellent news, thank you. I'm sure when the initial directory
choice was made the snap team was under pressure to meet product
deadlines (Touch/phone/cloud) so deferring a better solution until later
probably made sense then; an argument can be made for a mandatory
$HOME/snap directory
I agree with comment #2 on urgency. Although this issue has been
prioritized as "Wishlist" it really must be addressed before snaps are
rolled out as a stable production feature of desktop releases, otherwise
the practice of storing data under "$HOME/snap" risks becoming
effectively entrenched.
@andrea-francia Thanks for clearing that up.
I've installed the 0.17.1.14 tarball from upstream and can confirm that
the segfaults no longer occur when invoking the various trash-cli
commands.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
However, the relevant Debian bug says the segfaulting is fixed after
upgrading Python from version 2.7.12 (Ubuntu 16.10 uses the same version
for python2.7 currently) to version 2.7.13:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843612
** Bug watch added: Debian Bug tracker #843612
This is due to incompatibility with Python 3, which Ubuntu now uses
system-wide. Trash-cli was just updated upstream to work with Python 3
and it supposedly fixes the segfaulting, so the latest release needs to
be packaged for Ubuntu.
Upstream bug:
@dsfkljo322332: This bug affects upgrades via apt as well as dpkg. Gdebi
uses one of those on the back end, not sure which. See comment #34 and
#30 for more details.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@dsfkljo322332: Are you using dpkg to install the upgrades? Try
upgrading the libappstream3 package first, then the appstream package.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1579712
Title:
In comment #30 I took the procedure from comment #24 and added two
commands to rename appstream's apt config file, but those commands
aren't necessary because they have no effect when appstream is installed
via the `dpkg` command.
The appstream package's postinst file explicitly calls
@ximion: I missed that. After upgrading libappstream3 from -proposed,
everything works fine. Thanks.
The reason I warned against removing the binary is because it's a bad
practice in general, even though in this particular problem scenario the
removed binary gets restored when its package is
Okay, I've successfully upgraded to appstream 0.9.4-1ubuntu1 from the
-proposed repo, but subsequent `sudo apt-get update` invocations still
hang on appstreamcli. I have no idea what to do now.
@ludentico: Yes, sorry, I was in a hurry and didn't include full paths.
--
You received this bug
@ludentico: Never `rm` files without also removing the package they
belong to.
I discovered a workaround:
$ sudo mv 50appstream 50appstream.disabled
$ sudo apt-get update
$ ... [do what you need here] ...
$ sudo 50appstream.disabled 50appstream
--
You received this bug notification because you
That last command should have been:
$ sudo mv 50appstream.disabled 50appstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1579712
Title:
Refresh hangs due to strdup on non-NULL terminated
@pgbennett
I'm not sure how to discover which particular repo is causing
appstreamcli to hang, so you could try disabling *all* your third party
repos then update. Or disable them one-by-one, but that could be
tedious.
--
You received this bug notification because you are a member of Ubuntu
Public bug reported:
Snap package developers should be encouraged to store user data
according to the XDG Base Directory Specification [1][2].
I installed the "notes" app via snap on a Xenial desktop:
sudo snap install notes
and launched it using the snap wrapper script "/snap/bin/notes".
Public bug reported:
設定 snmpd (5.7.2~dfsg-8.1ubuntu5) ...
update-rc.d: warning: stop runlevel arguments (1) do not match snmpd
Default-Stop values (0 1 6)
/usr/sbin/invoke-rc.d: 1: /usr/sbin/invoke-rc.d: /sbin/runlevel: not found
* Starting network management services:
@Chronos:
Our issue is distinct from this bug. I intend to file a bug upstream
(kernel.org) once I finish working out how the ASUS platform driver
handles Bluetooth and I have a reasonable idea to whom the bug report
should be directed. I'll post a link back here when that's done.
In the
Yep, Docker works again with kernel 3.16.0-22.29. Thanks for fixing this
so promptly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1371310
Title:
docker.io doesn't work with apparmor 3.0 RC1
@Anton:
The fix that was released is the addition of Intel 7260 Bluetooth
firmware for device ID 8087:07dc, which has been shipping in Ubuntu
since at least Saucy.
It doesn't mean that Bluetooth is fixed. Bluez (and/or the kernel's
Bluetooth stack) still doesn't handle the setup properly
I just upgraded to Utopic final beta and am experiencing this bug. What
is a workaround to get my docker containers working?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1371310
Title:
docker.io
@jdstrand:
Sorry, I missed that bit. I rebooted into the old Trusty kernel and
Docker works fine (although compiz/mesa don't like the old kernel, so I
guess I'll try 3.16.0-16.22). Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Jeremy: I remind you that the original report and many comments here
aren't pushing exclusively for total removal of online results from the
Home lens, rather they're also suggesting a compromise position between
that and the current status quo: make this feature opt-in. I haven't
seen a statement
Jeremy: You well know that oftentimes a bug title doesn't sum up the
entirety of the report itself. And in this case, the report proposes an
alternative solution to the one stated in the title:
To anticipate one likely response: I understand that this feature can
be removed by uninstalling the
David: Because of Tor's design its latency is far too high to use in a
Dash context. Dash results are supposed to be near-instantaneous.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1055952
Title:
Daniel: Sorry, but what would be the point of linking Totem to a bug
that's marked Won't Fix?
I'm now convinced that Unredirect fullscreen windows should not be
enabled by default because, as reported above, it causes a major
regression in the functionality of Totem, Flash, and VLC/OpenGL on
My notebook has Intel 945GM video powered by the i915 driver under
Quantal. I'd be okay with enabling Unredirect fullscreen windows by
default if there were some other way to force Totem to sync to the
display's vblank interval for fullscreen video. I tested enabling
Unredirect fullscreen windows
Attaching output log of `gvfs-mount -li`. My 16 GB Patriot USB stick is
auto-mounted and listed as Drive(2).
** Attachment added: gvfs-mount-li.log
https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1067876/+attachment/3432289/+files/gvfs-mount-li.log
--
You received this bug
** Changed in: unity
Status: Invalid = Confirmed
** Changed in: unity (Ubuntu)
Status: Invalid = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1067876
Title:
Missing Safely
Original reporter should use the proper terms for the Unity desktop
components involved. There's no Unity-Task-Bar -- it's called the
Launcher. And the pop-up that appears when right-clicking on a Launcher
icon is called a Quicklist, not a context menu. For general Unity
terminology, see:
Quoting #129:
All of these should come with default settings for maximum privacy when a
live disk/
image boots up, and clear instructions to new users to check these settings
and
set them to their liking.
This is an important point.
Ubuntu needs to adopt a global Privacy by Default
Responding to Mario's comments in #118:
And what are you talking about 'a new user who has yet to learn to use
the terminal to remove the shopping lens'? There is a switch in Privacy
settings now.
The new privacy settings switch as currently implemented is a poor
workaround because it's
Isn't it in KernLog.txt above? Actually, if it wasn't clear I've already
found a solution; it seems like it was a configuration error unrelated
to libpoppler, so you can probably just close this ticket.
--
text is unreadable, shows up as white on white bg
https://bugs.launchpad.net/bugs/662851
Public bug reported:
Binary package hint: evince
Text is incorrectly rendered in white color on white background, making
it unreadable. Lines and shaded areas are still visible. However, text
can be selected and copy/pasted, it's just invisible.
Screenshot: http://imgur.com/8Y0R8.png
Examples:
--
text is unreadable, shows up as white on white bg
https://bugs.launchpad.net/bugs/662851
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Sorry for bothering everyone... I found the problem in the kernel log as
apparently apparmor wasn't allowing the fonts to be loaded. =\
--
text is unreadable, shows up as white on white bg
https://bugs.launchpad.net/bugs/662851
You received this bug notification because you are a member of
43 matches
Mail list logo
