Public bug reported:
= Problem =
It is too easy to make a system unusable.
= Examples
The following commands will all cause subsequent graphical logins to
fail:
== User is returned to login screen ==
- chmod 400 ~/.ICEauthority
- rm ~/.ICEauthority
In this scenario, the user is returned to
** Package changed: upstart (Ubuntu) = chromium-browser (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1300235
Title:
init (chromium-browser) crashed with SIGSEGV
The oldest of the two unity8 proceses (pid 2640) has been SIGSTOP'ed.
Since unity8 uses SIGSTOP to indicate to upstart that it is ready, this
suggests that when lightdm died, the session init was killed somehow
before unity8 was ready (either on first start or respawn).
--
You received this bug
Daniel - please can you attach the existing /var/crash/_sbin_init* to
this bug. I appreciate they do not represent the current issue, but if
may have been a re-occurence of the problem which did generated the
crash files so I'd like to see those anyway.
--
You received this bug notification
The most appropriate way to do this would probably be to use apport to
check for respawn limit messages in:
- the system log, and
- the users $HOME/.xsession-errors file.
Even at the default upstart log priority of 'message', when a job
reaches the respawn limit, upstart will log a message to
@elfy - is plymouth is still crashing for you?
$ sudo grep SEGV /var/log/syslog
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1371651
Title:
Daily does not boot into graphical
As discussed on irc, the problem seemed to be that the plymouth-ready
event was not being emitted since udev was not tagging a graphics device
with PRIMARY_DEVICE_FOR_DISPLAY, so it looked like the problem was
udev/kernel related.
According to jibel, if he enters the grub boot menu lightdm will
I have now recreated using utopic-desktop-amd64.iso (20140923) and
http://people.canonical.com/~jhunt/upstart/conf/rebooter.conf to force
continuous reboots.
It appears that the problem only occurs if quiet splash is specified
since I ran 25 boots without those options and was unable to recreate
Note also that I do have PRIMARY_DEVICE_FOR_DISPLAY=1 in /var/log/udev.
Recreation is under kvm.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1371651
Title:
Daily does not boot
It's looking like either quiet or more likely splash is the
triggering factor here.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1371651
Title:
Daily does not boot into graphical
After removing both 'quiet' and 'splash' options from
GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub, and running 'sudo
update-grub', I am no longer able to recreate the bug (over 100 boots on
a 64-bit kvm instance using utopic-desktop-amd64.iso (20140923)).
@elfy: can you provide details on how
205 boots and no problem with the 2 options removed.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1371651
Title:
Daily does not boot into graphical interface after installation
@arges: can you try reproducing without quiet splash as that seems to
be the best lead we have so far.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1371651
Title:
Daily does not
This sounds like a unity issue as I've seen no evidence of Upstart
misbehaving yet. That .xsession-errors log would be useful to have if
you can attach it though.
** Also affects: unity (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a
** Changed in: upstart
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dp-unity
https://bugs.launchpad.net/bugs/1235649
Title:
uevent spam causes libdbus
Yes, I confirm that the issue is resolved with 3.13.4.2-0ubuntu1.
Not relevant to this bug, but I do notice that the scan speed is quit
slow using simple-scan. Comparing with xsane at the same resolution
(300dpi):
- xsane: 23 seconds
- simple-scan: 2 minutes.
Thanks very much for the fast
Hi Robert,
Sorry to be vague, but I don't actually scan much so the last time I
recall doing it I was running trusty.
Yes, the proprietary brother drivers are required for wireless scanning
AIUI.
$ dpkg -l | grep brscan
ii brscan-skey 0.2.4-1
'ltrace -o /tmp/bug-1344869-ltrace-xsane.log -s 1024 -fl libsane.so.1
xsane' log from a successful wireless scan using xsane.
** Attachment added: ltrace -o /tmp/bug-1344869-ltrace-xsane.log -s 1024 -fl
libsane.so.1 xsane
*** This bug is a security vulnerability ***
Public security bug reported:
When my machine comes out of suspend, I am shown the lightdm greeter.
However, occasionally I am unable to enter my password since the
password box is not given focus. Clicking with the mouse in the password
box also
Public bug reported:
Attempting to scan via wifi from a Brother MFC-7860 DW fails; the
scanner shows scanning but:
- no image appears in simple-scan.
- simple-scan consumes 100% CPU
- the ~/.cache/simple-scan/simple-scan.log grows indefinately until disk space
is exhausted.
This used to work
When simple-scan is spinning, the following entry is added to the log
repeatedly until ENOSPC:
[+15,29s] DEBUG: scanner.vala:1310: sane_read (0) - (SANE_STATUS_GOOD,
0)
Further details:
$ cat /proc/$(pidof simple-scan)/stack
** Attachment added: strace snapshot of simple-scan consuming 100% CPU
https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1344869/+attachment/4156869/+files/bug-1344869-strace.txt.gz
--
You received this bug notification because you are a member of Desktop
Packages, which is
Interestingly, the problem is also seen if chromium is restarted and one
of the tabs is http://translate.google.com - closing that tab resolves
the cpu usage issue, and subsequently opening a new tab and going to
http://translate.google.com does *not* manifest the problem.
--
You received this
This happens every time the user attempts to access the unity settings.
Running from the command-line:
$ gnome-control-center
(unity-control-center:6424): Gtk-CRITICAL **:
gtk_radio_button_set_group: assertion '!g_slist_find (group,
radio_button)' failed
(unity-control-center:6424):
Yes.
** Changed in: vorbis-tools (Ubuntu)
Status: Incomplete = New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to vorbis-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1334204
Title:
ogg123 crashes after playing sound file
Public bug reported:
$ gdb --args `which ogg123` redalert.ogg
GNU gdb (Ubuntu 7.7.1-0ubuntu3) 7.7.1
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
Public bug reported:
Running the following as part of an lxc unprivileged container setup
(see [1]) used to work fine:
pactl load-module module-native-protocol-unix auth-anonymous=1
socket=$PULSE_PATH
However, as of today, this fails. Looking in syslog I see:
Public bug reported:
This happens frequently (I have a script that monitors CPU usage).
$ top -b -n1 | head
top - 07:44:06 up 30 min, 3 users, load average: 1.35, 1.08, 0.82
Tasks: 329 total, 2 running, 327 sleeping, 0 stopped, 0 zombie
%Cpu(s): 17.4 us, 1.6 sy, 0.4 ni, 80.1 id, 0.5
Looks like this might be being caused by flashplugin. After closing a
few tabs the problem is no longer recreatable.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1321602
After performing a few tests, the problem seems to be that if a tab
using youtube's html5 player exists at browser start, chromium will spin
@ 100% cpu. Closing that tab makes the cpu usage drop to normal levels.
What is odd is that if no youtube html5 tab exists at startup and I then
create a
Public bug reported:
Occasionally my Lenovo t440s starts to make a constant crackling /
humming sound. This doesn't stop sound from being played, but if no
sound is playing, the noise persists.
As it's a new laptop, I thought it might be a hardware issue. It almost
sounds like a bad earth
Note that the noise is heard when the laptop is connected on AC and on
battery alone.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1315281
Title:
skype occasionally makes
diwic has identified the problem to be skype rather than pulse itself.
** Package changed: pulseaudio (Ubuntu) = skype (Ubuntu)
** Summary changed:
- pulseaudio occasionally makes constant crackling / humming sound until killed
+ skype occasionally makes constant crackling / humming sound until
Problem persists with all peripherals unplugged.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1315281
Title:
skype occasionally makes constant crackling / humming sound until
Sounds like bug 861268.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu.
https://bugs.launchpad.net/bugs/1311488
Title:
Missing letters
Status in “nvidia-graphics-drivers-304” package in Ubuntu:
Public bug reported:
Moving a window to another workspace using the context menu options
Move to Workspace right or Move to Another Workspace causes unity to
lose track of the window entirely - it disappears never to return.
Note: the processes associated with the windows *are* still running as
Public bug reported:
When a VPN connection has been created, a notification appears stating:
VPN Login Message
VPN connection has been successfully established.
However, the converse is not true; disconnecting from the VPN does not
result in a message like this:
VPN Logout Message
To be clear, I am suggesting we have a notification appear when the user
manually disconnects the VPN at the point the connection is brought
down.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-applet in Ubuntu.
Thank you for reporting this bug. However, please do not report the same
bug three times :-)
** Package changed: upstart (Ubuntu) = gnome-session (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
Public bug reported:
(Long) Pressing the super (aka windows) key displays the Keyboard
Shortcuts overlay. However, this summary does not show that Super+L is
now a shortcut for locking the screen.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity 7.1.2+14.04.20140303-0ubuntu1
I don't know if the padlock is actually being overlayed onto the
existing connection-type image, but I'd prefer to see an icon like the
attached. In other words, invert the 2 arrows for a wired connection and
make the right-hand arrow stem shorter, allowing space for a padlock
bottom-right.
**
Public bug reported:
The current nm-applet icon that is shown for a wired VPN connection is
very unclear - overlaying a padlock onto the existing connection-type
icon works fine for the usual wifi icon, but with a wired connection the
padlock merges into the down arrow and looks like screen
This isn't really a bug with Upstart since it appears the problem is
that bamfdaemon is spamming dbus somehow. Upstart is simply logging the
output.
That said, there is an outstanding merge proposal to have the session
logrotate job run periodically which would have avoided so much disk
space
** Package changed: bamf (Ubuntu) = dbus (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to bamf in Ubuntu.
https://bugs.launchpad.net/bugs/1284164
Title:
~/.cache/upstart grows enormous
Status in “dbus” package in Ubuntu:
Public bug reported:
.
ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: udisks2 2.1.2-1
ProcVersionSignature: Ubuntu 3.13.0-7.25-generic 3.13.1
Uname: Linux 3.13.0-6-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.13.2-0ubuntu2
Architecture: i386
CustomUdevRuleFiles:
** Changed in: upstart (Ubuntu)
Status: In Progress = Fix Committed
** Also affects: upstart
Importance: Undecided
Status: New
** Changed in: upstart
Assignee: (unassigned) = James Hunt (jamesodhunt)
** Changed in: upstart
Status: New = Fix Committed
** Changed
This bug is fixed in upstart 1.11-0ubuntu2 which will be pushed out once
the alpha 2 freeze is over (Thurday).
If you are still affected by this problem (in other words you have not
managed to upgrade to alsa-utils 1.0.27.2-1ubuntu2), you will need to do
*one* of the following:
1) Disable
** Changed in: upstart (Ubuntu)
Status: Confirmed = In Progress
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1269731
Title:
init crashed with SIGSEGV
Status in
There is an upstart logrotate job that runs automatically soon after
session start, however, it does not (yet) run periodically to handle
rogue jobs such as gnome-session. You can however run the job yourself
simply enough as a non-root user:
$ start logrotate
Please attach a few lines of the
@TJ - thanks for your analysis, which mirrors our findings. We now have a fix
to Upstart and new tests to ensure this problem stays fixed.
@Luke - thanks too for fixing alsa-utils! :)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
This looks like either a problem with network-manager, or a problem with
your network configuration / hardware. Have you modified
/etc/network/interfaces?
** Also affects: network-manager (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are
** Changed in: upstart (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1256262
Title:
stop triggers logout (from gnome-session?)
** Also affects: gnome-session (Ubuntu)
Importance: Undecided
Status: New
** Changed in: gnome-session (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
** Changed in: upstart (Ubuntu)
Status: Fix Released = Incomplete
** Changed in: upstart (Ubuntu)
Status: Incomplete = In Progress
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions:
Public bug reported:
The main libreoffice icon seen in the dash is too bland.
I can see that it is attempting to represent in the most minimal way the
overall office suite (by not including text, cells, formulae, etc),
however, subtracting all content from the icon gives it an overly
ascetic air
Public bug reported:
Booting saucy under kvm and switching to tty1 results in the screen
going black once lightdm starts and this seems to also stop the user
switching vt's using ctrl-alt-fX.
** Affects: lightdm (Ubuntu)
Importance: Undecided
Status: New
** Attachment added:
Hi Jan,
Thanks for reporting this issue. I think you are correct - nm looks like
the culprit. Re-assigning...
** Package changed: upstart (Ubuntu) = network-manager (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Public bug reported:
Latest update to lightdm broke boot for me as ligthdm crashes on
startup.
dmesg shows:
[ 38.108529] lightdm[1621]: segfault at 3f7 ip b74ada42 sp bff82ccc error 4
in libglib-2.0.so.0.3703.0[b746b000+102000]
[ 39.364988] init: lightdm main process (1621) killed by SEGV
** Changed in: lightdm (Ubuntu)
Importance: Medium = High
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1203660
Title:
lightdm crashed with SIGSEGV in g_list_last()
Status in
Manually downloading the old revision and rebooting does resolve the
problem for me:
$ wget
http://gb.archive.ubuntu.com/ubuntu/pool/main/l/lightdm/lightdm_1.7.4-0ubuntu1_i386.deb
$ wget
http://gb.archive.ubuntu.com/ubuntu/pool/main/l/lightdm/liblightdm-gobject-1-0_1.7.4-0ubuntu1_i386.deb
$
The default behaviour of the boot with this bug is that the greeter
never appears; you just see the Ubuntu pulsing plymouth theme.
However, the system has booted so you can switch to a text console
(control+alt+f1 for example), login and take remedial action as shown in
#6.
--
You received this
Public bug reported:
.
ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: apport 2.9.1-0ubuntu1
Uname: Linux 3.8.0-999-generic i686
ApportLog:
ApportVersion: 2.9.1-0ubuntu1
Architecture: i386
CrashReports:
664:1000:114:0:2013-03-15 09:46:50.80321 +:2013-03-15
09:46:50.80321
Fix appears to have regressed.
** Changed in: unity
Status: Invalid = New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dp-unity
https://bugs.launchpad.net/bugs/737792
Title:
compiz
Public bug reported:
$ zenity --calendar
zenity: error while loading shared libraries: libGL.so.1: cannot open shared
object file: No such file or directory
$ ldd `which zenity`|grep -i gl
libglib-2.0.so.0 = /lib/i386-linux-gnu/libglib-2.0.so.0 (0xb703b000)
libGL.so.1 = not found
Problem was caused by failed background apt-get update on my system
which had not yet configured nvidia-current.
** Changed in: zenity (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to zenity in
Interestingly, since this issue is GUI related, it is still possible to
run dia without one:
$ dia --nosplash -t svg -e output.svg input.dia
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to dia in Ubuntu.
Public bug reported:
$ dia
sys:1: Warning: attempting to add an interface
(DiaInteractiveRendererInterface) to class (DiaGdkRenderer) after class_init
** (dia-normal:11678): CRITICAL **: dia_renderer_set_size: assertion
`irenderer != NULL' failed
** (dia-normal:11678): CRITICAL **:
Public bug reported:
gnome-session/main.c has disabled all signal handling, but intention was
seemingly to only disable SIGSEGV signal handing:
10:43 jodh chrisccoulson: hi - I'm looking at how gnome-session currently
shuts down and trying to understand why the following is
Public bug reported:
This looks to be a regression of bug 1049949.
$ wc -l /var/log/syslog
822 /var/log/syslog
$ grep signonpluginprocess /var/log/syslog | wc -l
557
ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: signond 8.44-0ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-0.4-generic
** Changed in: libnih (Ubuntu Raring)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/997359
Title:
nih uses eglibc private symbol __abort_msg
Not an Upstart issue.
** Package changed: upstart (Ubuntu) = fglrx-installer (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1069624
Title:
System failed to detect
Not an upstart issue. Sounds like it might be a non-privileged mounting
problem.
** Package changed: upstart (Ubuntu) = gvfs (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gvfs in Ubuntu.
Branch for when 'R' opens:
https://code.launchpad.net/~jamesodhunt/ubuntu/quantal/debconf/bug-1060249
Patch sent to Debian.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gsettings-desktop-schemas in Ubuntu.
The problem with debconf needs a little explanation. As show, the
command that caused the failure was:
/usr/bin/perl -w /usr/share/debconf/frontend /var/lib/dpkg/info/man-
db.postinst triggered /usr/share/man
The 'frontend' perl script determines which type of debconf frontend to
display. In
** Bug watch added: Debian Bug tracker #690776
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=690776
** Also affects: debconf via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=690776
Importance: Unknown
Status: Unknown
** Changed in: debconf (Ubuntu)
Status: Confirmed
I have the same problem.
After installing the dbg packages...
$ gdb --args /usr/lib/libreoffice/program/soffice.bin --help
GNU gdb (GDB) 7.5-ubuntu
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software:
Public bug reported:
I have the dbg packages installed. See attached gdb transcript for
backtrace for all threads.
ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: libreoffice (not installed)
ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4
Uname: Linux 3.5.0-16-generic i686
** Attachment added: gdb-transcript.log
https://bugs.launchpad.net/bugs/1062378/+attachment/3376376/+files/gdb-transcript.log
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
A way to fix this:
$ gsettings set org.gnome.desktop.screensaver embedded-keyboard-command
''
For some reason, I had the following set:
$ gsettings get org.gnome.desktop.screensaver embedded-keyboard-command
'onboard -xid'
--
You received this bug notification because you are a member of
This looks like it might be a duplicate of bug 615549.
I've done some digging and although I'm not sure this will fully resolve
the issue observed, I have found a bug in lightdm.conf which could cause
the behaviour seen...
As Clint intimates in #11, the current 'start on' condition...
Addendum to #19:
Currently the 'card0' matching is being attempted on DEVPATH. This isn't
obvious from the /var/log/udev extract shown, but the upstart-udev-
bridge will in this scenario create the event with the following
environment variable ordering:
1) DEVPATH
2) DEVNAME
3) SUBSYSTEM
4)
Please could those affected attach /var/log/udev?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/969489
Title:
lightdm tries (and fails) to start too early?
Status in Upstart:
New
This problem sounds like it could be kernel issue.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
For 12.10, we really should add a 'primary-graphics-card' event alias or
abstract job that abstracts the udev complexities since that confusing
condition (drm-device-added card0 PRIMARY_DEVICE_FOR_DISPLAY=1 or
stopped udev-fallback-graphics) is also semi-duplicated in other jobs:
-
This problem appears to be resolved for me on an installed precise
system. Copying bar.desktop to ~/Desktop/ and once I allow the file to
be executable (right click, properties), the icon text shows line 1 as
Install Ubuntu 12.04 and line 2 as LTS.
** Attachment added: bar.desktop
*** This bug is a duplicate of bug 751689 ***
https://bugs.launchpad.net/bugs/751689
It's not aliens, it is of course the kernel :)
** This bug has been marked a duplicate of bug 751689
ThinkPads overheat due to slow fans when on 'auto'
--
You received this bug notification because you
Public bug reported:
I'm not entirely sure where or why this is happening, but I have seen on
~5 occasions now my system spontaneously switch off.
Initially, I thought it might be an init/kernel issue, but today I saw
the problem occur twice and crucially, I also got to see the console and
there
Public bug reported:
Whilst investigating bug 937611, I enabled the on-screen keyboard.
However, I subsequently switched if off via System Settings -
Universal Access - Typing tab - Typing Assistant.
As expected, the keyboard no longer displays on the desktop but when the
screen locks
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-screensaver in Ubuntu.
https://bugs.launchpad.net/bugs/942530
Title:
on-screen keyboard always displays once enabled
Status in “gnome-screensaver” package in Ubuntu:
New
Bug
I have a Huawei E220 HSDPA USB Modem which fails with the same assertion
errors as above. I wonder if this is related to bug 840082?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
I have a Huawei E220 HSDPA USB Modem which fails to work with precise.
I'm seeing NM assertion failures in syslog as shown on bug 874987, so
for me this bug is not fixed. Is there some way to disable NM
configureing IPv6 for a connection? There is only an IPv4 tab displayed
when editing the
Public bug reported:
NM runs /etc/NetworkManager/dispatcher.d/01ifupdown when a connection
changes state.
If a connection is made, the dispatcher script runs:
exec run-parts /etc/network/if-up.d
However, when a connection goes down, the dispatcher script runs:
exec run-parts
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/925411
Title:
dispatcher script 01ifupdown never emits net-device-down
Status in “network-manager” package in Ubuntu:
New
Public bug reported:
1) Edit-preferences
2) click General
3) observer that general options are shown
4) click Tabs or Content and notice that window continues to show general
options (however long you wait).
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: firefox 10.0~b5+build1-0ubuntu1
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/922154
Title:
Tabs and Content tabs in edit-preferences do nothing
Status in “firefox” package in Ubuntu:
New
Bug description:
1)
Hmm after a reboot, the problem appears to have gone away. My selected
h/w profile is Analogue Stereo Output + Analogue Mono Input (which has
not changed).
There are a couple of extra odd things going on here:
1) if I change the h/w profile for the headset to Analogue Stereo
Output and switch to
Public bug reported:
If I plug in my Logitech H530 USB Headset, it shows as ClearChat Pro
USB under Hardware in 'gnome-control-center sound', but it does *not*
show up as a valid input or output device if I click either the Input or
Output tabs.
On the input tab, the Connector menu only has 1
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/917165
Title:
gnome-control-center does not allow selection of USB headset for input
or output
Status in
*** This bug is a duplicate of bug 861268 ***
https://bugs.launchpad.net/bugs/861268
** This bug has been marked a duplicate of bug 861268
text corruption in terminals (xterm, urxvt) and emacs
--
You received this bug notification because you are a member of Desktop
Packages, which is
Public bug reported:
File-Print-Print to file defaults to output format PostScript.
Although I'm a big fan of PostScript (even having programmed in it), I
think PDF should be the default now since:
(1) the resulting files are smaller (being compressed)
(2) standard desktop tooling handles PDF
1 - 100 of 116 matches
Mail list logo
