[Bug 1727565] [NEW] package virtualbox 5.1.30-dfsg-1 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Terminated)
Public bug reported: I've installed 17.10 since beta, and apt usually gets stuck, sometimes con console-setup other times installing dkms modules or such. It just hangs and never returns. ProblemType: Package DistroRelease: Ubuntu 17.10 Package: virtualbox 5.1.30-dfsg-1 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 AptOrdering: flip:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Thu Oct 19 04:44:01 2017 ErrorMessage: subprocess installed post-installation script was killed by signal (Terminated) InstallationDate: Installed on 2017-09-04 (51 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170903) Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5 SourcePackage: virtualbox Title: package virtualbox 5.1.30-dfsg-1 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Terminated) UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: virtualbox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package artful third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1727565 Title: package virtualbox 5.1.30-dfsg-1 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Terminated) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1727565/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1715830] [NEW] plymouth --ping hangs, stalling dpkg configure
Public bug reported: Installed updates via apt, and it was getting stuck on keyboard- configuration. I started playing around with its postinst script and realized it was stuck on plymouth --ping (so I removes that line and had the script assume plymouth was present as it is). Now I find the same problem on console-setup-linux. Will fix doing the same thing, but now I'm sure this means that plymought has really frozen on my system. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: plymouth 0.9.2-3ubuntu16 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Sep 8 05:37:57 2017 DefaultPlymouth: /usr/share/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth InstallationDate: Installed on 2017-09-04 (4 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170903) MachineType: ASUSTeK COMPUTER INC. N56VZ ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-12-generic.efi.signed root=UUID=06d5f09c-095f-48b5-b863-9932af30cf73 ro quiet splash vt.handoff=7 ProcFB: 0 nouveaufb 1 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-12-generic.efi.signed root=UUID=06d5f09c-095f-48b5-b863-9932af30cf73 ro quiet splash vt.handoff=7 SourcePackage: plymouth TextPlymouth: /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N56VZ.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N56VZ dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN56VZ.204:bd05/11/2012:svnASUSTeKCOMPUTERINC.:pnN56VZ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN56VZ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: N dmi.product.name: N56VZ dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: plymouth (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1715830 Title: plymouth --ping hangs, stalling dpkg configure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1715830/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1283003] Re: [Bluetooth + 14.04] Bluetooth headsets are not working after last couple of updates
I suffer the same symptoms. Used it in 14.04 (Ubuntu GNOME over here) and stopped working (though I did change lots of PPAs). Device is detected, paired correctly but it won't show up in Preferences > Sound. Running 'paclt list cards short' (per #14) does not list this (only the built-in card), while in Preferences > Bluetooth device shows up as paired (and device responds accordingly). Weirdly, sometimes the toggle "Bluetooth" in Preferences > Bluetooth shows up as disabled, while the device acts like it is indeed paired (so it is enabled actually). I've also found this on /var/log/syslog: > Jun 20 20:10:51 valinor bluetoothd[20013]: Adapter /org/bluez/20013/hci0 has > been enabled > Jun 20 20:10:51 valinor bluetoothd[20013]: Unknown command complete for > opcode 19 > Jun 20 20:10:51 valinor bluetoothd[20013]: Endpoint registered: sender=:1.57 > path=/MediaEndpoint/HFPAG > Jun 20 20:10:51 valinor bluetoothd[20013]: Endpoint registered: sender=:1.57 > path=/MediaEndpoint/HFPHS > Jun 20 20:10:51 valinor bluetoothd[20013]: Endpoint registered: sender=:1.57 > path=/MediaEndpoint/A2DPSource > Jun 20 20:10:51 valinor bluetoothd[20013]: Endpoint registered: sender=:1.57 > path=/MediaEndpoint/A2DPSink > Jun 20 20:11:17 valinor bluetoothd[20013]: Adapter /org/bluez/20013/hci0 has > been disabled > Jun 20 20:11:17 valinor bluetoothd[20013]: Adapter /org/bluez/20013/hci0 has > been enabled > Jun 20 20:11:20 valinor bluetoothd[20013]: Discovery session 0x7f2e86c14df0 > with :1.149 activated > Jun 20 20:11:27 valinor bluetoothd[20013]: Unknown command complete for > opcode 37 > Jun 20 20:11:30 valinor bluetoothd[20013]: Stopping discovery > Jun 20 20:11:33 valinor bluetoothd[20013]: Badly formated or unrecognized > command: AT+CBC=63 > Jun 20 20:11:33 valinor bluetoothd[20013]: Badly formated or unrecognized > command: AT+BIA=0,0,1,1,1,1,0,` These last two lines look suspect, perhaps they're useful somehow. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1283003 Title: [Bluetooth + 14.04] Bluetooth headsets are not working after last couple of updates To manage notifications about this bug go to: https://bugs.launchpad.net/blueman/+bug/1283003/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 969290] Re: usb2 port stops working after resume from suspend
stuff in kern.log Oct 17 20:27:47 valinor kernel: [13507.329431] usb 3-4: new full-speed USB device number 94 using xhci_hcd Oct 17 20:28:05 valinor kernel: [13512.345363] xhci_hcd :00:14.0: Timeout while waiting for evaluate context command Oct 17 20:28:05 valinor kernel: [13525.178721] xhci_hcd :00:14.0: Stopped the command ring failed, maybe the host is dead Oct 17 20:28:05 valinor kernel: [13525.178732] xhci_hcd :00:14.0: Abort command ring failed Oct 17 20:28:05 valinor kernel: [13525.179085] xhci_hcd :00:14.0: HC died; cleaning up Oct 17 20:28:05 valinor kernel: [13525.179143] usb 3-4: device descriptor read/all, error -22 Oct 17 20:28:05 valinor kernel: [13525.179147] hub 3-0:1.0: cannot disable port 4 (err = -19) Oct 17 20:28:10 valinor kernel: [13530.177135] xhci_hcd :00:14.0: Timeout while waiting for a slot Oct 17 20:28:10 valinor kernel: [13530.177146] xhci_hcd :00:14.0: Abort the command ring, but the xHCI is dead. Oct 17 20:28:10 valinor kernel: [13530.177164] hub 3-0:1.0: cannot reset port 4 (err = -19) Oct 17 20:28:10 valinor kernel: [13530.177218] hub 3-0:1.0: cannot disable port 4 (err = -19) Oct 17 20:28:10 valinor kernel: [13530.177250] xHCI xhci_free_dev called with unaddressed device Oct 17 20:28:15 valinor kernel: [13535.177028] xhci_hcd :00:14.0: Timeout while waiting for a slot Oct 17 20:28:15 valinor kernel: [13535.177032] xhci_hcd :00:14.0: Abort the command ring, but the xHCI is dead. Oct 17 20:28:15 valinor kernel: [13535.177040] hub 3-0:1.0: cannot reset port 4 (err = -19) Oct 17 20:28:15 valinor kernel: [13535.177067] hub 3-0:1.0: cannot disable port 4 (err = -19) Oct 17 20:28:15 valinor kernel: [13535.177098] xHCI xhci_free_dev called with unaddressed device Oct 17 20:28:20 valinor kernel: [13540.177014] xhci_hcd :00:14.0: Timeout while waiting for a slot Oct 17 20:28:20 valinor kernel: [13540.177019] xhci_hcd :00:14.0: Abort the command ring, but the xHCI is dead. Oct 17 20:28:20 valinor kernel: [13540.177032] hub 3-0:1.0: cannot reset port 4 (err = -19) Oct 17 20:28:20 valinor kernel: [13540.177035] hub 3-0:1.0: cannot disable port 4 (err = -19) Oct 17 20:28:20 valinor kernel: [13540.177038] xHCI xhci_free_dev called with unaddressed device Oct 17 20:28:20 valinor kernel: [13540.177043] hub 3-0:1.0: unable to enumerate USB device on port 4 Oct 17 20:28:20 valinor kernel: [13540.177045] hub 3-0:1.0: cannot disable port 4 (err = -19) Oct 17 20:28:40 valinor kernel: [13559.900411] show_signal_msg: 69 callbacks suppressed Oct 17 20:28:40 valinor kernel: [13559.900419] Watchdog[3871]: segfault at 0 ip 7ff56c83cd7e sp 7ff560828560 error 6 in chromium-browser[7ff56bbca000+53e1000] Oct 17 20:33:02 valinor kernel: [13821.583687] hamachid[1752]: segfault at a4d200 ip 00a4d200 sp 7fff694d93b8 error 15 Oct 17 20:36:30 valinor kernel: [14030.132653] usbcore: deregistering interface driver usbhid Oct 17 20:36:30 valinor kernel: [14030.145903] usbcore: registered new interface driver usbhid Oct 17 20:36:30 valinor kernel: [14030.145906] usbhid: USB HID core driver -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/969290 Title: usb2 port stops working after resume from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/969290/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 969290] Re: usb2 port stops working after resume from suspend
This is happening to me. I'm on Raring, fairly updated (haven't updated in a few days, so will do so soon). This is an Asus N56VM (Ivy Bridge, with USB2 and USB3 ports, all of them stop working). This has happened twice, and it doesn't happen every time. Most of the time suspend works ok. Sometimes I need to force it as closing the lid won't do (something stopping it? I just do pm-suspend). I just tried doing "sudo modprobe -r usbhid ; sudo modprobe usbhid" and it didn't fix anything. Looks like the whole USB is frozen. Only weird thing I've got is I use GNOME Shell 3.8 (in fact sometimes, on resuming, the gnome-shell process gets stuck at D "Uninterruptible Wait" state, and there's no way to fix it, I can start a second Xorg but I end up rebooting soon anyway). A few months ago I had some issues when suspending with something plugged into the USB3 ports does not let it suspend (tries to suspend and gets awaken immediately, and it tries again, endlessly). I mentioned this stuff because perhaps it's all connected. Kernel is a standard one "Linux valinor 3.8.0-31-generic #46-Ubuntu SMP Tue Sep 10 20:03:44 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/969290 Title: usb2 port stops working after resume from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/969290/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 726814] Re: 0781:5406 udisks-daemon uses a ton of CPU after inserting a SanDisk U3 Cruzer Micro usb stick
*** This bug is a duplicate of bug 689593 *** https://bugs.launchpad.net/bugs/689593 ** This bug has been marked a duplicate of bug 689593 2x100% CPU and memory usage growth when performing partition modifications via udisks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/726814 Title: 0781:5406 udisks-daemon uses a ton of CPU after inserting a SanDisk U3 Cruzer Micro usb stick To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/726814/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1152907] Re: usb-creator-gtk raises error immediately after entering password on erase disk
*** This bug is a duplicate of bug 1160035 *** https://bugs.launchpad.net/bugs/1160035 looks like it's a dupe of https://bugs.launchpad.net/ubuntu/+source/usb- creator/+bug/559524 rather the one currently marked as such also, in my case at least, udisks-daemon and udisks-helper-m (I guess it's "module", as top truncates it) stay eating 100% CPU (each) and memory until the whole system is completely unresponsive (best case scenario, it brings down gnome-shell and sends lots of things to swap before I kill it), so I guess this is also related to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/726814 happened with two different usb sticks... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1152907 Title: usb-creator-gtk raises error immediately after entering password on erase disk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-creator/+bug/1152907/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 969359] Re: [keyboard]: gnome-settings-daemon consumes 100% cpu (and blinking numlock)
still happening -- using Quantal, gsd 3.4.2-0ubuntu15 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/969359 Title: [keyboard]: gnome-settings-daemon consumes 100% cpu (and blinking numlock) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/969359/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 906020] Re: Sometimes Nautilus loses GTK theme
*** This bug is a duplicate of bug 639913 *** https://bugs.launchpad.net/bugs/639913 also dup of bug #761551 and bug #649809, but this can happen after startup (I had been working on it for hours) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/906020 Title: Sometimes Nautilus loses GTK theme To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/906020/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 906020] Re: Sometimes Nautilus loses GTK theme
*** This bug is a duplicate of bug 639913 *** https://bugs.launchpad.net/bugs/639913 Also happens in Precise and Quantal. Last time I was importing a massive library into Shotwell (which grew to consume lots of memory) ** Also affects: ubuntu Importance: Undecided Status: New ** This bug has been marked a duplicate of bug 639913 gnome-settings-daemon random crash at session start (xorg badmatch error) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/906020 Title: Sometimes Nautilus loses GTK theme To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/906020/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1010619] Re: [SRU] Rhythmbox 2.97 and 2.98 freezes with large collection
ref Testcase: with a 190gb collection, it happens > 90% of the time RB starts up -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1010619 Title: [SRU] Rhythmbox 2.97 and 2.98 freezes with large collection To manage notifications about this bug go to: https://bugs.launchpad.net/rhythmbox/+bug/1010619/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1010619] Re: [2.97-0ubuntu2] Rhythmbox freezes
I also confirm... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1010619 Title: [2.97-0ubuntu2] Rhythmbox freezes To manage notifications about this bug go to: https://bugs.launchpad.net/rhythmbox/+bug/1010619/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1070031] Re: Rhythmbox freezes at startup
*** This bug is a duplicate of bug 1010619 *** https://bugs.launchpad.net/bugs/1010619 ** This bug has been marked a duplicate of bug 1010619 [2.97-0ubuntu2] Rhythmbox freezes -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1070031 Title: Rhythmbox freezes at startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1070031/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1010619] Re: [2.97-0ubuntu2] Rhythmbox freezes
it also happens with these two versions on Ubuntu Quantal (dist upgraded from Precise): * 2.98-0.1~webupd8~quantal2 from ppa:webupd8team/rhythmbox * Precise's 2.96-0ubuntu4.1 installed manually (gotten these debs from packages.ubuntu.com: rhythmbox_2.96-0ubuntu4.1_amd64 librhythmbox-core5_2.96-0ubuntu4.1_amd64 rhythmbox-data_2.96-0ubuntu4.1_all gir1.2-rb-3.0_2.96-0ubuntu4.1_amd64) 2.96 worked wonderfully on Precise before upgrading... perhaps the XML got corrupted somehow during the upgrade? (though it doesn't look like it was modified) I've got a ~100gb collection. Also, if I start it with rhythmbox --rhythmdb-file=~/test.db it works, until it scanned enough of my ~/Music to start hanging again... My conclusion: * it's definitely related to having a large collection * it didn't happen on Precise * it happens on Quantal with Precise's Rhythmbox so I guess the problem lies in some other dependency (say, libxml or something)... any ideas? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1010619 Title: [2.97-0ubuntu2] Rhythmbox freezes To manage notifications about this bug go to: https://bugs.launchpad.net/rhythmbox/+bug/1010619/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1043568] Re: Quantal Light themes regression (usage of bitmaps)
Closing it, as it's mostly opinion by now. Just to state the obvious, thank you very much for your work on this. It does look like it will be noticeably better and more polished in 12.10. It's difficult, no doubt; but parts of it are already solved (the vector screenshots testify to this). Worst of all is getting apps to play along (GTK supports backends, Cairo helps a lot, themes could use CSS and/or SVG). And they will only start doing so when there's something to play with. And what struck me was the apparent regression from 11.10 (which I assume is due to the specific gradients and borders being hard to impossible to achieve with either CSS or SVG). As for Apple, even though they don't support arbitrary DPIs (that would be a nightmare of visual glitches), right now their implementation is more flexible than you give them credit (they expose 5 different presets, at least on their retina display, and they look like, say, 1x, 1.5x, 2x, 2.5x and 3x). They don't support rendering to multiple targets though (bad luck for those having an external display). Of course, I don't believe they provide 5 different bitmaps for every UI element. Quick google: bit.ly/Q1gjWF I don't believe that providing N different themes for specific DPIs is a workable solution (not flexible enough IMHO, plus, most stuff is already drawn in Inkscape and then exported, so it's actually less work for designers). ** Changed in: light-themes (Ubuntu) Status: New => Opinion ** Changed in: light-themes (Ubuntu) Status: Opinion => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1043568 Title: Quantal Light themes regression (usage of bitmaps) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/light-themes/+bug/1043568/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1043568] Re: Quantal Light themes regression (usage of bitmaps)
That's a shame, given that exposing GTK's scaling capabilities would be useful for supporting both hi-dpi displays and varying user preferences alike. Even though lacking, it could begin to unravel this chicken-and- egg problem. Having a scalable theme is needed for this (imagine letting the user scale a bitmap theme!). Particularly given that unico has great support for avoiding the use of bitmaps (11.10 had only one bitmap -- the slider with a sharp end, rendering most of its UI using CSS properties). Scaling only text is not useful as a user preference. I know it's needed for different circumstances (incl. different scripts), but it's not enough. David Zeuthen had a demo in the pre-gtk3 days*; it was ok but only scaled a few properties (e.g. border-radius was constant). -- nachokb * https://mail.gnome.org/archives/gtk-devel- list/2008-August/msg00044.html (the images can be found on archive.org) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1043568 Title: Quantal Light themes regression (usage of bitmaps) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/light-themes/+bug/1043568/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1043568] Re: Quantal Light themes regression (usage of bitmaps)
@andrea (#4) sorry I didn't understand your comment. For the record: the PDF attachment in #1 is how things should behave ideally (that is, except for the icons which is a tough problem to solve). Everything scales proportionally. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1043568 Title: Quantal Light themes regression (usage of bitmaps) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/light-themes/+bug/1043568/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1043568] Re: Quantal Light themes regression (usage of bitmaps)
** Attachment added: "SVG Vector screenshot of Marlin's properties dialog in 0.1.91-0ubuntu1 (latest version, on precise)" https://bugs.launchpad.net/ubuntu/+source/light-themes/+bug/1043568/+attachment/3282819/+files/marlin-properties-0.1.91-0ubuntu1-precise.svg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1043568 Title: Quantal Light themes regression (usage of bitmaps) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/light-themes/+bug/1043568/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1043568] Re: Quantal Light themes regression (usage of bitmaps)
** Attachment added: "PDF Vector screenshot of Marlin's properties dialog in 0.1.91-0ubuntu1 (latest version, on precise)" https://bugs.launchpad.net/ubuntu/+source/light-themes/+bug/1043568/+attachment/3282818/+files/marlin-properties-0.1.91-0ubuntu1-precise.pdf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1043568 Title: Quantal Light themes regression (usage of bitmaps) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/light-themes/+bug/1043568/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1043568] Re: Quantal Light themes regression (usage of bitmaps)
** Attachment added: "Vector screenshot of Marlin's properties dialog in 0.1.8.27.6 (oneiric)" https://bugs.launchpad.net/bugs/1043568/+attachment/3282817/+files/marlin-properties-0.1.8.27.6-oneiric.pdf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1043568 Title: Quantal Light themes regression (usage of bitmaps) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/light-themes/+bug/1043568/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1043568] [NEW] Quantal Light themes regression (usage of bitmaps)
Public bug reported: The need for resolution (more precisely, density) independence is growing everyday. High-DPI devices are available (high resolution notebooks, etc) since a few years ago and GTK is lagging. GTK3 and Unico seemed an improvement but it doesn't seem to materialize (we keep scaling only the text parts). One of the thing we need is scalable themes. In Oneiric, version 0.1.8.27.6 used CSS for most components (notable exception: the slider handle). Attached is a vector screenshot* (it's Marlin properties dialog, looked simple enough to demonstrate this) showing how well it could scale to different DPIs. And then two more showing a similar dialog in 0.1.91-0ubuntu1 (one in PDF, in which the transparent PNGs make cairo generate a less-than-optimal PDF, and a second one in SVG which has a different set of glitches). Quantal Light themes (which I installed on my Precise desktop) swaps them out for PNGs in order to support a specific visual style. I assume that style is hard or impossible to get just using CSS properties. This precludes the possibility of scaling the UI to better fit some devices or user preferences. There are a lot more problems to overcome to achieve good UI scaling, but this particular one was mostly resolved. So can't light-themes use CSS properties or at least SVG assets? * Joachim Breitner's gtk-vector-screenshot is an excellent utility, useful for documentation and stuff ** Affects: light-themes (Ubuntu) Importance: Undecided Status: New ** Tags: ui -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1043568 Title: Quantal Light themes regression (usage of bitmaps) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/light-themes/+bug/1043568/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 841734] Re: T.E.G. Client doesn't start
this is all that I found is syslog: "tegclient[7688]: segfault at 0 ip 7f841b38ba5c sp 7e5e6248 error 4 in libc-2.13.so[7f841b262000+195000]" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/841734 Title: T.E.G. Client doesn't start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/teg/+bug/841734/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 655184] Re: Menus should be condensed to fit panel/overlay of appmenu
in extreme cases like Stefan's, perhaps something like "if it can't show at least two menus or XXX pixels, default to only show 'More'" but named something like "Menu" and having the whole app's menu in vertical/overflow layout... Or adopt something like Firefox's approach and make the app name clickable and popup the menu (though that would be inconsistent with the default wide-enough behavior) nachokb -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/655184 Title: Menus should be condensed to fit panel/overlay of appmenu -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 654305] Re: [Maverick] Empathy cannot connect to GMail account
Still affecting me on Maverick final -- attached logs from empathy, showing things like this: > mcd-DEBUG: 11/23/2010 14:34:43.772450: proxy_destroyed: Channel proxy > invalidated: tp_dbus_errors_quark 8: Channel was closed > ... > mcd-DEBUG: 11/23/2010 14:34:43.781779: mcd_connection_invalidated_cb: Proxy > destroyed (wocky-xmpp-reader-error (#1): Namespace prefix xmlns on server is > not defined)! nachokb ** Attachment added: "misson-control-23-11-10_14-38-33.log" https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/654305/+attachment/1742684/+files/misson-control-23-11-10_14-38-33.log ** Changed in: empathy (Ubuntu) Status: Invalid => Confirmed -- [Maverick] Empathy cannot connect to GMail account https://bugs.launchpad.net/bugs/654305 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 452252] Re: No sound in ca0106 (Sound Blaster Audigy)
I had this problem, and it was fixed by doing this [1], that is, using alsamixer, muting the second volume "S/PDIF" (highlight it and press M). That is, if the digital out is not muted, analog is muted (??). Had fallen back to crappy integrated audio for months on 10.04, until it happened once again in 10.10. Went crazy to find this out. I wish I could "upvote" this user... [2]. [1] https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/303679/comments/24 / https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/303679/comments/27 [2] https://launchpad.net/~gordon-cook-comsol-it -- No sound in ca0106 (Sound Blaster Audigy) https://bugs.launchpad.net/bugs/452252 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 659406] Re: Kubuntu 10.10 (Maverick) Live-CD i386 Dektop does not boot
BTW most probably Nouveau does not yet support GT240 [1]. In that case, the problem is that the LiveCD tries to use it and hangs. nachokb [1] http://www.phoronix.com/scan.php?page=article&item=ecs_geforce_240&num=9 -- Kubuntu 10.10 (Maverick) Live-CD i386 Dektop does not boot https://bugs.launchpad.net/bugs/659406 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 659406] Re: Kubuntu 10.10 (Maverick) Live-CD i386 Dektop does not boot
** Attachment added: "dmesg.log" https://bugs.launchpad.net/ubuntu/+source/casper/+bug/659406/+attachment/1699001/+files/dmesg.log -- Kubuntu 10.10 (Maverick) Live-CD i386 Dektop does not boot https://bugs.launchpad.net/bugs/659406 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 659406] Re: Kubuntu 10.10 (Maverick) Live-CD i386 Dektop does not boot
-- cont -- second attachment ** Attachment added: "nouveau1.log" https://bugs.launchpad.net/ubuntu/+source/casper/+bug/659406/+attachment/1699000/+files/nouveau1.log -- Kubuntu 10.10 (Maverick) Live-CD i386 Dektop does not boot https://bugs.launchpad.net/bugs/659406 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 659406] Re: Kubuntu 10.10 (Maverick) Live-CD i386 Dektop does not boot
Same thing happened here with Ubuntu Maverick final Desktop Live CD; when trying to boot, Plymouth runs perfectly (detects resolutions correctly), but when it tries to start the regular desktop, it freezes. Screen shows garbage (mostly what's left on video memory, sometimes I even recognize something from my last Lucid session), but VT switching works. Switched to VT1 and tried to collect as much log data as possible. Problem seems, obviously, to be Nouveau. Attached you'll find to Xorg logs I found and a `dmesg | grep -i nouv` output showing some problems. My video card is a GDDR5 nVidia GT 240 (512mb). Will try to install with alternate CD and hope that nVidia's blob works fine (as it does right now with Lucid) -- but I really wanted to test out Nouveau (anyway, I can't live without VDPAU so I would have ended up using the proprietary blob anyway). Hope this helps, nachokb ** Attachment added: "Xorg.0.log.old" https://bugs.launchpad.net/ubuntu/+source/casper/+bug/659406/+attachment/1698999/+files/Xorg.0.log.old -- Kubuntu 10.10 (Maverick) Live-CD i386 Dektop does not boot https://bugs.launchpad.net/bugs/659406 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 546552] Re: MythTV is built without H.264 HE-AAC support
Running lucid with mythtv 0.23+fixes24158 here -- no libfaad support ** Changed in: mythtv (Ubuntu) Status: Fix Released => Confirmed -- MythTV is built without H.264 HE-AAC support https://bugs.launchpad.net/bugs/546552 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 501213] Re: Huawei E176 can't connect (hangs up)
Sidenote: works OK in Windows... Tried wicd -- seems to show the same problem: wvdial output: u...@host$ sudo wvdial --> WvDial: Internet dialer version 1.60 --> Cannot get information for serial port. --> Initializing modem. --> Sending: ATZ ATZ OK --> Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 OK --> Sending: AT+CGDCONT=1,"IP","igprs.claro.com.ar" AT+CGDCONT=1,"IP","igprs.claro.com.ar" OK --> Modem initialized. --> Sending: ATD*99***2# --> Waiting for carrier. ATD*99***2# CONNECT 720 --> Carrier detected. Starting PPP immediately. --> Starting pppd at Tue Dec 29 02:57:50 2009 --> Pid of pppd: 4787 --> Using interface ppp0 --> pppd: �[7f] --> pppd: �[7f] --> pppd: �[7f] --> pppd: �[7f] --> pppd: �[7f] --> pppd: �[7f] --> Disconnecting at Tue Dec 29 02:57:52 2009 --> The PPP daemon has died: A modem hung up the phone (exit code = 16) --> man pppd explains pppd error codes in more detail. --> Try again and look into /var/log/messages and the wvdial and pppd man pages for more information. --> Auto Reconnect will be attempted in 5 seconds --> Cannot get information for serial port. this is /var/log/messages (notice "CHAP auth OK" => "Modem hangup") Dec 29 02:55:15 lothlorien pppd[4567]: pppd 2.4.5 started by root, uid 0 Dec 29 02:55:15 lothlorien pppd[4567]: Using interface ppp0 Dec 29 02:55:15 lothlorien pppd[4567]: Connect: ppp0 <--> /dev/ttyUSB0 Dec 29 02:55:15 lothlorien pppd[4567]: CHAP authentication succeeded Dec 29 02:55:15 lothlorien pppd[4567]: CHAP authentication succeeded Dec 29 02:55:18 lothlorien pppd[4567]: Modem hangup Dec 29 02:55:18 lothlorien pppd[4567]: Connection terminated. Dec 29 02:55:18 lothlorien pppd[4567]: Exit. Dec 29 02:55:23 lothlorien pppd[4578]: pppd 2.4.5 started by root, uid 0 Dec 29 02:55:23 lothlorien pppd[4578]: Using interface ppp0 Dec 29 02:55:23 lothlorien pppd[4578]: Connect: ppp0 <--> /dev/ttyUSB0 Dec 29 02:55:23 lothlorien pppd[4578]: CHAP authentication succeeded Dec 29 02:55:23 lothlorien pppd[4578]: CHAP authentication succeeded Dec 29 02:55:27 lothlorien pppd[4578]: Modem hangup Dec 29 02:55:27 lothlorien pppd[4578]: Connection terminated. Dec 29 02:55:27 lothlorien pppd[4578]: Exit. any pointers??? -- Huawei E176 can't connect (hangs up) https://bugs.launchpad.net/bugs/501213 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 501213] Re: Huawei E176 can't connect (hangs up)
** Attachment added: "daily-ppa-091229-modem.log.txt" http://launchpadlibrarian.net/37260900/daily-ppa-091229-modem.log.txt -- Huawei E176 can't connect (hangs up) https://bugs.launchpad.net/bugs/501213 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 501213] Re: Huawei E176 can't connect (hangs up)
** Attachment added: "daily-ppa-091229-nm.log.txt" http://launchpadlibrarian.net/37260898/daily-ppa-091229-nm.log.txt -- Huawei E176 can't connect (hangs up) https://bugs.launchpad.net/bugs/501213 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 501213] Re: Huawei E176 can't connect (hangs up)
** Attachment added: "karmic-modem.log.txt" http://launchpadlibrarian.net/37260877/karmic-modem.log.txt -- Huawei E176 can't connect (hangs up) https://bugs.launchpad.net/bugs/501213 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 501213] Re: Huawei E176 can't connect (hangs up)
** Attachment added: "karmic-nm.log.txt" http://launchpadlibrarian.net/37260867/karmic-nm.log.txt -- Huawei E176 can't connect (hangs up) https://bugs.launchpad.net/bugs/501213 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 501213] Re: Huawei E176 can't connect (hangs up)
** Attachment added: "mm-test.log" http://launchpadlibrarian.net/37260851/mm-test.log -- Huawei E176 can't connect (hangs up) https://bugs.launchpad.net/bugs/501213 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 501213] [NEW] Huawei E176 can't connect (hangs up)
Public bug reported: Binary package hint: modemmanager Trying to use Huawei E176 -- it's detected but can't connect (tried vanilla karmic NM + ModemManager, and NM Daily PPA[1]). A quick look at logs (as per [2]) shows that it connects and then immediately hangs up. I've read around the forums that the integration of ModemManager broke many previously working modems. Is there a way to go back to 9.04-NM? I'll try wicd + wvdial now... I've attached NM's and MM's log (both with Karmic's default packages and the PPA's at 29 december 2009) and the output of the mm-test.py program. nachokb [1] https://launchpad.net/~network-manager/+archive/trunk [2] https://wiki.ubuntu.com/DebuggingModemmanager ** Affects: modemmanager (Ubuntu) Importance: Undecided Status: New -- Huawei E176 can't connect (hangs up) https://bugs.launchpad.net/bugs/501213 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 456937] Re: BUG: kernel oops when running hamachi's tuncfg
Problem was that Hamachi's binary was packed with UPX (somehow that worked in previous versions, but now it blows up). Make sure you have upx-ucl installed > sudo aptitude install upx-ucl > upx -d hamachi then the binary works... P.S. sorry I didn't comment it before, I solved it a few days ago -- nachokb -- BUG: kernel oops when running hamachi's tuncfg https://bugs.launchpad.net/bugs/456937 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 449268] Re: Karmic Restricted Driver Bug
Indeed it was solved by installing the bcmwl-kernel-source package... -- Karmic Restricted Driver Bug https://bugs.launchpad.net/bugs/449268 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 456937] Re: BUG: kernel oops when running hamachi's tuncfg
** Attachment added: "AlsaDevices.txt" http://launchpadlibrarian.net/34086567/AlsaDevices.txt ** Attachment added: "AplayDevices.txt" http://launchpadlibrarian.net/34086568/AplayDevices.txt ** Attachment added: "BootDmesg.txt" http://launchpadlibrarian.net/34086569/BootDmesg.txt ** Attachment added: "Card0.Amixer.values.txt" http://launchpadlibrarian.net/34086570/Card0.Amixer.values.txt ** Attachment added: "Card0.Codecs.codec.0.txt" http://launchpadlibrarian.net/34086571/Card0.Codecs.codec.0.txt ** Attachment added: "CurrentDmesg.txt" http://launchpadlibrarian.net/34086572/CurrentDmesg.txt ** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/34086573/Dependencies.txt ** Attachment added: "IwConfig.txt" http://launchpadlibrarian.net/34086574/IwConfig.txt ** Attachment added: "Lspci.txt" http://launchpadlibrarian.net/34086575/Lspci.txt ** Attachment added: "Lsusb.txt" http://launchpadlibrarian.net/34086576/Lsusb.txt ** Attachment added: "OopsText.txt" http://launchpadlibrarian.net/34086577/OopsText.txt ** Attachment added: "PciMultimedia.txt" http://launchpadlibrarian.net/34086578/PciMultimedia.txt ** Attachment added: "ProcCpuinfo.txt" http://launchpadlibrarian.net/34086579/ProcCpuinfo.txt ** Attachment added: "ProcInterrupts.txt" http://launchpadlibrarian.net/34086580/ProcInterrupts.txt ** Attachment added: "ProcModules.txt" http://launchpadlibrarian.net/34086581/ProcModules.txt ** Attachment added: "RfKill.txt" http://launchpadlibrarian.net/34086582/RfKill.txt ** Attachment added: "UdevDb.txt" http://launchpadlibrarian.net/34086583/UdevDb.txt ** Attachment added: "UdevLog.txt" http://launchpadlibrarian.net/34086584/UdevLog.txt ** Attachment added: "WifiSyslog.txt" http://launchpadlibrarian.net/34086585/WifiSyslog.txt -- BUG: kernel oops when running hamachi's tuncfg https://bugs.launchpad.net/bugs/456937 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 456937] [NEW] BUG: kernel oops when running hamachi's tuncfg
Public bug reported: After installing hamacho 0.9.9.9-20 on a Karmic system, tuncfg says "Killed" and apport talks about a kenrnel oops... meanwhile the system keeps being usable and having connectivity ProblemType: KernelOops Annotation: Your system might become unstable now and might need to be restarted. Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 2/2 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nachokb1955 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xf6afc000 irq 21' Mixer name : 'IDT 92HD71B7X' Components : 'HDA:111d76b2,102802aa,00100302' Controls : 32 Simple ctrls : 19 Date: Wed Oct 21 01:54:16 2009 DistroRelease: Ubuntu 9.10 Failure: oops HibernationDevice: RESUME=UUID=c877e464-3e14-4405-b38a-f6c17a3dd7f5 LiveMediaBuild: Ubuntu 9.10 "Karmic Koala" - Beta amd64 (20090929.2) MachineType: Dell Inc. Inspiron 1545 NonfreeKernelModules: wl Package: linux-image-2.6.31-14-generic 2.6.31-14.48 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-14-generic root=UUID=dab3ee9a-8c3e-4798-8c1f-7a2ad2948288 ro quiet splash ProcVersionSignature: Ubuntu 2.6.31-14.48-generic RelatedPackageVersions: linux-backports-modules-2.6.31-14-generic N/A linux-firmware 1.24 SourcePackage: linux Tags: kernel-oops Title: BUG: unable to handle kernel NULL pointer dereference at 0068 Uname: Linux 2.6.31-14-generic x86_64 dmi.bios.date: 05/13/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 0G848F dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA07:bd05/13/2009:svnDellInc.:pnInspiron1545:pvr:rvnDellInc.:rn0G848F:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Inspiron 1545 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-kerneloops kernel-oops -- BUG: kernel oops when running hamachi's tuncfg https://bugs.launchpad.net/bugs/456937 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 449268] Re: Karmic Restricted Driver Bug
this may be related (will try it tonight): http://ubuntuforums.org/showthread.php?t=1288865&highlight=restricted+drivers -- Karmic Restricted Driver Bug https://bugs.launchpad.net/bugs/449268 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 449268] Re: Karmic Restricted Driver Bug
** Attachment added: ".var.log.jockey.log.txt" http://launchpadlibrarian.net/33477280/.var.log.jockey.log.txt ** Attachment added: "BootDmesg.txt" http://launchpadlibrarian.net/33477281/BootDmesg.txt ** Attachment added: "CurrentDmesg.txt" http://launchpadlibrarian.net/33477282/CurrentDmesg.txt ** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/33477283/Dependencies.txt ** Attachment added: "Devices.txt" http://launchpadlibrarian.net/33477284/Devices.txt ** Attachment added: "Lspci.txt" http://launchpadlibrarian.net/33477285/Lspci.txt ** Attachment added: "Lsusb.txt" http://launchpadlibrarian.net/33477286/Lsusb.txt ** Attachment added: "ProcCpuinfo.txt" http://launchpadlibrarian.net/33477287/ProcCpuinfo.txt ** Attachment added: "ProcInterrupts.txt" http://launchpadlibrarian.net/33477288/ProcInterrupts.txt ** Attachment added: "ProcMaps.txt" http://launchpadlibrarian.net/33477289/ProcMaps.txt ** Attachment added: "ProcModules.txt" http://launchpadlibrarian.net/33477290/ProcModules.txt ** Attachment added: "ProcStatus.txt" http://launchpadlibrarian.net/33477291/ProcStatus.txt ** Attachment added: "UdevDb.txt" http://launchpadlibrarian.net/33477292/UdevDb.txt ** Attachment added: "UdevLog.txt" http://launchpadlibrarian.net/33477294/UdevLog.txt -- Karmic Restricted Driver Bug https://bugs.launchpad.net/bugs/449268 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 449268] [NEW] Karmic Restricted Driver Bug
Public bug reported: When trying to activate a proprietary driver for Broadcom BCM4312 wifi adapter on Ubuntu Karmic (tested Alpha 3, Alpha 5 and Beta), it fails. It tries to open a windows which supposedly downloads and installs the drivers, but it just vanishes immediately. See screencast[1]. Important detail: this didn't happen when running from the LiveCD, only when it is installed. When running from the LiveCD, it successfully install the proprietary Broadcom STA driver. Running lsmod doesn't show 'wl' module (it is shown when running from the LiveCD). May be related to: * 410963 (this seemed to be NetworkManager-specific -- everyone reporting that bug seems to have the driver installed)[2]. * 396203 (though in my case, no error message appeared -- I don't even know if it is Jockey crashing or what else)[3]. DELL Inspiron 1545 Notebook. [1] Screencast showing the problem: http://www.youtube.com/watch?v=cwiL-bvokDo [2] https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/410963 [3] https://bugs.launchpad.net/ubuntu/+source/jockey/+bug/396203 ProblemType: Bug Architecture: amd64 Date: Mon Oct 12 02:13:01 2009 DistroRelease: Ubuntu 9.10 ExecutablePath: /usr/bin/jockey-gtk InterpreterPath: /usr/bin/python2.6 MachineType: Dell Inc. Inspiron 1545 Package: jockey-gtk 0.5.4-0ubuntu1 PackageArchitecture: all ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-11-generic root=UUID=dab3ee9a-8c3e-4798-8c1f-7a2ad2948288 ro quiet splash ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-11.36-generic SourcePackage: jockey Uname: Linux 2.6.31-11-generic x86_64 dmi.bios.date: 05/13/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 0G848F dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA07:bd05/13/2009:svnDellInc.:pnInspiron1545:pvr:rvnDellInc.:rn0G848F:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Inspiron 1545 dmi.sys.vendor: Dell Inc. ** Affects: jockey (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug restricted-drivers -- Karmic Restricted Driver Bug https://bugs.launchpad.net/bugs/449268 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 185599] Re: Missing option to disable Fast User Switching
I prefer this alternative (rather than explaining in technical terms that some action has not easily explainable effects, force the user to logout so there are not two users fighting for Compiz). There's another issue in this setting: the NetworkManager applet is also only seen by one user at a time (even though the other one might have privileges to use it). Thanks, nachokb -- Missing option to disable Fast User Switching https://bugs.launchpad.net/bugs/185599 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 73004] Re: Dell 2005fpw lcd defaults to 1280x1024 instead of its native resolution of 1680x1050
** Attachment added: "Xorg.0.gutsy_final.log" http://launchpadlibrarian.net/10199122/Xorg.0.gutsy_final.log -- Dell 2005fpw lcd defaults to 1280x1024 instead of its native resolution of 1680x1050 https://bugs.launchpad.net/bugs/73004 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 73004] Re: Dell 2005fpw lcd defaults to 1280x1024 instead of its native resolution of 1680x1050
** Attachment added: "xresprobe_radeon_gutsy_final.txt" http://launchpadlibrarian.net/10199117/xresprobe_radeon_gutsy_final.txt -- Dell 2005fpw lcd defaults to 1280x1024 instead of its native resolution of 1680x1050 https://bugs.launchpad.net/bugs/73004 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 73004] Re: Dell 2005fpw lcd defaults to 1280x1024 instead of its native resolution of 1680x1050
Now I had some time to install Gutsy and try it. 1- LiveCD's Ubuntu Splash is shown in low resolution, but once installed, the same splash is shown in 1280x1024. 2- X boots straight into 1680x1050 :D :D !!! (and BTW Compiz Fusion worked flawlessly with my sh**ty Radeon 9600XT with the great Radeon open source driver (I'm about to try the restricted drivers manager and install fglrx, and then try to see if there's an easy way -- say, through Alberto Milone's repo -- to install the latest AIGLX-supporting fglrx). 3- The 6 virtual terminals tty1 .. 6 use low resolution (not even 1280x1024). Please notice that xresprobe is not reporting "crt" as disptype anymore (it's an empty string now, don't know if that's any good). I understand that ttys are not a priority (they are not really used by normal users), so that's not important. Is there a way for the console and splash to support resolutions higher than 1280x1024? Last I checked, vesafb was used and that was its limit... Thanks Bryce for your work. I attach for reference my new ddcprobe's, resprobe outputs and an 800-line tail of Xorg.0.log. nachokb ** Attachment added: "ddcprobe_gutsy_final.txt" http://launchpadlibrarian.net/10199115/ddcprobe_gutsy_final.txt -- Dell 2005fpw lcd defaults to 1280x1024 instead of its native resolution of 1680x1050 https://bugs.launchpad.net/bugs/73004 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 73004] Re: Dell 2005fpw lcd defaults to 1280x1024 instead of its native resolution of 1680x1050
** Attachment added: "800-line tail of my Xorg.0.log" http://launchpadlibrarian.net/9654020/Xorg.log -- Dell 2005fpw lcd defaults to 1280x1024 instead of its native resolution of 1680x1050 https://bugs.launchpad.net/bugs/73004 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 73004] Re: Dell 2005fpw lcd defaults to 1280x1024 instead of its native resolution of 1680x1050
I AM REALLY STUPID I wasn't sudoing xresprobe (now it's correct). You can see it's detected as "crt" :( ** Attachment added: "Non-empty xresprobe's output" http://launchpadlibrarian.net/9654015/xresprobe_radeon.txt -- Dell 2005fpw lcd defaults to 1280x1024 instead of its native resolution of 1680x1050 https://bugs.launchpad.net/bugs/73004 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 73004] Re: Dell 2005fpw lcd defaults to 1280x1024 instead of its native resolution of 1680x1050
Tried it in Gutsy Beta (which is older than your patch). BTW, even though it started in 1280x1024, I had the correct option already configured, so System > Preferences > Screen Resolution showed 1680x1050 (that is more than acceptable to me, no xorg.conf fiddling anymore). I attach ddcprobe's output and a long tail of Xorg.0.log (with video modes info). Sadly, xresprobe's output was empty (I'm running the driver chosen by the livecd which is radeon, perhaps I'll try it with fglrx next time... ** Attachment added: "ddcprobe's output" http://launchpadlibrarian.net/9654005/ddcprobe.txt -- Dell 2005fpw lcd defaults to 1280x1024 instead of its native resolution of 1680x1050 https://bugs.launchpad.net/bugs/73004 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 73004] Re: Dell 2005fpw lcd defaults to 1280x1024 instead of its native resolution of 1680x1050
By the way, I noticed usplash (and console) is limited to 1280x1024 (due to vesafb I think). Is there a chance to use 1680x1050? (or for that matter, many other resolutions, eg 1440x900, 1920x1200, 2560x1600 which are becoming standard in new not-so-expensive lcds). -- Dell 2005fpw lcd defaults to 1280x1024 instead of its native resolution of 1680x1050 https://launchpad.net/bugs/73004 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 73004] Re: Dell 2005fpw lcd defaults to 1280x1024 instead of its native resolution of 1680x1050
Same for 2007wfp here -- Dell 2005fpw lcd defaults to 1280x1024 instead of its native resolution of 1680x1050 https://launchpad.net/bugs/73004 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
