[Bug 1966588] [NEW] Huge numbers of newlines in bash after snap install command

7 latest/stable/… canonical✓ - After doing something like snap install I get the dialog to enter password for elevated rights. At the same time my bash commandline gets a huge number of newlines from somewhere. Thought you might like to know. Regards, Jeroen Baten ProblemType

[Bug 1571533] Re: Cannot use my dual-monitor setup via docking station anymore

It's been six years. I do not have access to that hardware setup anymore, sorry. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1571533 Title: Cannot use my dual-monitor setup via docking station

[Bug 1926809] Re: WD19 dock stops working in Ubuntu 21.04

What exact version of the mainland kernel would you recommend? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926809 Title: WD19 dock stops working in Ubuntu 21.04 To manage notifications about

[Bug 1935778] Re: [SRU] Request LLVM 12.0.1 backport to focal/updates

Hi Timo, I am happy to report that https://launchpad.net/ubuntu/+source/llvm- toolchain-12/1:12.0.0-3ubuntu1~20.04.4 does indeed fix the problem. Odin's LLVM branch builds against it and passes its test suite. Enabling proposed on Focal did not show any upgrades for LLVM. I ended up downloading

[Bug 1935778] Re: [SRU] Request LLVM 12.0.1 backport to focal/updates

Thank you, Timo. I'll test it this weekend and update the bug report with my findings as outlined. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1935778 Title: [SRU] Request LLVM 12.0.1 backport

[Bug 1935778] Re: [SRU] Request LLVM 12.0.1 backport to focal/updates

I can certainly do that. Much obliged. :-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1935778 Title: [SRU] Request LLVM 12.0.1 backport to focal/updates To manage notifications about this bug

[Bug 1935778] Re: [SRU] Request LLVM 12.0.1 backport to focal/updates

Thank you for your work on this, Gianfranco. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1935778 Title: [SRU] Request LLVM 12.0.1 backport to focal/updates To manage notifications about this bug

[Bug 1935778] [NEW] Request LLVM 12.0.1 backport to focal/updates

Public bug reported: Hi, Focal Fossa currently carries LLVM 12.0.0, which has a bug in its C API that renders it unusable as a backend for some compilers. The upstream commit that fixes the bug is https://github.com/llvm/llvm- project/commit/07234c7d6bc246925710b88a1f9552f678587165 and was

[Bug 1880245] Re: Error loading extension ubuntu-shell-extension-move-clock

I've found a patch here which works: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-move- clock/+bug/1816834 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880245 Title: Error

[Bug 1880245] Re: Error loading extension ubuntu-shell-extension-move-clock

PS I have the following versions: Package: gnome-shell-extension-move-clock Version: 1.01-2 Ubuntu 20.04.2 LTS -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880245 Title: Error loading extension

[Bug 1880245] Re: Error loading extension ubuntu-shell-extension-move-clock

A bit more readable JS WARNING: [/usr/share/gnome-shell/extensions/move_cl...@jonathan.bluemosh.com/extension.js 13]: reference to undefined property "panel" JS ERROR: Extension move_cl...@jonathan.bluemosh.com: TypeError: SessionMode._modes[mode].panel is undefined

[Bug 1880245] Re: Error loading extension ubuntu-shell-extension-move-clock

This is what I've been able to find in my logs (I'm a newbie, not sure if this is all relevant). JS WARNING: [/usr/share/gnome-shell/extensions/move_cl...@jonathan.bluemosh.com/extension.js 13]: reference to undefined property "panel" JS ERROR:

[Bug 1831789] Re: Add "dis_ucode_ldr" to linux boot options for Recovery Mode

Thanks Łukasz! It might be a bit problematic for me to test this in the same situation as I already upgraded my BIOS version, so I'm not having this issue anymore. Of course I can still test it in my current setup, but that does not hang while booting because the latest microcode is already

[Bug 1888090] Re: Frequent Kernel panic in 5.4.0-40 but not 5.4.0-29 on Gemini Lake cpu and r8169r

