[Bug 294941] Re: X locks up [use folder view to reproduce it]
Here is the backtrace: Backtrace: 0: /usr/bin/X(xorg_backtrace+0x26) [0x4ee236] 1: /usr/bin/X(mieqEnqueue+0x23f) [0x4cebbf] 2: /usr/bin/X(xf86PostMotionEventP+0xc4) [0x478754] 3: /usr/bin/X(xf86PostMotionEvent+0xb1) [0x478931] 4: /usr/lib/xorg/modules/input//evdev_drv.so [0x7f96d50ba83f] 5: /usr/bin/X [0x497c45] 6: /usr/bin/X [0x46f047] 7: /lib/libpthread.so.0 [0x7f96dac610f0] 8: /usr/lib/xorg/modules/drivers//nvidia_drv.so [0x7f96d6a786b7] 9: /usr/lib/libpixman-1.so.0 [0x7f96da3c8c6e] 10: /usr/lib/libpixman-1.so.0 [0x7f96da3dcbdb] 11: /usr/lib/libpixman-1.so.0 [0x7f96da3db96a] 12: /usr/lib/libpixman-1.so.0 [0x7f96da3e0984] 13: /usr/lib/libpixman-1.so.0(pixman_image_composite+0x79f) [0x7f96da3e05ef] 14: /usr/lib/xorg/modules//libwfb.so(wfbComposite+0x1ba) [0x7f96d633bc5a] 15: /usr/lib/xorg/modules/drivers//nvidia_drv.so [0x7f96d6a89556] 16: /usr/bin/X [0x531e98] 17: /usr/bin/X [0x5210da] 18: /usr/bin/X(Dispatch+0x364) [0x44d754] 19: /usr/bin/X(main+0x45d) [0x43376d] 20: /lib/libc.so.6(__libc_start_main+0xe6) [0x7f96d9203466] 21: /usr/bin/X [0x432b49] ERROR: Server Lockup! Stuck in an infinite loop. See backtrace above. ERROR: Server Lockup! Stuck in an infinite loop. See backtrace above. ERROR: Server Lockup! Stuck in an infinite loop. See backtrace above. ERROR: Server Lockup! Stuck in an infinite loop. See backtrace above. ERROR: Server Lockup! Stuck in an infinite loop. See backtrace above. ERROR: Server Lockup! Stuck in an infinite loop. See backtrace above. ERROR: Server Lockup! Stuck in an infinite loop. See backtrace above. ERROR: Server Lockup! Stuck in an infinite loop. See backtrace above. and so on and so on (more than 100lines "ERROR: Server Lockup! Stuck in an infinite loop. See backtrace above.") -- X locks up [use folder view to reproduce it] https://bugs.launchpad.net/bugs/294941 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 276518] Re: Xorg hangs due to EQ overflowing
Here is the backtrace: Backtrace: 0: /usr/bin/X(xorg_backtrace+0x26) [0x4ee236] 1: /usr/bin/X(mieqEnqueue+0x23f) [0x4cebbf] 2: /usr/bin/X(xf86PostMotionEventP+0xc4) [0x478754] 3: /usr/bin/X(xf86PostMotionEvent+0xb1) [0x478931] 4: /usr/lib/xorg/modules/input//evdev_drv.so [0x7f96d50ba83f] 5: /usr/bin/X [0x497c45] 6: /usr/bin/X [0x46f047] 7: /lib/libpthread.so.0 [0x7f96dac610f0] 8: /usr/lib/xorg/modules/drivers//nvidia_drv.so [0x7f96d6a786b7] 9: /usr/lib/libpixman-1.so.0 [0x7f96da3c8c6e] 10: /usr/lib/libpixman-1.so.0 [0x7f96da3dcbdb] 11: /usr/lib/libpixman-1.so.0 [0x7f96da3db96a] 12: /usr/lib/libpixman-1.so.0 [0x7f96da3e0984] 13: /usr/lib/libpixman-1.so.0(pixman_image_composite+0x79f) [0x7f96da3e05ef] 14: /usr/lib/xorg/modules//libwfb.so(wfbComposite+0x1ba) [0x7f96d633bc5a] 15: /usr/lib/xorg/modules/drivers//nvidia_drv.so [0x7f96d6a89556] 16: /usr/bin/X [0x531e98] 17: /usr/bin/X [0x5210da] 18: /usr/bin/X(Dispatch+0x364) [0x44d754] 19: /usr/bin/X(main+0x45d) [0x43376d] 20: /lib/libc.so.6(__libc_start_main+0xe6) [0x7f96d9203466] 21: /usr/bin/X [0x432b49] ERROR: Server Lockup! Stuck in an infinite loop. See backtrace above. ERROR: Server Lockup! Stuck in an infinite loop. See backtrace above. ERROR: Server Lockup! Stuck in an infinite loop. See backtrace above. ERROR: Server Lockup! Stuck in an infinite loop. See backtrace above. ERROR: Server Lockup! Stuck in an infinite loop. See backtrace above. ERROR: Server Lockup! Stuck in an infinite loop. See backtrace above. ERROR: Server Lockup! Stuck in an infinite loop. See backtrace above. ERROR: Server Lockup! Stuck in an infinite loop. See backtrace above. and so on and so on (more than 100lines "ERROR: Server Lockup! Stuck in an infinite loop. See backtrace above.") or please also see https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/294941 (Xpost is a bad idea but here I thing it could help). Xavier -- Xorg hangs due to EQ overflowing https://bugs.launchpad.net/bugs/276518 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 297543] Re: Update Package: nVidia 180.06
nvidia release cycle is such as we get fully usable "beta" drivers. Should we remove all the softwares with a version number < 1.0 from the repositories? ;) "beta" or "release" is not a problem: It works! Other drivers do not work. Xavier On Wed, Dec 3, 2008 at 8:17 AM, ma2412ma <[EMAIL PROTECTED]> wrote: > Why not? If the beta happens to be way better than the previous stable > release where's the problem? > > -- > Update Package: nVidia 180.06 > https://bugs.launchpad.net/bugs/297543 > You received this bug notification because you are a direct subscriber > of the bug. > > Status in Intrepid Ibex Backports: New > Status in "nvidia-graphics-drivers-177" source package in Ubuntu: Fix > Released > Status in "nvidia-graphics-drivers-180" source package in Ubuntu: Fix > Released > Status in nvidia-graphics-drivers-177 in Ubuntu Intrepid: In Progress > Status in nvidia-graphics-drivers-180 in Ubuntu Intrepid: In Progress > Status in nvidia-graphics-drivers-177 in Ubuntu Jaunty: Fix Released > Status in nvidia-graphics-drivers-180 in Ubuntu Jaunty: Fix Released > > Bug description: > Release Highlights, 180.06 > > http://www.nvnews.net/vbulletin/showthread.php?t=123072 > >* Added support for CUDA 2.1. >* Added initial support for PureVideo-like features on Linux via the new > VDPAU API (see the vdpau.h header file installed withthe driver). >* Added new workstation performance optimizations. >* Enabled the X Render "GlyphCache" by default. >* Disabled shared memory X pixmaps by default; see the"AllowSHMPixmaps" > option. >* Fixed a regression that could result in window decorationcorruption > when running Compiz using Geforce 6 and 7 series GPUs. >* Improved X pixmap placement on GeForce 8 series and later GPUs. >* Improved compatibility with recent Linux kernels. >* Improved stability on some GeForce 8 series and newer GPUs. > > > Release Highlights, 177.82: > >* Added support for the following new GPUs: > o Quadro NVS 450 > o Quadro FX 370 LP > o Quadro FX 5800 > o Quadro FX 4800 > o Quadro FX 470 > o Quadro CX >* Fixed a problem on recent mobile GPUs that caused a power management > resume from S3 to take 30+ seconds. >* Fixed a problem with hotkey switching on some recent mobile GPUs. >* Fixed an image corruption issue seen in FireFox 3. > > http://www.nvnews.net/vbulletin/showthread.php?p=1842773 > > Tested without any notable issues. Test with Jaunty ? > -- Update Package: nVidia 180.06 https://bugs.launchpad.net/bugs/297543 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 297543] Re: Update Package: nVidia 180.06
Noel J. Bergman wrote: > Another vote for 180.x as an Intrepid backport or at least a PPA, and > available in Jaunty. > Please post at least your configuration (you nvidia card) Xavier -- Update Package: nVidia 180.06 https://bugs.launchpad.net/bugs/297543 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 297543] Re: Update Package: nVidia 180.06
> I don't think they'll have a need to put this as an update while it's
> labelled as a 'beta' by nVidia (who use the term 'beta' properly).
>
Well ok maybe...but without this driver kde4 is not usable.
plasmoid just freeze if you have a geforce 8600.
The end user does not care if it is a beta or not.
The end user says "ho look kde4.1 is crap. I cannot use it on my box. It
is so unstable :(".
I'm not such an end user but I can understand this.
I have never see a bug in this new beta driver.
It does the job. The previous one does not.
Xavier
--
Update Package: nVidia 180.06
https://bugs.launchpad.net/bugs/297543
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 294941] Re: X locks up [use folder view to reproduce it]
** Attachment removed: "bt.txt" http://launchpadlibrarian.net/19443802/bt.txt -- X locks up [use folder view to reproduce it] https://bugs.launchpad.net/bugs/294941 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 294941] Re: X locks up [use folder view to reproduce it]
Well I'm just not able to reproduce it with the new nvidia driver x86_64-180.06 ...looks like a bug in close source nvidia drivers... 01:00.0 VGA compatible controller: nVidia Corporation GeForce 8600M GT (rev a1) Subsystem: Dell Device 01f1 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: nvidia Kernel modules: nvidia, nvidiafb Section "Screen" Identifier "Default Screen" Monitor "Configured Monitor" Device "Configured Video Device" DefaultDepth24 Option "RenderAccel" "True" Option "AllowGLXWithComposite" "True" Option "AddARGBGLXVisuals" "True" Option "PixmapCacheSize" "100" Option "AllowSHMPixmaps" "0" EndSection Section "Module" Load"glx" EndSection Section "Device" Identifier "Configured Video Device" Driver "nvidia" Option "NoLogo""True" EndSection Section "ServerFlags" Option "Xinerama" "0" EndSection -- X locks up [use folder view to reproduce it] https://bugs.launchpad.net/bugs/294941 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 298306] Re: Add nvidia-180 proprietary driver
Not only :) It looks like this version fixes this bug : https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/294941 (or at least I'm not able to reproduce this bug anymore.) -- Add nvidia-180 proprietary driver https://bugs.launchpad.net/bugs/298306 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 297543] Re: Update Package: nVidia 180.06
Same for me :) All the bugs using kde4 are gone. I'm going to test a .deb package of 180.06 as soon as it is available for Intrepid. To put it in a clear way: user experience of kwin is very poor with 177.82 because it buggy. I hope that there is a plan to propose this new driver (180 and the upcoming stable branch derived from 180) in intrepid. 177.82 is better but not sufficient to restore a good user experience of kwin (at least on my box (geforce 8 series)) -- Update Package: nVidia 180.06 https://bugs.launchpad.net/bugs/297543 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 389942] Re: python-nose is broken in Karmic alpha 2
After a manual update to nose version 0.11.0 it is still fully broken the exact same way. There is something broken here but I'm not sure what the root cause is... -- python-nose is broken in Karmic alpha 2 https://bugs.launchpad.net/bugs/389942 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 389942] Re: python-nose is broken in Karmic alpha 2
It works fine with python2.5 but not with Python 2.6.2+ (release26-maint, Jun 19 2009, 15:16:33) -- python-nose is broken in Karmic alpha 2 https://bugs.launchpad.net/bugs/389942 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 383248] [NEW] python-qwt5-qt4 cannot be installed on karmic
Public bug reported: Binary package hint: python-qwt5-qt4 python-qwt5-qt4 should not depend on python (< 2.6) but on python2.6 Current error message on up to date karmic: "The following packages have unmet dependencies: python-qwt5-qt4: Depends: python (< 2.6) but 2.6.2-0ubuntu1 is to be installed" ** Affects: pyqwt5 (Ubuntu) Importance: Undecided Status: New -- python-qwt5-qt4 cannot be installed on karmic https://bugs.launchpad.net/bugs/383248 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 325252] Re: Regression: cannot connect to WPA-PSK (TKIP encryption) wireless network with network manager plasmoid
Ok it does not work with WPA-PSK/network manager plasmoid/karmic (same way as already described). It used to work with Jaunty. I do work well with wicd. I can test whatever is needed to solve that problem. Which logs do you need (from network manager and/or wicd)? Let's see if we can kill this bug. -- Regression: cannot connect to WPA-PSK (TKIP encryption) wireless network with network manager plasmoid https://bugs.launchpad.net/bugs/325252 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to plasma-widget-network-manager in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 389942] Re: python-nose is broken in Karmic alpha 2
The problem is still there and is quite puzzling: http://groups.google.com/group/nose-users/browse_thread/thread/ab603fb160cc2d9c -- python-nose is broken in Karmic alpha 2 https://bugs.launchpad.net/bugs/389942 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 389942] Re: python-nose is broken in Karmic alpha 2
Andrew Straw wrote:
> It seems a difference between -0ubuntu1 and -0ubuntu2 (jaunty and karmic
> alpha 2) is this. It looks very relevant.
>
> --- a/Lib/unittest.py
> +++ b/Lib/unittest.py
> @@ -798,8 +798,10 @@ Examples:
> in MyTestCase
> """
> def __init__(self, module='__main__', defaultTest=None,
> - argv=None, testRunner=TextTestRunner,
> + argv=None, testRunner=None,
> testLoader=defaultTestLoader):
> +if testRunner is None:
> +testRunner = TextTestRunner
> if type(module) == type(''):
> self.module = __import__(module)
> for part in module.split('.')[1:]:
>
>
https://bugs.launchpad.net/ubuntu/+source/python-defaults/+bug/395362
--
python-nose is broken in Karmic alpha 2
https://bugs.launchpad.net/bugs/389942
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 395362] [NEW] unittest is broken
Public bug reported:
Hi,
Bug 389942 is caused by this difference between -0ubuntu1 and -0ubuntu2 (jaunty
and karmic):
--- a/Lib/unittest.py
+++ b/Lib/unittest.py
@@ -798,8 +798,10 @@ Examples:
in MyTestCase
"""
def __init__(self, module='__main__', defaultTest=None,
- argv=None, testRunner=TextTestRunner,
+ argv=None, testRunner=None,
testLoader=defaultTestLoader):
+if testRunner is None:
+testRunner = TextTestRunner
if type(module) == type(''):
self.module = __import__(module)
for part in module.split('.')[1:]:
This changes fully breaks python-nose this way:
nosetests
Traceback (most recent call last):
File "/usr/bin/nosetests", line 8, in
load_entry_point('nose==0.10.4', 'console_scripts', 'nosetests')()
File "/usr/lib/pymodules/python2.6/nose/core.py", line 219, in
__init__
argv=argv, testRunner=testRunner, testLoader=testLoader)
File "/usr/lib/python2.6/unittest.py", line 819, in __init__
self.runTests()
File "/usr/lib/pymodules/python2.6/nose/core.py", line 298, in
runTests
result = self.testRunner.run(self.test)
TypeError: unbound method run() must be called with TextTestRunner
instance as first argument (got ContextSuite instance instead)
If you revert this patch, nosetests is working again.
What was the driver of this patch? Would it break something if you revert
it?...as least it would fix python-nose.
** Affects: python-defaults (Ubuntu)
Importance: Undecided
Status: New
--
unittest is broken
https://bugs.launchpad.net/bugs/395362
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 395362] Re: unittest is broken
*** This bug is a duplicate of bug 389942 ***
https://bugs.launchpad.net/bugs/389942
> *** This bug is a duplicate of bug 389942 ***
> https://bugs.launchpad.net/bugs/389942
>
> Hi Xavier,
>
> As you note in your bug description, there is already a bug filed for
> this issue. Therefore, I'm marking this bug as a duplicate, and will
> open a python2.6 task on the parent bug.
>
> I will not open a python-defaults task on the parent bug because I see
> no reason why python-defaults is involved.
>
> ** This bug has been marked a duplicate of bug 389942
>python-nose is broken in Karmic alpha 2
>
>
Hi,
Well the point is that python2.6.2.tgz from python.org do not show this
patch on Lib/unittest.py. It reads:
def __init__(self, module='__main__', defaultTest=None,
argv=None, testRunner=TextTestRunner,
testLoader=defaultTestLoader):
if type(module) == type(''):
self.module = __import__(module)
for part in module.split('.')[1:]:
self.module = getattr(self.module, part)
Why is unittest.py patched by python2.6_2.6.2-0ubuntu2.diff this way?:
+--- Lib/unittest.py(.../tags/r262)(Revision 73476)
Lib/unittest.py(.../branches/release26-maint)(Revision 73476)
+@@ -798,8 +798,10 @@
+in MyTestCase
+ """
+ def __init__(self, module='__main__', defaultTest=None,
+- argv=None, testRunner=TextTestRunner,
++ argv=None, testRunner=None,
+ testLoader=defaultTestLoader):
++if testRunner is None:
++testRunner = TextTestRunner
+ if type(module) == type(''):
+ self.module = __import__(module)
+ for part in module.split('.')[1:]:
unittest.py comes from python2.6 that is why I have opened this bug
(but maybe it is not good practice. Please tell me).
Will this patch on unittest.py part of python2.6.3 ?
Should python-nose try to accomadate with this patch ?
Xavier
--
unittest is broken
https://bugs.launchpad.net/bugs/395362
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 378464] [NEW] mimms should not depend on python2.5
Public bug reported: Binary package hint: mimms mimms should not depend on python2.5 but only on python2.6. ** Affects: mimms (Ubuntu) Importance: Undecided Status: New -- mimms should not depend on python2.5 https://bugs.launchpad.net/bugs/378464 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 259808] Re: X Lockup in Intrepid (infinite loop)
Ok...at least 6hours without a freeze...the bug could really be in Xinerama :) Now we have to figure out why... -- X Lockup in Intrepid (infinite loop) https://bugs.launchpad.net/bugs/259808 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 259808] Re: X Lockup in Intrepid (infinite loop)
:( "I can easily reproduce it when i use "Folder view" plasmoid... When i click on a file within folder view or when i try to select multiple files..." Indeed...X lockups each time I do that. Each time I get get "[mi] EQ overflowing. The server is probably stuck in an infinite loop." in Xorg.0.log. Can someone please confirm that the bug is present not only on kubuntu but also on ubuntu? -- X Lockup in Intrepid (infinite loop) https://bugs.launchpad.net/bugs/259808 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 259808] Re: X Lockup in Intrepid (infinite loop)
"Bad" news: I'm not able to reproduce this bug on my box using the nv driver. So, either it is a bug in nvidia driver and we have to wait for a fix, either it is a bug on the open source side. It can be in the kernel (drm and so on), in Xorg or even, in qt or in kde.. I used to play with gdb/valgring but if someone could tell me how I'm supposed to start X and plasma so that I could get a useful backtrace if would be nice. If someone can reproduce that using the nv driver please let us know asap :) -- X Lockup in Intrepid (infinite loop) https://bugs.launchpad.net/bugs/259808 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 259808] Re: X Lockup in Intrepid (infinite loop)
Hum ok but I would like to see someone using ubuntu (and not kubuntu) able to reproduce that. My point is the following : Are we sure it does not come from qt/kde trying to ask the X server do something fully wrong? Ok ok it looks like it is a bug at a lower level... -- X Lockup in Intrepid (infinite loop) https://bugs.launchpad.net/bugs/259808 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 259808] Re: X Lockup in Intrepid (infinite loop)
Using KDE or gnome? -- X Lockup in Intrepid (infinite loop) https://bugs.launchpad.net/bugs/259808 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 240823] Re: UKenglish hyphenation patterns don't work with babel
On a fresh intrepid install (not an update), I get this: test.tex:0: No hyphenation patterns were loaded for(babel) the language `French'(babel) I will use the patterns loaded for \language=0 instead. Looks like hyphenation is fully broken on intrepid. sudo update-language sudo fmtutil-sys --all do not help. I hope that there is an easy fix/workaroud because latex without hyphenation is something not really usable. Xavier -- UKenglish hyphenation patterns don't work with babel https://bugs.launchpad.net/bugs/240823 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 240823] Re: UKenglish hyphenation patterns don't work with babel
Oups sorry for the noise. Please ignore my last comment. -- UKenglish hyphenation patterns don't work with babel https://bugs.launchpad.net/bugs/240823 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 259808] Re: X Lockup in Intrepid (infinite loop)
Same issue here on a fresh intreprid install (not an update from 8.04): Total xorg freeze during ~20s and "[mi] EQ overflowing" in the xorg log. nvidia 177.80 is installed. I'm on a laptop, only one screen, nothing but the automatically generated xorg.conf (no extra options). One usb mouse always plugged. I would be happy to test whatever you want to find where it comes from. Xavier -- X Lockup in Intrepid (infinite loop) https://bugs.launchpad.net/bugs/259808 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 259808] Re: X Lockup in Intrepid (infinite loop)
Ok I have updated the kernel and some kde package via apt-get dist-upgrade but I still have the same problem. No improvement. It would be nice to have one xorg maintainer here to tell us what we should do to help in an as efficient as possible way. My config : nvidia driver (and not nv), one screen only, xinerama off in xorg.conf. A fresh and up to date intrepid kubuntu (no upgrade from 8.04 but a fully new install). X lockup during at least 10s. No real way to know what triggers that bug but I occurs each time I try to select files in a plamoid directory view. [mi] mieqEnequeue: out-of-order valuator event; dropping. [mi] EQ overflowing. The server is probably stuck in an infinite loop. -- X Lockup in Intrepid (infinite loop) https://bugs.launchpad.net/bugs/259808 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 294941] [NEW] X locks up [use folder view to reproduce it]
Public bug reported: I come from 259808 and open this one for clarification: My config : nvidia driver (and not nv), one screen only, xinerama off in xorg.conf. A fresh and up to date intrepid kubuntu (no upgrade from 8.04 but a fully new install). X lockup during at least 10s. No real way to know what triggers that bug but I occurs each time I try to select files in a plamoid "folder view". I get this error message each time I get a X lock up [mi] mieqEnequeue: out-of-order valuator event; dropping. [mi] EQ overflowing. The server is probably stuck in an infinite loop. I'm going to apply the patch https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/259808/comments/48 asap. Up to now, I have this backtrace (bt.txt) Bryce: As said, I'm going to apply your patch. I can also do whatever would help to kill this bug. ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New -- X locks up [use folder view to reproduce it] https://bugs.launchpad.net/bugs/294941 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 294941] Re: X locks up [use folder view to reproduce it]
** Attachment added: "bt.txt" http://launchpadlibrarian.net/19443802/bt.txt -- X locks up [use folder view to reproduce it] https://bugs.launchpad.net/bugs/294941 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 259808] Re: Confusing error message printed when X locks up. Needs clarification.
Thanks a lot for the link and the patch. Please see : https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/294941 -- Confusing error message printed when X locks up. Needs clarification. https://bugs.launchpad.net/bugs/259808 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 294941] Re: X locks up [use folder view to reproduce it]
Hum on which version of mieq.c should I apply your patch from https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/259808/comments/48 ? If I try to apply it on mieq.c comming from apt-get source xorg-server, I get this: patching file mieq.c Hunk #1 FAILED at 126. Hunk #2 succeeded at 133 with fuzz 1 (offset -23 lines). Hunk #3 FAILED at 147. 2 out of 3 hunks FAILED -- saving rejects to file mieq.c.rej Do you already have newer version of mieq.c or am I doing something wrong? -- X locks up [use folder view to reproduce it] https://bugs.launchpad.net/bugs/294941 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 259808] Re: Confusing error message printed when X locks up. Needs clarification.
lockup-err-msg-cleanup.patch looks great to get a backtrace when X lockups. The problem is that I cannot figure out on which version of mieq.c should be patched. It is easy to modify this patch so that is can be applied on mieq.c you get viq apt-get source but it doesn't compile (xorg-backtrace() is not definied). Could someone tell me how I can get the correct set of files to perform this test. -- Confusing error message printed when X locks up. Needs clarification. https://bugs.launchpad.net/bugs/259808 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 314191] [NEW] brightness is jumping around on a dell 9''
Public bug reported: Binary package hint: kdemultimedia Hi, I'm using an up-to-date kubuntu ibex on a dell mini 9''. The problem is that the backlight brightness is jumping around. It looks like random. It jumps up and down without a simple pattern (AFAICS). /sys/class/backlight/acpi_video0/actual_brightness is always in between 0 and 15. The only workaround is to set the correct brightness using something like: echo 10 > /sys/class/backlight/acpi_video0/brightness && rmmod video (then of course the brightness is stable). Is works with the ubuntu preinstalled by dell. That is why I'm filling this bug report against kdemultimedia...but I'm not sure... It may be due to the fact that actual_brightness is only in a 0 15 range. ** Affects: kdemultimedia (Ubuntu) Importance: Undecided Status: New -- brightness is jumping around on a dell 9'' https://bugs.launchpad.net/bugs/314191 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdemultimedia in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 314191] Re: brightness is jumping around on a dell 9''
Indeed! and pkill krunner does the job. Please mark as duplicate of bug #278471. -- brightness is jumping around on a dell 9'' https://bugs.launchpad.net/bugs/314191 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdemultimedia in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 278471] Re: Screen flickers or blanks every 10 s with KDE4
Well I still have krunner in kde4.2 and no kephal (or am I missing something??) It is a problem 4.2 packaging from http://ppa.launchpad.net/kubuntu-experimental/ubuntu To sum up, I have to pkill krunner in 4.2 to kill this bug. -- Screen flickers or blanks every 10 s with KDE4 https://bugs.launchpad.net/bugs/278471 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdebase-workspace in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 318603] Re: /sys/class/backlight/ empty on a dell 9''
Solved by a kernel and bios update (respectively 2.6.28-5 and resvision A04). ** Changed in: linux (Ubuntu) Status: Incomplete => Fix Released -- /sys/class/backlight/ empty on a dell 9'' https://bugs.launchpad.net/bugs/318603 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 318603] [NEW] /sys/class/backlight/ empty on a dell 9''
Public bug reported: Binary package hint: linux-image-2.6.28-4-generic /sys/class/backlight/ is empty on my dell 9'' It prevents any tunning of the backlight level. Iµm not sure of the last kernel version providing me with a non empty /sys/class/backlight/ ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- /sys/class/backlight/ empty on a dell 9'' https://bugs.launchpad.net/bugs/318603 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 275980] Re: vlc is missing RTSP support
Low priority ok but it is quite annoying when your dsl provider provides you with TV via rtsp :(. A simple rebuild of the package with a trivial patch on the rules file is enough kill this bug. Please just add --enable-realrtsp (I must admit I haven't checked the build dep so far) ;). If there is a plan to update vlc in intrepid soon, please add this fix. -- vlc is missing RTSP support https://bugs.launchpad.net/bugs/275980 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 275980] Re: vlc is missing RTSP support
Well of course a small patch is also needed on the .install files (AFAICS). -- vlc is missing RTSP support https://bugs.launchpad.net/bugs/275980 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 318603] Re: /sys/class/backlight/ empty on a dell 9''
Here it is :) ** Attachment added: "dmesg.txt" http://launchpadlibrarian.net/21448284/dmesg.txt -- /sys/class/backlight/ empty on a dell 9'' https://bugs.launchpad.net/bugs/318603 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 318603] Re: /sys/class/backlight/ empty on a dell 9''
For info, /sys/class/backlight/ is *not* empty with a 2.6.27-7-generic (from the kubuntu 8.10 livecd) See the corresponding dmesg. ** Attachment added: "dmesg810.txt" http://launchpadlibrarian.net/21484035/dmesg810.txt -- /sys/class/backlight/ empty on a dell 9'' https://bugs.launchpad.net/bugs/318603 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 342839] Re: python-nose-10.3.1 incompatibility with python-2.6 in jaunty
The solution is to update to 0.10.4 See http://code.google.com/p/python-nose/issues/detail?id=161 for details -- python-nose-10.3.1 incompatibility with python-2.6 in jaunty https://bugs.launchpad.net/bugs/342839 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 389942] Re: python-nose is broken with python 2.6.3-dev
Where is the fix?? http://bugs.python.org/issue6177 does not provide the fix. It is the commit which *breaks* python-nose. -- python-nose is broken with python 2.6.3-dev https://bugs.launchpad.net/bugs/389942 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 389942] Re: python-nose is broken with python 2.6.3-dev
> Where is the fix??
> http://bugs.python.org/issue6177 does not provide the fix. It is the commit
> which *breaks* python-nose.
>
>
nosetests returns
Traceback (most recent call last):
File "/usr/bin/nosetests", line 8, in
load_entry_point('nose==0.11.1', 'console_scripts', 'nosetests')()
File "/usr/lib/pymodules/python2.6/nose/core.py", line 113, in __init__
argv=argv, testRunner=testRunner, testLoader=testLoader)
File "/usr/lib/python2.6/unittest.py", line 819, in __init__
self.runTests()
File "/usr/lib/pymodules/python2.6/nose/core.py", line 192, in runTests
result = self.testRunner.run(self.test)
TypeError: unbound method run() must be called with TextTestRunner
instance as first argument (got ContextSuite instance instead)
It is still broken.
Xavier
--
python-nose is broken with python 2.6.3-dev
https://bugs.launchpad.net/bugs/389942
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 406509] Re: saods9 package shows wrong dependencies
On jaunty but also on karmic. ds9 does not start. It fails with this message: version conflict for package "Tcl": have 8.4, need 8.5 couldn't open "/usr/lib/tclIndex": no such file or directory while executing "open [file join $dir tclIndex]" Please update. -- saods9 package shows wrong dependencies https://bugs.launchpad.net/bugs/406509 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 389942] Re: python-nose is broken with python 2.6.3-dev
Indeed :) Nose is still fully broken in karmic :( File "/usr/lib/pymodules/python2.6/nose/core.py", line 192, in runTests result = self.testRunner.run(self.test) TypeError: unbound method run() must be called with TextTestRunner instance as first argument (got ContextSuite instance instead) -- python-nose is broken with python 2.6.3-dev https://bugs.launchpad.net/bugs/389942 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 403156] [NEW] BUG in dvb-usb
Public bug reported: Binary package hint: linux-image-2.6.31-3-generic Insert a Digittrade-DVB-T-USB-Stick on a karmic kubuntu running Linux femto 2.6.31-3-generic 32bits. You get this BUG and this trace: 105.176144] usb 1-8: new high speed USB device using ehci_hcd and address 4 [ 105.312879] usb 1-8: configuration #1 chosen from 1 choice [ 105.395899] dvb-usb: found a 'Afatech AF9015 DVB-T USB2.0 stick' in cold state, will try to load a firmware [ 105.395922] usb 1-8: firmware: requesting dvb-usb-af9015.fw [ 105.455849] dvb-usb: downloading firmware from file 'dvb-usb-af9015.fw' [ 105.513565] BUG: unable to handle kernel paging request at f823716a [ 105.513592] IP: [] af9015_rw_udev+0x20a/0x2c0 [dvb_usb_af9015] [ 105.513624] *pde = 37010067 *pte = 7e5a6161 [ 105.513640] Oops: 0003 [#1] SMP [ 105.513653] last sysfs file: /sys/module/dvb_usb_af9015/initstate [ 105.513665] Modules linked in: dvb_usb_af9015(+) dvb_usb dvb_core michael_mic arc4 ecb ppdev bridge stp bnep cbc joydev dm_crypt aes_i586 aes_generic lp parport snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_pcm_oss snd_mixer_oss snd_pcm snd_seq_dummy snd_seq_oss snd_seq_midi b44 snd_rawmidi ssb snd_seq_midi_event snd_seq uvcvideo lib80211_crypt_tkip snd_timer videodev btusb v4l1_compat snd_seq_device wl(P) dell_wmi mmc_block dell_laptop snd psmouse pcspkr dcdbas sdhci_pci serio_raw sdhci soundcore lib80211 snd_page_alloc led_class r8169 mii fbcon tileblit font bitblit softcursor i915 drm i2c_algo_bit video output intel_agp agpgart [ 105.513816] [ 105.513825] Pid: 3417, comm: modprobe Tainted: P (2.6.31-3-generic #19-Ubuntu) Inspiron 910 [ 105.513832] EIP: 0060:[] EFLAGS: 00010207 CPU: 0 [ 105.513841] EIP is at af9015_rw_udev+0x20a/0x2c0 [dvb_usb_af9015] [ 105.513848] EAX: 0032 EBX: f4893d34 ECX: 000c EDX: [ 105.513854] ESI: f4893cbe EDI: f823716a EBP: f4893d0c ESP: f4893c98 [ 105.513860] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 105.513867] Process modprobe (pid: 3417, ti=f4892000 task=f691cb60 task.ti=f4892000) [ 105.513872] Stack: [ 105.513875] 0034 f4893cb8 07d0 0086 f4893cc4 001401e8 f4b34c00 [ 105.513890] <0> 0002 82f0 326a 007d4006 800cc012 00fa800c 800cc012 006480bb [ 105.513905] <0> a000 02010201 02010202 39020101 ee04fe18 d510aa0e 0d13c914 0106fb08 [ 105.513922] Call Trace: [ 105.513934] [] ? af9015_download_firmware+0xe7/0x130 [dvb_usb_af9015] [ 105.513956] [] ? dvb_usb_download_firmware+0x7e/0xd0 [dvb_usb] [ 105.513968] [] ? dvb_usb_device_init+0x257/0x310 [dvb_usb] [ 105.513980] [] ? af9015_usb_probe+0x83/0x12c [dvb_usb_af9015] [ 105.513993] [] ? usb_autopm_do_device+0x67/0xf0 [ 105.514002] [] ? usb_probe_interface+0x87/0x160 [ 105.514011] [] ? sysfs_create_link+0x12/0x20 [ 105.514021] [] ? really_probe+0x50/0x140 [ 105.514030] [] ? _spin_lock_irqsave+0x2a/0x40 [ 105.514039] [] ? driver_probe_device+0x19/0x20 [ 105.514047] [] ? __driver_attach+0x79/0x80 [ 105.514055] [] ? bus_for_each_dev+0x48/0x70 [ 105.514063] [] ? driver_attach+0x19/0x20 [ 105.514071] [] ? __driver_attach+0x0/0x80 [ 105.514079] [] ? bus_add_driver+0xbf/0x2a0 [ 105.514088] [] ? driver_register+0x65/0x120 [ 105.514096] [] ? usb_register_driver+0x79/0xe0 [ 105.514117] [] ? af9015_usb_module_init+0x1b/0x38 [dvb_usb_af9015] [ 105.514126] [] ? do_one_initcall+0x3f/0x190 [ 105.51
Re: [Bug 403156] [NEW] BUG in dvb-usb
and here is the upstream discussion: http://www.mail-archive.com/linux-me...@vger.kernel.org/msg07381.html Please apply. Xavier > Public bug reported: > > Binary package hint: linux-image-2.6.31-3-generic > > Insert a Digittrade-DVB-T-USB-Stick on a karmic kubuntu running Linux femto > 2.6.31-3-generic 32bits. > You get this BUG and this trace: > 105.176144] usb 1-8: new high speed USB device using ehci_hcd and address 4 > > [ 105.312879] usb 1-8: configuration #1 chosen from 1 choice > > [ 105.395899] dvb-usb: found a 'Afatech AF9015 DVB-T USB2.0 stick' in cold > state, will try to load a firmware > > [ 105.395922] usb 1-8: firmware: requesting dvb-usb-af9015.fw > > [ 105.455849] dvb-usb: downloading firmware from file 'dvb-usb-af9015.fw' > > [ 105.513565] BUG: unable to handle kernel paging request at f823716a > > [ 105.513592] IP: [] af9015_rw_udev+0x20a/0x2c0 [dvb_usb_af9015] > > [ 105.513624] *pde = 37010067 *pte = 7e5a6161 > > [ 105.513640] Oops: 0003 [#1] SMP > > [ 105.513653] last sysfs file: /sys/module/dvb_usb_af9015/initstate > > [ 105.513665] Modules linked in: dvb_usb_af9015(+) dvb_usb dvb_core > michael_mic arc4 ecb ppdev bridge stp bnep cbc joydev dm_crypt aes_i586 > aes_generic lp parport snd_hda_codec_realtek snd_hda_intel snd_hda_codec > snd_pcm_oss snd_mixer_oss snd_pcm snd_seq_dummy snd_seq_oss snd_seq_midi b44 > snd_rawmidi ssb snd_seq_midi_event snd_seq uvcvideo lib80211_crypt_tkip > snd_timer videodev btusb v4l1_compat snd_seq_device wl(P) dell_wmi mmc_block > dell_laptop snd psmouse pcspkr dcdbas sdhci_pci serio_raw sdhci soundcore > lib80211 snd_page_alloc led_class r8169 mii fbcon tileblit font bitblit > softcursor i915 drm i2c_algo_bit video output intel_agp agpgart > > [ 105.513816] > > [ 105.513825] Pid: 3417, comm: modprobe Tainted: P > (2.6.31-3-generic #19-Ubuntu) Inspiron 910 > > [ 105.513832] EIP: 0060:[] EFLAGS: 00010207 CPU: 0 > > [ 105.513841] EIP is at af9015_rw_udev+0x20a/0x2c0 [dvb_usb_af9015] > > [ 105.513848] EAX: 0032 EBX: f4893d34 ECX: 000c EDX: > > [ 105.513854] ESI: f4893cbe EDI: f823716a EBP: f4893d0c ESP: f4893c98 > > [ 105.513860] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 > > [ 105.513867] Process modprobe (pid: 3417, ti=f4892000 task=f691cb60 > task.ti=f4892000) > [ 105.513872] Stack: > > [ 105.513875] 0034 f4893cb8 07d0 0086 f4893cc4 > 001401e8 f4b34c00 > [ 105.513890] <0> 0002 82f0 326a 007d4006 800cc012 00fa800c > 800cc012 006480bb > [ 105.513905] <0> a000 02010201 02010202 39020101 ee04fe18 d510aa0e > 0d13c914 0106fb08 > [ 105.513922] Call Trace: > > [ 105.513934] [] ? af9015_download_firmware+0xe7/0x130 > [dvb_usb_af9015] > [ 105.513956] [] ? dvb_usb_download_firmware+0x7e/0xd0 [dvb_usb] > > [ 105.513968] [] ? dvb_usb_device_init+0x257/0x310 [dvb_usb] > > [ 105.513980] [] ? af9015_usb_probe+0x83/0x12c [dvb_usb_af9015] > > [ 105.513993] [] ? usb_autopm_do_device+0x67/0xf0 > > [ 105.514002] [] ? usb_probe_interface+0x87/0x160 > > [ 105.514011] [] ? sysfs_create_link+0x12/0x20 > > [ 105.514021] [] ? really_probe+0x50/0x140 > > [ 105.514030] [] ? _spin_lock_irqsave+0x2a/0x40 > > [ 105.514039] [] ? driver_probe_device+0x19/0x20 > > [ 105.514047] [] ? __driver_attach+0x79/0x80 > > [ 105.514055] [] ? bus_for_each_dev+0x48/0x70 > > [ 105.514063] [] ? driver_attach+0x19/0x20 > > [ 105.514071] [] ? __driver_attach+0x0/0x80 > > [ 105.514079] [] ? bus_add_driver+0xbf/0x2a0 > > [ 105.514088] [] ? driver_register+0x6
[Bug 403156] Re: BUG in dvb-usb
Linux image Version: 2.6.31-4.23. The problem is still the same.
Here is the patch:
Signed-off-by: Nils Kassube
---
--- orig/linux-2.6.31/drivers/media/dvb/dvb-usb/af9015.c2009-06-30
11:34:45.0 +0200
+++ linux-2.6.31/drivers/media/dvb/dvb-usb/af9015.c 2009-07-07
14:58:27.0 +0200
@@ -81,7 +81,6 @@
switch (req->cmd) {
case GET_CONFIG:
- case BOOT:
case READ_MEMORY:
case RECONNECT_USB:
case GET_IR_CODE:
@@ -100,6 +99,7 @@
case WRITE_VIRTUAL_MEMORY:
case COPY_FIRMWARE:
case DOWNLOAD_FIRMWARE:
+ case BOOT:
break;
default:
err("unknown command:%d", req->cmd);
--
BUG in dvb-usb
https://bugs.launchpad.net/bugs/403156
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 403156] Re: BUG in dvb-usb
apo wrote: > I can confirm for 2.6.31-5 (kubuntu karmic alpha 4) > > [ 3530.212193] usb 2-1: new high speed USB device using ehci_hcd and address > 4 > > [ 3530.348913] usb 2-1: configuration #1 chosen from 1 choice > > > [ 3530.368736] dvb-usb: found a 'Afatech AF9015 DVB-T USB2.0 stick' in cold > state, will try to load a firmware > > [ 3530.368749] usb 2-1: firmware: requesting dvb-usb-af9015.fw > > > [ 3530.437640] dvb-usb: downloading firmware from file 'dvb-usb-af9015.fw' > > > [ 3530.495125] BUG: unable to handle kernel paging request at > c900050db16a > > [ 3530.495141] IP: [] memcpy_c+0xb/0x20 > > > [ 3530.495159] PGD 11fc06067 PUD 11fc07067 PMD 11a421067 PTE 8000ac47c161 > > > [ 3530.495172] Oops: 0003 [#1] SMP > > > [ 3530.495180] last sysfs file: > /sys/devices/pci:00/:00:1d.7/usb2/2-1/firmware/2-1/loading > > [ 3530.495188] CPU 1 > > > [ 3530.495192] Modules linked in: tun binfmt_misc ppdev bridge stp bnep nfsd > exportfs nfs lockd nfs_acl auth_rpcgss sunrpc dm_crypt dvb_usb_af9015 dvb_usb > dvb_core coretemp uinpu t sbp2 lp parport joydev arc4 ecb snd_hda_codec_idt > iwlagn iwlcore snd_hda_intel snd_hda_codec mac80211 snd_pcm_oss snd_mixer_oss > snd_pcm dell_wmi sdhci_pci sdhci snd_seq_dummy p smouse snd_seq_oss > dell_laptop snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq ricoh_mmc > uvcvideo snd_timer dcdbas serio_raw cfg80211 usbhid led_class snd_seq_device > nvidia(P ) videodev v4l1_compat v4l2_compat_ioctl32 btusb snd soundcore > snd_page_alloc tg3 ohci1394 ieee1394 fbcon tileblit font bitblit softcursor > i915 drm i2c_algo_bit video output inte l_agp > > > [ 3530.495328] Pid: 259, comm: khubd Tainted: P 2.6.31-5-generic > #24-Ubuntu XPS M1330 > > [ 3530.495335] RIP: 0010:[] [] > memcpy_c+0xb/0x20 > > [ 3530.495346] RSP: 0018:88011b1d16c8 EFLAGS: 00010202 > > > [ 3530.495352] RAX: c900050db16a RBX: 88011b1d17a0 RCX: > 0006 > > [ 3530.495357] RDX: 0002 RSI: 88011b1d16f2 RDI: > c900050db16a > > [ 3530.495363] RBP: 88011b1d1770 R08: R09: > > > [ 3530.495369] R10: R11: R12: > 880104204000 > > [ 3530.495375] R13: 0008 R14: R15: > 88011b1d16f0 > > [ 3530.495382] FS: () GS:88002803c000() > knlGS: > > [ 3530.495389] CS: 0010 DS: 0018 ES: 0018 CR0: 8005003b > > > [ 3530.495394] CR2: c900050db16a CR3: 01001000 CR4: >
[Bug 395630] Re: Broadcom STA module is not loadable on karmic due to unknown symbols
** Changed in: bcmwl (Ubuntu) Status: Fix Released => Confirmed -- Broadcom STA module is not loadable on karmic due to unknown symbols https://bugs.launchpad.net/bugs/395630 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 395630] Re: Broadcom STA module is not loadable on karmic due to unknown symbols
On a fresh karmic on a dell mini: FATAL: Error inserting wl (/lib/modules/2.6.31-14-generic/updates/dkms/wl.ko): Unknown symbol in module, or unknown parameter (see dmesg) and in the dmesg: [ 51.603074] wl: disagrees about version of symbol lib80211_get_crypto_ops [ 51.603083] wl: Unknown symbol lib80211_get_crypto_ops dpkg -S lib80211.ko : linux-image-2.6.31-14-generic: /lib/modules/2.6.31-14-generic/kernel/net/wireless/lib80211.ko linux-backports-modules-2.6.31-14-generic: /lib/modules/2.6.31-14-generic/updates/cw/lib80211.ko Removing linux-backports-modules-2.6.31-14-generic does not help (same error message). BTW, with a "Network controller: Broadcom Corporation BCM4312 802.11b/g (rev 01)" which driver are we suppose to use?? b43? wl? In jaunty, I use to use wl and it was fine. -- Broadcom STA module is not loadable on karmic due to unknown symbols https://bugs.launchpad.net/bugs/395630 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 395630] Re: Broadcom STA module is not loadable on karmic due to unknown symbols
insmod /lib/modules/2.6.31-14-generic/kernel/net/wireless/lib80211.ko insmod /lib/modules/2.6.31-14-generic/kernel/net/wireless/lib80211_crypt_ccmp.ko insmod /lib/modules/2.6.31-14-generic/kernel/net/wireless/lib80211_crypt_tkip.ko insmod /lib/modules/2.6.31-14-generic/kernel/net/wireless/lib80211_crypt_wep.ko modprobe wl does work so the fix should be quite easy. -- Broadcom STA module is not loadable on karmic due to unknown symbols https://bugs.launchpad.net/bugs/395630 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 395630] Re: Broadcom STA module is not loadable on karmic due to unknown symbols
Never mind...Removing linux-backports-modules-2.6.31-14-generic does fix the pb. -- Broadcom STA module is not loadable on karmic due to unknown symbols https://bugs.launchpad.net/bugs/395630 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 406520] Re: libatlas3gf-sse2 zgemv function gives wrong result
Please remove this package from ubuntu. It's buggy. It does provide wrong numerical results. Wrong results (without a warning) is the worst thing you can get when you use atlas (old and supposibly robust). http://mail.scipy.org/pipermail/numpy-discussion/2010-January/047766.html You can remove this packqge because you provide a non sse version which is ok (maybe slower but bug free). -- libatlas3gf-sse2 zgemv function gives wrong result https://bugs.launchpad.net/bugs/406520 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 454898] Re: cryptsetup starts too early
Still fully broken. Unfortunately, I would have to understand how to tune the upstart sequence to try to fix this... Any comments? > ** Changed in: cryptsetup (Ubuntu) > Status: New => Confirmed > > -- cryptsetup starts too early https://bugs.launchpad.net/bugs/454898 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 395630] Re: Broadcom STA module is not loadable on karmic due to unknown symbols
On 11/16/2009 07:15 PM, QuentinHartman wrote: > removing linux-backports-modules-2.6.31-15-generic also worked for me, > however, I need that installed to allow the modules for vmware > workstation to build properly. So the process that I run through anytime > the kernel or vmware changes is: > > -Install backports-modules > -rebuild vmware kernel modules > -uninstall backports > -rebuild bcmwl (if the kernel is what changed) > > That's not a solution ;) backports-modules should stop to provide modules with a incompatible ABI compare to the one which is in the kernel mainlinebut I assume it is not that easy. Xavier -- Broadcom STA module is not loadable on karmic due to unknown symbols https://bugs.launchpad.net/bugs/395630 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 454898] Re: cryptsetup starts too early
> I confirm the problem on a EEE 901A. > I use an encrypted SD card for my home folder, and even if /etc/crypttab is > configured correctly I usually do not get a prompt at the splash screen. > However, I said "usually": sometimes I DO get the prompt as it should be, > typically when starting encrypted partitions is delayed by some reason, such > as a fsck of the root partition. > So if I have to guess it is really a timing issue. > > The bug is still there 4days before release :( I think a timer cannot solve this problem. A timer is never a proper fix when we have a sync pb. We need synchronization here. cryptsetup should not start before the end of disks detection. As we are switching to an async boot sequence, it may be hard...but it is mandatory. -- cryptsetup starts too early https://bugs.launchpad.net/bugs/454898 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 419173] [NEW] device notifier should not list luks paritions listed in fstab
Public bug reported: Binary package hint: plasma-widgets-workspace Hi, cryto luks partitions listed in /etc/fstab and already mounted at boot time should not be listed as "recently plugged devices" by the widget "device notifier" For instance I have this line in my fstab /dev/mapper/data/home/gnata/Data ext4defaults0 1 Data is mounted at boot time (as / is :)) that is why "device notifier" should ignore this partition. @+, Xavier ** Affects: kdebase-workspace (Ubuntu) Importance: Undecided Status: New -- device notifier should not list luks paritions listed in fstab https://bugs.launchpad.net/bugs/419173 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 419173] Re: device notifier should not list luks paritions listed in fstab
I'm using an up to date karmic so the bug in present in kde4.3.0. -- device notifier should not list luks paritions listed in fstab https://bugs.launchpad.net/bugs/419173 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 432584] Re: dpkg and emacs mutually exclusive
Same bug on my box: "the following packages have unmet dependencies: emacs22: Depends: emacs22-bin-common (= 22.2-0ubuntu3) but it is not going to be installed Depends: libasound2 (> 1.0.18) but it is not going to be installed Depends: libice6 (>= 1:1.0.0) but it is not going to be installed Depends: libsm6 but it is not going to be installed Depends: libxmu6 but it is not going to be installed Depends: libxt6 but it is not going to be installed Depends: xaw3dg (>= 1.5+E-1) but it is not going to be installed libc6: Depends: tzdata but it is not going to be installed" Well all these packages *are* installed. "http://archive.ubuntu.com karmic/main libice6 2:1.0.5-1" has for instance to be updated. -- dpkg and emacs mutually exclusive https://bugs.launchpad.net/bugs/432584 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 378464] Re: mimms should not depend on python2.5
Well what's the problem to close this one? -- mimms should not depend on python2.5 https://bugs.launchpad.net/bugs/378464 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 419173] Re: device notifier should not list luks paritions listed in fstab
Closed as non bug. See http://bugs.kde.org/show_bug.cgi?id=205277 ** Changed in: kde4libs (Ubuntu) Status: Triaged => Invalid -- device notifier should not list luks paritions listed in fstab https://bugs.launchpad.net/bugs/419173 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 403156] Re: BUG in dvb-usb
Fixed in 2.6.31-8-generic. ** Changed in: linux (Ubuntu) Status: New => Fix Released -- BUG in dvb-usb https://bugs.launchpad.net/bugs/403156 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 454898] Re: cryptsetup starts too early
Something has changed but that's not that good: It does not ask for the password during the boot. Worst, /etc/init.d/cryptdisks restart now hangs: * Stopping remaining crypto disks... * data (stopped)... [ OK ] * Starting remaining crypto disks... * data (starting) and it look like it's look in a infinite loop I may have done something wrong with the "proposed" update: udev Version: 147~-6 2.6.31-16-generic crypsetup Version: 2:1.0.6+20090405.svn49-1ubuntu7.1 Well the other pb is that it is only a test machine. That's why I'm going to install a Lynx on it. Let's see if it is fine with a fresh (and allready lucid) lynx. > Accepted cryptsetup into karmic-proposed, the package will build now and > be available in a few hours. Please test and give feedback here. See > https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to > enable and use -proposed. Thank you in advance! > > ** Changed in: cryptsetup (Ubuntu Karmic) > Status: In Progress => Fix Committed > > ** Tags added: verification-needed > > -- cryptsetup starts too early https://bugs.launchpad.net/bugs/454898 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 454898] Re: cryptsetup starts too early
> Also, when this hang occurs, please check whether you have multiple > 'watershed' processes running. If the boot-time cryptsetup has hung for > whatever reason, 'cryptdisks restart' will also hang waiting, to avoid > colliding with the one that's already running. > > ok. I stop /etc/init.d/cryptdisks restart (looping for ever) with crtl+c and then: ps aux |grep watershed root 886 0.0 0.0 1668 484 ?S14:57 0:00 /lib/udev/watershed /lib/cryptsetup/askpass Enter passphrase to unlock the disk /dev/mmcblk0p1 (data): root 988 0.0 0.0 1668 464 ?S14:57 0:00 /lib/udev/watershed /lib/cryptsetup/askpass Enter passphrase to unlock the disk /dev/mmcblk0p1 (data): but this message never appears during the boot process. I kill both watershedprocesses and then the /etc/init.d/cryptdisks restart is working fine: Enter passphrase to unlock the disk /dev/mmcblk0p1 (data): key slot 0 unlocked. Command successful. * data (started)... [ OK ] It looks like something starts during the boot but it is not a blocking call. It may explain why I do not see "Enter passphrase to unlock the disk /dev/mmcblk0p1 (data):" during the boot. This question remains unresponded and watershed is still alive waiting for an input. fstab: # proc/proc procdefaults0 0 # / was on /dev/sda2 during installation UUID=0fd38542-fff5-43ce-b78b-f11e0cea69a3 / ext4 errors=remount-ro 0 1 # swap was on /dev/sda1 during installation UUID=30240ff1-54bd-412f-bab0-757b788bf87f noneswap sw 0 0 /dev/mapper/data/home/gnata/data ext4defaults0 1 crypttab: # data /dev/mmcblk0p1none luks All these tests are performed on a new fresh karmic + dist-upgrade after insertion of "proposed" in the sources.list. -- cryptsetup starts too early https://bugs.launchpad.net/bugs/454898 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 454898] Re: cryptsetup starts too early
Well, using 'defaults,bootwait' it does work. However, I use a set of encrypted SDcards. If there is no card in the slot, it does not boot anymore (I only get a maintenance shell). That's why I put: /dev/mapper/data/home/gnata/data ext4defaults0 1 and not: /dev/mapper/data/home/gnata/data ext4defaults0 0 in the fstab (pass=1) Now, if I add bootwait, then it is like having pass=0. Ok, maybe it is just a bad idea to put SDcard in the fstab? (but I think that "pass=1 in the fstab" should address this usecase). Xaiver. -- cryptsetup starts too early https://bugs.launchpad.net/bugs/454898 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 454898] Re: cryptsetup starts too early
Steve, Ok I'm going to use "noauto". I'm not quite sure there is a point to support my usecase (too complex and too specific). You can set this bug to "won't fix". I'm fine with that. -- cryptsetup starts too early https://bugs.launchpad.net/bugs/454898 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 454898] [NEW] cryptsetup starts too early
Public bug reported: I hope that the tilte is correct. I have encrypted a sdcard using cryptsetup. During the boot sequence, it does not ask for the password. I fail to find an error message in the logs. I think my config is ok because /etc/init.d/cryptdisks start does work: * Starting remaining crypto disks... * data (starting) Enter passphrase to unlock the disk /dev/mmcblk0p1 (data): (I enter the password) key slot 0 unlocked. Command successful. data (started)... [ OK ] and then, "mount -a" mounts the encrypted partition. It looks like cryptsetup starts *before* /dev/mmcblk0p1 is created. That would explain why cryptsetup fails to see my encrypted disk at boot time. My config files: crypttab: # data /dev/mmcblk0p1none luks fstab: /dev/mapper/data/home/gnata/data ext4defaults0 1 ** Affects: ubuntu Importance: Undecided Status: New -- cryptsetup starts too early https://bugs.launchpad.net/bugs/454898 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1799550] Re: No way to encrypt at partition level (dual boot)
Any chance to see some progress on this topic in 21.10? It should be possible to encryt / without having to play with the command line, no matter if we are in dual boot or if we are not. It should be possible to /create/open a encrypted LUKS container and to install (k)ubuntu on it without having the use the command line. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1799550 Title: No way to encrypt at partition level (dual boot) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1799550/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1083038] Re: Encrypted LVM in Ubiquity unavailable when installing alongside an existing OS
Still one progress on this issue with 21.04. It is not possible to install an encrypted kubuntu 21.04 alongside windows in dual boot **without having to use the command line**. This is a *security issue* because non expert users won't be able to install an encrypted kubuntu. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1083038 Title: Encrypted LVM in Ubiquity unavailable when installing alongside an existing OS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1083038/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1083038] Re: Encrypted LVM in Ubiquity unavailable when installing alongside an existing OS
Read "no progress" and not "one progress" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1083038 Title: Encrypted LVM in Ubiquity unavailable when installing alongside an existing OS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1083038/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1799550] Re: No way to encrypt at partition level (dual boot)
No progress on this topic :( It is still not possible to install kubuntu 20.10 encrypted in dual boot with windows without having to deal with the command line. This is a security issue as it forces many beginners to go for a non encrypted installation. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1799550 Title: No way to encrypt at partition level (dual boot) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1799550/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1799550] Re: No way to encrypt at partition level (dual boot)
I might work with the ubuntu installer 20.10 (to be confirmed) but it does not work with the kubuntu installer. By 'it does not work' I mean 'the option is not given'. One has to create the LUKS, open it, then launch the installer and eventually use chroot to make it work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1799550 Title: No way to encrypt at partition level (dual boot) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1799550/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1773457] Re: Full-system encryption needs to be supported out-of-the-box including /boot and should not delete other installed systems
Well it's an issue indeed but the fact that no encryption is possible without having to deal with the command line is much worst. Le lun. 21 déc. 2020 à 22:15, Nodøn <1773...@bugs.launchpad.net> a écrit : > Encryption should also be possible without LVM. LVM is very good, but if > you are using for example BTRFS, you may don't want to use both at the > same time. Should just be an option. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1773457 > > Title: > Full-system encryption needs to be supported out-of-the-box including > /boot and should not delete other installed systems > > Status in grub2 package in Ubuntu: > Confirmed > Status in ubiquity package in Ubuntu: > Confirmed > > Bug description: > In today's world, especially with the likes of the EU's GDPR and the > many security fails, Ubuntu installer needs to support full-system > encryption out of the box. > > This means encrypting not only /home but also both root and /boot. The > only parts of the system that wouldn't be encrypted are the EFI > partition and the initial Grub bootloader, for obvious reasons. > > It should also not delete other installed systems unless explicitly > requested. > > On top of this, the previous method of encrypting data (ecryptfs) is > now considered buggy, and full-disk encryption is recommended as an > alternative. Unfortunately, the current implementation of full-disk > encryption wipes any existing OS such as Windows, making the > implementation unusable for most users. > > Now, using LUKS and LVM, it is already possible to have full-disk > encryption (strictly, full-partition encryption because it leaves any > existing OS alone), while encrypting /boot. Reference: > > https://help.ubuntu.com/community/ManualFullSystemEncryption > > ... but with one major limitation: Grub is incorrectly changed after > an update affecting the kernel or Grub, so that a manual Grub update > is required each time this happens (this is fully covered in the > linked instructions). > > If the incorrect Grub change is fixed, it should be (relatively) > simple to support full-system encryption in the installer. > > Further information (2018-08-17): > > The NCSC recommends, "Use LUKS/dm-crypt to provide full volume > encryption." > References: > • > https://blog.ubuntu.com/2018/07/30/national-cyber-security-centre-publish-ubuntu-18-04-lts-security-guide > • https://www.ncsc.gov.uk/guidance/eud-security-guidance-ubuntu-1804-lts > > **EDIT** > Refer to comment #47 for an alternative version. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1773457/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1773457 Title: Full-system encryption needs to be supported out-of-the-box including /boot and should not delete other installed systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1773457/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1773457] Re: Full-system encryption needs to be supported out-of-the-box including /boot and should not delete other installed systems
No it is not a grub issue. It's an issue with the installer which does not provide this option anymore. Wishlist..kind of but I think it is much closer to a big security issue than to a wishlist. The net result is that people do install kubuntu without any encryption. Le mar. 22 déc. 2020 à 19:40, Julian Andres Klode < 1773...@bugs.launchpad.net> a écrit : > ** Changed in: grub2 (Ubuntu) >Importance: Undecided => Wishlist > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1773457 > > Title: > Full-system encryption needs to be supported out-of-the-box including > /boot and should not delete other installed systems > > Status in grub2 package in Ubuntu: > Confirmed > Status in ubiquity package in Ubuntu: > Confirmed > > Bug description: > In today's world, especially with the likes of the EU's GDPR and the > many security fails, Ubuntu installer needs to support full-system > encryption out of the box. > > This means encrypting not only /home but also both root and /boot. The > only parts of the system that wouldn't be encrypted are the EFI > partition and the initial Grub bootloader, for obvious reasons. > > It should also not delete other installed systems unless explicitly > requested. > > On top of this, the previous method of encrypting data (ecryptfs) is > now considered buggy, and full-disk encryption is recommended as an > alternative. Unfortunately, the current implementation of full-disk > encryption wipes any existing OS such as Windows, making the > implementation unusable for most users. > > Now, using LUKS and LVM, it is already possible to have full-disk > encryption (strictly, full-partition encryption because it leaves any > existing OS alone), while encrypting /boot. Reference: > > https://help.ubuntu.com/community/ManualFullSystemEncryption > > ... but with one major limitation: Grub is incorrectly changed after > an update affecting the kernel or Grub, so that a manual Grub update > is required each time this happens (this is fully covered in the > linked instructions). > > If the incorrect Grub change is fixed, it should be (relatively) > simple to support full-system encryption in the installer. > > Further information (2018-08-17): > > The NCSC recommends, "Use LUKS/dm-crypt to provide full volume > encryption." > References: > • > https://blog.ubuntu.com/2018/07/30/national-cyber-security-centre-publish-ubuntu-18-04-lts-security-guide > • https://www.ncsc.gov.uk/guidance/eud-security-guidance-ubuntu-1804-lts > > **EDIT** > Refer to comment #47 for an alternative version. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1773457/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1773457 Title: Full-system encryption needs to be supported out-of-the-box including /boot and should not delete other installed systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1773457/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1773457] Re: Full-system encryption needs to be supported out-of-the-box including /boot and should not delete other installed systems
Right. https://bugs.launchpad.net/bugs/1799550 has been opened in 2018 to track the dual boot issue. This is the security issue I was referring to. Sorry for the confusion. Le mar. 22 déc. 2020 à 22:30, Julian Andres Klode < 1773...@bugs.launchpad.net> a écrit : > The issue reported here is that /boot is not encrypted in the supported > configurations. Which is meh - we don't have much authenticated > encryption, so boot can still be manipulated. Sealed TPM measurements > address the problem of verifying the bootloader, kernel, initrd, and the > configuration better. It does not provide security by obfuscation as > encryption does, but that obfuscation can be circumvented - you can > modify an encrypted boot partition and still get a working system - and > authenticated encryption that would also authenticate the content is not > stable yet. > > I cannot say much on the other issue raised in recent comments on dual > boot setups not installing encrypted, but I fail to see how it's related > to this bug report > > I do want to point out that with devices now being sold with BitLocker > out of the box, that you do have to disable BitLocker first to even get > the ability to install another OS, so I fail to see how that improves > the situation for dual boot users who need encryption. > > But in any case adding comments to bugs that are unrelated to the bug is > not really helpful, you end up with nobody knowing what people are > talking about anymore. > > Hence my suggestion would be to open a new bug report against ubiquity > describing the dual boot setup issues so that that can be tracked on its > own and we don't have to discuss two bugs in one bug report. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1773457 > > Title: > Full-system encryption needs to be supported out-of-the-box including > /boot and should not delete other installed systems > > Status in grub2 package in Ubuntu: > Confirmed > Status in ubiquity package in Ubuntu: > Confirmed > > Bug description: > In today's world, especially with the likes of the EU's GDPR and the > many security fails, Ubuntu installer needs to support full-system > encryption out of the box. > > This means encrypting not only /home but also both root and /boot. The > only parts of the system that wouldn't be encrypted are the EFI > partition and the initial Grub bootloader, for obvious reasons. > > It should also not delete other installed systems unless explicitly > requested. > > On top of this, the previous method of encrypting data (ecryptfs) is > now considered buggy, and full-disk encryption is recommended as an > alternative. Unfortunately, the current implementation of full-disk > encryption wipes any existing OS such as Windows, making the > implementation unusable for most users. > > Now, using LUKS and LVM, it is already possible to have full-disk > encryption (strictly, full-partition encryption because it leaves any > existing OS alone), while encrypting /boot. Reference: > > https://help.ubuntu.com/community/ManualFullSystemEncryption > > ... but with one major limitation: Grub is incorrectly changed after > an update affecting the kernel or Grub, so that a manual Grub update > is required each time this happens (this is fully covered in the > linked instructions). > > If the incorrect Grub change is fixed, it should be (relatively) > simple to support full-system encryption in the installer. > > Further information (2018-08-17): > > The NCSC recommends, "Use LUKS/dm-crypt to provide full volume > encryption." > References: > • > https://blog.ubuntu.com/2018/07/30/national-cyber-security-centre-publish-ubuntu-18-04-lts-security-guide > • https://www.ncsc.gov.uk/guidance/eud-security-guidance-ubuntu-1804-lts > > **EDIT** > Refer to comment #47 for an alternative version. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1773457/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1773457 Title: Full-system encryption needs to be supported out-of-the-box including /boot and should not delete other installed systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1773457/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1799550] Re: No way to encrypt at partition level (dual boot)
Thank you so much for the feedback! Le mer. 23 déc. 2020 à 00:20, Julian Andres Klode < 1799...@bugs.launchpad.net> a écrit : > I think the answer there is fscrypt - native encryption at the > filesystem level supported by ext4 and some other day - but I'm not sure > what the plans are. Partitioning is hard and the requirement to setup a > separate /boot and crypt device are not always possible, though it is > less of an issue these days with GPT devices. > > As I pointed out on another bug report, the goal to dual boot with > encryption is not helped much by new devices being sold with BitLocker > enabled for the drive, forcing you to disable it in order to install > Ubuntu in the first place (one reason I imagine being that the > encryption key is sealed to the Windows boot process in the TPM, so > there's not a way to decrypt it from another OS, or even Windows booted > from a different disk). > > That the installer is unable to unlock luks partitions is a bit > unfortunate as it forces users to do more steps manually, and makes > reinstalling Ubuntu harder on systems where you want to keep /home but > replace /; or running multiple distributions in parallel - I've been hit > by that as well. > > In any case, I understand and share the concerns raised here and will > try to raise that internally, as this might also simply have went out of > our radar. > > ** Tags added: rls-hh-incoming > > ** Changed in: ubiquity (Ubuntu) >Status: Confirmed => Triaged > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1799550 > > Title: > No way to encrypt at partition level (dual boot) > > Status in ubiquity package in Ubuntu: > Triaged > > Bug description: > I'm using kubuntu alongside with windows in a dual boot, therefore I > cannot use the full disk partition option. There is no option in the > installer to get an encrypted kubuntu with windows (or any other OS) > already installed on the same disk. There used to be an option to encrypt > /home (up to 16.10 IIRC) but it does not exist anymore. > I had to follow and adapt this tutorial > http://blog.botux.fr/en/2015/09/ubuntu-installation-manual-full-disk-encryption-lvm-on-luks/ > to get my encrypted kubuntu. > Is it a bug in the installer or a missing (important, as security > related) feature? > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1799550/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1799550 Title: No way to encrypt at partition level (dual boot) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1799550/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1799550] [NEW] No way to encrypt at partition level (dual boot)
Public bug reported: I'm using kubuntu alongside with windows in a dual boot, therefore I cannot use the full disk partition option. There is no option in the installer to get an encrypted kubuntu with windows (or any other OS) already installed on the same disk. There used to be an option to encrypt /home (up to 16.10 IIRC) but it does not exist anymore. I had to follow and adapt this tutorial http://blog.botux.fr/en/2015/09/ubuntu-installation-manual-full-disk-encryption-lvm-on-luks/ to get my encrypted kubuntu. Is it a bug in the installer or a missing (important, as security related) feature? ** Affects: ubiquity (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/1799550 Title: No way to encrypt at partition level (dual boot) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1799550/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1799550] Re: No way to encrypt at partition level (dual boot)
Thanks for the answer but I'm not sure I fully understand. If I do the setup manually the partitioning and launch the installer once it is done, is there a way to perform the installation on this encrypted partition without having to chroot the environment and to create manually crypttab and cryptroot and to tune grub (as explained in http://blog.botux.fr/en/2015/09/ubuntu-installation-manual-full-disk- encryption-lvm-on-luks/ ) ? Xavier -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1799550 Title: No way to encrypt at partition level (dual boot) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1799550/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1799550] Re: No way to encrypt at partition level (dual boot)
Ok I missed that point. You can close it if you want,except if you intend to support resizing *and* disk encryption. Sorry for the noise. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1799550 Title: No way to encrypt at partition level (dual boot) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1799550/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1799550] Re: No way to encrypt at partition level (dual boot)
Well actually I don't see how to achieve that with the *k*unbuntu installer. I have created an encrypted partition blkid /dev/sda7 /dev/sda7: UUID="c9deed35-610e-4328-b8e7-079e95d43f76" TYPE="crypto_LUKS" PARTLABEL="Linux" PARTUUID="13aac430-9701-4323-810d-53231decca9c (on which I installed kubuntu as described in the blog link). I reboot on a kubuntu usb key. The installer offers the "full disk" encryption option, which is not what I want. Therefore I go for the "manual partitioning", but the installer sees the sda7 partition only as "unknown". If I format /dev/sda7 as ext4, I get an unencrypted ext4 partition and not a ext4 partition encrypted in an lvm. Maybe I should open the luks container before I launch the installer? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1799550 Title: No way to encrypt at partition level (dual boot) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1799550/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1774720] Re: Kubuntu installer crashes when toggling the checkbox to format an existing partition, in the manual partitioner
This is an old unresolved bug : https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1687637 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1774720 Title: Kubuntu installer crashes when toggling the checkbox to format an existing partition, in the manual partitioner To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1774720/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1804314] [NEW] Wrong WARNING Option 'hash' missing in crypttab
Public bug reported: I have installed kubuntu 18.10 on an encrypted partition. I have written a /etc/crypttab CryptDisk UUID=c9deed35-610e-4328-b8e7-079e95d43f76 none luks,hash=sha256,tries=3 At each boot, I get this warning "cryptsetup: WARNING: Option 'hash' missing in crypttab". I tried with and without the hash=sha256 but the warning does not change. ** Affects: cryptsetup (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/1804314 Title: Wrong WARNING Option 'hash' missing in crypttab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1804314/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1801404] [NEW] Macbook air, 18.10, fn keys to set keyboard backlight do not work
Public bug reported: The F5/F6 keys used to work to set the keyboard backillumination level with 18.04 but they do not work anymore with 18.10 4.18.0-10-generic The back illumination can be turned on with : echo 255 > /sys/class/leds/smc\:\:kbd_backlight/brightness but not anymore with the Fn keys. I'm not sure if it is a kernel issue or a keyboard mapping / X issue. Which test should I run to try to figure out where the problem is? ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: xavier 1452 F pulseaudio /dev/snd/controlC1: xavier 1452 F pulseaudio CurrentDesktop: KDE Date: Fri Nov 2 19:45:26 2018 InstallationDate: Installed on 2018-10-27 (6 days ago) InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: Apple Inc. MacBookAir7,2 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic root=/dev/mapper/lvm--vg-ubuntu--root ro cryptopts=target=CryptDisk,source=/dev/disk/by-uuid/0e4ab982-9511-479c-8a7a-4d933fcd3df1,lvm=lvm-vg quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/05/2018 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA71.88Z.0178.B00.1806051659 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-937CB26E2E02BB01 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir7,2 dmi.chassis.asset.tag: Chassis Board Asset Tag# dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-937CB26E2E02BB01 dmi.modalias: dmi:bvnAppleInc.:bvrMBA71.88Z.0178.B00.1806051659:bd06/05/2018:svnAppleInc.:pnMacBookAir7,2:pvr1.0:rvnAppleInc.:rnMac-937CB26E2E02BB01:rvrMacBookAir7,2:cvnAppleInc.:ct9:cvrMac-937CB26E2E02BB01: dmi.product.family: Mac dmi.product.name: MacBookAir7,2 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug cosmic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1801404 Title: Macbook air, 18.10, fn keys to set keyboard backlight do not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801404/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1773457] Re: Full-system encryption needs to be supported out-of-the-box including /boot and should not delete other installed systems
The issue remains the same with 19.10 (beta I tried yesterday). The 19.10 Kubuntu installer cannot install an encrypted kubuntu in dual boot with e.g. windows10. It is still possible to setup such an encrypted kubuntu but it requires to chroot after the installer has finished its job and to configure crypttab manually. It is far from being user friendly and it gives a bad first impression. ** Changed in: ubiquity (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1773457 Title: Full-system encryption needs to be supported out-of-the-box including /boot and should not delete other installed systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1773457/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1799550] Re: No way to encrypt at partition level (dual boot)
** Changed in: ubiquity (Ubuntu) Status: Triaged => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1799550 Title: No way to encrypt at partition level (dual boot) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1799550/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1773457] Re: Full-system encryption needs to be supported out-of-the-box including /boot and should not delete other installed systems
Any chance to see a fix in 20.04? We need to be able to encrypt (k)ubuntu data when ubuntu is installed alongside windows. /home encrytion was not perfect but it was better than nothing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1773457 Title: Full-system encryption needs to be supported out-of-the-box including /boot and should not delete other installed systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1773457/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869575] [NEW] Ubiquity kubuntu does not support / partition encryption (dual boot)
Public bug reported: This bug exists at leat with 19.04, 19.10 and 20.04 beta. With the ubuntu installer one can click on "do something else" and choose "physical volume for encryption" to create an encrypted partition. The installer nicely ask for the password and creates and then shows /dev/mapper/sdaX_crypt which can eventually be formated/mounted as /. Alongside with a non-encrypted /boot partition the installation works like a charm. With the kubuntu installer it does not work. If one selects "manual" and then "physical volume for encryption", the installer does not ask for a password and no /dev/mapper/sdaX_crypt is created. Therefore it is not possible to install kubuntu with an encrypted / out of the box. It is possible to install kubuntu on a fully encrypted drive but many users are in dual boot. Workaround : either create the encrypted partition with the command line before you run the kubuntu installer or install ubuntu and try to apt install kde afterwards. ** Affects: ubiquity (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/1869575 Title: Ubiquity kubuntu does not support / partition encryption (dual boot) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1869575/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869575] Re: Ubiquity kubuntu does not support / partition encryption (dual boot)
I would argue that it is a security issue as it will prevent new users (typical dual boot users) from encrypting the data. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869575 Title: Ubiquity kubuntu does not support / partition encryption (dual boot) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1869575/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1756840] Re: Buggy, under-maintained, not fit for main anymore; alternatives exist
Ok but what am I supposed to do on a dual boot machine?? I cannot use full disk encryption as I have other partitions for the other OS (or can I??) fscrypt ? where is it documented?? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1756840 Title: Buggy, under-maintained, not fit for main anymore; alternatives exist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/1756840/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1773457] Re: Full-system encryption needs to be supported out-of-the-box including /boot and should not delete other installed systems
Any change to be able to install an encrypted Ubuntu 19.10 alongside of a win10? I don't know if /boot should be encrypted but not being able to encrypt anything out of the box in 19.04 is a security regression. Crypaetup may not be perfect but it used to be good enough in many usecases. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1773457 Title: Full-system encryption needs to be supported out-of-the-box including /boot and should not delete other installed systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1773457/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1799550] Re: No way to encrypt at partition level (dual boot)
Ok it is a feature request but I see it more as a security regression. It used to be possible to encrypt /home in one click in the installer. This feature does not exist anymore and (I assume that) many users simply gave up and installed an unencrypted (k)Ubuntu. It is possible to install an encrypted "/" but the howto is not given in the installer. http://blog.botux.fr/en/2015/09/ubuntu-installation-manual-full-disk-encryption-lvm-on-luks/ is useful but needs to be adapted (no more swap) : it is far from obvious for a standard user. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1799550 Title: No way to encrypt at partition level (dual boot) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1799550/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1804314] Re: Wrong WARNING Option 'hash' missing in crypttab
It should be fairly simple to silence this warning. If cryptsetup is a script it should even be possible to find a simple workaround before an official fix is release. The question is : which options are correct and which one should trigger a warning?? In case of a lvm, are we supposed to provide the hash, the luks and who knows which option explicitly in /etc/crypttab?? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1804314 Title: Wrong WARNING Option 'hash' missing in crypttab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1804314/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1514120] Re: Ubiquity needs to not disable the LVM and encryption options for dual boot
"we are hoping the installer will support this out-of-the-box in the next release." That would be nice because it is a regression compared to 18.04 which was (IIRC) the last version offering a simple way to encrypt /home in the installer. As the swap should also be encrypted, the simplest way to go is to encrypt /. If we encrypt / I understand that we still need a /boot not encrypted...or do we have a way to encrypt the whole / including /boot? The user should not have to care about these "details". The need is to have a simple way to encrypt the user data. "Simple" means "in the installer". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1514120 Title: Ubiquity needs to not disable the LVM and encryption options for dual boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1514120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1804314] Re: Wrong WARNING Option 'hash' missing in crypttab
/etc/crypttab CryptDisk UUID=c9deed35-610e-4328-b8e7-079e95d43f76 none luks,retry=1,lvm=lvm-vg /etc/default/grub GRUB_CMDLINE_LINUX="cryptopts=target=CryptDisk,source=/dev/disk/by-uuid/c9deed35-610e-4328-b8e7-079e95d43f76,lvm=lvm-vg" /etc/initramfs-tools/conf.d/cryptroot CRYPTROOT=target=CryptDisk,source=/dev/disk/by-uuid/c9deed35-610e-4328-b8e7-079e95d43f76 and I get this warning : cryptsetup: WARNING: Option 'hash' missing in crypttab for plain dm-crypt mapping CryptDisk. Please read /usr/share/doc/cryptsetup/README.initramfs and add the correct 'hash' option to your crypttab(5) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1804314 Title: Wrong WARNING Option 'hash' missing in crypttab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1804314/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1804314] Re: Wrong WARNING Option 'hash' missing in crypttab
Because I followed an old and probably outdated documentation. Should I remove the lines in /etc/default/grub and in /etc/initramfs-tools/conf.d/cryptroot completely? My current /etc/crypttab read: CryptDisk UUID=c9deed35-610e-4328-b8e7-079e95d43f76 none luks,retry=1,lvm=lvm-vg Is it correct? It seems that retry=1 is also an outdated option... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1804314 Title: Wrong WARNING Option 'hash' missing in crypttab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1804314/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1804314] Re: Wrong WARNING Option 'hash' missing in crypttab
Thanks! https://blog.botux.fr/fr/2015/02/installation-ubuntu-utopic-14-10-encryption-manuelle-lvm-on-luks/ is wrong towards the end. Nothing special is needed in /etc/default/grub and /etc/initramfs- tools/conf.d/cryptroot shall not be created. Simply put CryptDisk UUID= none luks in your /etc/crypttab and the warning is gone. It would be cool if the installer setup all that automatically. It works in full disk but not in dual boot. You can close this bug. ** Changed in: cryptsetup (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1804314 Title: Wrong WARNING Option 'hash' missing in crypttab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1804314/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1799550] Re: No way to encrypt at partition level (dual boot)
The issue remains the unchanged with 19.10. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1799550 Title: No way to encrypt at partition level (dual boot) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1799550/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1773457] Re: Full-system encryption needs to be supported out-of-the-box including /boot and should not delete other installed systems
Agreed. "Full-system encryption needs to be supported out-of-the-box" full system shall mean 'the Linux partitions' an not 'the full disk'. In 19.04 it is not possible to install an encrypted kubuntu in dual boot with windows10 without playing with the command line. It means that no users new to Linux can encrypt the its Ubuntu. This is a severe security issue -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1773457 Title: Full-system encryption needs to be supported out-of-the-box including /boot and should not delete other installed systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1773457/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
