By the way, I know that we could get this by just using DKMS for our
modules (and we could still do that if we absolutely had to), but we
prefer not to. The reason for this is that not all distributions that
we target support DKMS, so we still need to provide our home-grown DKMS
replacement. We
** Patch added: "First suggested patch"
https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1829029/+attachment/5263673/+files/update-secureboot-policy.diff
** Description changed:
- Already discussed by e-mail/IRC with Matthieu. We (the VirtualBox team)
+ Already discussed by
Public bug reported:
Already discussed by e-mail/IRC with Mathieu. We (the VirtualBox team)
would like to call update-secureboot-policy to enroll a signing key when
we install our host kernel modules on Ubuntu/Debian systems. However,
currently the tool exits if no DKMS modules are found. This
Seemed to work when I tested it yesterday (I do not always have access
to the test set-up). So assuming fixed. Thank you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1803319
Title:
GNOME Shell
Sounds reasonable. Thanks for letting me know.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1803319
Title:
GNOME Shell task bar menus not updated with external monitor primary
and laptop screen
Please let me know when there Ubuntu packages I can test. I have
upgraded to 19.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1803319
Title:
GNOME Shell task bar menus not updated with
I started bisecting, but a colleague happened to find a work-around
which fixed the problem, so I stopped. You might update your bisection
page to mention that one should do bindeb-pkg builds, not deb-pkg. I
used the Ubuntu mainline git repository - is that any different from
Linus's repository?
Does anyone know of anything similar or possibly interesting kernel
commits to look at before I spend too long bisecting?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1805151
Title:
Desktop
Update: 4.19.4-041904-generic is affected, 4.20.0-042000rc1-generic is
not.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1805151
Title:
Desktop freeze running VirtualBox, Intel graphics
To
Public bug reported:
This is identical to bug 1804885, but as requested I am filing this while
running the standard Ubuntu kernel. I will copy and paste my summary below.
Updates since I created that bug:
* This occurs with the mainline PPA 4.18.12-041812-generic kernel.
* The glxinfo
Created bug 1805151. Thanks for your time.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1804885
Title:
Desktop freeze running VirtualBox, Intel graphics
To manage notifications about this bug go
Public bug reported:
When I start a VirtualBox virtual machine (reproducible with the Ubuntu
18.04/VirtualBox 5.2.22 packages from virtualbox.org) with VMSVGA
emulation and 3D pass-through enabled, my system hangs. Sometimes I can
recover if I get to a VT fast enough to kill the process. Also,
Public bug reported:
My set-up: a laptop with an internal screen open and scaled to 150% and
an external monitor at 100% set to act as the primary screen. When I
open the menus in the GNOME Shell task bar (calendar or settings/log-
out/etc menu) they are displayed but not updated when I mouse
Note: works as expected in 18.10. As no one else seems to be interested
I will close this.
** Changed in: gnupg2 (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
After rebooting into 18.10 this morning this seemed to work. I will
assume it is fixed, close the bug and re-open it if necessary.
** Changed in: gnome-shell (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
No desktop files installed: everything running out of the build
directory, and the only thing installed outside is the kernel modules
and a udev rule.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Quite simple: I start VirtualBox or a virtual machine straight from the
build directory (without installing) and the icon in the dock is a red,
crossed-out circle. After deliberately or due to a timeout locking the
screen and unlocking it, the correct X11 property icon is
Public bug reported:
For some time now I have noticed that Subversion fails to use the gpg
agent to store passwords in memory for the current session. Someone on
the Subversion mailing list[1] suggested that it might be because the
GPG_AGENT_INFO variable is not being set in the environment, and
Public bug reported:
I have trouble imagining I am the first person to report this, but I did
not (quickly) find a duplicate. When only one version of Qt is
installed, can qtchooser select it automatically? E.g. when I start
linguist and only have Qt5 installed, could it start Qt5 Linguist?
This has mysteriously started working again. I can't see any relevant
package updates, so I can only assume that it was some local problem.
** Changed in: subversion (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
I did a fresh installation of Ubuntu 18.04 and put Subversion on it. I
expected Subversion to use the GNOME keyring by default (i.e. without
further interaction from me) for storing passwords, but it asks me
instead whether I want to store passwords as plain text. Is this
The information I added today is rather relativised by the fact that
today I am unable to reproduce the problem with the Ubuntu 4.15 kernels
either. I will update this when (if?) it happens again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1754601/+attachment/5088051/+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: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1754601/+attachment/5088060/+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/1754601
Title:
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1754601/+attachment/5088047/+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/1754601
Title:
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1754601/+attachment/5088059/+files/RfKill.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1754601
Title:
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1754601/+attachment/5088049/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1754601/+attachment/5088050/+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/1754601
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1754601/+attachment/5088053/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1754601
Title:
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1754601/+attachment/5088057/+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/1754601
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1754601/+attachment/5088054/+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: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1754601/+attachment/5088061/+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: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1754601/+attachment/5088048/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Tags added: apport-collected
** Description changed:
Some time after upgrading to Bionic, I have found that openconnect has
some trouble keeping a VPN connection open to our company VPN. Since
openconnect in Bionic seems to be based on the same upstream release as
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1754601/+attachment/5088056/+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: "Lspci.txt"
https://bugs.launchpad.net/bugs/1754601/+attachment/5088052/+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/1754601
Title:
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1754601/+attachment/5088058/+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/1754601
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1754601/+attachment/5088055/+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/1754601
No problems seen so far with 4.15.7-041507-generic either, after 25
minutes connected to the VPN. Sounds like it might be a problem in the
Ubuntu changes to 4.15 after all.
** Also affects: linux-meta (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification
The Cisco tool has trouble with both kernels. openconnect has so far
not had problems with 4.16rc6 from the mainline PPA. So it is only
Bionic's 4.15 so far. Not tested with mainline PPA 4.15, but I can if
that makes sense. I am guessing it is a heisenbug, but I might be
wrong.
I posted to
I tried it for a bit with the old Artful kernel without issues. As soon
as I booted back into the Bionic 4.15 I was unable to connect to the VPN
again. It might be worth mentioning that the Cisco VPN tool also failed
to connect. I did not try that one with 4.13.
--
You received this bug
Public bug reported:
Some time after upgrading to Bionic, I have found that openconnect has
some trouble keeping a VPN connection open to our company VPN. Since
openconnect in Bionic seems to be based on the same upstream release as
in Artful I assume that the problem is more likely to be in the
Even though 3.28 is due out after the Bionic feature freeze? What about
X.Org 1.20, which is due out a few days later?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1722725
Title:
GNOME Shell
Do you expect 3.26.3 to end up in Bionic? If not, would it be possible
to back-port the fix?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1722725
Title:
GNOME Shell disabling wrong screen when
The patches are attached to gnome-bugs #788915.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1722725
Title:
GNOME Shell disabling wrong screen when docking laptop
To manage notifications about
Would it be possible to apply the upstream patches to the version in
Bionic? I am happy to install the updated packages before they hit the
repositories.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I am currently running version 1.8.4-0ubuntu0.17.10.1 of both packages
and have not seen this problem for a while. I have rebooted several
times since installing the packages.
Off-topic, but since yesterday (can't remember it happening earlier) I
have started seeing mouse button freezes after
For those people having host freezes, please try to reproduce them using
packages from virtualbox.org and open a bug report there if appropriate.
It would be appreciated if you link to any appropriate Launchpad bugs,
but still provide all information on the virtualbox.org bug, including a
log file
Ah, it is the old problem with lightdm not waiting for the udev
notification that the driver is loaded.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1443853
Title:
Ubuntu boot in Oracle VirtualBox
Actually Lubuntu probably doesn't support Wayland at all.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1443853
Title:
Ubuntu boot in Oracle VirtualBox ends up with a corrupted display
To manage
I would just point out that the problem with Lubuntu live which was
reported and which I reproduced would force a fall-back from Wayland to
X.Org.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1443853
This issue should be fixed in versions of Ubuntu which provide the
VirtualBox graphics driver. However the person who re-opened the bug
discovered another issue: at least the Lubuntu live ISO seems to load
the VirtualBox driver rather late in the boot process, which can result
in X.Org loading
I must admit that I have not seen this freeze for a while (unless I just
missed it among all the swap-to-death freezes I have had recently), but
I installed the packages. I did not enable proposed, I just manually
installed libinput-bin and libinput10, versions 1.8.4. I probably can't
give any
At least in my case, I think that the sensible approach is to make
wayland-server treat requests for deleted objects non-fatal, as
suggested by Pekka Paalanan in the blog post linked to above.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Just for the sake of adding a comment too... I am getting this in the following
situation. I hope the description is correct.
1) I change the display set-up on my laptop slightly too fast, e.g. close the
lid, re-open, re-close (I did that quite a bit recently trying to work out bug
patterns).
Or a third hypothesis: systemd-logind triggers a suspend on lid close if
there is no external monitor plugged in. Perhaps it looks for a while
too long like there is no monitor, so that systemd-logind suspends the
system and the GNOME Shell wayland output object disappears, causing the
xwayland
Thinking of it I might be confusing cause and effect here: the
unexpected suspend might be caused somehow by the xwayland and gnome-
shell crash.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1724259
Not succeeded in reproducing this again after rebuilding GNOME Shell
with ASAN_OPTIONS=detect_leaks=0 CFLAGS="-fsanitize=address
-fsanitize=return -fsanitize=bounds -fsanitize=object-size". I do now
manage to trigger debian bug 823216 quite reliably now, with the
difference that I can log on
>From the other bug (this is getting a bit tiring):
I was able to trigger the crash pretty easily with the old library still
in use by opening and closing the lid a few times in quick succession
and then trying to type an update to this bug. After restarting I was
not immediately able to trigger
I have rebuilt libinput10 with the patch in that freedesktop.org bug
report and will see if that helps things before trying to submit
anything to launchpad.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I installed debug symbols for libinput and had a look at the core file,
and it looks very much like this:
https://bugs.freedesktop.org/show_bug.cgi?id=103298
I am missing the top frame in that stack trace, but I am guessing that
is just chance based on when I took the trace. The description of
That won't fix the outdated packages (one of them was curl...) though,
will it? And does disabled mean that Launchpad will refuse to accept
the upload even if my system tries to send it?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I checked and it was the main thread which was using CPU. Uploading a
crash report (Apport would not submit it due to a couple of outdated
packages). Note that this is on a different system with a fresh Ubuntu
17.10 install (not upgraded; but the report should tell you all that).
** Attachment
Thank you. I assume then that my failure to get a crash report was due
to the GNOME Shell process and not to the underlying mechanism. I will
just check the GNOME Shell/Mutter/whatever source next time beforehand.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I will do that next time I see this. A question: is there a signal I
can send to the process (SEGV?) to trigger an Apport bug report in
/var/crash? And would that make things easier for you?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Here is a gdb stacktrace. I tried sending signal 3 to the process in
the hope that it would trigger an apport bug report, but it did not.
** Attachment added: "gdb.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1724259/+attachment/4991557/+files/gdb.txt
--
You received
I have definitely observed bug 1716160 as well, even after correcting
the GNOME settings (though it happens less often then). However this
does not match either of the two. I still do not have a good feeling
for exactly when it happens, so if you do not mind I will just update
the bug next time
To my way of thinking, an exception is for something the programmer did
not foresee. Since this is now a known failure mode of Apport, I would
expect - in an ideal world in which there was enough time to work on all
known bugs - a clean exit with a clear error message.
--
You received this bug
Public bug reported:
I have an 11K crash report in /var/crash, which Apport refuses to
process due to a lack of "free memory to automatically analyze the
problem and send a report to the developers". So I am attaching it here
in case it is of interest. At least the question of why Apport has so
** Attachment added: "_lib_systemd_systemd-udevd.0.crash"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1726020/+attachment/4985136/+files/_lib_systemd_systemd-udevd.0.crash
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Are you talking about the guest screen or the host screen flashing? And
are you sure that X11 is running after installing those packages? In a
terminal in the guest run "ps -Af | grep X" and see if Xwayland is in
the list.
--
You received this bug notification because you are a member of
** Summary changed:
- gnome-shell assert failure: gnome-shell: libinput.c:2157:
libinput_device_destroy: list_empty(>event_listeners)
+ gnome-shell assert failure: gnome-shell: libinput.c:2157: assertion failed:
libinput_device_destroy: list_empty(>event_listeners)
--
You received this bug
Looking at the journald error log, the problem happened after Okt 17
15:27:08. I hoped that apport would take a stack trace of the gnome-
shell process, but I will probably have to do that myself when I get the
chance. Can you retrace a stack trace if the debug packages are not
installed?
--
*** This bug is a duplicate of bug 1724259 ***
https://bugs.launchpad.net/bugs/1724259
Reported this again using apport as bug 1724259.
** This bug has been marked a duplicate of bug 1724259
System freeze after docking and display configuration change
--
You received this bug
Public bug reported:
I have been having regular system freezes after switching from using my
laptop stand-alone to waking it up on a docking station with an external
monitor. I have seen this using two identical docking station plus
monitor combinations. I am still trying to find a pattern. I
Just got this again with 4.13.0-15-generic after suspending and resuming
the laptop. No docking station or screen reconfiguration.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1723075
Title:
Public bug reported:
I have been having regular system freezes after switching from using my
laptop stand-alone to waking it up on a docking station with an external
monitor. I have seen this using two identical docking station plus
monitor combinations. I am still trying to find a pattern. I
Public bug reported:
I use GNOME Terminal frequently. I tend (at least since I upgraded) to
start it from GNOME Shell's dash, using the "all applications" category.
For some reason it never makes it to the frequently used list. If it is
of interest:
$ grep terminal
Public bug reported:
I often switch between working with a docking station, closed laptop and
an external monitor, and an open laptop without docking station or
monitor. I noticed since updating to 17.10 that GNOME Shell would not
switch correctly from the setup where the laptop was being used
Public bug reported:
I hope that this is the right place for this. What I am seeing is that
every time I switch networks with my laptop entries get added to the
resolv.conf search list but never deleted. For whatever reason, once I
have left our company network I am unable to access resources
Update: I see that there are files in /var/crash, but they are all from
October 5. I will try deleting the GNOME Shell one and see if a new one
is created if another crash happens.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I saw something similar again today. Hard to say how similar. For some
reason Apport does not seem to be doing the automatic reporting, though
it looked like it was set up at a quick glance. I will try catching it
myself.
--
You received this bug notification because you are a member of
I overcame my laziness and restarted everything. I was just able to
reconfigure monitors without a crash, so assume this is fixed. I can
always re-open if really necessary. Thanks.
** Changed in: mutter (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification
Gianfranco suggested off-Launchpad that I test the most recent version
of libmutter (3.26.1), as it looks from the source as though this issue
is fixed there. I will report back in a few days (I generally suspend
and resume without restarting my session, so it will be a while until I
start using
Quick fix below. For reasons of time I have done no testing beyond that
GNOME Shell no longer crashes with the patch below. I have not tested
the effect on scaling settings.
** Patch added: "mutter.patch"
Second try with debug symbols for glib2.0 and libmutter.
Thread 1 "gnome-shell" received signal SIGSEGV, Segmentation fault.
meta_monitor_mode_get_resolution (monitor_mode=monitor_mode@entry=0x0,
width=width@entry=0x7fff256d5ad8, height=height@entry=0x7fff256d5adc)
at
Public bug reported:
When I change the monitor configuration on my newly updated Artful
system I get a desktop crash. A quick reproduction with gdb attached to
gnome-shell gave the following back-trace, unfortunately with symbols
for gnome-shell but not for libmutter (I am still a bit of a
I was also experiencing this issue with the official 4.10.0-21-generic
kernel; I ran the ~lp1674838 kernel for several days, and have been
running the -22-generic test kernel for a couple without problems.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
If upstream means VirtualBox upstream, I wonder whether this is still an
issue with VirtualBox 5.1. We re-did the capturing code for that
version when we switched to Qt 5.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
When starting a VirtualBox virtual machine using VMSVGA emulation on
Ubuntu 17.04 I get a crash. I tracked this down to the Intel code in
libdrm and Chris Wilson committed the fix to git as 19c4cfc5. I
verified that the crash occurs with libdrm build from git before but not
Gianfranco, now I am interested - could you point me to the change you
mean?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1443853
Title:
Ubuntu 14.10 ISO live boot in Oracle VirtualBox ends up
Public bug reported:
Reporting this against network manager for want of better information.
Sorry for the imprecise report - I will be glad to observe and update.
Since upgrading to 16.10 I have had problems with my USB "ethernet"
network connection provided by a tethered Android 2.3 device.
The problem is not caused by any changes in the Linux OHCI or USB code
(and obviously the VirtualBox USB emulation did not change either). It's
almost certainly triggered by the timer wheel rework which went into the
4.8 kernel.
There is a watchdog routine in the OHCI driver which is meant to be
Oh sorry, I see that I ran ubuntu-bug on the (Yakkety) host system, so
the information in the bug is obviously incorrect.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1633409
Title:
dpkg hang
This is a Xenial virtual system. Can I do the test on that?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1633409
Title:
dpkg hang while installing mainline kernel packages
To manage
Public bug reported:
Before I start: this issue does not inconvenience me very much. I am
mainly submitting it because it provides a good test case to investigate
dpkg hangs, which it seems do occur from time to time. If it is not of
interest please feel free to close again, or to let the bug
Sorry for the noise. After fixing my change the local menus are gone.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1604009
Title:
Empty menus in global app-menu in VirtualBox second window
To
User error indeed - I did #if 0 instead of #if 1. Rebuilding now, but
because of my lack of experience with debuild I am stuck in a full build
again.
By the way, lots of test cases fail after the change. I disabled them
in debian/rules locally.
--
You received this bug notification because
I rebuilt Qt5 with that change but do not see any difference. Might be
user error of course. I downloaded with apt-get source, made the
change, rebuilt with debuild binary and (for simplicity) installed all
resulting .deb files with dpkg -i.
--
You received this bug notification because you
Not sure if you want to include the double menu issue here or if you
prefer to treat the bug as fixed. As a reminder, the double menu issue
seemed to happen with appmenu-qt because it simply hid the local menus
but did not intercept hide and show requests from the application.
--
You received
1 - 100 of 221 matches
Mail list logo
