Excellent, many thanks!
On Sun, Aug 18, 2013 at 6:25 AM, Arthur de Jong adej...@debian.org wrote:
I've merged your change upstream in both the 0.8 and 0.9 branches.
Attached is a patch that should be suitable for dropping in
debian/patches for version 0.8.13-2.
** Patch added:
Good to know about the PID file, but as far as I know, there is no
mechanism in Upstart for utilizing PID files. This is an intentional design
decision, see
https://lists.ubuntu.com/archives/upstart-devel/2008-August/000735.html(the
section on the pid file stanza being removed)
Is there any
I'd agree that expect fork looks like the correct approach, and until the
latest release, using that stanza seemed to work without issue.
It's true that adding functionality to accommodate a service management
system is a poor separation of concerns, but nslcd's generation of a PID
file does
Hi Arther,
Good to know. I think the behavior I'm seeing is most likely a result of
some change to Upstart, because I'm using the same modified 0.8.10-1
package that I've used in the past. Even so, the process ID that Upstart
decides to track is very definitely incorrect whether I track the first
Another patch rev: after upgrading to Raring (nss-pam-ldapd 0.8.10), the
expect fork stanza no longer behaves correctly. Running script to
determine fork count (http://upstart.ubuntu.com/cookbook/#how-to-
establish-fork-count) indicated 6 calls to fork or clone when nslcd
starts.
To address this
Juan,
If nscld timeouts are causing slow boot times (which may or may not be the
case in the situation you describe--I'd recommend disabling nslcd to see if
the boot time improves), I don't know of clean solution except the init
scripts that I've written and attached to this bug report.
HTH
On
I'm experiencing the same problem on Ubunutu 13.04, util-linux
2.20.1-5.1ubuntu8, gnome-diskutility 3.6.1-1ubuntu1
Here's the relevant fstab lines. (all three were generated by the Disks
utility):
# Windows is installed on sda1 (and sda3)
/dev/disk/by-partlabel/Win7 /mnt/Win7 auto
I recommend giving in to this temptation. ;) I'm happy to help with
testing in any way I can.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/806761
Title:
Feature Request: Upstart scripts for nslcd
This is actually a KWin issue. I'm not sure if a bug has been filed
against that.
** Changed in: kubuntu-active-meta (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The 13.04 release still contains this bug.
On the Kubuntu Active FAQ, there is a method to enable the mouse
pointer, but it is only shown for RPM-based systems.
** Changed in: plasma-mobile (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member
(Or request that it be marked triaged, anyway... and get developers to
see if they can get the darned resize screen up.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1164592
Title:
Ubiquity
On jbicha's request, I tested a Live USB of both 13.04 and the 13.10
daily build. The 13.04 image I used to reproduce the bug (successfully),
and the 13.10 image I looked at to check for a fix.
The 13.10 image I used (for 20130614) to install Ubuntu GNOME alongside
my current installs showed that
I found out what it was - a bad flag inside a startup script. You may
close this bug now.
** Changed in: xfce4-session (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
In Xubuntu 13.04, I have been experiencing instances where xfce4-session
will, for no given reason or warning, kill itself, bringing me back to
the login screen (lightdm-gtk-greeter). I have searched through
tracebacks and have found no explainable reason for this.
When installing Wings3D from apt-get, here's the output:
$ sudo apt-get install wings3d
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are
#39, with #40's edit, works. Now on to TeamViewer's end of the puzzle.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1094218
Title:
lsb_release crashed with IOError in getstatusoutput(): [Errno 10]
Pasi,
Does this only affect the upgrade via Update Manager/Software Updater or using
[ do-release-upgrade ] in the terminal and/or upgrading via live image?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Adding ppa:ubuntu-unity/daily-build and updating libnux-4.0.0 fixed the
problem for me on my Intel Mobile 945GSE.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1087534
Title:
[regression] Corrupted
Public bug reported:
When I run git-hg clone https://bitbucket.org/astiob/hgshelve; I get this
output:
Initialized empty Git repository in
/home/test_user/test44/hgshelve/hgshelve/.git/
requesting all changes
adding changesets
adding manifests
adding file changes
added 64 changesets with 80
Okay, another patch rev and a big-huge post addressing Arthur's last
concerns (thanks again to him for taking the time to review the patch).
-Regarding serialization of network interface bring-ups, I've addressed
this by running the flock command asynchronously. As far as I can tell,
this doesn't
Another revision, this time using the correct target state when calling
the wait-for-start script, per http://upstart.ubuntu.com/cookbook/#job-
states
** Patch added: Path Rev 8
I noticed an error in the k5start Upstart script: the settings in the
/etc/defaults/nslcd file were being overridden. I've attached a revised
patch.
Still working on my reply to Arthur's latest.
** Patch added: Patch Rev 7
Public bug reported:
Hello.
Description:Ubuntu 12.04.1 LTS
Release:12.04
ldirectord:
Installed: 1:3.9.2-5ubuntu4.1
Candidate: 1:3.9.2-5ubuntu4.1
Version table:
*** 1:3.9.2-5ubuntu4.1 0
500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/universe amd64
Packages
That is correct... so far so good
exec lightdm -d
On Sun 16 Dec 2012 02:12:08 PM EST, Gavin Graham wrote:
@Daniel (internalkernel)
Just confirming so it isn't lost in the midst, you changed
'exec lightdm'
to
'exec lightdm -d'
and now you are getting Lightdm performing correctly each
This seems to happen everytime I boot my computer... I'm running a fresh
install of 12.10 on an i7 core, primary SSD, Nvidia drivers from x-swat
and Dual monitors with Twinview enabled.
What I've tried so far with no success:
- rename to *card0
: seemed to have no effect as there is no card0
Are you opening the .deb package directly or opening qapt-deb-installer
first?
It doesn't seem to work using the latter method (although it should) on
12.10. I successfully installed Google Chrome by opening the .deb
package directly. (from the file manager)
--
You received this bug
Public bug reported:
This error occurred during the dist-upgrade process.
fuzzy@unicycle:~$ lsb_release -rd
Description:Ubuntu 12.04.1 LTS
Release:12.04
fuzzy@unicycle:~$ apt-cache policy emacs23
emacs23:
Installed: 23.3+1-1ubuntu9.1
Candidate: 23.3+1-1ubuntu9.1
Version table:
Okay, I've attached revised scripts that should be compatible with
Debian Wheezy (to the extent that I can readily test, which is a Wheezy
build using pbuilder). The lack of a separate System V init script for
nslcd-k5start does not seem to cause any issues.
All the technical issues Arthur raised
I do agree that the reasons for including the sleep.d script aren't very
clear, so I'm definitely in favor of reviewing the script's reason for
existence and removing it if removal is the appropriate action. I'll try
to establish contact with the Debian maintainer about this issue.
** Bug watch
Oops, I didn't realize Jeroen had already logged a Debian bug:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=689584
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1058883
Title:
start-on
** Description changed:
- The local-filesystems signal is not generated during a resume after
- suspend, so aiccu doesn't (re)start correctly during resume. The
- original reason for the local-filesystem condition to be present was to
- avoid issues with logging when the local filesystems aren't
I think it's worth noting that a great deal of confusion surrounding
aiccu restarts is probably related to inconsistencies in the daemon's
behavior.
When the daemon starts, it will terminate if it cannot contact the
tunneling service, which is very different from how the daemon behaves
once it's
On Fri, Oct 5, 2012 at 9:48 AM, Jeroen Massar jer...@unfix.org wrote:
When the daemon starts, it will terminate if it cannot contact the
tunneling service
At failures it will always log the error and terminate. This as that is
the way that a user will notice things and start looking into
I stumbled across another relevant bug report while working on an un-
related issue: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=566910
** Bug watch added: Debian Bug tracker #566910
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=566910
--
You received this bug notification because
I'm not sure why the restart is there. Perhaps it's trying to guarantee the
routing tables are correct. Or perhaps it's intended to start up the aiccu
daemon if the computer is suspended on a network with native IPv6 support,
then resumed on a network without native IPv6 support, where the aiccu
Looking at the Debian changelog, it appears this resume script has its
origins in this bug report:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=531003
On Wed, Oct 3, 2012 at 1:49 PM, Jeroen Massar jer...@unfix.org wrote:
I'm not sure why the restart is there. Perhaps it's trying to
** Bug watch added: Debian Bug tracker #531003
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=531003
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1058883
Title:
start-on conditions in Upstart
out the offending line and use the package's original Upstart
script (with the local-filesystem condition intact), the sixxs interface is
still present on resume.
On Mon, Oct 1, 2012 at 12:13 PM, Caleb enlightened.des...@gmail.com
wrote:
In my case the issue arises when resuming from suspend
In my case the issue arises when resuming from suspend on a laptop, using
wlan for network connectivity. After resuming, ifconfig doesn't show the
sixxs interface, and aiccu service status is stopped. Obviously IPv6
connectivity is unavailable in this situation.
I'll do some poking around to see
One potential solution is to put a script in /etc/network/if-up.d that
executes before any of the other scripts in that directory and waits for
a specific condition (e.g. an IP address is assigned, or a route becomes
available). I posted an example here:
Public bug reported:
The local-filesystems signal is not generated during a resume after
suspend, so aiccu doesn't (re)start correctly during resume. The
original reason for the local-filesystem condition to be present was to
avoid issues with logging when the local filesystems aren't mounted,
Ah, good to know. Thanks for the link.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/806761
Title:
Feature Request: Upstart scripts for nslcd
To manage notifications about this bug go to:
Sounds quite nifty, but wouldn't that make the fix Ubuntu-specific? As I
understand it, the Ubuntu folks like to see a problem fixed upstream if
possible.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi Arthur,
Thanks for looking at this, and taking the time to give your feedback.
- If Upstart isn't part of the base Debian install, I'd agree that
dropping the init script doesn't make sense, although the race
conditions that the Upstart scripts aim to address wouldn't be
addressed. Do you
So, any further recommendations or fixes? If not, what's the next step?
Should I be coordinating with Arthur to get this merged upstream?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/806761
Title:
+1
It's really nice that Wine can integrate like this, and having the icons
look perfect would make a big difference.
I swear this worked in a previous version...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
New revision. Changes:
-much cleaner mechanism for avoiding races in if-up.d script (thanks Clint!)
-Longer timeout waiting for credentials cache from k5start, to make sure
timeout errors from k5start get logged.
** Patch added: Patch rev 5
Hi Client,
No worries about the response time. I really appreciate your help in
making these scripts as excellent as possible.
The recommended method for serializing start attempts is working well.
I'll dogfood the change for a day or so, then post a revised patch.
--
You received this bug
Hi James,
Well, that's embarrassing--I did upload the wrong file. Thanks for
pointing that out. The correct patch file is attached.
I'll take a look at the instance stanza as well--it'd be be nice to have
a more elegant solution to that interface issue.
** Patch added: Upstart script patch,
I'm assuming the lack of comments indicates that there are no violent
objections to the path I'm taking. The current revision has been working
quite well on my system, as well as a testbed VM. So, I'm re-subscribing
ubuntu-sponsors and attaching the revised patch.
Overview of changes:
-changed
One further point: I don't think we can replace the defaults file with
env stanzas, because some of the variables that can be overridden in the
defaults file require expansion, which the env stanza doesn't support.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
silently.
Thanks for your time and attention to making this patch as robust and
bullet-proof as possible. Every refinement gives me a warm fuzzy
feeling. :D
-Caleb
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
Hi Clint! Many thanks for taking the time to review the patch! I'm
revising the scripts based on your feedback and should have a new
debdiff soon.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/806761
Okay, after reading the Daemon Behavior section of the Upstart cookbook
(http://upstart.ubuntu.com/cookbook/#daemon-behaviour), I've settled on
a solution that I'm reasonably happy with: looping in a post-start
script until the ticket cache is detected on the file system _or_ a
timeout occurs (so
Seems like this is best fixed at the Debian level, but after wasting a
couple hours with configuration issues, crashes in the GTK interface,
and no clear way to reload a report from draft (why in the world would a
draft be helpful if I can't reload it?!) in reportbug, I've run out of
patience.
Adding gnome-panel to the Requires stanzas in xmonad's control file is
not correct--many people will want to install xmonad without using
Gnome. Adding gnome-panel to the Recommends stanza doesn't provide a
strong guarantee that the dependency will be met.
I believe the correct solution is a
Further details: with gnome-panel, login with the session (it will
fail), then switch to a virtual console (that is, hit Ctrl+Alt+F1).
Login, and cat .xsession-errors. It will contain a single line:
gnome-session [PID]: WARNING: Unable to find required component 'gnome-
panel'
--
You received
The odd behavior turned out to be a race condition between the nslcd and
nslcd-k5start scripts: per the Upstart docs
(http://upstart.ubuntu.com/cookbook/#expect), Upstart assumes the job
has started after the first PID that is generated in the script, unless
an expect stanza is present. So,
Thinking more about the way the sasl_mech and krb5_ccname options were
handled, I saw that the logic in the nslcd-k5start file wasn't very good
--we should only be looking for the kinit and k5start binaries if the
user enabled Kerberos, either through the defaults file override, or
with the
Hi Arther,
Thanks for taking the time to review the patch. :)
The motive for Upstart scripts instead of a init.d script is simple:
with the init.d script, I couldn't find a simple way to guarantee nslcd
started _after_ a network connection was available. At the time I logged
the feature request
Here's a debdiff against nss-pam-ldap 0.8.10 with the required changes.
** Patch added: upstart scripts for nslcd
https://bugs.launchpad.net/ubuntu/+source/nss-pam-ldapd/+bug/806761/+attachment/3213474/+files/nslcd-upstart.debdiff
--
You received this bug notification because you are a
Same issue as well... NM shows connected, I receive a DHCP lease... but
attempting to ping anything other than my local interfaces is a fail.
I've tried to narrow it down to kernel versions, backported wireless,
etc... nothing helped.
I did notice after first installing 12.04, network manager
*** This bug is a duplicate of bug 734428 ***
https://bugs.launchpad.net/bugs/734428
** This bug has been marked a duplicate of bug 734428
[Upstream] Wrong automatic text color dark grey with black background
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I'd like to add that I'm still affected by this bug in a clean install
of Ubuntu 12.04. I will attach a screenshot, to show that it can be
reproduced, and to illustrate the effect, which is not always
immediately noticeable with some true black text for contrast.
--
You received this bug
** Attachment added: Screenshot of the problem persisting in Ubuntu 12.04.
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/734428/+attachment/3127017/+files/ScreenshotUbuntu12.04.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
I'm hesitant to call the no-daemonize Upstart script a fix because it
doesn't actually address the underlying problem. It seems like more of a
work-around to me.
However, I think Jan's concern is very valid. Pushing the changes into
the main repository might be the best option at this point:
Public bug reported:
For some reason when I upgrade the Linux image from 2.6.32-37 to
2.6.32-38, the NVIDIA driver doesn't function AT ALL. Please fix
whatever it is that's causing this.
ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: nvidia-96 96.43.17-0ubuntu1.1
ProcVersionSignature:
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/930685
Title:
NVIDIA 96 driver doesn't work on Ubuntu 10.04 running over Linux
2.6.32-38-generic image
To manage notifications about this bug go to:
I don't completely understand why, but using Cedric's backport PPA in
bug #873784 to get correct handling of the wtmp file also resolved the
issue with the session selection for me. Worth a try for those who are
affected by this bug.
--
You received this bug notification because you are a
I've posted this upstream, with some comments on how the issue might be
resolved: https://bugs.freedesktop.org/show_bug.cgi?id=43997
** Bug watch added: freedesktop.org Bugzilla #43997
https://bugs.freedesktop.org/show_bug.cgi?id=43997
--
You received this bug notification because you are a
Just a note that the 'no LDAP user is listed after reboot' is likely the
same bug reported in bug #873784
(https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/873784)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Re: hyperair = wontfix:
It is, in fact, a fairly minor cosmetic quibble. One that can none-the-less
impact user experience.
It also appears to be very simple to fix. (hell, I could probably fix it
myself if I had a clue. Depends on how Banshee was written.)
Hence, filed in papercuts :)
Same problem here. Keys work when Banshee is open but that means it
plays alongside Pithos.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/860600
Title:
Media keys aren't working (Ubuntu 11.10,
I also updated to 11.10, and have had to drop down to a console window
to kill chrome twice now. For me, all keyboard and mouse clicks are not
(apparently) registered. Perhaps something with fglrx?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
I execute
apport-collect 870323
in the terminal and get this response
Traceback (most recent call last):
File /usr/share/apport/apport-gtk, line 368, in module
app.run_argv()
File /usr/lib/python2.6/dist-packages/apport/ui.py, line 560, in run_argv
return self.run_update_report()
Public bug reported:
I am using Ubuntu 10.10 the Maverick Meerkat - released in October 2010
and supported until April 2012.
update manager fails and displays the following:
(Could not initialize the package information
An unresolvable problem occurred while initializing the package
Public bug reported:
After tearing off the options menu and changing some settings in
emacs, it froze. I was unable to do anything in the graphics environment
after that, although I could still move the mouse.
ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: emacs 23.2+1-7ubuntu2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/863437
Title:
emacs crashed GUI
To manage notifications about this bug go to:
*** This bug is a duplicate of bug 842072 ***
https://bugs.launchpad.net/bugs/842072
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/842119
Title:
package gnome-control-center-data
*** This bug is a duplicate of bug 842072 ***
https://bugs.launchpad.net/bugs/842072
Public bug reported:
When trying to install updates, this package won't install.
ProblemType: Package
DistroRelease: Ubuntu 11.10
Package: gnome-control-center-data 1:3.1.91-0ubuntu1
ProcVersionSignature:
Hello Micah,
The issue has been resolved upon upgrading to Firefox 5.
Thank you,
Caleb
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/799957
Title:
Tabs from other computers XML parsing error
Public bug reported:
Binary package hint: firefox
Hello,
Upon trying to open tabs from other computers, I receive the following
error:
XML Parsing Error: undefined entity
Location: about:sync-tabs
Line Number 7, Column 1:window id=tabs-display
^
My system is Kubuntu 11.04 32 bit with Firefox
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/799957
Title:
Tabs from other computers XML parsing error
To manage notifications about this bug go to:
It appears this was actually a consequence of conky running on the
desktop.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/779732
Title:
keyboard shortcuts don't work immediately after app closes
Public bug reported:
Binary package hint: unity
I recently noticed that some keyboard shortcuts (for example Alt-F2 to
open the dash) don't work immediately after a program exits. For
example: run gedit, close using Alt-F4, press Alt-F2. Ideally, the dash
should open so that I can run another
of the
alternatives (as I have done...)
Caleb
** Affects: blas (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/769175
Title:
alternatives for both
to have only one instead of
trying to keep them in sync (LP #769175).
Caleb
** Affects: atlas (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/769180
I'm currently using the wacom-dkms package from the 'irie/wacom' PPA,
and it appears that ONLY finger-touch-based input manipulates the cursor
and nothing else (such as the pen).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
And it seems the 2nd button on the tablet works as right-click, and the
3rd as left-click.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/703783
Title:
Wacom BambooFun tablet powered, but no input
Public bug reported:
The device is powered when plugged in, but doesn't manipulate the mouse
cursor or anything. Even tried the workaround of jumping between virtual
terminals (Ctrl+Alt+F1, and back to Ctrl+Alt+F7) to no avail.
Specific model:
CTH-661
The lsusb output for this device:
Bus 002
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/703783
Title:
Wacom BambooFun tablet powered, but no input
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Public bug reported:
USB devices (such as USB flash storage, USB mouse, etc) worked in kernel
version 2.6.31-20 and prior (perhaps Ubuntu 10.04 kernel?), but stopped
working in 2.6.35-22 and thereafter.
When a device is plugged in, it is indicated via dmesg of the device
being detected, but
** Description changed:
USB devices (such as USB flash storage, USB mouse, etc) worked in kernel
- version 2.6.35-22 and prior (perhaps Ubuntu 10.04 kernel?), but stopped
+ version 2.6.31-20 and prior (perhaps Ubuntu 10.04 kernel?), but stopped
working in 2.6.35-22 and thereafter.
When
I've finally found a pattern to this bug as it seemed fairly sporadic.
It appears that USB will work on 2.6.35-22 and after ONLY if a USB device is
plugged in at boot (such as at GRUB menu; or before being turned on)
Whereas on 2.6.31-20 and prior, USB will work regardless if a device is plugged
Nope, it's better now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/444261
Title:
waiting for service to start text in pending operations is misleading
--
ubuntu-bugs mailing list
Public bug reported:
When configuring ethernet bonding on Ubuntu 10.04.1 - 2.6.32-25-server
#45-Ubuntu SMP Sat Oct 16 20:06:58 UTC 2010 x86_64 GNU/Linux, setting
mode 6 (balance-alb) causes a kernel Oops once some network traffic is
sent or recieved on the interface.
The problem is with the
Public bug reported:
Binary package hint: tvtime
Can't get any audio, nor adjust it, not muted either. Stuck at 0. Able to get
audio when using VLC. TV tuner card audio is through Line In ('audio out' port
from the tuner card, bridged to a 'line in' port).
Worked out of the box just fine all
** Attachment added: Dependencies.txt
https://bugs.launchpad.net/bugs/650693/+attachment/1651059/+files/Dependencies.txt
--
mixer: Can't open device /dev/mixer, mixer volume and mute unavailable
https://bugs.launchpad.net/bugs/650693
You received this bug notification because you are a
Nope, it works now.
On Mon, Sep 13, 2010 at 4:46 PM, rusivi1 388...@bugs.launchpad.net
wrote:
Thank you for posting this bug.
Does this still happen in Lucid?
** Changed in: yelp (Ubuntu)
Status: New = Incomplete
--
Repeat the search online does not work
Public bug reported:
Binary package hint: banshee
Error occurred upon login.
ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: banshee 1.6.1-1~lucid1
ProcVersionSignature: Ubuntu 2.6.32-24.38-generic 2.6.32.15+drm33.5
Uname: Linux 2.6.32-24-generic x86_64
NonfreeKernelModules: nvidia
101 - 200 of 545 matches
Mail list logo
