Ubuntu 20.04, xmlcopyeditor 1.2.1.3
Most of my folders are synchronized with Nextcloud and I cannot open a HTML
file.
A copy of the same file in ~/temp (not synchronized) opens perfectly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
The "No java runtime was found" warning disappeared. Likely corrected
upstream since 2016.
I realise today that installing libbatik-java and libavalon-framework-
java packages in Ubuntu makes the two other warnings disappear too.
I suppose that these warnings a related to the contents of the
Certainly in 19.04 (I do not remember when it begun: 18.10?), at some moment
appeared a much larger line spacing, pushing the OK button or the Quit button
out of the screen.
In LibreOffice Calc, I can choose formatting, but not get it actually: OK
button out of reach.
In Nextcloud (dialog from
Screen capture with a LibreOffice Calc dialog.
** Attachment added: "LOCalc_2019-08-27_10-35-00.png"
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1803706/+attachment/5284877/+files/LOCalc_2019-08-27_10-35-00.png
--
You received this bug notification because you are a member of
Screen capture with Nextcloud.
I am not a professional. To me it seems reasonable to think GTK is the culprit
but others may know better.
** Attachment added: "Nextcloud_2019-08-27_10-29-59.png"
Since April, I forgot. But I always use either apt-get install, either
synaptic. But in my report of April, I see update-notifier. I have a
faint remembrance of the update notifier giving it a try every day until
I got bored, filed the bug and found a workaround.
Le 13/08/19 à 22:37, Brian
Found this workaround in #1655431. Quoting: Boris Rybalkin (ribalkin) wrote on
2017-11-26: #18
Was able to fix sf mirrors issue by replacing sf mirror with some github copy:
sudo sed -i
's#http://downloads.sourceforge.net/corefonts#https://github.com/pushcx/corefonts/raw/master#g'
I still had the mscorefonts problem (errors in sourceforge mirrors) in 19.04.
Found this workaround in #1655431. Quoting: Boris Rybalkin (ribalkin) wrote on
2017-11-26:#18
Was able to fix sf mirrors issue by replacing sf mirror with some github copy:
sudo sed -i
Public bug reported:
A window proposes to finish the installation of ttf-mscorefonts-
installer. A dialog appears in another window but disappears
immediately. For the fraction of a second it can be seen, it looks like
the identification windows that comes for some upgrades (kernel etc.).
I observe the same behavior with Nemo 3.6.5-1 amd64, Ubuntu 18.04, GNOME
3.28.1, theme Adwaita (default).
When I write this it makes me think to change the theme: bingo! the renaming
selection is normal with Ambiance or Radiance.
--
You received this bug notification because you are a member
*** This bug is a duplicate of bug 1751194 ***
https://bugs.launchpad.net/bugs/1751194
This bug is said to be a duplicate of 1751194 which seems to be non
existing or private (?). The result is that when gjs-console crashes, I
get other crashes proposed, but never "in JS_GetContextPrivate()",
(From Bug 1762022)
I did add the ppa to my sources list and installed the new version.
I did not have a crash at startup since (but I am not sure to have had one
every time).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
More information about this:
It does *not* happen with Ubuntu 16.04 (4.4.0-81-generic #104-Ubuntu SMP Wed
Jun 14 08:17:06 UTC 2017 x86_64)
LibreOffice Version: 5.1.6.2, Build ID: 1:5.1.6~rc2-0ubuntu1~xenial2, Locale :
fr-FR (fr_BE.UTF-8)
fonts-freefont.otf and ttf 20120203-4
In my Ubuntu 17.04
Memory 3,8 Gb. Ubuntu 16.10 up to date as of today. Desktop is Flashback with
Nemo. Appmenu-qt5 is not installed. Indicator-applet-complete
12.10.2+15.20141127.2-0ubuntu1, indicator-application
12.10.1+15.20150128.2-0ubuntu1.
Indicator-applet gets mad after some time. At the beginning of the
Public bug reported:
In LibreOffice Writer or Calc, in the chain « test » the last » is invisible if
the font is FreeSerif. This seems peculiar to the combination
FreeSerif-LibreOffice:
-- If I change font in LibreOffice, the » reappears (even others Free
something).
-- If I write the same in
Public bug reported:
Ubuntu GNOME 16.04.
jing 20131210+dfsg+1-4 (xenial)
java-wrappers 0.1.28 (xenial)
Using jing gives:
[warning] /usr/bin/jing: No java runtime was found
[warning] /usr/bin/jing: Unable to locate avalon-framework in /usr/share/java
[warning] /usr/bin/jing: Unable to locate
Sebastien Bacher a écrit ce qui suit, le 23/07/14 12:10 :
it would be nice to have a bug we can use for the SRU, not sure if that
one is appropriate since it's years old and close. Otherwise agreed that
we should fix that issue in trusty
In the Debian sid package xkb-data 2.12-1, the bug *is*
(In reply to comment #69)
…
Regarding the voting, is there generic popular Linux-oriented site in
France? Like slashdot.org or smth...
There is a popular Linux-oriented site in France (linuxfr.org) and the
final ajustments of this layout were done after discussion on this site.
I
(In reply to comment #69)
…
Regarding the voting, is there generic popular Linux-oriented site in
France? Like slashdot.org or smth...
There is a popular Linux-oriented site in France (linuxfr.org) and the
final ajustments of this layout were done after discussion on this site.
I
I feel extremely uneasy because I am a user of free software and I am
full of respect and gratitude for the people who make this possible,
including of course Nicolas Mailhot. I am an amateur and I am conscious
that I rely entirely on the work of devoted paid and unpaid
professionals.
But in this
I feel extremely uneasy because I am a user of free software and I am
full of respect and gratitude for the people who make this possible,
including of course Nicolas Mailhot. I am an amateur and I am conscious
that I rely entirely on the work of devoted paid and unpaid
professionals.
But in this
More arguments in favor of reverting to an normal behaviour of Ctrl-R:
-- Most computers in most operating systems, languages (including French until
recently), desktops... have two identical Ctrl keys. It is queer to have French
keyboards doing otherwise since a few years.
-- Like having two
More arguments in favor of reverting to an normal behaviour of Ctrl-R:
-- Most computers in most operating systems, languages (including French until
recently), desktops... have two identical Ctrl keys. It is queer to have French
keyboards doing otherwise since a few years.
-- Like having two
This bug is still present in package xkb-data 2.10.1ubuntu1 (trusty):
include level5(rctrl_switch)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1013881
Title:
Right-Ctrl key broken on French OSS
I am affected by this bug.
But the sound plays if in the home folder. This made me think that it is a
problem of white space in the path. Indeed may path was
~/Musique/Got mail
I also tried space in the file name. Thunderbird sound does not work. Otherwise
it does.
Conclusion: Thunderbird new
The above holds for a plain up to date Ubuntu (Ubuntu 12.04 and
Thunderbird 13.0.1)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/732572
Title:
New Mail Notification Sound does not play in Natty
There is a lot of variants of this bug with a lot of discussion about esound,
pulseaudio, libcanberra and whatever.
On a plain up do date Ubuntu (12.04, with Thunderbird 13.0.1) I observed this:
A notification wav does not work if either the path, either the
filename, contains a space. It does
Thanks to Emmanuel Castro for the workaround (forcing a previous version).
The choice w
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1013881
Title:
Right-Ctrl key broken on French OSS keyboard
To
Sorry, pushed some wrong key.
[The choice…] was between 2.5-1ubuntu1 (precise) and 2.5-1ubuntu2
(precise-proposed). On https://help.ubuntu.com/community/UbuntuUpdates,
I read: « Enabling the proposed updates repository can break your
system. It is not recommended for inexperienced users. » I
With Belgian OSS, I have the same Ctrl-R changed into Level5 as Emmanuel
Castro (his attached image 2012-06-16).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1013881
Title:
Right-Ctrl key broken
My device 14e4:4324 (rev 03) worked out of the box with 10.04 and 10.10.
The postinst of firmware-b43-installer in 12.04 considers it legacy (there is a
Fix for 14e4:4320 (rev 03) only).
But the device does work with the latest firmware. Executing the contents of
the function latest_firmware ()
b43-fwcutter seems to do the job when asked to
The problem seems to be with the postinst of firmware-b43-installer
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/979322
Title:
package
New install of 12.04
Using Gnome Classic (no effects)
In gconf-editor
/desktop/gnome/peripherals/keyboard/kbd/layouts = be oss
but the keyboard behaves like an ordinary be
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
12.04
keyboard pc105, be, oss
I tried (with gnome-control-center) different options supposed to give
non break space on level 3 but if I get some non break space, it is on
level 4
For the moment, I read in gconf editor:
/desktop/gnome/peripherals/keyboard/kbd/options : nbsp
Public bug reported:
Binary package hint: nautilus
Aparently Nautilus (2.26.2) does not support the FTPES protocol (Auth TLS) for
FTP.
I want to connect a ProFTPd 1.3.1 server with Auth TLS security. I cannot
connect with Nautilus. (Filezilla connects but with an error.) I do connect
with
In the case of ID 2001:f111 D-Link Corp. [hex] DBT-122 Bluetooth
adapter, it seems that it was not so much a kernel bug than a bluez bug:
It still does NOT work with kernel 2.6.29 and the regular Bluez 4.3x from the
Ubuntu distribution.
It DOES work OK with Bluez 4.40-2 from Debian.
--
I just did boot back in 2.6.28 (2.6.28-12-generic #43-Ubuntu SMP Fri May 1
19:27:06 UTC 2009 i686).
My D-Link DBT-122 (ID 2001:f111) works as expected. This confirms that, for
this dongle, Bluez 4.00 to 4.32 was the problem and Bluez 4.40 the solution,
not the kernel. (Mind the fact that there
For some dongles (as my D-Link DBT-122), there little or no kernel
problem, but a Bluez problem.
This is what I did concretely:
— display http://http.us.debian.org/debian/pool/main/b/bluez/
— click libbluetooth3_4.40-2_i386.deb and simply accept installation by GDebi
— idem with
No improvement with 2.6.29.
I read somewhere that the bug was fixed upstream with kernel 2.6.29. I
installed this kernel following www.ramoonus.nl/2009/03/24/linux-
kernel-2629-installation-guide-for-ubuntu-and-debian-linux/
I see no improvement:
uname -srvmo
Linux 2.6.29-020629-generic #020629
It does work with Bluez 4.40-2. So it seems that it was not so much a
kernel bug than a bluez bug.
Installed Bluez 4.40-2 from http://http.us.debian.org/debian/pool/main/b/bluez/
dpkg -l | grep blue
ii bluetooth 4.40-2
Bluetooth
I subscribed to the linux-blueto...@vger.kernel.org and posted essentially the
above information on 17-4-2009. There was absolutely no reaction.
I found that a user had opened 525220:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=525220 in the Debian Bug
Tracking System. I placed essentially
The original bug goes as follows:
Bluetooth doesn't work for at least the following devices:
ID 1131:1001 Integrated System Solution Corp. KY-BT100 Bluetooth Adapter
ID 1131:1004 Integrated System Solution Corp. Bluetooth Device
ID 2001:f111 D-Link Corp. [hex] DBT-122 Bluetooth adapter
ID
The D-Link DBT-122 USB dongle does not work with btusb and Bluez 4.xx.
lsusb
Bus 003 Device 002: ID 2001:f111 D-Link Corp. [hex] DBT-122 Bluetooth adapter
uname -a
Linux library 2.6.28-12-generic #43-Ubuntu SMP Fri May 1 19:27:06 UTC 2009 i686
GNU/Linux
dpkg -l | grep bluez
ii bluez
** Changed in: linux (Ubuntu Intrepid)
Status: Fix Committed = Confirmed
** Changed in: linux (Ubuntu Jaunty)
Status: Fix Released = Confirmed
** Changed in: linux (Ubuntu)
Status: Fix Released = Confirmed
--
Bluetooth doesn't work (hci_cmd_task: hci0 command tx timeout)
This has been marked fixed too early. For some dongles, there is absolutely no
improvement since to move from bluez 3.xx to 4.xx, there is always a command
tx timeout and Connection timed out (110).
The bug may have been fixed for some Integrated System devices, but obviously
not for some
Kernel bug NOT fixed
I read three weeks ago in the list linux-blueto...@vger.kernel.org somebody
patching btusb.c with
+ /* Integrated System Solution devices */
+ { USB_DEVICE(0x1131, 0x1004), .driver_info = BTUSB_WRONG_SCO_MTU },
+
I wonder if this explains that some Integrated
New flavor of the kernel this morning. The famous more than six month
regression hci0 command tx timeout is still there.
~$ uname -a
Linux library 2.6.28-12-generic #43-Ubuntu SMP Fri May 1 19:27:06 UTC 2009 i686
GNU/Linux
I insert my dongle
~$ lsusb | grep Blue
Bus 003 Device 002: ID 2001:f111
Mine still does not work. This is a regression form 8.04 over two
releases 8.10 and 9.04. I wonder why the Bluez bug (filed more than six
month ago) is still considered New (through two releases), importance
undecided (decidedly important to me) and unassigned (I am not able to
fix it myself!)
Got Bluez 4.35 just now. Just as broken as always since 4.xx.
hciconfig -a
hci0: Type: USB
BD Address: 00:13:46:00:55:A0 ACL MTU: 377:10 SCO MTU: 16:0
UP RUNNING
RX bytes:667 acl:0 sco:0 events:19 errors:0
TX bytes:327 acl:0 sco:0 commands:21 errors:0
Sorry that I had now time to test 4.33 when asked to. But I did install
4.33 somewhat later and I am now with 4.34 and experienced no crash any
more.
Of course crashing or not, it does not make much difference because it
is just as broken: the regression from 8.04 is still there. Bluez
definitely
@ Stiff
As you may see at the top of the page, this is a two-sided bug, with a kernel
side (btusb driver) and a Bluez side. The kernel side is said to be fixed. The
Bluez side is qualified as New and Undecided. As a result nobody seems to be
working on this any more (the Bluez side is not
I wonder why a functionality present in 8.04 and broken for the full duration
of 8.10 (regression) can be still Undecided and not assigned three weeks
before the launch of 9.04.
But I am not a developer and I do not know how such work is assigned in
Canonical and in the community. Is there a
Still no improvement. The bluetooth daemon seems to be incompatible with
btusb.
lsusb | grep D-Link
Bus 002 Device 003: ID 2001:f111 D-Link Corp. [hex] DBT-122 Bluetooth adapter
uname -a
Linux library 2.6.28-11-generic #39-Ubuntu SMP Thu Apr 2 03:00:35 UTC 2009 i686
GNU/Linux
sudo
No improvement with 4.34
---
uname -a : Linux library 2.6.28-11-generic #38-Ubuntu SMP Fri Mar 27 09:00:52
UTC 2009 i686 GNU/Linux
lsusb : Bus 002 Device 003: ID 2001:f111 D-Link Corp. [hex] DBT-122 Bluetooth
adapter
dpkg -l | grep blue* : ii bluetooth
@Ari
I thought better to keep things separated and that's why I opened bug #329828
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/329828. At that time, this
#268502 was registered as kernel bug only and I thought my problem was not
kernel (my post 2009-02-07 above).
But is seems that
Some Bluetooth dongles may have a kernel problem but others not. People
keep telling others to try new kernels and patch kernels. But for some
dongles, there is no kernel problem but a Bluez daemon problem. See my
test on 2009-03-18: with the daemon stopped, with btusb alone, my dongle
scans my
Once more. With bluez 4.32-0ubuntu3 today (2009-03-28 12:44:58 status
installed bluez 4.32-0ubuntu3).
--
bluetoothd crashed with SIGSEGV in calloc()
https://bugs.launchpad.net/bugs/337080
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Idem today
--
w3m crashed with SIGSEGV in memmove()
https://bugs.launchpad.net/bugs/286488
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.com
tracker-extract crashed with SIGSEGV
--
tracker-extract crashed with SIGSEGV in tracker_extract_get_metadata()
https://bugs.launchpad.net/bugs/331679
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Apport says once more: bluetoothd crashed with SIGSEGV in calloc()
Didn't find the time to look at the ppa yet. I am still with Bluez 4.32.
--
bluetoothd crashed with SIGSEGV in calloc()
https://bugs.launchpad.net/bugs/337080
You received this bug notification because you are a member of Ubuntu
Apport says: nautilus crashed with SIGSEGV in gconf_client_remove_dir()
--
nautilus crashed with SIGSEGV in gconf_client_remove_dir()
https://bugs.launchpad.net/bugs/182345
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Once more. At the beginning of a Gnome session, two hours ago also.
--
nautilus crashed with SIGSEGV in gconf_client_remove_dir()
https://bugs.launchpad.net/bugs/182345
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
The problem with the D-Link Corp. DBT-122 Bluetooth adapter (ID
2001:f111) may not be a kernel problem. I once (7-3-2009) had it working
(no timeout, could scan) with the btusb driver while the bluetoothd
daemon was stopped (of was it mere chance?) This would indicate a Bluez
bug, not a kernel bug
lsusb: Bus 002 Device 003: ID 2001:f111 D-Link Corp. [hex] DBT-122
Bluetooth adapter
uname -a:Linux library 2.6.28-11-generic #34b268502v1 SMP Wed Mar 18
15:32:17 UTC 2009 i686 GNU/Linux (patched kernel)
I stop the daemon, take the dongle out and back in. Bingo:
sudo hciconfig hci0 up
hciconfig
No improvement with Bluez 4.32
hciconfig -a
hci0: Type: USB
BD Address: 00:13:46:00:55:A0 ACL MTU: 377:10 SCO MTU: 16:0
UP RUNNING
RX bytes:667 acl:0 sco:0 events:19 errors:0
TX bytes:621 acl:0 sco:0 commands:29 errors:0
Features: 0xff 0xfe 0x0d 0x38
Jaunty, restart after an update just now. Got a message that Nautilus
crashed. Could open Nautilus normally.
--
nautilus crashed with SIGSEGV in gconf_client_remove_dir()
https://bugs.launchpad.net/bugs/182345
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I kept using vesa for one month. Today, after a big update, including
libdrm-intel1 2.4.5-0ubuntu1
xserver-xorg-video-intel 2:2.6.1-1ubuntu4
I gave intel a try and everything seems to work. At least, I go through
gdm :-)
--
[i945] Screen(s) found, but none have a usable configuration error on
This seems definitely more a Bluez bug than a kernel bug. (But of course the
kernel could be held responsible for the Bluez problems :-)
lsusb | grep tooth
Bus 001 Device 004: ID 2001:f111 D-Link Corp. [hex] DBT-122 Bluetooth adapter
uname -r
2.6.28-8-generic
dpkg -l blue*
ii bluetooth
Again
--
bluetoothd crashed with SIGSEGV in calloc()
https://bugs.launchpad.net/bugs/337080
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.com
** Attachment added: CoreDump.gz
http://launchpadlibrarian.net/23474689/CoreDump.gz
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/23474690/Dependencies.txt
** Attachment added: ProcMaps.txt
http://launchpadlibrarian.net/23474691/ProcMaps.txt
** Attachment added:
Public bug reported:
Binary package hint: gftp
Crashed during the upload of a long series (500) of html pages (2 KB)
and photos (20 à 200 KB) of a reasonable dimension
ProblemType: Crash
Architecture: i386
Disassembly: 0xb653a440:
DistroRelease: /usr/bin/lsb_release:81: DeprecationWarning: the
Public bug reported:
Binary package hint: python-gammu
Even with python 2.5 and python-all installed, the python-gammu (0.28-1)
package in jaunty does not install because it conflicts with python
2.6.1-0ubuntu9 included in jaunty.
(Jaunty up to date as of today)
** Affects: python-gammu
No more result with 4.30
Kernel : ~$ uname -r
2.6.28-8-generic
My device : ~$ lsusb |grep tooth
Bus 001 Device 003: ID 2001:f111 D-Link Corp. [hex] DBT-122 Bluetooth adapter
Bluez software : ~$ dpkg -l blue*
||/ NomVersionDescription
Public bug reported:
Binary package hint: bluez
Very soon after booting and entering a Gnome session, doing nothing
special yet.
ProblemType: Crash
Architecture: i386
DistroRelease: /usr/bin/lsb_release:81: DeprecationWarning: the sets module is
deprecated import sets Ubuntu 9.04
** Attachment added: CoreDump.gz
http://launchpadlibrarian.net/23337856/CoreDump.gz
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/23337857/Dependencies.txt
** Attachment added: Disassembly.txt
http://launchpadlibrarian.net/23337858/Disassembly.txt
** Attachment
** Attachment added: CoreDump.gz
http://launchpadlibrarian.net/23084082/CoreDump.gz
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/23084083/Dependencies.txt
** Attachment added: Disassembly.txt
http://launchpadlibrarian.net/23084084/Disassembly.txt
** Attachment
I never used w3m in my life. I wonder why it was running.
** Attachment added: _usr_bin_w3m.1000.crash
http://launchpadlibrarian.net/22934632/_usr_bin_w3m.1000.crash
--
w3m crashed with SIGSEGV in memmove()
https://bugs.launchpad.net/bugs/286488
You received this bug notification because you
*** This bug is a duplicate of bug 131868 ***
https://bugs.launchpad.net/bugs/131868
** Attachment added: CoreDump.gz
http://launchpadlibrarian.net/22865484/CoreDump.gz
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/22865485/Dependencies.txt
** Attachment added:
** Attachment added: CoreDump.gz
http://launchpadlibrarian.net/22865651/CoreDump.gz
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/22865652/Dependencies.txt
** Attachment added: Disassembly.txt
http://launchpadlibrarian.net/22865653/Disassembly.txt
** Attachment
Using Intel 945G as hardware,
lspci
00:02.0 VGA compatible controller: Intel Corporation 82945G/GZ Integrated
Graphics Controller (rev 02)
but as vesa because of a bug in xorg-intel.
Gdmgreeter problem solved for me after upgrade a few minutes ago.
--
gdmgreeter crashed with SIGSEGV in
Firefox crashed when I attempted to close a Firefox window.
** Attachment added: _usr_lib_firefox-3.0.6_firefox.1000.crash
http://launchpadlibrarian.net/22704870/_usr_lib_firefox-3.0.6_firefox.1000.crash
--
firefox crashed with SIGSEGV
https://bugs.launchpad.net/bugs/213484
You received
This time bluetoothd crashed at the beginning of a gnome session, doing
nothing. (I was opening Firefox to Google for more information on how to
have Bluetooth working :-)
** Visibility changed to: Public
--
bluetoothd crashed using gnome bluetooth
https://bugs.launchpad.net/bugs/329676
You
Public bug reported:
Binary package hint: bluetooth
I suspect this is a bluetooth/bluez/bluetoothd bug, NOT a kernel bug
because my Bluetooth adapter DOES work with kernel 2.6.28 and
bluetooth/bluez 3.xx hcid (see
https://bugs.launchpad.net/ubuntu/+bug/289836/comments/19 for Intrepid
with kernel
** Attachment added: daemon-bluetoothd-hcid.txt
http://launchpadlibrarian.net/22656852/daemon-bluetoothd-hcid.txt
--
Bluetooth/Bluez 4.xx unable to use some adapters
https://bugs.launchpad.net/bugs/329828
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Attachment added: CoreDump.gz
http://launchpadlibrarian.net/22657310/CoreDump.gz
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/22657312/Dependencies.txt
** Attachment added: ProcMaps.txt
http://launchpadlibrarian.net/22657313/ProcMaps.txt
** Attachment added:
Public bug reported:
Binary package hint: xserver-xorg-video-intel
New installation of Jaunty: lsb_release -rd
Description:Ubuntu jaunty (development branch)
Release:9.04
After the progress bar with Ubuntu logo showing correctly, I get the gdm
sound and a black screen. Ctrl+Alt+F1
** Attachment added: failsafeX-backup-090210085536.tar
http://launchpadlibrarian.net/22531495/failsafeX-backup-090210085536.tar
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/22531496/Dependencies.txt
** Attachment added: LsHal.txt
After upgrading from Ubuntu 8.10, upon restart I got after the
progression bar with Ubuntu logo a black (blueish) screen for gdm (with
usual sound). Ctrl+Alt+F1 seemed to do something, but with the same
screen. At least Ctrl+Alt+Del would restart the system. Choosing 2.6.27
in grub didn't make a
Video is Intel 945G. (Full lspci -vvnn attached)
00:02.0 VGA compatible controller [0300]: Intel Corporation 82945G/GZ
Integrated Graphics Controller [8086:2772] (rev 02)
Subsystem: ASUSTeK Computer Inc. Device [1043:817a]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV-
I came here seeing a warning about Intel under
http://www.ubuntu.com/testing/jaunty/alpha4#Known%20Issues but I realise that
my problem (above) has little to do with this bug. (I do not get Fatal server
error: Couldn't bind memory for BO front buffer.) Should I file this as
another bug?
I keep
Running Jaunty since this morning (in Belgium, winter, UTC+1). Let's see
for Klondike.
--
crash/freeze playing Klondike Solitaire, calling ExaCheckPutImage+0x103
https://bugs.launchpad.net/bugs/298483
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
1. I do use a D-Link DBT-122 Bluetooth adapter with kernel 2.6.27
=
Kernel: uname -r
2.6.27-11-generic
Bluetooth dongle: lsusb
Bus 001 Device 006: ID 2001:f111 D-Link Corp. [hex] DBT-122 Bluetooth adapter
Bluetooth software: dpkg --get-selections | grep blue
Bryce Harrington a écrit ce qui suit, le 05/02/09 06:19 :
Dominique, upstream would like you to test against the current (2.6.x)
driver. The best way to test this is to download an ISO image of
jaunty, which you can do at http://cdimages.ubuntu.com/releases/jaunty/,
burn to CD, boot, and
In the post above, I meant Debian unstable (some people do use
unstable).
--
crash/freeze playing Klondike Solitaire, calling ExaCheckPutImage+0x103
https://bugs.launchpad.net/bugs/298483
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This is not a guest only issue.
I have the same problem with the main user in a fresh installation (8.10
from Alternate CD, nothing special). I thought I had made a mistake,
maybe in my own partitioning scheme. Thus the third time I let the
installer take the whole disk (/ and swap). The result
Same information at the same time in /va/log/gdm/:0.log.1
** Attachment added: :0.log.1
http://launchpadlibrarian.net/21860327/%3A0.log.1
--
crash/freeze playing Klondike Solitaire, calling ExaCheckPutImage+0x103
https://bugs.launchpad.net/bugs/298483
You received this bug notification
Playing Klondike in Solitaire Aisleriot. Froze while dragging a card.
That card had two images (was shown in two slightly different positions
of the movement).
Xorg didn't crash but everything froze but the mouse pointer. No menu,
no clicking, no Ctrl+Alt+F1. Reset.
Nothing in /var/crash. I
Indeed in my case it is not a guest issue.
Indeed it is very serious to have a system systematically freeze on login from
the installation.
But these auth.log error message have nothing to do with it: I realise
that I have just the same auth.log on my regular machine working
perfectly. My
Just in case... the game software is AisleRiot, now 2.24.1.1. I play only the
Klondike game and I do very often to release the stress after some big work,
certainly once a day at least. But it doesn't make X freeze or crash very
often: see dates above, sometimes twice the same day, sometimes
Didn't last two month. Again playing Klondike. No other user program
running. Everything froze while dragging a card. The screen didn't
disappear or go into low graphics, just froze. Only the mouse pointer
moved (a hand, because frozen while dragging). Nothing else would
happen, no way to stop the
1 - 100 of 137 matches
Mail list logo