IMHO kernel version 5.4.0-40 should be deleted with the highest prejudice. Never before have I experienced 3 kernel panics in one day and a few after that. This thing should have never left Canonical quality control for an LTS system. And I have been running Ubuntu since the first release. Jul

[Bug 1890190] [NEW] package initramfs-tools 0.136ubuntu6.2 failed to install/upgrade: subproces van pakket initramfs-tools werd script post-installation geïnstalleerd gaf de foutwaarde 1 terug

Public bug reported: don't know ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.2 ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18 Uname: Linux 4.15.0-112-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult:

[Bug 1871645] [NEW] After update stuck in lock-screen

Public bug reported: After a clean install of ubuntu 20.04 beta, I updated the system, after the update was processed the system directed me to locked-screen. I was unable to log back in, or to reboot or shutdown because the system said i was still logged in. After a REISUB it would finally

[Bug 433231] Re: xorg: directory "/usr/share/fonts/X11/cyrillic" does not exist.

sudo apt-get install xfonts-cyrillic fixed it on ubuntu 18.04 ** Changed in: xorg (Ubuntu) Status: Invalid => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/433231 Title: xorg: directory

[Bug 1868374] UdevDb.txt

apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1868374/+attachment/5339670/+files/UdevDb.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 1868374] Lsusb.txt

apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1868374/+attachment/5339662/+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/1868374 Title:

[Bug 1868374] RfKill.txt

apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1868374/+attachment/5339669/+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/1868374 Title:

[Bug 1868374] ProcEnviron.txt

apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1868374/+attachment/5339665/+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/1868374

[Bug 1868374] IwConfig.txt

apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1868374/+attachment/5339660/+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/1868374

[Bug 1868374] ProcCpuinfo.txt

apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1868374/+attachment/5339663/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868374

[Bug 1868374] ProcModules.txt

apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1868374/+attachment/5339667/+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/1868374

[Bug 1868374] ProcCpuinfoMinimal.txt

apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1868374/+attachment/5339664/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1868374] Lspci.txt

apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1868374/+attachment/5339661/+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/1868374 Title:

[Bug 1868374] PulseList.txt

apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1868374/+attachment/5339668/+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/1868374

[Bug 1868374] CurrentDmesg.txt

apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1868374/+attachment/5339659/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1868374] ProcInterrupts.txt

apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1868374/+attachment/5339666/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1868374] Re: Asus WMI hotkey driver bug: External display mode button seems "stuck" on the latest bios

ase amd64 (20190210) SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.12 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: jeroen 2488 F...

[Bug 1868374] CRDA.txt

apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1868374/+attachment/5339658/+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/1868374 Title: Asus

[Bug 1868374] [NEW] Asus WMI hotkey driver bug: External display mode button seems "stuck" on the latest bios

Public bug reported: When I upgrade my laptop (ASUSTeK COMPUTER INC. ZenBook UX450FDX_UX480FD/UX450FDX, BIOS UX450FDX.307 07/05/2019) to the latest BIOS (UX450FDX.313), the laptop keeps getting events to change the display mode (FN+F8), when having an external monitor connected this makes the

[Bug 1860277] [NEW] Failed mysql upgrade to 8.0 which is part of Ubuntu 19.10 upgrade cannot be repaired due to mysql-5.7 being unavailable after upgrade to Ubuntu 19.10

Public bug reported: Title says it all. Although mysql_upgrade was run successfully on the original 5.7 database files, the in-place upgrade ran into trouble (invalid key field), causing mysql-8.0 to be unable to complete the table upgrade and generate the DD tables. There is no way to repair

[Bug 1851833] Re: [Sager Clevo notebook model PB50_70RF, RD, RC] Unable to adjust brightness of backlight

Yes it does -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851833 Title: [Sager Clevo notebook model PB50_70RF,RD,RC] Unable to adjust brightness of backlight To manage notifications about this

