*** This bug is a duplicate of bug 68020 ***
https://bugs.launchpad.net/bugs/68020
deleting the log files worked for me
--
Azureus crashes with SIGSEGV
https://bugs.launchpad.net/bugs/71220
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact f
I don't need a backport as I found a way around it in14.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1403228
Title:
unable to connect external monitor
To manage notifications about this bug go
I did what you said penalvch and booted from USB
http://cdimage.ubuntu.com/daily-live/current/vivid-desktop-amd64.iso, as
the bug previously was also present when booting from USB.
The bug does not exist in that ISO.
However in earlier versions I fixed it by making a custom display
configuration
Public bug reported:
When connecting a BenQ T905 through HDMI with a resolution of around
1280x1020, the mouse starts wobling back and forth 4-5 times a second.
Checking the log, it seems like the system cant decide on a correct
resolution and changing it back and forth between different resolutio
** Also affects: ubuntu
Importance: Undecided
Status: New
** No longer affects: ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1402516
Title:
computer freeze connecting external mon
** Description changed:
When connecting a BenQ T905 through HDMI with a resolution of around
1280x1020, the mouse starts wobling back and forth 4-5 times a second.
Checking the log, it seems like the system cant decide on a correct
resolution and changing it back and forth between differen
** Also affects: ubuntu
Importance: Undecided
Status: New
** Description changed:
Computer freezes and mouse moves back and forth while connecting
external monitor.
Similar bug report on Linux Mint 17 (also Ubuntu 14.04 based).
https://bugs.launchpad.net/linuxmint/+bug/133289
** Also affects: 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/1332895
Title:
Mint 17 - Cinnamon - using HDMI with some external monitors
To manag
It seems to Ubuntu 14.04 in general also, I posted this bug after
testing Ubuntu Desktop 14.04.1
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1403228
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
** Description changed:
When connecting a BenQ T905 through HDMI with a resolution of around
1280x1020, the mouse starts wobling back and forth 4-5 times a second.
Checking the log, it seems like the system cant decide on a correct
resolution and changing it back and forth between differen
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1403228
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1332895
Title:
Mint 17 - Cinnamon - using HDMI with some external monitors
To manage notifi
Please mark yourself affected here also, since it's here the root cause
lies i suspect, unless also in Debian?
Link to ubuntu bug:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1403228
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
Found a workaround though: when connecting external monitor, spam Fn+F4.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1332895
Title:
Mint 17 - Cinnamon - using HDMI with some external monitors
To
Public bug reported:
The installation always fails at about the same point regardless of
whether a USB stick is used or a DVD is used for the installation.
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: ubiquity 19.04.9
ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
Uname: Linux 5.
Public bug reported:
I have attempted fresh install of Ubuntu 17.10 numerous times onto a
drive that has previously held versions of Ubuntu. I have used both USB
and DVD installs. I have created several DVD's changing the write speed
without success.
I have checked read speeds of HDD's and done f
Since then I have re-created my USB Stick, and re-installed numerous
times on various drives with the same failure at 39% of the files
copied. In the latest attempt I used the guided installation using the
entire /dev/sda disk, but it failed in the same manner.
I generally always use manual instal
I decided to try the alternative download. I first tried usb-creator-
kde, but that app hung up and never gave an error message. So, I decided
to use UNetBootLoader and, very interestingly, it hung up at 41% disk
copying the iso file to the usb. My install always fails at 39%. The
sha256SUM checked
I downloaded kubuntu from:
http://cdimage.ubuntu.com/kubuntu/releases/17.10/release/kubuntu-17.10
-desktop-amd64.iso. I then used UNetBootLoader and it stopped at the
same point, 41%, on filesystem.squashfs.
The alternate download location is:
http://cdimage.ubuntu.com/kubuntu/releases/17.10/relea
Public bug reported:
crash right at the end of the install
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: ubiquity 17.10.10
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CasperVersion: 1.387
Public bug reported:
Here is the back trace information:
Application: GDebi (gdebi-kde), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[KCrash Handler]
#6 0x in ()
#7 0x7f018591ea3a in sip_api_get_cpp_ptr () at
/usr/l
I've confirmed that the innodb_additional_mem_pool_size line is
commented out, but I still get the same error after restarting. I have
done sudo apt-get dist-upgrade as well as sudo apt-get update, so
everything is literally up to the minute. I am not sure what else to try
at this point.
--
You r
Public bug reported:
I have attempted to install Yakkety on an existing computer(which had
Ubuntu on previously) with new drives and other hardware. I am using
UNETBootin with a downloaded latest daily version of Ubuntu. The
download occurred yesterday and about 1700 Zulu UTC+6. This is the
thi
In my most recent attempt to install I did a fresh download of Kubuntu 16.10
live to another Pen Drive
and got an error message 'ubi-console-setup' failed with return code of 1. I
tried to re-select the keyboard, if that is what it is referring to, choosing
the Danish keyboard instead of US. It
The stalling event seems to occur at setting the time zone. The
keyboard thing might just be a red herring.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1589122
Title:
Yakkety crash during install
It continues to crash at configuring time zone. I have tried setting
the time and time zone using the trial version kubuntu, which works
fine, of course, it doesn´t transfer anything over to setup.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
It appears that there is a timeout happening when the install program
tries to sync with the time server. I have been looking,
unsuccessfully, for a way to get past that problem. The machine is
logged onto the router, so it has access to the internet. I am working
from the machine now with the tr
** Summary changed:
- Yakkety crash during install 3/4 way through
+ Yakkety crash during install setting NTP
** Description changed:
I have attempted to install Yakkety on an existing computer(which had
Ubuntu on previously) with new drives and other hardware. I am using
UNETBootin with
I have continued to attempt install each time with the same result. I
am installing onto a SAMSUNG 500MB SSD. The BIOS of the computer is
setup for UEFI + Legacy. For what itś worth I have pinged from the
Virtual Console ntp.ubuntu.com successfully.
During the install I checked automatic updatin
I have continued to re-install using many different USB MemorySticks. I
have switched from using UEFI USBKey to instead using legacy USBKey. I
have noticed that an additional error appears now that the copy function
has failed, etc., etc. My computer mostly has USB 3.1, but there are a
couple of
I am discontinuing attempts to install Kubuntu 16.10. I have tried
using UEFI and Legacy with both USB Stick and DVD all with the same
result. The USB always shows 1 file in error on checkdisk. I have
updated each day to have the latest daily version. I have wiped the
USB's and re-formatted in GP
No problems with 1:2.22.1-0ubuntu3.
Thanks a lot, guys!
--
gnome-display-properties crashed on opening with SIGSEGV in rw_mode_get_width()
https://bugs.launchpad.net/bugs/216676
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu
I think your problem (translaterx_german) is quite different to mine.
Please file a new bug.
I'm closing this one. Somehow it went away.
get-edid now works. xrandr returns the list of resolutions successfully,
on the correct device:
Screen 0: minimum 320 x 200, current 1680 x 1050, maximum 1680
Symptom of bug mysteriously disappeared - the machine had been rebooted
10~20 times without change, but after the power went off while it was
on, on the next boot things were fine.
** Changed in: xserver-xorg-video-ati (Ubuntu)
Status: New => Invalid
--
failing to detect available resolut
Hi. Where/how can we get this latest version, 1:2.22.1-0ubuntu5? The
pool appears to have only 2.22.1-0ubuntu2 as far as I can see, but it
may be that I don't know where to look.
This problem's just run into me as I recently upgraded my hardy install.
I'm using ATI, however! An
Public bug reported:
Binary package hint: gnome-control-center
I recently upgraded to the latest hardy - beforehand all was working
well; using `radeon' kernel module for my ATI card. Post-upgrade, the
screen resolution changed to 1280x768 (from 1680x1024 or thereabouts -
widescreen monitor). So,
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/13405162/Dependencies.txt
** Attachment added: "Disassembly.txt"
http://launchpadlibrarian.net/13405163/Disassembly.txt
** Attachment added: "ProcMaps.txt"
http://launchpadlibrarian.net/13405164/ProcMaps.txt
** Attac
Public bug reported:
Binary package hint: xserver-xorg-video-ati
Hi there,
This appears to be a regression in the latest hardy. All was working
well, I upgraded (~400 packages). My monitor's maximal resolution is
1680x1050, which I used. Post-upgrade, it's now at 1280x768. Due to an
unrelated[?]
** Attachment added: "X logs"
http://launchpadlibrarian.net/13405791/Xorg.0.log
--
failing to detect available resolutions, cannot use proper ones (regressed)
https://bugs.launchpad.net/bugs/216696
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Attaching `sudo get-edid`. It fails, in the end.
** Attachment added: "output from `sudo get-edid`"
http://launchpadlibrarian.net/13405799/edid-output
--
failing to detect available resolutions, cannot use proper ones (regressed)
https://bugs.launchpad.net/bugs/216696
You received this bug no
Here's X's log.
** Attachment added: "X logs"
http://launchpadlibrarian.net/13406441/Xorg.0.log
--
gnome-display-properties crashed on opening with SIGSEGV in rw_mode_get_width()
https://bugs.launchpad.net/bugs/216676
You received this bug notification because you are a member of Ubuntu
Bugs,
X config. I will look into getting a proper stacktrace for you.
** Attachment added: "xorg.conf"
http://launchpadlibrarian.net/13406450/xorg.conf
--
gnome-display-properties crashed on opening with SIGSEGV in rw_mode_get_width()
https://bugs.launchpad.net/bugs/216676
You received this bug not
(gdb) run
Starting program: /usr/bin/gnome-display-properties
[Thread debugging using libthread_db enabled]
[New Thread 0xb6ca2720 (LWP 10742)]
CRTC 4a Timestamp: 7278908
CRTC 4b Timestamp: 7278908
Output 4c Timestamp: 7278908
Output 4d Timestamp: 7278908
Output 4e Timestamp: 7278908
Program rece
No problems. Here's the extra back trace info. I'll run it with valgrind
next.
(gdb) thread apply all bt full
Thread 1 (Thread 0xb6d5f720 (LWP 11066)):
#0 rw_mode_get_width (mode=0x3) at randrwrap.c:1104
__PRETTY_FUNCTION__ = "rw_mode_get_width"
#1 0x0804d62b in rebuild_gui (app=0x807a0
Valgrind log attached! Looks painful.
** Attachment added: "valgrind.log"
http://launchpadlibrarian.net/13406992/valgrind.log
--
gnome-display-properties crashed on opening with SIGSEGV in rw_mode_get_width()
https://bugs.launchpad.net/bugs/216676
You received this bug notification because yo
Perfect!
Well, almost. No screens appear - I believe this is because I also
*happen* to be suffering from (proposed) bug 216696 - i.e. X detects no
monitors as being available. I'm hoping it's not a complicating factor.
Either way, given these packages gnome-display-properties no longer
crashes,
Of course, my apologies.
Arlen
** Attachment added: "valgrind.log"
http://launchpadlibrarian.net/13421489/valgrind.log
--
gnome-display-properties crashed on opening with SIGSEGV in rw_mode_get_width()
https://bugs.launchpad.net/bugs/216676
You received this bug notification becau
ack to "New") so that it is clear
> to everyone that it needs work.
No problems! I'll look out for it then.
Cheers,
Arlen
** Attachment added: "unnamed"
http://launchpadlibrarian.net/13421674/unnamed
--
gnome-display-properties crashed on opening with SIGSEGV
I had a similar problem (Gutsy/AMD64, 2.6.22-14-generic, kvm
1:16-1ubuntu2), in that tap0 wasn't visible (ifconfig -a) on my host,
and kvm reported "can't add tap0 to bridge eth1: Operation not
supported" when starting.
However, after my host finished booting and everything network related
had fin
I get the same issue without wins in nsswitch.conf at all - but stranger
results yet depending on whether or not an iPhone is currently connected
to the computer.
With an iPhone connected, I get an invalid pointer crash with backtrace
ending in libusb, then libc shortly thereafter. (log attached)
As always, if any more information is helpful, let me know; it's been
ages since I followed up on a bug report ...
--
rhythmbox crashed with SIGSEGV in _nss_wins_gethostbyname_r()
https://bugs.launchpad.net/bugs/529714
You received this bug notification because you are a member of Ubuntu
Bugs, wh
I'm going to go ahead and take away the opinion I had of this some three
and a half years ago now - honestly, the GDB stub is in all likelihood
much more useful than whatever Bochs come up with themselves.
chilicuil; is there some overriding reason you can't use gdb to debug it
instead? As William
51 matches
Mail list logo
