EzDevInfo.com

There's an issue with an Alpha/Beta Release of Ubuntu, what should I do?

I've been running Alpha releases of Ubuntu for some time now. I keep running into issues - how can I get these resolved? What should I do when I encounter these problems? And where can I find other Ubuntu+1 users to ask questions?

Why did Apport make my bug report private?

Apport detected a crash and assisted with submitting a bug report to Launchpad, but it make the report private. Why?

It doesn't seem very helpful that I'm the only one with permission to read the report. Do I need to now track down someone else to look through it?

What does "Fix Committed" mean?

Is it valid if I mark a bug "Fix Committed" if the package in question is hosted upstream (outside of Launchpad)?

example: bug report, committed fix.

Natural Scrolling doesn't work in 12.04 in some windows. Where should I report the bug?

Natural scrolling using ".Xmodmap": pointer = 1 2 3 5 4 7 6 8 9 10 11 12 doesn't work anymore in 12.04 on some Ubuntu-specific apps like the Software Center, settings window, and update-center. Under what package should I report the bug?

What should I do when Ubuntu freezes?

All operating systems freeze sometimes, and Ubuntu is no exception. What should I do to regain control when...

• just one program stops responding?
• nothing at all responds to mouse clicks or key presses?
• the mouse stops moving entirely?

In what order should I try various solutions before deciding to pull the power plug?

What should I do when starting up Ubuntu fails? Is there a diagnostic procedure I can follow?

What tools do I need to use to report a bug in a developers PPA?

When you want to report an error the best way to report a package in Ubuntu is sudo ubuntu-bug package.

But what if the package is in a developers PPA and I want to report an error with enough information, what tools can I use to generate that necessary information?

Should I include logs that contain "sensitive information"?

Sometimes, when info is being collected by ubuntu-bug (either automatically following a program crash or by manually calling it) the following dialog pops up:

Should I include these files or not? What is "dangerous" about someone else know my computer's hostname?

I want to fix a bug. Where do I start?

Although I am not a professional programmer, I have written a program or two. Yet, nowadays every engineer and scientist learns to program a bit as well, and as such I am used to writing programs in Python, C and MATLAB. Now I want to give back a bit to Ubuntu and its great folks and fix a bug!

I had a look at the list of the bitesize campaign and had to find that most of them are not that easy for me to fix as I suspect they require a lot of time to get into the matter, and I do not have that. Still I discovered this one and it looks manageable and like a cool feature to me.

As I have never written a patch or released a program to the wild before though, I have no idea where to start. What should be my first step to tackle that problem?

Bottom line: Where and how do I start fixing that guy?

How can I track a bug that caused a crash and was reported via apport / whoopsie?

It used to be that when a program crashed, especially when a user was using a pre-release of Ubuntu, apport could be used to open a bug report. The user could then track the bug, see if it affected others, help fix it, etc.

As of Precise 12.04, this behavior and workflow changed. As I discovered in Bug #993450 “Apport fails to submit bug report”, by default apport no longer opens a bug report (and it is awkward but not impossible to get it to do so). At the same time people are noticing a new "whoopsie" process, as described at What is the 'whoopsie' process and what does it do?.

After some more googling, I dug this blueprint up, which describes the whole process: ErrorTracker - Ubuntu Wiki. (It didn't mention whoopsie or daisy, so I added them - please correct me if I got it wrong).

Wow - this sounds like great work to streamline and improve the crash reporting process.

I'm left with this question: how does a user learn what the status of the problem is? The blueprint now has this requirement

The user should have some way to check back on the status of their crash report; e.g. have some report ID they can look at to see statistics and/or any associated bug #. E.g. provide a serial number at time of filing that they can load via a web page later on.

which seems unimplemented. Is there anything available in the meantime?

And how does a developer get into the game? Going to https://daisy.ubuntu.com just provides an "Incorrect Content-Type" error message.

Finally, I suggest documenting the apport behavior changes in the Release Notes. It should be of interest to anyone who has been trying to help out Ubuntu.

Where can I send feature requests?

Where can I send feature requests? Both for Ubuntu as a whole and individual (supported) apps?

Should I report an old bug that is still present?

Hot corners enabled via the Unity tweak tool in Ubuntu 16.04 do not work properly after rebooting. I've seen that this bug has been present since 14.04 and it has been reported on Launchpad, but it was just "confirmed". Should I report the bug again?

How do I subscribe to a bug?

Sometimes people tell me to subscribe to a Launchpad bug so I can follow along it's progress, how do I do this?

How are Ubuntu bugs' importance values decided?

How is a specific bug's importance decided for bugs against packages in ubuntu?

And by Importance, I mean 'Low', 'Medium', and other importance values on the Launchpad bug trackers.

16.04 LTS wifi connection issues

I discovered several issues with wifi connection after installing 16.04 LTS.

First, wifi doesn't reconnect normally after sleep or hibernation. Sometimes the network icon turns into a "up and down arrows"(I don't know what it is for) after waking up but is still connected. Sometimes network is simply lost and it doesn't display any network in the list so there's simply no way to use wifi at all.