[Bug 1791427] Re: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th

@thorstenr-42: Also have a nfc model so still facing the same dead touchpad issues. I've never built a custom kernel before, just loaded a kernel module for a wifi nic that didn't have drivers in the kernel. How do you go about building and running this? Also I'm wondering what would be

[Bug 1851833] [NEW] Unable to adjust brightness of backlight

Public bug reported: I am unable to adjust the brightness of the backlight of my laptop screen either by using the slider of by changing the value in /sys/class/backlight/intel_backlight/brightness directly. I have tried changing my GRUB configuration: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash

[Bug 1837038] Re: Broken and defunct libv8-3.14 urgently needs removal

It looks like the problem has been solved upstream by Debian who has removed this package from sid. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1837038 Title: Broken and defunct libv8-3.14

[Bug 1837038] Re: Broken and defunct libv8-3.14 urgently needs removal

In the latest versions of Debian/Ubuntu, postgresql-10-plv8 has already been removed and r-cran-v8 has been ported to use the working v8 provided by libnode: https://packages.ubuntu.com/eoan/r-cran-v8 So this only leaves 'uwsgi-plugin-v8'. In Debian this package has been removed from the stable

[Bug 1837038] Re: Broken and defunct libv8-3.14 urgently needs removal

Is there somebody that can take a look at this? Again libv8-3.14 crashes on start, has a lot of security issues and has been removed from Debian stable. What's worse is that libv8-3.14 is masking the working version of libv8-dev from libnode-dev. Copying from

[Bug 1837038] Re: Broken and defunct libv8-3.14 urgently needs removal

Thank you! Indeed, the Debian maintainer (Jérémy Lal) told me he is in the process of removing libv8-3.14 entirely as well, but they need to deal with the last reverse dependency (uwsgi-plugin-v8). But for them it's less of an urgent issue because they have already removed it from stable

[Bug 1837038] [NEW] Broken and defunct libv8-3.14 urgently needs removal

Public bug reported: I am the upstream author of r-cran-v8, the R bindings for libv8. The libv8-3.14 package has been superseded in Debian by libnode-dev. Both packages provide "libv8-dev" however libv8-3.14 is broken beyond repair with many security problems and crashes when compiled with

[Bug 1829620] Re: intel-microcode on ASUS makes kernel stuck during loading initramfs on bionic-updates, bionic-security

I have started the process of adding dis_ucode_ldr to grub recovery mode in Ubuntu. https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1831789 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829620

[Bug 1831789] [NEW] Add "dis_ucode_ldr" to linux boot options for Recovery Mode

Public bug reported: Due to some recent problems with a microcode update which broke booting of some laptops I suggest adding "dis_ucode_ldr" to recovery mode boot options to allow booting after a bad microcode update. See the following topics that describe the problems:  -

[Bug 1831789] Re: Add "dis_ucode_ldr" to linux boot options for Recovery Mode

Related to #1829620 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1831789 Title: Add "dis_ucode_ldr" to linux boot options for Recovery Mode To manage notifications about this bug go to:

[Bug 1830205] [NEW] There is no space between the offsets column and the first databyte

