Just to note this caught me out. I switched my Mantic system to use an
encrypted root some weeks ago, and used luks2 (with pbkdf2 as Argon2
isn't supported by grub2).
This was working fine, but I decided to upgrade early to Noble today,
only to find my system unbootable. I managed to sort it once
That's great news - thanks very much. This will make working on RetroPie
development in a chroot much easier (we have workarounds to avoid using
git because of this issue).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I get a hang doing this most times in an emulated ARM chroot with qemu-
arm-static (Raspbian). Host machine is x86_64 Ubuntu 16.04 running qemu
2.5.0.
git clone --depth 1 https://github.com/libretro/picodrive.git
cd picodrive &&
git submodule update --init
--
You received this bug notification
Public bug reported:
Apologies if this is filed against the wrong package - I assumed the fix
would be to set a dependency in a package like xubuntu-desktop but I
could be wrong.
When updating from 13.10 to 14.04, if a new user is added or xfce4
panels for an existing user reset to default, no
It is a shame this didn't get addressed - despite there being some fixes
that could at least be worked from. Now anyone installing the upcoming
xubuntu are going to have a non working volume control. Get ready for a
lot more bug reports - reflects a little poorly too on ubuntu as a whole
-
Just to add this isn't just a Dell issue - so perhaps the issues could
be merged/marked duplicate.
Affects my Acer Travelmate p273 -
psmouse serio1: alps: Unknown ALPS touchpad: E7=73 03 50, EC=73 02 02
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
an alternative would be to use the original script this was intended to
replace - http://svn.apache.org/repos/asf/subversion/trunk/contrib
/client-side/svn_load_dirs/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Looks like a patch that could go upstream too. if nl80211 reports no
capabilities then try wext. and considering your list (appreciate your
research here), it seems a good option. only recently nm added support
for the nl80211 interface, so perhaps they are a bit ahead of the kernel
in this
some compile errors with that patch. drvinfo.driver is a char[32] and
brackets are mismatched.
wifi-utils.c: In function 'wifi_utils_init':
wifi-utils.c:76:17: error: incompatible types when assigning to type 'char[32]'
from type 'void *'
wifi-utils.c:85:3: error: expected ')' before 'ret'
sorry that should have been an attachment. my brain is totally non
functional today.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/973241
Title:
ipw2200 driver doesn't report any capabilities or
patch seems to work. thanks for that.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/973241
Title:
ipw2200 driver doesn't report any capabilities or wireless properties
using the nl80211 interface
Thanks for the rip regarding nl80211/wext - I modified the code to not
try nl80211 first and just use wext.
seems to work. Uploading packages here -
https://launchpad.net/~jools/+archive/ipw2200
Would be nice if network manager could have a workaround to check for
this device and force wext or
s/rip/tip
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/973241
Title:
ipw2200 driver doesn't report any capabilities or wireless properties
using the nl80211 interface to network-manager
To
note for those with the problem of not being able to connect to a wpa
network on ipw2200 - I have put some packages on my a ppa -
https://launchpad.net/~jools/+archive/ipw2200 that use wext instead of
the nl80211 interface working around the problem. Would be nice if
network manager could have a
Sorry a misunderstanding then. When I posted in #49 I was referring
earlier to the kernel not returning correct information about the
hardware - then you referenced some patches and I assumed you meant they
were a workaround (hence the comment about not having to git bisect).
Ill debug it in the
I built network-manager/network-manager-gnome packages with those
patches in, and I am still unable to connect to my wpa network (my
wireless network is disabled in the menu).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
aah, a fix in nm rather than a kernel fix. I'll give it a try thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/908380
Title:
[ipw2200] nm-applet crashed with SIGABRT in g_assertion_message()
I realise that fixing it in nm is the wrong way of course. sorry for my
previous message if it sounded unappreciative. Thanks for the work with
this issue so far.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Might as well close it, as it isn't an issue with later releases.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/762806
Title:
[regression] shipped mousetweaks (3.0) does not work with shipped
excellent news - do you have any reference/commit id for the fix ? saves
me git bisecting to try and locate at what point it broke, which I was
considering doing this week.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I have unfortunately little faith after a major issue I reported before
natty release, which the fix was relatively simple, was never done, and
is still broken and will remain so until natty is out of support, and
then closed, yet be broken for all users who ever tried natty :/
that's completely
Well, I have given up hope of having this fixed. At least I fixed it for
my users of joggler ubuntu. it's a quick fix. this will no doubt remain
high priority unless naty gets to end of life and then closed. shame
:(
--
You received this bug notification because you are a member of Ubuntu
Bugs,
since this device does support wpa, isn't a quick workaround to override
what is returned until it is fixed in the kernel ? otherwise.
Considering precise release date, this needs to be fixed else
networkmanager is useless for anyone with one of these cards.
--
You received this bug notification
Philipp: that is how it has been for me recently. it shows my wireless
but I am unable to select it. Manually creating it works. Choosing to
connect to a hidden network crashes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
It suggested you remove the old meta data from the disk to re-add but I
didn't see that you did that. do that and then try and add it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/945786
Title:
The current message is certainly not clear. I concur with the others
here. A user may not know all the background information regarding the
project so it could easily be misleading.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
How did you disable the messaging menu extension? the addons settings
window doesn't work here either. (i commented on the duplicate by
accident sorry).
--
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 933951 ***
https://bugs.launchpad.net/bugs/933951
How did you disable the messaging menu extension? the addons settings
window doesn't work here either.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
log : note the additional errors caused when choosing the addons menu.
-- Exception object --
+ QueryInterface (function) 3 lines
+ message (string) 'Component returned failure code: 0x80570016
(NS_ERROR_XPC_GS_RETURNED_FAILURE) [nsIJSCID.getService]'
+ result (number) 2153185302
+ name (string)
mdadm has generally lagged behind on ubuntu. one of ubuntu server weak
points imho (hence I maintained a custom mdadm previously that had fixes
for many issues).. much was fixed for natty but there are still issues -
many in terms of initramfs, and udev device discovery in terms of mdadm.
Would
** Changed in: mdadm (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/904491
Title:
Please import 3.2.x from Debian
To manage notifications about this bug go
I can confirm this major issue ;-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/900214
Title:
Example feed should include Ubuntu Podcast(s)
To manage notifications about this bug go to:
Public bug reported:
svn-load was fixed for natty but is broken again on oneiric
TypeError: get_login() takes exactly 3 arguments (4 given)
Traceback (most recent call last):
File /usr/bin/svn-load, line 652, in module
Load %s into %s. % (os.path.basename(d), import_dir))
well, apart from me of course, and the others that use my modified
distribution of Ubuntu for the O2 Joggler, but luckily I fixed it for
them.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/762806
still nothing ? Would you like me to build you an older mousetweaks
package with a newer version number, and submit it? You have to take
accessibility stuff like this more seriously, or else, there is no point
writing up all the documents that state how good ubuntu is for this.
this is an easy
you can change the minimum sync speed to speed up resyncs. since the
raid can be used right away anyway, I dont see the problem. You can
create the array with the assume-clean option, but since you had already
created the array, you should have reblanked the disks, including the
raid superblocks.
or just stop trying to outsmart mdadm, and just let it sync on creation,
and you can be sure everything is fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/828421
Title:
Create new RAID1 array
Just to note: your best place for stuff like this is the linux raid
email list, as it's nothing ubuntu specific. you can probably get a more
detailed answer there.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I'd be happy to help in any way I can.
My thinking to a quick fix is a fake version numbered mousetweaks 2.32
so something like 3.0.0+really2.32 or so, just until the next ubuntu
release is out.
I understand there are lots of open bugs, but a lot is the fault of the
way ubuntu is scheduled for
Any change of an update as to when this would be fixed? Doesn't feel
like accessibility is any sort of priority for Ubuntu when an important
issue like this (which is easy to fix), is left open for two months
after release.
--
You received this bug notification because you are a member of Ubuntu
thanks for reassigning/sorting the bug metadata. I was trying to assign
it to mousetweaks unity but seemed unable to do so (probably because
it was assigned already to unity (ubuntu) - no doubt user error ;-) .
Pleased it has some attention now.
--
You received this bug notification because you
I was asked on #ubuntu-dev to add a short steps to reproduce on here
so. in case it is needed (although none of the mouse accessibility stuff
works due to the configuration changes gconf to dconf as was mentioned
by Gerd earlier, so it is quite easy to reproduce by trying either
simulate second
As this also affects the classic desktop should the bug be also
assigned elsewhere, or a new bug opened for that (likely the same issue
though)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/762806
doing
killall mousetweaks; mousetweaks --ssc
makes the second click work for me, so perhaps mousetweaks is being
started with the wrong options or something ? I'll try and debug it
further.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
in maverick, in gconf-editor there is
/desktop/gnome/accessibility/mouse/
with delay_enable (bool) and delay_time (float)
these exist in natty too, but in natty delay_time is an int, and there
is a error This key has no schema. The key has no owner (in maverick
it is mousetweaks).
missing some
ok. this looks like a mousetweaks bug. The new 3.0 version of
mousetweaks seems to miss agconf schema that was in the older version.
downgrading to the maverick version fixes this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: mousetweaks
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/762806
Title:
simulated second click with unity
--
ubuntu-bugs mailing list
it also seems other accessibility stuff is broken. like simulate second
click
https://bugs.launchpad.net/unity/+bug/762806
this makes unity non functional for any single click touchscreens, or
for any users that may require this to help them use the desktop.
--
You received this bug
I can confirm this issue. I currently build kernels on a lucid
virtualbox to use on maverick/natty.
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
** Tags removed: needs-kernel-logs needs-upstream-testing
--
You received this bug notification because you are a member of
I was having disconnects after kernel 2.6.26 with a usb harddrive on an
intel mac mini. No USB quirks, or max sector changes helped. in the end
I traced the issue to kernel commit
b963801164618e25fbdc0cd452ce49c3628b46c8
I reverted the commit (had to be done manually), and everything is rock
I was having disconnects after kernel 2.6.26 with a usb harddrive on an
intel mac mini. No USB quirks, or max sector changes helped. in the end
I traced the issue to kernel commit
b963801164618e25fbdc0cd452ce49c3628b46c8
I reverted the commit (had to be done manually), and everything is rock
makes more sense instead of having just a file with the credentials, you could
just have a file with additional parameters.
You can of course then include the credentials with username=xxx,password=xxx
this way you can include other options that you might need such as uid,gid,
nounix etc
**
makes more sense instead of having just a file with the credentials, you could
just have a file with additional parameters.
You can of course then include the credentials with username=xxx,password=xxx
this way you can include other options that you might need such as uid,gid,
nounix etc
**
has this been removed in natty ? I am now running i5-2500k with maverick
and the latest xorg code from the xorg-edgers ppa and i just had to
remove this patch to get compiz working on my setup. can't see any
problems so far.
--
You received this bug notification because you are a member of
Sorry, i thought i was looking at the natty source and i wasnt. looks
like it is removed or at least its not in the file referenced. sorry to
jump on this closed bug too. Cheers.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Something like this should do the trick
** Patch added: autofscred.patch
https://bugs.launchpad.net/ubuntu/+source/autofs5/+bug/530051/+attachment/1747370/+files/autofscred.patch
** Tags added: maverick
--
Autofs and semiautomatic credentials
https://bugs.launchpad.net/bugs/530051
You
Something like this should do the trick
** Patch added: autofscred.patch
https://bugs.launchpad.net/ubuntu/+source/autofs5/+bug/530051/+attachment/1747370/+files/autofscred.patch
** Tags added: maverick
--
Autofs and semiautomatic credentials
https://bugs.launchpad.net/bugs/530051
You
Can confirm this. I was also having this issue on lucid though too I'm
sure, and it also affecting scrolling. disabling KMS solves it here -
many thanks. Hopefully a new version of the driver can be rolled out on
ubunut.
** Changed in: xserver-xorg-video-ati (Ubuntu)
Status: New =
This was the closest bug I could find to an issue I have been having
with maverick built kernels and efi. some background first:
I have been building kernels on a linuxmint 9 (lucid) based system, for
a joggler device target (efi based device - see
http://en.wikipedia.org/wiki/O2_Joggler).
The
just to note with new mdadm 3.1.4+ it uses /dev/.mdadm/map for the
location which is available from the initramfs stage and once root is
mounted.
--
maps file not getting copied from initramfs to real rootfs (loosing state,
race, misconfig)
https://bugs.launchpad.net/bugs/550131
You received
What versions is your PPA good for?
It is for lucid. will also work on maverick. Don't use it on Karmic.
It seems like virtually all of the complexity is in init.d scripts and
udev rules to have things happen automatically. If you were willing to
just do an assemble manually and mount, or in a
I would say mdadm is rather more important than many other packages as
it is a core component for anyone wanting to use software raid, and as
something that is part tool part kernel driver, having it mismatched can
cause problems. Certainly more important than moving the window icons :)
Reading
Funnily enough I just updated a machine to maverick with it to test, and
it worked fine. btw i put it on a PPA
https://launchpad.net/~jools/+archive/mdadm if you are interested (apt-
add-repository ppa:jools/mdadm). note the version is slightly different
from the one i had before to make it more
Glad it's working for you. In regards to the device renaming, it's
because it didn't recognise the array as belonging to the machine so it
assembled it as md127 to not conflict with any other arrays. Please see
http://www.spinics.net/lists/raid/msg30175.html
You probably want to update your
Why has this been set to incomplete? The initial explanation is quite
clear. /var/run doesn't exist at the initramfs stage and it will fail.
If you updated to a new mdadm, this will use /dev/.mdadm folder for the
map file - this exists throughout the initramfs and is carried over once
root is
I explained slightly wrong, since my memory was vague. The old mdadm
2.7.1 in ubuntu probably makes the map file ok, but it won't get carried
across onto the rootfs. mdadm 3.1.2 wanted to place the map file in a
different location and failed. my solution at the time was to change the
location, and
Please demonstrate to me where the map file created in initramfs is then
copied to the root filesystem so it is available for mdadm at that
stage. It isn't! I'm not going to play the game setting the bug to
confirmed/invalid back and forth.
to fix this you need to either copy the map file to the
Just to follow up, I am now running my 3.1.4 package on my fileserver.
Would be interested to know if anyone else is using it, whilst we wait
for an official mdadm update.
--
Please upgrade to a non-outdated version
https://bugs.launchpad.net/bugs/495370
You received this bug notification
I finally got around to doing some upgrades on my fileserver. Thought
about switching back to debian, but I thought for now, I'll just get my
mdadm package working again properly on lucid.
http://malus.exotica.org.uk/~buzz/mdadm/lucid/
binaries for x86 are there.
you can build from source with
Yes it is a karmic package. Ii get a chance I could upgrade it to lucid.
Your fix is probably fine though. What we need though is someone as part
of ubuntu to maintain this though. I will never put ubuntu on a software
raid machine again :/
--
Please upgrade to a non-outdated version
Shouldn't happen. Might be safest right now to use the standard package
until I have time to take a look.
--
Please upgrade to a non-outdated version
https://bugs.launchpad.net/bugs/495370
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
yes its dangerous. debian most likely has completely difference
initramfs scripts. you could leave your machine unbootable. If you want
a newer version you can try my packages
http://malus.exotica.org.uk/~buzz/mdadm/
--
Please upgrade to a non-outdated version
I have not adapted a debian package to lucid, rather upgraded the ubuntu
package to a newer version and fixed some bugs. The package works fine
for me at least. Not sure about issue 26. I'd have to have a look. I'm
recently considering to upgrade to debian though on my system, as
ubuntu is letting
I'm slightly confused then since my scripts specifically copy to
/var/run/mdadm/map. mdadm.map is the third choice of mdadm should it not
be able to make files in the first location that is set in the makefile
config. however even if it did make a map file there in the initramfs,
my script wouldnt
The first version copied the map file to /var/run/map. I then changed my
mind as I saw ubuntu had a mdadm folder there, and I changed the
location to /var/run/mdadm/map. I'm running the 3.1.2-0ubuntu2 version
and the map file is working correctly from the mdadm folder.
--
Please upgrade to 3.1.x
I have jo...@aero:~$ ls -l /var/run/mdadm/map
-rw--- 1 root root 54 2010-04-21 22:27 /var/run/mdadm/map
Btw I did try making the initramfs folder from the hook, but it never
worked. I wonder if it ignores empty folders, which is why i went for
the init-top script instead.
--
Please upgrade
I haven't sorted a ppa yet, but I stuck my package up here
http://malus.exotica.org.uk/~buzz/mdadm/
My changes:
3.1.2 wants to put its map file by default at /var/run/map so
init-top script to make a /var/run folder for the map file (would be
better in initramfs init - but I only want to
many of the major problems are due to ubuntu shipping lucid with an 18
month old version of mdadm. Does feel as though raid is completely
maintained in Ubuntu currently.
--
mdadm --create with typo overwrites device file
https://bugs.launchpad.net/bugs/215542
You received this bug notification
Unmaintained i mean .. (my spellchecker says it's not a word but I don't
care) :)
If someone could update ubuntu to mdadm 3.1.2 I'm sure we could close
many of the bugs.
** Changed in: mdadm (Ubuntu)
Status: Incomplete = Confirmed
--
mdadm --create with typo overwrites device file
Due to the state/age of mdadm and raid on ubuntu, I've been seriously
considering switching back to debian. Currently I am running my own
package of 3.1.2 based on ubuntu's package (with the hotplug\udev way of
building arrays). I basically grabbed the ubuntu source, uupdated, and
manually fixed
(and i changed the path mdadm uses to store its map file when
constructing arrays on boot from initramfs), although the better fix is
to add the missing folder /var/run/mdadm to the mdadm initramfs script i
guess.
--
Please upgrade to 3.1.x for lucid
https://bugs.launchpad.net/bugs/495370
You
I wouldn't say I'm good at building packages, but I know how to update
existing ones a little.. Didn't try getting the map files across from
the initramfs to the root fs. Does mdadm require it once the array is
already constructed ?
--
Please upgrade to 3.1.x for lucid
It's worth noting (as I reported on #531748) that autofs4 came with such
functionality and you can actually use the /etc/auto.smb from autofs4
with autofs5 to get the credentials facility back.
--
Autofs and semiautomatic credentials
https://bugs.launchpad.net/bugs/530051
You received this bug
I can confirm I am also having this problem.
Running Lucid Beta 1
** Changed in: svn-load (Ubuntu)
Status: New = Confirmed
--
svn-load can't connect to my repository
https://bugs.launchpad.net/bugs/509425
You received this bug notification because you are a member of Ubuntu
Bugs, which
2.6.7 has bugs when resuming a reshape. 3.1.2 is the current release.
2.6.7 is ~18 months old. Please can we have an updated mdadm ? mdadm
3.1.2 along with kernel 2.6.32 has support for many many new features
also, which are useful including conversion between raid 1/5/6 as well
as many bug fixes
Just to add to this. 2.6.7.x is pretty old and it has major problems as
mentioned. Please bring us up to date! I think 2.6.7 was released some
18 months ago. Many new abilities such as raid 1 to raid 5 reshaping are
also not available even though we have the kernel version for such
stuff.
--
Public bug reported:
Binary package hint: autofs5
in autofs4, the /etc/auto.smb file had functionality to get credentials
from /etc/auto.smb.$key (host). This seems to have been lost with
autofs5. The /etc/auto.smb works fine with autofs5, but you might want
to just take the credfile features
** Attachment added: auto.smb
http://launchpadlibrarian.net/40132719/auto.smb
--
autofs5 auto.smb has lost some user/password features that were available in
autofs4
https://bugs.launchpad.net/bugs/531748
You received this bug notification because you are a member of Ubuntu
Bugs, which is
88 matches
Mail list logo
