[Bug 1811072] [NEW] df locks up with 100% cpu with zfs on usb, df unkillable
Public bug reported: Last reproduced with linux-image-generic-hwe-18.04-edge 4.18.0.13.62 on bionic with cpu AMD Ryzen 7 1700 Eight-Core Processor external usb hdd drive /dev/disk/by-id/usb-WD_My_Passport_0820_5758353x:0-part1 luks encrypted partition zfs pool zfs pool used only for backups using syncoid initially after zpool import -a `df -h` works 30 minutes later `df -h` hangs, doesn't print any output at all, probably after a zfs receive df process using 100% cpu kill -KILL has no change in df process, it doesn't die, it's still in R and using 100% cpu strace -p hangs, doesn't print any output, also can't be killed unplugging the usb doesn't have any effect, df still in R at 100% cpu reproducible, happens every time. I can't reproduce with kernel 4.15.0-43-generic. ** Affects: linux-meta-hwe-edge (Ubuntu) Importance: Undecided Status: New ** Description changed: - Last reproduced with linux-image-generic-hwe-18.04-edge 4.18.0.13.62 + Last reproduced with linux-image-generic-hwe-18.04-edge 4.18.0.13.62 on + bionic external usb hdd drive /dev/disk/by-id/usb-WD_My_Passport_0820_5758353x:0-part1 luks encrypted partition zfs pool zfs pool used only for backups using syncoid - initially after zpool import -a `df -h` works + initially after zpool import -a `df -h` works 30 minutes later `df -h` hangs, doesn't print any output at all, probably after a zfs receive df process using 100% cpu kill -KILL has no change in df process, it doesn't die, it's still in R and using 100% cpu strace -p hangs, doesn't print any output, also can't be killed reproducible, happens every time. I can't reproduce with kernel 4.15.0-43-generic. ** Description changed: Last reproduced with linux-image-generic-hwe-18.04-edge 4.18.0.13.62 on bionic external usb hdd drive /dev/disk/by-id/usb-WD_My_Passport_0820_5758353x:0-part1 luks encrypted partition zfs pool zfs pool used only for backups using syncoid initially after zpool import -a `df -h` works 30 minutes later `df -h` hangs, doesn't print any output at all, probably after a zfs receive df process using 100% cpu kill -KILL has no change in df process, it doesn't die, it's still in R and using 100% cpu strace -p hangs, doesn't print any output, also can't be killed + unplugging the usb doesn't have any effect, df still in R at 100% cpu reproducible, happens every time. I can't reproduce with kernel 4.15.0-43-generic. ** Description changed: Last reproduced with linux-image-generic-hwe-18.04-edge 4.18.0.13.62 on - bionic + bionic with cpu AMD Ryzen 7 1700 Eight-Core Processor external usb hdd drive /dev/disk/by-id/usb-WD_My_Passport_0820_5758353x:0-part1 luks encrypted partition zfs pool zfs pool used only for backups using syncoid initially after zpool import -a `df -h` works 30 minutes later `df -h` hangs, doesn't print any output at all, probably after a zfs receive df process using 100% cpu kill -KILL has no change in df process, it doesn't die, it's still in R and using 100% cpu strace -p hangs, doesn't print any output, also can't be killed unplugging the usb doesn't have any effect, df still in R at 100% cpu reproducible, happens every time. I can't reproduce with kernel 4.15.0-43-generic. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811072 Title: df locks up with 100% cpu with zfs on usb, df unkillable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-edge/+bug/1811072/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1799849] [NEW] segfault when starting new session
Public bug reported: Description:KDE neon User Edition 5.14 Release:18.04 (but also happens on fres install of ubuntu 18.04) Application: x2goclient (x2goclient), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7ff0f2520cc0 (LWP 4264))] Thread 4 (Thread 0x7ff0c4e36700 (LWP 4272)): [KCrash Handler] #6 0x7ff0f2105f1f in ?? () from /usr/lib/x86_64-linux-gnu/libssh.so.4 #7 0x7ff0f210720a in ?? () from /usr/lib/x86_64-linux-gnu/libssh.so.4 #8 0x7ff0f20f1903 in ssh_channel_poll () from /usr/lib/x86_64-linux-gnu/libssh.so.4 #9 0x5640f90836e1 in ?? () #10 0x5640f9087b6f in ?? () #11 0x7ff0ef672adb in QThreadPrivate::start (arg=0x5640fa26f650) at thread/qthread_unix.cpp:367 #12 0x7ff0ef3ab6db in start_thread (arg=0x7ff0c4e36700) at pthread_create.c:463 #13 0x7ff0eeb3388f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7ff0d2215700 (LWP 4267)): #0 0x7ff0eb0527d9 in g_main_context_prepare () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7ff0eb05336b in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7ff0eb05354c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7ff0ef89853b in QEventDispatcherGlib::processEvents (this=0x7ff0cc000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #4 0x7ff0ef83c7fa in QEventLoop::exec (this=this@entry=0x7ff0d2214d30, flags=..., flags@entry=...) at kernel/qeventloop.cpp:214 #5 0x7ff0ef667bba in QThread::exec (this=) at thread/qthread.cpp:525 #6 0x7ff0e3085e45 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7ff0ef672adb in QThreadPrivate::start (arg=0x7ff0e32fdd60) at thread/qthread_unix.cpp:367 #8 0x7ff0ef3ab6db in start_thread (arg=0x7ff0d2215700) at pthread_create.c:463 #9 0x7ff0eeb3388f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7ff0e0135700 (LWP 4266)): #0 0x7ff0eeb26bf9 in __GI___poll (fds=0x7ff0e0134c68, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7ff0ec968747 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7ff0ec96a36a in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7ff0e3587ed9 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7ff0ef672adb in QThreadPrivate::start (arg=0x5640f9e02f70) at thread/qthread_unix.cpp:367 #5 0x7ff0ef3ab6db in start_thread (arg=0x7ff0e0135700) at pthread_create.c:463 #6 0x7ff0eeb3388f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7ff0f2520cc0 (LWP 4264)): #0 0x7ff0ef3b19f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x7ffc5008e2a8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x5640f9df8898, cond=0x7ffc5008e280) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x7ffc5008e280, mutex=0x5640f9df8898) at pthread_cond_wait.c:655 #3 0x7ff0ec968952 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #4 0x7ff0ec96a06f in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #5 0x7ff0ec96a1ef in xcb_wait_for_reply64 () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #6 0x7ff0f17046a8 in _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6 #7 0x7ff0f16fb092 in XQueryTree () from /usr/lib/x86_64-linux-gnu/libX11.so.6 #8 0x5640f901f7e4 in ?? () #9 0x5640f901fb28 in ?? () #10 0x5640f905812e in ?? () #11 0x5640f90e169c in ?? () #12 0x7ff0ef86d565 in QMetaObject::activate (sender=sender@entry=0x5640f9febd10, signalOffset=, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffc5008e730) at kernel/qobject.cpp:3771 #13 0x7ff0ef86dc37 in QMetaObject::activate (sender=sender@entry=0x5640f9febd10, m=m@entry=0x7ff0efcc2da0 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffc5008e730) at kernel/qobject.cpp:3633 #14 0x7ff0ef87a337 in QTimer::timeout (this=this@entry=0x5640f9febd10, _t1=...) at .moc/moc_qtimer.cpp:200 #15 0x7ff0ef87a698 in QTimer::timerEvent (this=0x5640f9febd10, e=) at kernel/qtimer.cpp:255 #16 0x7ff0ef86e08b in QObject::event (this=0x5640f9febd10, e=) at kernel/qobject.cpp:1273 #17 0x7ff0f0b64e1c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #18 0x7ff0f0b6c3ef in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #19 0x7ff0ef83e4d8 in QCoreApplication::notifyInternal2 (receiver=0x5640f9febd10, event=event@entry=0x7ffc5008ea30) at kernel/qcoreapplication.cpp:1048 #20 0x7ff0ef8979ae in QCoreApplication::sendEvent (event=0x7ffc5008ea30, receiver=) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:234 #21 QTimerInfoList::activateTimers (this=0x5640f9e42950) at
[Bug 1779597] [NEW] [Satellite P55W-C, Realtek ALC233, Speaker, Internal] Pulseaudio fails to detect card
Public bug reported: It's related to a JBL Flip 2 bluetooth speaker. It worked perfectly in 16.04, in 18.04 the bluetooth speaker doesn't reconnect after a laptop suspend/resume cycle, I need to delete it from the bluetooth paired devices and repair it. Often the output sound device is missing, it only shows dummy. If I suspend while the bluetooth speaker is connected it's garanteed to disappear, but it sometimes disappears after I turn off the bluetooth speaker without suspending. Rebooting restores the output sound device and the internal speaker starts working again. I'm happy to provide further info and do some testing. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.1 Uname: Linux 4.17.3-041703-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jul 2 13:53:42 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2016-06-21 (740 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel PCH Symptom_Jack: Speaker, Internal Title: [Satellite P55W-C, Realtek ALC233, Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: Upgraded to bionic on 2018-03-17 (106 days ago) dmi.bios.date: 07/26/2015 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.00 dmi.board.name: 0693 dmi.board.vendor: FF40 dmi.board.version: 2.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis ManuFacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr1.00:bd07/26/2015:svnTOSHIBA:pnSatelliteP55W-C:pvrPSPVTU-004001B:rvnFF40:rn0693:rvr2.0:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion: dmi.product.family: PEGA Family dmi.product.name: Satellite P55W-C dmi.product.version: PSPVTU-004001B dmi.sys.vendor: TOSHIBA ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1779597 Title: [Satellite P55W-C, Realtek ALC233, Speaker, Internal] Pulseaudio fails to detect card To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1779597/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779597] Re: [Satellite P55W-C, Realtek ALC233, Speaker, Internal] Pulseaudio fails to detect card
Oh, and I upgraded the kernel with ukuu, it also happens with the kernel in 18.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1779597 Title: [Satellite P55W-C, Realtek ALC233, Speaker, Internal] Pulseaudio fails to detect card To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1779597/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1563146] Re: lockup when using DVI and display port with skylake
It locked up with 4.4.0-040400-generic I'll try the latest one which looks like will be 4.6.0-040600rc1 I just had an X crash with a single dvi monitor just now triggered by logging out from an nx session I think that one is an intel video driver bug. I have no idea if the hard lockup is also a intel video driver bug. [ 83243.377] (EE) [ 83243.377] (EE) Backtrace: [ 83243.377] (EE) 0: /usr/bin/X (xorg_backtrace+0x4e) [0x564984a8f68e] [ 83243.378] (EE) 1: /usr/bin/X (0x5649848db000+0x1b89f9) [0x564984a939f9] [ 83243.378] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7fcb1ec7e000+0x352f0) [0x7fcb1ecb32f0] [ 83243.378] (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (0x7fcb1ec7e000+0x7f16b) [0x7fcb1ecfd16b] [ 83243.378] (EE) 4: /lib/x86_64-linux-gnu/libc.so.6 (0x7fcb1ec7e000+0x80eb8) [0x7fcb1ecfeeb8] [ 83243.378] (EE) 5: /lib/x86_64-linux-gnu/libc.so.6 (cfree+0x4c) [0x7fcb1ed0283c] [ 83243.378] (EE) 6: /usr/bin/X (0x5649848db000+0x1b4a88) [0x564984a8fa88] [ 83243.378] (EE) 7: /usr/bin/X (CloseDownClient+0x11a) [0x5649849326ea] [ 83243.378] (EE) 8: /usr/bin/X (0x5649848db000+0x57fe9) [0x564984932fe9] [ 83243.378] (EE) 9: /usr/bin/X (0x5649848db000+0x5c34b) [0x56498493734b] [ 83243.378] (EE) 10: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) [0x7fcb1ec9ea40] [ 83243.378] (EE) 11: /usr/bin/X (_start+0x29) [0x5649849216c9] [ 83243.378] (EE) [ 83243.378] (EE) Segmentation fault at address 0x0 [ 83243.378] (EE) Fatal server error: [ 83243.378] (EE) Caught signal 11 (Segmentation fault). Server aborting [ 83243.378] (EE) [ 83243.378] (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. [ 83243.378] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. [ 83243.378] (EE) [ 83243.378] (II) AIGLX: Suspending AIGLX clients for VT switch [ 83243.410] (EE) Server terminated with error (1). Closing log file. On Wed, Mar 30, 2016 at 5:53 AM, Joseph Salisbury < joseph.salisb...@canonical.com> wrote: > Did this issue start happening after an update/upgrade? Was there a > prior kernel version where you were not having this particular problem? > > Would it be possible for you to test the latest upstream kernel? Refer > to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest > v4.6 kernel[0]. > > If this bug is fixed in the mainline kernel, please add the following > tag 'kernel-fixed-upstream'. > > If the mainline kernel does not fix this bug, please add the tag: > 'kernel-bug-exists-upstream'. > > Once testing of the upstream kernel is complete, please mark this bug as > "Confirmed". > > > Thanks in advance. > > [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-rc1-wily/ > > ** Changed in: linux (Ubuntu) >Importance: Undecided => Medium > > ** Tags added: kernel-da-key > > ** Changed in: linux (Ubuntu) >Status: Confirmed => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1563146 > > Title: > lockup when using DVI and display port with skylake > > Status in linux package in Ubuntu: > Incomplete > > Bug description: > When using dual monitors, one connected to the dvi port, and one > connected to the display port, > and when nxclient 3.5.0-7 is running, the kernel will lock up about once > a day, sometimes more often. > > after it has locked up, the mouse cursor doesn't move, caps lock doesn't > toggle the keyboard light, the pc can't be pinged, > there is nothing written in the logs about the crash. > > If nxclient isn't running, it doesn't lock up. I don't think it has > locked up since switching to vga and dvi. > > I believe this is a skylake problem. I'm able to help test and debug > if required and given instructions. > > ProblemType: Bug > DistroRelease: Ubuntu 15.10 > Package: linux-image-4.2.0-34-generic 4.2.0-34.39 > ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4 > Uname: Linux 4.2.0-34-generic x86_64 > ApportVersion: 2.19.1-0ubuntu5 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC0: michael1805 F pulseaudio > CurrentDesktop: GNOME > Date: Tue Mar 29 12:26:58 2016 > HibernationDevice: RESUME=UUID=d420eadc-7df8-467a-a6f6-f8e02376eb4a > InstallationDate: Installed on 2016-01-12 (76 days ago) > InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 > (20151021) > IwConfig: >enp3s0no wireless extensions. > >lono wireless extensions. > Lsusb: >Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub >Bus 001 Device 003: ID 046d:c31c Logitech, Inc. Keyboard K120 >Bus 001 Device 004: ID 046d:c03d Logitech, Inc. M-BT96a Pilot Optical > Mouse >Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > MachineType: System manufacturer System Product Name > ProcFB: 0 inteldrmfb > ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-34-generic >
[Bug 1563146] [NEW] lockup when using DVI and display port with skylake
Public bug reported: When using dual monitors, one connected to the dvi port, and one connected to the display port, and when nxclient 3.5.0-7 is running, the kernel will lock up about once a day, sometimes more often. after it has locked up, the mouse cursor doesn't move, caps lock doesn't toggle the keyboard light, the pc can't be pinged, there is nothing written in the logs about the crash. If nxclient isn't running, it doesn't lock up. I don't think it has locked up since switching to vga and dvi. I believe this is a skylake problem. I'm able to help test and debug if required and given instructions. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-34-generic 4.2.0-34.39 ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4 Uname: Linux 4.2.0-34-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michael1805 F pulseaudio CurrentDesktop: GNOME Date: Tue Mar 29 12:26:58 2016 HibernationDevice: RESUME=UUID=d420eadc-7df8-467a-a6f6-f8e02376eb4a InstallationDate: Installed on 2016-01-12 (76 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) IwConfig: enp3s0no wireless extensions. lono wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c31c Logitech, Inc. Keyboard K120 Bus 001 Device 004: ID 046d:c03d Logitech, Inc. M-BT96a Pilot Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer System Product Name ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-34-generic root=/dev/mapper/ubuntu--vg-root ro i915.preliminary_hw_support=1 i915.ips=0 quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-34-generic N/A linux-backports-modules-4.2.0-34-generic N/A linux-firmware1.149.3 RfKill: SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/16/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0902 dmi.board.asset.tag: Default string dmi.board.name: H170M-E D3 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0902:bd11/16/2015:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH170M-ED3:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wily -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1563146 Title: lockup when using DVI and display port with skylake To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1563146/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63184] Re: ethernet with dhcp
Hello, thanks for your bug report. How long did you wait for an IP address? I think this bug might be a duplicate of bug 59926 Can you reboot without a link, bring the link up and wait 10 minutes? ** Changed in: Ubuntu Sourcepackagename: None = dhcp3 Status: Unconfirmed = Needs Info -- ethernet with dhcp https://launchpad.net/bugs/63184 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 61733] Re: rhythmbox will not copy files with certain chars in their name to playlists
Hi thanks for your bug report. Are you running dapper? This looks like bug #37115 ** Changed in: rhythmbox (Ubuntu) Status: Unconfirmed = Needs Info -- rhythmbox will not copy files with certain chars in their name to playlists https://launchpad.net/bugs/61733 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 61733] Re: rhythmbox will not copy files with certain chars in their name to playlists
*** This bug is a duplicate of bug 37115 *** Thanks Jeff, yeah, the gnome bug report didn't mention other special characters, but I believe the fix included them. Please reopen if you still have this problem when you update to edgy. ** This bug has been marked a duplicate of bug 37115 rhythmbox can't add a file with '' to a playlist ** Changed in: rhythmbox (Ubuntu) Status: Needs Info = Rejected -- rhythmbox will not copy files with certain chars in their name to playlists https://launchpad.net/bugs/61733 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 60807] Re: no discharging icon if booted from battery
*** This bug is a duplicate of bug 36129 *** ** This bug has been marked a duplicate of bug 36129 Battery discharging notification icon invisible when starting with AC disconnected -- no discharging icon if booted from battery https://launchpad.net/bugs/60807 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 36129] Re: Battery discharging notification icon invisible when starting with AC disconnected
** Bug 60807 has been marked a duplicate of this bug -- Battery discharging notification icon invisible when starting with AC disconnected https://launchpad.net/bugs/36129 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 60807] Re: no discharging icon if booted from battery
*** This bug is a duplicate of bug 36129 *** I think $display_icon_policy is correct. Also battery.rechargeable.is_discharging = true (bool) battery.rechargeable.is_charging = false (bool) looks OK, same as in bug 36129, so I'll mark it as a dup, you can track its progress over there. Thanks for the the bug report. ** Changed in: gnome-power-manager (Ubuntu) Status: Needs Info = Rejected -- no discharging icon if booted from battery https://launchpad.net/bugs/60807 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 61175] Re: edgy: closing laptop screen ends my session (should give blanck screen)
Hello, lid closing works fine for me. What model laptop do you have, and what about killing gnome-power-manager and starting it like gnome-power-manager --verbose --no-daemon /tmp/out 21 then close the lid, does it log you out? can you attach /tmp/out? ** Changed in: Ubuntu Sourcepackagename: None = gnome-power-manager -- edgy: closing laptop screen ends my session (should give blanck screen) https://launchpad.net/bugs/61175 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 60807] Re: no discharging icon if booted from battery
Hi, thanks for your bug report. Please boot from battery, and check gnome-power-manager is running (ps aux|grep gnome-power-manager), and attach the output of lshal and gconftool-2 -R /apps/gnome-power-manager I think this is likely the same bug as bug #36129 ** Changed in: gnome-power-manager (Ubuntu) Status: Unconfirmed = Needs Info -- no discharging icon if booted from battery https://launchpad.net/bugs/60807 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 60662] Re: does not save gateway details
*** This bug is a duplicate of bug 59690 *** Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. ** Changed in: Ubuntu Status: Unconfirmed = Rejected ** This bug has been marked a duplicate of bug 59690 Static IP configuration doesn't adds the default route to the gateway -- does not save gateway details https://launchpad.net/bugs/60662 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 59690] Re: Static IP configuration doesn't adds the default route to the gateway
** Bug 60662 has been marked a duplicate of this bug -- Static IP configuration doesn't adds the default route to the gateway https://launchpad.net/bugs/59690 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 59882] Re: Access to remote SSH server does not distinguish the connection by port
Hello, I tried testing that here, and I also had problems. I think the problem is with remote host identification. ie, if you try to connect to the servers using ssh from the command line, like ssh -p 2201 192.168.2.1 and ssh -p 2202 192.168.2.1, one command will work, the other will fail with an error message like WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! One solution would be to add two ip addresses to the gateway, 192.168.2.10 and 192.168.2.20 one for each remote ssh server, and use DNAT. 192.168.2.10 - 192.168.1.10 192.168.2.20 - 192.168.1.20 -- Access to remote SSH server does not distinguish the connection by port https://launchpad.net/bugs/59882 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 59211] Re: Blam doesn't start since Mono update (Edgy)
That patch worked for me, thanks. But i had to manually install cli- common-dev to get the file dh_clideps, build-deps didn't suck it down. -- Blam doesn't start since Mono update (Edgy) https://launchpad.net/bugs/59211 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 59895] Re: Updating Kernel modified Grub doesn't respect customised entries
I think the problem is everything between the lines ### BEGIN AUTOMAGIC KERNELS LIST and ### END DEBIAN AUTOMAGIC KERNELS LIST gets auto regenerated when a new kernel is installed, and update-grub is run. see bug 21412 and bug 2646. What happens if you copy the windows entry above ### BEGIN AUTOMAGIC KERNELS LIST and run sudo update-grub ? ** Changed in: grub (Ubuntu) Status: Unconfirmed = Needs Info -- Updating Kernel modified Grub doesn't respect customised entries https://launchpad.net/bugs/59895 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 59905] Re: RhythmBox crashes when a connected DAAP share is put to sleep
This looks like http://bugzilla.gnome.org/show_bug.cgi?id=352927 -- RhythmBox crashes when a connected DAAP share is put to sleep https://launchpad.net/bugs/59905 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 21412] Re: Default update-grub behaviour is not intuitive with respect to user modifications
** Bug 59895 has been marked a duplicate of this bug -- Default update-grub behaviour is not intuitive with respect to user modifications https://launchpad.net/bugs/21412 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 59895] Re: Updating Kernel modified Grub doesn't respect customised entries
*** This bug is a duplicate of bug 21412 *** I've marked it as a dup of bug 21412. You might want to add a comment to that bug? ** This bug has been marked a duplicate of bug 21412 Default update-grub behaviour is not intuitive with respect to user modifications -- Updating Kernel modified Grub doesn't respect customised entries https://launchpad.net/bugs/59895 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
