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: /us
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/
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 PROTECTE
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 be
> 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 o
** 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 mail
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+ SpecCycl
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 beca
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
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
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
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
ins
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 bu
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
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
> """
>
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='__ma
*** 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
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 notificati
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.
:(
"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.lo
"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/va
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 (
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
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
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-
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
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 scr
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 kn
** 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 mailin
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 U
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 wi
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()
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/actu
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.
--
k
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.launc
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
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)
Import
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 i
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@li
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.
--
u
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/
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
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 su
> 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
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 de
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)
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
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-
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.000
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
** 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.
--
ubu
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 sym
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_
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
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 t
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
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:
>
> -
> 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 en
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
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 ma
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 go
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://l
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 membe
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-bu
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)...
> 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
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/mapp
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 becaus
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
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
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 thi
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
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 bec
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
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 f
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
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
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. Partition
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 e
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 crypt
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:
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 kubun
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 t
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 wit
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 key
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 confi
** 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 notifica
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.
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/map
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 kubun
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.
ht
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
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 encr
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 provid
"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
/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=CryptDis
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
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 you
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 t
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 t
1 - 100 of 208 matches
Mail list logo
