I can also confirm that after following the instructions from #51 on
Bionic, this bug is fixed.
(I would however comment that it would have been easy to miss that
safety measure and upgrade a whole bunch of proposed packages by
mistake. I would caution everyone to be more careful when directing no
However, changing `glib`'s `scaling-factor` to 2 as described by both
answers to https://askubuntu.com/q/906797/142526 did solve the issue on
my desktop, running Bionic.
This is accomplished by creating
`/usr/share/glib-2.0/schemas/93_hidpi.gschema.override` with
[org.gnome.desktop.interface]
I can also confirm that after following the instructions from #51 on
Bionic, this bug is fixed.
(I would however comment that it would have been easy to miss that
safety measure and upgrade a whole bunch of proposed packages by
mistake. I would caution everyone to be more careful when directing no
No, I was mistaken; it didn't solve the issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1726548
Title:
Windows resized after resume
To manage notifications about this bug go to:
https://bugs.l
I have this issue on a desktop connected to a Dell 28" at a resolution
of 3840x2160 and scale of 200%. Running `gsettings set
org.gnome.desktop.interface scaling-factor 1` (or `2`) doesn't do the
trick.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
@pjgoodall, how was a fix released? `apt policy zfs-auto-snapshot`
returns no results on Xenial.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1602409
Title:
Ubuntu 16.04 Should package zfs-auto-sna
I can also confirm that the bug is fixed (tested with Texmaker; I don't
have Qt Assistant).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1380702
Title:
No keyboards shortcuts in QT apps
To manage
@Robert yes, you would, as this bug appears in the version of TeXlive
contained in the official repository.
Purge TeXlive again, but next time follow the instructions on
https://www.tug.org/texlive/quickinstall.html to install a vanilla
instance of TeXlive.
--
You received this bug notification
@YihuiXie(xie) of course; I don't mean to imply the bug is any less
important to address because of this workaround. Just to point
@RobertBlankenship in the right direction (as he indicated he wishes).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
Let me just re-iterate that comment #14 includes another workaround, in
my opinion superior to removing the `app-menu-qt5` package altogether. I
suspect that it would still works in 16.10.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
@RobertOrzanna,
Is that after manually removing it, or does 16.10 come that way?
If the latter, I'd still attempt the workaround (as I think it actually
works around what's wrong in the relation between QT5 and Ubuntu's Dash,
instead of manually 'crippling' Unity to 'force its hand', as it were).
@Dimitry, whether or not `appmenu-qt5` is in use in 16.10, that doesn't
tell us if running a QT5 program setting `ENV UBUNTU_MENUPROXY= `
returns the use of keyboard shortcuts. Can you confirm / deny?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
@NorbertPreining have you noted the fact that this error is given in response to
> tlmgr init-usertree
as well? It seems one cannot set up user-mode. I presume that's not how it's
*supposed* to work?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
@NorbertPreining: Ok, that's reasonable enough (though not clear from
previous remarks; certainly, I see no reason to close this bug
considering it is still present in Ubuntu).
If it helps anyone, this issue affected me on a machine which shouldn't
have had `texlive-base' installed; something in t
Public bug reported:
When I originally upgraded to Saucy, I encountered the same bug many
reported with using modifier-only combinations to switch keyboard layout
(but 1218322?). Thankfully, that was swiftly resolved with suggested
updates (I didn't employ any special ppa solution back then, but r
** Changed in: lxc (Ubuntu)
Status: Expired => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1367495
Title:
Bridge still not created if bind9 is on
To manage notifications about th
** Attachment added: "ps.txt"
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1367495/+attachment/4294749/+files/ps.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1367495
Title:
Bridge sti
** Attachment added: "brctl.txt"
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1367495/+attachment/4294748/+files/brctl.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1367495
Title:
Brid
** Attachment added: "ifconfig.txt"
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1367495/+attachment/4294747/+files/ifconfig.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1367495
Title:
Certainly. The service was already running, so I stopped and restarted
it for good measure.
root@srv-Ub1404:~# start lxc-net
start: Job is already running: lxc-net
root@srv-Ub1404:~# stop lxc-net
lxc-net stop/waiting
root@srv-Ub1404:~# start lxc-net
lxc-net start/running
`sudo netstat -nr` returns:
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt
Iface
0.0.0.0 .1 0.0.0.0 UG0 0 0
eth0
.0 0.0.0.0 255.255.255.0 U 0 0 0
eth0
`sudo ne
Well, I can't attest to Dan Kegel's setting, but this is my copy of
`/etc/default/lxc-net`. Indeed, that line isn't commented out, and I
don't have a `dnsmasq.conf` in `/etc/lxc`.
** Attachment added: "lxc-net"
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1367495/+attachment/4295165/+fil
This is odd. On advice from Flockport community I attempted to manually
configure the bridge (its basic elements, at least) by entering
sudo brctl addbr lxcbr0
sudo ifconfig lxcbr0 10.0.3.1 netmask 255.255.255.0 up
This went just fine, with `ifconfig` reporting (beyond those interfaces al
Well, it does help `lxc-net` create the bridge (shown on `brctl show` and
`ifconfig`), but apparently not to configure it appropriately. `lxc-net` is
still not listed when I run `service --status-all`, and attempting to start a
container returns:
server@srv-Ub1404:~$ lxc-start -n u1
Quot
Wait, 'lxc-net' does show as `running` when I run `initctl list`. I
guess that's what I get for not checking if the manuals I've been using
are 100% compatible with my distro.
Regardless, it still gives those errors, and starting containers fails
with that seemingly network-related message. Attemp
Aha! It was an unprivileged container (I used to get the same error
messages with privileged and unprivileged containers), and it turns out
in one of my purge - install cycles I forgot to add "$USER veth lxcbr0
2" to `/etc/lxc/lxc-usernet`. I did that (it's now the only line there
after the first c
Okay. FYI I went ahead and defined my own bridge to let containers
communicate directly with my router's dhcp server, but I've created and
started a new privileged container `pr1` and made sure it uses `lxcbr0`
and not my `br0`. Still, it's possible I'll have to tell `lxcbr0` to
plug into `br0` rat
Not by design, no. Any of that, really, since I wouldn't have known
where to go to make these alterations if I wanted to (well, now that you
pointed that out, I should be able to reverse-engineer it and see if it
at least assigns IP addresses to containers automatically that way).
It's a pretty new
@Robert what response do you get when you type `whereis tlmgr`?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1242914
Title:
tlmgr unable to set up TLPDB
To manage notifications about this bug go t
29 matches
Mail list logo
