I have a way of reproducing dolphin crash in Beta 2
1. open dolphin
choose view->decrease several times
in my system this produces crash repeatedly
(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbo
As vmware open-sourced vmware-tools we can close this bug.
--
vmware tools install fails
https://bugs.launchpad.net/bugs/80645
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.co
It does not work in gutsy either
--
pinnacle pctv 110i remote does not work in feisty
https://bugs.launchpad.net/bugs/122494
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
https:
I think I encountered something similar
--
totem-gstreamer crashed with SIGSEGV in g_object_set_valist()
https://bugs.launchpad.net/bugs/189574
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@list
I'll try with tribe-5 tomorrow.
--
nv driver - widescreen not recoginzed Asus A8Jn
https://bugs.launchpad.net/bugs/127529
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
ht
O course adding "1280x800" in xorg.conf is a work around, but it does
not a valid bug solution. Screen resolution should be determined at
live-cd startup and should not require manual xorg.conf editing.
--
nv driver - widescreen not recoginzed Asus A8Jn
https://bugs.launchpad.net/bugs/127529
You
Public bug reported:
(gusty - tribe 3)
As in summary, wireless card is not detected. Driver is not loaded. ifconfig
and iwconfig shows nothing
It worked fine in 6.10 and 7.04
** Affects: Ubuntu
Importance: Undecided
Status: New
--
Intel 3945 wireless card not detected on Asus A9
The same situation with my Asus A8Js - no sound card detected in gutsy
--
No sound card in Gutsy with D630
https://bugs.launchpad.net/bugs/124590
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-b
Public bug reported:
Binary package hint: xorg
Gutsy - tribe 3
Widescreen screen is not recognized after cd-boot. I am left with 1024x768 max
resolution, and there is no way to change it.
Asus A8Js - Nvidia 7300 and 1280x800 screen.
It never worked in Ubuntu, so probably won't work now either
Please close that report.
False alarm. At the second boot card is detected. Maybe It was just accident at
the first time.
I wonder why it didn't for for the first time.
--
Intel 3945 wireless card not detected on Asus A9Js
https://bugs.launchpad.net/bugs/127526
You received this bug notification
** Attachment added: "xorg.conf"
http://launchpadlibrarian.net/8545412/xorg.conf
--
nv driver - widescreen not recoginzed Asus A8Jn
https://bugs.launchpad.net/bugs/127529
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubu
** Attachment added: "Xorg.0.log"
http://launchpadlibrarian.net/8545414/Xorg.0.log
--
nv driver - widescreen not recoginzed Asus A8Jn
https://bugs.launchpad.net/bugs/127529
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
u
I also notice very high cpu usage during basic operations like moving
windows - top shows 60-70% cpu utilization
--
nv driver - widescreen not recoginzed Asus A8Jn
https://bugs.launchpad.net/bugs/127529
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
it is a typical laptop 1280x800 screen.
in Xorg.0.log it is recognized properly:
(--) NV(0): Panel size is 1280 x 800
(II) NV(0): Panel is LVDS
but somehow that information is ignored afterwards
--
nv driver - widescreen not recoginzed Asus A8Jn
https://bugs.launchpad.net/bugs/127529
You rec
I checked today with Tribe-5. It work's flawlessly! Thank you!.
** Changed in: xorg (Ubuntu)
Status: Incomplete => Fix Released
--
nv driver - widescreen not recoginzed Asus A8Jn
https://bugs.launchpad.net/bugs/127529
You received this bug notification because you are a member of Ubuntu
That problem is fixed in Gutsy, so I think it can be closed
--
r8169 driver does not detect link
https://bugs.launchpad.net/bugs/86798
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.u
I have checked today with Linux ali 2.6.20-15-generic (linux-
image-2.6.20-15-generic_2.6.20-15.27) and the bug is still present
--
r8169 driver does not detect link
https://bugs.launchpad.net/bugs/86798
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
Public bug reported:
feisty with all recent updates.
TV card pinnacle 110i (saa7134 module, card=77)
remote detected by kernel
dmesg:
41.065255] saa7130/34: v4l2 driver version 0.2.14 loaded
[ 41.065844] ACPI: PCI Interrupt Link [APC1] enabled at IRQ 16
[ 41.065856] ACPI: PCI Interrupt 00
ethtool:
before connecting cable:Settings for eth0:
Supported ports: [ TP ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Supports auto-negotiation: Yes
Adv
Public bug reported:
Binary package hint: beryl-core
Beryl with aquamarine as for 27.03
ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Tue Mar 27 21:33:52 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/bin/beryl
Package: beryl-core 0.2.1.dfsg+git20070318-0ubuntu2
PackageArchit
** Attachment added: "CoreDump.gz"
http://librarian.launchpad.net/7037173/CoreDump.gz
** Attachment added: "Dependencies.txt"
http://librarian.launchpad.net/7037174/Dependencies.txt
** Attachment added: "Disassembly.txt"
http://librarian.launchpad.net/7037175/Disassembly.txt
** Attachm
I confirm. Knetwork manager almost always crashes at first login. On
subsequent logins it works though.
--
knetworkmanager crashes on login
https://launchpad.net/bugs/94089
--
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
I can confirm this behaviour with Asus A8Jn laptop and kernel 2.6.20-11.
I'll post required information later.
--
Fan not activated on recover from hibernate
https://launchpad.net/bugs/93241
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubunt
Public bug reported:
In feisty asus_acpi is in version 0.30 which does not support many current
notebooks (ie popular A8J series)
please update to version 0.32
** Affects: Ubuntu
Importance: Undecided
Status: Unconfirmed
--
asus_acpi in old version, does not support notebooks
htt
uname -a
Linux ali 2.6.20-8-generic #2 SMP Tue Feb 13 05:18:42 UTC 2007 i686 GNU/Linux
** Attachment added: "dmesg"
http://librarian.launchpad.net/6466148/dmesg.log
--
asus_acpi in old version, does not support notebooks
https://launchpad.net/bugs/85407
--
ubuntu-bugs mailing list
ubuntu-b
lspci output
** Attachment added: "lspci-vvnn.log"
http://librarian.launchpad.net/6466149/lspci-vvnn.log
--
asus_acpi in old version, does not support notebooks
https://launchpad.net/bugs/85407
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinf
I attached required information.
My architecture is ubuntu-x86
Essential information:
in dmesg:
[ 76.976000] Asus Laptop ACPI Extras version 0.30
[ 76.976000] unsupported model A8JN, trying default values
[ 76.976000] send /proc/acpi/dsdt to the developers
I checked in acpi4asus.sf.net
Public bug reported:
Binary package hint: linux-source-2.6.20
You need system with r8169 card (Realtek Gigabit card)
1. start system with ethernet cable _disconnected_
2. connect ethernet cable
- system says no link detected - not true
To overcome this you have to
1) unload driver - rmmod r816
Public bug reported:
Binary package hint: ubiquity
I choose polish locale
Traceback (most recent call last):
File "/usr/bin/ubiquity", line 166, in ?
main()
File "/usr/bin/ubiquity", line 161, in main
install(sys.argv[1])
File "/usr/bin/ubiquity", line 57, in install
ret = wiza
This bug is not present in Kubuntu Fiesty 7.4 (12.01.2007 update)
--
Two "Manage Repositories" entries under different menus in Adept Manager
https://launchpad.net/bugs/74262
--
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
Sorry for previous post. The bug is of course present.
--
Two "Manage Repositories" entries under different menus in Adept Manager
https://launchpad.net/bugs/74262
--
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
Public bug reported:
Binary package hint: linux-386
Kubuntu fiesty 2 is installed in vmware server 1.01
after issuing "instal VM tools" command and nothing happens - kernel does not
see new device
** Affects: linux-meta (Ubuntu)
Importance: Undecided
Status: Unconfirmed
--
vmwar
I can confirm that bug with two different NVMe drivers - Samsung EVO970
and WD Black in 4.18.0-10-generic and in 4.15.0-20-generic kernels.
H270 Intel chipset on the motherboard
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
The same problem appears for me with 4.18.0-10-generic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1696422
Title:
Sudden Read Only File System
To manage notifications about this bug go to:
https:
Attachment contains error from dmesg output. For me reproduction steps
are: write large (>10G) amount of data to NVMe ssd.
** Attachment added: "nvme-heavy-write-error.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+attachment/5204874/+files/nvme-heavy-write-error.txt
--
Y
My Samsung is indeed [144d:a808]. I'll check WD later on - it's not connected
at this time.
I was not able to reproduce this bug using Clear Linux current kernel
(4.18.16-645).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
My Samsung is indeed [144d:a808]. I'll check WD later on - it's not connected
at this time.
I was not able to reproduce this bug using Clear Linux current kernel
(4.18.16-645).
I checked kernel https://people.canonical.com/~khfeng/lp1785715/ with no
nvme-core.default_ps_max_latency_us= settings
Then I'm puzzled. I'll retest later with WD.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1746340
Title:
Samsung SSD corruption (fsck needed)
To manage notifications about this bug go to:
https://
38 matches
Mail list logo
