Public bug reported:
http://packages.ubuntu.com/wily/gnome-panel
gnome-panel Recommends: evolution-common
...which in turn Recommends: evolution
Is this on purpose?
Could you please lower the "Recommends" to "Suggests"?
Gnome-flashback isn't a flavor with a live CD etc, so it makes more sense to
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:
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
** 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.
> 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.
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
Better regex to avoid a possibly commented #port=0:
grep -qr "^[[:space:]]*port=0" /etc/dnsmasq.d/ /etc/dnsmasq.conf && return
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
Better regex to avoid a possibly commented #port=0:
grep -qr "^[[:space:]]*port=0" /etc/dnsmasq.d/ /etc/dnsmasq.conf && return
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1501189
Title:
Don't
Public bug reported:
The following function is defined in /etc/init.d/dnsmasq:
start_resolvconf()
{
# If interface "lo" is explicitly disabled in /etc/default/dnsmasq
# Then dnsmasq won't be providing local DNS, so don't add it to
# the resolvconf server set.
for interface in
Public bug reported:
The following function is defined in /etc/init.d/dnsmasq:
start_resolvconf()
{
# If interface "lo" is explicitly disabled in /etc/default/dnsmasq
# Then dnsmasq won't be providing local DNS, so don't add it to
# the resolvconf server set.
for interface in
** Attachment added: "Xorg.7.log"
https://bugs.launchpad.net/ubuntu/+source/xorg-lts-trusty/+bug/1298846/+attachment/4471940/+files/Xorg.7.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1298846
This bug still exists in a supported release, namely 12.04.5, with the
trusty backported xorg stack.
# lspci -nn -k | grep -A 2 VGA
00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc.
[AMD/ATI] Kabini [Radeon HD 8400] [1002:9830]
Subsystem: ASUSTeK Computer Inc.
Here's my version of the workaround, it patches all the nppdf files only if
they match the broken md5sum.
Just copy/paste all of it in a single line in a terminal and enter your
password when prompted by the sudo command.
find /usr /opt -name '*nppdf*' | xargs md5sum | while read sum file; do
Public bug reported:
Ubuntu 14.04.3, software-properties-gtk 0.92.37.3
If I have this in my sources.list.d/some-source.list:
deb http://ppa.launchpad.net/ts.sch.gr/ppa/ubuntu trusty main #My repository
Then "main" does not appear in the list box in the software-properties-gtk
dialog → Other
Fix committed in http://bazaar.launchpad.net/~ltsp-upstream/ltsp/ltsp-
trunk/revision/2666
Thanks for the patch!
** No longer affects: ltsp (Ubuntu)
** Changed in: ltsp
Status: New => Fix Committed
** Changed in: ltsp
Assignee: (unassigned) => Andy Igoshin (andy-igoshin)
--
You
Public bug reported:
The unit /lib/systemd/system/ifup@.service is Debian and Ubuntu specific, it's
not part of upstream systemd.
On shutdown, it unconditionally ifdowns all interfaces:
ExecStop=/sbin/ifdown %I
This is a regression from previous init systems (sysvinit and upstart)
which cared
This also affects LTSP, e.g. Wily clients can't shutdown because
/sbin/poweroff is no longer accessible once ifup@.service unmounts
/dev/nbd0.
If systemd is fixed in Ubuntu before 15.10 is released, problem solved,
otherwise we'll need to commit the following in upstream LTSP.
Script
AFAIK, you can see the `exec /bin/sh -` running on the server if you run `ps`
there.
The "gnome-keyring is not unlocked" part is due to LDM not using PAM to unlock
the keyring, like lightdm does.
So I'm marking this as Invalid, please reopen it if my rationale was
wrong.
** No longer affects:
@costamagnagianfranco, a new lts kernel exists in trusty
(linux-image-generic-lts-vivid 3.19.0.26.13),
and this is the launchpad bug report that apport directs us to when trying to
upload the crash,
so I'm reopening it, if you think it should be closed and another one should be
opened, please
The problem still exists in 15.10 daily build.
** Changed in: console-setup (Ubuntu)
Status: Fix Released = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/133072
Title:
tty console
Public bug reported:
This affects all Ubuntu CDs and installations after 14.10.
The VTs are not configured to show UTF-8 characters because of a wrong
CHARMAP value at /etc/default/console-setup (ISO-8859-15 instead of
UTF-8).
The cause most probably is that recent console-setup.postinst
I think this should be fixed in console-setup, but it's possible that
the live CD code may want to use LANG=C.UTF-8 in any case.
...I put livecd-rootfs in the affects list, please use LANG=en_US.UTF-8
instead of LANG=C and LC_ALL=C.
$ egrep -r 'LANG=|LC_ALL=' .
./debian/changelog: * Minor
If I change the layout switching combination
from the default ['Superspace']
to something else like e.g. ['Super1'],
then it does work fine.
Maybe Super+Space is intercepted somewhere else?
I think I saw a commit a few months ago about intercepting some
modifiers in the WM, maybe that's what
Public bug reported:
My keyboard layout is us,gr, and the new Gnome way to switch between them is
by pressing Super+Space.
This works fine in:
* Gnome-Flashback (Metacity) 14.04
* Unity 14.04
* Unity 15.10
It doesn't work in:
* Gnome-Flashback (Metacity) 15.10
I've tested with the 15.10
I've verified that x11-utils 7.6+4ubuntu0.2 works as expected in Ubuntu
12.04.1, please push it to precise-updates.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
in: ltsp (Ubuntu)
Status: Triaged = Fix Released
** Changed in: ltsp (Ubuntu)
Assignee: Stéphane Graber (stgraber) = 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
Jaunty is EOL, closing this bug report.
** Changed in: nbd (Ubuntu)
Status: Confirmed = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/381766
Title:
nbd-server no config file
To
Jaunty is EOL, closing this bug report.
** Changed in: nbd (Ubuntu)
Status: Confirmed = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nbd in Ubuntu.
https://bugs.launchpad.net/bugs/381766
Title:
nbd-server no
Public bug reported:
[Impact]
Xprop added support for UTF8_STRING back in 2009:
http://cgit.freedesktop.org/xorg/app/xprop/commit/?id=eb64005382abf6262c913a46e6186e019a179d59
Unfortunately `xprop -f 8u -set` has been broken until 2012:
** Also affects: ltsp (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ltsp (Ubuntu)
Importance: Undecided = High
** Changed in: ltsp (Ubuntu)
Status: New = Fix Committed
** Changed in: ltsp (Ubuntu)
Assignee: (unassigned) = Alkis Georgopoulos (alkisg)
--
You
To work around the issue from the LTSP side, I pushed the following changes:
http://bazaar.launchpad.net/~ltsp-upstream/ltsp/ldm-trunk/revision/1577
http://bazaar.launchpad.net/~ltsp-upstream/ltsp/ltsp-trunk/revision/2646
Anyone interested in getting Unity to work with LTSP in Ubuntu 14.04 should
Package: ldm (not installed)
You're not using LDM, maybe you wanted to file that against LightDM?
It sounds more like a xorg issue though, if it still happens for you in a
recent version of ubuntu, file it again.
** Changed in: ldm (Ubuntu)
Status: New = Invalid
--
You received this
If someone still has this issue, what's the output of this command?
sudo ltsp-info
LDM_SESSION=gnome-fallback is the correct lts.conf entry.
** Changed in: ldm (Ubuntu)
Status: Confirmed = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
The no tray issue was fix-committed in
https://bugs.launchpad.net/ubuntu/+source/ltsp/+bug/1457730
The no lock screen issue was fix-committed with LDM_PASSWORD_HASH.
** Changed in: ltsp
Status: Triaged = Fix Committed
--
You received this bug notification because you are a member of
I tried with a 16bit thin client on 14.04 and it worked fine, both with
the Unity and the gnome-flashback session, so marking the bug as fix
released.
** Changed in: compiz
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I tried with a 16bit thin client on 14.04 and it worked fine, both with
the Unity and the gnome-flashback session, so marking the bug as fix
released.
** Changed in: compiz (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Public bug reported:
Ubuntu 14.04, upstart 1.12.1-0ubuntu4.2.
man Xsession:
Xsession may optionally be passed a single argument indicating the type of X
session to be started.
default produces the same behavior as if no session type argument had been
given at all.
In
*** This bug is a duplicate of bug 1349474 ***
https://bugs.launchpad.net/bugs/1349474
** This bug has been marked a duplicate of bug 1349474
ltsp: jetpipe can not start
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I've had success with:
Ubuntu 14.04.2 64bit
Lexmark S305
lexmark-inkjet-legacy 1.0-1
I played a lot before I got it to work, but I think that in the end only 2
changes were needed,
...a mode change in:
-rwxr-xr-x 1 root root 144K Aug 16 2012 /usr/local/lexmark/v3/bin/printfilter
...and in
It also worked fine in Ubuntu 12.04 32bit, and the printfilter mode
changing wasn't needed, it's possibly not used at all with the lxusb
backend.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/902535
I tested my patch from #3 and it does work, but I don't have access to
commit it because it's in the Ubuntu packaging and not in the upstream
code.
Both /etc/X11/Xsession.d/40-ltsp-server and
/opt/ltsp/i386/etc/X11/Xsession.d/40-ltsp-client need to have that one line
changed.
So the result
I'm verifying that it works for Precise.
Steps I did:
I downloaded http://releases.ubuntu.com/12.04/ubuntu-12.04.4-desktop-amd64.iso.
This has linux-signed-generic-lts-saucy installed.
I updated to the latest update-manager version in -updates:
# apt-get update
# apt-get install update-manager
Verifying for precise.
I fully updated all the meta packages. And I also removed all the old meta
packages.
I only kept a couple of old kernels around.
Then, the previous update-manager-core version produced an empty apt line,
while the newer one didn't.
Exact output:
# dpkg-query -W
I too verify that 1:0.156.14.18 in precise-updates fixes the issue, it
doesn't prompt for ltsp-client and ltspfsd removal anymore.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1415785
Title:
Some additional information:
If I remove the update-manager package, then hwe-support-status 1:0.156.14.18
gives an apt-get line without requiring the --show-replacements parameter.
The exact output is:
Your current Hardware Enablement Stack (HWE) is no longer supported
since 2014-08-07.
** Tags added: patch
** Changed in: update-manager (Ubuntu)
Importance: Undecided = High
** Changed in: update-manager (Ubuntu)
Assignee: (unassigned) = Michael Vogt (mvo)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
- Please remove all references to the ltsp-client, ltsp-client-core,
- ltspfs, and ltspfsd packages from the update-manager sources, as update-
- manager currently removes those packages on dist-upgrades.
-
- Please also SRU this to 12.04 and 14.04, I've seen dozens of
I won't reopen it because it's not exactly the same issue, but since it was one
of the first google hits for my problem, I'll note here that I too got the
message:
/usr/sbin/grub-probe: warning: Couldn't find physical volume `(null)'. Some
modules may be missing from core image..
...and,
Public bug reported:
Please remove all references to the ltsp-client, ltsp-client-core,
ltspfs, and ltspfsd packages from the update-manager sources, as update-
manager currently removes those packages on dist-upgrades.
Please also SRU this to 12.04 and 14.04, I've seen dozens of LTSP
** Attachment added: update-manager-removes-ltsp.png
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1415785/+attachment/4307780/+files/update-manager-removes-ltsp.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
A quick how-to for those seeking to enable remote logging for ltsp
clients in Ubuntu.
1) Uncomment the following lines in /etc/rsyslog.conf:
# provides UDP syslog reception
$ModLoad imudp
$UDPServerRun 514
2) Restart rsyslog:
sudo service rsyslog restart
3) Set the following line in lts.conf:
AFAIK, the showexec mount parameter that you're already using handles
the executable files just fine, and it won't be affected by the dmask
change.
Output from a patched udisks2 with dmask dropped:
alkisg@pc ~ $ grep vfat /proc/self/mountinfo
35 22 8:33 / /media/alkisg/usbstick
** Changed in: linux (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/345374
Title:
Silicon Integrated Systems [SiS] 191 Gigabit Ethernet
To manage
Quotting pitti from comment #2:
We won't change the behaviour in udisks, there needs to be some default after
all.
Please completely remove dmask from the vfat/ntfs mount options, like fmask
already is (absent).
Patch available at LP #482501.
I assume that dmask=0077 was added at some point
*** This bug is a duplicate of bug 453605 ***
https://bugs.launchpad.net/bugs/453605
** This bug has been marked a duplicate of bug 453605
Make default mount umasks configurable
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 453605 ***
https://bugs.launchpad.net/bugs/453605
** Also affects: udisks (Ubuntu)
Importance: Undecided
Status: New
** Also affects: udisks2 (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: nautilus (Ubuntu)
** This
P.S. completely removing dmask from the mount options and letting
/media/username cover the permission issues,
couples well with UDISKS_FILESYSTEM_SHARED,
so that people that want USB drives to be shared across users,
can just specify UDISKS_FILESYSTEM_SHARED=1 in udev for those drives.
Then
This is fixed in five-or-more 1:3.12.1-1, but it still affects the
current LTS release, 14.04, which has version 1:3.8.2-1.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1330956
Title:
high score
I think that 40-ltsp-server and 40-ltsp-client should be deleted, and
DESKTOP_SESSION should be set from X50-dmrc-processing in CLIENT_ENV,
since that's the script that parses the xsession files and so it can
output DESKTOP_SESSION with no additional overhead.
--
You received this bug
Can you test if this solves the problem?
Replace:
DESKTOP_SESSION=$(echo $1 | sed s/gnome-session --session=//g
With:
DESKTOP_SESSION=$(grep -l ^Exec=$1\$ /usr/share/xsessions/*.desktop
2/dev/null | sed -n '1 s,.*/\(.*\)\.desktop,\1,p')
--
You received this bug notification because you
*** This bug is a duplicate of bug 1321922 ***
https://bugs.launchpad.net/bugs/1321922
** This bug has been marked a duplicate of bug 1321922
gnome-keyring-daemon failing of sshfs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Yes it's still happening on 3.13.0-29-generic.
[3.912539] random: nonblocking pool is initialized
[ 19.999335] Adding 3957756k swap on /dev/sda7. Priority:-1 extents:1
across:3957756k FS
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
** Tags removed:
LDM uses `ssh user@server` to authenticate users.
It then copies the user /etc/passwd information from the server to the client,
but it doesn't copy the /etc/shadow part, i.e. the user password hash.
So fat client and localapps users do not have a password set, and thus
cannot use `sudo`, cannot
** Changed in: ltsp
Status: New = Triaged
--
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
To manage notifications about this bug go to:
The panel part might be because gnome-settings-daemon gets loaded before
unity-settings-daemon, and thus unity-panel-service doesn't start at all.
Try manually running /usr/lib/unity/unity-panel-service, if then the panel
applets get loaded, yeah file a separate bug against Unity*.
I don't know
I think the problem is the missing ID_FS_TYPE in udev for nbd devices,
and that it's also reported more properly there:
https://bugs.freedesktop.org/show_bug.cgi?id=62565
Maybe wait-for-root could find some better workaround when ID_FS_TYPE is
unset though, e.g. checking the output of `blkid`...
Input from upstream:
(12:17:39 μμ) rtcm: alkisg: yeah, mutter resolves the ISO_Next_Group keysym to
keycodes and installs passive grabs for all those keycodes
(12:21:00 μμ) rtcm: alkisg: so yeah, compiz would need something like
I think the problem is the missing ID_FS_TYPE in udev for nbd devices,
and that it's also reported more properly there:
https://bugs.freedesktop.org/show_bug.cgi?id=62565
Maybe wait-for-root could find some better workaround when ID_FS_TYPE is
unset though, e.g. checking the output of `blkid`...
Public bug reported:
unity-settings-daemon = gsd-keyboard-manager.c has an Ubuntu specific patch
that strips the grp: part in XKB options:
if (n_sources 2 || g_strcmp0 (g_getenv (XDG_CURRENT_DESKTOP),
Unity) == 0)
strip_xkb_option (options, grp:);
The original upstream
Yes, it's still an issue in Trusty.
Also please use Incomplete, not Invalid when you need feedback from a bug
reporter.
root@ltsp241:~# blkid
/dev/nbd0: TYPE=squashfs
/dev/nbd1: UUID=d7bfcbc8-9718-46f9-b9e3-daf9e46f596a TYPE=swap
/dev/sr0: LABEL=Ubuntu 10.04.3 LTS i386 TYPE=iso9660
Hmmm, maybe this is an easier way to reproduce something similar without
using NBD at all:
wait-for-root /dev/sr0 1
succeeds in a booted system,
but fails from the initramfs if one adds break=bottom in the kernel command
line.
It succeeds in both cases for e.g. /dev/sda1.
--
You received
Yes, it's still an issue in Trusty.
Also please use Incomplete, not Invalid when you need feedback from a bug
reporter.
root@ltsp241:~# blkid
/dev/nbd0: TYPE=squashfs
/dev/nbd1: UUID=d7bfcbc8-9718-46f9-b9e3-daf9e46f596a TYPE=swap
/dev/sr0: LABEL=Ubuntu 10.04.3 LTS i386 TYPE=iso9660
Hmmm, maybe this is an easier way to reproduce something similar without
using NBD at all:
wait-for-root /dev/sr0 1
succeeds in a booted system,
but fails from the initramfs if one adds break=bottom in the kernel command
line.
It succeeds in both cases for e.g. /dev/sda1.
--
You received
@seb128: it's still an issue in Trusty + gnome-flashback + metacity,
which is the default environment for Edubuntu/LTSP (netbooted clients).
** Changed in: unity-settings-daemon (Ubuntu)
Importance: Low = High
** Changed in: unity-settings-daemon (Ubuntu)
Status: Incomplete = Confirmed
No, it's not an issue anymore in 14.04, so Wouter must have fixed it.
Marking as fix released.
** Changed in: nbd (Ubuntu)
Status: Incomplete = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nbd in Ubuntu.
No, it's not an issue anymore in 14.04, so Wouter must have fixed it.
Marking as fix released.
** Changed in: nbd (Ubuntu)
Status: Incomplete = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I uninstalled ibus and I still had the problem.
I think the Win+Space shortcut to change layouts is handled by
gnome-settings-daemon, so I've put it in the Affects list.
I also think it's a bad idea to have a DE-specific way to change
keyboard layouts, because then we'd need to press e.g.
As Dmitry mentioned in bug 1241284, the layout change is monitored by
some *daemon. It used to be monitored by gnome-settings-daemon, and now
it's monitored by unity*? Dunno I'm not using unity, but I've put gnome-
settings-daemon in the Affects list.
Was the code that we're looking for in
** Also affects: indicator-keyboard
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.
I have the same problem.
My keyboard combination to switch layouts is Super+space. If I do:
1) Press Super
2) Press Space
3) Release Super
4) Release Space
...the keyboard layout isn't changed, the steps (3) and (4) need to
happen in the opposite order for the layout to be changed.
So people
By old-style you mean XKB? And new-style is IBus?
IBus is too buggy, keyboard layout switching only works if one types slowly
(LP: #1241284), and sometimes it doesn't work at all, and sometimes the
indicator doesn't get updated even if you use the new-style switching, and it
needs 40+ MB RAM
I think there's another bug involved here.
nm-applet is now always launched in my gnome-fallback session, nice.
But I don't always see it in the systray, it's intermittent.
E.g. I reboot with autologin enabled, and I don't see the applet.
The nm-applet process is there though.
Then I logoff /
OK Dmitry and thank you for trying it,
but in my opinion if the ibus keyboard indicator is shown twice, that's an ibus
bug and not a gnome-panel bug,
and it should be solved by making that setting default to false:
$ grep systray /etc/dconf/db/ibus.d/00-upstream-settings
I manually applied the patch and nm-applet now works fine.
Please commit/release it. :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1267100
Title:
nm-applet is no longer launched at startup on
That said, if nm-applet and pidgin get fixed for 14.04, notification-
area isn't that important anymore...
I tried manually applying the patch for nm-applet, it works fine.
Pidgin works fine too, after playing a bit with its settings.
So yup notification-area isn't that important anymore.
@penalvch: as I mention in comment #6, the kernel-fixed-upstream tag
is not appropriate because this was never an upstream bug, so nothing
was fixed upstream. It's an ubuntu-specific bug, so upstream is not
related at all to this bug and shouldn't appear in any tags.
The needs-kernel-logs tag
I think anyone can just run `dmesg` and verify that the bug exists in all
recent Ubuntu kernels and in none of the vanilla or Debian kernels.
I don't know why the logs are important here.
I don't think there's any point in closing bugs just to lower the bug count
(which means nothing if the bugs
@penlalvch: I was asked in #ubuntu-kernel to file this bug report so
that they can assign someone to work on it.
If you keep adding it needs this and that tags, then this bug report
appears to be incomplete, and no developer will start working on it
until I satisfy/remove the tags.
But as I keep
@Alkis: I think there is a typo in Ubuntu's patch.
Can you stop nautilus (nautilus -n) and then try to launch it with:
$ env XDG_CURRENT_DESKTOP=GNOMEF nautilus
For some reason `nautilus -n` didn't do it, but `killall nautilus;
nautilus` did the trick.
I.e. after the `killall nautilus`
With gnome-flashback, I did the following change:
$ grep DesktopName /usr/share/xsessions/gnome-fallback.desktop
X-LightDM-DesktopName=FGNOME
Logout/login, my environment now is:
DESKTOP_SESSION=gnome-fallback
SESSIONTYPE=gnome-session
XDG_CURRENT_DESKTOP=FGNOME
And, nautilus 1:3.10.1-0ubuntu2
Thanks a lot for the feedback, I'm marking it as Won't Fix then.
Some notes:
1) nm-applet integration has issues, it doesn't display the applet for me on
gnome-flashback without manually adding notification-area. I also tried with a
recent 14.04 live CD, some times nm-applet did appear and some
Mathieu, I reopened this bug because it was never resolved... not just for the
TFTP issue.
Please see my #143 comment.
If you want more feedback tell me what to send, but DNS never worked properly
for me when dnsmasq and nm-dnsmasq are both running.
--
You received this bug notification
Mathieu, I reopened this bug because it was never resolved... not just for the
TFTP issue.
Please see my #143 comment.
If you want more feedback tell me what to send, but DNS never worked properly
for me when dnsmasq and nm-dnsmasq are both running.
--
You received this bug notification
Please boot without that parameter, get a local shell (e.g. with
SCREEN_02=shell in lts.conf), and run these:
lspci -nn -k | grep -A 2 VGA
dpkg -l '*nvidia*' | grep ^ii
...and attach the output here.
plymouth:force-splash will go away in 14.04, but it'd be nice to see
exactly which cases were
Can you try replacing /usr/share/ltsp/nbd-disconnect in the chroot, with this
file?
http://bazaar.launchpad.net/~ltsp-upstream/ltsp/ltsp-trunk/view/head:/client/share/ltsp/nbd-disconnect
Then run ltsp-update-image, reboot client, and see if it fixes things.
** Changed in: ltsp (Ubuntu)
Hi Christopher, as mentioned in my other kernel related bug reports I
just didn't know that launchpad wasn't the appropriate place to report
kernel bugs. So for some of my bug reports I provided feedback for 3-4
years and the only result I got was the occasional can we close it
now? answer.
I'll
*** This bug is a duplicate of bug 994575 ***
https://bugs.launchpad.net/bugs/994575
Thomas thank, this appears to be working fine with resolvconf
1.69ubuntu1 on Trusty, so I'm marking it as a duplicate of the bug you
referenced.
** This bug has been marked a duplicate of bug 994575
Since Ubuntu switched to logind, I don't think this is ever going to get
fixed.
** Changed in: consolekit (Ubuntu)
Status: New = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/535521
** Changed in: baltix
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/503919
Title:
Translations missing in tuxpaint-data Ubuntu 10.04 package
To manage notifications
That was fixed upstream at some point, it only checks for *sh now.
** Changed in: plymouth (Ubuntu)
Status: New = 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/930865
Title:
401 - 500 of 1390 matches
Mail list logo