I first tried restarting network manager by running sudo service network-manager restart. It worked but was not a permanent resolution.

Then according to another thread, I added SUSPEND_MODULES="iwlwifi"to

/etc/pm/config.d/config

After doing this, the reconnect issue seems to be fixed(can automatically reconnect and icon doesn't change anymore.) However, I find the wifi connection gets lost randomly (about every 30 minutes) even when the computer is running and the network icon remains the connected state when connection is lost.

Another issue after adding the code is, when I put my computer to sleep, the screen will turn off for a second but then turns back on for around 5 seconds(during which the system will cut off wifi connection). And then the computer will go to sleep after this unusual "two-phase" process.

Plz find Wireless Cards info below

*-network               
       description: Wireless interface
       product: RTL8723BE PCIe Wireless Network Adapter
       vendor: Realtek Semiconductor Co., Ltd.
       physical id: 0
       bus info: pci@0000:02:00.0
       logical name: wlp2s0
       version: 00
       serial: b0:c0:90:5c:1c:d5
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
       configuration: broadcast=yes driver=rtl8723be driverversion=4.4.0-21-generic firmware=N/A ip=192.168.0.8 latency=0 link=yes multicast=yes wireless=IEEE 802.11bgn
       resources: irq:16 ioport:d000(size=256) memory:df200000-df203fff

00:00.0 Host bridge: Intel Corporation Sky Lake Host Bridge/DRAM Registers (rev 07)
00:01.0 PCI bridge: Intel Corporation Sky Lake PCIe Controller (x16) (rev 07)
00:02.0 VGA compatible controller: Intel Corporation Sky Lake Integrated Graphics (rev 06)
00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI Controller (rev 31)
00:14.2 Signal processing controller: Intel Corporation Sunrise Point-H Thermal subsystem (rev 31)
00:16.0 Communication controller: Intel Corporation Sunrise Point-H CSME HECI #1 (rev 31)
00:17.0 SATA controller: Intel Corporation Sunrise Point-H SATA controller [AHCI mode] (rev 31)
00:1c.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #1 (rev f1)
00:1d.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #9 (rev f1)
00:1f.0 ISA bridge: Intel Corporation Sunrise Point-H LPC Controller (rev 31)
00:1f.2 Memory controller: Intel Corporation Sunrise Point-H PMC (rev 31)
00:1f.3 Audio device: Intel Corporation Sunrise Point-H HD Audio (rev 31)
00:1f.4 SMBus: Intel Corporation Sunrise Point-H SMBus (rev 31)
00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (2) I219-V (rev 31)
01:00.0 VGA compatible controller: NVIDIA Corporation GK208 [GeForce GT 730] (rev a1)
01:00.1 Audio device: NVIDIA Corporation GK208 HDMI/DP Audio Controller (rev a1)
02:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8723BE PCIe Wireless Network Adapter
03:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller (rev 01)

05/01/2016 Update: I don't know what happened but the issue gets worse now. Wifi connection gets lost about every 5 minutes and I have to reconnect or restart network-manager.

How do I report a bug?

I found a problem with an application on Ubuntu.

Questions :

• How do I best report the issue?
• What sort of information should I provide?