the readability a lot. Best regards, Jeroen van der Laan ** Affects: ghex (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1830205 Title

[Bug 1768565] Re: pdfsam crashes at launch on Bionic Beaver 18.04 LTS

I also can confirm that this bug is still not fixed: Exception in thread "main" java.lang.NoClassDefFoundError: javafx/scene/layout/HBox at java.base/java.lang.ClassLoader.defineClass1(Native Method) at java.base/java.lang.ClassLoader.defineClass(ClassLoader.java:1009) at

[Bug 1600299] Re: Giving up after 5 attempts. Error: g-io-error-quark: The specified location is not mounted

same issue backup was working fine 2 weeks ago, now it started giving this error Ubuntu 18.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1600299 Title: Giving up after 5 attempts. Error:

[Bug 1318030] Re: Cannot login-without-password when home folder is encrypted

** Summary changed: - Cannot login-without-password when home folder in encrypted + Cannot login-without-password when home folder is encrypted ** Description changed: - Users of which the home folder is encrypted using the CLI (unfortunately + Users of whom the home folder is encrypted using

[Bug 1581088] Re: Middle mouse (wheel-click) button stopped working after upgrade to 16.04

In Kubuntu 18.04 the middle mouse button of my Logitech M310 didn't work anymore. After I tried the workaround as described in #91 and #95 it started working again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1800792] Re: Update to 8u181-b13-1ubuntu0.18.04.1 breaks Maven builds

Viktor: Ah, OK, thanks for checking. Interesting that your builds fail in OpenJDK 11 as well as 8, but mine only in this updated OpenJDK 8. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1800792

[Bug 1800792] Re: Update to 8u181-b13-1ubuntu0.18.04.1 breaks Maven builds

I've had to disable JaCoCo, and set the of the Surefire- plugin to 0 to get the mini-project 'NiceXVI' linked above to build under this OpenJDK 8 version. So it looks like it is not just JaCoCo. OpenJDK 11 works after updating JaCoCo though. Viktor: I have the set $JAVA_HOME in order for Maven

[Bug 1800792] Re: Update to 8u181-b13-1ubuntu0.18.04.1 breaks Maven builds

So this probably not a bug for the OpenJDK 11 package, but it is for the OpenJDK 8 package. No version of JaCoCo seems to work with the version released today. Viktor: Does your build work in OpenJDK 11? -- You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 1800792] Re: Update to 8u181-b13-1ubuntu0.18.04.1 breaks Maven builds

After some more testing and frustration I've found that after updating JaCoCo to 0.8.2 the newest OpenJDK 11 build works, as does the OpenJDK 10 provided by Ubuntu. The OpenJDK 8 version now provided by Ubuntu doesn't. -- You received this bug notification because you are a member of Ubuntu

[Bug 1800792] Re: Update to 8u181-b13-1ubuntu0.18.04.1 breaks Maven builds

Triage: I think this issue can be closed, although I don't quite understand why a seemingly minor patch in JDK 8 should break tools in this way. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1800792

[Bug 1800792] Re: Update to 8u181-b13-1ubuntu0.18.04.1 breaks Maven builds

Found the root cause: the JaCoCo plugin in my builds needed updating to a more recent version. If anyone lights upon this problem; OpenJDK 8u181-b13-1ubuntu0.18.04.1 and newer break older JaCoCo releases. The newer versions of this tool do work with these and newer JDK releases up to and including

[Bug 1800792] Re: Update to 8u181-b13-1ubuntu0.18.04.1 breaks Maven builds

** Attachment added: "Output of mvn clean install" https://bugs.launchpad.net/ubuntu/+source/openjdk-8/+bug/1800792/+attachment/5207389/+files/crash.txt ** Also affects: openjdk-11 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a

[Bug 1800792] [NEW] Update to 8u181-b13-1ubuntu0.18.04.1 breaks Maven builds

Public bug reported: Today both the OpenJDK 8 and 11 packages were updated. In the case of OpenJDK 8: openjdk-8-jdk: 8u181-b13-0ubuntu0.18.04.1 → 8u181-b13-1ubuntu0.18.04.1 OpenJDK 11 (10 really): openjdk-11-jdk: 10.0.2+13-1ubuntu0.18.04.2 → 10.0.2+13-1ubuntu0.18.04.3 After this update all my

[Bug 1797875] Re: ImageMagick 8:6.8.9.9-7ubuntu5.13 quality regression

** Attachment added: "The sample PDF" https://bugs.launchpad.net/ubuntu/+source/imagemagick/+bug/1797875/+attachment/5201213/+files/demo.pdf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1797875

[Bug 1797875] [NEW] ImageMagick 8:6.8.9.9-7ubuntu5.13 quality regression

Public bug reported: I would like to report a regression in ImageMagick 8:6.8.9.9-7ubuntu5.13. This report is related to https://bugs.launchpad.net/bugs/1796563, but involves image quality instead of permissions. What happens: In the new version (= security patch) of ImageMagick, the quality of

[Bug 1794318] Re: unable to boot after installing vagrant

** Attachment added: "bios screenshots.tar.gz" https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1794318/+attachment/5193579/+files/bios%20screenshots.tar.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1794318] Re: unable to boot after installing vagrant

