*** This bug is a duplicate of bug 2013216 ***
https://bugs.launchpad.net/bugs/2013216
If you toggle maximised state with Super+Up or move left or right with
Super+Left or Super+Right the window gets focused and dragging works
again until you click inside a window again.
--
You received
*** This bug is a duplicate of bug 2013216 ***
https://bugs.launchpad.net/bugs/2013216
I had been using 23.04 for over a month since the beta. This only
started happening on my PC today. What happened? This is incredibly
annoying :/
--
You received this bug notification because you are a
It happens with mainline kernl builds and stock ubuntu kernels regrdless
of stable branches that those kernels come from.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
Public bug reported:
When kernels are installed, or when update-initramfs -u is run on a
kernel, it causes gnome-shell to freeze for a few seconds if the machine
is booted with that kernel or a newly installed kernel. During the
freezes, the mouse pointer is still movable but the rest of the
This is simple to fix, by changiong control file and rebuilding the
packages. What is holding canonical from releasing an unbroken version?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to curl in Ubuntu.
Can't canonical turn libcurl3 into a transitional package for libcurl4?
When I did so manually I got stuff to work fine. Most 3rd party binaries
use dot target libcurl3 as there was no libcurl4 package when in fact
they'd work fine against libcurl4 since the ABI did nto change between
curl 3 and
This is causing havoc! People installing .NET Core which depends on
libcurl3 cannot install cmake that is depending on libcurl4. The
nomenclature of these packages implies that they should be installable
side by side.
--
You received this bug notification because you are a member of Ubuntu
Touch
@cl-netbox : Did the update fix your variant of the issue?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1633824
Title:
nautilus ignores trash on external drives
Status
After updating, then logging out then back in; I confirm that this fixes
the issue for USB drives making their trash folder be treated like that
of internal drives.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a
Update-Manager just offered the update to me (I use proposed). I will
test and report back.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1633824
Title:
nautilus ignores
Public bug reported:
apport showed up
ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: libasn1-8-heimdal:amd64 1.7~git20160703+dfsg-1
ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21
Uname: Linux 4.4.0-43-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion:
Public bug reported:
apport showed up
ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: libwind0-heimdal:amd64 1.7~git20160703+dfsg-1
ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21
Uname: Linux 4.4.0-43-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion:
*** This bug is a duplicate of bug 1633355 ***
https://bugs.launchpad.net/bugs/1633355
Public bug reported:
apport showed up
ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: libheimbase1-heimdal:amd64 1.7~git20160703+dfsg-1
ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21
I fixed it! For some reason, an update changed a gsetting in the system
"org.gnome.desktop.lockdown disable-lock-screen true". Using dconf-
editor to flip the flag back to default fixes the issue.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
As a side note. I ran apport-collect via ssh as I was not at home.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1618537
Title:
Apparmor update breaks Ctrl-ALt-L
Reverting the nvidia update does not fix it.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1618537
Title:
Apparmor update breaks Ctrl-ALt-L
Status in apparmor package
Reverting the nvidia update does not fix it.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1618537
Title:
Apparmor update breaks Ctrl-ALt-L
Status in apparmor package
I will revert the nvidia update and check whether it fixes the issue.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1618537
Title:
Apparmor update breaks Ctrl-ALt-L
I need the driver for my gpu to work correctly. I updated my driver to
the latest stable one that was released last week. Before that update
all was ok.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1618537/+attachment/4731303/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1618537/+attachment/4731304/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1618537/+attachment/4731301/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
apport information
** Attachment added: "XorgLogOld.txt"
https://bugs.launchpad.net/bugs/1618537/+attachment/4731311/+files/XorgLogOld.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1618537/+attachment/4731307/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
apport information
** Attachment added: "nvidia-installer.log.txt"
https://bugs.launchpad.net/bugs/1618537/+attachment/4731313/+files/nvidia-installer.log.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in
apport information
** Attachment added: "xdpyinfo.txt"
https://bugs.launchpad.net/bugs/1618537/+attachment/4731316/+files/xdpyinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
apport information
** Attachment added: "Xrandr.txt"
https://bugs.launchpad.net/bugs/1618537/+attachment/4731312/+files/Xrandr.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
apport information
** Attachment added: "upstart.unity7.log.txt"
https://bugs.launchpad.net/bugs/1618537/+attachment/4731315/+files/upstart.unity7.log.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1618537/+attachment/4731294/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
apport information
** Attachment added: "GsettingsChanges.txt"
https://bugs.launchpad.net/bugs/1618537/+attachment/4731298/+files/GsettingsChanges.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1618537/+attachment/4731295/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
apport information
** Attachment added: "DkmsStatus.txt"
https://bugs.launchpad.net/bugs/1618537/+attachment/4731296/+files/DkmsStatus.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
apport information
** Attachment added: "MonitorsUser.xml.txt"
https://bugs.launchpad.net/bugs/1618537/+attachment/4731302/+files/MonitorsUser.xml.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
apport information
** Attachment added: "XorgConf.txt"
https://bugs.launchpad.net/bugs/1618537/+attachment/4731309/+files/XorgConf.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1618537/+attachment/4731305/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1618537/+attachment/4731306/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
apport information
** Attachment added: "XorgLog.txt"
https://bugs.launchpad.net/bugs/1618537/+attachment/4731310/+files/XorgLog.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
apport information
** Attachment added: "UnitySupportTest.txt"
https://bugs.launchpad.net/bugs/1618537/+attachment/4731308/+files/UnitySupportTest.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
apport information
** Attachment added: "upstart.unity-panel-service.log.txt"
https://bugs.launchpad.net/bugs/1618537/+attachment/4731314/+files/upstart.unity-panel-service.log.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
apport information
** Attachment added: "BootLog.txt"
https://bugs.launchpad.net/bugs/1618537/+attachment/4731293/+files/BootLog.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1618537/+attachment/4731300/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1618537/+attachment/4731299/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
apport information
** Attachment added: "DpkgLog.txt"
https://bugs.launchpad.net/bugs/1618537/+attachment/4731297/+files/DpkgLog.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
apport information
** Tags added: apport-collected possible-manual-nvidia-install third-
party-packages ubuntu xenial
** Description changed:
- After updating apparmor in 16.04 LTS, Ctrl-Alt-L no longer switches to
- the lock screen. Switching profiles does work however. When using Ctrl-
-
The Brightness & Lock settings seem immutable apart from the auto lock
timeout setting.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1618537
Title:
Apparmor update
There was also a recent p11-kit update. Could it be the cause?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1618537
Title:
Apparmor update breaks Ctrl-ALt-L
Status in
There was also a recent p11-kit update. Could it be the cause?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1618537
Title:
Apparmor update breaks Ctrl-ALt-L
Status in
I do not have such messages. This happened after a small batch of
updates that included a set of apparmor packages.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1618537
>From the apt log:
Start-Date: 2016-08-30 18:01:51
Commandline: aptdaemon role='role-commit-packages' sender=':1.154'
Upgrade: python3-libapparmor:amd64 (2.10.95-0ubuntu2.2, 2.10.95-0ubuntu2.3),
libapparmor1:amd64 (2.10.95-0ubuntu2.2, 2.10.95-0ubuntu2.3),
apparmor-easyprof:amd64
There are days when this happens many times and days where it does not
happen at all. I may switch to gnome shell until this gets fixed.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
compiz crash log after two auto logouts
** Attachment added: _usr_bin_compiz.1000.crash
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1443791/+attachment/4383065/+files/_usr_bin_compiz.1000.crash
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
hud crash on 17th april
** Attachment added: _usr_lib_i386-linux-gnu_hud_hud-service.1000.crash
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1443791/+attachment/4378095/+files/_usr_lib_i386-linux-gnu_hud_hud-service.1000.crash
--
You received this bug notification because you are a
In onc case, I had a unity panel service crash, in another a crush in
the hud and in compiz. Will upload crash files shortly.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
compiz crash on 17th april
** Attachment added: _usr_bin_compiz.1000.crash
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1443791/+attachment/4378105/+files/_usr_bin_compiz.1000.crash
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
unity panel service on 12th april
** Attachment added: _usr_lib_unity_unity-panel-service.1000.crash
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1443791/+attachment/4378106/+files/_usr_lib_unity_unity-panel-service.1000.crash
--
You received this bug notification because you are a
second part of unity log for april 17th (this means there were two unity
startups the second one(uploaded before) being the one after the crash)
** Attachment added: unity7.log.1.gz
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1443791/+attachment/4378108/+files/unity7.log.1.gz
--
unity panel service log part 2
** Attachment added: unity-panel-service.log.1.gz
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1443791/+attachment/4378110/+files/unity-panel-service.log.1.gz
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
part one of unity log for april 17th
** Attachment added: unity7.log
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1443791/+attachment/4378107/+files/unity7.log
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
unity panel service log part 1
** Attachment added: unity-panel-service.log
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1443791/+attachment/4378109/+files/unity-panel-service.log
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
lockscreen log
** Attachment added: unity-panel-service-lockscreen.log
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1443791/+attachment/4378111/+files/unity-panel-service-lockscreen.log
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Ok I will attach the specified files, the next times this occurs.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1443791
Title:
the system sometimes logs out rather than
Public bug reported:
I am using Ubuntu 15.04 and booting with systemd. In most cases locking
the screen works as expected but in certain cases the machine logs out
instead. Can this be fixed?
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug
For me it happened when booting with systemd. I got 100% use of one of
the cores by cupsd on boot. Turning the printer on seems to fix it.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
I am not sure about all of them. They included Jenkins, tomcat and a
bunch of obsolete packages removed by the upgrade
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
Strangely, after purging teh configs of my removed packages (that still
had upstart jobs on my machine) I did nto have to wait 2 mins for
network while my machine booted this morning. I am hoping that this
fixed state keeps repeating.
--
You received this bug notification because you are a
** Attachment added: mountall.log
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1379021/+attachment/4230588/+files/mountall.log
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
Thanks. I will attach the logs as requested.
--
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/1379021
Title:
after utopic upgrade: boot delays for 2 minutes
Status in
Also, I used to have a wifi dongle attached to teh machine which is no
longer ther. I have changed /etc/udev/rules.d/70-persistent-net.rules to
no longer include it (problem still persists)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Where do I add --debug? The Linux command line?
--
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/1379021
Title:
after utopic upgrade: boot delays for 2 minutes
Status in
apport information
** Attachment added: ProcEnviron.txt
https://bugs.launchpad.net/bugs/1379021/+attachment/4229468/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
apport information
** Tags added: apport-collected utopic
** Description changed:
- After upgrading to utopic, my system waits 2 minutes for network at
- boot, the boots ok. This has happened in previous releases as well for
- other people and is an annoying issue which will alarm many people
-
** Attachment added: /etc/fstab
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1379021/+attachment/4229472/+files/fstab
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
apport information
** Attachment added: UpstartRunningSystemJobs.txt
https://bugs.launchpad.net/bugs/1379021/+attachment/4229470/+files/UpstartRunningSystemJobs.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart
apport information
** Attachment added: UpstartRunningSessionJobs.txt
https://bugs.launchpad.net/bugs/1379021/+attachment/4229469/+files/UpstartRunningSessionJobs.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
apport information
** Attachment added: Dependencies.txt
https://bugs.launchpad.net/bugs/1379021/+attachment/4229467/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
apport information
** Attachment added: BootLog.txt
https://bugs.launchpad.net/bugs/1379021/+attachment/4229466/+files/BootLog.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
** Attachment added: /etc/network/interfaces
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1379021/+attachment/4229471/+files/interfaces
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
mountall.log (without --debug for now):
fsck from util-linux 2.25.1
/dev/sda2 has been mounted 27 times without being checked, check forced.
/dev/sda2: 4127369/60424192 files (0.3% non-contiguous), 76260275/241690368
blocks
fsck from util-linux 2.25.1
/dev/sda2: clean, 4127074/60424192 files,
This issue is manifesting itself again in 14.10
--
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/950662
Title:
Waiting for network message on bootup when all network
Public bug reported:
After upgrading to utopic, my system waits 2 minutes for network at
boot, the boots ok. This has happened in previous releases as well and
is an annoying issue which will alarm many people especially teh non-
techinical users. Also, many fixes described in older bug reports
Public bug reported:
After upgrading to utopic (around the time of when the final beta was
out), network manager caesed to auto start on boot. I can however start
it manually using sudo service network-manager start. When this
happended iI also noticed the automatic addition of 2 mins waiting
Public bug reported:
Currently the failsafe boot service is only shipped as an upstart job.
Since in utopic there is an ongoing transition to systemd there is a
race between upstart and systemd when it comes to networking. Network
manager may be getting started by systemd (package has a systemd
82 matches
Mail list logo
