Bulk transfer as requested in T17796
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to modemmanager in Ubuntu.
https://bugs.launchpad.net/bugs/977761
Title:
Add support for using QMI protocol
Status in gnome-control-center:
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to base-passwd in Ubuntu.
https://bugs.launchpad.net/bugs/1986619
Title:
Fail to install base-passwd
Status in base-passwd package in Ubuntu:
Confirmed
Bug description:
/hom
This is fixed upstream with:
https://git.kernel.org/pub/scm/libs/klibc/klibc.git/commit/?id=d16525038612be94cf2573c02eac8c7f76321f62
It's about time to make a new upstream release, so I will aim to do that
and the Debian update this week.
--
You received this bug notification because you are a m
Public bug reported:
The latest release is 0.28.0 and fixes some bugs I've encountered
https://github.com/Exiv2/exiv2/releases/tag/v0.28.0
** Affects: exiv2 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch s
A couple of days ago I upgraded my 21.10 system to 22.04 and got this
"out of memory" issue (Dell XPS 15 9550 with 3840x2160 display).
The fix in comment #41 worked (changing the compression to 19), and the
sequence of commands in #44 helped. However, just noting that there are
several typos in #4
Joseph, out of interest, what model of XPS 13 do you have? I'm getting
new XPS 13 soon and wondering if it'll have the same issue (I guess it's
likely given the 4k screen).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initr
I also can’t install it on my i9 12900k system. Some people have
suggested that it might help do deactivate TPM but as I am using Windows
11 for gaming this is not an option for me unfortunately. Also on my T14
no problem with TPM! (i5 10310u)
--
You received this bug notification because you are
I can say, that I have this dialog only if I have a flatpak updates, not
apt updates.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to packagekit in Ubuntu.
https://bugs.launchpad.net/bugs/1962346
Title:
Ubuntu reboots inste
.
Thanks!
Ben
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22
Uname: Linux 5.11.0-25-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.18
Architecture
Public bug reported:
The issue is screen glitches
issue is intermittent and temporary
I think it started after a recent update
But it gives the impression of an unstable system
things flickering like a highlighted file in nautilus or in filezilla
shadows under dialog boxes flickering
the icons
Public bug reported:
Sounds like a fairly common problem according to [this
page](https://wiki.ubuntu.com/X/Troubleshooting/Freeze): my display
freezes, and while I'm still able to move the mouse around, I can't
successfully click or type at any windows. It takes about 30 seconds for
gnome-shell t
*** This bug is a duplicate of bug 1871794 ***
https://bugs.launchpad.net/bugs/1871794
Noticed that I couldn't use my headset mic on any apps in the past month, but
the above reports are describing the same behavioural issues as I am seeing soI
think I am hitting the same problem.
Using Se
Public bug reported:
System version detection falsh
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: initramfs-tools 0.136ubuntu6.2
ProcVersionSignature: Ubuntu 5.3.0-53.47~18.04.1-generic 5.3.18
Uname: Linux 5.3.0-53-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersi
+1 to bionic backport please
--
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/1691908
Title:
fstab binds appear as mounts (x-gvfs-hide is being ignored)
Status in GLib:
E
*** This bug is a duplicate of bug 1866194 ***
https://bugs.launchpad.net/bugs/1866194
After looking through the posted bug and comments I'm not sure that the
issues are related. It seems more like, in this case, GNOME is just out
of sync with pulse about what the default device is thanks to p
*** This bug is a duplicate of bug 1866194 ***
https://bugs.launchpad.net/bugs/1866194
Is it supposed to switch back on reboot though? If I select a certain
device I expect it to stay that way. It's not like I'm unplugging and
replugging my USB device. From a user's perspective this certainly
Public bug reported:
/usr/bin/ld: warning: libIlmImf-2_2.so.22, needed by
/usr/local/lib/libopencv_imgcodecs.so, not found (try using -rpath or
-rpath-link)
/usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to
`Imf_2_2::ChannelList::insert(char const*, Imf_2_2::Channel con
I notice that the output from setupcon mentions loading the font twice.
That seems to correspond to this fragment of code in setupcon:
# FONTFILES
FONTFILES=''
if [ "$FONT" ]; then
for f in $FONT; do
FONTFILES="$FONTFILES `findfile $fontdir $f`"
RES=`findfile $fontdir $f`
Public bug reported:
When I specify a large font file using the FONT variable in .console-
setup, setupcon fails to load the font, reporting "putfont: KDFONTOP:
Invalid argument". If I specify the same font by setting CODESET,
FONTFACE, and FONTSIZE, the setupcon loads it fine.
For instance, if
Steve Langasek wrote:
> The root failure is:
> objcopy -O binary usr/klibc/syscalls/typesize.o
> usr/klibc/syscalls/typesize.bin
> mkdir -p usr/include/klibc/; perl /tmp/klibc-2.0.6/usr/klibc/syscalls.pl -2
> usr/klibc/syscalls/SYSCALLS.i
> /tmp/klibc-2.0.6/usr/klibc/arch/x86_64/sysstub.ph x
(In reply to Takashi Iwai from comment #127)
> Hm, interesting, AZX_DCAPS_POSFIX_LPIB basically sets the position reporting
> based on LPIB instead of the position buffer. I thought the position buffer
> isn't available or unreliable on non-Intel chips, but it might be different
> on the recent AM
IS this fix now implemented to the latest ISO available for download?
--
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/1835809
Title:
AMD Ryzen 3000 series fails to boot
S
Public bug reported:
This is present in Ubuntu 18.04, 18.10, 19.04, and 19.10 daily build. It
was not present in Ubuntu 16.04.
I have a USB microphone which also appears to pulse as a speaker. Pulse
keeps picking it as the default audio device. I can switch audio devices
to my analog line out, wh
(In reply to Marco from comment #100)
> Yea, I'm still trying to find the energy to begin to write a parser for the
> codec commands, but this will surely take quite a lot of time.
This actually sounds like something I would be interested in working on.
However I don't really have any experience
Is there a workaround? This is currently breaking my entire audio setup
(using Ubuntu Studio, where jackd is crucial)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to jackd2 in Ubuntu.
https://bugs.launchpad.net/bugs/1832651
T
How does one upgrade to systemd-241 in ubuntu?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to jackd2 in Ubuntu.
https://bugs.launchpad.net/bugs/1832651
Title:
jackdbus fails to start: cannot allocate memory
Status in syst
Public bug reported:
The `.log/jack/jackdbus.log` shows the following after trying to
start/restart jack using "Ubuntu Studio Controls" (also tried using
`jack_control start`):
ERROR: Cannot lock down 82280346 byte memory area (Cannot allocate
memory)
This is a fresh install of Ubuntu Studio
This bug affects far more than 2 users.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python2.7 in Ubuntu.
https://bugs.launchpad.net/bugs/1792164
Title:
ImportError: /PATH/xxx.so: undefined symbol: PyFPE_jbuf
Status in
Public bug reported:
These cards are picked up as having mute/VolUp/VolDown buttons, but they
only ever report a VolDown. Windows behavior (without manually installed
drivers) appears to match OS-side volume to the display on the card,
which suggests the card tries to report its volume level as an
Public bug reported:
Similar to the Steelseries Arctis headphones, these sound "cards"
present as two output devices, one intended for voice chat and one for
everything else. As a result they also need a special profile.
But there's another complication. They also have hardware HRTF that
requires
The UX391UA fix is not in 4.20 as it was already a release candidate.
To get sound working on this model you'll need to download the 4.20
source, apply the patch to sound/pci/hda/patch_realtek.c then compile
and install the kernel.
--
You received this bug notification because you are a member of
apport information
** Attachment added: "xdpyinfo.txt"
https://bugs.launchpad.net/bugs/1809656/+attachment/5224923/+files/xdpyinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wayland in Ubuntu.
https://bugs.launch
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1809656/+attachment/5224921/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wayland in Ubuntu.
https://bugs.launchpad.n
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1809656/+attachment/5224917/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wayland in Ubuntu.
https://bugs.
apport information
** Attachment added: "MonitorsUser.xml.txt"
https://bugs.launchpad.net/bugs/1809656/+attachment/5224916/+files/MonitorsUser.xml.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wayland in Ubuntu.
htt
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1809656/+attachment/5224919/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wayland in Ubuntu.
https:/
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1809656/+attachment/5224918/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wayland in Ubuntu.
apport information
** Attachment added: "Xrandr.txt"
https://bugs.launchpad.net/bugs/1809656/+attachment/5224922/+files/Xrandr.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wayland in Ubuntu.
https://bugs.launchpad.n
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1809656/+attachment/5224920/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wayland in Ubuntu.
https://bugs.
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1809656/+attachment/5224915/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wayland in Ubuntu.
https://bugs.launchpad.net
apport information
** Attachment added: "DpkgLog.txt"
https://bugs.launchpad.net/bugs/1809656/+attachment/5224913/+files/DpkgLog.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wayland in Ubuntu.
https://bugs.launchpa
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1809656/+attachment/5224914/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wayland in Ubuntu.
https://bugs.launchpad.net
apport information
** Tags added: apport-collected bionic ubuntu wayland-session
** Description changed:
Ubuntu 18.04 Pop!_OS flavour, AMD RX 560, AMD Ryzen 5 2400G (video
disabled), proprietary AMD drivers 18.40, Gnome Wayland session, 4k
monitor.
I tried to use ubuntu-bug, but it sa
Public bug reported:
Ubuntu 18.04 Pop!_OS flavour, AMD RX 560, AMD Ryzen 5 2400G (video
disabled), proprietary AMD drivers 18.40, Gnome Wayland session, 4k
monitor.
I tried to use ubuntu-bug, but it says, that xwayland is not officially
supported package and quit. Feel free to ask any logs or com
@sojusnik
Yes, you're right, I missed the closing bracket. The correct line to
add is:
SND_PCI_QUIRK(0x1043, 0x10a1, "ASUS UX391UA", ALC294_FIXUP_ASUS_SPK),
You won't find patch_realtek.c anywhere in /lib/modules/ because it's
already been compiled and installed. You need to download the sourc
The fixes in the 4.20-rc kernels are for other laptops, not the UX391UA.
You'll need to add:
SND_PCI_QUIRK(0x1043, 0x10a1, "ASUS UX391UA", ALC294_FIXUP_ASUS_SPK
to /sound/pci/hda/patch_realtek.c
to get sound working on this laptop.
I used the 4.19.9 kernel, applied the 3 linked patches and adde
Also works for me @vblack2006
I downloaded the current stable kernel from kernel.org (4.19.9), applied
the 3 patches that you linked to and added:
SND_PCI_QUIRK(0x1043, 0x10a1, "ASUS UX391UA", ALC294_FIXUP_ASUS_SPK
to /sound/pci/hda/patch_realtek.c
After compiling and installing, I now have sou
I got an error when building the modules from @VanVan's github due to
/sound/pci/hda_codec.h having been moved to /include/sound/hda_codec.h
Fixing this let the compile finish without error (this is on Fedora 29).
--
You received this bug notification because you are a member of Ubuntu
Touch see
I've compiled 4.20-rc6 from VanVan's github repository, and it has no
effect on my UX391UA - still no sound.
I notice the patch doesn't actually refer specifically to the UX931UA
though, only other ASUS models.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
I was able to workaround this problem by following Mauricio Grueso's suggestion
in bug #1776652:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1776652
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs
Thanks for getting back to me! I no longer have this piece of hardware
so it's ok for me to close this one for now.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/322210
Title:
This bug was fixed upstream almost a year ago. It would be nice to see
this addressed in Ubuntu 16.04 LTS, which is still on libmagic1 version
5.25.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to file in Ubuntu.
https://bugs.
Public bug reported:
After upgrading to kernal 4.15.0-36.39~16.04.1 this morning (2018-10-02)
I am no longer able to communicate with remote repos using ssh keys.
Reverting back to the previous kernal ( 4.15.0-34.37~16.04.1 ) fixes
this issue.
Git version is 2.19.0
1) Description: Ubuntu 16.04.5
Public bug reported:
Description:Ubuntu 18.04.1 LTS
Release:18.04
python2.7:
Installed: 2.7.15~rc1-1
Candidate: 2.7.15~rc1-1
-Python 2.7.15rc1 has the problem below ---
$ python
Python 2.7.15rc1 (default, Apr 15 2018, 21:51:34)
[GCC 7.3.0] on linu
*** This bug is a duplicate of bug 1768610 ***
https://bugs.launchpad.net/bugs/1768610
I had these exact same symptoms today with my nVidia GTX 960 after doing
a platform upgrade from 17.10 to 18.04.
Issue was actually dead simple to fix, the upgrade to 18.04 removed some
PPAs (including the
Hey all,
Kubuntu (which means plasma and KDE) is no exception. Running default config.
But for some time it worked. So it must have been in an update of the past few
weeks,
It's not just alt+arrow for me. Even alt+f1 through alt+f8 will switch
(to) console.
I guess this is a problem:
$ sudo d
I just modified comment 31 (https://bugs.launchpad.net/ubuntu/+source
/gnome-shell/+bug/1508146/comments/31):
$ sudo dumpkeys | grep -v -E '^(\W+)alt(\W+)keycode.*Cons' | sudo
loadkeys
Everything with alt at the beginning and Console will not switch (to)
consoles anymore.
** Also affects: kubunt
Public bug reported:
The raw_description property of apt.package.Version returns the summary
rather than the long description. This is because it accesses
self._records instead of self._translated_records, and the long
description is located only in the translated records.
Ubuntu 18.04 LTS
pytho
This bug still exists in Ubuntu 18.04
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.04 LTS
Release:18.04
Codename: bionic
$ pulseaudio --version
pulseaudio 11.1
--
You received this bug notification because you are a member of Ubun
ahhh cool that helped. I have updated to 18.04 last week and did not come
across any problems any more.
gRTZ ben
On Tue, 27 Mar 2018 at 11:20 DimanNe <1720...@bugs.launchpad.net> wrote:
> Thank you, benvantende! Reinstalling pulseaudio has helped me too
>
> --
> You
This happened to me upgrading from Artful.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
https://bugs.launchpad.net/bugs/1747138
Title:
package resolvconf 1.79ubuntu9 failed to install/upgrade: trigg
Public bug reported:
Tried upgrading from Artful to Bionic this weekend, had problems.
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: systemd 237-3ubuntu4
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
NonfreeKernelModules: nvidia_modeset
Public bug reported:
No observed failure in user space - but I got a pop-up warning, so here
we go...
ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-3
The bug still exists in Ubuntu 17.10.
The following might be useful information:
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 17.10
Release:17.10
Codename: artful
$ pulseaudio --version
pulseaudio 10.0
--
You received this bug notif
You also said to "change the bug status to Confirmed." It is my
impression that I'm not supposed to do that since I'm the original
reporter.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.la
Public bug reported:
I have an Ubuntu 17.10 box with WiFi and Ethernet devices. The ethernet
device is not connected at all. The WiFi is connected to WiFi network.
The problem is, the connection drops itself after a while. I did some
research and find out, the NM creates a new connection for the
Public bug reported:
also no PCI sound.
Description:Ubuntu 17.04
Release:17.04
Kernel 4.10.0-32-generic
reverting to kernel 4.10.0-30-generic works
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.10.0-32.36-generic
report.
> https://bugs.launchpad.net/bugs/1720519
>
> Title:
> Module "module-switch-on-connect" should be loaded once at most.
> Refusing to load.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bu
fixed myself by reinstalling pulseaudio
** Changed in: pulseaudio (Ubuntu)
Assignee: (unassigned) => ben van 't ende (benvantende)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubunt
0
Package: pulseaudio 1:10.0-2ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
Uname: Linux 4.13.0-12-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/pcmC0D0p: ben2809 F...m chro
tu 4.13.0-12.13-generic 4.13.3
Uname: Linux 4.13.0-12-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/pcmC0D0p: ben2809 F...m chrome
/dev/snd/controlC0: ben2809 F chrome
/dev/snd/timer: ben
This bug has just hosed a system I installed for my parents. An
unattended-upgrader that breaks your system if you don't attend to it IS
broken.
Having known about this problem for many years, the least you could have
done is added a warning to the installer that choosing lvm or encryption
will m
Public bug reported:
Attempted to remove kernel but errored on removal.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-91-generic (not installed)
ProcVersionSignature: Ubuntu 4.4.0-92.115-generic 4.4.76
Uname: Linux 4.4.0-92-generic x86_64
NonfreeKernelModules: zfs zu
Public bug reported:
attempted to remove old kernels and could not remove the extra packages.
Having issues with zfs, trying to find a good kernel to work with.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-93-generic 4.4.0-93.116
ProcVersionSignature: Ubuntu 4.4.0-9
Public bug reported:
1] >lsb_release -rd
Description:Ubuntu 17.04
Release:17.04
2] >apt-cache policy systemd
systemd:
Installed: 232-21ubuntu5
Candidate: 232-21ubuntu5
Version table:
*** 232-21ubuntu5 500
500 http://dca-ubuntu-repo.ipipenet.com/ubuntu zesty-updates/main
i've figured out at least part of this issue.
the system now no longer hangs at shutdown, but there are still
filesystems it complains it is unable to unmount, and the system still
hangs if it unable to unmount /home, which happens to be an nfs share
[i'm uncertain if this is of particular relevan
Public bug reported:
i'd done a new install of 17.04, and this had been working ok. this
morning, i did an update, and now the system complains about being
unable to unmount certain filesystems, as well as hanging during the
shutdown process upon displaying "[ ok ] reached target shutdown"
Aug
Public bug reported:
Release: Ubuntu 17.04
PulseAudio Version: 1:10.0-1ubuntu2
I expected the audio on my system to work without any additional action on my
part. Instead, the audio does not work despite working on Windows.
A few years ago, my onboard sound broke so I bought a pci sound card
(EN
Just a few updates which may be of use to anyone else having the same
issues...
1). As this issue persists without a truly good solution, it may be a
good idea to simply replace the wifi card with, say, an Atheros one
which works better. You can find them relatively cheaply on ebay.
2). One of th
Public bug reported:
...
ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: gconf2-common 3.2.6-3ubuntu7
ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
Uname: Linux 4.10.0-20-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
Date: Fri May 12 14:01:31 2017
ErrorMes
Issue definitely persists on 4.11/upstream. I came across an interesting
output in dmesg which may explain why bluetooth works while the WiFi
doesn't:
[17326.525545] iwlwifi :01:00.0: Could not load the [0] uCode section
[17326.525697] iwlwifi :01:00.0: Failed to start INIT ucode: -5
[1732
It took less than 10 minutes of testing for the issue to come back up
again under 4.11-rc7. Definitely NOT fixed upstream. I'll keep testing
and see if I find any other unique behaviours/error messages. Thanks
again, let me know if there's anything I can do!
** Tags added: kernel-bug-exists-upstre
** Attachment added: "Output dmesg crash on resume"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1684213/+attachment/4866130/+files/ucode-error-crash.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-mana
** Attachment added: "Output of modinfo iwlwifi"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1684213/+attachment/4866129/+files/modinfo-iwlwifi.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager i
Some additional notes after testing for a while...
The crashing behavior doesn't occur consistently in the same way.
Sometimes the Bluetooth crashes with the Wifi, while sometimes it
recovers fine and continues to work while the Wifi doesn't. In addition,
it seems that the Wifi crash breaks Networ
Public bug reported:
Hardware: Acer CB3-131 Chromebook (GNAWTY) running Ubuntu Mate natively (BIOS
enabled by SeaBIOS firmware from scripts here:https://mrchromebox.tech/). Uses
Intel 7260 wifi, rev. bb:
01:00.0 Network controller: Intel Corporation Wireless 7260 (rev bb)
Software: Ubuntu Mate
Just a quick note: having moved some affected systems back to Ubuntu,
this bug has just manifested in production on Ubuntu 16.04 LTS:
/opt/dump/bin/dump_multi: line 11: wait: pid 56652 is not a child of
this shell
My test script above no longer demonstrates it though. I'll see if I
can come up w
Public bug reported:
Ubuntu16.04.2 LTS_Xenial Xerus_-Release amd64(20170215.2}
This bug if it is one is as a result of a previous attempt to get Ubuntu to
install on this ssd(Samsung 840 EVO). The installation stalled straight after
the automated restart( the ubuntu splash screen sat there for 1
** Description changed:
The change of how cloud-init renders
/etc/network/interface.d/50-cloud-init.cfg, standard tools no longer work as
expected:
* resolvconf will nullify nameservers
* if* commands ignore secondary addresses
-
- The rendering is considered dangerous per Debian
(https:
The fact that this was reported on 2014-09-04 and *still* has not been
fixed is unbelievable.
It seems related to (or the same as)
https://bugs.launchpad.net/ubuntu/+source/zlib/+bug/1512992 , which was
opened on 2015-11-04 and has not been fixed yet either.
Only ten days ago was a fix proposed,
I'm afraid I did not, no.
On 21 February 2017 at 10:16, Ben <1434...@bugs.launchpad.net> wrote:
> I think I recently worked around this on Xubuntu (Ubuntu 16.04.2 LTS) by
> removing all xscreensaver remnants (which I believe to be conflicting with
> Light Locker). I did this,
I think I recently worked around this on Xubuntu (Ubuntu 16.04.2 LTS) by
removing all xscreensaver remnants (which I believe to be conflicting with
Light Locker). I did this, but use at your own risk:
```
sudo apt-get remove $(apt-cache search "^xscreensaver" | cut -d ' ' -f1 | tr
'\n' ' ')
```
This patch is broken:
1. $OPTIONS is used (unquoted) in 4 different places but this patch only
updates one of them
2. Quoting $OPTIONS prevents use of multiple options
Unfortunately I don't see a reasonable way to fix this while using only
POSIX shell features.
- If bzdiff is changed to use bas
Judging from the posts in this bug report, it took 2 weeks and three
days to solve this problem for the end-users (for the other releases.
Support for precise ends in 16 weeks...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Public bug reported:
Most commonly, they'll be partway on the upper monitor, but mostly on
the bottom. But sometimes, they'll be halfway off the screen on the
bottom monitor. New windows are sometimes created in slightly odd places
as well; usually, the titlebar will be on the top screen and the r
Public bug reported:
I have a USB drive with two partitions, one unencrypted and one
encrypted. The encrypted partition serves as the physical volume for a
LVM volume group.
cfdisk shows me:
Disk: /dev/sdb
Size: 74.5 GiB, 80026361856 bytes, 156301488
I'm experiencing this exact issue. 16.10 x64, not dual booted. Only
difference is mine is fill disk encrypted, so my device is dm-0.
Let me know what to attach
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to e2fsprogs in Ubun
16.10 have unity-panel-service taking up 3.5 GB of RAM. I've mainly
noticed it after resume, as Firefox randomly begins to crash/freeze
before the entire system becomes unstable.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
This bug appears to have been re-introduced in the re-write from stand-
alone `mount` to libmount, and thus is still present in Ubuntu 16.04
LTS. Reported upstream and got a fix there (https://github.com/karelzak
/util-linux/commit/3c4a3de0fcb8f21bffacfd8bdc3d6fbd683c71f5). Would
love to see this
I have the same problem on an X220T, whose screen can flip into a tablet
mode. The touchscreen works great for everything until I want to type
something. In Gnome Shell, anytime I select a text field with the
touchscreen, it assumes I want to use the on-screen keyboard (OSK) and
automatically pops
1 - 100 of 214 matches
Mail list logo