@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 Desktop
Packages, which is subscribed to gnome-shell in
** 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 Desktop
Packages, which
** 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 Desktop
Packages, which is subscribed to gnome-shell in
** 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 Desktop
Packages, which is subscribed to gnome-shell in
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%,
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
@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 Desktop
Packages, which is subscribed to appstream in 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 Desktop
Packages, which is subscribed to appstream in Ubuntu.
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
That last command should have been:
$ sudo mv 50appstream.disabled 50appstream
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream in Ubuntu.
https://bugs.launchpad.net/bugs/1579712
Title:
Refresh hangs due to strdup on
@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
@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 Desktop
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:
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 Desktop
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dp-unity
19 matches
Mail list logo