bios screenshots -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1794318 Title: unable to boot after installing vagrant To manage notifications about this bug go to:

[Bug 1794318] Re: unable to boot after installing vagrant

sudo dmidecode # dmidecode 3.1 Getting SMBIOS data from sysfs. SMBIOS 2.8 present. 76 structures occupying 2828 bytes. Table at 0xCBD62018. Handle 0x, DMI type 11, 5 bytes OEM Strings String 1: String 2: $BIOSE121 String 3: String 4:

[Bug 1794318] Re: unable to boot after installing vagrant

sudo mdadm --examine /dev/sd[a-z] /dev/sda: Magic : Intel Raid ISM Cfg Sig. Version : 1.2.06 Orig Family : b64dd376 Family : b64de296 Generation : 0806 Attributes : All supported UUID : fe813c51:b5e27074:8e458e63:fd55063a Checksum :

[Bug 1794318] Re: unable to boot after installing vagrant

sudo mdadm --assemble --scan returns nothing -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1794318 Title: unable to boot after installing vagrant To manage notifications about this bug go to:

[Bug 1794318] Re: unable to boot after installing vagrant

sudo mdadm --detail-platform [sudo] password for jeroen: Platform : Intel(R) Rapid Storage Technology Version : 12.9.0.2006 RAID Levels : raid0 Chunk Sizes : 4k 8k 16k 32k 64k 128k 2TB volumes : supported 2TB disks : supported Max Disks : 6 Max

[Bug 1794318] Re: unable to boot after installing vagrant

find /etc/initramfs-tools/ -ls 14417979 4 drwxr-xr-x 5 root root 4096 sep 26 08:25 /etc/initramfs-tools/ 14419131 4 -rw-r--r-- 1 root root 378 jan 5 2018 /etc/initramfs-tools/update-initramfs.conf 14419128 4 drwxr-xr-x 12 root root

[Bug 1794318] Re: unable to boot after installing vagrant

sudo cat /proc/mounts [sudo] password for jeroen: sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0 proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0 udev /dev devtmpfs rw,nosuid,relatime,size=8140992k,nr_inodes=2035248,mode=755 0 0 devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5

[Bug 1794318] Re: unable to boot after installing vagrant

after a purge remove vagrant I get raid problems. ** Attachment added: "cannot activate member md127.jpg" https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1794318/+attachment/5193074/+files/cannot%20activate%20member%20md127.jpg ** Changed in: mdadm (Ubuntu) Status: Invalid =>

[Bug 1794318] Re: unable to boot after installing vagrant

initramfs ** Attachment added: "initramfs.tar.gz" https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1794318/+attachment/5193066/+files/initramfs.tar.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1794318] Re: unable to boot after installing vagrant

After installing vagrant it did a update-initramfs, which I presume, broke booting from kernel 4.15.0-34-generic when I switched back, using the grub menu, to a previous kernel 4.15.0-29-generic I could still boot without problems -- You received this bug notification because you are a member

[Bug 1794318] Re: unable to boot after installing vagrant?

** Description changed: - My system won't boot after a kernel upgrade. When I switch back to the previous kernel version it works fine. - I've got 3 ssd's and 1 hdd. - Currently I'm using 2 ssd's for intel fake raid 1(mirror) for kubuntu 18.04 - The last ssd has windows 10 installed. +

[Bug 1794318] Re: unable to boot after installing vagrant?

