Public bug reported:
This is likely an issue to do with having both python2.7 and 3.5 on the
machine. The work around is the same as that I gave for samba in Bug
1651660.
TL:DR Copy weakref.py from the 3.5 directory to the 2.7 directory and
edit syntax until offender installs
Patched weakref.py
Nope
kim@T610:/usr/lib/python2.7$ pycompile -p python-samba
Traceback (most recent call last):
File "/usr/bin/pycompile", line 26, in
import logging
File "/usr/lib/python2.7/logging/__init__.py", line 26, in
import sys, os, time, cStringIO, traceback, warnings, weakref, collections
Looks like I can't edit that post but just in case anyone is wondering
there is a / missing from /usr/lib/pytho2.7 in step 2.
Cheers
Kim
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1651660
Title:
OK so this is what I did to resolve the problem (I hope) Crude but it
appears to work.
1/ go to /usr/lib/pytho2.7 and rename weakref.py to weakref-org.py
2/ copy weakref.py from /usr/lib/python3.5 to usr/lib python2.7
3/ sudo apt-get -f install and edit until it runs
4/ rename the weakref-org.py b
Andreas
When you say Can you run pycompile? Are you asking me (Geokimbo) or the
Samba/Ubuntu team?
If me then I guess I can, I haven't used python but I have been writing
code for >40 years so can obviously build executables in other
languages. I have plenty of virtual machine experienc
OK I have this same issue on my work desktop, home desktop and laptop
all of which have python 2.7, 3 and 3.5. Today I also updated one of my
file servers which only has python 2.7 and it did the job happily. All
are running 16.04. So the issue is to do with python version bindings.
Although this B
I've just got back to the office and updated the desktop with apt from a
terminal and get the same thing.
Here is a copy of the traceback
Preparing to unpack
.../python-samba_2%3a4.3.11+dfsg-0ubuntu0.16.04.16_amd64.deb ...
Traceback (most recent call last):
File "/usr/bin/pyclean", line 24, in
I received the same error but do not have any cifs links in fstab nor
was I accessing an SMB remote drive at the time. Iturned my laptop on,
the software updater prompt came up and I allowed it to update whilst
getting mail . In case it is of use here is my stat report
kim@Inspiron-15:~$ stat /usr
I started up a live CD session and wiped the partitions from the two
raid volumes then did a clean install using 16.04.2 - All went as it
should do so either the problem has been fixed or it was the way I held
my mouth when installing.
Thanks
--
You received this bug notification because you are
OK I'll give it a go tomorrow if I get a break. Will let you know how I
go.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1679922
Title:
Xenial crash on install to IBM x3850 X5
To manage notificati
This is still an issue for 16.04 and an 80 "core" system. SysInfo only
shows 72 cores while lscpu shows 80. As an aside the layout of the
SysInfo GUI could do with a workover. For 4 CPUs it is fine but after
that it starts to get very red. I have 3 machines with dual hexacores
and 2 machines with
After sending this report I was returned to a Live console. I checked
the drives from disks and they looked OK. Selected install Ubuntu from
the Unity desktop and touch wood, it looks to be working with LVM
ticked, updates and third party addons unticked.
--
You received this bug notification bec
Public bug reported:
Attempting install of 16.04 to IBM server via USB. 4 physical drives
configured in RAID adapter as two groups one of one drive, the other of
3 in RAID 0. Ubuntu sees these as sda (3 drive group) and sdb (single
drive selected as boot device in raid setup). Trying install with
It appears to be fixed now though, either that or the alsamixer fix is
now sticky. If it doesn't work out of the box then do an update and if
that doesn't work try the alsamixer fix and it should then continue to
work after reboot.
--
You received this bug notification because you are a member of
I just realised my Yes was a ambiguous. Yes it still exists and has not
been fixed on 16.04.1.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1551385
Title:
No sound on ASUS Xonar DGX Soundcard (16.0
Yes. On a Dell t610. Same symptoms as above. Soundcard works fine on
CentOS 6 live so hardware is OK
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1551385
Title:
No sound on ASUS Xonar DGX Soundcard
Follow up - successfully installed 14.04 on VBox (Win 7 x 64 base)
after dropping the amount of memory required and turning off load 3rd
party apps as both these are mentioned as possible causes, above. Don't
know which one did the job but it is now a working system.
--
You received this bug not
Same issue here installing on VBox on a Win7 base. Installed just fine
on another Dell machine with VBox last week. Will try again with less
RAM allocated. While I accept the comment that RAM is not HDD and this
may be a different issue, this is the thread Launchpad directed me to
when the install
12.04 and 14.04.
Both machines are currently updating and working fine through software
updater/update manager
Cheers
Kim
On 21/02/2015 8:34 AM, Geokimbo wrote:
> Sorry for the delay in responding, I've been away.
>
> dpkg-reconfigure failed because it could not find
> ttf
Sorry for the delay in responding, I've been away.
dpkg-reconfigure failed because it could not find
ttf-mscorefonts-installer so I downloaded the exe but I don't have wine
on that machine so it is not recognised as an extractable archive by the
archive manager. I transferred the exe to a windo
Public bug reported:
I was doing an Update using the manager GUI and at the same time using
Gnome Commander to try and find a directory on the file system. Both
dialogues went dark and I had to kill them by right clicking on their
icon on the task bar. I then opened a terminal and ran apt-get upda
Same problem here with 11.04 x32 on an intel platform. Upgraded from
10.04 to 11.04 and the install froze on installing udisks. Unable to
reboot, I downloaded the 11.04 image and tried to repair the
installation from CD. This froze near the end of the install at the
clean up stage. I could still n
22 matches
Mail list logo
