In the older versions of Ubuntu, an incorrect UUID could be ignored with
. Now for a faulty UUID in the fstab, I can only start my
computer with a Live CD and correct the fstab. The older solution was
great.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
The error is in Ubuntu 16.10 too.
The error is really annoying.
If a UUID changes and the fstab is not corrected then the computer can be only
started using an live-CD
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
With my motherboard I can manage disks with MBR and GPT disks in UEFI
mode. If I install Ubuntu with MBR disks, the installation hangs on the
choice of the partitions. If I install Ubuntu on hard drives with GPT
and UEFI mode, there are no problems with the installation!
--
You received this bug
** Changed in: file-roller (Ubuntu)
> Status: New => Incomplete
>
Hello,
I don't often works with rpm-archives.
I just opened a rpm-archive und now file-roller 3.2.1 works correctly.
Regards Dieter Baum
--
You received this bug notification because you are a member of U
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/881559
Title:
In Oneiric 64 bit file-roller dont open an rpm file
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+sourc
Public bug reported:
It is not possible to open an rpm archiv
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: file-roller 3.2.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.23-0ubuntu3
Arch
Am 20.08.2010 21:34, schrieb Giuseppe Sacco:
> The problem is in Lucid hylafax version: it does not unmout correctly
> /var/spool/hylafax/etc and give error during updates and reinstall. The
> fix is quite simple: upgrade hylafax after having stopped it.
>
> ** Changed in: hylafax (Ubuntu)
>
Am 18.08.2010 11:48, schrieb Giuseppe Sacco:
> Ok, probably I understood the problem: the /var/spool/hylafax/etc remain
> mounted even when stopping hylafax. Try to check it this way
>
> # /etc/init.d/hylafax stop
> # mount
> .. check if it is mounted
> # umount /var/spool/hylafax/etc
> # dpkg --co
Am 17.08.2010 16:04, schrieb Giuseppe Sacco:
> Could you try updating the packages while hylafax is stopped? Please
> type these commands:
>
> # /etc/init.d/hylafax stop
> # dpkg --configure hylafax-server
> # dpkg --configure hylafax-client
> # /etc/init.d/hylafax start
>
>
These are the mess
Am 17.08.2010 16:04, schrieb Giuseppe Sacco:
> Could you try updating the packages while hylafax is stopped? Please
> type these commands:
>
> # /etc/init.d/hylafax stop
> # dpkg --configure hylafax-server
> # dpkg --configure hylafax-client
> # /etc/init.d/hylafax start
>
>
I have restore my r
Am 17.08.2010 12:33, schrieb Giuseppe Sacco:
> Hi,
> was you updating the system from a previous Ubuntu version? In that case, do
> you know what was prevous hylafax version?
>
> Thanks,
> Giuseppe
>
>
Hallo Giuseppe,
Sorry my bad english.
I have installed hylafax 2:6.0.3-5.1ubuntu1 on my c
** Attachment added: "AptOrdering.txt"
https://bugs.launchpad.net/bugs/619139/+attachment/1494966/+files/AptOrdering.txt
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/619139/+attachment/1494967/+files/Dependencies.txt
** Attachment added: "Df.txt"
https://bug
Public bug reported:
I dont have mor informations. The report was create automatically.
Greetings.
ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: hylafax-client 2:6.0.3-5.1ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-24.39-generic 2.6.32.15+drm33.5
Uname: Linux 2.6.32-24-generic x86_64
13 matches
Mail list logo