I've added my logs after a failed boot (using a usb live disk). ** Attachment added: "log.tar.gz" https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1794318/+attachment/5193049/+files/log.tar.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 1794318] Re: unable to boot after installing vagrant?

** Summary changed: - unable to boot + unable to boot after installing vagrant? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1794318 Title: unable to boot after installing vagrant? To manage

[Bug 1794318] Re: kernel update breaks boot on intel fake raid 1

full* ** Summary changed: - kernel update breaks boot on intel fake raid 1 + unable to boot -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1794318 Title: unable to boot To manage notifications

[Bug 1794318] Re: kernel update breaks boot on intel fake raid 1

I reinstalled my system again and did a fool update and a reboot. It looks like something else is causing the problem. ** Description changed: My system won't boot after a kernel upgrade. When I switch back to the previous kernel version it works fine. I've got 3 ssd's and 1 hdd.

[Bug 1794318] Re: kernel update breaks boot on intel fake raid 1

View attachment for more info. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1794318 Title: kernel update breaks boot on intel fake raid 1 To manage notifications about this bug go to:

[Bug 1794318] [NEW] kernel update breaks boot on intel fake raid 1

Public bug reported: My system won't boot after a kernel upgrade. When I switch back to the previous kernel version it works fine. I've got 3 ssd's and 1 hdd. Currently I'm using 2 ssd's for intel fake raid 1(mirror) for kubuntu 18.04 The last ssd has windows 10 installed. My hdd is currently

[Bug 1766495] Re: "your libfreerdp does not support h264"

Same here, Ubuntu 18.04.1 LTS (Lubuntu), latest Remmina version. Workaround the same as above, changing color depth to True Color (32bpp) fixed it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 29894] Re: can't take screenshot when menu on panel is opened

Today I wanted to make a screenshot on Ubuntu 18.04.1 LTS with a menu open but it still fails and the issue still persists. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/29894 Title: can't

[Bug 1711087] Re: ad2p sink profile mic not available

Yes, this is a duplicate of bug #508522. IMHO I think that we should close this issue and re-open bug #508533. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1711087 Title: ad2p sink profile mic not

[Bug 1711087] Re: ad2p sink profile mic not available

*re-open #508522 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1711087 Title: ad2p sink profile mic not available To manage notifications about this bug go to:

[Bug 1792790] Re: mismatch on package

** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: New => Invalid ** Converted to question: https://answers.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+question/674023 -- You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 1792790] Re: mismatch on package

What to do next, I cannot update my desktop. ** Also affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New ** No longer affects: apport (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1792790] [NEW] mismatch on package

Public bug reported: LANG=C; sudo apt-get -f install Reading package lists... Done Building dependency tree Reading state information... Done Correcting dependencies... Done The following packages were automatically installed and are no longer required: linux-headers-4.15.0-32

[Bug 1753518] Re: package grub-efi-amd64-signed 1.93+2.02-2ubuntu8 failed to install/upgrade: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 1

Latitude E7450. Same issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1753518 Title: package grub-efi-amd64-signed 1.93+2.02-2ubuntu8 failed to install/upgrade: installed

[Bug 1791421] [NEW] Nautilus hangs when opening a password protected .7z file

Public bug reported: Very simple scenario: On a fresh Ubuntu 18.04 installation (with Unity and pzip-full installed) I try to open a password protected .7z file (created in an older Ubuntu version). Nautilus starts flickering, CPU usage rises to 80% for minutes and Nautilus is not usable for a

[Bug 1003682] Re: Borderless printing doesn't work on the Photosmart B8500 with hpcups

I don't longer have access to a photosmart printer so I can't confirm if it is still a problem or not. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1003682 Title: Borderless printing doesn't work

[Bug 1461698] Re: Cross-hair pointer leaves a trace on screen in eeschema

