Sorry Paride
$ aptitude install samba=2:4.13.5+dfsg-2ubuntu2
didn't work due to unmet dependencies for other samba components.
However I notice that an update to Samba today has solved the problem
and I can access Windows Shares and my backups work OK.
--
You received this bug notification b
Sorry Paride
$ aptitude install samba=2:4.13.5+dfsg-2ubuntu2
didn't work due to unmet dependencies for other samba components.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1953687
Title:
Samba
I can get to the NAS using its IP address so Déjà Dup must be using the
Widows shares.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1953687
Title:
Samba connected network devices no longer appear i
I seem to have the same problem as you have. I marked mine as a
duplicate of yours as Paride is woking on yours. I have found that it
affects my backups as they get saved on my NAS.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
*** This bug is a duplicate of bug 1953687 ***
https://bugs.launchpad.net/bugs/1953687
** This bug has been marked a duplicate of bug 1953687
Samba connected network devices no longer appear in "Windows Network" folder
of Nautilus.
--
You received this bug notification because you are a
** Description changed:
When trying to access my NAS using Files or to do a backup which saves
on my NAS I get this error message.
- Failied to mount Windows share: Invalid argument
+ Failed to mount Windows share: Invalid argument
- I would expect access my NAS.
+ I would expect access
Public bug reported:
When trying to access my NAS using Files or to do a backup which saves
on my NAS I get this error message.
Failied to mount Windows share: Invalid argument
I would expect access my NAS.
I am using Ubuntu version 21.10
Note that /etc/samba/smb.conf was updated yesterday.
s
I have now upgraded to 21.04, and all seems OK.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1936669
Title:
Software Update won't install version 21.04
To manage notifications about this bug go to
I ran
apt-get install dh-python
this removed
python-is-python2
and upgraded
dh-python
apt-cache policy dh-python now shows
dh-python:
Installed: 4.20200925
Candidate: 4.20200925
Version table:
*** 4.20200925 500
500 http://gb.archive.ubuntu.com/ubuntu groovy/universe amd64 Pac
I ran
apt-get install dh-python
this removed
python-is-python2
and upgraded
dh-python
apt-cache policy dh-python now shows
dh-python:
Installed: 4.20200925
Candidate: 4.20200925
Version table:
*** 4.20200925 500
500 http://gb.archive.ubuntu.com/ubuntu groovy/universe amd64 Pac
It shows:
dh-python:
Installed: 4.20191017ubuntu7
Candidate: 4.20200925
Version table:
4.20200925 500
500 http://gb.archive.ubuntu.com/ubuntu groovy/universe amd64 Packages
500 http://gb.archive.ubuntu.com/ubuntu groovy/universe i386 Packages
*** 4.20191017ubuntu7 100
Thanks for your message Brian.
do-release-upgrade reports:
Checking for a new Ubuntu release
Please install all available updates for your release before upgrading.
Then returns to the prompt.
If I then run
apt-get update
apt-get upgrade
apt-get dist-upgrade
I get nothing except the message t
Thanks for your message Brian.
do-release-upgrade reports:
Checking for a new Ubuntu release
Please install all available updates for your release before upgrading.
Then returns to the prompt.
If I then run
apt-get update
apt-get upgrade
apt-get dist-upgrade
I get nothing except the message t
running the commands:
apt-get update
apt-get upgrade
apt-get dist-upgrade
also do not upgrade to 21.04.
The last two commands report that dh-python has been kept back.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
Public bug reported:
Every time my system installs new software it tells me that a new
version (21.04) of Ubuntu is available to update from my current version
20.10.
There is a Upgrade button for me to press. I expect it to call the
Upgrade routine to install version 21.04.
Instead, nothing ha
I have used the fix in https://askubuntu.com/questions/838491/dpkg-
divert-error-rename-involves-overwriting-error-after-upgrading-
from-16-04/838673#838673. I hope it cures the problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I have re-run the command on the correct computer, which is an ASUS
32-bit 1015PEM eeepc. I hope you can sort out the reports.
(The wrong computer was the LENOVO E50-00)
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a
My apologies, I ran the apport-collect command on the wrong computer.
I added this bug because the distribution update program told me to file
a bug report
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1924802/+attachment/5489079/+files/RfKill.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1924802
Title:
sy
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1924802/+attachment/5489077/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1924802
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1924802/+attachment/5489071/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1924802
Title:
sysd
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1924802/+attachment/5489076/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/192
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1924802/+attachment/5489081/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1924802
Ti
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1924802/+attachment/5489068/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1924802
Title:
sysdem
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1924802/+attachment/5489075/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1924802
apport information
** Tags added: bionic
** Description changed:
Having updated from 16.04 to 18.04 sysdemd-shim is not working
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu50.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: to
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1924802/+attachment/5489080/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1924802
Title:
sy
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1924802/+attachment/5489078/+files/PulseList.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1924802
Titl
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1924802/+attachment/5489074/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1924802/+attachment/5489073/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1924802
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1924802/+attachment/5489072/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1924802
Title:
sysd
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1924802/+attachment/5489070/+files/IwConfig.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1924802
Title:
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1924802/+attachment/5489069/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1924802
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1924802/+attachment/5489046/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1924802
Title:
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1924802/+attachment/5489045/+files/Lsusb-t.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1924802
Title:
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1924802/+attachment/5489041/+files/IwConfig.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1924802
Title:
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1924802/+attachment/5489043/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1924802
Title:
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1924802/+attachment/5489040/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1924802
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1924802/+attachment/5489044/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1924802
Title:
sysd
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1924802/+attachment/5489042/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1924802
Title:
sysd
apport information
** Tags added: apport-collected groovy
** Description changed:
Having updated from 16.04 to 18.04 sysdemd-shim is not working
+ ---
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu50.5
+ Architecture: amd64
+ AudioDevicesInUse:
+ USERPID ACCESS COMMAND
+ /dev/s
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1924802/+attachment/5489039/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1924802
Title:
sysdem
Public bug reported:
Having updated from 16.04 to 18.04 sysdemd-shim is not working
** Affects: linux (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
Here is the make log
** Attachment added: "Make log"
https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1901880/+attachment/5428455/+files/make.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
Public bug reported:
I have a USB wifi adapter, I installed rtl88x2BU and for every kernel
update in 20.04 dkms built it automatically without any problems.
Now I have updated to 20.10 I would expect this to happen but the build
fails:
Building module:
cleaning build area...
make -j4 KERNELRELE
I have done that but I shouldn't have had to. There must have been some
change to Samba on the upgrade to 20.04 that caused it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880305
Title:
Failed t
I have done that but I shouldn't have had to. There must have been some
change to Samba on the upgrade to 20.04 that caused it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880305
Title:
Failed t
Thanks for your comment Jim. My NAS is a ZyXEL NSA325 v2 and doesn't
have any access to SMB settings.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880305
Title:
Failed to mount Windows share: Sof
Hi Robie
I think you've missed the point. There is a bug that was introduced by
the upgrade from 19.10 to 20.04. I assume it is somewhere in Samba.
My use of NT1 is not meant to be a fix for the reason you have given.
It is just a workaround.
Please change it back from Won't Fix to something s
** No longer affects: nautilus (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880305
Title:
Failed to mount Windows share: Software caused connection abort
To manage notifications about th
Have created a workaround which works:
1. created directory ~/.smb
2. copied /etc/samba/smb.conf to it
3. added 'client min protocol = NT1' to [global] section.
as suggested in bug #1879776
** Also affects: samba (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug not
Public bug reported:
Since upgrading from 19.10 to 20.04 I cannot access folders on my NAS.
What happens:
In Nautilus (1:3.36.2-0ubuntu1) I do the following
1. Go to Other Locations
2. Click on Windows Network
3. Double Click on WORKGROUP
4. Double Click on DYLAN (the NAS at 192.168.1.5)
5. Dou
Update to 4.4.0-164 has cured this bug. I can now boot with this kernel
and log in OK.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824641
Title:
[regression] Atom N550: Blank screen after booting
Another update to 4.4.0-154, still the same, screen still blank after
booting, 143 still works.
** Summary changed:
- [regression] Atom N550: Blank screen after booting kernel 4.4.0-145 or 146 or
148 or 150 or 151 (but 4.4.0-143 works)
+ [regression] Atom N550: Blank screen after booting kernel
Another update to 4.4.0-151, still the same, screen still blank after
booting, 143 still works.
** Summary changed:
- [regression] Atom N550: Blank screen after booting kernel 4.4.0-145 or 146 or
148 or 150 (but 4.4.0-143 works)
+ [regression] Atom N550: Blank screen after booting kernel 4.4.0-1
Another update to 4.4.0-150, still the same, screen still blank after
booting,
** Summary changed:
- [regression] Atom N550: Blank screen after booting kernel 4.4.0-145 or 146 or
148 (but 4.4.0-143 works)
+ [regression] Atom N550: Blank screen after booting kernel 4.4.0-145 or 146 or
148 or 150
Another update to 4.4.0-148, still the same, screen still blank after
booting,
** Summary changed:
- [regression] Atom N550: Blank screen after booting kernel 4.4.0-145 or 146
(but 4.4.0-143 works)
+ [regression] Atom N550: Blank screen after booting kernel 4.4.0-145 or 146 or
148 (but 4.4.0-14
** Summary changed:
- [regression] Atom N550: Blank screen after booting kernel 4.4.0-145 (but
4.4.0-143 works)
+ [regression] Atom N550: Blank screen after booting kernel 4.4.0-145 or 146
(but 4.4.0-143 works)
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
An update with 4.4.0-146 has been installed and there is no fix in it.
The screen is still blank.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824641
Title:
[regression] Atom N550: Blank screen af
Attached is Xorg log for the boot of 4.4.0-145
** Attachment added: "Xorg log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824641/+attachment/5255955/+files/Xorg.0.log.old
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Attached is a syslog for the boot of 4.4.0-145 from start up to shut
down in the way described above.
** Attachment added: "Syslog from boot of 4.4.0-145"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824641/+attachment/5255939/+files/syslog4.4.0-145
--
You received this bug notifica
Sorry I cannot collect log files for the kernel giving the bug. If I
can collect any useful information using the kernel that does work,
please let me know
** Changed in: mutter (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubunt
Sorry I cannot collect log files for the kernel giving the bug. If I
can collect any useful information using the kernel that does work,
please let me know
** Changed in: mutter (Ubuntu)
Status: New => Incomplete
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
Yo
Please not that Launchpad has automatically assigned this bug to mutter,
but mutter is not installed on the notebook in question, so I have added
linux
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ub
Public bug reported:
Having run update on my i386 Asus Eee PC with Intel Atom N550 Dual core
CPU running 16.04.06 LTS, it installed linux 4.4.0-145. If I boot this
kernel everything is blank. Just a black screen. If I change to a
terminal using Ctrl Alt F4 it is still a black screen but I can
ca
Here's an update on this...
If, when in GRUB, I select the Advanced option and then choose the
(upstart) option, it works OK.
If I do the default boot, it nearly always results in the error message
and no wifi.
I hope this will give you some idea of what is going wrong.
--
You received this bu
Hi Daniel
I'm grateful that you mentioned bug 1727356. I would have taken the
opportunity to upgrade to 18.04 but I see that I will have to wait until
it is fixed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
It seems I spoke too soon.
When I started the machine back up again today using 4.4.0-130, the bug
was back again.
It seems that when I restart, sometimes it will start without the error
message, then it will be back again if I restart again. Its quite
random.
Another thing I have noticed is th
Bug has been fixed in upgrade just released including kernel 4.4.0-131.
Even though the bug was reported against 4.4.0-124, it was also present
in releases between that and 4.4.0-130
** Changed in: xorg (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because yo
Public bug reported:
When booting an error window is displayed. The only option that works
is to use the default configuration.
This problem has been introduced by an upgrade in recent months, i.e.
since April 2018
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcV
See errors in the xorg log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1783850
Title:
Cannot find display configuration
To manage notifications about this bug go to:
https://bugs.launchpad.net/ub
After upgrade to 16.10, this problem is back but the freezes do not
occur as frequently as they did in 16.04 before my 'fix'
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1536721
Title:
System freez
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: compiz (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1536721
Title:
System freezes
To man
I have found a cure for this. I went into Setup and then into Advanced
and Disabled 'Turbo Mode' which is described as follows:
Enabled/Disabled Turbo Mode to allow processor to assess its own
thermals, current & power to come up with a dynamic upper limit on its
frequency benefit
--
You receiv
I think you may be right, Henry. I went out on a walk along a country
lane this afternoon and decided to try out uNav. I don't think that app
expects the device to have a location to hand to it when it starts. Your
press an icon in the header to determine you current location, and it
worked. As I
Updated to OTA 12. Location icon now shows, but location still doesn't
not work for things like Google Maps, Here maps and Nearby scope.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1588994
Title:
Public bug reported:
Since installing OTA-11 Google maps reports 'Google maps could not
determine your precise location' and Here maps says 'Can't find your
location'.
Location detection is ON.
'Using GPS, anonymised Wi-Fi and mobile network info' is selected in
Location settings.
** Affects: l
This may be the same as bug 1588459
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1588994
Title:
Location not working since OTA-11 on BQ 4.5
To manage notifications about this bug go to:
https://bu
Have tried SSH to the frozen computer and it does not work. Does this
indicate something more fundamental than a problem in compiz or xorg?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1536721
Title
... and also freezes when screen is locked.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1536721
Title:
System freezes
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubun
... and also freezes when screen is locked.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1536721
Title:
System freezes
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubun
I have reported this under compiz as the freeze most often occurs when
scrolling up and down or moving about in web pages. It has, however,
also occurred when in other programs, such as playing a game of
Solitaire.
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
Public bug reported:
My system frequently freezes. The screen is still displayed but no
input is accepted from mouse or keyboard. The only action available is
to switch off and re-start.
ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1
ProcVersionS
Thank you for the help, Phillip. I suspect this has something to do
with this
http://support.lenovo.com/sg/en/product_security/modify_uefi_variable
and a heavy handed 'fix' for it. It seems I shall just have to get used
to pressing F12 on boot.
--
You received this bug notification because yo
sda2 is mounted on /boot/efi. sda3 is mounted on /media/tony.
It's not quite true that it is refusing to let me boot anything but
windows. It's just making it a little bit more difficult by making me
boot Ubuntu from the F12 boot menu. I just have to remember to hold
down F12 when I start up.
Here is the output of sudo parted -l
Model: ATA WDC WD5000AAKX-0 (scsi)
Disk /dev/sda: 500GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:
Number Start End SizeFile system Name
Flags
1 1049kB 1050MB 1049MB ntfs
Hi Salil
This looks like the same as I have reported (see
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1469245)
In the bios boot menu, do you have an 'ubuntu' option which then boots
to a GRUB menu like mine?
You may be able to try some of the things suggested to me. They may
work fo
Photo of F12 boot menu (taken on Ubuntu phone!)
** Attachment added: "image20150628_141110689.jpg"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1469245/+attachment/4421519/+files/image20150628_141110689.jpg
--
You received this bug notification because you are a member of Ubuntu
B
Hi Phillip
Thanks for all your help. Unfortunately, what you suggested did not
change anything. It is still booting straight into Windows unless I go
via the F12 boot menu. So I have done some tests.
Here is the output of efibootmgr -v after running sudo efibootmgr -o
4,8,0
BootCurrent: 0004
** Changed in: ubiquity (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1469245
Title:
Following install GRUB menu does not appear on startup
To manage notif
efibootmgr -v
BootCurrent: 0004
Timeout: 6 seconds
BootOrder: ,0004,0008,0003,0002,0001
Boot* Windows Boot Manager
HD(2,1f4800,82000,c380ecc2-e19f-41f3-94ff-c1bb937d71dc)File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.
GRUB menu
** Attachment added: "image20150626_165727808.jpg"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1469245/+attachment/4421052/+files/image20150626_165727808.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
/var/log/installer/partman
** Attachment added: "partman"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1469245/+attachment/4421050/+files/partman
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
Public bug reported:
Ubuntu was installed on a new Lenovo E50-00 desktop PC using a USB stick
alongside Windows 8.1. The installer was used to create a data
partition for Ubuntu. First install failed with the install hanging
while 'completely removing xfsprogs'. The install was rerun using the
F12 boot menu
** Attachment added: "image20150626_165710580.jpg"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1469245/+attachment/4421051/+files/image20150626_165710580.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
/var/log/installer/syslog
** Attachment added: "syslog"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1469245/+attachment/4421049/+files/syslog
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
Hi crx...@hotmail.com
Are you saying that you get LO's Open/Save dialogues even when the
option in Tools > Options > LibreOffice > General is not ticked (which
is the default setting)?
I only have experience of Ubuntu Linux and Windows where I always use
the system dialogues.
When I came to try
I have Version: 4.2.7.2 (using Ubuntu 4.04LTS) and there is still a
delete option on right click but it now has a 'Confirm Delete' dialogue,
which would seem to be sufficient to stop accidental deletion. The same
happens if you press the Delete key.
I would prefer it to behave like Nautilus (now
I have retested thus using LO version 4.2.7.2 and Ubuntu 14.04 and it
seems to be OK now so I am changing the status to RESOLVED/FIXED.
If any one else still has this problem using 4.2.7.2 or later, please
put it back to NEW.
--
You received this bug notification because you are a member of Ubun
Tested with mainline kernel (linux-image-3.15.0-031500rc2-generic) -
Both hotkeys and the Brightness slider in the Brightness & Lock settings
dialogue change the screen brightness correctly.
** Tags added: kernel-fixed-upstream
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
1 - 100 of 402 matches
Mail list logo
