[Bug 1971758] [NEW] package os-prober 1.79ubuntu1 failed to install/upgrade: vereistenproblemen - blijft ongeconfigureerd
Public bug reported: update niet ProblemType: Package DistroRelease: Ubuntu 21.10 Package: os-prober 1.79ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-40.45-generic 5.13.19 Uname: Linux 5.13.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu71.1 AptOrdering: firefox:amd64: Remove NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu May 5 20:20:35 2022 ErrorMessage: vereistenproblemen - blijft ongeconfigureerd InstallationDate: Installed on 2022-01-09 (115 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 3.9.4-1build1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.9ubuntu2 apt 2.3.9 SourcePackage: os-prober Title: package os-prober 1.79ubuntu1 failed to install/upgrade: vereistenproblemen - blijft ongeconfigureerd UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: os-prober (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971758 Title: package os-prober 1.79ubuntu1 failed to install/upgrade: vereistenproblemen - blijft ongeconfigureerd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/os-prober/+bug/1971758/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971759] [NEW] package os-prober 1.79ubuntu1 failed to install/upgrade: vereistenproblemen - blijft ongeconfigureerd
Public bug reported: update niet ProblemType: Package DistroRelease: Ubuntu 21.10 Package: os-prober 1.79ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-40.45-generic 5.13.19 Uname: Linux 5.13.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu71.1 AptOrdering: firefox:amd64: Remove NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu May 5 20:20:35 2022 ErrorMessage: vereistenproblemen - blijft ongeconfigureerd InstallationDate: Installed on 2022-01-09 (115 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 3.9.4-1build1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.9ubuntu2 apt 2.3.9 SourcePackage: os-prober Title: package os-prober 1.79ubuntu1 failed to install/upgrade: vereistenproblemen - blijft ongeconfigureerd UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: os-prober (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971759 Title: package os-prober 1.79ubuntu1 failed to install/upgrade: vereistenproblemen - blijft ongeconfigureerd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/os-prober/+bug/1971759/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876056] Re: No automatic switch to headset microphone on connect
@rcassini - that is what the modification I suggested also does. To get back towards Pulsaaudio though, I did pay more attention to differen platforms. It occured to my that Mac OS also isn't capable of detecting what type of jack is plugged in, but still manages to make a decent automatic choice. I noticed that: - When I plug in headphones, it uses the internal mic -> OK - When I plug a simple headset, it switches to headset mic -> OK - When I plug in a more advanced headset with mute control that is unmuted, it still switches to headset mic -> OK - When I plug in this same headset with the mic muted, it remains on internal mic -> questionable, but makes sense. When I then unmute, it still switches to headset mic. So it seems to actually poll the wires for a signal, and if any input that looks like a mic is coming through, it switches. So when it's muted, no signal comes through and it assumes it's a headset. Simple and clever, and usually what you want. The main drawback is that this may lead to a situation where you think you're muted but you're actually not muted because it uses the internal mic which isn't muted. Still, something that I'd like to see implemented in Pulseaudio as well! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876056 Title: No automatic switch to headset microphone on connect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1876056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874453] Re: ubuntu/focal64 very slow to boot and reboots once
@jchittum, confirmed also your fix using fresh `vagrant init ubuntu/focal64` and `vagrant up` thx -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874453 Title: ubuntu/focal64 very slow to boot and reboots once To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1874453/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888210] Re: Migration of KRunner shortcut doesn't work (or launcher starts in background)
Seems like it is! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888210 Title: Migration of KRunner shortcut doesn't work (or launcher starts in background) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-workspace/+bug/1888210/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888210] [NEW] Migration of KRunner shortcut doesn't work (or launcher starts in background)
Public bug reported: *Summary:* Since the upgrade to 20.04 (coming from Kubuntu 19.10), the Alt+F2 (or my personal alternative Alt+D) that are bound to launching KRunner seem to open KRunner in the background. Previously I could press Alt+D (or Alt+F2) and start typing, hit enter and start a new program. Now, I can only do this when I'm looking at an empty workspace. If I have any application open in the current workspace, the shortcut seems to be ignored and the program name is typed into the open application. *Solution or workaround* It seems that in the Global Shortcuts I need to assign the shortcuts to Application Launcher -> KRunner rather than Other Shortcuts -> Run Command. When I manually set the shortcuts there, KRunner launches in the foreground again. If this is the expected migration path, it should be automated after the version upgrade. *Require information* 1) Ubuntu version: Description:Ubuntu 20.04 LTS Release:20.04 2) Version: plasma-workspace Installed: 4:5.18.5-0ubuntu0.1 3) What I expected to happen: I expect Alt+F2 or Alt+D (or other configured shortcuts) to start KRunner in the foreground and accept subsequent keypresses. If the target for shortcuts is changed between Plasma versions, I expect this migration to be automated after upgrading. 4) What happend instead: Alt+F2 / Alt+D doesn't show KRunner and only accepts input when there are no other windows on screen. Migration has to be done manually after discovering the difference. ** Affects: plasma-desktop (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888210 Title: Migration of KRunner shortcut doesn't work (or launcher starts in background) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-desktop/+bug/1888210/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887807] Re: KDE doesn't prompt whether headphones or a headset is plugged in
Thanks @seb128 - I was convinced I assigned it to kubuntu-desktop instead of pulseaudio, but apparently somehow I failed doing that. My apologies. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887807 Title: KDE doesn't prompt whether headphones or a headset is plugged in To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdebase/+bug/1887807/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887807] [NEW] KDE doesn't prompt whether headphones or a headset is plugged in
Public bug reported: As a follow-up from: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1876056 I have a Dell XPS 7590 with a combined headset jack. As I understood from the previous ticket 1876056, when on Ubuntu you plug in something, it will prompt you what you plugged in: either a headset or headphones. Kubuntu doesn't do this. This means that it will never automatically switch to the headset microphone when I plug it in, even though I never ever use headphones on this laptop. So it would be great if Kubuntu would prompt me what I plugged in and allow me to either select every time or select the default option when I plug something in. For now I'm working around this by adding [Jack Headphone Mic] state.plugged = no state.unplugged = unknown [Jack Headset Mic] state.plugged = no state.unplugged = unknown to /usr/share/pulseaudio/alsa-mixer/paths/analog-input-internal-mic.conf but after each update of pulseaudio this file gets reverted. And it's not really user friendly. I'm really not sure against what package I should report this - please correct me if this should be more specific (e.g. phonon or kde multimedia). I wouldn't know which part this would be. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887807 Title: KDE doesn't prompt whether headphones or a headset is plugged in To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1887807/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872001] Re: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0
I've been running a couple of days not on the new release from eoan- proposed: 5.3.0-53-generic and this solved the docker issues introduced by earlier versions. So far no GPU hangs either. Not sure if anything related to this bug was changed in -53 in comparison to -52, but it's looking good. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872001 Title: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872001/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872001] Re: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0
Another occurrence of this bug for me too, unfortunately: [23965.090982] i915 :00:02.0: GPU HANG: ecode 9:0:0x, hang on rcs0 [23965.091992] i915 :00:02.0: Resetting rcs0 for hang on rcs0 This is the first for me in a week of using 5.3.0-52-generic so it's definitely less common. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872001 Title: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872001/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872001] Re: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0
@rhardy good that it worked all out for you. However, just for your information: upgrade to 20.04 wasn't necessary to run a newer kernel. I've been running a 5.4 kernel for quote some time on 19.10 using the mainline utitlity from http://ppa.launchpad.net/cappelikan/ppa/ubuntu which works perfectly. And after a couple of days of testing on 5.3.0-52 from eoan-proposed, I now feel confident enough to say that it fixes the i915 issues I experienced before, so it definitely improves the situation. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872001 Title: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872001/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1831587] Re: brightness control not work with OLED panel
Same here on a Dell XPS 7590 with OLED display, same as @rojer9 in #4. The script above in #6 works, combine with the autostart .desktop file from Archlinux wiki. Any chance of this either becoming automated in the setup or having the relevant kernel modules adjusted to adjust the brightness correctly on OLED displays? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1831587 Title: brightness control not work with OLED panel To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1831587/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872001] Re: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0
I've done some testing with 5.3.0-52 over the past few hours and it seems to work properly. However, the kernel in #57 also worked significantly better than the one from the repositories but I did still experience the GPU HANG a couple of times over the course of 2 days so I am not completely certain yet. Until today, 5.4.28-050428 has been the only one I tested that worked without any issues over several weeks. I'll keep running this one to see if the issue still pops up or not. Is 5.3.0-52 in proposed different from the patches applied in #57? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872001 Title: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872001/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876056] Re: No automatic switch to headset microphone on connect
No, that seems to be an actual regression. The thing I'm reporting turns out to be an intentional configuration issue related to limitations of the hardware / jack detection. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876056 Title: No automatic switch to headset microphone on connect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1876056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876056] Re: No automatic switch to headset microphone on connect
@seb128 yes you are right. The explanation there makes a lot of sense - after some experimentation I found that the headset mic becomes available no matter whether I plugin a headphones or a headset, so it doesn't actually detect the presence of a microphone, it just happens that something is plugged in. However, that issue also mentions: > Ubuntu solves this by popping up a GUI that asks what you plugged in. This seems like a sane thing to do in this situation. As I'm using Kubuntu and not Ubuntu, where should this feature be requested? For the time being, I added the two suggested sections to /usr/share/pulseaudio/alsa-mixer/paths/analog-input-internal-mic.conf [Jack Headphone Mic] state.plugged = no state.unplugged = unknown [Jack Headset Mic] state.plugged = no state.unplugged = unknown This works beautifully. But now, indeed, when I plug in a regular headset without a microphone it will still switch making me effectively muted. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876056 Title: No automatic switch to headset microphone on connect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1876056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876056] [NEW] No automatic switch to headset microphone on connect
Public bug reported: On my Dell XPS 7590, when I plugin a headset with a 4-pin-connector, the audio OUTPUT automatically switches from the speakers in the laptop to the headset. However, the audio INPUT does not switch from the microphone in the laptop to the microphone in the headset. Using for example pavucontrol, I can switch to the microphone manually on the tab 'input devices' - on that tab Port will be on 'Internal Microphone' and I can set it to 'Headset Microphone'. What's even more confusing is that when I unplug the headset, both input AND output switch back to internal automatically and the port on the 'Input Devices'. This is on Ubuntu 19.10 with kernel 5.4.28-050428-generic (but I also see the same issue on kernel 5.3.0-48) and pulseaudio 1:13.0-1ubuntu1.1. If any more information is needed, let me know. inxi -F: System:Host: idefixpsie Kernel: 5.4.28-050428-generic x86_64 bits: 64 Desktop: KDE Plasma 5.16.5 Distro: Ubuntu 19.10 (Eoan Ermine) Machine: Type: Laptop System: Dell product: XPS 15 7590 v: N/A serial: Mobo: Dell model: 0VYV0G v: A00 serial: UEFI: Dell v: 1.5.0 date: 12/25/2019 Battery: ID-1: BAT0 charge: 77.7 Wh condition: 87.4/97.0 Wh (90%) CPU: Topology: 6-Core model: Intel Core i7-9750H bits: 64 type: MT MCP L2 cache: 12.0 MiB Speed: 4029 MHz max: 4500 MHz Core speeds (MHz): 1: 4213 2: 4160 3: 4229 4: 4210 5: 4224 6: 4163 7: 4280 8: 4189 9: 4291 10: 4198 11: 4149 12: 4188 Graphics: Device-1: Intel UHD Graphics 630 driver: i915 v: kernel Display: x11 server: X.Org 1.20.5 driver: modesetting unloaded: fbdev,vesa resolution: 3840x2160~60Hz OpenGL: renderer: Mesa DRI Intel UHD Graphics 630 (Coffeelake 3x8 GT2) v: 4.5 Mesa 19.2.8 Audio: Device-1: Intel Cannon Lake PCH cAVS driver: snd_hda_intel Sound Server: ALSA v: k5.4.28-050428-generic Network: Device-1: Intel driver: iwlwifi IF: wlan0 state: up mac: 5c:80:b6:7a:2c:45 IF-ID-1: docker0 state: down mac: 02:42:90:4c:31:a2 Drives:Local Storage: total: 953.87 GiB used: 67.58 GiB (7.1%) ID-1: /dev/nvme0n1 model: SSDPEMKF010T8 NVMe INTEL 1024GB size: 953.87 GiB Partition: ID-1: / size: 496.44 GiB used: 67.27 GiB (13.6%) fs: ext4 dev: /dev/dm-1 ID-2: /boot size: 704.5 MiB used: 288.4 MiB (40.9%) fs: ext4 dev: /dev/nvme0n1p2 ID-3: swap-1 size: 6.61 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/dm-2 Sensors: System Temperatures: cpu: 47.0 C mobo: N/A Fan Speeds (RPM): N/A Info: Processes: 346 Uptime: 2d 17h 51m Memory: 31.12 GiB used: 9.08 GiB (29.2%) Shell: bash inxi: 3.0.36 ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Attachment added: "lshw.txt" https://bugs.launchpad.net/bugs/1876056/+attachment/5363903/+files/lshw.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876056 Title: No automatic switch to headset microphone on connect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1876056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872001] Re: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0
I've been running the 5.3.0-48-generic_5.3.0-48.41+lp1861395v1 for 2 days now. It definitely did get better but this afternoon I did get another "Resetting rcs0 for hang on rcs0" so it doesn't seem to be solved completely. @kerneltoast: thanks for the suggestion, I did that. No more nouveau errors in dmesg and battery life has improved significantly. Awesome. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872001 Title: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872001/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872001] Re: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0
@kerneltoast I don't want to make use of my nvidia card. I'm attempting to use i915 exclusively to conserve battery and prime doesn't work properly at all anyway. I'm saving my nvidia GPU for my dualboot Windows partition. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872001 Title: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872001/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872001] Re: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0
Oh, wait, are you implying that I should actually blacklist nouveau in order to disable it and use Intel exclusively? I'll give that a try. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872001 Title: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872001/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872001] Re: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0
@arighi - it helps, but introduces different problems on my Dell XPS 15 7590. I get much less frequent lockups but they still do occur. It seems to introduce similar issues with Nouveau. My dmesg gives me lots of messages like this: [ 67.714761] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] [ 67.855754] nouveau :01:00.0: DRM: failed to idle channel 0 [DRM] [ 5396.978950] nouveau :01:00.0: tmr: stalled at [ 5412.086427] nouveau :01:00.0: timeout [ 5412.086464] WARNING: CPU: 11 PID: 11576 at drivers/gpu/drm/nouveau/nvkm/subdev/mmu/vmmtu102.c:44 tu102_vmm_flush+0x130/0x140 [nouveau] and lots of more information. I'll add the full output of dmesg as an attachment. Not sure if the new problems are introduced by your patch but I didn't experience them before on 5.3 and are also not occuring on the 5.4.28-050428-generic kernel from `mainline`. So back to 5.4.28 for me, again. ** Attachment added: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872001/+attachment/5358160/+files/dmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872001 Title: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872001/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872001] Re: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0
Update: I just tried the recently released linux-image-5.3.0-48-generic that was made available through eoan-proposed, but I still get the `Resetting rcs0 for hang on rcs0` error, so it's back to mainline 5.4.28-050428-generic for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872001 Title: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872001/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872192] Re: xserver-xorg-video-intel causes screen flickering in plasma on XPS 15 7590
You are so right, my apologies. This bug report can be discarded. In my efforts to get everything working on a new installation of Kubuntu over the past few days, I unknowingly enabled the Intel driver for XOrg. Unknowingly because: I assumed I was already using it. I put in a config snippet in /etc/X11/xorg.conf.d/20-intel.conf in a (failed) attempt to fix the screen brightness controls. This specifically links the PCI address and the intel drivers. I now removed that file, re-installed xserver-xorg-video-intel package and no flickering. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872192 Title: xserver-xorg-video-intel causes screen flickering in plasma on XPS 15 7590 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1872192/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872192] [NEW] xserver-xorg-video-intel causes screen flickering in plasma on XPS 15 7590
Public bug reported: I have been experiencing screen flickering related to the compositor in KDE / Plasma on Ubuntu 19.10 on my Dell XPS 15 7590 laptop. I found the same problem + a solution here: https://www.reddit.com/r/kde/comments/f7itw4/plasma_flickering_neonkubuntu/ It turns out that even though I do have Intel chip (IGP on Core i7-9775H) using the Intel driver i915, the package xserver-xorg-video- intel doesn't seem to be required and does cause screen flickering. Removing this package as suggested on reddit fixes the flickering issue for me and so far I didn't seen any negative side effects - all 3D rendering still works. Either xorg-video-intel package should be solved to not cause flickering (and have effects where it is not needed) or it shouldn't be installed by default. ** Affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872192 Title: xserver-xorg-video-intel causes screen flickering in plasma on XPS 15 7590 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1872192/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871867] Re: i915: GPU HANG: ecode 9:0:0x00000000, hang on rcs0
Using the `mainline` utility from https://launchpad.net/~cappelikan/+archive/ubuntu/ppa I now installed a mainline kernel version 5.4.28-050428-generic - the latest currently available in the 5.4 series. Using this kernel, I don't experience this issue at all - no hangs, not even during the use of IntelliJ. I tested it for a couple of hours in which I normally had dozens of hangs. If it helps diagnosing this issue, I'm willing to bisect the issue with various mainline versions between 5.3.0-47 and 5.4.28. Let me know if this has any value. For now I'm sticking with this new kernel version. Not sure if related - I did have an additional issue with the graphics. Directly after boot, but also after suspend, during connecting to wifi, I'd get loads of the `iwlwifi :3b:00.0: Unhandled alg: 0x71b` messages and the display would also freeze for couple of seconds (10 - 20). During this specific freeze, the mouse pointer would also be unresponsive. This would be accompanied by loads of messages in the kernel log like: nouveau :01:00.0: fifo: SCHED_ERROR 08 [] I managed to fix this by adding nouveau.modeset=0 to the kernel command line. Like I said, I don't know if these are related. Does the i915 GPU hang also occur on laptops without a nvidia gpu? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871867 Title: i915: GPU HANG: ecode 9:0:0x, hang on rcs0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871867/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871867] Re: i915: GPU HANG: ecode 9:0:0x00000000, hang on rcs0
Another remark: I already enabled -propsed for Eoan to see if that includes an updated, therefore I'm now running linux- image-5.3.0-47-generic from eoan-proposed. I had the exact same problems while running the kernel from the main repo linux- image-5.3.0-46-generic. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871867 Title: i915: GPU HANG: ecode 9:0:0x, hang on rcs0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871867/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871867] [NEW] i915: GPU HANG: ecode 9:0:0x00000000, hang on rcs0
Public bug reported: I just installed Kubuntu 19.10 on my brand new Dell XPS 15 7590 laptop. The display freezes quite regularly for a couple of seconds. In that period, the mouse pointer does move, but nothing else happens: I cannot interact, move windows, scroll, type or whatever. Afterwards the system becomes responsive again. In the kernel log I see messages like: [ 2110.867998] i915 :00:02.0: GPU HANG: ecode 9:0:0x, hang on rcs0 [ 2110.869007] i915 :00:02.0: Resetting rcs0 for hang on rcs0 [ 2120.523573] iwlwifi :3b:00.0: Unhandled alg: 0x71b [ 2146.443128] iwlwifi :3b:00.0: Unhandled alg: 0x71b [ 2173.551329] iwlwifi :3b:00.0: Unhandled alg: 0x71b [ 2204.008717] iwlwifi :3b:00.0: Unhandled alg: 0x71b [ 4404.960469] i915 :00:02.0: Resetting rcs0 for hang on rcs0 [ 6020.935285] i915 :00:02.0: Resetting rcs0 for hang on rcs0 I found that this problem occurs significantly more frequent when I'm using Jetbrains IntelliJ IDE, but I did experience it in several other occassions as well. I found similar reports both in UBuntu as other places that seem to be related: https://bugs.launchpad.net/ubuntu/+source/linux-signed-5.4/+bug/1863087 https://bugs.freedesktop.org/show_bug.cgi?id=111805 https://bugs.archlinux.org/task/64725 https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1862865 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861395 The ones on Launchpad are marked as invalid for Eoan and only apply for Focal. The XPS 7590 has a Intel chip and nvidia chip, I'm experiencing the problem both with and without the nvidia driver loaded. I ran apport when it wasn't loaded to make sure the kernel isn't tainted with it. Based on the feedback I see that this may be fixed in the most recent releases of kernel 5.4 (>= 5.4.0-17) but I don't see a proper way to install this in Eoan. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-47-generic 5.3.0-47.39 ProcVersionSignature: Ubuntu 5.3.0-47.39-generic 5.3.18 Uname: Linux 5.3.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: evdwal 1280 F pulseaudio CurrentDesktop: KDE Date: Thu Apr 9 17:25:04 2020 InstallationDate: Installed on 2020-04-06 (2 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. XPS 15 7590 ProcFB: 0 i915drmfb ProcKernelCmdLine: \\vmlinuz-5.3.0-47-generic root=/dev/mapper/vgkubuntu-root ro quiet splash net.ifnames=0 biosdevname=0 vt.handoff=7 initrd=\initrd.img-5.3.0-47-generic RelatedPackageVersions: linux-restricted-modules-5.3.0-47-generic N/A linux-backports-modules-5.3.0-47-generic N/A linux-firmware1.183.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.name: 0VYV0G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd12/25/2019:svnDellInc.:pnXPS157590:pvr:rvnDellInc.:rn0VYV0G:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 7590 dmi.product.sku: 0905 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug eoan package-from-proposed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871867 Title: i915: GPU HANG: ecode 9:0:0x, hang on rcs0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871867/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823004] Re: Upgrade to 19.04 - cannot install 'install-info' (triggers looping)
Anyone lucky enough to find any fixes to this? I faced this issue too yesterday. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823004 Title: Upgrade to 19.04 - cannot install 'install-info' (triggers looping) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1823004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1761844] Re: Very large emojis displayed in subject line and in the email list
Just in to be fair to Canonical or even Thunderbird Developers and their people it is impossible to test an application for every bug that may arise. How would you see and test an emoji email would you even think of it. There are so many things that take place when you start your email client. I am sure emoji's in emails would be the last thing they would think of testing. To give you an example just look at Microsoft and Windows 10 or 7 how often do updates get released and something breaks. I'm sure Microsoft do their best to test their updates but sometimes these things just slip through because of a conflict with the app or the operating system. Having said that Thunderbird 60.1 will be released any day now and this bug has been fixed in that release. You will be able to update directly from your current email client to the new one. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1761844 Title: Very large emojis displayed in subject line and in the email list To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1761844/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1774900] Re: prime-select wont select intel chip
Seems to be intermittent, or a once off. Repeating the reboot has me back on the intel card. I'll come back to this if I can get it to replicate. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1774900 Title: prime-select wont select intel chip To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-384/+bug/1774900/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1774900] [NEW] prime-select wont select intel chip
Public bug reported: Recently started experiencing issue where prime-select wont activate the intel card. Hard to pinpoint when this changed occured, as I usually use the intel card, and switching requires a reboot (the machine hangs if I do a simple logout/login or "systemctl restart lightdm.service"). dave@dave-mate:~$ sudo prime-select nvidia Info: the current GL alternatives in use are: ['nvidia-384-prime', 'nvidia-384-prime'] Info: the current EGL alternatives in use are: ['nvidia-384-prime', 'nvidia-384-prime'] Info: selecting nvidia-384 for the nvidia profile update-alternatives: using /usr/lib/nvidia-384/ld.so.conf to provide /etc/ld.so.conf.d/x86_64-linux-gnu_GL.conf (x86_64-linux-gnu_gl_conf) in manual mode update-alternatives: using /usr/lib/nvidia-384/ld.so.conf to provide /etc/ld.so.conf.d/x86_64-linux-gnu_EGL.conf (x86_64-linux-gnu_egl_conf) in manual mode update-alternatives: using /usr/lib/nvidia-384/alt_ld.so.conf to provide /etc/ld.so.conf.d/i386-linux-gnu_GL.conf (i386-linux-gnu_gl_conf) in manual mode update-alternatives: using /usr/lib/nvidia-384/alt_ld.so.conf to provide /etc/ld.so.conf.d/i386-linux-gnu_EGL.conf (i386-linux-gnu_egl_conf) in manual mode dave@dave-mate:~$ sudo prime-select intel Info: the current GL alternatives in use are: ['nvidia-384', 'nvidia-384'] Info: the current EGL alternatives in use are: ['nvidia-384', 'nvidia-384'] Info: selecting nvidia-384-prime for the intel profile update-alternatives: using /usr/lib/nvidia-384-prime/ld.so.conf to provide /etc/ld.so.conf.d/x86_64-linux-gnu_GL.conf (x86_64-linux-gnu_gl_conf) in manual mode update-alternatives: using /usr/lib/nvidia-384-prime/ld.so.conf to provide /etc/ld.so.conf.d/x86_64-linux-gnu_EGL.conf (x86_64-linux-gnu_egl_conf) in manual mode update-alternatives: using /usr/lib/nvidia-384-prime/alt_ld.so.conf to provide /etc/ld.so.conf.d/i386-linux-gnu_GL.conf (i386-linux-gnu_gl_conf) in manual mode update-alternatives: using /usr/lib/nvidia-384-prime/alt_ld.so.conf to provide /etc/ld.so.conf.d/i386-linux-gnu_EGL.conf (i386-linux-gnu_egl_conf) in manual mode dave@dave-mate:~$ lsb_release -rd Description:Ubuntu 16.04.4 LTS Release:16.04 dave@dave-mate:~$ apt-cache policy nvidia-384 nvidia-384: Installed: 384.130-0ubuntu0.16.04.1 Candidate: 384.130-0ubuntu0.16.04.1 Version table: *** 384.130-0ubuntu0.16.04.1 500 500 http://pg.archive.ubuntu.com/ubuntu xenial-updates/restricted amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/restricted amd64 Packages 100 /var/lib/dpkg/status ** Affects: nvidia-graphics-drivers-384 (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Using the NVIDIA GUI, this message appears." https://bugs.launchpad.net/bugs/1774900/+attachment/5148359/+files/Screenshot%20at%202018-06-04%2009-27-38.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1774900 Title: prime-select wont select intel chip To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-384/+bug/1774900/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1761844] Re: Very large emojis displayed in subject line and in the email list
The fix by bugrasan works OK and gets the emojis down to normal size however the emoji's are no longer colour but black and white. This is at least a good workaround for the time being. I think you will find this problem will be fixed in a later version of Thunderbird. I downloaded Thunderbird 60 Beta tar.bz2 from their website. Without actually installing it I extracted the folder and ran that version of Thunderbird from within that folder. It will automatically pick up you settings and email addresses etc from the version you have installed. It worked fine and the emojis contained in this version of Thunderbird are of normal size and are coloured. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1761844 Title: Very large emojis displayed in subject line and in the email list To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1761844/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1761844] Re: Thunderbird: emojis is displayed in the email list
I can confirm I too have this problem. Three pc's running ubuntu 18.04 and all have the same problem in thunderbird. This was not present running thunderbird on Ubuntu 16.04. This problem does not replicate on thunderbird in Windows. It would appear that it is Operating System specific. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1761844 Title: Thunderbird: emojis is displayed in the email list To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1761844/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1748895] Re: LO unable to find a working email configuration
Confirm fixed under latest libreOffice update, and Ubuntu MATE 16.04 Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1748895 Title: LO unable to find a working email configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1748895/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1748895] Re: LO unable to find a working email configuration
apt policy libreoffice-common libreoffice-common: Installed: 1:6.0.1~rc1-0ubuntu0.16.04.1~lo1 Candidate: 1:6.0.1~rc1-0ubuntu0.16.04.1~lo1 Version table: *** 1:6.0.1~rc1-0ubuntu0.16.04.1~lo1 500 500 http://ppa.launchpad.net/libreoffice/ppa/ubuntu xenial/main amd64 Packages 500 http://ppa.launchpad.net/libreoffice/ppa/ubuntu xenial/main i386 Packages 100 /var/lib/dpkg/status 1:5.1.6~rc2-0ubuntu1~xenial3 500 500 http://au.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://au.archive.ubuntu.com/ubuntu xenial-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main i386 Packages 1:5.1.2-0ubuntu1 500 500 http://au.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 500 http://au.archive.ubuntu.com/ubuntu xenial/main i386 Packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1748895 Title: LO unable to find a working email configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1748895/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1748895] Re: LO unable to find a working email configuration
Still present with LO6 and Thunderbird on Ubuntu 16.04.03 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1748895 Title: LO unable to find a working email configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1748895/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1504362] Re: Desktop flashes briefly on resume before going to lock screen
*** This bug is a duplicate of bug 1532508 *** https://bugs.launchpad.net/bugs/1532508 I can also confirm that this bug is still present on Ubuntu 16.04.3. When screen is resuming from being blank it will randomly continue to flicker to a black screen then back. This might only happen once in every 10 resume sessions however it does happen. When this is happening if I click my mouse it will fix it and it will be normal again. This was not present on an earlier version of Ubuntu the first release 16.04. I have tried the following 1. Reinstalling Ubuntu 2. Downgrading to an earlier kernel however nothing seems to fix it and the bug is still there. My Specs are as follows: Processor: AMD A8-7650K Radeon R7, 10 Compute Cores 4C+6G × 4 Graphics: AMD KAVERI (DRM 2.49.0 / 4.10.0-40-generic, LLVM 5.0.0) OS: Ubuntu 16.04.3 64-bit -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1504362 Title: Desktop flashes briefly on resume before going to lock screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1504362/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1691741] Re: Execute NX-protected page - 4.4.0-78-generic - kernel panic
Still no crashes seen with 4.4.0-79-generic (and newer versions). Would consider this fixed then. ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1691741 Title: Execute NX-protected page - 4.4.0-78-generic - kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1691741/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1691741] Re: Execute NX-protected page - 4.4.0-78-generic - kernel panic
** Tags added: kernel-unable-to-test-upstream -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1691741 Title: Execute NX-protected page - 4.4.0-78-generic - kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1691741/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1691741] Re: Execute NX-protected page - 4.4.0-78-generic - kernel panic
Due to the nature of the data on the machine and the fact that I don't know what apport will send, I'm unable to execute the apport-collect. # Some data from /usr/bin/crash: KERNEL: /usr/lib/debug/boot/vmlinux-4.4.0-78-generic DUMPFILE: dump.201705181342 [PARTIAL DUMP] CPUS: 4 DATE: Thu May 18 13:42:12 2017 UPTIME: 00:16:34 LOAD AVERAGE: 0.21, 0.05, 0.01 TASKS: 547 NODENAME: RELEASE: 4.4.0-78-generic VERSION: #99-Ubuntu SMP Thu Apr 27 15:29:09 UTC 2017 MACHINE: x86_64 (2199 Mhz) MEMORY: 16 GB PANIC: "BUG: unable to handle kernel paging request at 88042a284000" PID: 0 COMMAND: "swapper/1" TASK: 88042a278000 (1 of 4) [THREAD_INFO: 88042a28] CPU: 1 STATE: TASK_RUNNING (PANIC) # crash> bt PID: 0 TASK: 88042a278000 CPU: 1 COMMAND: "swapper/1" #0 [88042a283b78] machine_kexec at 8105c0db #1 [88042a283bd8] crash_kexec at 8110e572 #2 [88042a283ca8] oops_end at 81031c49 #3 [88042a283cd0] no_context at 8106ad35 #4 [88042a283d30] __bad_area_nosemaphore at 8106b000 #5 [88042a283d78] bad_area_nosemaphore at 8106b183 #6 [88042a283d88] __do_page_fault at 8106b447 #7 [88042a283de0] trace_do_page_fault at 8106b7f7 #8 [88042a283e10] do_async_page_fault at 81063ef9 #9 [88042a283e20] async_page_fault at 81842be8 #10 [88042a283e38] tick_nohz_idle_exit at 810ff75e #11 [88042a283ed8] cpu_startup_entry at 810c4736 #12 [88042a283f30] start_secondary at 810517c4 # crash> bt -f # #9 [88042a283e20] async_page_fault at 81842be8 88042a283e28: 88042a28 88042a283e38: 810ff75e #10 [88042a283e38] tick_nohz_idle_exit at 810ff75e 88042a283e40: 88042a283ed0 81f38d40 88042a283e50: 00e797438af0 4c00 88042a283e60: 00010002a665 88042a283e70: 000a 0001 88042a283e80: 0001 88042a283e90: 0083 0083 88042a283ea0: 88042a284000 88042a283eb0: 0010 00010082 88042a283ec0: 88042a283ed0 0018 88042a283ed0: 88042a283f28 810c4736 #11 [88042a283ed8] cpu_startup_entry at 810c4736 88042a283ee0: 88042a28 88042a284000 88042a283ef0: ee041b0196f77cc4 a1abbcd2b8b123ce 88042a283f00: 88042a283f10: 88042a283f20: 88042a283f48 88042a283f30: 810517c4 #12 [88042a283f30] start_secondary at 810517c4 # crash> dis tick_nohz_idle_exit 0x810ff74f: mov%r12,0xa8(%rbx) 0x810ff756 : mov%r12,%rsi 0x810ff759 : callq 0x810ff170 0x810ff75e : mov0xd0989b(%rip),%rdi # 0x81e09000 0x810ff765 : sub0x78(%rbx),%rdi # lsmod info's Module Size Used by zfs 2813952 5 zunicode 331776 1 zfs zcommon57344 1 zfs znvpair90112 2 zfs,zcommon spl 102400 3 zfs,zcommon,znvpair zavl 16384 1 zfs ppdev 20480 0 input_leds 16384 0 shpchp 36864 0 serio_raw 16384 0 i2c_piix4 24576 0 8250_fintek16384 0 parport_pc 32768 0 parport49152 2 ppdev,parport_pc mac_hid16384 0 autofs440960 2 ttm94208 0 drm_kms_helper155648 0 syscopyarea16384 1 drm_kms_helper sysfillrect16384 1 drm_kms_helper sysimgblt 16384 1 drm_kms_helper fb_sys_fops16384 1 drm_kms_helper psmouse 131072 0 drm 364544 2 ttm,drm_kms_helper pata_acpi 16384 0 floppy 73728 0 No idea if this is useful though. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1691741 Title: Execute NX-protected page - 4.4.0-78-generic - kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1691741/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1691741] [NEW] Execute NX-protected page - 4.4.0-78-generic - kernel panic
Public bug reported: After upgrading from 4.4.0-77 to 4.4.0-78 I started getting kernel panics. The crashes do not happen immediately, but have happened generally after a couple of minutes, sometimes more. After enabling linux-crashdump stuff, I managed to extract this dmesg. [ 995.103846] kernel tried to execute NX-protected page - exploit attempt? (uid: 0) [ 995.104141] BUG: unable to handle kernel paging request at 88042a284000 [ 995.104407] IP: [] 0x88042a284000 [ 995.104594] PGD 43f20b067 PUD 43f20e067 PMD 42a3da063 PTE 80042a284163 [ 995.104946] Oops: 0011 [#1] SMP [ 995.105143] Modules linked in: zfs(PO) zunicode(PO) zcommon(PO) znvpair(PO) spl(O) zavl(PO) ppdev input_leds shpchp serio_raw i2c_piix4 mac_hid parport_pc parport 8250_fintek autofs4 ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm psmouse floppy pata_acpi [ 995.107081] CPU: 1 PID: 0 Comm: swapper/1 Tainted: P O 4.4.0-78-generic #99-Ubuntu [ 995.107299] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.9.3-0-ge2fc41e-prebuilt.qemu-project.org 04/01/2014 [ 995.107573] task: 88042a278000 ti: 88042a28 task.ti: 88042a28 [ 995.108070] RIP: 0010:[] [] 0x88042a284000 [ 995.108637] RSP: 0018:88042a283ed0 EFLAGS: 00010082 [ 995.109116] RAX: 0001 RBX: 00e797438af0 RCX: [ 995.109638] RDX: 0001 RSI: 0083 RDI: 0083 [ 995.110143] RBP: 81f38d40 R08: 000a R09: [ 995.110665] R10: 00010002a665 R11: 4c00 R12: 88042a283ed0 [ 995.82] R13: 810ff75e R14: R15: 88042a28 [ 995.111733] FS: () GS:88043fc8() knlGS: [ 995.112486] CS: 0010 DS: ES: CR0: 8005003b [ 995.112978] CR2: 88042a284000 CR3: 00043d246000 CR4: 06e0 [ 995.113497] DR0: DR1: DR2: [ 995.114085] DR3: DR6: fffe0ff0 DR7: 0400 [ 995.114612] Stack: [ 995.114965] 88042a283f28 810c4736 88042a28 88042a284000 [ 995.116204] ee041b0196f77cc4 a1abbcd2b8b123ce [ 995.117389] 88042a283f48 [ 995.118425] Call Trace: [ 995.118811] [] ? cpu_startup_entry+0x176/0x350 [ 995.119293] [] ? start_secondary+0x154/0x190 [ 995.119775] Code: ff ff ff 00 00 00 00 00 00 00 00 10 00 00 00 00 00 00 00 02 02 00 00 00 00 00 00 58 3f 28 2a 04 88 ff ff 18 00 00 00 00 00 00 00 8c 27 2a 04 88 ff ff 00 00 00 00 00 00 00 00 02 00 00 00 00 [ 995.125554] RIP [] 0x88042a284000 [ 995.126088] RSP [ 995.126453] CR2: 88042a284000 I've upgraded other machines as well, and only this particular VM shows this behaviour. I have a crash dump, but I haven't looked into the contents yet. Getting the dmesg was already a pain in the behind. The VM this happens on is: - a KVM guest - x86_64, 4 cores - 16gb ram lsb_release: Distributor ID: Ubuntu Description:Ubuntu 16.04.2 LTS Release:16.04 Codename: xenial lspci says: 00:00.0 Host bridge: Intel Corporation 440FX - 82441FX PMC [Natoma] (rev 02) 00:01.0 ISA bridge: Intel Corporation 82371SB PIIX3 ISA [Natoma/Triton II] 00:01.1 IDE interface: Intel Corporation 82371SB PIIX3 IDE [Natoma/Triton II] 00:01.2 USB controller: Intel Corporation 82371SB PIIX3 USB [Natoma/Triton II] (rev 01) 00:01.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 03) 00:02.0 VGA compatible controller: VMware SVGA II Adapter 00:03.0 Unclassified device [00ff]: Red Hat, Inc Virtio memory balloon 00:0a.0 SCSI storage controller: Red Hat, Inc Virtio block device 00:0b.0 SCSI storage controller: Red Hat, Inc Virtio block device 00:12.0 Ethernet controller: Red Hat, Inc Virtio network device 00:1e.0 PCI bridge: Red Hat, Inc. QEMU PCI-PCI bridge 00:1f.0 PCI bridge: Red Hat, Inc. QEMU PCI-PCI bridge Let me know if there are other helpful details I can provide. If I find out more, I'll update this ticket. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1691741 Title: Execute NX-protected page - 4.4.0-78-generic - kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1691741/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1166529] Re: Creative Recon3d & Sound Blaster Z (CA0132), No Sound At All; Broken Beyond All Repair
I just gave up and got me a Asus Xonar sound card and disabled the onboard. Works a treat! The longer I worked with it, the more I got convinced it's a crappy chip. Even in Windows 10 it doesn't work properly - sometimes the volume levels are ignored or attached to different outputs than they should be. Also, when I started Ubuntu 16.04 once, I needed to completely shut down the computer - if I just reboot to Windows it will also not work in Windows. After a shut down it usually works again. I have no clue what this chip is doing and how it's interacting with the driver on Linux, but it's bad. Very bad. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1166529 Title: Creative Recon3d & Sound Blaster Z (CA0132), No Sound At All; Broken Beyond All Repair To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1166529/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1166529] Re: Creative Recon3d & Sound Blaster Z (CA0132), No Sound At All; Broken Beyond All Repair
I have the same issue: no sound on a Recon3D / CA0132. The sound chip is an onboard chip labelled Sound Core 3D, the motherboard is a GA-X170-Extreme ECC. This is on Ubuntu 16.04. Alsa / Pulseaudio claim everything is good, but there's no sound coming out of it at all. dmesg | grep hda shows: [7.200088] snd_hda_intel :00:1f.3: enabling device ( -> 0002) [7.200197] snd_hda_intel :01:00.1: enabling device ( -> 0002) [7.200226] snd_hda_intel :01:00.1: Handle vga_switcheroo audio client [7.241033] snd_hda_intel :00:1f.3: failed to add i915_bpo component master (-19) [7.252621] snd_hda_codec_ca0132 hdaudioC0D0: autoconfig for CA0132: line_outs=1 (0xb/0x0/0x0/0x0/0x0) type:line [7.252623] snd_hda_codec_ca0132 hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [7.252625] snd_hda_codec_ca0132 hdaudioC0D0:hp_outs=1 (0x10/0x0/0x0/0x0/0x0) [7.252626] snd_hda_codec_ca0132 hdaudioC0D0:mono: mono_out=0x0 [7.252627] snd_hda_codec_ca0132 hdaudioC0D0:dig-out=0xc/0x0 [7.252628] snd_hda_codec_ca0132 hdaudioC0D0:inputs: [7.252629] snd_hda_codec_ca0132 hdaudioC0D0: Mic=0x12 [7.252630] snd_hda_codec_ca0132 hdaudioC0D0: Line=0x11 [7.503386] snd_hda_codec_generic hdaudioC1D0: ignore pin 0x6, too many assigned pins [7.511395] snd_hda_codec_generic hdaudioC1D0: ignore pin 0x7, too many assigned pins [7.511398] snd_hda_codec_generic hdaudioC1D0: autoconfig for Generic: line_outs=0 (0x0/0x0/0x0/0x0/0x0) type:line [7.511399] snd_hda_codec_generic hdaudioC1D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [7.511400] snd_hda_codec_generic hdaudioC1D0:hp_outs=0 (0x0/0x0/0x0/0x0/0x0) [7.511400] snd_hda_codec_generic hdaudioC1D0:mono: mono_out=0x0 [7.511401] snd_hda_codec_generic hdaudioC1D0:dig-out=0x4/0x5 [7.511402] snd_hda_codec_generic hdaudioC1D0:inputs: [7.847710] snd_hda_codec_ca0132 hdaudioC0D0: ca0132 DSP downloaded and running [8.711805] snd_hda_codec_ca0132 hdaudioC0D0: ca0132 DSP downloaded and running I tried blacklisting snd-hda-codec-hdmi, which didn't work so I ended up removing the file from lib/modules/*/ altogether. Didn't help. I also tried adding enable_msi=1 and/or position_fix=1 to /etc/modprobe.d/alsa-base.conf, neither of them worked. Even though the dmesg now no longer states that MSI is being disabled for snd_hda_intel. Maybe relevant: the motherboard has a HDMI-out (which doesn't work because I don't have a iGPU on my processor), and the videocard (Gigabyte NVidia GTX 1070 G1 Gaming) also has a HDMI-output which is also bound to snd-hda-intel. (Relevant) output of lspci -k: 00:1f.3 Audio device: Intel Corporation Sunrise Point-H HD Audio (rev 31) Subsystem: Gigabyte Technology Co., Ltd Sunrise Point-H HD Audio Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 01:00.0 VGA compatible controller: NVIDIA Corporation Device 1b81 (rev a1) Subsystem: Gigabyte Technology Co., Ltd Device 3701 Kernel driver in use: nvidia Kernel modules: nvidiafb, nouveau, nvidia_367, nvidia_367_drm 01:00.1 Audio device: NVIDIA Corporation Device 10f0 (rev a1) Subsystem: Gigabyte Technology Co., Ltd Device 3701 Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel The first one must be the onboard chip, the second one the graphics part of the nvidia card and the third one the HDMI port on the nvidia card. Is there any way to prevent snd_hda_intel from binding to the HDMI ports? I have no interest in audio over HDMI, so I'd be happy to disable it to see if that helps. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1166529 Title: Creative Recon3d & Sound Blaster Z (CA0132), No Sound At All; Broken Beyond All Repair To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1166529/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1569383] Re: Intel HD Graphics 530 crashes on glxinfo in MSHYBRID mode
Just to update: where I said 'turned off by default' I realized I don't actually know what I'm talking about. I never had a Optimus-laptop before, and I never worked with Bumblebee or the like. Therefore I don't know what the state is, and/or how this is supposed to work. Ideally, of course, the nvidia-card would power up and down based on graphic load or application profiles, just like in Windows, but I'm thinking that's not going to happen for a while. With the current situation where you need to switch in between login sessions, at least I'd expect that if I used prime-select or nvidia- settings to switch to IGP, it would actually turn off the nvidia card. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1569383 Title: Intel HD Graphics 530 crashes on glxinfo in MSHYBRID mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1569383/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1569383] Re: Intel HD Graphics 530 crashes on glxinfo in MSHYBRID mode
You're right, my nvidia card is not turned off. /rpco/acpi/bbswitch listed it as on. Battery usage was better than before, though. Maybe because when not actually using the GPU, it at least scales down to a lower frequency, conserving power (because an additional issue, most likely related to the nvidia drivers, is that the nvidia card always runs at max speed and never turns down. Maybe this is because I'm using a UHD display, not sure. No way to check when running in IGP-mode). Running the command rmmod nvidia_drm nvidia_modeset nvidia_uvm nvidia gives me a notice that nvidia_uvm is not loaded but does unload the other modules. After that I am able to turn off the nvidia card using the command you provided. Battery usage then drops from around 32 Watts to around 19 Watts in idle, so that's a significant improvement. I can't reproduce your crashes when running lshw or lspci, though, they all run fine, even after turning off the nvidia card. Also running something like phoronix-test-suite is fine, the system remains stable. Maybe that's a difference in kernel and/or nvidia driver versions? I've tested using both linux kernel 4.6.0-040600-generic (4.6.0-040600.201605151930) and 4.4.0-23-generic (4.4.0-23.41), using nvidia-364 (364.19-0ubuntu0~gpu16.04.3). Would be very useful / good for battery performance if the nvidia card would be turned off by default. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1569383 Title: Intel HD Graphics 530 crashes on glxinfo in MSHYBRID mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1569383/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1569383] Re: Intel HD Graphics 530 crashes on glxinfo in MSHYBRID mode
I just installed kernel 4.4.0-23.41 from xenial-proposed and it seems to include whatever alleviated this issue. My laptop isn't crashing anymore. There is the occasional glitch: sometimes when I enter my password at the login screen, the screen will actually not redraw at stay at the login screen while the contents seem to have changed. Moving my mouse cursor actually changes the cursor depending on what should be underneath. Switching to anther VT and back to X.org redraws the screen and fixes it. Also the title bar sometimes gets garbled. Moving or resizing the window fixes that. I did h experience these issues with 4.6 too, by the way. All in all, it's definitely usable this way! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1569383 Title: Intel HD Graphics 530 crashes on glxinfo in MSHYBRID mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1569383/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1569383] Re: Intel HD Graphics 530 crashes on glxinfo in MSHYBRID mode
FWIW: today I installed kernel 4.6.0-040600-generic from http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-yakkety/ on my Kubuntu Xenial setup. On this kernel version the nvidia-drivers I was using, nvidia-361, didn't work anymore (it said that kernel 4.6.0 was not supported), so I upgraded to nvidia-464 from https://launchpad.net /~graphics-drivers After this I had one more glitch, that is that even though nouveau is listed in /etc/modprobe.d/nvidia-graphics-drivers.conf as blacklist nouveau blacklist lbm-nouveau it would still be loaded, preventing the nvidia driver from working properly. By adding nouveau.blacklist=1 to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub I could prevent it from loading. Using this combination, I now have a fully working optimus setup. I can switch using nvidia-settings between nvidia and intel graphics and both run equally stable. It seems this issue was fixed in kernel 4.6.0 (possibly related to kernel bug https://bugzilla.kernel.org/show_bug.cgi?id=109081). I'm fairly certain that the newer nvidia driver doesn't influence it as even without that, the intel driver would work fine on 4.6.0. I just couldn't switch to the nvidia GPU. Will kernel 4.6.x make it into Xenial at some point? It seems that it's might be required for Skylake laptops to work completely. ** Bug watch added: Linux Kernel Bug Tracker #109081 http://bugzilla.kernel.org/show_bug.cgi?id=109081 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1569383 Title: Intel HD Graphics 530 crashes on glxinfo in MSHYBRID mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1569383/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1569674] Re: [Kubuntu] Fail to connect to wifi after a recent update
I just was struck by this bug too. Very annoying. Thankfully, plugging in a network cable gave me a working internet connection so I was able execute the downgrade as suggested in #39 without too much hassle. It's quite a serious show stopper bug that is hard to fix because it breaks the connection you need in order to fix it! Thanks Ovidiu-Florin BOGDAN for the workaround. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1569674 Title: [Kubuntu] Fail to connect to wifi after a recent update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/networkmanager-qt/+bug/1569674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1569880] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1569880/+attachment/4635554/+files/JournalErrors.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1569880 Title: Touchpad not always enabled after a suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1569880/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1569880] Re: Touchpad not always enabled after a suspend
apport information ** Tags added: apport-collected ** Description changed: On my laptop (Clevo P650RA) the touchpad is not always enabled after a suspend. I have worked around this by creating /etc/systemd/system/trackpad.service that runs a script in /etc/pm/sleep.d/ that re-enables the trackpad by doing: DISPLAY=:0.0 /bin/su -c '/usr/bin/xinput set-prop "SynPS/2 Synaptics TouchPad" "Device Enabled" 1' >> /var/log/touchpad.log For some reason, the 'Device Enabled' flag is set to 0 during suspend, and it sometimes is not automatically re-enabled (but then again, sometimes it is). I tried reporting this using 'ubuntu-bug xserver-xorg-input-evdev' like instructed, but unfortunately, ubuntu-bug seems to segfault while attempting to report the bug. + --- + ApportVersion: 2.20.1-0ubuntu1 + Architecture: amd64 + DistroRelease: Ubuntu 16.04 + InstallationDate: Installed on 2016-04-12 (1 days ago) + InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) + NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia + Package: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 + PackageArchitecture: amd64 + ProcEnviron: + LANGUAGE= + TERM=xterm + PATH=(custom, no user) + LANG=nl_NL.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 + Tags: xenial + Uname: Linux 4.4.0-18-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1569880/+attachment/4635553/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1569880 Title: Touchpad not always enabled after a suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1569880/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1569880] [NEW] Touchpad not always enabled after a suspend
Public bug reported: On my laptop (Clevo P650RA) the touchpad is not always enabled after a suspend. I have worked around this by creating /etc/systemd/system/trackpad.service that runs a script in /etc/pm/sleep.d/ that re-enables the trackpad by doing: DISPLAY=:0.0 /bin/su -c '/usr/bin/xinput set-prop "SynPS/2 Synaptics TouchPad" "Device Enabled" 1' >> /var/log/touchpad.log For some reason, the 'Device Enabled' flag is set to 0 during suspend, and it sometimes is not automatically re-enabled (but then again, sometimes it is). I tried reporting this using 'ubuntu-bug xserver-xorg-input-evdev' like instructed, but unfortunately, ubuntu-bug seems to segfault while attempting to report the bug. ** Affects: xserver-xorg-input-evdev (Ubuntu) Importance: Undecided Status: New ** Tags: evdev suspend touchpad xenial xorg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1569880 Title: Touchpad not always enabled after a suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1569880/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1569383] Re: Intel HD Graphics 530 crashes on glxinfo in MSHYBRID mode
** Package changed: xorg (Ubuntu) => xserver-xorg-video-intel (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1569383 Title: Intel HD Graphics 530 crashes on glxinfo in MSHYBRID mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1569383/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1569383] Re: Intel HD Graphics 530 crashes on glxinfo in MSHYBRID mode
Update: since it's quite hard to gather more information, I tried pinging the laptop from another machine. The moment I enter 'glxinfo' on the laptop it stops responding to the ping requests, so it seems not only the GUI freezes but the entire kernel. In addition, I have installed linux-crashdump but it doens't seem to do anything in this case, no linux-image-* is generated in /var/crash and no kexec console is opened at freeze. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1569383 Title: Intel HD Graphics 530 crashes on glxinfo in MSHYBRID mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1569383/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1569383] Re: Intel HD Graphics 530 crashes on glxinfo in MSHYBRID mode
It also freezes when closing the lid -> attempting to suspend. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1569383 Title: Intel HD Graphics 530 crashes on glxinfo in MSHYBRID mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1569383/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1569383] [NEW] Intel HD Graphics 530 crashes on glxinfo in MSHYBRID mode
Public bug reported: On my laptop (Clevo P650RA) with Skylake / Intel Core i7 6700HQ with Intel HD Graphics 530 IGP and a nvidia GTX965M DGP, glxinfo crashes when running in IGP mode, The laptop uses Optimus / MSHYBRID technology to be able to utilize both IGP and DGP. After setup I install nvidia-361 driver, which will make the system run using DGP mode by default. Using prime-select intel I can switch to using the IGP. After logging out and in again, the IGP is being used. However, when doing certain tasks, the system will crash. Running glxinfo is one of them. Another one is: cat /proc/acpi/bbswitch In addition, it sometimes seemingly at random, probably when some kind of desktop effect is performed. It seems that some kind of interaction with ACPI / IGP will make it crash. This is running Kubuntu 16.04 Xenial Beta 2. Some version numbers: Kernel version (uname -r): 4.4.0-18-generic linux-image-4.4.0-18-generic: 4.4.0-18.34 xserver-xorg-core: 2:1.18.3-1ubuntu2 xserver-xorg-video-intel: 2:2.99.917+git20160325-1ubuntu1 sddm: 0.13.0-1ubuntu5 plasma-desktop: 4:5.5.4-0ubuntu1 lsb_release -a: Distributor ID: Ubuntu Description:Ubuntu Xenial Xerus (development branch) Release:16.04 Codename: xenial I'll attach a kern.log and a Xorg.0.log from a Intel IGP session on this laptop. Please let me know if I should provide other information, and how to collect this after a full system freeze. ** Affects: ubuntu Importance: Undecided Status: New ** Tags: crash intel optimus prime ** Attachment added: "Xorg.0.log after a succesful login" https://bugs.launchpad.net/bugs/1569383/+attachment/4634217/+files/Xorg.successfull.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1569383 Title: Intel HD Graphics 530 crashes on glxinfo in MSHYBRID mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1569383/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1569383] Re: Intel HD Graphics 530 crashes on glxinfo in MSHYBRID mode
Here's the kern.log file ** Attachment added: "Kern.log when attempting to use IGP" https://bugs.launchpad.net/ubuntu/+bug/1569383/+attachment/4634218/+files/kern.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1569383 Title: Intel HD Graphics 530 crashes on glxinfo in MSHYBRID mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1569383/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1014240] Re: [Asus eeepc 1225B] Keyboard and Touchpad randomly not working at startup
Christopher, thanks for the explanation. However, I was under the impression that the automatic response was due to the fact that I changed state of this bug to 'new' (because it was set to 'expired' and I suffered from the same problem). I'm currently awaiting the problem but I haven't encountered it since I installed the latest kernel version in 16.04: 4.4.0-16-generic. If it occurs again, I will file a new report rather than post here. Thanks again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1014240 Title: [Asus eeepc 1225B] Keyboard and Touchpad randomly not working at startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1014240/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1014240] Re: [Asus eeepc 1225B] Keyboard and Touchpad randomly not working at startup
Right, I can give that a try, but it's a tad hard. I'll remove the i8042.reset flag and wait until it hangs again. Because the keyboard doesn't work in that case, I'll have to resolve it by doing another suspend/resume iteration and then will link the items. Since it's not predictable, it may take one or two days. In my case, you should add tag: xenial, rather than Precise, even though it seems to affect other releases too. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1014240 Title: [Asus eeepc 1225B] Keyboard and Touchpad randomly not working at startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1014240/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1014240] Re: [Asus eeepc 1225B] Keyboard and Touchpad randomly not working at startup
** Changed in: linux (Ubuntu) Status: Expired => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1014240 Title: [Asus eeepc 1225B] Keyboard and Touchpad randomly not working at startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1014240/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1014240] Re: [Asus eeepc 1225B] Keyboard and Touchpad randomly not working at startup
I had the same problem on my new laptop (Clevo P650RA), and adding 'i8042.reset' to GRUB_CMDLINE_LINUX_DEFAULT fixed it for me. Shouldn't this be enabled by default? This is on "Ubuntu Xenial Xerus (development branch) - Release: 16.04" by the way. My exact kernel error was: i8042: failed to resume active multiplexor, mouse won't work In that case, the mouse indeed didn't work, but neither did the touchpad. Closing the laptop lid, waiting for a couple of seconds for it to suspend again and reopening the laptop lid was a workaround to resolve the situation, but the i8042.reset takes away the need to do so. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1014240 Title: [Asus eeepc 1225B] Keyboard and Touchpad randomly not working at startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1014240/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1563307] [NEW] Pulseaudio keeps enabling optical output
Public bug reported: My laptop (Clevo P650RA) has a combined optical out (SPDIF) and headphone jack. The jack is continously emitting a red light for the optical output, even when I'm not using it (which is almost always). I can manually disable this by running 'alsamixer' and mute channel 'S/PDIF 16'. However, this state is not stored. After a reboot it is always re-enabled. I tried saving alsa mixer levels but this is ignored. Additionally, when switching output profiles from 'Analog Stereo Duplex' to 'Digital Stereo (IEC958)-output', the S/PDIF 16 channel is unmuted again and the red light turns on. But when I switch back to 'Analog Stereo Duplex', the S/PDIF 16 channel is not muted again and the red light remains. Reqeuested info: 1) Description:Ubuntu Xenial Xerus (development branch) - Release: 16.04 2) pulseaudio: 1:8.0-0ubuntu2 3) I expect the S/PDIF output to be muted until I explicitly request optical output. Even more preferable (seems to be possible at least on Mac OS X): optical out is enabled when a optical jack is inserted, otherwise it is always disabled. 4) S/PDIF light is nearly always on. Please let me know if you require additional information. I'll attach the output of 'aplay -L' and 'amixer controls'. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Attachment added: "alsa-mixer-controls.txt" https://bugs.launchpad.net/bugs/1563307/+attachment/4615887/+files/alsa-mixer-controls.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1563307 Title: Pulseaudio keeps enabling optical output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1563307/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1563307] Re: Pulseaudio keeps enabling optical output
** Attachment added: "alsa-aplay-list.txt" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1563307/+attachment/4615888/+files/alsa-aplay-list.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1563307 Title: Pulseaudio keeps enabling optical output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1563307/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1547431] Re: Does not allow appstream files
Just to confirm, works fine with Rolf's patch (tested on Trusty). Thanks Stefan taking away the need to build it myself :-). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1547431 Title: Does not allow appstream files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-cacher-ng/+bug/1547431/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 806032] Re: Fn + F[89] does not work for controlling brightness on Clevo laptops (B7130, W150HRM)
I'm not sure if this is still / again the same problem, but I have a very similar issue on a recently bought Clevo P650RA laptop, running Ubuntu Xenial / 16.04 and the similar bug search when reporting a new bug led me to this issue. The brightness keys do not work; setting the brightness manually through /sys/class/backlight/intel_backlight works fine. Probably related: in the BIOS I can select either MSHYBRID or DISCRETE for the GPU, meaning either Optimus-like-technology or DISCRETE only. When using DISCRETE, the brightness keys do work. However, in that case I'm forced to use the Nouveau driver since the nvidia driver will not work anymore. And the nouveau driver makes this laptop crash after a short while, so it's not really a viable alternative. When running in MSHYBRID, maybe there are more possible connected devices making this bug appear? There's also some ACPI Warnings in DMESG that may be related. I'll attach the output of dmesg to this message. Please let me know if I should report a new bug rather than necroposting in this old bug that appears to be resolved long ago. I'd be happy to provide more information if you point me in the right direction for obtaining that information. ** Attachment added: "dmesg.txt showing some ACPI warnings that may be related" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/806032/+attachment/4599404/+files/dmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/806032 Title: Fn + F[89] does not work for controlling brightness on Clevo laptops (B7130, W150HRM) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/806032/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1286779] Re: Please migrate libjetty-extra-java to tomcat7
The same thing is happening to me in Kubuntu Trusty: $ sudo apt-get install libjetty-extra-java Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libjetty-extra-java : Depends: libtomcat6-java (= 6.0.20-2) but it is not going to be installed E: Unable to correct problems, you have held broken packages. $ sudo apt-cache policy libjetty-extra-java libjetty-extra-java: Installed: (none) Candidate: 6.1.26-1ubuntu1 Version table: 6.1.26-1ubuntu1 0 500 http://nl.archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages Any idea on when this updated package will make its way to the official repositories? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1286779 Title: Please migrate libjetty-extra-java to tomcat7 To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1286779/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1335304] [NEW] package ifupdown 0.7~alpha5.1ubuntu5.1 failed to install/upgrade: ErrorMessage: subprocess new pre-installation script returned error exit status 4
Public bug reported: While doing a release upgrade from oneiric to precise ProblemType: Package DistroRelease: Ubuntu 12.04 Package: ifupdown 0.7~alpha5.1ubuntu5.1 Uname: Linux 3.0.17xls-domU+ x86_64 ApportVersion: 1.23-0ubuntu4.1 Architecture: amd64 Date: Fri Jun 27 21:39:09 2014 ErrorMessage: ErrorMessage: subprocess new pre-installation script returned error exit status 4 InstallationMedia: Ubuntu-Server 11.10 Oneiric Ocelot - Release amd64 (20111011) SourcePackage: ifupdown Title: package ifupdown 0.7~alpha5.1ubuntu5.1 failed to install/upgrade: ErrorMessage: subprocess new pre-installation script returned error exit status 4 UpgradeStatus: Upgraded to precise on 2014-06-27 (0 days ago) ** Affects: ifupdown (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package precise -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1335304 Title: package ifupdown 0.7~alpha5.1ubuntu5.1 failed to install/upgrade: ErrorMessage: subprocess new pre-installation script returned error exit status 4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1335304/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1303462] Re: [Regression] Window titlebars placed behind panel
I can confirm that the packages for this bug in proposed updates have fixed the problem. Once installed just logout and back in and the problem will be gone. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1303462 Title: [Regression] Window titlebars placed behind panel To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1303462/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1303462] Re: [Regression] Window titlebars placed behind panel
Thank You Whitaar that workaround worked like a charm and fixed all my misbehaving windows on all of my PC's. Your help is very much appreciated. Cheers Wal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1303462 Title: [Regression] Window titlebars placed behind panel To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1303462/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1303462] Re: [Regression] Window titlebars placed behind panel
This bug also affects Image Viewer. When pictures are opened and then the page maximised the maximise, minimise, close buttons slip up under the top panel and cannot be accessed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1303462 Title: [Regression] Window titlebars placed behind panel To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1303462/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1312057] [NEW] Minimise Maximise Close Button hidden under top taskbar Ubuntu 14.04
Public bug reported: Have Ubuntu 14.04 installed on a Desktop and a Laptop. Since installing I have noticed that when some pages when they are opened minimised usually by default, that Minimise, Maximise Close Buttons are hidden under the top taskbar and can not be accessed. This happens on both my PC's and probably affect others. I have found this happens so far with Libre office minimised window, XSane scan window, and with internet browsers when opening popup windows. To overcome this ALT X F7 will let you drag the page down after which you can do with it whatever you want. Can't find if this bug has been reported before but I must say it is somewhat annoying. I have noticed doing a google that others have had the same problem. ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1312057 Title: Minimise Maximise Close Button hidden under top taskbar Ubuntu 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1312057/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 45026] Re: K3b dont find emovix-2 and normalize
+1 for the bug, thanks for the workaround with the script. Someone please incorporate this into the package, this is ridiculous! -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/45026 Title: K3b dont find emovix-2 and normalize To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/k3b/+bug/45026/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1034470] Re: Mouse pointer flicker or disappear when moving it with left mouse button down
I can confirm that I have just installed th GMA3600 driver for the Acer Cedarview from the Proposed Restricted Releases Repository and this cursor proplem has been fixed with that update. This update has also fixed brightness and resolution problems that that go hand in hand with the cursor problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1034470 Title: Mouse pointer flicker or disappear when moving it with left mouse button down To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-fbdev/+bug/1034470/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1034470] Re: Mouse pointer flicker or disappear when moving it with left mouse button down
I too am using exactly the same netbook with Ubuntu 12.04 installed. I also have a similar problem with a cursor that flickers randomly and sometimes disappears for a short time. Particularly when hovering over website links or or icons particularly in System Settings. It can be quite annoying at times. Googling the problem it appears that some others are also having similar problems. I am aware that in Ubuntu there are no Graphics Card drivers for this particular Netbook as yet and as such it can only run in 2D mode. Maybe the issue is there with the Grapics Card. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1034470 Title: Mouse pointer flicker or disappear when moving it with left mouse button down To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-psb/+bug/1034470/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1019755] Re: Suddenly have to unlock keyring after each login
Yes I am getting similar behaviour. It only started yesterday. I will suddenly get the same message as above after I have been logged into my PC for about 20mins or so. It just comes out of nowhere. I don't use a password or keyring etc to login. But this message pops up out of nowhere after a short time. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1019755 Title: Suddenly have to unlock keyring after each login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1019755/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 818675] Re: Please package the latest version of solr (3.5.0)
Why is it even in the repositories if the current release is around 2 years old? The package should be dropped if noone is going to maintain it, because then at least it doesn't give the (false) impression that you can get an up to date version from the repository. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/818675 Title: Please package the latest version of solr (3.5.0) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/solr/+bug/818675/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 982485] Re: [regression] Nvidia 295.40: Unity 3D does not work at all with the new nvidia driver
Hi Madbiologist, I downloaded and installed the 295.49 driver from launchpad see post #152. Mine is running perfectly. I am running Ubuntu 12.04 with a Nvidia Geforce 7100 Graphics Card. I did not bother downloading from proposed as I already had a working driver. Not sure if you are just checking to see if the new update works or if you have downloaded it from proposed and found it doesn't work. If you have done the latter. Uninstall the previous driver then install 295.49. Hope this helps. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/982485 Title: [regression] Nvidia 295.40: Unity 3D does not work at all with the new nvidia driver To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/982485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 982485] Re: [regression] Nvidia 295.40: Unity 3D does not work at all with the new nvidia driver
Hi Evan if you are running 64 bit Ubuntu 12.04 precise go to the link below and download the 55.9MB Deb file. Once downloaded open it and install it it will automatically install through software centre. It does work and fixed all my problems with the previous driver. https://launchpad.net/~suraia/+archive/ppa/+build/3464331 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/982485 Title: [regression] Nvidia 295.40: Unity 3D does not work at all with the new nvidia driver To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/982485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 982485] Re: [regression] Nvidia 295.40: Unity 3D does not work at all with the new nvidia driver
Hi Ben, If Update Manager still wants to install the old driver, go to Synaptic Package Manager and lock the new driver. That way in will stop it from wanting to install the old one. Once the new driver is released then unlock it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/982485 Title: [regression] Nvidia 295.40: Unity 3D does not work at all with the new nvidia driver To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/982485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 982485] Re: [regression] Nvidia 295.40: Unity 3D does not work at all with the new nvidia driver
Just to advise that I have just installed the 295.49 driver and everything is working OK. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/982485 Title: [regression] Nvidia 295.40: Unity 3D does not work at all with the new nvidia driver To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/982485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 982485] Re: [regression] Nvidia 295.40: Unity 3D does not work at all with the new nvidia driver
Has anyone tried the 295.49 driver yet and is it working OK. I have read one prevous post which stated that this driver hung his system. But reading his attached printout it would appear he may have had the 295.40 driver installed and not the 295.49. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/982485 Title: [regression] Nvidia 295.40: Unity 3D does not work at all with the new nvidia driver To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/982485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 982485] Re: [regression] Nvidia 295.40: Unity 3D does not work at all with the new nvidia driver
I still have the 295.33 driver installed and they have been working for the last4 days now since I insalled them without any problems. I do note from post #101 and a couple of others that an updated driver (295.49) is now availale after the troublesome 295.40 driver. Can anyone confirm whether the 295.49 drivers are actually working properly when they are installed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/982485 Title: [regression] Nvidia 295.40: Unity 3D does not work at all with the new nvidia driver To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/982485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 982485] Re: [regression] Nvidia 295.40: Unity 3D does not work at all with the new nvidia driver
Hi Matt, Yes I did read your previous post. Did you try and install the new driver after you done a fresh install or did you try to install to install it on a system you had already tinkered with and changed the settings. I have found from previous experience that it is better to try the new driver after you have done a fesh install of your system as everything is back to the way it should be to except the driver. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/982485 Title: [regression] Nvidia 295.40: Unity 3D does not work at all with the new nvidia driver To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/982485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 982485] Re: [regression] Nvidia 295.40: Unity 3D does not work at all with the new nvidia driver
Alex that looks lik a fix for the 64 bit driver. No mention of a briver for 32 bit systems. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/982485 Title: [regression] Nvidia 295.40: Unity 3D does not work at all with the new nvidia driver To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/982485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 982485] Re: [regression] Nvidia 295.40: Unity 3D does not work at all with the new nvidia driver
Thank you Alejandro. I was able to successfuly install the 295.33 driver through terminal on Precise 12.04. To stop it updating to a higher version of that particular package, I then then installed synaptic package manager and locked the 295.33 package so it cannot be updated. I will leave it that way until a stable version of 295.40 is available. I am sure this has been suggested before but perhaps Canonical should enable the 295.33 driver to be installed in the interim until a proper fix is found for the current 295.40 driver as this is affecting tens of thousands of users. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/982485 Title: [regression] Nvidia 295.40: Unity 3D does not work at all with the new nvidia driver To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/982485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 982485] Re: [regression] Nvidia 295.40: Unity 3D does not work at all with the new nvidia driver
Don Just install the 295.33 driver through your normal terminal with the following commands: sudo add-apt-repository ppa:ubuntu-x-swat/x-updates sudo apt-get update sudo apt-get install nvidia-current=295.33-0ubuntu1~precise~xup1 On reboot it will be working. The update manager will then want to install the current version untick it to stop it from doing so and make sure your updates are only displayed and not installed automatically through settings. Then if you haven't already done so install Synaptic Package manager and find the 295.33 driver on it you installed. Then go to settings and lock this version. It will get a little lock next to it and turn red. Now the driver cannot be updated until you unlock it. I will be keeping it locked until I am absolutely sure the 295.40 driver has been fixed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/982485 Title: [regression] Nvidia 295.40: Unity 3D does not work at all with the new nvidia driver To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/982485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 982485] Re: [regression] Nvidia 295.40: Unity 3D does not work at all with the new nvidia driver
Hi Shahin if you graphics card isn't working reinstall your operating system then try what I have outlined in my previous post. It does work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/982485 Title: [regression] Nvidia 295.40: Unity 3D does not work at all with the new nvidia driver To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/982485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 982485] Re: [regression] Nvidia 295.40: Unity 3D does not work at all with the new nvidia driver
Hi Don Its good to hear you are up and running. I should have mentioned in my previous post that although you have locked the driver from updating in synaptic and update manager. Be careful if you are doing updates through terminal apt-get as this does not recognise the lock in synaptic and will bypass it and you will end up with the 295.40 driver again. At least we have a system that is now running smoothly with no crashes or freezes.Cheers -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/982485 Title: [regression] Nvidia 295.40: Unity 3D does not work at all with the new nvidia driver To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/982485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 982485] Re: [regression] Nvidia 295.40: Unity 3D does not work at all with the new nvidia driver
Hi Bryce I take on board what you are saying but like most of us here and many others out there who have upgraded from a previous version of Ubuntu to 12.04 whether by fresh install or update we expected at a least this these type of basic problems i.e. Graphic Card issues would have been ironed out. I am aware that 295.40 was a security update of 295.33 but .40 is just not working. With many PC's out there using the Nvidia Cards particularly Series 6 and 7 we just want a system that works as it is supposed to not one that crashes, freezes or just does not boot up every time we install the .40 driver. I don't think any Linux based system would receive priority as far as Nvidia go as we are only a minority cummunity out there in the Windows dominated world. Nvidia might fix it today,tomorrow or next week month who knows. In the mean time many are left pulling their hair out with operating systems that just don't work.Cheers -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/982485 Title: [regression] Nvidia 295.40: Unity 3D does not work at all with the new nvidia driver To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/982485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 991861] [NEW] Ubuntu 12.04 fails to boot properly after installing Nvidia Geforce 7100 drivers
Public bug reported: After installing Ubuntu 12.04 on my desktop PC and installing proprietary graphic card drivers and rebooting ubuntu fails to boot up and switches between black screen and flashes of desktop without unity menu. I am currently running on PC Nvidia Geforce 7100 Graphics card. Have tried fresh install several times but just does not work. I also have two laptops. One which I installed 12.04 Beta 2 on a month ago and kept it updated and it has kept running ever since with no issues. The other laptop has 12.04 LTS installed and it has a issue on startup sends a message through apport but does go and has no other issues. Obviously the issue is with the desktop pc. I do note this bug has been around for a while now but has not been addressed. Is it likely to be addressed. I know this has been reported elsewhere but would appreciate being updated. ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/991861 Title: Ubuntu 12.04 fails to boot properly after installing Nvidia Geforce 7100 drivers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/991861/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 327235] Re: unicode-math not included
Same here. Apparently it hasn't been fixed/added in oneiric. How about pangolin? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/327235 Title: unicode-math not included To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texlive-extra/+bug/327235/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 667378] Re: ltsp-build-client --arch i386 failes at password for root
** Changed in: ltsp (Ubuntu) Status: New = Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/667378 Title: ltsp-build-client --arch i386 failes at password for root -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 667378] Re: ltsp-build-client --arch i386 failes at password for root
Found a fix, added the parameters --prompt-rootpass and --purge-root the first probably solved it for me.. -- ltsp-build-client --arch i386 failes at password for root https://bugs.launchpad.net/bugs/667378 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 667378] Re: ltsp-build-client --arch i386 failes at password for root
i meant --purge-chroot -- ltsp-build-client --arch i386 failes at password for root https://bugs.launchpad.net/bugs/667378 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 667378] Re: ltsp-build-client --arch i386 failes at password for root
** Tags added: i386 ltsp ltsp-build-client passwd root -- ltsp-build-client --arch i386 failes at password for root https://bugs.launchpad.net/bugs/667378 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
Re: [Bug 609815] Re: Fresh wubi 10.04 install + package update can brick the system
Hi Jordan, I'd love to look for lupin-support, but yesterday, during another package update, a new kernel got installed that somehow failed to update grub at least that is my guess). This left me with the grub command line when booting. That was the point where I gave up for now. Anyway this might help. In my case 2 partitions are involved. Windows is installed on a small partition (i.e. C:) and I installed Ubuntu on the large data partition (i.e. D:). No RAID configuration since this is a simple laptop. Not sure whether it matters, but there's also a recovery partition located in front of the C: partition. - Recovery (7.81 GB) - OS_Install (43.95 GB) - Data (414 GB) Regards, Alex On Sun, Aug 15, 2010 at 5:51 AM, Jordan jordan.ug...@gmail.com wrote: Could you please check if the package lupin-support is installed? Running apt-cache policy lupin-support in a terminal will tell you. -- Fresh wubi 10.04 install + package update can brick the system https://bugs.launchpad.net/bugs/609815 You received this bug notification because you are a direct subscriber of the bug. Status in Wubi, Windows Ubuntu Installer: Confirmed Status in Ubuntu: Invalid Bug description: Steps to reproduce: Install 10.04 (32-bit desktop edition) within Windows using Wubi. Boot Ubuntu and start a package update. This updates 'grub'. During the package install phase, 'grub' pops up a window that asks you whether or not to perform the update. If you do NOT choose to abort, but choose to let 'grub' update the system, it overwrites the windows master boot record. Result: This bricks the system since neither Windows or Linux boot (since both depend on the Windows bootloader). The solution is to use a recovery disk/stick to replace the MBR by a windows version again. This is not for everyone. So there are 2 problems here: - A newbie user can brick his system. Great way to popularize Linux. - 'grub' manages to ask difficult questions (to inexperienced users) during a routine package update. P.S. Sorry for the ad-hoc bug report. This needs analysis by someone who knows what he/she is talking about. Is this a grub, wubi or generic Ubuntu issue? The problem is real though. To unsubscribe from this bug, go to: https://bugs.launchpad.net/wubi/+bug/609815/+subscribe -- Fresh Wubi 10.04 install + grub update renders system unbootable https://bugs.launchpad.net/bugs/609815 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 609815] [NEW] Fresh wubi 10.04 install + package update can brick the system
Public bug reported: Steps to reproduce: Install 10.04 (32-bit desktop edition) within Windows using Wubi. Boot Ubuntu and start a package update. This updates 'grub'. During the package install phase, 'grub' pops up a window that asks you whether or not to perform the update. If you do NOT choose to abort, but choose to let 'grub' update the system, it overwrites the windows master boot record. Result: This bricks the system since neither Windows or Linux boot (since both depend on the Windows bootloader). The solution is to use a recovery disk/stick to replace the MBR by a windows version again. This is not for everyone. So there are 2 problems here: - A newbie user can brick his system. Great way to popularize Linux. - 'grub' manages to ask difficult questions (to inexperienced users) during a routine package update. P.S. Sorry for the ad-hoc bug report. This needs analysis by someone who knows what he/she is talking about. Is this a grub, wubi or generic Ubuntu issue? The problem is real though. ** Affects: ubuntu Importance: Undecided Status: New -- Fresh wubi 10.04 install + package update can brick the system https://bugs.launchpad.net/bugs/609815 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 524454] Re: Networking is disabled on boot (usually after suspend/hibernate)
I can confirm this problem, at least partially. I'll test some more. I did a fresh install of Lucid on my new PC. First, networking worked fine. Then I tried suspending, but resume did not work so I performed a cold reboot. After that, networking did not come up. The fix proposed, removing NetworkManager.state, fixed it for me. -- Networking is disabled on boot (usually after suspend/hibernate) https://bugs.launchpad.net/bugs/524454 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 553653] [NEW] Ubuntu One replaced a new file with an OLD one, erasing changes and progress I had made.
Public bug reported: Binary package hint: ubuntuone-client None ProblemType: Bug .home.will..cache.ubuntuone.log.syncdaemon.exceptions.log: .home.will..config.ubuntuone.syncdaemon.conf: [bandwidth_throttling] on = False read_limit = 0 write_limit = 0 .home.will..config.ubuntuone.ubuntuone.client.conf: [ubuntuone] connected = False connect = 0 show_applet = 0 bookmarked = True Architecture: amd64 Date: Thu Apr 1 18:25:57 2010 DistroRelease: Ubuntu 9.10 InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027) NonfreeKernelModules: nvidia Package: ubuntuone-client 1.0.3-0ubuntu1 PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-20.57-magicmouse SourcePackage: ubuntuone-client Uname: Linux 2.6.31-20-magicmouse x86_64 ** Affects: ubuntuone-client (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug -- Ubuntu One replaced a new file with an OLD one, erasing changes and progress I had made. https://bugs.launchpad.net/bugs/553653 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 553653] Re: Ubuntu One replaced a new file with an OLD one, erasing changes and progress I had made.
** Attachment added: .home.will..cache.ubuntuone.log.oauth.login.log.txt http://launchpadlibrarian.net/42830699/.home.will..cache.ubuntuone.log.oauth.login.log.txt ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/42830700/Dependencies.txt ** Attachment added: UbuntuoneClientPackages.txt http://launchpadlibrarian.net/42830701/UbuntuoneClientPackages.txt ** Attachment added: XsessionErrors.txt http://launchpadlibrarian.net/42830702/XsessionErrors.txt -- Ubuntu One replaced a new file with an OLD one, erasing changes and progress I had made. https://bugs.launchpad.net/bugs/553653 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 453798] Re: KPackageKit crashing on Karmic
I tried installing kpackagekit-dbgsym but it does not seem to be available. The only dbgsym I could find was: eg...@daedalus:~$ apt-cache search dbgsym pkg-create-dbgsym - automatically build debug symbol ddeb packages Anyway, I tried to run dbg on the process, but right now I could not reproduce the crash. I'll try again when there are more updates to be installed. -- KPackageKit crashing on Karmic https://bugs.launchpad.net/bugs/453798 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kpackagekit in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 453798] [NEW] KPackageKit crashing on Karmic
Public bug reported: While I personally detest kpackagekit and have continued using Adept on Karmic Koala, there seems to be no way around it because every now and then a KPackageKit message pops up telling me there are available updates. Sometimes I then using adept or 'apt-get upgrade' to install the upgrades, but today I gave in and clicked the 'Update now' button in KPackageKit. And wham, it disappeared out of the system tray, doing nothing. I ended up still installing the updates manually. This is not the first time this happens, but somehow I cannot seem to be able to get apport to collect any data about the crash. If I do, I'll try to attach it. Another annoyance is that when installing updates with kpackagekit it needs administrative privileges, I get a GTK popup screen asking for my password instead of the nice kdesudo screen. This doesn't seem right, but might be a different issue. ** Affects: ubuntu Importance: Undecided Status: New -- KPackageKit crashing on Karmic https://bugs.launchpad.net/bugs/453798 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