Instaling version 5 (see http://kicad-pcb.org/download/ubuntu/ ) fixes the problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1461698 Title: Cross-hair pointer leaves a trace on screen in

[Bug 1461698] Re: Cross-hair pointer leaves a trace on screen in eeschema

I can confirm that a fresh ubuntu install with 4.0.7+dfsg1-1ubuntu2 shows the described behaviour. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1461698 Title: Cross-hair pointer leaves a trace on

[Bug 1641290] Re: [04f3:0903] Elan Microelectronics Corp fingerprint reader not recognised

Ouch what a mistake to make! Not sure what the fingerprint reader is: jeroen@nice:~$ lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 0bda:5768 Realtek Semiconductor Corp. Bus 001 Device 004: ID 0a5c:5834 Broadcom Corp. Bus 001 Device 003: ID 04f3:2335

[Bug 1641290] Re: [04f3:0903] Elan Microelectronics Corp fingerprint reader not recognised

Hi, I have an Dell Latitude 7370 with an Elan fingerprint reader and can't get it to work jeroen@nice:~/libfprint$ lsusb | grep -i elan Bus 001 Device 003: ID 04f3:2335 Elan Microelectronics Corp. I tried your fork of libprintf, Igor, and noticed you don't support ID 04f3:2335. I added

[Bug 1776615] [NEW] mysqldump: Got error: 1016: Can't open file: 'some_file' (errno: 24 - Too many open files) when using LOCK TABLES

Public bug reported: This is a report and also the fix. Please patch this so I don't have to any more. Error: During run of automysqlbackup I get the following email: mysqldump: Got error: 1016: Can't open file: 'some_file.frm' (errno: 24 - Too many open files) when using LOCK TABLES mysqldump:

[Bug 1764194] Re: Dell Latitude 5490/5590 BIOS update 1.1.9 causes black screen at boot

can confirm after updating ubuntu Xenial and removing nomodeset from boot options, everything seems to work again :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1764194 Title: Dell Latitude

[Bug 1764194] Re: Dell Latitude 5490/5590 BIOS update 1.1.9 causes black screen at boot

What about Xenial?!! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1764194 Title: Dell Latitude 5490/5590 BIOS update 1.1.9 causes black screen at boot To manage notifications about this bug go

[Bug 1764194] Re: Dell Latitude 5490/5590 BIOS update 1.1.9 causes black screen at boot

i really don't understand why they allow anyone to update the status in launchpad, it only creates confusion, especially when you can't revert accidental changes :( maybe @joseph salisbury can reopen this -- You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 1764194] Re: Dell Latitude 5490/5590 BIOS update 1.1.9 causes black screen at boot

i'm also on the 4.13 kernel on xenial thanks for fixing the issue! it's really important for me cause i really need my external monitor to be more productive at work can't wait for the xenial kernel update to drop -- You received this bug notification because you are a member of Ubuntu Bugs,

[Bug 1764194] Re: Dell Latitude 5490/5590 BIOS update 1.1.9 causes black screen at boot

will this also be fixed in xenial? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1764194 Title: Dell Latitude 5490/5590 BIOS update 1.1.9 causes black screen at boot To manage notifications about

[Bug 1771758] Re: putty crashed with SIGSEGV in XrmQGetResource()

*** This bug is a duplicate of bug 1720905 *** https://bugs.launchpad.net/bugs/1720905 Thank you, I wasn't sure if crash in XrmQGetResource was the same as crash in XGetDefault, but just noticed that the workaround mentioned in #1720905 (starting putty with 'sudo -u MY_USER putty') works for

[Bug 1764194] Re: Dell Latitude 5490/5590 BIOS update 1.1.9 causes black screen at boot

any way to fix it for regular users (without compiling a kernel) nomodeset works, but i can't use my external display if i use it -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1764194 Title: Dell

Re: [Bug 1748450] Re: gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() from g_log() from

Same here, after I read this message, I changed my login settings to Ubuntu on Wayland and never got this error again 2018-04-14 8:38 GMT+02:00 Per-Inge : > I always get this bug when I start with an Xorg session. I started with > a Wayland session and didn't get the

  1   2   3   4   5   6   7   8   9   10   >