Here is one method to see the dialog without working remotely:
sudo sed 's/yes/auth_self/' -i
/usr/share/polkit-1/actions/org.freedesktop.accounts.policy
Then press Alt+Ctrl+F2 to switch to vt2, and Alt+Ctrl+F7 to switch back to vt7.
After testing, to revert the change, run:
sudo sed 's/auth_sel
To sum up, two problems:
1) `metacity (and marco) --composite` in 12.04 and 14.04 had only 60% of the
compiz performance.
2) `metacity` (both composite and no-composite) got a lot slower in 16.04, at
60% and 25% respectively of the compiz performance.
--
You received this bug notification beca
> Any chance that you could track down version when it started to be slow?
> Was composite already slow in previous LTS?
Initial tests show that metacity had about the same performance as marco in
12.04 and in 14.04.
In those versions, `metacity (or marco) --composite` performs only about 60% as
mterry, charlesk, I took the liberty of subscribing you because I think it
involves this commit:
https://code.launchpad.net/~mterry/indicator-messages/tell-accounts-services/+merge/93290
The issue is happening to me as well, on Ubuntu 16.04 gnome-flashback, in 2
cases:
1) sometimes when I try to
Yet another benchmark, glmark2, in a very recent core i5 client.
Scores:
No WM: 2058
marco --no-composite: 1894
compiz : 1878
metacity --no-composite: 742
xcompmgr: 716
marco --composite: 708
metacity --composite: 441
In an ideal world, gnome-flashback would support compiz first, then
`metacity -
I was able to reproduce the issue in Debian Stretch after applying an
Ubuntu specific patch to it. So I'm suspecting that Ubuntu's etwork-
manager might be involved in this, I've put it to the affects list.
Specifically, by editing Debian's /lib/systemd/system/NetworkManager.service
like this:
-A
I can't reproduce the issue in Debian Stretch.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1487679
Title:
Breaking ordering cycle by deleting job nbd-client.service/start
To manage notifications
Hmm. The "2 3 4 5" change doesn't seem to be enough to break the
dependency cycle.
I played a bit to see what could break the cycle but I couldn't find it.
By completely removing /etc/init.d/nbd-client, all is fine.
By putting *just* this minimal header:
# Required-Start: $network
...and removin
The same issue (mostly) was reported in https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=796633
Wouter plans to replace the init script with a generator in time for
Debian Stretch.
I've asked him to comment on if what pitti suggested is acceptable till
then (for Ubuntu Xenial's release).
** Bu
I'm experiencing this in Xenial 16.04 fully updated.
I have nbd-client installed but I'm not using its sysvinit service at all
(LTSP).
One out of 10 boots, systemd decides to:
Απρ 07 08:20:15 srv1-dide systemd[1]: network.target: Breaking ordering cycle
by deleting job NetworkManager.service/star
> Probably way easier is to document, to execute in terminal:
> gsettings set org.gnome.metacity compositing-manager false
It's easy for one sysadmin to run a few commands in a terminal.
It's not easy for hundreds of students, e.g. 5-10 years old, to run a few
commands in a terminal.
Sysadmins (
> @Alberts, I'll do some more tests and come up with hard numbers
concerning the performance of metacity with or without compositing.
I did some benchmarks and reported them in
https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1566157
Now I'm more convinced that metacity's compositing-manag
Here's another benchmark, with an SDL 2D game, teeworlds, running full
screen:
no wm: 220 FPS
metacity --no-composite: 220
metacity --composite: 130
compiz: 218
xcompmgr: 130
compton: 129
I really think that the user's choices would be:
1) compiz, for every PC that supports it,
2) metacity --no-c
And here are some numbers for glxgears again (on another pc), but with xcompmgr
and compton included.
The first column is the WM used, the second is the FPS for glxgears, and the
third the FPS for glxgears -fullscreen:
no wm 221 15
metacity --no-composite 170 15
metacity --composite
I run another set of benchmarks using x11perf.
I don't know how much they can help in pinpointing the issue(s), but they do
show that `metacity --composite` is extremely slower than `metacity
--no-composite` or `compiz`.
I'm attaching the output in LibreOffice Calc format, I think it's more
read
Ah, I forgot to include the results without a window manager as a
comparison:
$ killall metacity & sleep 5 && glxgears -fullscreen & sleep 20 && killall
glxgears
44884 frames in 5.0 seconds = 8976.656 FPS
44905 frames in 5.0 seconds = 8980.993 FPS
Normalized: 118 FPS, the fastest of all.
$ kil
Public bug reported:
I did the following benchmarks between `metacity --no-composite`,
`metacity --composite`, and `compiz`, in Ubuntu 16.04.
First, I disabled vsync:
$ cat ~/.drirc
Then I ran glxgears as follows:
$ metacity --no-composite --replace & sleep 5 && glxgea
@Alberts, Dmitry:
> No compositor means - no desktop window or it will be black - you will never
> see background.
> My plan is to fix this in Xenial+1. Less patches will mean less work for me,
> too :P
That's a good example, does that mean that in Ubuntu 16.10 if one
doesn't use compositing he
@Alberts, I'll do some more tests and come up with hard numbers concerning the
performance of metacity with or without compositing. I do believe that in some
cases it will be possible to optimize the performance through appropriate bug
reports and patches; but I also strongly believe that there
Public bug reported:
In Ubuntu 12.04 and 14.04, metacity's compositing-manager was false by default.
In 16.04, it's been set to true.
I tried to pinpoint the advantages vs the disadvantages of that, and currently
I've only seen disadvantages.
I was testing with: gsettings set org.gnome.metacity
@Dmitry, I don't know why compositing-manager was changed from false to true,
so I didn't know if it was important to revert it or not. I thought that people
that want a compositing manager use compiz, but since metacity is implementing
it with xrender instead of opengl, maybe it will work fine
I was able to reproduce it:
*) In flashback 12.04, by setting
/apps/metacity/general/compositing_manager=true. The default was false, that's
why we never saw the problem there.
*) In flashback 14.04, by setting org.gnome.metacity compositing-manager=true.
The default was false, that's why we nev
Testing with lightdm-gtk-greeter, I do get the expected xprops:
ESETROOT_PMAP_ID(PIXMAP): pixmap id # 0xe1
_XROOTPMAP_ID(PIXMAP): pixmap id # 0xe1
And it works fine, i.e. no grey background there.
I'm testing with the default background, i.e.
$ gsettings get org.gnome.desktop.background
Hi Alberts, sure, here it is:
_NET_WORKAREA(CARDINAL) = 0, 0, 1024, 768, 0, 0, 1024, 768, 0, 0, 1024, 768, 0,
0, 1024, 768
_NET_CLIENT_LIST_STACKING(WINDOW): window id #
_NET_CLIENT_LIST(WINDOW): window id #
_NET_DESKTOP_NAMES(UTF8_STRING) = "Χώρος εργασίας 1", "Χώρος εργασίας 2",
"Χώρος εργασ
Two more tests.
1) I created an /usr/share/xsessions/xterm session that just ran xterm.
At that xterm, I ran metacity. It cleared the wallpaper. I don't think it
should have cleared it at that point.
I killed metacity and the wallpaper was restored.
2) I created a /usr/local/bin/metacity wrapper
I think that gray background is caused by metacity.
If at that point I kill metacity, I get the lightdm wallpaper back.
If I run metacity again at that point, I get the user wallpaper properly drawn
(that's a different wallpaper than the one used by lightdm).
Maybe a race condition between metaci
Here's one method to reproduce it and get a shell at exactly the point
where the gray background is drawn:
sudo echo '#!/bin/sh
xterm
exec /usr/bin/gnome-panel "$@"' > /usr/local/bin/gnome-panel
sudo chmod +x /usr/local/bin/gnome-panel
Once that wrapper is created, try to login. You'll get an x
Guys you are right, it only happened in my user account because I had a
~/bin/evolution shell wrapper from the old days, even though I no longer
have evolution installed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
ed?
I replied:
> On 23/12/2015 07:45 μμ, Alkis Georgopoulos wrote:
>
> In gnome-flashback-metacity, it lasts for half a second, and it's a
> solid gray #808080 (I managed to get a screenshot of it).
>
> In gnome-flashback-compiz, it lasts for 0.1 second so at first I was
I installed Ubuntu and then gnome-flashback. I didn't install evolution.
Unity hides the "Add Event" menu, gnome-flashback doesn't hide it.
I don't know if Unity (re)shows the menu if one installs evolution.
Isn't it a problem that there's a menu that does nothing in a normal
installation?
If hid
Public bug reported:
gnome-flashback-compiz under Ubuntu 16.04.
Clicking on the sound applet and then selecting "Sound Settings" doesn't do
anything.
It should launch 'unity-control-center sound' instead.
Clicking on the name applet and then "About This Computer" should launch
"unity-control-ce
apw uploaded a test kernel without CONFIG_IP_PNP in
http://people.canonical.com/~apw/lp1259861-xenial/.
I tested it with "ip=dhcp break=top" and it didn't have the 10 sec delay.
Thanks a lot Andy!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
$ for d in karmic lucid maverick natty oneiric precise quantal raring saucy
trusty utopic vivid wily xenial; do
echo "$d: $(wget -q
http://kernel.ubuntu.com/~kernel-ppa/configs/$d/i386-config.flavour.generic -O
- | grep -w CONFIG_IP_PNP)"
done
karmic:
lucid:
maverick:
natty: # CONFIG_IP_
> TJ (tj) wrote 9 hours ago:#26
> Originally introduced into the Ubuntu 13.10 (Saucy) configuration with commit
> 301b4bb
> UBUNTU: rebase to v3.10-rc4
TJ, that doesn't match my tests as mentioned in comment #21,
i.e. that I see the issue since kernel 3.8, and that
https://wiki.ubuntu.com
I think the upstream commit that set CONFIG_IP_PNP=y is this:
https://github.com/torvalds/linux/commit/c1b362e3b4d331a63915b268a33207311a439d60#diff-364c3610ebc6899c22148ba10636c71c
Ubuntu and openSUSE now have CONFIG_IP_PNP=y and experience the issue.
Debian and Fedora do not have CONFIG_IP_PNP s
The problem is not there in Ubuntu 12.04.2 (kernel 3.5.0-54)
and it is there in Ubuntu 12.04.3 (kernel 3.8.0-44).
My test case is to boot with ip=dhcp break=top. When the problem doesn't
exist, I get an initramfs prompt in 2 seconds, when it exists I get it
in 12 seconds, and that shows up in dmes
@rhansen, sorry, it turns out you were right!
ip= is what's causing my kernel delay. I even tried without an initramfs
to verify it, and it caused 10 seconds of delay before the kernel panic
because of the missing initramfs.
I'll try to gather more info about it.
--
You received this bug notifi
@rhansen, your bug might be a different one, since ip=dhcp is processed
by the initramfs, while I'm talking about the kernel, before the
initramfs gets to run.
The bug is still there in Xenial.
I noticed that it doesn't happen in all hardware; I've seen it in *some* real
clients and under Virtual
This is still an issue in Ubuntu 16.04, now initramfs-tools
unconditionally calls `wait-for-root /dev/nbd0 10` without even using
ROOTDELAY.
I also reported this bug to https://github.com/yoe/nbd/issues/36.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
> ... I'll try to raise the issue in Debian's im-config, ... I will ask
that ibus isn't running in locales where it's not needed...
I installed Debian Stretch with the Gnome desktop environment and neither
im-config nor ibus were installed by default there.
So I cannot report it in Debian, as it
Thank you very much Gunnar, the latest PPA changes work as expected for me in
gnome-flashback, i.e. ibus isn't running and I can type Greek just fine.
What you have in the PPA is a good compromise for 16.04, please keep it that
way.
For the future, post 16.04, I'll try to raise the issue in Debi
Hi Gunnar,
> May I ask: Which display language are you using? If it's something
else but Greek, can you please switch to Greek, log out, log in again,
and then try to type in Greek (with IBus running). Does that make a
difference?
I tested with display language = Greek. I haven't tested with disp
> With those changes, im-config (and gnome-language-selector) will
default to IBus in Ubuntu GNOME.
Hi, I've tested the packages from the PPA under Xenial's gnome-flashback, and
now I got ibus running by default.
And it again breaks keyboard layout switching with the default Win+Space, so I
can'
Fix committed in https://launchpad.net/ubuntu/+source/session-
shortcuts/1.1, thank you Dmitry!
** Changed in: session-shortcuts (Ubuntu)
Importance: Undecided => Low
** Changed in: session-shortcuts (Ubuntu)
Status: New => Fix Released
** Changed in: session-shortcuts (Ubuntu)
As
The solution of this bug report,
caused this regression to all other desktop environments except Unity:
https://bugs.launchpad.net/ubuntu/+source/session-shortcuts/+bug/1551670
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
Public bug reported:
Hi, the new logout/reboot/shutdown shortcuts show up in the Applications
→ Accessories menu of Gnome-flashback and other Desktop Environments.
I don't think they make sense there, maybe they should be marked to only
be shown in the Dash/Unity session.
Btw, they're also not t
Since noone filed an SRU and releases <= 15.04 are EOL and it's fixed in 16.04,
I'm marking this as Won't Fix in Ubuntu.
https://wiki.ubuntu.com/StableReleaseUpdates
** Changed in: ltsp (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member
Since 14.04 there are no alternate CD images, so I'm marking the ltsp
(Ubuntu) part of this bug report as Invalid.
** Changed in: ltsp (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
I'm closing the LTSP task as LTSP 5.5.6 got released and was published
in Xenial without the fix being included, and the newer ifupdown makes
the fix not necessary anymore.
** Changed in: ltsp (Ubuntu)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a me
New LTSP/LDM releases can become available for older Ubuntu versions by
following the SRU procedure as described in
https://wiki.ubuntu.com/StableReleaseUpdates.
I'm marking this bug as "Incomplete" so that it expires if noone follows
the SRU procedure, it doesn't make sense to keep bug reports op
Fix released in LTSP 5.5.6.
** Changed in: ltsp (Ubuntu)
Status: Fix Committed => 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/1027085
Title:
issue with SCREEN_07=shell
To man
The LTSP and LDM Xenial packages got updated, so I'm marking this fix
released.
** Changed in: ltsp (Ubuntu)
Importance: Undecided => High
** Changed in: ltsp (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
I'm still seeing this in Ubuntu 16.04 fully updated (2016-02-18) with
gnome-flashback and compiz.
The minimize with alt+space/maximize workaround is still valid.
Hopefully this will be fixed for 16.04!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
This is fixed in Debian, why can't we apply the patch in Ubuntu?
@chrisccoulson, could you please provide some reasoning behind "This isn't
something that we're going to be changing in Ubuntu"?
@bdrung, I have the following xul extensions installed:
xul-ext-adblock-plus 2.7.1+dfsg-1~ubun
Hi Martin,
I reported it here: https://github.com/systemd/systemd/issues/2638
We also need to fix this in the systemd packaging in Debian/Ubuntu:
# grep printf /var/lib/dpkg/info/systemd.postinst
printf "0.0 0 0.0\n0\nLOCAL" > /etc/adjtime
This is similar to https://bugs.debian.org/cgi-
With the switch to configure UTC from /etc/adjtime instead of
/etc/default/rcS, I'm having the following regression:
I've installed Xenial some months ago and it's fully updated.
Without customizing it, my /etc/adjtime reads:
0.0 0 0
0
The regression is this:
# timedatectl set-local-rtc 1
Failed
> Alkis, would be great if you could test with 0.8.8ubuntu2!
I confirm that ifupdown 0.8.8ubuntu2 solves the issue.
I tested both with plain `poweroff` and with `ifdown -a`, which didn't bring
DOWN the "manual" interface.
Thanks a lot Martin!
--
You received this bug notification because you a
Well...
This is *not* needed anymore, i.e. the current bug was solved:
# sed '/^ExecStop=/d' -i /lib/systemd/system/ifup@.service
Unfortunately now this is needed, i.e. the same bug appeared elsewhere:
# sed '/^ExecStop=/d' -i /lib/systemd/system/networking.service
The networking.service file no
> ifupdown should not have a config stanza (or at least only a manual
one) for this.
Hi Martin, yup, when network manager was introduced in Ubuntu I've had added
code to LTSP to dynamically put "iface $DEVICE inet manual" in
/etc/network/interfaces, to prevent network manager from assigning an I
Thank you Martin, I'm attaching journal.txt.
** Attachment added: "journal.txt"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1492546/+attachment/4534902/+files/journal.txt
** Changed in: systemd (Ubuntu)
Status: Incomplete => Triaged
--
You received this bug notification be
Hi Martin, I've set up remote syslogging and I'm attaching the relevant
lines for the "ltsp33" client.
** Attachment added: "syslog"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1492546/+attachment/4534472/+files/syslog
** Changed in: systemd (Ubuntu)
Status: Incomplete => Tr
I believe this was caused by missing environment variables in the session, like
DESKTOP_SESSION, XDG_MENU_PREFIX etc.
I've fixed those upstream in LDM+LTSP and I've released them in the Greek
schools PPA.
Can someone check if adding the PPA to their sources, both in their
server and in the chroo
Hi Robie,
from https://wiki.ubuntu.com/Bugs/Importance => Critical:
> Renders the system temporarily or permanently unusable
Yup, especially if you are on a single core system and you've never heard of
what a terminal or a `kill -9 `is.
> Severely affects applications beyond the package responsi
://wiki.ubuntu.com/StableReleaseUpdates
** Changed in: ltsp (Ubuntu)
Importance: Undecided => Medium
** Changed in: ltsp (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: ltsp (Ubuntu)
Assignee: (unassigned) => Alkis Georgopoulos (alkisg)
--
You received this bug not
Ubuntu 13.10 is EOL, does this still happen with some supported Ubuntu
release?
Also, LTSP can't put such a file in /etc/skel, not all LTSP users are using KDE.
Some other solution should be found instead...
** Changed in: ltsp (Ubuntu)
Status: New => Incomplete
--
You received this bug
Ubuntu 11.10 is now EOL, can you reproduce it with some supported
version?
** Changed in: ltsp (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1156538
Title:
In LTSP upstream, `ltsp-config nbd-server`, which is also called by
`ltsp-update-image`, creates swap.conf if it doesn't exist.
If that still doesn't happen in 12.04, could you create an SRU to have this
backported?
https://wiki.ubuntu.com/StableReleaseUpdates
** Changed in: ltsp (Ubuntu)
Imp
New => Fix Committed
** Changed in: ltsp (Ubuntu)
Assignee: (unassigned) => Alkis Georgopoulos (alkisg)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1027085
Title:
issue with SCREEN_
*** This bug is a duplicate of bug 206924 ***
https://bugs.launchpad.net/bugs/206924
** This bug has been marked a duplicate of bug 206924
Make it possible to create a guest account
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
*** This bug is a duplicate of bug 693151 ***
https://bugs.launchpad.net/bugs/693151
** This bug has been marked a duplicate of bug 693151
Login screen is centered between two monitors with dual head setup
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
Is this still an issue in recent Ubuntu/LTSP versions?
** Changed in: ltsp (Ubuntu)
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/221363
Title:
Policy Kit Unl
Hi, to get this fix backported to previous Ubuntu versions one would need to
follow the SRU process:
https://wiki.ubuntu.com/StableReleaseUpdates
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1387773
Martin, I'm seeing a regression for this with systemd 228-2ubuntu1 in Ubuntu
Xenial.
Now I again have to remove the "ExecStop=/sbin/ifdown %I" stanza in order to
get netbooted clients to shut down.
Maybe something else is stopping the ifup service on shutdown now?
I tried to downgrade to the ver
Hi Shahar Or, unfortunately Ubuntu doesn't accept newer versions of upstream
packages.
It usually only accepts small fixes if one follows the SRU process:
https://wiki.ubuntu.com/StableReleaseUpdates
You might try to change this bug report to an SRU, maybe the Ubuntu
maintainer will accept it.
>
Hi, LDM will be deprecated in LTSP 6, so I don't think anyone's going to work
on this issue.
So I'm marking it "Won't Fix".
** Changed in: ltsp
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
So the problem is that some other package or process renamed update-inetd?
Then this isn't a problem with ldm, is it?
When packages depend on other packages, they can expect their executables to be
present without checking for them...
** Changed in: ldm (Ubuntu)
Status: New => Incomplete
Marc is this still an issue?
** Changed in: ldm (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/867608
Title:
ldm should depend on gettext-base to make trans
*** This bug is a duplicate of bug 693151 ***
https://bugs.launchpad.net/bugs/693151
** This bug has been marked a duplicate of bug 693151
Login screen is centered between two monitors with dual head setup
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
** No longer affects: ldm (Ubuntu)
** Changed in: ltsp
Status: New => Incomplete
** Changed in: ltsp
Assignee: (unassigned) => Alkis Georgopoulos (alkisg)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
Fix released in LDM 2.2.16.
** Changed in: ltsp (Ubuntu)
Status: Fix Committed => 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/1457730
Title:
Upstart packaging conflicts with m
Fix released in LDM 2.2.15.
** Changed in: ltsp
Status: Fix Committed => 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/1316320
Title:
Screen Lock does not prompt for password
T
Fix released in LTSP 5.5.4.
** Changed in: ltsp
Status: Fix Committed => 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/1020113
Title:
ltsp: screen session "ssh" not working in p
Public bug reported:
Freshly installed Xenial daily build.
I reported the issue in the gnome-flashback mailing list, and Alberts replied:
> Upstream network-manager-applet does not autostart applet in GNOME any more:
> https://git.gnome.org/browse/network-manager-applet/commit/?id=2a7336451cb6f06
Lefteris, could you add the upstream patch here and follow all the SRU
steps? Thank you!
** Changed in: socat (Ubuntu)
Importance: Undecided => Critical
** Changed in: socat (Ubuntu)
Status: New => Confirmed
** Bug watch added: Debian Bug tracker #803378
http://bugs.debian.org/cgi-b
*** This bug is a duplicate of bug 158 ***
https://bugs.launchpad.net/bugs/158
Hi, as the bug title says, it's a problem with socat, not with epoptes.
We cannot solve it in the epoptes code.
We've had reported it in https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=803378, you can co
Hi, LTSP in Ubuntu has been broken for some years now, it's lacking a
lot of necessary fixes that are upstream in LTSP.
Use the Greek schools PPA to get a working LTSP:
sudo add-apt-repository --yes ppa:ts.sch.gr
sudo apt-get update
sudo apt-get dist-upgrade
...both in your server and your chroot
** Also affects: ltsp (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1506756
Title:
LTSP-pnp 14.04-1 clients don't boot correctly - black screen
Public bug reported:
$ tail -1 /etc/update-manager/release-upgrades
Prompt=never # Original value: Prompt=lts
I'm using inline comments like the one above to mark the original values in
files that I change in /etc.
But in this case it's considered an invalid value, probably like:
Prompt="never #
Thank you Dmitry. :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1502570
Title:
gnome-panel indirectly installs evolution
To manage notifications about this bug go to:
https://bugs.launchpad.net/
Since the code that breaks XDG_DATA_DIRS is in LXDE, LTSP can't fix it without
directly patching startlxde.
This can not be done in a non-intrusive way for thin clients as it requires
breaking the server installation (wrong debsums etc).
I'm marking this as won't fix, please file the bug report
1) It works fine for me with no regressions at all, thank you very much.
2) I just noticed that contrary to what I wrote in the bug title, ibus also
breaks Unity, but only a little, so I hadn't noticed before.
It eats up the accent but only the first time that the user tries it. I.e.
";" + "a" =
Because then we would lose all the other recommended packages:
http://packages.ubuntu.com/wily/gnome-panel
alacarteeasy GNOME menu editing tool
evolution-data-serverevolution database backend server
gnome-appletsVarious applets for the GNOME panel - binary files
gnome-session-flashb
Would it be at all possible to have this in Wily?
We're thinking of installing 15.10 in some schools here instead of 14.04, and
it would make things a bit easier for us.
Thank you very much in any case.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
Hi Robie,
while this also happens in Debian, the use case is more common in Ubuntu,
because NetworkManager is patched to use a spawned dnsmasq instance as a local
resolver, and mixing the two DNS servers is problematic (neither bind-dynamic
nor bind-interfaces work very well).
In Debian they mo
Thanks a lot Martin, works fine for me.
/me reverts the LTSP workaround...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1492546
Title:
Systemd runs ifdown on shutdown even when it shouldn't
To man
Hi Gunnar,
that patch works lovely for me, I tried it in Wily beta 2 + updates in:
gnome-flashback-metacity (running ibus)
mate-desktop (running fcitx)
lubuntu (running fcitx)
...and it prohibited ibus and fcitx from running, solving the keyboard layout
switching problems that they were causing (
> How can you tell that im-config shouldn't start IBus?
Isn't that why system settings vs user settings exist?
For example, my /etc/default/keyboard reads:
XKBLAYOUT="us,gr"
XKBOPTIONS="grp:alt_shift_toggle,grp_led:scroll"
Then for example Gnome puts those as the default layouts for my session.
Gunnar, one of the 3 problems here is that im-config starts ibus while it
shouldn't.
We Greeks have no need for ibus, and
IM_CONFIG_DEFAULT_MODE=auto
should understand that and act accordingly like im-switch did in the past.
In the past I've exchanged some emails with Osamu, the im-config Debi
** Also affects: im-config (Ubuntu)
Importance: Undecided
Status: New
** Also affects: ibus (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
The problem seems to be some incompatibility between ibus and gnome-flashback.
ibus doesn't cause problems in Unity but it does cause this problem in
flashback.
A workaround for gnome-flashback would be to conflict with ibus until
this is solved.
A workaround for users: in/etc/default/im-config,
301 - 400 of 1335 matches
Mail list logo
