I do not think there can be anything more concrete.
I think I have followed everything prescribed (yes it is time consuming for me
to read all that tons of text, but do wonder - I did it..)
Now, if you guys do not have capacity to investigate, it'd be quite fair to
admit that, rather than tryin
Or do you want me to record a video ?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2025027
Title:
When I disconnect PC from LAN, I can't turn on Wi-Fi software-w
gtk package dropped in 1.5.5-10
Please re-open if seen in the qt package
** Changed in: winff (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad
** Changed in: winff (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1399945
Title:
Settings, Preferences, ect. - All key
The entry in /usr/lib/tmpfiles.d/sshd.conf SHOULD be:
d /run/sshd 0755 root root
When it isn't, sshd cannot be started up after a reboot.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchp
I have the same problem on two machines running Ubuntu 18.04 with a Sony
WH-1000XM2.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1724919
Title:
Bluetooth headphones
identical for me. My problem reporting has not been disabled:
$ cat /etc/default/apport
# set this to 0 to disable apport, or to 1 to enable it
# you can temporarily override this with
# sudo service apport start force_start=1
enabled=1
--
You received this bug notification because you are a mem
The mouse is one of the most important parts of a laptop and it plays a
role of the indicator and helps us to swipe the cursor over the monitor,
but if you are having an issue with the mouse, then
https://epsonsupports.net/blog/epson-printer-not-printing/ will help you
a lot in this regarding.
--
I had the same problem with ssh, after reboot I was not able to SSH to
the server.
My solution to the SSH problem was the following (through an emergency
console session from the VPS provider's control panel):
sudo nano /etc/ssh/sshd_config
Find:
UsePrivilegeSeperation yes
and change to:
UsePriv
Output of uname -a:
Linux newpnc 2.6.32-042stab132.1 #1 SMP Wed Jul 11 13:51:30 MSK 2018
x86_64 x86_64 x86_64 GNU/Linux
Output of mount | grep run:
tmpfs on /run type tmpfs (rw,nosuid,nodev,mode=755)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
none on /run/shm type
Ah ok, thank you for the information.
Since it is an OpenVZ container, I assume my only option is to apply the
temporary solution above, then start to look for a VPS provider that
supports a more current kernel version (or one that would let me upgrade
the kernel).
Thanks again.
Peter
--
You
Public bug reported:
My Samsung CLP-680ND printer is set up on a wired network. It works
correctly from a Windows 10 laptop, printing duplex (double sided)
pages. On Ubuntu 18.04 and 18.10 it does not print duplex although the
option can be selected on the print dialogue. Otherwise printing is OK.
I ran into the same problem on "Ubuntu 18.04.2 LTS" but the only
required thing to fix it was to run "sudo update-initramfs -u".
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bug
Public bug reported:
Troubleshoot steps followed:
https://wiki.ubuntu.com/Hotkeys/Troubleshooting.
I can try provide info from https://wiki.ubuntu.com/DebuggingProcedures
if wanted.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: udev 237-3ubuntu10.22
ProcVersionSignature: Ubuntu 4.15.0-51
** Package changed: systemd (Ubuntu) => udev (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1833443
Title:
Calculator button does nothing (Calculator not launched
Here's is the Crash.log of Update-Manager.
** Attachment added: "crash.log"
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1834055/+attachment/5272860/+files/crash.log
** Description changed:
Hi!
I updated some packages + to kernel 4.15.0-52-generic in Ubuntu-Mate.
After that
Public bug reported:
Hi!
I updated some packages + to kernel 4.15.0-52-generic in Ubuntu-Mate.
After that I can't open the "Update-Manager + software-properties-gtk"
anymore.
Terminal Output:
Segmentation fault
Kern.log:
Jun 24 17:29:35 user1 kernel: [ 3571.244993] update-manager[14392]: segfa
Public bug reported:
Processing triggers for initramfs-tools (0.133ubuntu10) ...
ln: failed to create hard link '/boot/initrd.img-4.15.0-1045-raspi2.dpkg-bak'
=> '/boot/initrd.img-4.15.0-1045-raspi2': Operation not permitted
update-initramfs: Generating /boot/initrd.img-4.15.0-1045-raspi2
Unsuppo
Julian,
unfort. testing the patch above against a bionic system didn't help, I'm
still getting duplicate deb-src entries
# deb-src http://ppa.launchpad.net/juju/stable/ubuntu bionic main
# deb-src http://ppa.launchpad.net/juju/stable/ubuntu bionic main
# deb-src http://ppa.launchpad.net/juju/stab
I have the same problem with eboard 1.1.3 on Debian Buster. The program
build is quite old (2016), hence it seems that the problem is with some
high-level library.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+2.0 in Ubu
Public bug reported:
Regression with Ryzen 3 2200G, UEFI Asrock B450 Pro4 motherboard and
55-75 Hz monitor.
Booting Xubuntu 19.10 live iso with safe graphics options did give a
stable desktop display, but
xubuntu@xubuntu:~$ xrandr
xrandr: Failed to get size of gamma for output default
Screen 0:
I have a completely encrypted home (auto configured) in bionic and have
the same error messages in dmesg. Moreover, since a few weeks ago, the
home directory sometimes gets broken in a way that all list requests
(ls, browse in nautilus) hang just on the home directory (process in S
state) and only
I forgot to mention: when attaching strace to the problematic ls, strace
also hangs and cannot be interrupted with CTRL+C - the console is
practically dead.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to coreutils in Ubuntu.
Public bug reported:
Recently (last 1 month) I encounter the problem that after waking up the
computer from sleep mode (suspend to RAM) sometimes the home directory
(encrypted) becomes inaccessible to programs.
For example ls ~/ will just hang in S mode.
Attaching an strace to ls from another co
** Changed in: upower (Ubuntu)
Status: Expired => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upower in Ubuntu.
https://bugs.launchpad.net/bugs/1744366
Title:
xfce power manager shows wrong battery life
I forgot to post the version of upower I am running:
peter@peter-Studio-1558:~$ apt show upower
Package: upower
Version: 0.99.4-2ubuntu0.3
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upower in Ubuntu.
https
that it reports an unusually high energy-full value
(>65Wh) whereas the design capacity is actually much smaller (~5Wh). I
speculate that this could cause confusion into the actual state of
charge and may prematurely shut the laptop down....
peter@peter-Studio-1558:~$ upower -d
Device: /
We're seeing this in the context of a charm where add-apt-repository is
called periodically. We ended up with a sources.list file weighing in at
2.6Mb, which created problems for the regex engine there. In light of
this can I ask to reconsider the "low" importance of this bug?
FTR. this is Bionic,
clarification: breaking regex parsing at /usr/lib/python3/dist-
packages/aptsources/sourceslist.py that is
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-apt in Ubuntu.
https://bugs.launchpad.net/bugs/1311056
Title:
Public bug reported:
When enabling UCA a hyperlink is printed:
$ sudo add-apt-repository cloud-archive:train-proposed
Ubuntu Cloud Archive for OpenStack Train
For Bionic,
$ lsb_release -c
Codename: bionic
$ dpkg-query -W software-properties-common
software-properties-common 0.96.24.32.11
$ sudo add-apt-repository cloud-archive:rocky
Ubuntu Cloud Archive for OpenStack Rocky
More info: https://wiki.ubuntu.com/OpenStack/CloudArchive
Press [E
For Xenial,
$ lsb_release -c
Codename: xenial
$ dpkg-query -W software-properties-common
software-properties-common 0.96.20.9
$ sudo add-apt-repository cloud-archive:ocata
Ubuntu Cloud Archive for OpenStack Ocata
More info: https://wiki.ubuntu.com/OpenStack/CloudArchive
Press [ENTER
Subscribing field-medium, we're seeing this repeatedly
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-apt in Ubuntu.
https://bugs.launchpad.net/bugs/1311056
Title:
apt-add-repository adds duplicate commented/disable
** Tags added: canonical-bootstack
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cron in Ubuntu.
https://bugs.launchpad.net/bugs/1779767
Title:
Default cron PATH does not include /snap/bin
Status in cron package in Ubunt
Public bug reported:
graphics drivers on ubuntu 18.04 problem.
Live cd works ok, ubuntu 16 works ok.
Graphics card is atom series .. im thing
THANKS FOR HELP
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
Uname: Linux 4.18.0-041800-generic x86_64
NonfreeKernelModules
Public bug reported:
Installed live session on a Dell XPS 13. Runs really well but after
enabling wayland and turning on the experimental bits
gsettings set org.gnome.mutter experimental-features "['scale-monitor-
framebuffer']"
I still don't get fractional scaling on the single laptop screen (1
Issue finally went away for me after upgrading to 18.04.3 LTS.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1173915
Title:
initctl continuously takes 100% of CPU
Status
Public bug reported:
With python 2.7.17, ujson==1.35 does not install from PyPI properly.
This was not a problem with 2.7.15-4ubuntu4~18.04.2.
The root cause is likely during the `bdist_wheel` operation, as a whl
built with python 2.7.15 will install and function under 2.7.17.
Steps to reproduce
Using python-ujson is not an option unfortunately as my full use case
also involves a virtualenv.
That said, I’m wondering if this may also cause problems in python-ujson
the next time the deb needs to be built from sources, perhaps in a mass
rebuild?
--
You received this bug notification becaus
Have you tried to disable the UFW
sudo ufw disable
to check if the Firewall is interfering? You can enable it again with
sudo ufw enable
if the firewall it not the culprit.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wi
The fixup was included in Mesa 18.0.1 - so if you rebase on upstream's
stable point-release above patch would not be needed anymore.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bu
See: https://cgit.freedesktop.org/mesa/mesa/log/?h=mesa-18.0.1 and
exactly:
https://cgit.freedesktop.org/mesa/mesa/commit/?h=mesa-18.0.1&id=19db663cf028c184b1173795d1d38b152743e781
and also mentioned in the Changelog:
Mark Thompson (1): st/va: Enable vaExportSurfaceHandle()
--
You received this
Public bug reported:
after trying to upgrade from 16.04 to 18.04 Ive got 17.10 and now im
stuck with a system error
ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: systemd-sysv 234-2ubuntu12.3
ProcVersionSignature: Ubuntu 4.13.0-39.44-generic 4.13.16
Uname: Linux 4.13.0-39-generic x86_6
Public bug reported:
error occurred at initial boot-up
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: bluez 5.37-0ubuntu5.1
ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
Uname: Linux 4.13.0-39-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.16
Architecture: amd64
Date
Public bug reported:
If environment variable name defined in AuthorizedKeysFile contains underscore
character (environment="FOO_BAR=1" ...), sshd refuses connection and throws
following error:
authorized_keys:1: bad key options: invalid environment string
** Affects: openssh (Ubuntu)
Impor
directory
dpkg-query: no packages found matching gtk
Gtk-Message: 11:21:20.142: GtkDialog mapped without a transient parent. This is
discouraged.
peter@peter-GeForce6100PM-M2:~$ apport-bug light-themes
(apport-gtk:19203): Gtk-WARNING **: 11:29:01.986: Theme parsing error:
gtk-main.css:73:38: Failed to
Public bug reported:
Ubuntu prepares to ship libva 2.1 and mesa 18.x for Bionic. Mesa misses
one tiny patch to make modern AMD GPUs work with VAAPI on wayland / gbm
/ mir. We tried to get this into final 18.0 but was not yet accepted.
The change itself is a minor. Without it a certain feature is n
See the Purism "Design report #4: symbiotic applications" for a very
similar approach:
- https://puri.sm/posts/librem5-progress-report-8/
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtubuntu in Ubuntu.
https://bugs.launch
Hello,
I also confirm this bug on 2 computers with Kubuntu 16.04.
By selecting XRender as the rendering engine everything works.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs
Public bug reported:
Appears identical to Bug #815996, except my system freezes on
I can recover using the same followed by
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-101.124-generic 4.4.95
Uname: Linux 4.4.0-101-generic x86_64
hi again,
sorry, I don't know much about reporting bugs (its my first bug-report), but I
think, what has to be done, is creating a new-version-package of librsvg for
ubuntu 16.04.
where do I have to ask for this?
I'm not shure, but as Nautilus says "Gleitkomma Ausnahme" (floating point
exceptio
Public bug reported:
I cannot understand this error.
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: systemd 235-3ubuntu2
ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
Uname: Linux 4.13.0-19-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
ApportVersion: 2.20.8-0ubuntu
Public bug reported:
If a user is over quota, or if the home directory disk is full, they get
logged out straight after logging in, when the home directory is on NFS.
No information is presented to the user that would let them know the
problem.
This is because of an error in the way that lightdm
** Bug watch added: Sourceware.org Bugzilla #22273
https://sourceware.org/bugzilla/show_bug.cgi?id=22273
** Also affects: glibc via
https://sourceware.org/bugzilla/show_bug.cgi?id=22273
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a me
This issue was also reported at the WSL GitHub project:
https://github.com/Microsoft/WSL/issues/2615
The reason seems to be a bug in glibc that has been fixed a few months ago:
https://sourceware.org/bugzilla/show_bug.cgi?id=22273
To fix this we need this patch for glibc in 17.10.
** Bug watch a
Please, first check if "dmsetup udevcomplete" is called from within udev
rules.
To check that, you need to enable udevd debug mode (e.g. configure
udev_log="debug" in /etc/udev/udev.conf). Then watch systemd journal for
systemd-udevd messages:
journalctl -f -u systemd-udevd
Then try to run th
Public bug reported:
Not much to report there was an error when this package as to install in
the background
Description:Ubuntu 17.10
Release:17.10
openssh-server:
Installed: 1:7.5p1-10ubuntu0.1
Candidate: 1:7.5p1-10ubuntu0.1
Version table:
*** 1:7.5p1-10ubuntu0.1 500
Public bug reported:
Attempts to launch bash in an arm64 qemu-user environment in bionic
results in the following error message:
bash: xmalloc: .././shell.c:1709: cannot allocate 10 bytes (0 bytes
allocated)
This causes any qemu/chroot based bootstrapping to fail as many packages
invoke bash dur
and performing a shutdown/reboot
everything is o.k.
(Sometimes -- seldomly -- on tty1 an error message was shown.)
peter@TP:~/bin$ uname --all
Linux TP 4.4.0-83-generic #106-Ubuntu SMP Mon Jun 26 17:54:43 UTC 2017 x86_64
x86_64 x86_64 GNU/Linux
+ ---
+ .tmp.unity_support_test.0
e.
After switching to tty1, logging in and performing a shutdown/reboot
everything is o.k.
(Sometimes -- seldomly -- on tty1 an error message was shown.)
peter@TP:~/bin$ uname --all
Linux TP 4.4.0-83-generic #106-Ubuntu SMP Mon Jun 26 17:54:43 UTC 2017 x86_64
x86_64 x86_64
e.
After switching to tty1, logging in and performing a shutdown/reboot
everything is o.k.
(Sometimes -- seldomly -- on tty1 an error message was shown.)
peter@TP:~/bin$ uname --all
Linux TP 4.4.0-83-generic #106-Ubuntu SMP Mon Jun 26 17:54:43 UTC 2017 x86_64
x86_64 x86_64
ng to tty1, logging in and performing a shutdown/reboot
everything is o.k.
(Sometimes -- seldomly -- on tty1 an error message was shown.)
peter@TP:~/bin$ uname --all
Linux TP 4.4.0-83-generic #106-Ubuntu SMP Mon Jun 26 17:54:43 UTC 2017 x86_64
x86_64 x86_64 GNU/Linux
---
.tmp.unity_su
ng to tty1, logging in and performing a shutdown/reboot
everything is o.k.
(Sometimes -- seldomly -- on tty1 an error message was shown.)
peter@TP:~/bin$ uname --all
Linux TP 4.4.0-83-generic #106-Ubuntu SMP Mon Jun 26 17:54:43 UTC 2017 x86_64
x86_64 x86_64 GNU/Linux
---
.tmp.unity_supp
itching to tty1, logging in and performing a shutdown/reboot
everything is o.k.
(Sometimes -- seldomly -- on tty1 an error message was shown.)
peter@TP:~/bin$ uname --all
Linux TP 4.4.0-83-generic #106-Ubuntu SMP Mon Jun 26 17:54:43 UTC 2017 x86_64
x86_64 x86_64
switching to tty1, logging in and performing a shutdown/reboot
everything is o.k.
(Sometimes -- seldomly -- on tty1 an error message was shown.)
peter@TP:~/bin$ uname --all
Linux TP 4.4.0-83-generic #106-Ubuntu SMP Mon Jun 26 17:54:43 UTC 2017 x86_64
x86_64 x86_64
e.
After switching to tty1, logging in and performing a shutdown/reboot
everything is o.k.
(Sometimes -- seldomly -- on tty1 an error message was shown.)
peter@TP:~/bin$ uname --all
Linux TP 4.4.0-83-generic #106-Ubuntu SMP Mon Jun 26 17:54:43 UTC 2017 x86_64
x86_64 x86_64
s possbile.
After switching to tty1, logging in and performing a shutdown/reboot
everything is o.k.
(Sometimes -- seldomly -- on tty1 an error message was shown.)
peter@TP:~/bin$ uname --all
Linux TP 4.4.0-83-generic #106-Ubuntu SMP Mon Jun 26 17:54:43 UTC 2017 x86_64
x86_64 x86_64
e.
After switching to tty1, logging in and performing a shutdown/reboot
everything is o.k.
(Sometimes -- seldomly -- on tty1 an error message was shown.)
peter@TP:~/bin$ uname --all
Linux TP 4.4.0-83-generic #106-Ubuntu SMP Mon Jun 26 17:54:43 UTC 2017 x86_64
x86_64 x86_64
switching to tty1, logging in and performing a shutdown/reboot
everything is o.k.
(Sometimes -- seldomly -- on tty1 an error message was shown.)
peter@TP:~/bin$ uname --all
Linux TP 4.4.0-83-generic #106-Ubuntu SMP Mon Jun 26 17:54:43 UTC 2017 x86_64
x86_64 x86_64
ng to tty1, logging in and performing a shutdown/reboot
everything is o.k.
(Sometimes -- seldomly -- on tty1 an error message was shown.)
peter@TP:~/bin$ uname --all
Linux TP 4.4.0-83-generic #106-Ubuntu SMP Mon Jun 26 17:54:43 UTC 2017 x86_64
x86_64 x86_64 GNU/Linux
---
.tmp.unity_supp
switching to tty1, logging in and performing a shutdown/reboot
everything is o.k.
(Sometimes -- seldomly -- on tty1 an error message was shown.)
peter@TP:~/bin$ uname --all
Linux TP 4.4.0-83-generic #106-Ubuntu SMP Mon Jun 26 17:54:43 UTC 2017 x86_64
x86_64 x86_64
itching to tty1, logging in and performing a shutdown/reboot
everything is o.k.
(Sometimes -- seldomly -- on tty1 an error message was shown.)
peter@TP:~/bin$ uname --all
Linux TP 4.4.0-83-generic #106-Ubuntu SMP Mon Jun 26 17:54:43 UTC 2017 x86_64
x86_64 x86_64
itching to tty1, logging in and performing a shutdown/reboot
everything is o.k.
(Sometimes -- seldomly -- on tty1 an error message was shown.)
peter@TP:~/bin$ uname --all
Linux TP 4.4.0-83-generic #106-Ubuntu SMP Mon Jun 26 17:54:43 UTC 2017 x86_64
x86_64 x86_64
e.
After switching to tty1, logging in and performing a shutdown/reboot
everything is o.k.
(Sometimes -- seldomly -- on tty1 an error message was shown.)
peter@TP:~/bin$ uname --all
Linux TP 4.4.0-83-generic #106-Ubuntu SMP Mon Jun 26 17:54:43 UTC 2017 x86_64
x86_64 x86_64
s possbile.
After switching to tty1, logging in and performing a shutdown/reboot
everything is o.k.
(Sometimes -- seldomly -- on tty1 an error message was shown.)
peter@TP:~/bin$ uname --all
Linux TP 4.4.0-83-generic #106-Ubuntu SMP Mon Jun 26 17:54:43 UTC 2017 x86_64
x86_64 x86_64
ng to tty1, logging in and performing a shutdown/reboot
everything is o.k.
(Sometimes -- seldomly -- on tty1 an error message was shown.)
peter@TP:~/bin$ uname --all
Linux TP 4.4.0-83-generic #106-Ubuntu SMP Mon Jun 26 17:54:43 UTC 2017 x86_64
x86_64 x86_64 GNU/Linux
---
.tmp.unity_supp
e.
After switching to tty1, logging in and performing a shutdown/reboot
everything is o.k.
(Sometimes -- seldomly -- on tty1 an error message was shown.)
peter@TP:~/bin$ uname --all
Linux TP 4.4.0-83-generic #106-Ubuntu SMP Mon Jun 26 17:54:43 UTC 2017 x86_64
x86_64 x86_64
ng to tty1, logging in and performing a shutdown/reboot
everything is o.k.
(Sometimes -- seldomly -- on tty1 an error message was shown.)
peter@TP:~/bin$ uname --all
Linux TP 4.4.0-83-generic #106-Ubuntu SMP Mon Jun 26 17:54:43 UTC 2017 x86_64
x86_64 x86_64 GNU/Linux
---
.tmp.unity_su
(only once during the last few weeks,
If I remember it correctly) and is not predictable.
Best regards, Peter
On Mon, 26 Feb 2018, Christopher M. Penalver wrote:
> Peter Schmitt, to see if this is already resolved in your release,
could
> you please update your HWE stack as per
> https://wik
Public bug reported:
In Ubuntu 16.04.3 and 17.10.1 holding down either shift key on a Dell
Latitude 7480 causes random mouse clicks to occur without being nowhere
near the touchpad with palms. No external mouse/keyboard connected.
Disabling `Tap to click` in `Mouse & Touchpad` settings makes the
p
Public bug reported:
mouse only partial usuable...: move around no execute commands
possible...!!
screen is not changeable...?
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-37-gener
Public bug reported:
No idea
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: systemd-sysv 237-3ubuntu10.3
ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
Uname: Linux 4.15.0-33-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Thu Aug 30 10:56:28 2018
E
Public bug reported:
1.)
Ubuntu 14.04.1 LTS
2.)
Package version:
isc-dhcp-client 4.2.4-7ubuntu12.13
3.)
I have attempted to run dhclient using the '-cf' option to pass the path
to a custom configuration file in '/etc'. My custom configuration
differs from the default as it does not request
** Description changed:
1.)
Ubuntu 14.04.1 LTS
2.)
Package version:
isc-dhcp-client 4.2.4-7ubuntu12.13
-
3.)
I have attempted to run dhclient using the '-cf' option to pass the path
to a custom configuration file in '/etc'. My custom configuration
differs from
*** This bug is a duplicate of bug 1704174 ***
https://bugs.launchpad.net/bugs/1704174
** This bug has been marked a duplicate of bug 1704174
update apparmor rules to include wicd's dhclient.conf file
--
You received this bug notification because you are a member of Ubuntu
Touch seeded pa
Public bug reported:
Since using Ubuntu 18.04.1 LTS on boot at the login screen the screen is
frozen. I tried both gdm3 and lightdm login managers, with either I
don't get into the system.
I am using Intel 2nd generation (Sandy bridge) CPU with on-board GPU: HD
Graphics 2000. I have an external 2
Public bug reported:
This is a Zotac CI547 box. It has to video outputs: one HDMI and one
DisplayPort. The HDMI port appears as DP-1 in the logs, the DisplayPort
as DP-2. The hardware is Intel HD 620 and is allegedly able to run two
displays simultaneously at 4K. I have one WQHD monitor (=2560x144
Any progress on this? Nobody can confirm the issue. Have you tried
anything, upgrading, other fixes?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libdc1394-22 in Ubuntu.
https://bugs.launchpad.net/bugs/1671118
Title:
pac
Public bug reported:
Whilst working normally, I was unable to interact with gnome-shell. The
clock at the top of the screen continued to increment, and I could ssh
in to the machine, but clicking anywhere on the screen resulted in
nothing. Changing to another VTY and back again had no effect.
I
my syslog just says:
syslog:Aug 18 08:28:26 blacklab systemd-resolved[868]: Positive Trust Anchors:
syslog:Aug 18 08:28:26 blacklab systemd-resolved[868]: . IN DS 19036 8 2
49aac11d7b6f6446702e54a1607371607a1a41855200fd2ce1cdde32f24e8fb5
syslog:Aug 18 08:28:26 blacklab systemd-resolved[868]: . IN
This may be related:
https://unix.stackexchange.com/questions/207999/mouse-recognized-as-keyboard-xinput-fedora-22
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1554471
Title:
> Precise archive is only signed with the old key. To support using the
precise archive in newer releases, such as with debootstrap, we need to
do the following ...
This comment implied to me that the use of debootstrap to create an
Ubuntu 12.04 chroot on e.g. Ubuntu 18.04 (which includes the ubun
Going over my notes on this topic I realized that I hadn't pointed out
in my previous message that the issue I've pointed out has already
triggered a workaround (that shouldn't be necessary IMHO) in the
pbuilder project:
https://bugs.launchpad.net/ubuntu/+source/pbuilder/+bug/599394
In my opinion
It's a shame I can't edit comments on Launchpad: Please disregard my
last comment, I seem to have misread the pbuilder issue, sorry for the
noise. That doesn't change the validity of my point about updating
debootstrap though.
--
You received this bug notification because you are a member of Ubun
For whatever it's worth: I wouldn't mind spending a bit of time trying
to set up https://python-apt.readthedocs.io/ based on the git repository
at https://git.launchpad.net/ubuntu/+source/python-apt, although I can't
tell if this plan will actually work without trying it (for example I
don't know i
Public bug reported:
While working on the development of a Python package I created (deb-pkg-
tools) that uses python-apt and refers to its documentation I noticed
that the online documentation seems to have disappeared...
This makes it impossible for my project to cross-reference the python-
apt
Public bug reported:
When I launch applications with flatpak, "journalctl -f" shows the
following:
Jan 11 22:44:13 localhost systemd[1244]: flatpak-org.kde.krita-8134.scope:
Failed to add PIDs to scope's control group: Permission denied
Jan 11 22:44:13 localhost systemd[1244]: Failed to start
f
I tested it again with the regular Gnome-based Ubuntu desktop, and it
exhibits the same bug, so i changed the title accordingly. It seems
there is no connection to the flatpak problem.
** Summary changed:
- Kubuntu: Failed to add PIDs to scope's control group
+ Failed to add PIDs to scope's contr
*** This bug is a duplicate of bug 858122 ***
https://bugs.launchpad.net/bugs/858122
I have this too. ProFtp throws this error after each disconnect of a ftp
user:
roftpd: pam_systemd(proftpd:session): Failed to connect to system bus:
Failed to connect to socket /var/run/dbus/system_bus_socke
Same here with T470p
(uname -a: "Linux pl 4.10.0-42-generic #46~16.04.1-Ubuntu SMP Mon Dec 4
15:57:59 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux")
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bu
101 - 200 of 694 matches
Mail list logo
