Here is a patch for 24.04 (noble). It has been a long time since I've
done any *buntu dev work so I'm sure I screwed something up. If not,
great here is a patch, otherwise let me know what I screwed up or feel
free to tweak/improve it. I just finished testing this and now I can
connect to an old Op
Public bug reported:
Initial desktop startup on Antsle Nano - system crash occurred.
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: grub-efi-arm64-signed 1.187.6~20.04.1+2.06-2ubuntu14.4
ProcVersionSignature: Ubuntu 5.4.0-92.103-generic 5.4.157
Uname: Linux 5.4.0-92-generic aarch64
App
This is a high impact bug. Any idea when the upstream will be available
to install for us peasants?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2026194
Title:
When clicking on some maximized or ti
Public bug reported:
# System Details Report
---
## Report details
- **Date generated:** 2024-05-14 16:11:26
## Hardware Information:
- **Hardware Model:** ASUS TUF GAMING X570-PRO
_WI-FI_
- **Memory:**
I'm having the same xorg crash problem on Xubuntu 24.04 beta, see
#2061246 (dup'ed to here.) I can reproduce the problem with a Ubuntu
24.04 beta install, but there xorg always crashes, unlike the
Xubuntu/xfce4 flavor where the first login after booting fails but
trying again immediately will succ
I'm also experiencing the Out of Memory error on a fresh install of
Ubuntu Server 22.04 on an Intel NUC BXNUC10i5FNK1 with 8GB of memory.
After pressing any key it boots to a kernel panic stating not syncing
VFS, unable to mount root fs.
--
You received this bug notification because you are a mem
Just did a fresh install of 20.04.3 LTS, updated & installed linux-
generic-hwe-20.04 and it booted up just fine. Only difference is
/etc/default/grub on a client's appliance, this is the default/grub on
the machine that freezes:
# If you change this file, run 'update-grub' afterwards to update
#
Same thing, hardware is an Intel NUC NUC10i5FNK. OS: Ubuntu Server
20.04.3 LTS. Kiosk machine, when I select 5.13.0-28 to boot, it just
freezes at loading ramdisk. 5.11.0-46-generic works just fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Public bug reported:
notice while upgrading
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: libpython3.8:amd64 3.8.10-0ubuntu1~20.04.1
ProcVersionSignature: Ubuntu 5.11.0-41.45~20.04.1-generic 5.11.22
Uname: Linux 5.11.0-41-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.18
AptOrdering:
(A bit delayed, but just for anyone finding this...)
No, you cannot remove a FAULTED normal data device - device_removal
involves migrating all the data off the old one, which you cannot do if
it's not there.
(logs and caches are different.)
You'll need to recreate the pool.
--
You received th
Public bug reported:
If you do zfs send -D with 0.8.x userland and 2.0.x kernel, it will
actually try to produce a deduplicated send stream (whereas 2.0.x
userland stubs out that flag and prints a "this did nothing, stop trying
to use it" note).
On the system that generated it (20.04 amd64, runni
I lied, it totally happens on 20.04 (w/5.4.0-89-generic) and 21.04
(5.11.0-37-generic), I just had forgotten I hadn't used virtio-scsi on
them, just SATA.
Oh boy.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
Public bug reported:
As I often do, I tried running OpenZFS git master's ZFS Test Suite
against the new Ubuntu 21.10 release, to make sure nothing was secretly
broken.
This is on an Ubuntu 21.10 amd64 VM (running 5.13.0-20-generic) inside
VirtualBox 6.1.26 on Windows 10 x64, using virtio-scsi for
My suggestion would be to print a warning unconditionally on first
install that you should test it and not assume it will just work, and/or
to not set crashkernel=... with the default in the first place so people
have to go explicitly set it (and, implicitly, read about the fact that
one size does
I suppose I should have made it clear that just changing the amount of
memory reserved was not sufficient.
Perhaps it would be useful to print a message saying "hey, I know we set
something by default, but we don't expect that to actually work, so you
should probably test and adjust it"?
Because
** Description changed:
I tried installing kdump-tools (1.6.7-1ubuntu2.2) on my up to date 20.04
system, installed specifically to try reproducing a bug.
But when I tried, after kdump-config status reported "ready to dump" on
reboot, echo 'c' | sudo tee /proc/sysrq-trigger, it printed t
Public bug reported:
I tried installing kdump-tools (1.6.7-1ubuntu2.2) on my up to date 20.04
system, installed specifically to try reproducing a bug.
But when I tried, after kdump-config status reported "ready to dump" on
reboot, echo 'c' | sudo tee /proc/sysrq-trigger, it printed the panic to
c
Thanks. I eventually removed enough packages from the system to allow the
upgrade to work. It was a long time ago so I don't remember the details
anymore and I think I threw out my notes.
Since then, apt upgrades, including kernel upgrades, have been working
fine.
Just one more year, and we get t
Public bug reported:
As described in Debian bugs [1] and [2], alien 8.95.3 (and .1 and .2,
but those aren't being shipped by any release of Ubuntu) cannot
successfully generate any debs, ever - with neither bug patched, it will
error out on attempting to generate any deb at all due to a syntax err
This is really annoying, counter-intuitive behaviour. At the very least
the old behaviour should be restorable by a setting.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767431
Title:
restore type
*** This bug is a duplicate of bug 1903312 ***
https://bugs.launchpad.net/bugs/1903312
** This bug has been marked a duplicate of bug 1903312
Ubiquity not selecting correct timezone when connected to Internet
--
You received this bug notification because you are a member of Ubuntu
Bugs, w
Public bug reported:
When installing Kubuntu with the daily build, I am unable to select a
time zone. With nothing selected, I clicked to proceed with the install
and it appears to still proceed as expected.
I'm reporting as whilst installation appeared to work correctly for me,
there may be fri
I updated mono
```
Mono JIT compiler version 6.12.0.90 (tarball Fri Sep 4 14:02:38 UTC 2020)
Copyright (C) 2002-2014 Novell, Inc, Xamarin Inc and Contributors.
www.mono-project.com
TLS: __thread
SIGSEGV: altstack
Notifications: epoll
Architecture:
Public bug reported:
11/30/20
PROBLEM: attempted to install ubuntu 20.04 with windows 10. stops 3/4 of the
way through.
I think the problem is the partitioning of the drive, or the fact
that I am using a
gaming computer. I had ben running only UBUNTU on this computer for
I've just noticed an additional problem - do-release-upgrade did not
restore third-party repositories to /etc/apt/sources.list, so all my
third party packages have silently stopped being updated.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Thanks for checking. I have submitted the bug report. It is bug
#1902767.
On Tue, Nov 3, 2020 at 12:36 PM Brian Murray <1246...@bugs.launchpad.net>
wrote:
> Please submit a new bug using 'ubuntu-bug ubuntu-release-upgrader' as
> that will add log files which I can examine to help sort out the
> s
Public bug reported:
This error comes up both before and after removing two ppas using ppa-
purge. Note that I am using a low-latency kernel with bionic. I would
suspect this but I upgraded another system running this kernel with no
problems.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package:
I added the PPA packages back in, reinstalled the related software, and
removed them with ppa-purge. Followed that with apt update, autoremove
and a necessary reboot. After all that, I got the same "unresolvable
problem" error when I tried to do-release-upgrade.
--
You received this bug notificat
I added the PPA packages back in, reinstalled the related software, and
removed them with ppa-purge. Followed that with apt update, autoremove
and a necessary reboot. After all that, I got the same "unresolvable
problem" error when I tried to do-release-upgrade.
--
You received this bug notificat
I followed instructions and removed all ppas using add-apt-repository
--remove followed by ppa-purge. Nothing changed in the flow of do-
release-upgrade.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
I'm running Ubuntu 16.04.7 LTS 64bit and Logwatch 7.4.2.
My root user has /sbin in the path and when I run zpool I don't have to prefix
it with the path.
Still to make this logwatch section work, I had previously edited my
/usr/share/logwatch/scripts/services/zz-zfs on lines 54 and 55 to have
th
Public bug reported:
I think that it attached the crash report, but on initial installation,
it let me resize a ntfs partition to do ext4. It looks like it was
installing and then it said that I had a fatal error. I will try again
to see if I can boot from the created drive but it is trying to sen
Public bug reported:
Reproduce the error:
Open system settings, you should see "winfx settings" screen.
Double click one of the icons. it may work but if you double click one
of the icons again, you'll see an error message that says:
This application has raised an unexpected error and must abor
Same problem occurs with logwatch 7.4.2-1ubuntu1 in U 16:
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.04.6 LTS
Release:16.04
Codename: xenial
fix is the same.
regards
rich
--
You received this bug notification because you are a member of Ubuntu
** Package changed: apport (Ubuntu) => installation-report (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880682
Title:
LTS 20.04 install fails with probe failure locating drives that were
Public bug reported:
I tried to install LTS 20.04 on a machine (e5-2670 powered) which had
drives (Crucial 500GB SATA, HGST 2GB rotating) formatted for a pfSense
(FreeBSD) test. Install failed to probe for disks multiple times. dd'ing
zeros over the front part of thedrives allowed installation to
Public bug reported:
/boot/vmlinuz-5.1.15-surface-linux-surface is unsigned.
E: Your kernels are not signed with a key known to your firmware. This system
will fail to boot in a Secure Boot environment.
dpkg: error processing package grub-efi-amd64-signed (--configure):
installed grub-efi-amd64-
Public bug reported:
The log to file functionality does not appear to work in 0.9-0ubuntu2
(default on Ubuntu Focal). On 0.5-0ubuntu4 (tried on Ubuntu Xenial) the
-l flag wrote the log to the specified file. In 0.9-0 the log
always ends up written to syslog regardless of what I specify to -l.
Ex
I followed the steps above on Linux Mint, and the output of "journalctl
-b | grep i915" no longer had the "GPU HANG or Resetting rcs0 for hang
on rcs0" errors.
I also confirmed that running Zoom no longer has any lags or hangs. It
works as expected.
So confirming this fix worked!
(Sorry, I'm ne
I can also confirm that this problem continues in 5.3.0-51-generic
However, I see it very frequently (not just for 5 seconds... happening
all the time) with two different use cases.
1) When i have a headset (with a mic) plugged into the front audio port.
One of my cores also goes to 100% utilizat
Public bug reported:
wont install on any partition.
attempts to install on /dev/sda even though the install is going to /dev/sdb
for info, sdb is an ssd drive that I had 18.04 on previously.
/dev/sdb checks out as OK.
this is an install of 20.04 LTS
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Pa
It happened to me again just now. I ssh'ed to the computer and did a
reboot, but even after the ssh service had shut down, the computer was
still hung with a frozen screen saver, and I still had to do a hardware
reset in order to get it going again.
--
You received this bug notification because
*** This bug is a duplicate of bug 1869629 ***
https://bugs.launchpad.net/bugs/1869629
** This bug has been marked a duplicate of bug 1869629
please add /etc/mdns.allow to /etc/apparmor.d/abstractions/mdns
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
This problem is indeed somewhat pervasive, I also filed bug 1869632 on
cups-browsed doing the same thing, for the same reason. I suspect more
will pop up. I don't think libnss_mdns is too widely used, most people
would use libnss_mdns_minimal. I only have to use libnss_mdns because
my ISP is insan
Bug also exists in package version 1.27.3-1 (current version in focal)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1869632
Title:
AppArmor profile denied access to /etc/mdns.allow
To manage notif
Public bug reported:
Many messages in syslog
audit: type=1400 audit(1585521672.468:40): apparmor="DENIED"
operation="open" profile="/usr/sbin/cups-browsed" name="/etc/mdns.allow"
pid=1323 comm="cups-browsed" requested_mask="r" denied_mask="r" fsuid=0
ouid=0
This is caused by configuring libnss-m
As a workaround, hanging /etc/apparmor.d/local/usr.sbin.chronyd to
include
/etc/mdns.allow r,
and reloading with
sudo apparmor_parser -r /etc/apparmor.d/usr.sbin.chronyd
made it shut up.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
Public bug reported:
Many repetitions of
audit: type=1400 audit(1585517168.705:63): apparmor="DENIED"
operation="open" profile="/usr/sbin/chronyd" name="/etc/mdns.allow"
pid=1983815 comm="chronyd" requested_mask="r" denied_mask="r" fsuid=123
ouid=0
in log. I use libnss-mdns for .local name reso
Looking into this, it seems the problem is that /usr/lib/systemd/scripts
/chronyd-starter.sh expects to be able to check for the cap_sys_time
capability by grepping the output of "capsh --print" for
"^Current.*cap_sys_time". However, in Focal the output of "capsh
--print" for a root process is jus
Public bug reported:
A current discussion on orca-list indicates that some blind users are
finding Orca's use of gsettings to be problematic:
The most accessible Linux version to use with Orca?
https://mail.gnome.org/archives/orca-list/2020-March/msg00233.html
Here are some relevant snippets:
>
Noting once again that I am still having this problem. I am worried
because no one seems to be working on it or have any idea how to work
around it (other than by disconnecting the cable from my computer to the
back of my TV when I'm not playing something on the TV screen).
--
You received this
I am still occasionally experiencing this problem (or something that
looks just like it) in 2020. In my case, the freezing happens only when
the Cinnamon screen saver is active -- the date/time on the screen saver
stops advancing, and no keys or mouse clicks will revive it -- even
selectively kill
Still having this problem. I'm temporarily working around it by
disconnecting the HDMI cable from the computer to the back of the TV
when I'm not actually playing something on the larger screen, but this
is clearly not acceptable as a long-term solution.
--
You received this bug notification bec
I'm using Xorg. And the password manager is xkeepass ( and keepass2 )
On 12/9/19 11:49 AM, Jamie Strandboge wrote:
> Thank you for using Ubuntu and reporting a bug.
>
> Are you using wayland or Xorg for your desktop session? What password
> manager are you using?
>
> ** Information type changed f
I don't think Compiz is relevant here. My computer isn't running Compiz
— its display manager is GDM3 as best I can tell. (ri...@richw.org, the
original reporter of this bug)
** Package changed: compiz (Ubuntu) => gdm3 (Ubuntu)
--
You received this bug notification because you are a member of
I note this bug has been classified as affecting Compiz. However, as
best I can tell, Compiz is not running on my computer. /etc/X11
/default-display-manager on my computer contains the value
"/usr/sbin/gdm3".
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Public bug reported:
Ubuntu 19.10, gdm3 3.34.1-1ubuntu1, cinnamon 4.0.10-2, cinnamon-
screensaver 4.0.3-1, nvidia-driver 435.21-0ubuntu2.
I have a TV set connected to my computer as a second monitor (for
displaying YouTube videos, etc.).
When I turn off both my main monitor and the TV for the ni
As I wrote earlier, the EDID file I used came from edid-generator github
and it is called 1920x1080.bin . You want me to google that for you?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821533
Titl
I'm not sure this is a Linux problem. It may be that the panel is
reporting bad EDID data. I haven't investigated enough to say for sure.
In any case none of the more recent Linux releases fixed the problem in
my tests. Also no other open source OSs were able to deal with the
onboard LCD panel eith
I was able to display on an external monitor, or the internal monitor,
but not both simultaneously. I didn't spend too much time trying to
solve the problem and now the laptop is with a family member at another
location. If you work on this issue and find a solution please post it
here.
--
You re
Public bug reported:
Settings Panel -> Application Style -> Windows Decorations is Non-Usable
and has been bugged since beta. Upgrade from beta to release Kubuntu
19.04. Panel looks like this when selected:
https://i.imgur.com/jLSysQS.jpg
rich@tworobots:~$ lsb_release -rd
Description:
@aM, your solution worked for me too. I now have Crashplan working.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1790966
Title:
Electron apps segfault on glibc 2.28 (cosmic)
To manage notificatio
I also experienced "A stop job is running for Session c2 ... / 1min 30
s)". Newbies (like me) might need to know that in a fresh install of
Ubuntu 16.04, the file /etc/systemd/system.conf has (almost) all lines
commented out with a # . So, in addition to changing the number in the
line #DefaultTime
** Summary changed:
- failure to detect and use Intel 620 graphics pci id 3ea0
+ drm fails to accept edid version 2.4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821533
Title:
drm fails to accep
I was able to get the onboard LCD panel working, finally, as follows:
First I extracted the edid file from the LCD panel using get-edid and
putting that in /lib/firmware/edid/ncp.bin, and then forcing the kernel
to take that using the kernel boot option
drm.edid_firmware=edid/ncp.bin. This failed,
Below is the EDID information from the onboard panel. Why can't drm/i915
deal with it?
guest@guest-ZenBook-UX431FA:~$ sudo get-edid | parse-edid
This is read-edid version 3.0.2. Prepare for some fun.
Attempting to use i2c interface
No EDID on bus 0
No EDID on bus 1
No EDID on bus 2
No EDID o
Correction: last message should read "Why is the driver/module expecting
EDID major version *1* and getting *2*?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821533
Title:
failure to detect and us
I think the problem is that the laptop's onboard LCD panel is reporting
EDID data with version 2 and the i915 driver can only deal with version
1 at the moment. How can this be fixed?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
htt
Progress! Based on information in dmesg, pasted in at the end of this
message, I thought maybe the graphics device was found OK but the laptop
was trying to drive an external monitor instead of the onboard display.
Sure enough, when I boot without nomodeset option and with an external
HDMI monitor
Is it known whether any machines with Intel Graphics 620 with pci id
0x3ea0 have functioning graphics with any version of Ubuntu?
This is relatively new hardware, but it seems unlikely that I am the
only one in the world who has tried this combination, and if other
people with different machines w
I tried booting 4.18.0-16-generic (which i believe is the hwe kernel)
with kernel option drm.debug=0xff. When the system came up of course it
had no video but I could ssh in and grab the dmesg output, which is
attached to this message. dmesg had many drm-related debugging messages
and i915-related
Just in case my addition of i915 to initramfs was causing a problem with
drm-intel-next, I removed i915 from initramfs and repeated the test. The
result was the same, no video after a certain point in the boot process
with nomodeset using the drm-intel-next kernel as in #8.
--
You received this b
I installed kernel and modules and headers from
https://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-next/current/
and rebooted without nomodeset option. Same behavior: after the "loading
initramfs" message the screen blanks and never comes back.
--
You received this bug notification because
Based on a lead from an Arch Linux blog post, I tried adding the i915
module to the initramfs. This could possibly lead to earlier
initialization of the graphics device and it also seems consistent with
the DragonFlyBSD "probe early" patch I linked to in my initial bug
report which may have fixed t
Also: booting without nomodeset kernel option for v5.1-rc2 kernel leads
to black screen, just as before. At that point the system cannot even be
switched to text console with ctrl-alt-Fn.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks for your help.
Unfortunately, no change after installing v5.1-rc2: Still stuck in
800x600 after booting with nomodeset kernel option.
Added kernel-bug-exists-upstream and marked confirmed.
dmesg output attached.
** Attachment added: "dmesg"
https://bugs.launchpad.net/ubuntu/+source/x
** Description changed:
Booting very new laptop hardware (ASUS Zenbook UX431FA) from 18.04 usb
install (also 18.10, also 19.04 daily) leads to black screen. Adding
"nomodeset" to kernel boot parameter gives 800x600 video only and
permits installing OS to disk. Applying updates and hardware
Public bug reported:
Booting very new laptop hardware (ASUS Zenbook UX431FA) from 18.04 usb
install (also 18.10, also 19.04 daily) leads to black screen. Adding
"nomodeset" to kernel boot parameter gives 800x600 video only and
permits installing OS to disk. Applying updates and hardware enablement
wants to see it.
It would REALLY be nice if a fix trickled down soon...
thanks
rich
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1611945
Title:
/dev/disk/by-path not properly populated for (e
Update Manager came through with the update a couple of hours ago -
Fixed the blue background on HP Photosmart B210. Thanks for quick work
Guys
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1817308
Ti
Interesting. I never manually changed the configuration. If any conversion
was done, it was by the installation. There may be a bug after all.
Thanks
Rich
On Mon, Dec 3, 2018 at 4:45 AM Karl Stenerud
wrote:
> Hi Rich,
>
> Thanks for reporting this. It looks from the log
Public bug reported:
I was able to partially mitigate the bug by replacing smb.conf with the
pre-upgrade version. That allowed access to drives and printers from a
Windows 7 computer, but did not help with a file share attached from a
fully patched Windows 10 computer. The Win 10 upgrade may be a
ExecStart twice is what I meant (this is the way to replace the command
from the base definition instead of adding another command to the list,
see the systemd.unit man page for details.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
No, ExecStart twice is correct. This is the way systemd overrides
work; normally a value for a keyword adds to the list of values from
the base .service definition. I don't want that, I want to replace
it. The special ExecStart= with no value tells systemd to reset the
base value to empty, th
This is also affecting my company. We use monit on all boxes for process
management and have had to pin on a downrev version.
Do we know if the package maintainer knows that this is an issue? Can we
get some confirmation of that?
--
You received this bug notification because you are a member of
second (and subsequent) time one boots after
updating the system, and these days I never reboot unless I have
updated, since suspend works for desktops/laptops and who reboots
servers if you don't have to?
Rich
On Sat, Sep 22, 2018 at 8:54 AM Anders Hall wrote:
>
> Thanks, workaround in
** Package changed: ubuntu => php-defaults (Ubuntu)
--
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/1792938
Title:
PHP 7.2.7 contains various security issues.
To manage notifications about th
Similarly, I have set in apt.conf.d
Acquire::https::Proxy "DIRECT";
(because apt-cacher-ng can't cache https) and I get
proxy 'DIRECT' looks invalid
The regexp definitely needs to be broadened.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Public bug reported:
Cacti fails to show many graphs, and also has problems reindexing.
The error given is:
sizeof(): Parameter must be an array or an object that implements Countable in
/usr/share/cacti/site/lib/utility.php on line 541
Fix is by patch:
diff --git a/lib/utility.php b/tmp/util
** Also affects: redmine (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- ruby-rails 2:4.2.10 does not utilise PGSQL 10 sequence model
+ ruby-rails 2:4.2.10 is not compatible with PostgreSQL 10 (sequence handling
changed since 9.x)
--
You received this bug notificatio
Cleaner details found at: https://help.heroku.com/WKJ027JH/rails-error-
after-upgrading-to-postgres-10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776931
Title:
ruby-rails 2:4.2.10 does not utili
Public bug reported:
>From PostgreSQL v10, the sequence object has altered, moving attributes such
>as "increment_by" and "min_value" to the pg_sequences catalog, rather than
>holding them in the sequence itself.
The rails package on Ubuntu 18.04 does not seem to have caught up with this.
The e
STILL not fixed.
4.4.0-124-generic #148~14.04.1-Ubuntu SMP Thu May 3 07:26:53 UTC 2018 x86_64
x86_64 x86_64 GNU/Linux
GNU gdb (Ubuntu 7.7.1-0ubuntu5~14.04.3) 7.7.1
any c program compiled with -g and then
gdb -tui program
set a breakpoint
run
multiple dl-debug.c:74: No such file or directory.
w
The ppa:openafs/stable workaround restored AFS client service to my
machine (which had been lost after I switched to the HWE kernel in early
January 2018). Currently running openafs-client
1.6.22-3~ppa0~ubuntu16.04.1.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I filed a bug report with GNOME:
https://bugzilla.gnome.org/show_bug.cgi?id=792832
I added the link to:
Also affects project.
** Bug watch added: GNOME Bug Tracker #792832
https://bugzilla.gnome.org/show_bug.cgi?id=792832
** Also affects: gedit via
https://bugzilla.gnome.org/show_bug.cgi
** Description changed:
If I paste a special character - say from the Character Map - into Gedit
or medit in Ubuntu 16.04 into the middle of a line, then the space
characters directly after the special character display with a
- "compressed" character spacing/display until the behaviour is
-
** Tags added: ui
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1744946
Title:
Special characters change the width of trailing/leading space
character in Gedit (and medit)
To manage notifications
Public bug reported:
If I paste a special character - say from the Character Map - into Gedit
or medit in Ubuntu 16.04 into the middle of a line, then the space
characters directly after the special character display with a
"compressed" character spacing/display until the behaviour is
"interrupted
*** This bug is a duplicate of bug 1736838 ***
https://bugs.launchpad.net/bugs/1736838
Public bug reported:
I am using a Hyper-V virtual machine on Windows 10 Pro (1709 build
16299.125), and have received the error in the summary following the
first update after install.
ProblemType: Package
:-O!
It only took eight years, but we did it folks!
Hooray!
R
On Tue, Dec 5, 2017 at 10:23 AM, Jeremy Bicha wrote:
> This is finally "fixed" in Ubuntu 18.04 Alpha by having gnome-user-share
> depend on the packages it needs. The depends are not a fully functional
> Apache install but just an A
1 - 100 of 1261 matches
Mail list logo
