*** This bug is a duplicate of bug 245213 ***
https://bugs.launchpad.net/bugs/245213
I don't think this is a duplicate bug.
I had the exact same problem in Ubuntu NBR 9.04.
I fixed it through starting up in recovery mode (option in the grub boot
loader), then selecting 'attempt to automatica
No, I just haven't logged on in a while. I'd still like to try :-)
Thanks,
Daniel
--
[needs-packaging] KScannerButtons
https://bugs.launchpad.net/bugs/112039
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
u
I have read the guide to packaging in the ubuntu wiki and feel pretty
confident. A mentor would be helpful but I don't need one that badly.
I would be really interested in working on this package or another one
like it.
Thanks very much,
Daniel
--
[needs-packaging] KScannerButtons
https://bugs.
Hi Paul, thanks for pointing me to this bug from
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1827791.
Is this also on a Dell XPS 13 9380?
Your comment about Wayland made me curious, as I was using the default
Xorg session.
Testing with Wayland on 19.04 I also see the same problem
In comment 28, the freeze happened just before taking the log, yet the
last log entry was from ~1 minute earlier, so it doesn't look like there
were any relevant log entries.
However just now I had a freeze, and there are some messages in dmesg:
[10980.231902] perf: interrupt took too long (2512
*** This bug is a duplicate of bug 1826125 ***
https://bugs.launchpad.net/bugs/1826125
I agree with mactyr that this should not be a duplicate of that bug. The
flaw that I see is not what is shown in those videos. There is no
glitching, it is the whole screen flashing brighter, and is why I us
On the basis of 3 of us deeming that the symptoms of the other bug are
different to the ones described in this bug, I have removed the
duplicate link. I hope that's OK.
If it helps narrow it down, it seems that we all have the non-touch
1080p version, and all notice it much more when Night Light i
Hi Thomas, that sounds very similar to what we are seeing over in bug
1827790.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1826125
Title:
Dell XPS 13 9380 flickering (Whiskey Lake)
To manage not
Public bug reported:
Sendmail 8.15.2 seems to have a file descriptor bug/handling problem,
which is exposed when the ldap_routing feature is enabled.
I'm not certain I understand what you mean by "source package", but I
assume what you're looking for is the 'sendmail' package.
Distro: Ubuntu 16.
I'm seeing the same behavior out of rsyslogd. It shows up most
frequently with CRON runs, but I've seen it on kernel syslog entries as
well.
I'm shipping my logs into ELK, and I was noticing that old indices kept
getting updated. When I dug into the issue, I saw that this was
happening on a rela
@Colin: I'm experiencing the same issue. Installing updates to 14.04LTS
on my laptop in early December has made the GUI on my computer unusable
as well. It's a ThinkPad, I think with a stock Intel video chipset in
it. Here is the output of my .xsession-errors file:
Script for auto started at ru
One addendum: the permissions of my ~/.X* files are good (I own them and
they're writeable), and the permissions on /tmp and /tmp/.X11* look
correct as well. I moved ~/.config/dconf out of the way as well, and
that didn't make a difference either.
--
You received this bug notification because yo
Using the script that Marmuta suggested at the top generates two files.
Here is the content of the user one:
SpiRegistry daemon is running with well-known name -
org.a11y.atspi.Registry
** (at-spi2-registryd-:14335): WARNING **: Failed to register client:
GDBus.Error:org.freedesktop.DBus.Error.Se
Public bug reported:
I'm reporting this here to raise awareness of the bug. I suspect it's
the same identical problem reported with Bind9 on Fedora, at:
https://bugzilla.redhat.com/show_bug.cgi?id=709205
Basically, with DNSSEC enabled, and the "managed-keys-directory" option
commented out in the
I discovered this bug the hard way when I transferred over my named.conf
from a Ubuntu 10.04 LTS system to 12.04. The managed-keys-directory
option was not valid in 10.04 (Bind 9.7.0).
** Bug watch added: Red Hat Bugzilla #709205
https://bugzilla.redhat.com/show_bug.cgi?id=709205
** Also affe
I still hit this issue a few times per week, usually after resuming from
suspend.
I've attached the dmesg output from the most recent one (today). In this
instance, although the Wi-Fi was not working, I was still able to
interact with the system and shut it down cleanly. That's not always the
case
** Attachment removed: "dmesg output after Wi-Fi crash"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818881/+attachment/5279667/+files/wifi-crash-2019-07-28.txt
** Attachment added: "dmesg output after Wi-Fi crash"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818881/+atta
Public bug reported:
I had a device request an IP on one VLAN (one interface associated with
the server -- ens256), and then I moved the device to a different VLAN
(interface ens192 on the server), and was surprised when the DHCPD
process continued to hand out the same IP on the new VLAN.
Here ar
I also noticed problems with omshell after upgrading to Ubuntu 20.04,
and after finding this bug report I can confirm that compiling the ISC
sources (w/o the Ubuntu/Debian patches) does resolve the problem(s)
reported here.
--
You received this bug notification because you are a member of Ubuntu
Public bug reported:
I'm not sure what the issue was, or if it's significant.
What happened: I was upgrading from Ubuntu 22.04 to Ubuntu 24.04
During the upgrade (before the reboot to run on the Ubuntu 24.04 kernel), LPRng
was restarted and errored out. (Should it have errored out? That seems wr
Reassigned to installation-guide per mdke's suggestion.
** Changed in: ubuntu-docs (Ubuntu)
Sourcepackagename: ubuntu-docs => installation-guide
--
Install Manual link on Alternate CD incorrect
https://launchpad.net/bugs/53691
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://li
ThinkWiki has some more information on this:
http://thinkwiki.org/wiki/Predesktop_Area
which links to
http://thinkwiki.org/wiki/Hidden_Protected_Area
http://thinkwiki.org/wiki/Rescue_and_Recovery
The basic gist is that there's a hidden part of the hard drive (at the
end) that can be booted into wh
While not a duplicate, the recovery partition accessibility problem is
also discussed in Bug 19634.
--
Grub removes Windows boot option when NTFS partition needs recovery
https://launchpad.net/bugs/21175
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/l
** Package changed: xorg (Ubuntu) => ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1727039
Title:
Xorg crash
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+
Public bug reported:
This problem occur:
- when I input USB stick
- When I have click about system (more details of Ubuntu)
- Using normally, so open a video then system log off or freeze.
I try Ctrl + Shft + F1 or Ctrl + Shift + F2 but it goes to the GDM login
screen.
ProblemType: Bug
DistroRe
Public bug reported:
I got some messages in logs program.
Message:
"CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Erro ao chamar
StartServiceByName para org.gnome.ScreenSaver:
GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process
org.gnome.ScreenSaver exited with st
*** This bug is a duplicate of bug 1720400 ***
https://bugs.launchpad.net/bugs/1720400
Issue presented on a 17.10, a fresh install.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1724738
Title:
Public bug reported:
When I've put my pendrive system just close session and I go back to log in
screen. It happens in very different ways.
Attached goes the logs file.
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.
Public bug reported:
Binary package hint: postgresql-8.4
Upon installing postgresql-8.4, the server fails to start during --configure.
The log shows:
PANIC: could not open file "pg_xlog/0001" (log file 0,
segment 0): Invalid argument
Steps to reproduce:
-boot Ubuntu 10.10 l
--
Server failed to start during --configure: could not open file (pg_xlog):
Invalid argument
https://bugs.launchpad.net/bugs/672365
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.
** Attachment added: "/var/log/postgresql/postgresql-8.4-main.log"
https://bugs.launchpad.net/ubuntu/+source/postgresql-8.4/+bug/672365/+attachment/1726452/+files/postgresql-8.4-main.log
--
Server failed to start during --configure: could not open file (pg_xlog):
Invalid argument
https://bu
** Attachment added: "/var/log/apt/term.log"
https://bugs.launchpad.net/ubuntu/+source/postgresql-8.4/+bug/672365/+attachment/1726453/+files/term.log
** Summary changed:
- Server failed to start: could not open file: Invalid argument
+ Server failed to start: could not open file (pg_xlog): I
*** This bug is a duplicate of bug 658857 ***
https://bugs.launchpad.net/bugs/658857
** This bug has been marked a duplicate of bug 658857
package postgresql-8.4 8.4.5-0ubuntu10.10 failed to install/upgrade: el
subproceso script post-installation instalado devolvió el código de salida de
*** This bug is a duplicate of bug 658857 ***
https://bugs.launchpad.net/bugs/658857
** Changed in: postgresql-8.4 (Ubuntu)
Status: New => Confirmed
** Changed in: postgresql-8.4 (Ubuntu)
Status: Confirmed => New
--
Server failed to start during --configure: could not open fil
Interestingly enough, this appears to be a regression. I got the same
results as you did on a 10.10 livecd.
However, on a 10.04.1 livecd, postgresql-8.4 installs and starts
successfully.
** Summary changed:
- package postgresql-8.4 8.4.5-0ubuntu10.10 failed to install/upgrade: el
subproceso scr
In particular http://www.piware.de/2010/09/postgresql-9-0-final-
released/#comment-1083 and the comment below it highlight the issue.
--
server fails to start, does not detect livecd filesystem's wal_sync_method
https://bugs.launchpad.net/bugs/658857
You received this bug notification because you
Public bug reported:
Binary package hint: linux-image-2.6.35-22-generic
Failed to symbolic-link /boot/initrd.img-2.6.35-22-generic to
initrd.img: File exists
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: update-manager 1:0.142.20
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
** Summary changed:
- Kernel update on livecd fails to symlink initrd.img:
+ Kernel update on livecd fails to symlink initrd.img: File exists
--
Kernel update on livecd fails to symlink initrd.img: File exists
https://bugs.launchpad.net/bugs/663608
You received this bug notification because yo
I'm not sure if this is expected behavior, feel free to close the bug if
it is.
I booted from a 10.10 livecd, ran Update Manager, and told it to install
everything it found updates for.
I'll attach the entire /var/log/apt/term.log, but here's the relevant
piece:
Setting up linux-image-2.6.35-22-
Public bug reported:
package linux-image-2.6.32-24-generic 2.6.32-24.43 failed to
install/upgrade: subprocess installed post-installation script returned
error exit status 2
I used Update Manager to attempt to update the following packages:
-linux-image-2.6.32-24-generic
-linux-headers-2.6.32-24
** Attachment added: "/var/log/apt/history.log"
https://bugs.launchpad.net/bugs/645700/+attachment/1625324/+files/history.log
** Attachment added: "AptOrdering.txt"
https://bugs.launchpad.net/bugs/645700/+attachment/1625325/+files/AptOrdering.txt
** Attachment added: "Dependencies.txt"
I can, in fact restart after this error.
After restarting, Update Manager reports that the system is up to date.
~$ apt-cache policy linux-image-2.6.32-24-generic
linux-image-2.6.32-24-generic:
Installed: 2.6.32-24.43
Candidate: 2.6.32-24.43
Version table:
*** 2.6.32-24.43 0
500 ht
*** This bug is a duplicate of bug 609932 ***
https://bugs.launchpad.net/bugs/609932
My naive understanding is that this is not a duplicate of bug #609932.
The relevant parts of my dpkg terminal log are:
Preparing to replace linux-headers-2.6.32-24-generic 2.6.32-24.39 (using
.../linux-heade
*** This bug is a duplicate of bug 562312 ***
https://bugs.launchpad.net/bugs/562312
** This bug is no longer a duplicate of bug 609932
package linux-image-2.6.32-24-generic 2.6.32-24.38 failed to
install/upgrade: subprocess installed post-installation script returned error
exit status 2
In my case ( bug #645700 ) there were over 700MB free, so presumably
lzma did not run out of space.
In my case, /vmlinuz does point to a valid file, but I have no idea if
this was true before the update:
~$ ls -al /vmlinuz
lrwxrwxrwx 1 root root 30 2010-09-17 00:28 /vmlinuz ->
boot/vmlinuz-2.6.3
45 matches
Mail list logo
