fixed with todays update chromium 124.0.6367.118
** Changed in: chromium-browser (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063049
Title:
Google
Public bug reported:
chromium snap only launches with titlebar and transparent window after
recent snap update on wayland and intel grafics.
Adding --ozone-platform=wayland fixes the issue for me. (workaround from
bug #1968610)
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package:
tried the fix from the new package manually (removing
/lib/firmware/ath11k/WCN6855/hw2.1) and after that the update worked.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1964814
Title:
*** This bug is a duplicate of bug 1964814 ***
https://bugs.launchpad.net/bugs/1964814
new package is in proposed.
if you cant wait or dont want to enable/download proposed packages rmeove
/lib/firmware/ath11k/WCN6855/hw2.1 manually and the update will work.
--
You received this bug
looks like it was fixed in shim(-signed) package.
It works now as intended again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1929324
Title:
Grub menu is not shown because of shim error message
I did file a new bug here:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1929324
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928490
Title:
"Could not create MokListRT" message on boot
To
Public bug reported:
Running 21.04 on a thinkpad x230.
There is a shim error
https://bugs.launchpad.net/ubuntu/+source/shim/+bug/1924605 "could not create
MokListXRT: Out of Resources" which displays this errormessage at bootup.
So Grub works, the menu works (you can still use the arrowkeys if
So people say they can still navigate blindly on grub menu when this
errormessage is displayed since it only blocks the menu beeing
displayed, not grub as such.
So i wonder if there is a better way of displaying this error as a
workaround.
--
You received this bug notification because you are a
The Problem is that this blocks the Grub-Menu from beeing displayed
(while some say they can use the keys to navigate blindly on the menu.
didnt test this so far myself)
So in case of some recovery beeing needed this gets a big issue.
--
You received this bug notification because you are a
@julian: i understand your point. But i dont understand why it worked
some weeks ago and with a 20.04 live usb while there are no changes to
the efi or bios.
So from a rational there must be something broken on recent 21.04 state.
it may not be grub itself but something in that whole efi setup.
As said before it worked some weeks ago and still works on a 20.04.5
live usb. So there is something broken in the 21.04 setup of the whole
grub/kernel/efi stuff.
I stumbled about the releasenotes from 21.04 now talking about some shim
issue. and i found
i grabbed the packages right from the launchpad building page and installed
them:
libnextcloudsync0_3.1.1-1ubuntu1.1_amd64.deb
nextcloud-desktop_3.1.1-1ubuntu1.1_amd64.deb
nextcloud-desktop-common_3.1.1-1ubuntu1.1_all.deb
nextcloud-desktop-l10n_3.1.1-1ubuntu1.1_all.deb
the issue in Comment 18 comes from mixing higher versioned clients, they
are not downgradeable.
"That is because the sync database of 3.2.0-rc3 and 3.1.3 are
incompatible. In general it is not supported to downgrade. To recover
from that you need to delete the sync database while the client is
I think there is something wrong with the whole
uefi/grub/mokutil/efivars/kernel setup on 21.04.
I changed the attributes with chattr -i and checked with lsattr. When running
"rm -rf ..." i dont get an error but it doesnt delete the file. Without -rf i
get the error "invalid Argument". (Running
I cant remove those variables in /sys/firmware/efi/efivars on my thinkpad x230.
I removed the -i kernel protection on the files but still get "invalid
argument".
I even tried different Setup- or User-Modes in Bios for Secureboot. That only
shrinked the dbx variable a bit but didnt solve the
What efivars did you delete because i am unsure what efivars i can
delete safely.
My by far largest efivars are:
-rw-r--r-- 1 root root 19308 Apr 20 22:49
MokListXRT-605dab50-e046-4300-abb6-3dd810dd8b23
-rw-r--r-- 1 root root 13504 Apr 20 22:49
dbx-d719b2cb-3d3a-4596-a3bc-dad00e67656f
can confirm that with libnextcloudsync0_3.1.1-1_amd64.deb and nextcloud-
desktop_3.1.1-1_amd64.deb from debian bullseye it works again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923053
Title:
Having the same issue with 21.04 with my ubuntu and windows dualboot on my
thinkpad x230.
But i am running not at zvs but "standard" ext4. So i doubt that is the issue
here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
i tried with the appimage version of the client and that works ootb with
the user configs etc.
wget
https://github.com/nextcloud/desktop/releases/download/v3.2.0/Nextcloud-3.2.0-x86_64.AppImage
chmod +x Nextcloud-3.2.0-x86_64.AppImage
./Nextcloud-3.2.0-x86_64.AppImage
So something is broken on
Public bug reported:
Running unstable 21.04 with sway on wayland and since end of march i
cant start the nextcloud client anymore.
First it looked like a qt/wayland issue and i installed qt5dxcb-plugin
and qtwayland5. But it still doesnt start and just prints "Segmentation
fault (core dumped)"
build radiotray-ng for my 20.04 development install. works as it should. had to
convert my old bookmarks.xml to the new json setup.
would recommend to change to radiotray-ng, too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
the last times the kernel panic got triggered by watching Youtube Video
in Firefox.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1810345
Title:
kernel: general protection fault: [#1] SMP PTI
i tried with 4.20.0-042000-generic and got a crash again (when running
in screensaver mode/idle). even sysreq reisub didnt work, had to
hardreset. i dont know how to trigger this crash on purpose. yesterday
it worked with the 4.20 kernel without crash.
i put the journalctl -b -1 as attachment,
Public bug reported:
using 18.10, all updates included. Desktop (gnome on wayland) is
crashing from time to time at idle, or on reactivating from screensaver
or while working(mostly while playing videos in browsers) where only
sysreq gets to reboot. Running kernel 4.18.0-13-generic #14-Ubuntu
@21:
https://lists.ubuntu.com/archives/ubuntu-announce/2018-April/000231.html
while you were demanding to be informed about every step developers and
volunteers do at the release, they did their job and made the release happen.
If you are really that interessted in the release process, i bet the
so after some reboots i need to change my last comment:
right now i need to toggle the commands plugin every time i login for
the mediakeys to work. :/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I am running 18.04 with unity and just tested some other Desktops that
are installed long time also: LXQt, Budgie, gnome (wayland and xorg).
Gnome crashed on both. After relogin to unity the keys didnt work while
"sudo showkey" shows that the buttons are working. They even get the
function in the
Public bug reported:
running 16.04 server with live-patch service enabled.
$ canonical-livepatch status
client-version: "7.23"
architecture: x86_64
cpu-model: Intel(R) Xeon(R) CPU E3-1225 v3 @ 3.20GHz
last-check: 2018-03-28T21:25:31.372467559+02:00
boot-time: 2018-03-18T08:08:39+01:00
uptime:
Public bug reported:
pytrainer doesnt start on 18.04.
output from terminal is:
> running pytrainer from egg installation
> data_path: /usr/share/pytrainer/
> gettext_path: /usr/share/locale
> site_path: /usr/lib/python2.7/site-packages
> Traceback (most recent call last):
> File "/usr/bin/pytr",
there were some gstreamer updates the last days. that seemed to have
fixed it.
** Changed in: corebird (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
there were some gstreamer updates the last days. since then radiotray is
working again.
** Changed in: radiotray (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
when clicking on embedded videos i get the error:
> Could not create gtksink. Need gst-plugins-bad >= 1.6
i do have the gstreamer bad packages installed.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: corebird 1.7.3-1
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic
Public bug reported:
after recent updates to 18.04 radiotray doesnt start anymore.
when starting in terminal this is the output:
/usr/lib/python2.7/dist-packages/radiotray/XmlDataProvider.py:23: PyGIWarning:
Gtk was imported without specifying a version first. Use
gi.require_version('Gtk',
running 18.04.
saw a massiv syslog file and running grep -i uread /var/log/syslog.1|grep -i
"Feb 25 12" |wc -l:
> 63197
i dont think we need this to make syslog extra big for no reason.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
running 18.04 this message is spamming into syslog:
> nm-applet[3607]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: network-manager 1.8.4-1ubuntu4
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
*** This bug is a duplicate of bug 1662003 ***
https://bugs.launchpad.net/bugs/1662003
this might be the issue: https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=871643
** This bug has been marked a duplicate of bug 1662003
/sbin/crda failed with exit code 249
--
You received this bug
*** This bug is a duplicate of bug 1662003 ***
https://bugs.launchpad.net/bugs/1662003
Public bug reported:
running 18.04 dev and seeing this in my syslog:
> systemd-udevd[332]: Process '/sbin/crda' failed with exit code 249.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: crda
Just saw that Dell revoked their A15 Bios Update for the Poweredge T20.
So i downgraded to Bios A14 and the /proc/cpuinfo now shows 0x22 as
microcode again. It was 0x23 on the revoked BIOS A15.
Looks like the mce errors are gone now on load.
--
You received this bug notification because you are
people still running on 15.04, which End of Life was February 2016,
really should consider to do a fresh 16.04 LTS install now and stay on
LTS versions when they dont want to upgrade every 6 months.
But dealing with those upgrade situations should still be considered
from the ubuntu side. Like
Public bug reported:
Hi, running 16.04 server on a Dell Poweredge T20. Since latest
meltdown/spectre Kernel update i get "mce: [Hardware Error]: Machine
check events logged" shown in the logs. This happens when the server is
compiling stuff scheduled per cron.
the mce-log shows entries like:
*** This bug is a duplicate of bug 1741934 ***
https://bugs.launchpad.net/bugs/1741934
4.4.0-109 fixed it for me. so this bug is resolved, thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
While trying to get the BIOS update to a USB-Pendrive i found out on my
Thinkpad x230 running 17.10 the latest kernel update make the USB not working
properly :/
It show all usb pendrives as write-protected, while with the older kernel they
do work. i will open another bug for this, when i
ok, updated the BIOS, did not change.
if i boot the linux-image-4.4.0-108-generic_4.4.0-108.131~lp1741934_amd64.deb
from #3 it hangs after:
Loading Linux 4.4.0-108-generic...
Loading initial ramdisk...
when running the recovery mode, when booting the regular mode it doesnt
show anything.
--
ok, the kernel from #3 didnt work. still the same issue, just doesnt do
anything after grub.
will try the new bios from dell now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1742323
Title:
@3 i will try your kernel builds right now. I cant take a screenshot
since there is just a blank screen.
@4 i did run ubuntu-bug on the booting kernel, which is the older one.
I just saw Dell offering a Bios/Uefi update. I will flash that after trying the
test-kernel from @3
--
You received
Public bug reported:
Using a Dell Poweredge T20 and Ubuntu 16.04 with the 4.4 Kernel.
Just got the Meltdown update to kernel linux-image-4.4.0-108-generic but this
doesnt boot at all. It just hangs after grub. There is no logs from syslog or
such. SysReq Keys dont work neither.
The last kernel
I still think this bug falls completely under point 2.1 of the SRU wiki page.
Twitter changed the character limit for a reason, and to say: "just use the old
limit" is not a solution, because it makes you now act differently on their
service than the rest of the users, who can use the new limit.
This Bug is not fixed for the actual supported packages.
Since not using the correct Character Limit is a heavy bug, i think the stable
packages should be updated/patched.
** Changed in: corebird (Ubuntu)
Status: Fix Released => Confirmed
--
You received this bug notification because
Public bug reported:
Twitter changed to a new character limit of 280 characters:
https://blog.twitter.com/official/en_us/topics/product/2017/tweetingmadeeasier.html
The Corebird dev already changed the limit for corebird:
Public bug reported:
after recent updates on 17.10 (development) lightdm fails. It only shows
a black screen and the cursor. Cant change to tty1 with ctrl+alt+f1.
started from grub with systemd.unit=multi-user.target into tty1 and
started gdm from there, so i could log on to unity (with broken
I marked the bugreports for packages affected by this on my system as
duplicates:
Bug #1710718
Bug #1710719
Bug #1710720
Bug #1710721
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1574670
Title:
*** This bug is a duplicate of bug 1574670 ***
https://bugs.launchpad.net/bugs/1574670
Hi, yeah i have no issue to mark that bugs (there are several of them
for several packages affected) as duplicates of that bug. My intention
was to document which packages are affected and need this change
*** This bug is a duplicate of bug 1574670 ***
https://bugs.launchpad.net/bugs/1574670
** This bug has been marked a duplicate of bug 1574670
ubuntu-support-status returns inaccurate information
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
*** This bug is a duplicate of bug 1574670 ***
https://bugs.launchpad.net/bugs/1574670
** This bug has been marked a duplicate of bug 1574670
ubuntu-support-status returns inaccurate information
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
*** This bug is a duplicate of bug 1574670 ***
https://bugs.launchpad.net/bugs/1574670
** This bug has been marked a duplicate of bug 1574670
ubuntu-support-status returns inaccurate information
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
Some libpcre* packages from 16.04 have the wrong support timeframe set
into the package info. Therefore they are falsely shown as unsupported
on the "ubuntu-support-status" output:
~$ apt show libpcre3-dbg
Package: libpcre3-dbg
Version: 2:8.38-3.1
Priority: optional
Public bug reported:
The libsdl* packages from 16.04 have the wrong support timeframe set
into the package info. Therefore they are falsely shown as unsupported
on the "ubuntu-support-status" output:
~$ apt show libsdl1.2-dev
Package: libsdl1.2-dev
Version: 1.2.15+dfsg1-3
Priority: optional
Public bug reported:
The python* packages from 16.04 have the wrong support timeframe set
into the package info. Therefore they are falsely shown as unsupported
on the "ubuntu-support-status" output:
~$ apt show python-dbg
Package: python-dbg
Version: 2.7.11-1
Priority: extra
Section: python
Public bug reported:
The x11proto* packages from 16.04 have the wrong support timeframe set
into the package info. Therefore they are falsely shown as unsupported
on the "ubuntu-support-status" output:
~$ apt show x11proto-fixes-dev
Package: x11proto-fixes-dev
Version: 1:5.0-2ubuntu2
Priority:
The issue seems to be, that ubuntu-support-status reads the package
information about support timeframe and some maintainers get confused or
mix or forget to set the proper timeframe for the LTS releases to 5
years (for the main repo).
On a 16.04 machine it lists python-dbg as unsupported. the
Ok, the workaround with commenting out PrivateUsers=yes from
/lib/systemd/system/fwupd.service worked here, too, on the 17.04 on the
Lenovo Thinkpad x230.
fuwpd is not crashing anymore. But i dont really know what the
consequences of this workaround are.
--
You received this bug notification
having the same issue on a Lenovo Thinkpad x230
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1663548
Title:
fwupd crashed with SIGSEGV in _int_malloc()
To manage notifications about this bug go
there are still users showing up with 15.04 ubuntu releases in use in
#ubuntu. Telling them to use the -d switch is still the wrong way.
Why was vivid and wily not added to the http://old-
releases.ubuntu.com/ubuntu/ repo? that would give the user the chance to
do the EOLupgrade like it used to
Public bug reported:
uptodate 16.10.
Tried to install thinkfan form the repos and the install fails due to some
systemd issues:
Vorbereitung zum Entpacken von .../thinkfan_0.9.2-1_amd64.deb ...
Entpacken von thinkfan (0.9.2-1) ...
Trigger für ureadahead (0.100.0-19) werden verarbeitet ...
installed the freshly build amd64 yakkety .debs from the link in #91 and
its working again now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1641380
Title:
chromium-browser:
Public bug reported:
running ubuntu 16.10, uptodate.
installed gedit-latex-plugin and enabled that in the settings menu. after that
gedit crashes on startup. only removing the gedit-latex-plugin package helps.
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: gedit 3.22.0-1ubuntu1
a user just had the "snapd always hanging on install/reinstall and
blocking apt" issue.
after some fiddeling we used the workaround from Comment#4
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1621336/comments/4
:
starting a rootshell with "sudo -i". then running "echo "bash -c
'service
Public bug reported:
A user in #ubuntu complained about no beeing able to upgrade his EOL
15.04 (cloud) server install, so i made a 15.04 server install in vbox
to test this scenario, and he is right:
Running "sudo do-release-upgrade" results in:
"An upgrade from 'vivid' to 'xenial' is not
Ok, now i just tested a "sudo do-release-upgrade -d" which seems to
work.
But this is a total desaster and must be solved differently. There are
too many bad howtos out there alread telling every user just to run the
-d upgrade which results in users ending up on devel releases when the
dont want
Public bug reported:
Updated my homserver from 14.04 to 16.04. Got a "/dev/sda1 will be
fscked on next reboot" hint in the MOTD. Did some reboots and the fsck
never happend. Tried with "sudo touch /forcefsck" but the message didnt
go away. Thought it was an error of the MOTD scripts and tried to
As already said in https://bugs.launchpad.net/ubuntu/+bug/1606850 :
i really suggest the release-team chases the bugs before the .1 release
and opens the LTS upgrade on the .1 release.
As you can see here on comment #2 people want to upgrade and the
internet is full of the wrong advice to use
Public bug reported:
The LTS upgrade path from LTS to the next LTS should be opened on the .1
pointrelease of the next LTS.
>From the view of a Supporter the situation right now is katastrophic. We
had enough trouble telling everyone that the LTS upgrade is not opened
directly on the 16.04
Removing the libvdpau-va-gl1 package fixes this crash.
Need to test what the drawbacks are on this workaround.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1568863
Title:
vlc crashes with segfault
*** This bug is a duplicate of bug 1573685 ***
https://bugs.launchpad.net/bugs/1573685
** This bug has been marked a duplicate of bug 1573685
Security fixes from 50.0.2661.75 and 50.0.2661.94
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Information type changed from Private Security to Public Security
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1579814
Title:
chromium browser needs an update to fix CVEs
To manage
*** This bug is a duplicate of bug 1568863 ***
https://bugs.launchpad.net/bugs/1568863
** This bug has been marked a duplicate of bug 1568863
vlc crashes with segfault in libvdpau_va_gl.so.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
making another dublicate of that bug and hope the data helps to fix it.
seems like this is more of a kernel issue?
uptodate 16.04, using vlc from the repo. using dvb-t usb stick. worked
before on 15.10.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: vlc 2.2.2-4
*** This bug is a duplicate of bug 1309942 ***
https://bugs.launchpad.net/bugs/1309942
It is a Won't Fix and known since ubuntu 14.04. see
https://bugs.launchpad.net/unity-tweak-tool/+bug/1309942
** This bug has been marked a duplicate of bug 1309942
Window Controls not functioning.
--
Public bug reported:
using uptodate 16.04
watching a dvb-t channels.conf with vlc (which worked in 15.10 and still
works on windows with same channels.conf and vlc) crashes after some
time ( <1min) and freezed whole system.
Only Sysreq reboot works.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
** Attachment added: "syslog from the crash"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1565483/+attachment/4621829/+files/syslog
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 1564593 ***
https://bugs.launchpad.net/bugs/1564593
Public bug reported:
still the same issue. but it crashes the whole system now on 16.04
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: vlc 2.2.2-4
ProcVersionSignature: Ubuntu 4.4.0-16.32-generic
Public bug reported:
uptodate 16.04
channels.conf and usb-dvbt-stick known to work before upgrade to 16.04.
opening channels.conf loads the first tv channel already with a wrong
screen ratio. seems like its cut of beeing resized to 4:3 while the vlc
window is like 16:9.
switching to another
I dont think this is a bug. The wording says what the issue is. The Key
used is only sha1 which is considered too weak. The ones using that old
Keys should fix their repos and make proper signing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
*** This bug is a duplicate of bug 1538300 ***
https://bugs.launchpad.net/bugs/1538300
There was just an update for the ofono package. Maybe that clears this
anyway
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Ok, with thanks to lotuspsychje who did some testing it seems the issue
is triggered with switching of the "show the menu for one window"
setting in systemsettings->appearance -> theme behaviour.
switching it one time triggers "something" that makes the windowsbuttons
go to the right side no
Using ubuntu with Unity. Theme is radiance.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1545556
Title:
ubuntu 16.04: window buttons of gedit are placed on the right side
To manage notifications
Public bug reported:
ubuntu 16.04 alpha:
gedit 3.18 now has its toolbar placed in the window titlebar. because of that
the window buttons are placed on the right again.
this is inconsistent to all other windows (i just realized it because i
moved the curser to the left upper edge to close gedit
This really needs to be adressed ASAP.
The Support Communites are flooded by angry users with blocked
Packagesystems due to a full /boot blocking new kernels to be installed.
In this time, when we have 5TB HDDs and even 500GB SSDs, i really dont know why
we still need that small /boot
*** This bug is a duplicate of bug 1357093 ***
https://bugs.launchpad.net/bugs/1357093
** This bug has been marked a duplicate of bug 1357093
Kernels not autoremoving, causing out of space error on LVM or Encrypted
install
--
You received this bug notification because you are a member
https://bugzilla.redhat.com/show_bug.cgi?id=1241930 this seems to be
ths root of this issue: wpa_suplicant since version 2.4 doesnt work with
the older software still used by most infrastructure.
** Bug watch added: Red Hat Bugzilla #1241930
https://bugzilla.redhat.com/show_bug.cgi?id=1241930
could be triggered by some Networks still using to short DH Keys or using TLS
<1.2.
wpa_supplicant 2.4 drops the connection if this is the case.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1498837
Public bug reported:
Windows on the same machine and android smartphone can connect with same
username and password without issues.
Tried several certificates (to rule out changes on certificates form the
last setting 10months ago when it worked on the same ubuntu install).
It connects to the
http://packages.ubuntu.com/de/precise/ubuntuone-control-panel-qt tells
me its only in the repos for 12.04
besides i upgraded to 15.10 recently and its still that paid apps are
not present in the software-center.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Public bug reported:
a user in the #ubuntu IRC channel complains he cant see paid apps in
15.04 softwarecenter while he said he could before the upgrade from
14.04/14.10.
testing this on my 15.04 machine i can confirm it. i cant see paid apps,
too.
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Public bug reported:
Ubuntu 15.04, uptodate
virtualbox install from the repo.
I cant start a VM and getting an error with the hint to run a command which
doesnt work:
The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there is
a permission problem with /dev/vboxdrv. Please
A User reported that behaviour and on his sudo apt-get update there
were some PPAs with errors. After removing the failing PPAs the issue
seems to be resolved.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2015-1593
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1421864
Title:
CVE-2015-1593 Linux ASLR integer overflow
To manage
i really cant think how this could be waited so long to ship a fix. this
is really not acceptable.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1257186
Title:
memory leakage messages (no talloc
i really cant think how this could be waited so long to ship a fix. this
is really not acceptable.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/1257186
Title:
memory leakage
Public bug reported:
Tried the current iso from 11.02.2015 and had the same issue like some
Monts ago:
The Desktop video output is offset downwards, like 1/3 of the screen
high. So the Panel is at ~ 2/3 height of the Screen. But the mousecursor
is not offset. So if you click on what you see, in
1 - 100 of 183 matches
Mail list logo
