Public bug reported:
Ich bekomme von der Aktualisierungsverwaltung diese Meldung:
Die Paketoperation ist gescheitert
Das Installieren oder Entfernen eines Software-Pakets ist gescheitert.
ProblemType: Package
DistroRelease: Ubuntu 24.04
Package: linux-headers-generic 6.8.0-53.55+1
ProcVersionSign
Public bug reported:
I got a message telling like: A package operation failed after update.
ProblemType: Package
DistroRelease: Ubuntu 24.04
Package: linux-generic 6.8.0-53.55+1
ProcVersionSignature: Ubuntu 6.8.0-51.52-generic 6.8.12
Uname: Linux 6.8.0-51-generic x86_64
ApportVersion: 2.28.1-0ubu
I have the same problem. Ubuntu 24.04 (fresh install, all packages
updated) will not charge an old HP EliteBook 8460 with healthy battery.
It worked fine with OpenSUSE 15.5.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
I can't believe that 8 years later users are still expected to simply
live with a cluttering "~/snap" folder in their $HOME. It shouldn't be
that difficult to change it to "~/.snap", should it?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
Hello Rex,
for me the Solution was to change the ldap tls cipher parameter.
You can easaly check it when you disable ldap_tls_cipher_suite. After this the
connection work for me.
After a while of search i found that Ubuntu or sssd changed the ssl tool or his
paramerts
Not Openssl is used anym
I found that the "Workspace Indicator" was causing this problem for me.
https://extensions.gnome.org/extension/21/workspace-indicator/
Clean install of 18.04 on real hardware. Xorg session. Nvidia 1050 with
open source drivers. 2k resolution. Problem did NOT occur for two
weeks. Installed "Wor
Public bug reported:
Description:Ubuntu Bionic Beaver (development branch)
Release:18.04
libnvidia-compute-390:
Installed: 390.48-0ubuntu3
Candidate: 390.48-0ubuntu3
Version table:
*** 390.48-0ubuntu3 500
500 http://at.archive.ubuntu.com/ubuntu bionic/restricted amd64 P
I am new to bug reporting so apologies if I'm doing this wrong.
It seems I am also affected by this. I tried the upgrade from mate 17.10
to 18.04 with nvidia installed which lead to a black screen. Then I
tried upgrading first and then installing nvidia also a black screen. I
have a Lenovo w550s w
I am new to bug reporting so apologies if I'm doing this wrong.
It seems I am also affected by this. I tried the upgrade from mate 17.10
to 18.04 with nvidia installed which lead to a black screen. Then I
tried upgrading first and then installing nvidia also a black screen. I
have a Lenovo w550s w
Public bug reported:
The current shipped version is unfortunately badly out of date. 4.1.6 is
from 2011 and has no Python 3 compatibility. The current version is
4.2.2 and supports Python 3.6 (and 2.7).
** Affects: omniorb-dfsg (Ubuntu)
Importance: Undecided
Status: New
--
You rec
NUK SKL-H BIOS version 0045 and later should fix this issue.
https://downloadcenter.intel.com/download/26698/NUCs-BIOS-Update-KYSKLi70-86A-
Thanks
Tomas
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
Public bug reported:
Trying to get Xampp running. MariaDB would never launch
ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: mariadb-server-10.1 (not installed)
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
Uname: Linux 4.10.0-19-generic x86_64
NonfreeKernelModules: nvidia_u
This is a BIOS issue can you please attach dmidecode of your platform, I'd like
to know more detailed platform and bios information.
Also please add the while dmesg and cat /proc/iomem
Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
Public bug reported:
Error occured while dist-upgrade from 12.4 LTS to 14.4
Last part of main.log:
2016-12-28 19:57:55,129 DEBUG found components: {'trusty-updates':
set(['restricted', 'main', 'multiverse', 'universe']), 'trusty-security':
set(['restricted', 'main', 'multiverse', 'universe']),
Still an issue in 16.04. Workaround in comment 24
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/898087/comments/24
works for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/898087
Title:
K
Public bug reported:
1- install
2- error - crash
3- remove
4- install
5- systemd crash
6- reboot
7- error message
8- mysql-server running ok
9- ?
Thank
ProblemType: Package
DistroRelease: Ubuntu 15.10
Package: mysql-server-5.6 5.6.27-0ubuntu1
ProcVersionSignature: Ubuntu 4.2.0-23.28-generic 4.2.6
Thaddaeus, sorry but I don't understand how is this invalid when the default
out-of-the-box configuration is broken?
I am pretty sure that most of the users, like myself, did not explicitly choose
or configure light-locker, we just got it by default when upgrading to 14.04.
Thank you for providi
Here too on chrome 40.0.2214.94 (64-bit) on xubuntu 14.04.1.
Disabling compositor in xfce window manager tweaks worked for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1309801
Title:
[xubuntu]
How can this be invalid?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1389159
Title:
Clicking on search results doesn't take you to the corresponding page
To manage notifications about this bug go
I am experiencing what sounds like the same symptom, on xubuntu 14.04 -
screen blanks after inactivity, even after configuring it to never
blank.And it doesn't unblank on activity - it only unblanks when I
blindly type my password (apparently the session is locked but the
password prompt is no
apport information
** Attachment added: "xserver.devices.txt"
https://bugs.launchpad.net/bugs/1391984/+attachment/4271818/+files/xserver.devices.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
apport information
** Attachment added: "XorgLogOld.txt"
https://bugs.launchpad.net/bugs/1391984/+attachment/4271815/+files/XorgLogOld.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1391984
Ti
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1391984/+attachment/4271812/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1391984
Title:
Ma
apport information
** Attachment added: "xdpyinfo.txt"
https://bugs.launchpad.net/bugs/1391984/+attachment/4271817/+files/xdpyinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1391984
Title:
apport information
** Attachment added: "UdevLog.txt"
https://bugs.launchpad.net/bugs/1391984/+attachment/4271813/+files/UdevLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1391984
Title:
apport information
** Attachment added: "XorgLog.txt"
https://bugs.launchpad.net/bugs/1391984/+attachment/4271814/+files/XorgLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1391984
Title:
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1391984/+attachment/4271801/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1391984
apport information
** Attachment added: "BootLog.txt"
https://bugs.launchpad.net/bugs/1391984/+attachment/4271799/+files/BootLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1391984
Title:
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1391984/+attachment/4271808/+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/1391984
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1391984/+attachment/4271811/+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/1391984
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1391984/+attachment/4271810/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/139
Same in latest kernel (3.13.0-40-generic)
** Tags added: apport-collected ubuntu
** Description changed:
On a Macbook Air 2013 (6,2), I used to run Mint 16 XFCE (natively, not via
virtualization), and had my external Samsung display happily running at its max
resolution of 2560x1440 via a HD
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1391984/+attachment/4271806/+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/1391984
Title:
Max
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1391984/+attachment/4271807/+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/1391984
Title:
Max
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1391984/+attachment/4271809/+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/1391984
apport information
** Attachment added: "DkmsStatus.txt"
https://bugs.launchpad.net/bugs/1391984/+attachment/4271802/+files/DkmsStatus.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1391984
Ti
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1391984/+attachment/4271800/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1391984
apport information
** Attachment added: "Xrandr.txt"
https://bugs.launchpad.net/bugs/1391984/+attachment/4271816/+files/Xrandr.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1391984
Title:
Ma
apport information
** Attachment added: "DpkgLog.txt"
https://bugs.launchpad.net/bugs/1391984/+attachment/4271803/+files/DpkgLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1391984
Title:
apport information
** Attachment added: "LightdmDisplayLog.txt"
https://bugs.launchpad.net/bugs/1391984/+attachment/4271804/+files/LightdmDisplayLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
apport information
** Attachment added: "LightdmLog.txt"
https://bugs.launchpad.net/bugs/1391984/+attachment/4271805/+files/LightdmLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1391984
Ti
apport information
** Attachment added: "BootDmesg.txt"
https://bugs.launchpad.net/bugs/1391984/+attachment/4271798/+files/BootDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1391984
Titl
Confirmed same resolution limitation exists in 14.10.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1391984
Title:
Max resolution of external monitor degrades when upgrading from 13.10
to 14.04.1
Public bug reported:
On a Macbook Air 2013 (6,2), I used to run Mint 16 XFCE (natively, not via
virtualization), and had my external Samsung display happily running at its max
resolution of 2560x1440 via a HDMI adapter.
I confirmed the same resolution can be obtained when booting Xubuntu 13.10 f
current version is "20130613+svn660+dfsg-1" which basically contains
the upstream fix mentioned here.
** Changed in: pidgin-skype (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
So it looks like triggering a simple rebuild would fix this problem
right? So how can one trigger it for the repo?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1379713
Title:
Pidgin crashes when pi
It's actually a bug in the plugin not pidgin itself
** Package changed: pidgin (Ubuntu) => pidgin-skype (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1379713
Title:
Pidgin crashes when pid
Simply compiling libskype64.so from source and then placing that in the
local plugins directory worked.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1379713
Title:
Pidgin crashes when pidgin-skype
Public bug reported:
It seems the pidgin-skype extension causes a
Attempt to unlock mutex that was not locked
Aborted
error and pidgin crashes immediatly. Deinstalling skype-pidgin solves
the problem but then I can no longer access my skype chats of course.
ProblemType: Bug
DistroRelease: Ubunt
Worked perfectly! Thank you so much.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1160188
Title:
ATH9K wireless signal weak
To manage notifications about this bug go to:
https://bugs.launchpad.ne
I'm having trouble with the make command. Could someone explain how to
do this, or should I just wait for it to be released since this is over
my head?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/11
I got this at the end. Any suggestions?
grep: /boot/config-3.10.0-rc5: No such file or directory
WARNING: missing /lib/modules/3.10.0-rc5
Device driver support needs thus be built-in linux image!
ERROR: could not open directory /lib/modules/3.10.0-rc5: No such file or
directory
FATAL: could not
Thanks for the quick replies.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1160188
Title:
ATH9K wireless signal weak
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/
When I paste the second command "checkout v3.10-rc5" it tells me that
it's an invalid command.
I also tried:
"I've tryed that :
wget -O kernel.sh http://ubuntuone.com/1iJaMuISila67x9wV07SW4 && chmod +x
kernel.sh
and It works perfectly !!
Thanks"
Which didn't work for me.
Which of the above pos
*** This bug is a duplicate of bug 858122 ***
https://bugs.launchpad.net/bugs/858122
I know, it's weird, but this simple command works for me:
sudo /etc/init.d/dbus restart
Now everything works fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
appreciate it.
=)
Anyway we really like the 13.04 (final) it works well on this new system.
Ubuntu is great, and it keeps getting better and better. You are part of
what makes it better and better.
Thanks again, you were very, very helpful. =)
sincerely,
Lucille Winkler
On Thu, May 9, 2013 at 8:02 PM
i)
lucille@lucille-Inspiron-7720:~$ echo $?
0
lucille@lucille-Inspiron-7720:~$
On Fri, Apr 19, 2013 at 11:17 AM, Steve Langasek <
steve.langa...@canonical.com> wrote:
> On Fri, Apr 19, 2013 at 12:55:13PM -, Dan Winkler wrote:
> > Boot000C* ubuntu
> >
> HD(1,8
; each other. It will boot up in non secure mode. I want to able to boot
> to windows 8 hard drive or unbunta hard with out changing secure on
> and off. can any one help me. thanks dan winkler
>
> To manage notifications about this bug go to:
> https://bugs.launchpad
boot device ubuntu in my uefi boot to
boot from I get a blank screen. When I use the F12 key and go to my boot
menu and pick ubuntu boot device in pic p4180031 the I get this screen pic
p4180029. I hope this helps you to help me. Thanks Dan Winkler
On Wed, Apr 17, 2013 at 10:30 PM, Steve Langasek
y one
help me. thanks dan winkler
** Affects: shim (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/1170183
Title:
can not boot up in uefi secure
Christopher,
thanks removing all nvidia related packages that had no other
dependencies attached helped. So also in my case the Virtual Box package
update seemed to have caused the damage. Though I didn't need to remove
the Virtual Box package.
Thanks again for finding out,
Dietmar
--
You recei
The same here. After upgrade I can not run Unity any longer. Even the
fallback via llvm does only partly work since the menues (dash?) are not
loaded. So basically it's desktop background without any window manager.
I had to fall back to XFCE in order to get this working.
Kernel: Version: 3.5.0.17
** Also affects: auctex
Importance: Undecided
Status: New
** No longer affects: auctex
** Also affects: ecb (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.l
Although it says there was a fix released it occurred again last week.
See also log attached
** Attachment added: "crash.log"
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1028388/+attachment/3435329/+files/crash.log
--
You received this bug notification because you are
Confirmed for Ubuntu 12.04 on the same netbook (Asus Eee PC 1015-PX
Seashell). I will give more information when needed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/994084
Title:
Xubuntu 12.04 - sy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/903295
Title:
Upgrade from 11.04 to 11.10 doesn't work, tried both with
upgrademanager and from cd with terminal and shell. showed failures
don't app
Public bug reported:
When the Upgrade offer to Ubuntu 11.10. came, I paused the Upgrade to do
it later. It wasn't possible to resume the Upgrade and every new try is
blocked with the same failure message, both if I tried it directly over
the download manager like in the first place or -according t
I can just confirm that this (comment #4) is _not_ yet fixed by:
Installed: 1:0.9.6-0ubuntu4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/862260
Title:
Grid plugin behaviour random
To manage noti
I can reproduce this just as described. In addition the rescaling steps
which for example work for KP3 (i.e., 2/3, 1/2, 1/3, 1/4
width) no longer work for KP4/6. This used to work
flawlessly in 11.04.
** Changed in: unity
Status: Incomplete => Confirmed
** Changed in: unity (Ubuntu)
@Alessandro: Avidemux was not removed as such but simply had build
problems up to today. Just now a fix was released to oneiric-proposed
and if things go well it will hit the updates and some point. You can
follow the status of that in Bug #831096
--
You received this bug notification because you
Alan, sorry you are right. I thought that that was the same problem. I
just reverted the duplication note of #839219 again (btw I never did
anything to #874078 which doesn't even exist) so that that bug can be
handled by itself.
I hope that clears things up again.
--
You received this bug notif
** This bug is no longer a duplicate of bug 807771
synaptic crashed with SIGABRT in __kernel_vsyscall()
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/839219
Title:
synaptic crashes immediately on
*** This bug is a duplicate of bug 807771 ***
https://bugs.launchpad.net/bugs/807771
** This bug is no longer a duplicate of bug 839219
synaptic crashes immediately on startup with SIGABRT in raise() [Only when
accessibility is enabled, e.g. screen reader]
** This bug has been marked a dup
*** This bug is a duplicate of bug 807771 ***
https://bugs.launchpad.net/bugs/807771
** This bug is no longer a duplicate of bug 839219
synaptic crashes immediately on startup with SIGABRT in raise() [Only when
accessibility is enabled, e.g. screen reader]
** This bug has been marked a dup
*** This bug is a duplicate of bug 807771 ***
https://bugs.launchpad.net/bugs/807771
** This bug is no longer a duplicate of bug 839219
synaptic crashes immediately on startup with SIGABRT in raise() [Only when
accessibility is enabled, e.g. screen reader]
** This bug has been marked a dup
*** This bug is a duplicate of bug 807771 ***
https://bugs.launchpad.net/bugs/807771
** This bug has been marked a duplicate of bug 807771
synaptic crashed with SIGABRT in __kernel_vsyscall()
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
*** This bug is a duplicate of bug 807771 ***
https://bugs.launchpad.net/bugs/807771
** This bug is no longer a duplicate of bug 839219
synaptic crashes immediately on startup with SIGABRT in raise() [Only when
accessibility is enabled, e.g. screen reader]
** This bug has been marked a dup
*** This bug is a duplicate of bug 807771 ***
https://bugs.launchpad.net/bugs/807771
** This bug is no longer a duplicate of bug 839219
synaptic crashes immediately on startup with SIGABRT in raise() [Only when
accessibility is enabled, e.g. screen reader]
** This bug has been marked a dup
*** This bug is a duplicate of bug 807771 ***
https://bugs.launchpad.net/bugs/807771
** This bug is no longer a duplicate of bug 839219
synaptic crashes immediately on startup with SIGABRT in raise() [Only when
accessibility is enabled, e.g. screen reader]
** This bug has been marked a dup
*** This bug is a duplicate of bug 807771 ***
https://bugs.launchpad.net/bugs/807771
** This bug is no longer a duplicate of bug 839219
synaptic crashes immediately on startup with SIGABRT in raise() [Only when
accessibility is enabled, e.g. screen reader]
** This bug has been marked a dup
*** This bug is a duplicate of bug 807771 ***
https://bugs.launchpad.net/bugs/807771
** This bug is no longer a duplicate of bug 839219
synaptic crashes immediately on startup with SIGABRT in raise() [Only when
accessibility is enabled, e.g. screen reader]
** This bug has been marked a dup
*** This bug is a duplicate of bug 807771 ***
https://bugs.launchpad.net/bugs/807771
** This bug is no longer a duplicate of bug 839219
synaptic crashes immediately on startup with SIGABRT in raise() [Only when
accessibility is enabled, e.g. screen reader]
** This bug has been marked a dup
*** This bug is a duplicate of bug 807771 ***
https://bugs.launchpad.net/bugs/807771
** This bug is no longer a duplicate of bug 839219
synaptic crashes immediately on startup with SIGABRT in raise() [Only when
accessibility is enabled, e.g. screen reader]
** This bug has been marked a dup
*** This bug is a duplicate of bug 807771 ***
https://bugs.launchpad.net/bugs/807771
** This bug is no longer a duplicate of bug 839219
synaptic crashes immediately on startup with SIGABRT in raise() [Only when
accessibility is enabled, e.g. screen reader]
** This bug has been marked a dup
*** This bug is a duplicate of bug 807771 ***
https://bugs.launchpad.net/bugs/807771
** This bug is no longer a duplicate of bug 839219
synaptic crashes immediately on startup with SIGABRT in raise() [Only when
accessibility is enabled, e.g. screen reader]
** This bug has been marked a dup
*** This bug is a duplicate of bug 807771 ***
https://bugs.launchpad.net/bugs/807771
** This bug is no longer a duplicate of bug 839219
synaptic crashes immediately on startup with SIGABRT in raise() [Only when
accessibility is enabled, e.g. screen reader]
** This bug has been marked a dup
*** This bug is a duplicate of bug 807771 ***
https://bugs.launchpad.net/bugs/807771
** This bug is no longer a duplicate of bug 839219
synaptic crashes immediately on startup with SIGABRT in raise() [Only when
accessibility is enabled, e.g. screen reader]
** This bug has been marked a dup
*** This bug is a duplicate of bug 807771 ***
https://bugs.launchpad.net/bugs/807771
** This bug is no longer a duplicate of bug 839219
synaptic crashes immediately on startup with SIGABRT in raise() [Only when
accessibility is enabled, e.g. screen reader]
** This bug has been marked a dup
*** This bug is a duplicate of bug 807771 ***
https://bugs.launchpad.net/bugs/807771
** This bug is no longer a duplicate of bug 839219
synaptic crashes immediately on startup with SIGABRT in raise() [Only when
accessibility is enabled, e.g. screen reader]
** This bug has been marked a dup
*** This bug is a duplicate of bug 807771 ***
https://bugs.launchpad.net/bugs/807771
** This bug is no longer a duplicate of bug 839219
synaptic crashes immediately on startup with SIGABRT in raise() [Only when
accessibility is enabled, e.g. screen reader]
** This bug has been marked a dup
*** This bug is a duplicate of bug 807771 ***
https://bugs.launchpad.net/bugs/807771
** This bug is no longer a duplicate of bug 839219
synaptic crashes immediately on startup with SIGABRT in raise() [Only when
accessibility is enabled, e.g. screen reader]
** This bug has been marked a dup
*** This bug is a duplicate of bug 807771 ***
https://bugs.launchpad.net/bugs/807771
** This bug is no longer a duplicate of bug 839219
synaptic crashes immediately on startup with SIGABRT in raise() [Only when
accessibility is enabled, e.g. screen reader]
** This bug has been marked a dup
*** This bug is a duplicate of bug 807771 ***
https://bugs.launchpad.net/bugs/807771
** This bug is no longer a duplicate of bug 839219
synaptic crashes immediately on startup with SIGABRT in raise() [Only when
accessibility is enabled, e.g. screen reader]
** This bug has been marked a dup
*** This bug is a duplicate of bug 807771 ***
https://bugs.launchpad.net/bugs/807771
** This bug is no longer a duplicate of bug 839219
synaptic crashes immediately on startup with SIGABRT in raise() [Only when
accessibility is enabled, e.g. screen reader]
** This bug has been marked a dup
*** This bug is a duplicate of bug 807771 ***
https://bugs.launchpad.net/bugs/807771
** This bug is no longer a duplicate of bug 839219
synaptic crashes immediately on startup with SIGABRT in raise() [Only when
accessibility is enabled, e.g. screen reader]
** This bug has been marked a dup
*** This bug is a duplicate of bug 807771 ***
https://bugs.launchpad.net/bugs/807771
** This bug is no longer a duplicate of bug 839219
synaptic crashes immediately on startup with SIGABRT in raise() [Only when
accessibility is enabled, e.g. screen reader]
** This bug has been marked a dup
*** This bug is a duplicate of bug 807771 ***
https://bugs.launchpad.net/bugs/807771
** This bug is no longer a duplicate of bug 839219
synaptic crashes immediately on startup with SIGABRT in raise() [Only when
accessibility is enabled, e.g. screen reader]
** This bug has been marked a dup
*** This bug is a duplicate of bug 807771 ***
https://bugs.launchpad.net/bugs/807771
** This bug is no longer a duplicate of bug 839219
synaptic crashes immediately on startup with SIGABRT in raise() [Only when
accessibility is enabled, e.g. screen reader]
** This bug has been marked a dup
*** This bug is a duplicate of bug 807771 ***
https://bugs.launchpad.net/bugs/807771
** This bug is no longer a duplicate of bug 839219
synaptic crashes immediately on startup with SIGABRT in raise() [Only when
accessibility is enabled, e.g. screen reader]
** This bug has been marked a dup
OK I think I could figure what is kind of causing the segfault at least
for me. It's the language environment I'm using.
Steps to reproduce:
~$ export LANG=nb_NO.UTF-8
~$ sudo gdb synaptic
(gdb) run
Starting program: /usr/sbin/synaptic
[Thread debugging using libthread_db enabled]
Program receiv
1 - 100 of 305 matches
Mail list logo
