hello,
thank you for the quick reply.
my problem: until about 2 months ago I had my notebook connected to my
tv (DVI/HDMI) without problems. after an update ubuntu 20.04 no longer
recognizes other monitors.
what can i do?
greetings
volker
Am 09.09.21 um 04:04 schrieb Daniel van Vugt:
> Tha
Public bug reported:
fernseher wird nach upload nicht mehr erkannt
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-81.91-generic 5.4.128
Uname: Linux 5.4.0-81-generic x86_64
NonfreeKernelModules: nvidia wl
I do agree - /boot/efi does not exist. BUT: I did for sure nothing that
made it get lost. This has been done by a bunch of regular system
updates (apt update/upgrade) w/o any interaction with me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
: 2.20.1-0ubuntu2.30
AptOrdering:
grub-efi-amd64-signed: Configure
NULL: ConfigurePending
Architecture: amd64
Date: Wed Jul 14 12:23:59 2021
DpkgHistoryLog:
Start-Date: 2021-07-14 12:23:58
Commandline: apt-get install qpdf
Requested-By: volker (1000)
DpkgTerminalLog:
grub-efi-amd64-signed (1.167
cat /sys/power/disk
yields
[disabled]
cat /sys/power/state
yields
freeze mem
Trying to change any of them (e.g. the "state" file to "mem freeze disk
standby") with
sudo vi /sys/power/state
results in vi in the notice:
'"/sys/power/state" E514: write error (file system full)
WARNING: Original
** Description changed:
Hi!
I have Ubuntu 18.04 installed (due to Petalinux requirement) where
Hibernation so far at least worked. Recently I got an update
notification, confirmed it and am now running on this version:
$ uname -a
Linux datatel-XMG-CORE-M19-GTX-1650
Public bug reported:
Hi!
I have Ubuntu 18.04 installed (due to Petalinux requirement) where
Hibernation so far at least worked. Recently I got an update
notification, confirmed it and am now running on this version:
$ uname -a
Linux datatel-XMG-CORE-M19-GTX-1650 5.4.0-77-generic
Public bug reported:
The error prevents me from updating my system.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: grub-efi-amd64-signed 1.167~16.04.4+2.04-1ubuntu44.1
ProcVersionSignature: Ubuntu 4.4.0-210.242-generic 4.4.262
Uname: Linux 4.4.0-210-generic x86_64
ApportVersion:
Hi
How do I get back from the new version in focal-proposed to the old one
in focal? Or: Will everything be okay when it goes to from focal-
proposed to focal-updates in a week?
Bye
Volker
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
e & Updates program on
the https://wiki.ubuntu.com/Testing/EnableProposed wiki page. This would
avoid confusion later.
Cheers,
Volker
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1893513
Title:
ma
Hi,
"i8042.nopnp=1 pci=nocrs" also works with Lenovo V17-IIL.
Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878279
Title:
MSFT0004:00 06CB:CD98 Touchpad/trackpad mouse randomly not
Public bug reported:
Whanted to update my 18.04 to 20.04 but it is broken.
Some month ago i installed the AMD drivers from the homepage. Could
thats the problem?
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubuntu-release-upgrader-core 1:18.04.38
ProcVersionSignature: Ubuntu
Public bug reported:
Hi
I've installed calibre (apt install calibre), and it crashes immediately
when trying to start it:
desktop ~ $ calibre
Traceback (most recent call last):
File "/usr/bin/calibre", line 20, in
sys.exit(calibre())
File "/usr/lib/calibre/calibre/gui_launch.py", line
Public bug reported:
I've configured my ssh client(s) to use a port different from 22, in
order to avoid the large number of break-in attempts on the standard
port 22. That's the "Port" setting in /etc/ssh/ssh_config. I've also
configured my ssh servers (different machines) to use that port.
Public bug reported:
I've made a fresh new install of Ubuntu 20.04 on my UEFI desktop
computer. Which works, but some wrong packages seem to be installed: The
grub-pc package, which is meant for older, BIOS-based computers, is
installed. It should be grub-efi-amd64 instead.
Tom H in ubuntu-users
PS: Reinstalling the "lsof" package doesn't fix the problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1893513
Title:
man page of lsof command broken
To manage notifications about this bug go
Public bug reported:
When trying to view the manpage of lsof, this happens:
desktop ~ $ LANG=C man lsof
man: can't open /usr/share/man/./version: No such file or directory
No manual entry for lsof
The man page is present at /usr/share/man/man8/lsof.8.gz.
This: zless
Public bug reported:
Es konnte nicht ermittelt werden, welche Systemaktualisierungen
verfügbar sind
Ein unlösbares Problem trat während der Berechnung der
Systemaktualisierung auf.
Die wurde wahrscheinlich verursacht durch:
* Inoffizielle Software-Pakete, die nicht von Ubuntu
Public bug reported:
unfortunately, I have no time to narrow this down. Maybe this bug report
has some value, maybe not.
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: ca-certificates 20180409
Uname: Linux 4.19.56-x86_64-jb1 x86_64
ApportVersion: 2.20.9-0ubuntu7.12
Architecture: amd64
bug is not fixed until today ! Not in Ubuntu 16.04 nor in Ubuntu 18.04.3
LTS (5.15.0-70-generic )
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1572132
Title:
SMBv2+ does not show all files when
same problem: ls -al 516.p*- > file or dir not found
BUT ls -al 516.pdf->then file is shown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1572132
Title:
SMBv2+ does not
+1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1743200
Title:
No support for interface labels
To manage notifications about this bug go to:
alue. (Tried in German too to make sure it's not a subtle
> translation issue.)
>
> @Volker: Can you possibly - unlike me - trigger the crash by
> navigating
> to Settings -> Details -> About?
Yes, choosing "Details" in the list to the left, causes the crash. No
"
See attachment.
Bye!
** Attachment added: "gnome-control-center_dconf.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1845931/+attachment/5292995/+files/gnome-control-center_dconf.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Am Montag, den 30.09.2019, 20:49 + schrieb Gunnar Hjalmarsson:
> Wait now... So if you reset the gnome-control-center dconf settings,
> it
> works and keeps working again?
Yes.
> It might be some kind of regression from the changes in version
> 1:3.28.2-0ubuntu0.18.04.5 which made it to
DO NOT DO THAT, what I've written in the previous comment (moving away
~/.config/dconf/user). It resets the configuration of many programs. Do
this instead, to reset only the configuration of the Gnome Control
Center:
gsettings reset-recursively org.gnome.ControlCenter
--
You received this bug
Hi.
When you move away the file ~/.config/dconf/user, then it works again.
That "user" file is automatically regenerated.
Bye
Volker Wysk
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1845
Public bug reported:
Hi.
When I start gnome-control-center, I get a segmentation fault:
(gdb) r
Starting program: /usr/bin/gnome-control-center
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffcaceb700
See also https://bugs.launchpad.net/ubuntu/+source/net-snmp/+bug/1843036
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1843012
Title:
Missing agent sections: hr_fs, hr_mem after update to
Is this maybe a duplicate of https://bugs.launchpad.net/ubuntu/+source
/net-snmp/+bug/1843012 ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1843036
Title:
[regression] SNMP missing disks in
Same Problem with Ubuntu 18-04 and xerox printer . Always out-of-paper
but this is wrong. Can not clear that or suppress that message.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/559331
Title:
As of 6.6.2019, it works with the kernel version 4.15.0-51, which is new
to (K)Ubuntu.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1831494
Title:
USB-related kernel problem with scanner
To
Am Tue, 04 Jun 2019 05:34:25 -
schrieb Kai-Heng Feng :
> Does kernel parameter "mds=off" help?
Yes, it does!
Bye,
Volker Wysk
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1831494
Public bug reported:
My Canon CanoScan LiDE 220 scanner had worked reasonably well, until a
new kernel has been installed. It went into stop-and-go mode, and made
funny noises. This is worse in higher resolutions.
I had a notion that it might be a problem with USB, which in turn resides in the
in my case, ubuntu-19.04, besides dashtodock also activity configurator
does not work anymore
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1819086
Title:
Ubuntu 19.04: Dash-to Dock
** Changed in: pinfo (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1599374
Title:
Short form of option "--node" ("-n") is present, but broken and
Public bug reported:
This fixes it:
sudo mv /usr/share/mimelnk/application/x-eqonomize.desktop
/usr/share/applications
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
Uname: Linux 4.15.0-39-generic x86_64
** Description changed:
During the installation process the desktop freezes. It is still
possible to move the mouse cursor arround, but the desktop does not
respond to mouse clicks or pressed keyboard keys.
- This happens each time I try to install ubuntu 18.04 on this noteook
+ This
Public bug reported:
During the installation process the desktop freezes. It is still
possible to move the mouse cursor arround, but the desktop does not
respond to mouse clicks or pressed keyboard keys.
This happens each time I try to install ubuntu 18.04 on this noteook
making the installation
, such as vboxdrv.ko (3 more .ko files). Maybe, these are
remnants from the previous incomplete removal of the kernel?
volker
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767133
Title:
linux-image-4.15.0
ad #3 (continued):
attempt to de - install kernel 4.15.0-21: not possible to de - install the
image 4.15.0-21!
Removed the .postrm and .generic.list files, related to this kernel, in
/var/lib/dpkg/info/ in order to be able to get "apt" working.
Found 4.15.0-20~16.04 (version april 25) in
ad #3:
earlier today, I have tested the kernel 4.15.0-21 under lubuntu-16.04,
taken from ppa:canonical-kernel-team/ppa.
So far, 3 consecutive boots without problems.
I will report back after I have de - installed this kernel again, and
have replaced it by what I find in xenial-proposed.
--
kernel 4.15.0-20, backported to 16.04:
install is okay, BUT no boot (kernel panic); afterwards, the kernel is
uninstallable!
The same behaviour is found with kernel 4.19.0-19 for bionic.
Had to remove the .postinit, .postrm, etc. files in /var/lib/dpkg/info/
in order to be able to use the apt
#15:
after modifying /etc/initramfs-tools/conf.d/resume as described it is
necessary to do
sudo update-initramfs -u.
After doing this,the boot is normal; in my case the total boot time is
6.8s.
Apparently, there is a problem with the UUID in /resume.
--
You received this bug notification
slow boot:
a description of "my bug" can obviously be found in askubuntu.com, question:
1013830.
I followed the suggestion to modify
/etc/initramfs-tools/conf.d/resume
and replaced the line RESUME=UUID= . by RESUME=none
Unfortunately, it did NOT resolve "my bug".
@nio-wiklund
Could you
@nio-wiklund
as I mentioned in #5, also in my case the bug (33sec delay during boot) occurs
with lubuntu only (not with xubuntu, kubuntu, mate, ubuntu). Thus, it appears
that the bugs reported by us may be related.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I can report the following:
- Export of a lubuntu-18.04 VM running in VB in a 32bit host with HD.
This VM does not show the delay of about 30sec.
- Import of this VM into VB on the 64bit host with SSD; on this host all
64bit lubuntu-18.04 VMs show the 30 sec delay.
- Run the 32bit VM in VB on
exactly same problem for my lubuntu/lxqt bionic 64bit installation in
virtualbox: 33.9 sec from the boot menu to login screen. No problems for
the other flavours as mentioned above.
No such problems for a 32 bit installation without SSD, again as virtual
machine.
--
You received this bug
Update of lubuntu-18.04 (and ubuntu-mate-18.04)from kernel 4.13.0-36 to kernel
4.15.0-10:
boot fails:
Boot stops shortly after the boot screen appears, then screen becomes
black. Afterwards, the system tries several times to come up with the
boot screen again, but never succeeds; then stops
Boot of both ubuntu-mate and lubuntu/lxqt (both 18.04) with kernel
4.15.0-10 in virtualbox:
Boot starts correctly until the boot screen appears; continues to boot
for the fraction of a second. Then screen becomes black. System tries
again to come up to the boot screen several times. Then stops
ad #27:
for a very recent kernel, you could try 4.14.0-17 from the canonical-
kernel-team PPA: for me (Dell e6500) it runs reliably.
However, you need the boot option acpi=off.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ad #28:
you need to use the canonical-kernel-team/unstable PPA!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1742675
Title:
after upgrade to linux-image-extra-4.13.0-26-generic the system
ad #22 and 23:
same with me: 4.13.0-31 not working
BUT 4.4.0-112 working (without boot options) (32bit installation)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1742675
Title:
after upgrade to
ad #19
I've tried 4.14.14 as well: no boot without additional boot options.
With the above mentioned 5 boot options it fails to boot "sometimes"; one out
of three, may be.
It should mention that I'm using a dell latitude e6500 for these tests; the
discrepancy between our results will probably
ad #16:
in my case, mainline kernels, including 4.15-rc8, do also not work (even
with acpi=off).
However, 4.15-rc8 boots when adding (in grub) the 5 (!) options (all
seem to be necessary) acpi=off noapic nolapic irqpoll pnpbios=off (the
first 3 options are not sufficient; the last two options
for me,lubuntu,16.04, 32 bit installation, no kernels 4.13 and 4.14
boot, neither without or with acpi=off. Without acpi=off, boot stops
right after leaving the grub menu; with acpi=off after the message
"starting to show plymouth boot screen".
Neither does kernel 4.14.14-041414 boot; it fails
*** This bug is a duplicate of bug 1637026 ***
https://bugs.launchpad.net/bugs/1637026
Hello, I 've got the same problem with DB2. When I'm leaving the system
as the DB instance owner, all procs are killed. I guess, it depends on
the new systemd in 1604. ( see /var/log/syslog "received
Public bug reported:
This is a feature request.
I have an encrypted SSD which I want to use as a cache (an LVM-Cache)
for my encrypted harddisc.
The cached root filesystem depends on *both* crypto discs. The new
cached root volume is created from the original root volume
("OriginLV"), and two
Am Mittwoch, 11. Oktober 2017, 13:07:43 CEST schrieben Sie:
> Oh I see, sorry for misunderstanding that part (I'm the cli type).
> This is nothing that is missing due to Ubuntu, so you'd best report upstream
> as feature request at I think [1] for virt-manager. If you happen to do so
> please
Am Mittwoch, 11. Oktober 2017, 07:13:06 CEST schrieben Sie:
> Hi Volker,
> how about:
> $ vrish domrename
Okay, I mean there is no way to rename a virtual machine _in_the_virt-
manager_GUI_. Thanks for the hint.
Bye
V.W.
--
You received this bug notification because you are a member
Public bug reported:
I'm missing a function to rename virtual machines, once they are
created.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: virt-manager 1:1.3.2-3ubuntu1.16.04.4
ProcVersionSignature: Ubuntu 4.4.0-96.119-generic 4.4.83
Uname: Linux 4.4.0-96-generic x86_64
ApportVersion:
Yes I am. This matters..?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1712981
Title:
wrong keyboard localization when entering the password
To manage notifications about this bug go to:
Public bug reported:
This is known bug in dar/libdar. It is fixed in the newest upstream
version (2.5.12).
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: dar 2.5.3-1ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
Uname: Linux 4.4.0-93-generic x86_64
ApportVersion:
Public bug reported:
When you enter the new passphrase in the ubuntu installer, the keyboard
is still in English localization. When you enter it in the fresh
installed Ubuntu, then the configured localization is in place.
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: ubiquity 17.04.9
ad #16 to 19:
the problem, as described above, has disappeared with kernel 4.11.0-11
-> internet access is possible when strongswan vpn is activated.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ad #16:
the problem, as described above, still exists with kernel 4.11.0-9.
Upgrading to 4.12.0-4 solves the problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1698918
Title:
no internet
ad 16:
problem still exists with kernel 4.11.0-8: no internet access when strongswan
vpn is activated.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1698918
Title:
no internet connection when
add #16:
Thanks for your comments and suggestions!
kernel 4.11.0-7 has the same problem as the previous 4.11 builds:
strongswan vpn is activated, but no access to internet is possible.
Mainline kernel 4.11.6 (version from 17-06-2017): As I mentioned in one
of my previous mails to you, it has
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1698918/+attachment/4898749/+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/1698918
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1698918/+attachment/4898748/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1698918/+attachment/4898750/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1698918/+attachment/4898743/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1698918/+attachment/4898752/+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/1698918
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1698918/+attachment/4898751/+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/1698918
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1698918/+attachment/4898754/+files/WifiSyslog.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs,
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1698918/+attachment/4898753/+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/1698918
Title:
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1698918/+attachment/4898745/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1698918/+attachment/4898746/+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/1698918
Title:
no
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1698918/+attachment/4898744/+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/1698918
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1698918/+attachment/4898742/+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/1698918
Title:
no
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1698918/+attachment/4898747/+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/1698918
: 2.20.1-0ubuntu2.6
+ Architecture: i386
+ AudioDevicesInUse:
+ USERPID ACCESS COMMAND
+ /dev/snd/controlC0: volker 1718 F pulseaudio
+ CurrentDesktop: LXDE
+ DistroRelease: Ubuntu 16.04
+ HibernationDevice: RESUME=UUID=2deede5a-0aed-44ba-b9f5-be790bc7c030
+ InstallationDate: Installed
Public bug reported:
After the update from 4.10.0-22 to 4.11.0-6 there is no connection to the
internet anymore after starting strongswan vpn, v5.5.1. Strongswan vpn starts
as expected, but no http - connections can be established.
The same problem with the mainline kernel 4.6.11.
Downgrading
ad #7:
I confirm that your recent build 4.9.0-8 in ppa:canonical-kernel-team/unstable
boots properly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1642192
Title:
i386 4.9 in -proposed fails to
ad #5:
with the kernel 4.9-rc8 the boot problem described above has returned! No boot
possible; same behaviour as for the kernel versions BEFORE 4.9-rc7.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
at #4:
with the newest version of kernel 4.9, namely 4.9-rc7, the problem
mentioned above has disappeared: I can boot correctly with this new
kernel version for lubuntu-17.04. This holds for a lubuntu-17.04 VM
under virtualbox.
--
You received this bug notification because you are a member of
No boot with any of the the available 4.9 kernels, in particular
4.9.0-1, under Lubuntu-17.04 and 16.04.
Find similar lines in the console log, in particular the following which
was mentioned above:
Begin: Waiting for root file system ... Begin: running /scripts/local-block ...
done.
Begin:
Public bug reported:
lxqt was installed with lxqt metapackage. Afterwards, ppa:lxqt/ppa was
added, and update made via sudo apt-get update.
ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: liblxqt-l10n (not installed)
ProcVersionSignature: Ubuntu 4.6.0-12.14-generic 4.6.7
Uname: Linux
Public bug reported:
1)
Description:Ubuntu 16.04 LTS
Release:16.04
2)
openjdk-9-jdk:
Installed: (none)
Candidate: 9~b114-0ubuntu1
Version table:
9~b114-0ubuntu1 500
500 http://de.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
3)
I expected the package
d be best fixed
> directly in Debian, and then Ubuntu will pick up the fix automatically.
>
> Would you mind filing a bug with Debian please?
Okay, done.
Volker
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
Public bug reported:
Fetchmail supports only one mail account in conjunction with IMAP IDLE.
That's a pity. However, it should at least produce a proper error
message when IMAP IDLE is used and several accounts exist.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: fetchmail 6.3.26-2
Public bug reported:
Right click folder
Select to share
was asked to install additional packages
installation failed
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: grub2-common 2.02~beta2-36ubuntu3.2
ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
Uname: Linux 4.4.0-34-generic
** Description changed:
The option "--node" of "pinfo" is used to initially navigate to a section of
the info page (a node),
in the same way it is implemented in "info".
This option is important when accessing long info pages.
It could be expected that the option is compatible with
Public bug reported:
The option "--node" of "pinfo" is used to initially navigate to a section of
the info page (a node),
in the same way it is implemented in "info".
This option is important when accessing long info pages.
It could be expected that the option is compatible with "info",
and
ad #15:
I also feel that we talk about two different issues.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1570352
Title:
strongswan vpn cannot be established via the network-manager
To manage
ad #12:
Strange, for me, vpn can be established also from the GUI. I checked it with
two machines, both Lubuntu-16.04 under kernels 4.4.0-25 and 4.6.0-7.
Have you checked that you can set - up vpn via the console by using the
"ipsec" commands? (That worked also when I had the problem with
strongswan vpn, establishing connection via network manager:
with the most recent version of the network-manager-gnome,
v1.2.0-0ubuntu.16.04.3, vpn can again be established via the network
manager! No complaints anymore from my side.
--
You received this bug notification because you are a
Public bug reported:
I have no idea, this bug occured while installing the update 16.04
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: gnome-menus 3.13.3-6ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
NonfreeKernelModules:
To me the thumbnails are rather too small,
on a 2560x1600, 101 dpi screen (30").
The solution is the same, described in the current title:
"Static Application Switcher needs ability to change thumbnail size"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
The package description of the text theme package,
"plymouth-theme-ubuntu-text"
as shown in aptitude etc,
states it is a logo theme, just like
"plymouth-theme-ubuntu-logo" which is confusing
without much context.
The description of "plymouth-theme-ubuntu-text" is:
1 - 100 of 602 matches
Mail list logo
