Thanks Kai-Heng.
I have updated this and will keep you posted:
$ sudo dmidecode -s bios-version
1.19.0
$ sudo dmidecode -s bios-release-date
03/22/2022
Devices that have been updated successfully:
• System Firmware (1.12.1 → 1.19.0)
--
You received this bug notification because you are a
Just by way of update, this does not happen very often. It happened to
me again today after I have changed around which ports I have things in,
perhaps for the first time since I reported this a month ago. The same
Thunderbolt ports are not working after suspend, but the USB-C only port
works.
--
Public bug reported:
Trying to launch OBS studio with the package installed from apt gives an
error on Wayland.
$ obs
Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use
QT_QPA_PLATFORM=wayland to run on Wayland anyway.
qt.qpa.plugin: Could not find the Qt platform plugin "wayland" in ""
obs-studio installed via snap install obs-studio launches as expected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1973340
Title:
22.04 obs-studio does not launch out of the box with Wayland
To
Public bug reported:
Hello,
Since upgrading (fresh reinstall) to 22.04, I have had issues with Totem
crashing.
I have not been able to pin down when it works and when it doesn't, as
playing the same videos seems to work sometimes and not work others.
After it crashes, trying to open it again
(And Firefox gave me a notification about hitting version 100, so it
presumably did update)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1972545
Title:
Ubuntu Dock does not show indicator for open
** Attachment added: "As expected, closing and reopening Firefox makes it work
as expected"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1972545/+attachment/5587903/+files/Screenshot%20from%202022-05-09%2013-44-45.png
--
You received this bug notification
** Attachment added: "Screenshot of the dock"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1972545/+attachment/5587901/+files/Screenshot%20from%202022-05-09%2013-32-20.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Public bug reported:
I am using the Firefox Snap on a fresh install of 22.04 (using defaults,
as far as I know).
Normally, Firefox shows an indicator in the Dock showing that it is
running (the orange dot) and gives the ability to choose between open
windows.
At the moment, I have Firefox
Yes, I think that is correct.
If you look at this diagram:
https://www.dell.com/support/manuals/en-uk/xps-13-9370-laptop/xps-13-9370-setupandspecs/left?guid=guid-a06ee5db-8981-4955-86ab-82b36e5aff57=en-us
I normally plug the monitor with keyboard into the port labelled 2 and the
network adapter
Public bug reported:
When I try to report a bug in Firefox on 22.04 with the Firefox Snap, it gives
an error:
"The problem cannot be reported:
firefox is provided by a snap published by mozilla. No contact address
has been provided; visit the forum at https://forum.snapcraft.io/ for
help."
I
Public bug reported:
I have a Dell XPS 13 9370 that came with Ubuntu preinstalled. I have
just completed a fresh install of 22.04 on it.
When I suspend the laptop, the USB devices that were plugged in when I
suspended do not work. Specifically, I had an Ethernet adapter and a
USB-C monitor with
** Attachment added: "Headset back on, output has gone back to the headset but
microphone has not"
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1970185/+attachment/5583423/+files/Screenshot%20from%202022-04-25%2009-43-46.png
--
You received this bug notification
** Attachment added: "Headset turned off, input and output revert to internal
ones"
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1970185/+attachment/5583422/+files/Screenshot%20from%202022-04-25%2009-43-27.png
--
You received this bug notification because you are a
Public bug reported:
In Gnome's sound settings, it takes a sensible approach for my Bluetooth
headset speaker:
1) I set it as my preferred audio Output Device
2) I turn the headset off and it disappears, reverting to the built in speakers
3) I turn the headset on again and it switches back to
I normally use Wayland. I just tested this using Xorg instead and it is
working fine. Back to Wayland and it crashes. Back to Xorg and it is
fine.
** Summary changed:
- Launching Pitivi repeatedly crashes user session and takes me back to login
screen
+ Launching Pitivi repeatedly crashes
It seems to also be doing something to my sound. I use a Plantronics
headset (bluetooth, but with a dongle so it looks on the system like an
analogue in and analogue out). When pitivi crashes and logs me out, my
headset no longer works once I log back in. Switching the sound settings
to use the
Public bug reported:
I was using Pitivi without any issues and created a video.
Now, opening Pitivi immediately crashes my user session and takes me
back to the login screen.
Ubuntu 20.04 with Pitivi from the archive -- hopefully all that is in
the attached logs, but let me know if anything
Ah interesting, thanks Daniel. I did not realise Raspberry Pis were
doing Wayland by default.
Yes, it works as expected in xorg, but not in Wayland.
It's a Raspberry Pi 4 Model B - 8GB, in case that was not clear from my
logs.
--
You received this bug notification because you are a member of
Public bug reported:
I am running Hirsuite on a Raspberry Pi 4. My main keyboard for this
(TV) machine is a wireless Logitech K400r combined keyboard/trackpad.
When I first installed, I do not think there were any issues with the
keyboard. When I did updates, my keyboard half-stopped working. It
sudo lspci -vt
** Attachment added: "sudo lspci -vt"
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1929032/+attachment/5499761/+files/20210524_lspci-vt.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "dmesg"
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1929032/+attachment/5499759/+files/20210524_dmesg_log.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
sudo lspci -vvv
** Attachment added: "sudo lspci -vvv"
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1929032/+attachment/5499760/+files/20210524_lspci-vvv.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
Hello,
I have a certified Dell XPS 13 9370 that had Ubuntu pre-installed,
though I have since installed normal 20.04 on it. I have my mouse,
keyboard and headset dongle plugged in via my USB-C monitor. This works
well.
- Every evening, I suspend to RAM
Public bug reported:
Hello,
I have a certified Dell XPS 13 9370 that had Ubuntu pre-installed,
though I have since installed normal 20.04 on it. I have my mouse,
keyboard and headset dongle plugged in via my USB-C monitor. This works
well.
Every evening, I suspend to RAM (note that I changed
** Attachment added: "Playback on 200% screen"
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1892379/+attachment/5403153/+files/Screenshot%20from%202020-08-20%2015-54-40.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "Display Settings screenshot 2"
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1892379/+attachment/5403155/+files/Screenshot%20from%202020-08-20%2015-56-01.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Attachment added: "Display Settings screenshot 1"
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1892379/+attachment/5403154/+files/Screenshot%20from%202020-08-20%2015-55-54.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
I am using Ubuntu Focal Fossa with Wayland and two screens.
Display 1 is a 3840 x 2160 screen at 200% scaling
Display 2 is a 1920x1200 at 100% scaling
Fractional Scaling is on. Display 2 is my Primary Display.
When I play a video on Display 2, everything works as expected.
Hello all,
Apologies, I missed these recent messages.
For background, the error UnicodeDecodeError just means that a non-ASCII
character is hitting a piece of code that was not designed to handle it.
That is not surprising -- prior to the 0.8 series, very little of the
code was designed for
Public bug reported:
When using Google Meet in Firefox (Ubuntu 20.04, 76.0.1 (64-bit)), for
the first 5-10 seconds of the meeting, nobody can hear anything that I
am saying. After that, I have no issues. I also have no issues joining
with Chromium.
The sound indicator on my end (the little green
Is this related to: https://bugzilla.mozilla.org/show_bug.cgi?id=1530370
? If so, in the duplicate bug
(https://bugzilla.mozilla.org/show_bug.cgi?id=1619850 ) somebody said
"This is a 2020 goal."
** Package changed: evolution (Ubuntu) => firefox (Ubuntu)
** Bug watch added: Mozilla Bugzilla
All,
This should be fixed in 0.8.00, which has now been released. This is the
first 0.8-series release, so expect issues and test it out on data you
can afford to lose (if it comes to that).
I have now packaged up this version as a snap. You can install it by typing:
snap install duplicity
All, to clarify the current position, this is fixed in the 0.8 series,
but I set out the steps to test the fix in comment #15 and was waiting
on testing feedback before merging the patch back into the 0.7 series.
Nobody gave me any testing feedback. It is therefore not yet fixed in
the 0.7 series.
@Sebastian, Kenneth is planning to release a 0.8 version very soon.
Note that I have wound the Python 3 blueprint completion back a step, as
I have realised that there are some backend dependencies (e.g. pyrax)
that do not work on Python 3. I believe deja dup only uses a subset of
the backends
** Attachment added: "Screenshot with external monitor connected. Only whole
number scaling available."
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1826550/+attachment/5259303/+files/Screenshot%20from%202019-04-26%2014-32-06.png
--
You received this bug notification
Public bug reported:
Using 19.04 disco with Wayland.
I have a HiDPI laptop screen (XPS13) and a normal DPI external monitor.
I have enabled the experimental fractional scaling support.
When no external monitor is connected, the fractional scaling options
are displayed as expected. When the
Public bug reported:
Using 19.04 disco with Wayland.
I have a HiDPI laptop screen (XPS13) and a normal DPI external monitor.
I have the laptop screen set to 200% and the external screen set to
100%.
If I set the primary display to the built-in display but have the
display settings window open
Public bug reported:
Running 19.04 Disco with Wayland
Version 64ubuntu7
I have a HiDPI laptop screen (XPS13) and a normal DPI external monitor.
I have the laptop screen set to 200% and the external screen set to
100%.
When running the display solely on my built-in monitor, the dock is
correctly
The 0.8-series was affected by this (as I mentioned above, fixing the
underlying problem avoids this error and a number of these have been
fixed, so it is harder to trigger).
I have just proposed a fix for it be merged into the 0.8-series:
https://code.launchpad.net/~aaron-whitehouse/duplicity/08
Marking this as Fix Committed, as we have Python 3 compatible code in
0.8-series with all tests also being run against this environment. We
have not yet put out a 0.8 release, though.
See https://blueprints.launchpad.net/duplicity/+spec/python3
** Changed in: duplicity
Importance: Undecided
for proposing a
patch for this, which I had overlooked.
I have applied this in the branch here: lp:~aaron-
whitehouse/duplicity/07-uexc-fix
It would be helpful if you can please test to see if this fixes your problem as
follows:
1. Create a new destination directory to test with.
2. Test that duplicity fails
** Summary changed:
- backup fails with UnicodeDecodeError
+ backup fails with UnicodeDecodeError in uexc function
** Summary changed:
- backup fails with UnicodeDecodeError in uexc function
+ Duplicity fails with UnicodeDecodeError in uexc function
--
You received this bug notification
Using the firmware from Comment #5 above stopped the wireless and my my
Bluetooth mouse from working, so I have reverted it to the standard
Ubuntu version.
sudo lspci -vvv -s 02:00.0 gives:
02:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network
Adapter (rev 32)
Correct. Since I have been using Deep instead of S2Idle I have seen the
issue less -- though it has only been a couple of days as I was not
using this machine over the holidays. Even when it does break, Deep
suspending and resuming the machine brings the wireless back up and
working.
--
You
Done, thanks Kai-Heng. How can I check I'm using the new versions?
$ dmesg | grep ath10k
[ 15.152725] ath10k_pci :02:00.0: enabling device ( -> 0002)
[ 15.154816] ath10k_pci :02:00.0: pci irq msi oper_irq_mode 2 irq_mode 0
reset_mode 0
[ 15.436782] ath10k_pci :02:00.0:
I'm marking this as incomplete for now until I can provide more
information on relative power usage, things broken in modern
standby/s2idle etc.
If we can get the power usage materially similar to deep sleep but with
an instant-on experience etc (and everything else works as expected)
then that
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1808957
Title:
Dell XPS 13 (9370) defaults to s2idle sleep/suspend instead of deep
More background information on 'Modern Standby' on Linux here:
https://lwn.net/Articles/580451/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1808957
Title:
Dell XPS 13 (9370) defaults to s2idle
Having looked into this in more detail, it sounds as though this is the
intended behaviour for new laptops that declare ACPI_FADT_LOW_POWER_S0:
https://patchwork.kernel.org/patch/9433419/
This appears related to:
Normally (maybe always?) it is when the network is idle. Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1807974
Title:
Wireless regularly breaking (ath10k firmware crashed!) after upgrade
Public bug reported:
It seems that the Dell 9370 is set to go into s2idle mode rather than
deep sleep, forgoing significant power savings.
I have confirmed this by suspending and then checking:
sudo journalctl | grep "PM: suspend" | tail -2. If the output is
PM: suspend entry (s2idle)
PM:
Public bug reported:
I have a Dell XPS 13 9370 developer edition (Ubuntu version) running
Cosmic. A handful of times per day, my wireless stops working ("?"
appears in the icon in Network Manager). Turning wireless off and then
on again, or suspending and waking the machine up, makes the wireless
See also Bug #1627474
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1730331
Title:
ath10k_pci: firmware crashed!
To manage notifications about this bug go to:
See also Bug #1730331
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1627474
Title:
ath10k_pci :03:00.0: firmware crashed! (uuid n/a)
To manage notifications about this bug go to:
Anything that I can do to help get this fix into the Ubuntu package? I
cannot import photos, which is enough of a problem that I'm considering
downgrading to the earlier release -- but happy to help try to fix it
properly.
--
You received this bug notification because you are a member of Ubuntu
Marcus has said in the upstream bug:
"I released 2.5.16 some weeks ago.
the commit fixing this issue for backporting is
472a9461b457b4d08ecf10a93bb7f1efdc2124c0 "
It would be excellent if this could please make its way into Ubuntu.
--
You received this bug notification because you are a member
** Also affects: gphoto2 (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/1731341
Title:
Fujifilm X-T10 regression on 17.10: "Unable to fetch
I would say this is a duplicate of Bug #910964, except that bug hasn't
had any action since 2013 and this only just stopped working.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1731341
Title:
Looks like it is this:
https://sourceforge.net/p/gphoto/bugs/1032/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1731341
Title:
Fujifilm X-T10 regression on 17.10: "Unable to fetch previews from
$ gphoto2 -T
*** Error ***
An error occurred in the io-library ('Unspecified error'): No error description
available
*** Error (-1: 'Unspecified error') ***
For debugging messages, please use the
Public bug reported:
I have a Fujifilm X-T10. This worked perfectly in Shotwell in 17.04. Since
upgrading to 17.10, I receive an error whenever I try to import photos:
Unable to fetch previews from the camera: Unspecified error (-1)
lsusb gives:
Bus 001 Device 010: ID 04cb:02c8 Fuji Photo
Have you tried to verify your backup or do a new full backup?
> Can someone recommend a better backup software for personal use?
http://lmgtfy.com/?q=personal+backup+software+linux
There is a reason, though, that Deja Dup (which you are already using)
is the default in Ubuntu -- it is a pretty
Jonathan,
Given the latest version of xfce-settings (4.12.1) was easy to install
and fixed all of my issues (see comment #130 above), it would be
interesting to know whether this also fixed your problem.
Kind regards,
Aaron
--
You received this bug notification because you are a member of
I have an ASUS Z170M-Plus Mobo with an Intel Core i3-6100T, Intel HD 530
graphics and a Samsung TV connected through HDMI, running Mythbuntu
16.04.
I had the issue that when I turned the TV off and then back on again, the TV
would say "No Signal" and I would have to run
$ sudo service lightdm
Yes, not fixed for me either.
* Ubuntu 16.04 x64
* Firefox 47.0
* Keefox 1.6.0
Trying to log into help.ubuntu.com, I get the
"
Bad Request
Bad bot, go away! Request aborted.
"
message.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Duplicate of Bug #1388648?
(This one is actually older, but that one is higher priority and has
slightly more information.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1266003
Title:
unity
Also (unsurprisingly) an issue in Crossover (15.2 on Ubuntu 16.04), for
example using the default crosstie for Age of Empires 2.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1388648
Title:
Wine
*** This bug is a duplicate of bug 1313034 ***
https://bugs.launchpad.net/bugs/1313034
** This bug has been marked a duplicate of bug 1313034
Deja-dup reports it couldn't backup ~/.cache/dconf and ~/.gvfs even though
it's not supposed to try to (also, ~/.dbus)
--
You received this bug
Thanks Christopher,
Do you want me to do this with the latest mainline kernel, rather than
the Ubuntu 15.10 one?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1450755
Title:
Intel Wireless-N 2230
For comparison, on Windows 7 (machine in same spot)
Up to 54Mbps
>iperf -c 192.168.0.102
Client connecting to 192.168.0.102, TCP port 5001
TCP window size: 63.0 KByte (default)
Ah right, thanks Christopher. Sorry, I thought you were meaning on the
Ubuntu side. I've now done that (on the latest mainline) and there
doesn't seem to be a significant variation.
$ uname -r
4.5.0-040500rc5-generic
Wireless mode was 'Up to 144Mbps (best for wireless range)'
$ iperf -c
This issue still persists in 15.10.
$ iperf -s
Server listening on TCP port 5001
TCP window size: 85.3 KByte (default)
[ 4] local 192.168.0.102 port 5001 connected with
Public bug reported:
I really like using Bazaar Explorer, but I have issues every time that I
try to use the merge functionality. The text that comes up if there is a
conflict is white text on a yellow background and I can never see what
it is asking me. I've attached an example screenshot.
Updated to latest upstream again.
$ uname -r
4.1.0-040100rc6-generic
$ iwconfig
virbr0-nic no wireless extensions.
eth0 no wireless extensions.
wlan0 IEEE 802.11bgn ESSID:VM851079-2G
Mode:Managed Frequency:2.462 GHz Access
No, it doesn't seem to.
=
$ iwconfig
virbr0-nic no wireless extensions.
eth0 no wireless extensions.
wlan0 IEEE 802.11bgn ESSID:VM851079-2G
Mode:Managed Frequency:2.462 GHz Access Point: 10:0D:7F:18:C4:80
I don't think so, no.
It's this:
http://electronics360.globalspec.com/article/3410/netgear-super-hub-2-vmdg485-wireless-router-teardown
which looks quite different to the pictures on the page that you linked to.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
It's a Virgin Media Superhub 2, which is a Netgear VMDG485:
Information Cable Modem EuroDOCSIS 3.0 Compliant
Serial Number 3BW132UG04977
Boot Code Version PSPU-Boot 1.0.20.1356
Software VersionV1.01.29
Hardware Version3.11
Please let me know if you need anything
I have just tested this with the latest upstream kernel:
$ iperf -c 192.168.0.102
Client connecting to 192.168.0.102, TCP port 5001
TCP window size: 85.0 KByte (default)
[ 3]
Updating the BIOS does not solve the issue (the speed actually reduced
slightly).
After updating the BIOS, this is the output:
[ 3] local 192.168.0.3 port 49429 connected with 192.168.0.102 port 5001
[ ID] Interval Transfer Bandwidth
[ 3] 0.0-10.1 sec 21.6 MBytes 18.0 Mbits/sec
$
Public bug reported:
My Intel wireless card is significantly slower in Ubuntu than it is in
Windows 7.
According to iperf (with the laptop a couple of feet from the router and the
server plugged into it):
== Ubuntu 15.04 ==
[ 4] local 192.168.0.102 port 5001 connected with 192.168.0.3 port
Hello William,
This is more a request for advice at this stage, so I have converted
your bug to a question. If there are any bugs or feature requests that
become clear when people are answering your question, you could open a
new bug for these at that stage.
** Changed in: mythtv (Ubuntu)
Apologies all to waste your time. It turns out that, in moving my
computer slightly to upgrade the OS, the inside of my aerial cable broke
and this was a hardware issue.
I realised when I rolled it back and the issue persisted. I have
replaced the cable and all works fine now, thanks.
** Changed
Public bug reported:
I was using the TeVii DVB-S2 S480 (which is a dual tuner equivalent to two
DVB-S2 660 cards):
http://www.linuxtv.org/wiki/index.php/TeVii_S480
in Mythbuntu 12.04 for a long time without issue.
I have recently updated to 14.04 and it will no longer lock on channels, giving
Running
scan -x0 /usr/share/dvb/dvb-s/Astra-28.2E | tee channels.conf
gives tuning failed errors for each channel, eg:
DVB-S IF freq is 1782000
WARNING: tuning failed!!!
tune to: 12402:v:0:27500
DVB-S IF freq is 1802000
WARNING: tuning failed!!!
tune to: 12402:v:0:27500 (tuning failed)
Public bug reported:
Lightweight IDE for Python
Free, open-source, Apache 2 license
Intelligent Editor, Debugger, Refactorings, Inspections, VCS integration
Project Navigation, Testing support, Customizable UI, Vim key bindings
URL: http://www.jetbrains.com/pycharm/
License: Apache 2 license
Public bug reported:
In the 13.10 release, most of the time I do not seem to be able to click
the title bars (File, Edit etc). Very occasionally, it works. I can't
figure out what is making the difference.
ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: gnucash 1:2.4.13-1ubuntu1
Public bug reported:
I use a Dell Inspiron 14z with 13.10. I'm pretty sure that at least
vertical scrolling (by moving my finger along the right edge of the
touchpad) used to work, but neither work for me now in 13.10.
My hardware details should be attached.
ProblemType: Bug
DistroRelease:
It sounds like this also stops BindFS from working to share a local directory
on boot:
https://help.ubuntu.com/community/Bindfs-SharedDirectoryLocalUsers
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
- Ubiquity installer in 12.10 offers the ability to install Ubuntu in an
encrypted LVM. However, the options are only available when replacing an
existing operating system.
- If I wish to install Ubuntu alongside another OS, the options become grayed
out (see
Public bug reported:
I use Full-Disk Encryption. It does not seem possible to set up multiple
partitions within the encrypted area through the Something else manual
partitioner.
It is possible to create a Physical area for encrypted partitions (I'm
not 100% on the wording), but as far as I can
** Description changed:
I use Full-Disk Encryption. It does not seem possible to set up multiple
partitions within the encrypted area through the Something else manual
- partitioner.
+ partitioner on either 12.10 or 13.04 (or any of the earlier releases).
It is possible to create a
We have recently updated (new clean install) to 13.04 Raring Ringtail
and this appears to have been fixed. I now have a preview when scanning
and have no problems saving PDFs. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Sorry, I meant to say, it would be interesting to know if updating also
solves your problem, Pierre - you may be able to try from a live DVD of
13.04?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I have set out how I made this work (not well) in Answer# 216356
There is no way to divide up partitions within an encrypted partition,
as far as I have established. Confirmed today in 13.04. It would be good
to fix this, because at the moment the manual partitioner has a whole
lot of ways that
https://answers.launchpad.net/ubuntu/+source/ubiquity/+question/216356
** Tags added: 13.04
--
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
I just did a clean install of 13.04 Raring Ringtail and this still
occurs (on my first boot, unfortunately!)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1088244
Title:
No Full-Disk Encryption
Public bug reported:
I have a Dell Insprion 14z (Inspiron 5423) and I'm running 13.04. The
machine has an Intel 4000 HD and Radeon 7550M/7570M/7650M
By default, both graphics cards are powered up, even though only the integrated
Intel is used:
$ sudo cat /sys/kernel/debug/vgaswitcheroo/switch
Public bug reported:
The Alpha release of KeePassX 2.0 is available. With the poor ratings of
KeePass2 on Ubuntu and KeePassX providing support for .kdbx files, it
would be great to have this in Raring.
I for one really would like .kdbx support, particularly now that this
has been added to
Card with 282 photos, 7 videos.
1) Plug in camera, open Shotwell.
2) Error that camera in use by another application (pretty sure that didn't
used to happen in previous versions), unmount the camera.
3) Click on the camera, all thumbnails are shown.
4) Click Import All, hangs for a while, get
1 - 100 of 843 matches
Mail list logo
